This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Siemens Enterprise Communications GmbH & Co. KG is a trademark licensee of Siemens AG
AMOs Siemens
1.3 AMO Syntax
The AMO (Administration, Maintenance and Organization) stands for administration and main-tenance tasks that are needed for setting up, managing, troubleshooting, maintaining and com-missioning the HiPath 4000 system.
It is primarily a script language that is checked for correct syntax by the system. Tips are stored to provide the user with helpful information.
Syntactically incorrect entries are rejected by the system and the AMO enters a so-called prompt status. It requests entry of the correct values.
Syntactically correct but functionally incorrect entries are not queried.
Thus, for example, all executive-secretary groups can be accidentally deleted by an uninten-tional command.
1.3.1 Structure of a command
> An AMO never asks whether you really want to delete everything.
VERBADDCHANGEDISPLAYSTARTSTOP
USW.
NOUN:SBCSU:PERSI:DATE:COPY:GEZAB:
USW.
The VERB, or the action that is to be executed, is separated from the command, the NOUN, by a minus sign.
Between the invocation and the following parameters, acolon is used as a separator from the parameters.
One option for administration is the keyword-oriented entry. The parameter(s) are named and entered, which can also result in chains linked with a "§".
Parameter&Parameter&& Parameter,
If you would like to set up the same devices multiple times, you can also create the link with "&&", in which case the execution is from value to value. Up to ten links are possible.
The individual parameters are separated by a comma.
In addition to the keyword-oriented entry, a position-oriented entry is also possible. In this case, you need to know the position of the parameters and comment out those that are not re-quired. A mixture of both parameter entry types is not possible.
A semicolon is always placed at the end of an entry. This is performed automatically by the sys-tem when the AMO is run through but can also take place during entry if no other entries are needed. If parameters are still missing after all, the AMO outputs a query. You can enter a "?" or "??" for each query. You are then given a tip.
Mandatory parameters
Selectable mandatory
Freely selectable pa-rameters
Parameters that the AMO needs in order to fulfill its function and that cannot be replaced by its own values. One example is the station number of a subscriber.
Parameters that must be set but that can be supple-mented through default values or own search en-tries.
Parameters that have optional functions.These are generally not entered.
( ) EXPLANATORY TEXT PASSAGES[ ] PARAMETER NAME and PARAMETER VALUE may be entered.< > Name of PARAMETER VALUE, all possible values are explained
separately..{ } Entry of at least one PARAMETER, rest optional: Separating COMMAND CODE and PARAMETER- Separating ACTIVITY and FUNCTIONS OF THE COMMAND CODE; END of AMO INPUT
PARAMETER NAME = PARAMETER VALUE
One of the given PARAMETER VALUES must be assigned to the PARAMETER NAME.
PARAMETER NAME = <PARAMETER VALUE>
An individual value, a string of individual values, or a group of individual values must be allocated to the PARAMETER NAME.
[PARAMETER NAME = <PARAMETER VALUE>]
Optional input of PARAMETER NAME, PARAMETER VALUE.
& & STRING of INDIVIDUAL VALUES && GROUP of INDIVIDUAL VALUESI OR GATING - one of the given parameters is entered up to the semicolon as
an alternative.
<number> PARAMETER consists of DECIMAL NUMBER(S)<param> PARAMETER VALUE consists of LETTERS A...Z, DIGITS 0...9<string> PARAMETER VALUE consists of CHARACTERS (all except ', ”)<key-num> PARAMETER VALUE consists of CHARACTERS 0...9, A...D, *, #<a-b-c...> PARAMETER VALUE consists of PARAMETER ARGUMENTS<identifier> PARAMETER VALUE consists of CHARACTERS (A...Z, 0...9)
DISPLAY-PERSI TYPE =SYS;I TYPE = COPIN, [COPIN=<number>] ;I TYPE = MODULO ;I TYPE = NAME, [STNO=<number>] ;I TYPE = PIN, [PIN=<string>] ,[PINTYPE=<number>] ;I TYPE = STN, [STNO=<number>], PINTYPE=<string>] ;I TYPE = CCMS, [CCMSCD=<keynum>],[DPLN=<number>],[STNO=<number>] ;
Siemens Enterprise Communications GmbH & Co. KG is a trademark licensee of Siemens AG
AMOs Siemens
3 Protection of software features (codeword)
3.1 Feature description
Features are sold in feature packages. Each package is allocated a marketing value. The fea-ture quantities purchased by a customer are encrypted as an alphanumeric "codeword".The new hardware, HiPath 4000 V2, features a SIM card on the DSCXL board (ADP). The don-gle used for existing hardware is upwards compatible. However, if the system is upgraded to Hipath 4000 V2.0 then a new codeword has to be installed.
New hardware: Old hardware:
The dongle or the SIM card and the codeword "tell" the system which feature packages and quantities were purchased by the customer. When the system is configured, a special plausi-bility check is used to ensure that the configuration data corresponds to the purchased features and quantities.
SIM card on the DSCXL board (ADP) Dongle for existing systems
Siemens Enterprise Communications GmbH & Co. KG is a trademark licensee of Siemens AG
AMOs Siemens
3.2 Codeword variants
In HiPath 4000 V2.0 and later, the CODEWORD will feature four variants:
1. Normal mode:This is the approved operating mode as implemented in HiPath 1.0. In normal mode, a codeword and licenses are requested for all relevant licenses in the database.
2. Trial mode:This feature introduces a time-limited trial mode. When you activate trial mode, you can skip the license restrictions that are temporarily displayed. During this time, the AMOs work as if unrestricted licenses were available except that an advisory message is sent to the users if license restriction violations occur.
3. Emergency mode: The system activates the Emergency mode, in case of special situations. Special situations are:Validity of the Codeword is expired;Dongle resp. SIM card is missing;Codeword is missing;Dongle resp. SIM card does not match to Codeword;In the Emergency mode the AMO execution is blocked in the SWU. The only AMOs that can be executed are the AMO CODEW / DATE.
4. Escalated Emergency mode:The feature triggers an additional system operation restriction (it blocks the FEASU fea-ture) when the system is in escalation mode for an extended period of time. This restriction is known as escalation of the Emergency mode.
● In a network the network codeword from the Hipath 4000 Manager (LMT) is used. The original Codeword must be added previously in the system. The Network codeword then overwrites the Codeword on a daily basis. If this does not hap-pen then a 60 day test mode begins.
● The 30 Day Service-Dongle will no longer be given in Hipath4000 V2.0.
● The creation date is coded in the Codeword and is stored in the database, when the Code-word is added in the system. The possibility to add an older Codeword is blocked in this way.
TYPE Description Dongle Sim Card
TYPE 1 (Customer) standard: 2 x Test mode each for 30 days(then a new Codeword is required)
X X
TYPE 2 (Special) Via LMT (Licence Management Tool) with a time limit of 60 days or an agreed time limit
X X
Via LMT (Licence Management Tool) without a time limit
Siemens Enterprise Communications GmbH & Co. KG is a trademark licensee of Siemens AG
AMOs Siemens
3.3 Codew description
Unit Description AMOs Parameter
COMSCENDO Counting/marketingper configured B channel/ana-log channel to:
– station (optiset = 1 B chan-nel; optiset E or optiPoint 500... with adapter = 2 B chan-nels; optiip = 1 B channel, butmax. 2 B channels per Up0E)or attendant console
Siemens Enterprise Communications GmbH & Co. KG is a trademark licensee of Siemens AG
AMOs Siemens
● The expiry date is shown after each LOGON command or after the initial ADD command. You can also check the date with the DISPLAY-CODEW command.
● A new codeword is needed every time the purchased quantity is expanded.(Except "HIPATH AP VOICE COMPRESSION IP" where only the coding is dynamically changed (from G.729 to G.711) when the limit is reached.)The purchased quantity can be temporarily expanded in trial mode (see Section 1.2).
● An installed codeword only can be replaced by a new one. The creation date is saved in the codeword; the serial number is used for information purposes only.
● The codeword can be changed with the codeword tool.
● The hardware ID and codeword must match.
● In order to enter a codeword the date of the system must be valid.
● In the event of contractual violation, the user interface is disabled and you are prevented from starting any more SWU AMOs (for configuration).
● If the system prevents access although the codeword and dongle are valid, you can acti-vate the dongle with the following actions: unplug/plug in the dongle, enable line8 or per-form an A1 soft restart.
● Further information on the AMO CODEW can be found in the AMO description in theservice manual.
3.5 Generation (example)
● Add a codeword (dongle or SIM card must be inserted):
The purchased quantity can be temporarily expanded with trial mode.Trial mode is activated with CHANGE-CODEW. Utilization is not unlimited (maximum number specified in codeword, generally 2) and has a maximum utilization time (generally 30 days).
SWU administration is not disabled even if license violation is shown in trial mode ("!!!!!" in the "FREE" column). A mark that can be displaced with the AMO SDSU is applied to elements that exceed the license limit (stations, trunks, etc.). The number of units marked is also displayed in the AMO CODEW.
Trial mode is automatically terminated if not manually deactivated within the maximum time lim-it. When this happens, marked elements are disabled for security reasons and can only be en-abled if an appropriate codeword is set up.
No elements are marked or disabled for the features HIPATH PROCENTER ENTRY AGENT and HIPATH AP VOICE COMPRESSION IP. However, when trial mode ends, no agents above and beyond the license limits can log on and compressed connections cannot be set up.
Trial mode does not apply to the features HIPATH AP REMOTE SURVIVABILITY and CC-AP FOR AP EMERGENCY. The codeword’s license limit cannot be exceeded here.
● Activate trial mode:
CHANGE-CODEW:TRIAL=YES;
....(activated after consultation)
● Administration above and beyond the quantities purchased:
A new license concept based on the HiPath License Management (HLM) is used. The SIM card is not used anymore.
A HiPath 4000 V6 Flex License pro Port for all HiPath 4000 subscriber and Trunking connec-tions is available: analog, digital, HFA, SIP, Cordless, PSTN and SIP Service Provider.
After a first configuration with the Portal automatically a „grace period“ license will be generat-ed. This license is valid for 30 days.
A customer license must be created with MAC address (e.g. eth0 of the DSCXL2 board) and L-number. The created „.lic file“ can be downloaded with the Assistant. The Assistant creates a Codew for the RMX.
3.7 License Management in the HiPath 4000 Assistant V6
With the menu „HiPath 4000 Assistant V6 --> Access Management --> License Management“ the license can be downloaded and displayed.
Siemens Enterprise Communications GmbH & Co. KG is a trademark licensee of Siemens AG
AMOs Siemens
5 WABE - Digit Analysis
"Digit analysis" refers to the assignment of a digit analysis result (DAR) to a dialed digit se-quence or code. This assignment is dependent on the call progress state (CPS) and digit anal-ysis group or dial plan (DPLN). There are two types of digit analysis result: DARs with a specific dialing outcome (e.g. ’STN’; dialing result is station number), and DARs whose dialing outcome must be defined in other AMOs (e.g. ’CO’; the trunk routes which can be accessed via this DAR are defined with the AMO RICHT).
5.1 Structure of the DPLN
Digit Analysis is comprised of a general DPLN (WABE) part and one of 16 DPLN groups.
DPLN - General Part (valid for all dial plans)
Here are listed all codes for those digit analysis results (DAR) which are to be accessible for all stations (valid for all dial plans).
All stations (DAR=STN) must be listed here.
DIS-WABE:GEN;
Displays only the general part!
DPLN 0 DPLN 1 DPLN 2 . . .14 DPLN 15
Codes for digit analysis results (DAR) in this area are only accessi-ble for stations belong-ing to DPLN 1.
Station Number 4511 DIS-WABE:GEN,1;
Displays all DPLN entries for stations with DPLN 1.(DPLN general part and DPLN 1)
If STN is assigned to DPLN 1, SCSU/S(B)CSU must have parameter DPLN=1.
With this he gets access to all codes of the DPLN valid for all DPLN groups as well as the codes of DPLN 1.
Associated pairs for simultaneous processing are listed in Table 5-1 and pairs for sequential processing in Table 5-2. Digit analysis results AFWDVCE, ADND and ACOSX can also be used as 'feature toggling' digit analysis results. Thus, in the case of these digit analysis results, it is no longer necessary to handle them in pairs with the corresponding deactivation digit analysis results.
There are more features connected to special DARs, e.g. there are only decimal digits allowed with DAR STN or FLASHCD, also only 1 digit is allowed for DAR FLASHCD
Siemens Enterprise Communications GmbH & Co. KG is a trademark licensee of Siemens AG
AMOs Siemens
6 VBZ - Internal Traffic Restrictions
The internal traffic restriction matrix regulates communications among the traffic groups (ITR groups). Stations and trunks are combined into ITR groups which have an identical traffic re-striction matrix, i.e. which have the same traffic restrictions to other ITR groups.
Relations between ITR groups can be set up and changed as desired with the ITR matrix.
Only a portion of the total communications of the switching unit is regulated with the ITR matrix. The matrix is only queried when the dialing outcome is a station (also master station in a hunt group).
The following traffic relations between two groups are possible:
● A = allowed
● D = denied
Thus directional traffic restrictions between two ITR groups can also be regulated.
The traffic relation within one group must always be allowed. For that reason, the diagonal line of the matrix may not be altered (always contains the entry "A").
A second static matrix is used to regulate traffic relations between card users and card readers. This matrix is administrated by the AMO VBZA.
The features "controlled station restriction" and "controlled station restriction - group", as well as "controlled station-to-station restriction", do not affect the ITR matrix. For these features, a separate table exists, which is administrated by the AMO ACTDA.
The ITR matrix is created from the database and initialized with A (= allowed). As a result, an ADD branch for the AMO VBZ is not necessary.
Siemens Enterprise Communications GmbH & Co. KG is a trademark licensee of Siemens AG
AMOs Siemens
7 COSSU - Classes of Service
The classes of service contain combinations of authorizations and features and are assigned to one ore more stations (AMO-ACSU, AMO-SBCSU, AMO-SCSU resp. AMO-SSCSU). Class-es of service are also assigned to trunks for call traffic (AMO-TACSU, AMO-TDCSU resp. AMO-TSCSU).
Each class of service is divided into 3 services:
– Voice (VCE)
– Facsimile (FAX)
– Data Terminal (DTE)
Table 1 shows the COS authorizations, a description of the authorization, the service in which each authorization is applicable, and whether an autorization effects a station and/or a trunk. This table is only a compilation of classmarks. It does not allow you to establish cross-referenc-es between the different authorizations.
The -without direct trunk access- and -without tie trunk access- authorizations for the specified service are indicated by the fact that the direct trunk access and tie trunk access authorizations are not set for the corresponding service.
● COS 0 is not a valid class of service.
● LCR classes of service
Change, display, and regenerate LCR classes of service, each with up to 64 LCR authori-zations and LCR options (for example, LCR expensive route tone).
Sixty-four LCR classes of service are permanently configured, 32 of which are for voice, fax, and 32 of which are for data.
LCOSV=1 is initialized for the attendant console with all the authorizations. The others are initialized without contents and edited by means of the branch CHANGE
Siemens Enterprise Communications GmbH & Co. KG is a trademark licensee of Siemens AG
AMOs Siemens
8 TAPRO - Key Programming
The AMO TAPRO is used for loading the programmable key functions of digital and IP voice terminals.
Various standard or individual key assignments can be loaded. The AMO TAPRO also allows individual key functions to be changed. Furthermore, the AMO is used for the administration of the standard key assignments. As Spirit IP Phones will be configured using the already existing opti-IP device configuration, the required TAPRO functionality to allow administration of Key Layouts for Spirit IP Phones (with or without Key System Functionality) is already present. TAP-RO is extended to delete information on which type of Electronic Key Label shall be used and which individual text shall be used for the Electronic Key Label
In the generation sequence, AMO TAPRO is called at two points in the batch: before AMO SBC-SU to change standard key assignments, and after AMO SBCSU/SSCSU to change individual keys
Functions
The AMO TAPRO can be used for the following terminal types:
● optiset E T3 / T8 / T12
● optiPoint 500 T8 / T12 / T19
● optiPoint 600 T19
● optiPoint 4x0 T8 / T12 / T19
● optiPoint WL2 professional
● OpenStage 10, 15, 20, 30, 40,60 and 80
● OpenClient
● as well as the various add-on terminal types
With the AMO TAPRO, it is not necessary to set up the standard key assignments, since all 127 for optiset valid standard assignments for each terminal type are already stored in the data-base. All terminals are allocated one of these standard assignments when they are first config-ured.
● The terminal will be not deactivated from the AMO TAPRO, exception deletion of DSS keys.
● If the terminal was deactivated before the processing, it remain deactivated.
● A standard key layout with add-on terminal can be assigned to a subscriber OPTISET with-out add-on terminal, but only the key functions of the basic terminal are accepted.
Siemens Enterprise Communications GmbH & Co. KG is a trademark licensee of Siemens AG
AMOs Siemens
9 SBCSU - Station and S0 Bus Configuration of SWU
The AMO SBCSU configures terminal devices (stations) at S0 bus connections, S0 interfaces, Up0/E interfaces, IP interface and on the ATM switch. A maximum of one voice terminal may be assigned to an S0 bus. A maximum of three terminals with three different station numbers can be set up per Up0/E access. Apart from configuring stations, the AMO SBCSU offers the options of displaying, regenerating and changing the associated data, as well as cancelling sta-tion assignments.
The AMO SBCSU assigns all station combinations which contain the following terminals. All other station combinations are assigned with the aid of the AMOs SCSU or SSCSU.
● The following terminals are configured for the VOICE service:
– OPTISET: Digital telephone for Up0/E interface and CorNet-TS protocol
– OPTIP500: Digital telephone for Up0/E interface and CorNet-TS protocol
– OPTIIP: Digital telephone for IP interface and CorNet-TS protocol
– SET600: Digital telephone for S0 interface and EDSS1 (EURO-ISDN) or NI-BRI protocol
– ANADEV: Analog voice terminal(connected to Up0/E via terminal adapter a/b)
– Terminal equipment for Cordless Multicell Integration (CMI Version >= V2.2):BASE: CMI base station with Up0/E interface and CorNet-TS protocolRADIO: CMI mobile user with Up0/E interface and CorNet-TS protocolEXTLINE: CMI Extension connection with S0 interface and EDSS1 (EURO-ISDN) pro-tocol
– Voice terminal equipment with SIP or S0 or S2 interfaces
● The following terminals are configured for non-voice services only:
– API: Workstation protocol interface and CorNet protocol (DATA service)
– ANADEV: analog non-voice terminal (DTE and FAX)(connected to Up0/E via terminal adapter a/b)
● DTE:
– digital DTE with S0 interface, EDSS1 (EURO-ISDN) protocol
– digital DTE with U2B1Q interface, NI-BRI protocol
– digital DTE with V.24 interface (connected via terminal adapter), EDSS1 (EURO-ISDN) protocol
– digital DTE with U2B1Q interface (connected via terminal adapter),NI-BRI protocol
– analog DTE (connected to S0 via terminal adapter a/b and modem)
● FAX:
– Group 2 and 3 (connected to S0 via terminal adapter a/b)
– Group 4, EDSS1 (EURO-ISDN) or NI-BRI??? protocol
● Non-voice terminal equipment with S0 or S2 interfaces, e.g. DP systems, LANs, Servers.
The type of non-voice terminal equipment for DTE and FAX connected to S0 (analog, digital S0, digital X.21) is not taken into account for the purpose of assignment in this AMO. In addition to the terminal name, only the protocol type parameter DPROT resp. FPROT must be declared. The terminal attributes, which are not relevant for assignment purposes, are determined when the terminal first responds to a polling message at the bus connection or the station line circuit.
The terminals are assigned to the following modules:SLMS (S0 interface) (to Hicom H V1.0)
STMD (S0 interface) (to Hicom H V1.0)
STMD2, STMD3 (S0 interface)
DIU-N2, DIU-N4 (S2 interface)
DIU-S2 (S2 interface)
SLMQ (ANSI-U interface)In the case of extremely long lines (from 1-2 km up to 9 km)
SLMQ3 (U2B1Q interface)
SLC16 / SLC24 (Up0/E interface)
SLMO, SLMO16, SLMO24, SLMOP, SLOP2
(Up0/E interface)
STHC, STHC2 (combination of STMD and SLMO, i.e. S0 as well as Up0/E interface)
Siemens Enterprise Communications GmbH & Co. KG is a trademark licensee of Siemens AG
AMOs Siemens
Functions
● ADD Configuring the static and dynamic memories in the CC and the LTGs for the above-described device combinations as well as entering the static device data
● CHANGE Changing the static device data .
● DELETE Deleting specific service assignments or an entire station configura-tion
● DISPLAY Interrogating existing station configurations
● REGENERATE Regenerating existing station configurations
The digital terminals at S0/Up0/UpoE such as SET600/OPTISET/OPTIP500 are set up using AMO SBCSU.
Special subscribers (e.g. Hicom Trading Board subscribers) are configured by AMO SSCSU.
Each STN number can be assigned personalized data such as names or personal identification numbers (PIN) using AMO PERSI.
AMO TGER is used to assign additional station numbers to non-voice terminals which have al-ready been assigned a number (AMO SCSU/SBCSU).
It is also possible to configure "virtual" ports for all device types which have not been assigned to a module but are configured in the same way as regular physical ports. Virtual ports are iden-tified as INS=FLOAT or INS=ACLSTN. These ports are used by any ID card user who identifies himself at another terminal by inserting his ID card or by keying in the PIN, and who then makes the call using the features of his virtual port such as classmarks, speed dialing digit series etc.. An ANATECM is not allowed to be configured as virtual port.
It is also possible to install a signed off fictive station by depicting INS=SIGNOFF. A signed off station can only be an ANATE. Signed off stations can be signed on
● by entering a PIN-Number and a key number at the specific terminal or
● by being signed on terminal by means of service staff
● by administration command (AMO DSSU)
Signed off stations can be added to communication groups such as pick up groups, hunting groups etc. This allows a complete preconfiguration of subscribers.
For "virtual" ports (e.g. INS=FLOAT) PEN-specific parameters (e.g. COFIDX) are ignored.
A suffix-dialing connection is required for connecting special facilities such as VMX servers. This connection is identified as SPEC=SUFDIAL and parameterized using the parameter DH-PAR.
For special stations (e.g. COMTEL) and for special country specific adaptions in SLMA1/SLMA2/SLMA3/SLMA24/SLMAB/SLMAR-Loadware parameterization can be done by using parameter DHPAR.
Some special subscribers like Voice Pagers etc. are configured using parameter SPEC.
● ADD Configuring the static and dynamic memories in the CC and the LTGs for the above-described device combinations as well as entering the static device data
● CHANGE Changing the static device data .
● DELETE Deleting specific service assignments or an entire station configura-tion
● DISPLAY Interrogating existing station configurations
● REGENERATE Regenerating existing station configurations
Authorizations (COS)- and LCR-Authorizations (LCOS) classesLCOSV for service voiceLCOSD for service data1 for day authorization2 for night authorizationRelated AMOs:- for content:COSSU, SDAT- for LCR:LDPLN, LDAT
DPLN-group 0-15Standard=0Related AMO:WABE
ITR-group 0-15Standard=0Related AMO:VBZ
Secret station numberIf “yes” is selected, the setting of the AMOZAND instead of PERSI is used.Related AMOs:ZAND: ALLDATA2, DISPNUUM=XXXIf ONLYEXT is selected, it is possible to trans-mit an other number instead of the extensionnumber.Related AMO:KNMAT: MODCON=REPEXT
COSX-group 0-15Standard=0Related AMOs:BERUM, BERUZ for switchingFEASU: COSXCD, COSXDB, COSXKEY,COSXATND, COSXTWABE: DAR ACOSX/DCOSXPERSI: PIN for COPIN 7 for the STN
SecretarySubscriber is secretary of a “CHESE”executive-secretary groupRelated AMO:CHESE
Number of add-on devicesdependent of the device: 0-4
Station in serviceyes/no or signed off (no PEN is used)
Alarm number0: no alarm assigned8-519: number of directional alarm group520-583: number of personal alarm groupRelated AMOs:VADSU
Reject call back on busyAttention to parameter CBKBMAX in AMOSBCSU.
Related AMOs:FEASU: CBK, DCBB, DCBNOAZAND: ALLDATA, CBKNO(number of callbacks for a STN activated incase of busy or no answer)
Reject call back on no answerAttention to parameter CBKBMAX in AMOSBCSU.
Related AMOs:FEASU: CBK, DCBB, DCBNOAZAND: ALLDATA, CBKNO(number of callbacks for a STN activated incase of busy or no answer)
Max. number of callback1-5 or 99Attention to parameter RCBKB in AMO SBCSU Related AMOs:FEASU: CBK, DCBB, DCBNOAZAND: ALLDATA, CBKNO(number of callbacks for a STN activated incase of busy or no answer)
HeadsetWITHIND Headset with HW indicationNOIND: Headset without HW indicationAttention to parameter HSKEY in AMO SBCSU
Function of the HS key (Head set key)NORMAL: HS key must be used for answerHSGIND: HS key for indication of the head setRelated AMO:TAPRO
Text selector for display
Related AMOs:ZAND: ALLDATA2, TEXTSELIn ACTIVE TEXTSEL up to 5 languages can beselected.An user should select the language with a key:TAPRO: key LANSELSDAT: Attribute LNGDYN or LNGSTAT
Callback on no answer is stored in the mail-boxAttention to parameter RCBKNA in AMO SBC-SU
Related AMOs:FEASU: CBK, DCBB, DCBNOAZAND: ALLDATA, CBKNO
Siemens Enterprise Communications GmbH & Co. KG is a trademark licensee of Siemens AG
AMOs Siemens
11.2 Configuration of an IP subscriber
An IP-device like e.g. optiPoint 400, optiPoint 410, optiPoint 420 and optiPoint 600 will be con-figured in principle like a UP0/E subscriber. Additional resp. other parameters will be shown in the next part.
Siemens Enterprise Communications GmbH & Co. KG is a trademark licensee of Siemens AG
AMOs Siemens
12 SDAT - Administration of Individual Subscriber Attributes and General Subscriber Data
The AMO SDAT can be used to administer subscriber-related attributes and features for the voice service. It can process subscribers who have been added with the AMO SCSU, SBCSU, or SBCSU.
It can also be used to administer general data that is independent of any particular device.
12.1 CHANGE-SDAT
12.1.1 Changing Attributes / Features
When attributes are changed (added / removed), compatibility checks are carried out to test the following:
a) whether the attributes entered - or those already existing - are compatible with each other,
b) whether the attributes entered are compatible with the type of equipment belonging to the subscriber,
c) whether the attributes entered are compatible with special subscriber data
When attributes are added for ACD SUPERVISOR a check is carried out to establish whether there are sufficient purchased subscribers of this type.
When an ACD attribute is removed, a check is carried out to establish whether there are still ACD group relationships.
12.1.2 Changing General Subscriber Data (Branch DATA)
In this branch, it is possible to change general subscriber data that is independent of any device. This data consists of parameters that are processed in the AMO SBCSU and in the AMO SCSU and SSCSU.The checks correspond to the checks in the AMO with which the subscriber being changed was added.
12.1.3 Changing Subscriber Data (Branch DATA1)
In this branch, it is possible to change additional subscriber data. This data consists of param-eters that are processed with AMO SDAT only. AMO SBCSU, SCSU and SSCSU can not pro-cess this data.
Siemens Enterprise Communications GmbH & Co. KG is a trademark licensee of Siemens AG
AMOs Siemens
13 BERUM - Class of Service Switchover
Stations are allocated two classes of service (COS1 and COS2) in (COS1 = normal or day COS COS2 = alternative or night COS) in their line tables.The class of service are maintained by AMO COSSU and assigned to stations with the AMOs SCSU and SBCSU.An identifier (COS pointer) in the line tables indicates which COS is active.
AMO SCSU and AMO SBCSU subdivides the stations into COS switchover groups (COSX groups). This is performed in order to group stations so that a certain COS can be switched active for all of them.If no specific allocation has been made, a station belongs to COSX group 00. Stations with an active key switch (KEYSTN) are not changed over, but they are still assigned to a COSX group. The COSX groups are independent of other station groups formed on the basis of other fea-tures.
Switchover between the two classes of service can be performed from a station, from an atten-dant console, centrally using the AMO, via data channel and/or by means of a timed switchover.
a) COS Switchover from the Station
A station authorized for this type of switchover can switch over between the COSs us-ing the personal ID number (PIN) and a code for switchover using an active key switch (KEYSTN). As long as the alternative COS (COS2) is active, the user hears the special dial tone when he lifts the receiver. The station is assigned the authorization COSXCD (COS switchover by code) by AMO COSSU in order to be able to perform a switchover using the PIN. The PIN (maximum of 12 digits) is defined by the AMO PERSI.
b) COS Switchover from the Attendant Console (ATND)
Switchover of the normal COS of the COSX groups to an alternative COS can be per-formed from every attendant console, including the night attendant console (performed with the task BEZUM).
c) COS Switchover by AMO
COS switchover for COSX groups of stations can be performed using the AMO BERUM.
d) COS switchover using a data processing system (DVA) is implemented via a data channel.
The COS switchover for COSX groups can be carried out automatically at a specific, definable time. This time is defined using the AMO BERUZ (time table for times at which class of service switchover is to occur). Switchover is carried out by the task BEZUM.
Priorities for COS Switchover
The last COS switchover performed for a station is always in effect, regardless of where this change was carried out (from the station, from the attendant console or automatically).
Siemens Enterprise Communications GmbH & Co. KG is a trademark licensee of Siemens AG
AMOs Siemens
14 BERUZ - Times at which Class of Service Switchover is to Occur
Stations (configured by AMO SCSU and AMO SBCSU) are allocated two classes of service COS1 and COS2) in their line tables. A class of service contains the authorizations of a station. An identifier (COS pointer) in the line tables indicates which COS is active, i.e. which of the sta-tion’s authorizations are currently activated; this is usually COS1. AMO SCSU and AMO SBCSU subdivides stations into COS switchover groups. This is per-formed in order to group stations so that a certain COS can be switched active for all of them. The COSX groups are independent of other station groups formed by other features. If no specific allocation has been made, a station belongs to COSX group 0. Stations with an active key switch (KEYSTN) are not switched over, but they are still assigned to a COSX group.
The classes of service can be switched over from a station, from an attendant console, y means of AMO BERUM, via data channel, and/or by means of a timed switchover.
Switchover at a fixed Time (timed Switchover) A table is created in the database, in which the following data is entered for each day of the week and for each COS switchover group:
● A time at which COS1 is switched to active (COS1T),
● A time at which COS2 is switched to active (COS2T),
● A program switch indicating whether the displayed switchover to COS1 is to be carried out on that day (COS1),
● A program switch indicating whether the displayed switchover to COS2 is to be carried out on that day (COS2).
AMO BERUZ administrates this table. (The switchover is carried out with the task BEZUM.)
Siemens Enterprise Communications GmbH & Co. KG is a trademark licensee of Siemens AG
AMOs Siemens
15 ZIEL - Destination Addresses for Stations
This AMO is used to enter, interrogate or regenerate destinations in the database (DB) for the following features:
● Call forwarding - fixed (FWD)
● Messenger Call (MSGR)
● Direct station select keys (DSS)
● Name/repertory key (NAME)
● Individual speed dialling (SPDI)
● Saved Number Redial (SNR)
● Attendant Console Direct Destination Select keys (DDS)
● Destinations for the BUZZ Feature
AMO-ZIEL is also used to add, delete, interrogate or regenerate for:
● dialing external servers to deposit messages
● identifying external servers when retrieving messages with the START key
Call forwarding - fixed
Two forwarding variants are possible:
● STATION forwarding can be added or deleted by AMO ZIEL or by the subscriber, and activated or deactivated by the subscriber or by AMO ACTDA.
● SYSTEM forwarding is a new forwarding typeAdding and deleting destinations is only possible by AMO ZIEL, whereby different destina-tions can be entered for different forwarding types (eg.busy, no response), immaterial, if the incoming call is internal or external. The forwarding can be activated or deactivated by AMO ACTDA, or by the subscriber using the relevant codes.
● Call forwarding on no responseThe fixed call forwarding destinations do not act ad destinations for call forwarding on no response any more. These can be added as fixed destinations for forwarding type CFNR (no response) or CFB (busy) in the SYSTEM forwarding (AMO ZIEL), and activated by AMOACTDA, or can be added and activated as variable forwarding (CFNR or CFB) (AMO ACTDA).
Fixed destinations can be created for each service. This AMO however does not activate or de-activate forwarding. Destinations can be entered in the services VCE (voice), FAX and DTE. Destinations for devices working to the DSS1 protocol can only be activated as variable for-warding destinations by AMO ACTDA.Destinations can be entered for all created STNOs (station numbers) with the exception of at-tendant terminals, irrespective of whether or not the station concerned has any terminal devic-es.
The following diversion types can be used:
for SYSTEM forwarding
● CFU (Call Forward Unconditional)
● CFB (Call Forward Busy)
● CFNR (Call Forward No Reply)
● CFDND (Call Forward Do Not Disturb)
for STATION forwarding
● CFU (Call Forward Unconditional)
Messenger Call
The members of an integrated executive/secretary system can have a messenger call key on their voice terminal for which a fixed destination can be entered. This destination can also be pro-grammed at the administration and maintenance terminal. Only analog stations are permitted.
Direct station select keys
Direct station select (DSS) keys can be assigned to all terminals. The key functions for OPTISET and Optipoint 500 are defined with the help of the AMO TAPRO. Only internal destinations are possible (analog telephone, digital voice terminal, and personal attendant call number). In addition to entering the destination in the database, the AMO ZIEL also enters partner infor-mation for the destination station (controls the lamps in the DSS key).
Name/repertory key
The key functions for the OPTISET and Optipoint 500 are defined with the help of the AMO TAPRO. Destinations can only be entered after the key functions have been defined. The des-tination entry may be any combination of digits comprising a maximum of 22 characters. Destination entries may be protected against changing and deleting by the destination terminal user, using parameter PROTECT=YES. Changing or deleting by AMO will be possible further-more.Name/repertory keys of OPTISET / Optipoint 500 add on terminals have two levels to store des-tination entries. A level can be selected by entering a value for parameter LEVEL.
Siemens Enterprise Communications GmbH & Co. KG is a trademark licensee of Siemens AG
AMOs Siemens
Individual speed dialling
Stations that are permitted to use the SPDI are provided an SPDI list when created by means of AMO SBCSU. Stations with an analog telephone, a voice terminal, mobile users (without a device, but with a separate terminal connection), and DTE stations may use the SPDI. Voice terminals can also used name/repertory keys and DSS keys.
Saved Number Redial
Each analog telephone and voice terminal can store a dialed number with up to 22 digits for redial. The destination can be any combination of digits (0-9,*,#,A,B,C,D).
Attendant Console Direct Destination Select keys
Each attendant console has 42 destination (DDS) keys
● 40 destinations via the destination keys
● 2 destinations via R1, R2 keys (trunk group keys for reserving lines).
The destinations are entered into a storage area that can hold up to 42 The configuration is carried out when the attendant console is created by means of AMO AC-SU. The destination keys write memory locations 1-40, while the trunk group keys R1 and R2 are always defined at locations 41 and 42.
Destinations for the BUZZ Feature
The buzz feature allows a user to alert (buzz) a predefined keyset or DFT (optiset and optiPoint 500) by pressing the BUZZ key or by keying an access code. Voice communication is not pos-sible. Buzz causes the target keyset or DFT to be alerted and the originator’s station number to be displayed for two seconds. The buzz target (destination) and the originator must be locat-ed in the same node.
Siemens Enterprise Communications GmbH & Co. KG is a trademark licensee of Siemens AG
AMOs Siemens
16 ACTDA - Activation of User Features
The AMO ACTDA is used to regenerate feature-specific data entered by a user via the terminal. The functions DISPLAY, REGENERATE, ADD and DELETE are implemented. The AMO en-ables these data to be saved while the software version (APS) is being changed.
Using the DISPLAY function, the user data recorded by ACTDA can be displayed on the admin-istration and maintenance terminal.
A command batch is generated with the REGENERATE function, based on the user data. This command batch is used for reinitializing the database.
The ADD function initializes the database with the user data.
The AMO ACTDA is used mainly for regenerating data. In addition, it can be used for test pur-poses.
In special cases it can be necessary to deactivate the activated call forwarding of a station. This function has been implemented in the branch DELETE.
TYPE Feature
STN DND Do-not-disturb
FWD Fixed call forwarding
Variable call forwarding
OPTISET individual optiset E / optipoint 500 settings
OUTHUNT switch out of hunt group
RCUTOFF Ringer Cutoff
REMIND Timed reminder
REPSECR Deputy for secretary
RNGXFER Ring transfer
VCR Voice call rejection
ATNDGR NOPT Night variant for ATNDGR
ITR DNDGR Group do-not-disturb function
ISTR Controlled station-to-station restriction
Controlled station-to-station restriction for all ISTR groups
Siemens Enterprise Communications GmbH & Co. KG is a trademark licensee of Siemens AG
AMOs Siemens
17 PERSI - Personal Identification
The AMO PERSI is used to administer personal data. The cross-reference to the person is in-variably established via the station number.
a) NamesEach station number can be assigned either one or several (any number of) names; the name entered first will be displayed on DIGITE displays. All other names are used for ETD functions. The name can also be made up of 2 parts:
1. Surname, simple or composite, e.g. Hr. Meier, Fr. Dr. Huber
2. Name, and additional information, e.g. Anna, Dept. A3The characters of the "surname" are separated from those of the "name" by means of a "*".
Digite display: The DIGITE has a 24-character display. The type of display, e.g. station number plus name or name only is defined by means of AMO ZAND, TYPE=ALLDATA, DISPMODE-MODE1 to MODE5 (see examples). There is no verification of the last name. The number of blanks between the station number and the name is exactly one.
Examples
Input: Dr. v. Ritter*MartinDisplayMODE1: 32857 DR. V. RITTER M.MODE2: 32857MODE3: DR. V. RITTER MARTINMODE4: DR. V. RITTERMODE5: # DR. V. RITTER
b) Organizational unitEach name can be assigned an organizational unit (for ETD functions).If a station number has not been assigned a name, no org. unit can be assigned.If station number has been assigned several names, but not everyone of these names has been assigned an organizational unit, the organizational unit which was assigned last is automatically assigned to the remaining names.
c) Personal identification number (PIN)The PIN is used for personal identification of a person to the system. Each station number can be assigned any number of PINs. The length of a particular PIN type is determined centrally. The PIN length may or may not be the same for the types of PINs described above. Each PIN (except COSXCD) must be unique throughout the system.
The "class of PIN" (COPIN) is used for each PIN type in order to implement the PIN display feature and in order to distinguish between the different PIN types.The characteristics of the COPINs (1 through 15) are summarized in the so-called COPIN table in which the following default values are assigned to the type of PIN:
Function:
ADD-PERSI:
CHANGE-PERSI:
DELETE-PERSI:
DISPLAY-PERSI:
REGENERATE-PERSI
PINTYPE(COPIN)
PIN COTYPE PIN Meaning of a type of PIN
1 = PIN1 MOBILE Manual identification2 = PIN2 BUSLONG Identification of business calls (remains active until
manual deletion or timeout).3 = PIN3 BUSSHRT Identification of business calls4 = PIN4 PRIVSHRT Identification of private calls5 = PIN5 PCODE Identification of a project for a call (project code =
PCODE).6 = PINC PINCARD Identification by means of a magnetic/chip card which is
inserted into the card reader of the terminal.7 = COSXCD COSXCD Identification of users which are authorized to activate
COS changeover from the terminal.8 = SI SI Pin for service id9 = CDRAC PCODE CDR account code10 = PIN10 PCODE PIN for dialing pattern check11 = PIN11 MOBILE Manual identification12 = PIN12 MOBILE Manual identification13 = PIN13 MOBILE Manual identification14 = PIN14 MOBILE Manual identification15 = PIN15 MOBILE Manual identification
Siemens Enterprise Communications GmbH & Co. KG is a trademark licensee of Siemens AG
AMOs Siemens
18 LRNGZ - List of Central Speed Dialing Numbers
The central speed dialing facility (SPDC) is used to simplify dialing. Long call numbers (desti-nation numbers) - usually external numbers - can be transmitted by means of a speed dialing number.
The allocation of speed dialing numbers to destination numbers is stored in the central speed dialing lists.
Up to 16 of these lists (0 to 15) can be set up, each with a maximum of 1000 speed dialing num-bers.
Each user can access up to 2 of these lists, which are allocated to him with parameters SPDC1 (List 1) and SPDC2 (LIST 2) of a subscriber AMO (e.g. AMO SCSU or SBCSU).
The AMO LRNGZ is used to set up the lists and to allocate speed dialing numbers to each of them. The allocation of destination numbers is carried out using AMO ZRNGZ.
The SPDC feature is accessed by dialing a code following the speed dialing number.
There are two versions of access.
a) Access of both lists via only one dialing code (digit analysis result SPDC1 in AMO WABE).
In this case the speed dialing numbers of the lists, allocated to the user (parameter SPDC1 and SPDC2 of the subscriber AMO) must be different, since it is the speed di-aling number which determines whether the 1st or 2nd list is dialed. The administrator of the switch has to take care of the so called „unambiguousness“ of the speed dialing number ranges. Because of the various combinations of speed dialing lists, allocated to the users (any two lists out of the available lists 0 to 15 can be allocated to any user), AMO LRNGZ is not able to check the unambiguousness.
In the case of 3 digit speed dialing numbers a user can access a maximum speed di-aling number range of 000 to 999, divided over the two allocated lists. Therefore with this version of access a user has access to maximum 1000 speed dialing numbers.
b) Access of both lists via 2 dialing codes (digit analysis results SPDC1 and SPDC2 in AMO WABE). Via dialing code of digit analysis result SPDC1, the user has access to the 1st list, allocated to the user (parameter SPDC1 of the subscriber AMO) and via dialing code of SPDC2 to the 2nd list (parameter SPDC2 of the subscriber AMO)
In this case the speed dialing numbers of the lists, allocated to the user can be the same, i.e. the speed dialing number ranges can overlap, since the Lists are accessed via the dialing code (digit analysis results SPDC1 and SPDC2 in AMO WABE) and not via the speed dialing number.
In the case of 3 digit speed dialing numbers a user can access a maximum speed di-aling number range of 000 to 999 per list. Therefore with this version of access a user has access to maximum 2000 speed dialing numbers.
The AMO DIMSU is used to establish how many lists (parameter SPDCL) and destinations (pa-rameter SPDCD) can be set up in the system.
Siemens Enterprise Communications GmbH & Co. KG is a trademark licensee of Siemens AG
AMOs Siemens
19 ZRNGZ - Central Speed Calling Digit Series
The central automatic dialer is a memory area of abbreviated numbers which is distributed among several lists. All system subscribers can access a maximum of two lists each.The speed dialing lists are created by AMO LRNGZ.
An abbreviated number is used to simplify dialing. Each abbreviated number can be assigned an unabbreviated number. The number of suffix dialing digits describes the number of digits in the unabbreviated number which are to be transmitted with a time lag during automatic suffix dialing.
Siemens Enterprise Communications GmbH & Co. KG is a trademark licensee of Siemens AG
Abbreviation Siemens
Abbreviation
This table shows some important abbreviations.
Abbreviation Definition
AADP Administration Daten Processor AMC Administration and maintenance controlAMO Administration and maintenance OrganizationAPI Application Interface
CCC Common Control;CMI Cordless Multicell Integration COS Class of Service;
DDBAR Data Base Access Routine / Datenbasis ZugriffsroutineDEE Data Terminal Equipment / DatenendeinrichtungDSCXL Data and Switch Processor for CompactPCI/LANDSS Digital Subscriber Signalling 1
EEDSS1 European Digital Signalling System No1 (Europ. D-Kanal Protokol)
IISDN Integrated System Design Network/
Diensteintegrierendes digitales Nachrichtennetz
LLDU Logical Device Unit
MMMI Man Machine Interface (Mensch Maschine Schnittstelle)
OOS Operating System / Betriebssystem
QQSIG ECMA-Standard für die Signalisierung am Q-Referenzpunkt;