cap 07 EN4416EN20EN - Papagayo System · CODEW variants with dongle in HiPath 4000 V2.0 The HiPath 4000 V1.0 op erating mode is ... (Except "HIPATH AP VOICE COMPRESSION IP" where

General Features Siemens

General Features

1 Protection of Software Features (Codeword) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.1 Feature description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.2 Codeword variants. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.3 Codew Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.4 Service information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.5 Generation (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.6 Relevant AMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Alternate Routing on Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.1 Feature description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.1.1 Usage of the feature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.1.2 Main goals for the alternate routing destination numbers in respect to OOS sce-

nario. 182.1.3 Usage of Alternate Routing Destination Numbers . . . . . . . . . . . . . . . . . . . . . 192.1.4 Subscriber number supplementation (parameter EXTNO) . . . . . . . . . . . . . . 21

2.2 User interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262.2.1 Examples for usage the alternate routing on error in different OOS scenarios .

262.2.1.1 Called subscribers (A,B,C,D,E of one source group), are not reachable, be-

cause of device/board errors. 262.2.1.2 Called subscriber is not reachable, because deactivated via AMO with addition-

al request for alternate routing 292.2.1.3 Called HFA IP phones (A,B) are not reachable, because of IP errors, they

moved their logon location from HiPath 4000 to HiPath 3000. 322.2.1.4 Called subscribers (A,B) in its APs are in an APE situation to AP of the calling

device. 382.3 Service information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

EN4416EN20EN© 2004 Siemens AG

1

2

General FeaturesSiemens

2.3.1 Additional control mechanisms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432.3.2 General plausibility information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432.3.3 Special restriction information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432.3.4 Implausible conditions for supplementation: . . . . . . . . . . . . . . . . . . . . . . . . . 442.3.5 Plausibility of alternate routing destination numbers. . . . . . . . . . . . . . . . . . . 462.3.6 Output of Advisory messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472.3.7 HiPath 4000 Assistant. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502.3.8 Realization via AMO: AMO or AMO Batch> . . . . . . . . . . . . . . . . . . . . . . . . . 50

2.4 Relevant AMOs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513 Smart Card Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533.1 Feature Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543.3 Service Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543.4 AMO Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553.5 Relevant AMOs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564 HG3550V2.0 WAML-Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574.2 SCN-LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

4.2.1 Configuring the HiPath 4000 V2.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604.2.1.1 Adding the STMI2-IGW board and configuring the Board Data: . . . . . . . . . . 604.2.1.2 Configuring the HG3550 V2.0 LAN Circuit: . . . . . . . . . . . . . . . . . . . . . . . . . . 604.2.2 Configuring UBA in HiPath 4000 Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . 634.2.3 Configuring the Gateway HG3550 V2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654.2.3.1 Installing XML30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654.2.3.2 Establish connection to the HG3550 V2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . 654.2.3.3 Checking the LAN1 interface settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674.2.3.4 Configuring the LAN 2 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684.2.3.5 Setting the WAML call number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694.2.3.6 Configuring PSTN Peer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704.2.3.7 Setting the Calling number of the peer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724.2.3.8 Save board data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734.2.4 Configuration of the PC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744.2.5 Checking the VPN address and PPP1 settings . . . . . . . . . . . . . . . . . . . . . . 804.2.6 Adding S0 Subscriber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814.2.7 Starting the Dial-up Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 824.2.8 Adding a “Route add” on the PC (DOS-cmd) . . . . . . . . . . . . . . . . . . . . . . . . 824.2.9 Getting access to the HiPath 4000 Assistant . . . . . . . . . . . . . . . . . . . . . . . . 83

5 AMOs Rights in the HiPath 4000 V2.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855.1 ADP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855.2 CC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 905.3 dropped AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 966 Extended features and AMO changes in the

HiPath 4000 V2.0 976.1 AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97


General Features Siemens

6.2 CLIP for analoge Subscribers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1046.3 Integrated features without any AMO control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106


3

4

General FeaturesSiemens


Protection of Software Features Siemens

1 Protection of Software Features (Codeword)

1.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


5

6

Protection of Software FeaturesSiemens

1.2 Codeword variants

In HiPath 4000 V2.0 and later, the CODEWRD 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;

ComScendo CC-AP for AP Emergency

PNE

Voice com-pression IP Entry Agent

Protection of software features

Remote Survivability Cordless E

CODEWORD



Components without licence and not marked as LICMARKIn 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.

CODEW variants with dongle in HiPath 4000 V2.0

The HiPath 4000 V1.0 operating mode is maintained if the old hardware is used with a dongle. However, you must download a new codeword if you migrate to HiPath 4000 V2.0.

● 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 overwites the Codeword on a daily basis. If this does not hap-pen then a 60 day test mode begins.

● The 60 Day Service-Dongle will no longer be given in Hipath4000 V2.0.

● The Type 2 codeword will only be given in special cases.(applied for as an extra).

● The creation date is coded in the Codeword and is stored in the database, when the Code-word is added in the system. The try 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 60 days( then a new Codeword is required)

X X

TYPE 2 (Special) Via LMT (Licence Mangement Tool)with a time limit longer than 60 Days

X X

Via LMT(Licence Management Tool)without a time limit

X X


7

8


1.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

ACSU ACTYPE=AC4/ACW2Q/ACW-MQ

BCSU TYPE=SIGNOFF

RCSU RECAPL=ACDR/ACDMUS/HMUSIC

SBCSU DVCFIG=ANAFAX/ANADTE/ANADEV/FAX/DTE/OPTIP500/OP-TISET/S0PP/S2PP/SET600/OPTIIP

SCSU DVCFIG=ANATE/ANATECM/AUXDIGI

SSC TYPE=GENANS/MSGR/EX-TANN/CC/VMXMWI

SXSU ART=OPTIERW

– Trunk or tie(including ATM Networking)

TACSU DEVTYPE=TC/TC1/TC2/NW/TT/TT1/TT2/TT3/TT4

TDCSU DEV=S0COD/S0CONN/S1COD/S1CONN/S1PVC/S1SVC/LAN/S1PVCCO/S2COD/S2CONN/S2PVC/S2SVC/S2PVCCO/VCCOD/VCCONN/HG3550/CDG-CONN/CDGCOD/30/ATMS-VC/ATMPVC3/ATMPVC7/ATMPVC15/ATMPVC23/ATMPVC2X/ATMPVC30/ATMPVCCO

TSCSU DEV=CC/CCM/ANS/RA/RAS/DICT/SPKR/DOOR

CORDLESS E Counting/marketing of the acti-vation license per B channel (for example SLC16 to base station) irrespective of the operating software

SBCSU DVCFIG=BASE



1.4 Service information

● The counters bear no relationship to the feature dimensioning values administered with the AMO DIMSU.

● For the purposes of software feature protection, "ComScendo" is the equivalent of "station" for the following components:

– Optiset E

– optiPoint 500 / optiPoint 400 / optiPoint 410

– ANATE

– ANATECM

– AUXDIGI

– Signed off TSI instead of signed off station

– PP (all S0/S2)

– FBUS (all call numbers)

● The dongle or the SIM card is immediately activated on startup.

● The validity of a codeword may be limited to a specific period. It is calculated in days from the creation date.

PNE Counting/marketing per VPN B channel configured from/to the board with PNEDIUS2 line type (use the AMO BGDAT to check the line type of a board)

TDCSU DEV=S2CONN

HIPATH PRO-CENTER ENTRY AGENT

Counting/marketing per active (logged in) agent

AGENT AGTID=<number>

HIPATH AP REMOTE SURVIVABILITY

Counting the IPDA survivability remote shelves for connections over ISDN (ID9206)(AMO SIPCO parameter SURV-NET)

APRT CONF=ROUTER/AP

CC-AP FORAP EMERGEN-CY

Counting/marketing per CC con-figured for AP Emergency

APESU DATA=CCAP

Unit Description AMOs Parameter


9

10


● 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.

1.5 Generation (example)

● Add a codeword (dongle or SIM card must be inserted):

ADD-CODEW:CODEW1=W1RAZWX6HPK8HS5G39TKV6X9MKVAM9ENERJTVTZBDX34KFNHRUTP4GU1EC132N93,CODEW2=LJJ9MKK381DASTYEZNNU67366HMWAM33VVKKRKG7UHTDUGFWJN2PBBREGX;



● Display counters for purchased quantities / configured quantities:

1. Customer Dongle / SIM (TYPE 1 - Codeword)

DISPLAY-CODEW;

H500: AMO CODEW STARDED

SALES UNIT COUNTERS

===================

CODEWORD: AFTKSB3CJYN4LKZN7GNWZH8TXH63M29A5GA2L2JN261LGKEA8CPHLZV5UGKHVPHP

XGRZDWDF83BG6BLE2U6LSP8GYS8VY5NADW88BUAE6RA58HXMD2N99TJSC9

VERSION : H205

SERIAL NUMBER: 7

HARDWARE ID : C6EB8F3B

ENTRY DATE : 22.02.2004

TRIAL MODE : NOT ACTIVATED

CONFIRMATION : 3706

+---------------------------------------------+-------+-------+-------+-------+

| | | | | |

| UNIT | CON- | USED | FREE |BLOCKED|

| | TRACT | | | |

+---------------------------------------------+-------+-------+-------+-------+

| COMSCENDO | 976 | 913 | 63 | |

| CORDLESS E | 0 | 0 | 0 | |

| PNE | 0 | 0 | 0 | |

| HIPATH PROCENTER ENTRY AGENT | 0 | 0 | 0 | |

| SIGNALING SURVIVABILITY | 0 | 0 | 0 | |

| CC-AP FOR AP EMERGENCY | 0 | 0 | 0 | |

+---------------------------------------------+-------+-------+-------+-------+

H07: THE TEST MODE IS AVAILABLE (ANOTHER) 2 TIMES.

AMO-CODEW-111 CODEWORD FOR ADMINISTRATION LOCK IN SWU

DISPLAY COMPLETED;


11

12


2. Dongle / SIM with TYPE 2 - Codeword

DISPLAY-CODEW;

DISPLAY-CODEW;

H500: AMO CODEW STARTED

SALES UNIT COUNTERS

===================

CODEWORD: 3SK2N24LR9RF4G9919DZL3GN8C8SVWTN7RX7BWNBCTLTZPGMZN9FBXP97RRFTT72

R283HCUX6LSJXW5YD147WGWTV9FXD2CZBSWN7RY63VL9R7ASMWJ546YM7R

VERSION : H205

SERIAL NUMBER: 0

HARDWARE ID : 7ED439FB

ENTRY DATE : 07.01.2004

VALID UNTIL : 17.12.2005


CONFIRMATION : 0

+---------------------------------------------+-------+-------+-------+-------+

| | | | | |


| | TRACT | | | |

+---------------------------------------------+-------+-------+-------+-------+

| COMSCENDO | | 110 | | |

| CORDLESS E | | 0 | | |

| PNE | | 0 | | |

| HIPATH PROCENTER ENTRY AGENT | | 0 | | |

| SIGNALING SURVIVABILITY | | 0 | | |

| CC-AP FOR AP EMERGENCY | | 0 | | |

+---------------------------------------------+-------+-------+-------+-------+

H12: CURRENT CODEWORD IS A TYPE 2 CODEWORD.


DISPLAY COMPLETED;



Trial mode

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:

ADD-SCSU:STNO=4711,DVCFIG=ANATE;

● Display counters for configured quantities/purchased quantities:

DISPLAY-CODEW;

DISP-CODEW;

H500: AMO CODEW STARTED

SALES UNIT COUNTERS

===================

CODEWORD: 3SK2N24LR9RF4G9919DZL3GN8C8SVWTN7RX7BWNBCTLTZPGMZN9FBXP97RRFTT72

R283HCUX6LSJXW5YD147WGWTV9FXD2CZBSWN7RY63VL9R7ASMWJ546YM7R

VERSION : H205

SERIAL NUMBER: 0


13

14


HARDWARE ID : 7ED439FB

ENTRY DATE : 18.12.2005

VALID UNTIL : 17.12.2005


CONFIRMATION : 0

+---------------------------------------------+-------+-------+-------+-------+

| | | | | |


| | TRACT | | | |

+---------------------------------------------+-------+-------+-------+-------+

| COMSCENDO | 110 | 110 | !!!!! | 1 |

| CORDLESS E | | 0 | | |

| PNE | | 0 | | |

| HIPATH PROCENTER ENTRY AGENT | | 0 | | |

| SIGNALING SURVIVABILITY | | 0 | | |

| CC-AP FOR AP EMERGENCY | | 0 | | |

+---------------------------------------------+-------+-------+-------+-------+

H12: CURRENT CODEWORD IS A TYPE 2 CODEWORD.


DISPLAY COMPLETED;

DISPLAY-SDSU:STATUS=LICMARK,TYPE=PEN,LEVEL=PER3;

....(a component is marked if it was installed with the purchased quantities configured and the system is being operated in trial mode.)

DISPLAY-SDSU:STATUS=LICBLOCK,TYPE=PEN,LEVEL=PER3;

....(specifies the stations disabled on account of license violation when the trial mode expired.)



1.6 Relevant AMO

AMO Parameter Sprache/Language

Beschreibung/ Description

EINR-CODEW CODEW1 d Erster Teil des Codewortes

CODEW2 d Zweiter Teil des Codewortes

ADD-CODEW CODEW1 e First part of codeword

CODEW2 e Second part of codeword

AE-CODEW TESTMOD d Testmodus ein/ausschalten

CHANGE-CODEW TRIAL e Activate/deactivate trial mode

AB-SDSU LICMARK d Markierte Lizenz (im Testmodus)

LICBLOCK d Gesperrte Lizenez (Testmodus abgelau-fen)

DISP-SDSU LICMARK e Marked License (in testmode)

LICBLOCK e Blocked License (testmode expired)


15

16



Alternate Routing on Error Siemens

2 Alternate Routing on Error

2.1 Feature description

2.1.1 Usage of the feature

This feature provides an additional possibility to reach an alternate destination, if the called subscriber/ personal attendant/ subscribers of a source group is/are in an out_of_service (OOS) state.

The feature performs a new kind of alternate routing mechanism, using new predefined al-ternate routing destination numbers, which can be subscriber-individual or source group related. In some cases (see below), new authorizations will be validated.

In total, four different OOS scenarios of the called subscriber/ personal attendant/ sub-scribers of a source group will be handled.

1. The called subscriber/ personal attendant/ subscribers of a source group is/are OOS, because of a device/ board error.

(no additional authorization (SDAT) necessary)

2. The called subscriber/ personal attendant is OOS because switched off by AMO.

(authorization (SDAT) necessary for doing alternate routing when manual switched off

by AMO)

3. The called HFA IP phone is in an OOS state and has logged on to a Hipath 3000 be-cause of IP errors.

(authorization necessary to move logon from HiPath 4000 to HiPath 3000)

4. The access point (AP) of the called subscriber is in an Access Point Emergency (APE)

situation in relation to the AP of the calling device.

(no additional authorization necessary)

Normally, alternate routing will be done only once for a call. In case of an alternate routing because of APE, it might be necessary to execute another alternate routing again for one of the other 3 mentioned OOS scenarios.

EN4416DE20EN© 2004 Siemens AG

17

18

Alternate Routing on ErrorSiemens

The reason why is, that in kind of APE, in the AP of the calling device, it can not be verified for sure, whether the called subscriber in the target AP is in a seizable condition.

Because of this consideration, it is possible to administer two types of alternate routing destination numbers (OOS and APE) for a subscriber or a whole source group with differ-ent alternate destinations.

2.1.2 Main goals for the alternate routing destination numbers in respect to OOS scenario.

● Device/ board error

The goal is, to reach the called subscriber either with its mobile phone number, with an alternate number, via PSM or to lead the call to attendant, voice mail, phonemail or something else.

● Manual deactivated (by AMO) with activated authorization for alternate routing

If subscribers are deactivated manualy by AMO command, alternate routing will only be performed, if the subscribers are authorized for requesting alternate routing when called after a manual deactivation.

The goal is identical as for device/ board errors.

● Logged off HFA IP phones.

Authorized HFA IP phones can move their logon location from HiPath 4000 to HiPath 3000 in case of IP errors.

The goal is, to reach these HFA IP phones in their new logon location via public trunk access under their individual (modified) extension numbers.

● APE situation between APs of calling device and called subscriber/ personal at-tendant.

In case of an APE situation between APs of calling device and called subscriber/personal_attendant, the involved APs act as single switches.



The goal is, to reach the called subscriber in its AP via public trunk access. As a pre-condition, a public trunk access has to be administered between the related APs with routing elements without internal rerouting possibilities.

2.1.3 Usage of Alternate Routing Destination Numbers

You can administer an alternate routing destination number Either a subscriber individual alternate routing destination number for one subscriber ,or a source group related alternate routing destination number for a whole source group of related subscribers can be config-ured.

In certain OOS scenarios, it might be a requirement to confine to source group related al-ternate routing destination numbers,in order not tro waste memory.

It is possible to administer a source group related alternate routing destination number ei-ther as a complete number (EXTNO = 0) or as a incomplete number (EXTNO > 0), you also have the possibility to reach subscriber individual destinations with the supplementation. request (EXTNO > 0).

A supplementation will be done at time of alternate routing execution by call processing with the administered length (EXTNO) of the called subscribers extension number.

If you administer both kinds, and the numbers are different, the subscriber individual alter-nate routing destination numbers will be used with higher priority than the source group re-lated alternate routing destination numbers. With this design, you can treat special sub-scribers (vips) different than the rest of subscribers of a source group.

In case of usage, the alternate routing destination number will be checked for being usable to reach an alternate destination successfully. If it is not possible, to reach an alternate des-tination with the subscriber individual alternate number, another attempt will be done with the source group related alternate routing destination number.

7 Attention:

Routing elements, that are defined as with "internal rerouting", will not be used for alternate routing on error in general.


19

20


Depending of the OOS scenario (1 --> 4) the alternate routing destination numbers will be checked for usage in the following hierarchical manner:

● OOS because device/board error

- subscriber individual alternate routing destination number for OOS

- source group related alternate routing destination number for OOS

● OOS because manual deactivated with activated authorization for alternate routing



● OOS of logged off HFA IP phones with activated authorization for move logon



● OOS because of APE situation between APs of called subscriber and calling device

- subscriber individual alternate routing destination number for APE

- source group related alternate routing destination number for APE

If the called subscriber is not a HFA IP phone with the activated authorization for move logon, 2 additional attempts will be done



Device / board error Manual deactivated Moved logon AP Emergency

subscriber individual (OOS)



subscriber individual (APE)

Source Group related (OOS)



Source Group related (APE)





2.1.4 Subscriber number supplementation (parameter EXTNO)

Subscriber number suplementation is administered by AMO APRT,branch ALTERR

If you administer the source group related alternate routing destination number as a com-plete number, you have to set the parameter EXTNO = 0;

If you administer the source group related alternate routing destination number as a incom-plete number, you have to set the parameter EXTNO to the number of the called subscrib-ers digits, that are requested for supplementation.

The plausibility of a digit supplementation (design and usage) depends on the WABE result of the alternate routing destination number (source group related ), as well as the alternate routing type.

The plausibility checks of the AMO APRT allow the input of EXTNO > 0 only for those al-ternate routing destination numbers, that do not lead to WABE result = station. But there are many other possibilities that are not restricted by the AMO, but cannot be executed at the time of usage for special alternate routing scenarios.

● Usage of supplementation for APE

If you want to reach the subscribers, that are in APE situations, via public trunk loop in their own APs under their individual subscriber numbers, you must administer a source group related incomplete alternate routing destination number for type = APE, that contains a trunk access code for going public network and a incoming trunk access code to reach the APs, where the subscribers are located in.

The missing subscribers extension numbers will be supplemented at time of call exe-cution by call processing.

You have to administer, how many digits of the subscribers extension numbers should be used for supplementation with setting the parameter EXTNO > 0.

In this example, it is obvious, that EXTNO has to be set to the length of the subscribers extension numbers.

If you set the parameter EXTNO bigger than the length of the subscribers extension numbers, it is tolerated and will be decremented to the real length.

If you set the parameter EXTNO smaller than the length of the subscribers extension numbers, this alternate routing destination number can not be used for that case.


21

22


Example 1:

Exit Code = 0

Outgoing public trunk access = 0004989

Number (subscriber_A) = 54321

Administered source group related alternate routing number = 0004989-722

EXTNO = 5 --> supplementation done / result = 0004989-722-54321


EXTNO = 4 --> supplementation not possible

EXTNO = 0 --> supplementation not requested / the number 0004989722 do not

lead to a valid destination, but neither by AMO nor at time

of usage, this can be verified.

● Usage of supplementation for OOS (device/ board error or deactivated by AMO)

If you want to reach the subscribers, that are in OOS situation, with searching via PSM under their individual search numbers, you must administer a source group related al-ternate routing destination number for type = OOS, that contains the PSM access code.

The missing subscribers extension numbers will be supplemented at time of call exe-cution by call processing.


If the PSM is designed with search length = 0, the parameter EXTNO has to be set to the length of the called subscriber numbers.

If the PSM is designed with search length = x, the parameter EXTNO has to be set to that value (x). The normal situation is, that the search length is smaller than the length of called subscribers. In this case, the supplementation result leads to a cut search number. The cutting will be done from right hand side.

Example 2:

Paging access code = #77


Administered source group related alternate routing number = #77



Search length = 3

EXTNO = 3 --> supplementation done / result = #77-543



EXTNO = 0 --> supplementation not requested / invalid

Example 3:

Paging access code = #77


Administered source group related alternate routing number = #77

Search length = 0

Source group related alternate routing number = #77




EXTNO = 0 --> supplementation not requested / invalid

● Usage of supplementation for OOS in case of moved logon

If you want to reach the HFA IP phones, that have moved their logon location from Hi-Path 4000 to HiPath 3000 in their new logon switch under their individual extension number, you have to administer a source group related incomplete alternate routing destination number for type = OOS, that contains a trunk access code for outgoing public network and an incoming trunk access code, to reach the HiPath 3000.

The missing subscriber extension numbers will be supplemented at time of call execu-tion by Call processing.


It may be possible, that the HiPath 3000 works with a different number scheme than the HiPath 4000.

If the HFA IP phone extension numbers are identically in both switches, you have to set the parameter EXTNO to the identical extension number length of the HFA IP phones.


23

24


If the HFA IP phone extension numbers in the HiPath 3000 are smaller than in the Hi-Path 4000 (see example 4), you have to set the parameter EXTNO to the smaller HFA IP phone extension number length. in HiPath 3000. The later performed supplemen-tation then will cut the HFA IP phone extension numbers from left hand side on.

If the HFA IP phone extension numbers in the HiPath 3000 are bigger than in the Hi-Path 4000 (see example 5), you have to set the parameter EXTNO to the length of the HFA IP phone extension number in the HiPath 4000. As the extension numbers in Hi-Path 3000 starts with an additional digit (9), you must add this as a prefix to the source group related alternate routing number.

Example 4:

Outgoing public trunk access = 0004989,

Incoming trunk access for HiPath 3000 = 865

Number (HFA IP phone_A in HiPath 4000) = 54321


Administered source group related alternate routing number = 0004989-865



In HiPath 3000 -, the correct HFA IP phone can not be reached. No kind of syntax check can avoid this malfunction.

EXTNO = 3 --> supplementation done / result = 000498986-5321

In HiPath 3000 -, the correct subscriber can not be reached. No kind of syntax check can avoid this malfunction.

EXTNO = 0 --> supplementation is not requested / invalid

Example 5:

Outgoing public trunk access = 0004989,

Incoming trunk access for HiPath 3000 = 865


Number (HFA IP phone in HiPath 3000) = 9-54321

Administered source group related alternate routing number = 0004989-865-9



EXTNO = 4 --> supplementation possible / result = 0004989-865-9-4321

In HiPath 3000, the correct subscriber can not be reached No kind of syntax check can avoid this malfunction.

EXTNO = 5 --> supplementation done / result = 0004989-865-9-54321

EXTNO = 6 --> supplementation done / result = 0004989-865-9-54321

EXTNO = 0 --> supplementation is not requested / invalid


25

26


2.2 User interface

2.2.1 Examples for usage the alternate routing on error in different OOS scenarios

Make sure, that the maximum number of individual alternate routing destination numbers is big enough, otherwise increase the maximum number value by AMO DIMSU.

ADD-DIMSU:TYPE=USER,ALTROUT=<new_value>;

2.2.1.1 Called subscribers (A,B,C,D,E of one source group), are not reachable, because of device/board errors.

● What are the main goals?

Calling a subscriber specific individual alternate routing destination number (mobile phone number)

Calling a general destination like voicemail or attendant.

● What is possible?

The alternate routing number can be designed to reach any other destination.

If the alternate routing destination number leads to a outgoing trunk access, only those route elements will be used for alternate routing, that are defined as with " no internal re-routing ".



● AMO usage

– Calls to subscriber_A should be alternate routed to a mobile phone number 017nn...nn. Calls to subscriber_B should be alternate routed to a national public num-ber subscriber_F

STN-AOOS-NO =0017nnn..nnn

ALT-NO = #17with EXTNO

STN-BOOS-NO = 00303864444444

ISDN

017nnn..nnn

STN-FNO = 4444444

PagingNO = #17

Source -Grp = 3ALT-NO = 99

ATND = 99STN-C

STN-D

Source -Group = 2ATNDIND=7199

STN-GNO = 5555

ATNDINDOOS-NO = 5555

7100

7101


27

28


For routing type = OOS, you must define a subscriber individual alternating routing desti-nation number for subscriber_A:

CHANGE-SDAT:STNO=7100,TYPE=DATA1,STNOOOS=<0017nnn...nnn)

For routing type = OOS, you must define a subscriber individual alternate routing destina-tion number for subscriber_B:

CHANGE-SDAT:STNO=7101,TYPE=DATA1,STNOOOS=00303684444444

If the Redirecting number has to be send to the Carrier, the COT parameter R261 is to be set on the trunk:

CHANGE-COT:COTNO=xxx,COTTYPE=COTADD,PAR=R261;

– Calls to subscriber_C and subscriber_D of the related source group 3, should be al-ternate routed to the attendant.

For the related source group, you can define a source group related complete alternate routing destination number for routing type = OOS:

ADD-APRT:TYPE=ALTERR,SCRGRP=3,ALRTYPE=OOS,ALTRTNR=99;

– Calls to all subscribers of source group = 2 should be alternate routed to Paging sys-tem.

It will be assumed, that the Paging system works with LENGTH_SEARCH_NO = 0.

For routing type = OOS, you must define a source group related incomplete alternate rout-ing destination number for that source group 2, the called subscribers are members of.

As for every subscriber an individual search number is requested, the alternate routing destination number must be a incomplete number containing only the access code for PSM.

You must set the number of the supplemented digits (parameter EXTNO) equal the number length of subscribers extension number.

ADD-APRT:TYPE=ALTERR,SRCGRP=2,ALRTYPE=OOS,ALTRTNR=#17,EXTNO=4;

If the Paging system works with length search no = x (1-6), you must administer the param-eter EXTNO = <length_search_no>.



– Private calls for the attendant console 7199 should be alternate routed to to subscriber_G.

For routing type = OOS, you must define a subscriber individual alternate routing destina-tion number for ATNDIND=7199:

CHANGE-ACSU:ATNDNO=7199,STNOOOS=5555;

Caution: If you change the source group of a subscriber with AMO SDAT, the administered source group related alternate routing informations may not be valid anymore for this sub-scriber!

2.2.1.2 Called subscriber is not reachable, because deactivated via AMO with additional request for alternate routing


Calling a subscriber specific individual alternate routing destination number (mobile phone number)

Calling a general destination like analoge Phonemail, digital Voicemail/Xpression or atten-dant.


The alternate routing number can be designed to reach any other destination.

If the public network (Carrier) is checking the calling number, the new COT pa-rameter R261 must be set on the CO trunk, to send the Redirecting number.

If an analoge Phonemail is used for OOS, the number is checked in AMO ZIEL. If the number is a VMX (Type in AMO ZIEL) destination, the Redirecting num-ber is send.

For using a digital Voicemail / Xpression the destination number of the Voice-mail/Xpression has to be set in AMO ZIEL -> VMX, too. If the COT parameter R261 is used on the Tie trunks instead of th VMX entry, there could be prob-lems in a network.


29

30



● AMO usage

– Calls to a deactivated subscriber-A and subscriber_B should be alternate routed to the analoge Phonemail respec. to the Xpression.

For routing type = OOS, you must define a subscriber individual alternate routing destina-tion number for the subscriber_A and subscriber_B:

CHANGE-SDAT: STNO=7100,TYPE=DATA1,STNOOOS=90147;

CHANGE-SDAT: STNO=7150,TYPE=DATA1,STNOOOS=90500;

STN-AOOS-NO=90147

analoge Phonemail

90417

Source -Grp = 3

ALT-NO = 99

ATND= 99

STN-D

STN-C

Deactivate-DSSU: STN-ADeactivate-DSSU: STN-BDeactivate-DSSU: STN-CDeactivate-BSSU:............Deactivate-USSU:.............

Xpression

90500

S2

STN-BOOS-NO=90500

7100

7150

7120

7121



You must set a request for alternate routing, before deactivating the subscriber-A and subscriber_B with AMO e.g. DSSU:

CHANGE-SDAT:STNO=7100,TYPE=DATA1,AMOALTRT=YES;CHANGE-SDAT:STNO=7150,TYPE=DATA1,AMOALTRT=YES;

To send the Redirecting number to the Xpression, the COT parameter R261 is to be set on the S2 trunk:

CHANGE-COT:COTNO=xxx,COTTYPE=COTADD,PAR=R261;

– Calls to subscriber_C and subscriber_D of the related source group 3, should be al-ternate routed to the attendant.

For the related source group, you can define a source group related complete alternate routing destination number for routing type = OOS:

ADD-APRT:TYPE=ALTERR,SCRGRP=3,ALRTYPE=OOS,ALTRTNR=99;

You must set a request for alternate routing, before deactivating the subscriber_C and subscriber_D with AMO e.g. DSSU:

CHANGE-SDAT:STNO=7120&&7121,TYPE=DATA1,AMOALTRT=YES;

If you set this request and no kind of alternate routing destination number was administered before, the AMO SDAT will print out a hint-message.

If the public network (Carrier) is checking the calling number, the new COT pa-rameter R261 must be set on the CO trunk, to send the Redirecting number.

If an analoge Phonemail is used for OOS, the number is checked in AMO ZIEL. If the number is a VMX (Type in AMO ZIEL) destination, the Redirecting num-ber is send.

For using a digital Voicemail / Xpression the destination number of the Voice-mail/Xpression has to be set in AMO ZIEL -> VMX, too. If the COT parameter R261 is used on the Tie trunks instead of th VMX entry, there could be prob-lems in a network.


31

32


2.2.1.3 Called HFA IP phones (A,B) are not reachable, because of IP errors, they moved their logon location from HiPath 4000 to HiPath 3000.

Scenario 1

SUB-AOOS-No = 00049895684711

TLN-BOOS-No = 00049895684712

MOVING

IPNetwork

STMI

MOVING

ISDN

54711

4711

54712

or

Source-Grp = 2ALT-No = 004989568with Extno= 4

HiPath 4000

HiPath 3000

4712

CO Number:+49-89-568

Moving by fault

HG1500

IP: 1.30.11.180

IP: 1.40.41.180



● Device configuration:

HiPath 4000 HiPath 3000

number (HFA IP phone A): 54711 4711

number (HFA IP phone B): 54712 4712

station number length: 5 4


The main goal is, to call the HiPath 4000 logged off HFA IP phone in its new logon switch (Hipath 3000) via public trunk under its new or identical subscriber number.


The alternate routing destination number can be designed as outgoing public trunk access or outgoing tie trunk access followed by incoming trunk access to reach the Hipath 3000.

The alternate routing destination number can be designed as a subscriber individual alter-nate routing number or as an incomplete source group related alternate routing number (with supplementation request).


Not allowed is a source group related complete alternate routing number, as it is not possible, to reach individual subscribers in this way.

Not allowed are alternate routing numbers, that do not lead to a trunk access.


33

34


● AMO usage

– Calls to not reachable HFA IP phones, that have moved their logon location from HiPath 4000 to HiPath 3000, should be routed to the new logon location via public net-work. In HiPath 3000, the HFA IP phones have a different number scheme than in HiPath 4000.

You must authorize those HFA IP phones, that can move their logon location from HPath 4000 to HiPath 300:

CHANGE-SDAT:STNO=54711,TYPE=DATA1,MVHFAIP=YES;


You must set the gateway_IP address(es) for the source group(s), the HFA IP phones are members of. This is necessary to avoid loops within the HiPath 4000 and HiPath 3000 net-work.

For example, it could be possible, that a HFA IP phone is already logged off in HiPath 4000 and not yet logged on in HiPath 3000. In this case, every switch tries to perform an alter-nate routing to the other switch (ping/pong).

ADD-APRT:TYPE= ALTERR,SRCGRP=2,ALRTYPE=OOS,GWIPADR=1.30.11.180;

For type= OOS, you must define either subscriber individual alternate routing destination numbers for every HFA IP phone (A,B) or a source group related incomplete alternate rout-ing destination number for the source group(s), the HFA IP phones are members of.

A incomplete alternate routing destination number will be supplemented at time of usage with the extension number of the called HFA IP phone and with the administered length (parameter EXTNO). This makes it possible to reach individual subscribers in other switch-es.

If you want to use only subscriber individual alternate routing destination numbers, you have to administer a subscriber individual alternate number for both HFA IP phones with outgoing trunk access to public network (004989), with incoming trunk access to reach the HiPath 3000 (568) and the shortened part of the extension numbers (4711, 4712).

CHANGE-SDAT:STNO=54711,TYPE=DATA1,STNOOOS=0004989-568-4711;

CHANGE-SDAT:STNO=54712,TYPE=DATA1,STNOOOS=0004989-568-4712;



If you want to use only source group related incomplete alternate routing destination num-bers, you have to administer the source group related alternate destination number with outgoing trunk access to public network (004989) and with incoming trunk access (568) to reach the Hipath 3000.

Furthermore, you must set the supplementary length (parameter EXTNO) to the length of the HFA IP phones number in the HiPath 3000, which is = 4.

ADD-APRT:TYPE=ALTERR,SRCGRP=2,ALRTYPE=OOS,ALTRTNR=0004989-568,EXTNO=4;


35

36


Scenario 1



number (HFA IP phone A): 54711 954711

number (HFA IP phone B): 54712 954712

station number length: 5 6

SUB-AOOS-No = 0004989568954711

TLN-BOOS-No = 0004989568954712

MOVING

IPNetwork

STMI

MOVING

ISDN

54711

954711

54712

or

Source-Grp = 2ALT-No = 0049895689with Extno= 5

HiPath 4000

HiPath 3000

954712

CO Number:+49-89-568

Moving by fault

HG1500

IP: 1.30.11.180

IP: 1.40.41.180



● AMO usage

– Calls to not reachable HFA IP phone, that have moved their logon location from HiPath 4000 to HiPath 3000, should be routed to the new logon location via public network. In HiPath 3000, the HFA IP phones have a different number scheme than in HiPath 4000.

You must authorize those HFA IP phones, that can move their logon location from Hipath 4000 to HiPath 300:



You must set the gateway_IP address(es) for the source group(s), the HFA IP phones are members of. This is necessary to avoid loops within HiPath 4000 and HiPath 3000 network. For example, it could be possible, that a HiPath 4000 logged off HFA IP phone is not yet logged on in HiPath 3000 and every switch tries to perform an alternate routing to the other switch (ping/pong).

ADD-APRT:TYP=ALTERR,SRCGRP=2,ALRTYPE=OOS,GWIPADR=1.30.11.180;

For type= OOS, you must define either subscriber individual alternate routing destination numbers for every HFA IP phone (A,B) or a source group related incomplete alternate rout-ing destination number for the source group(s), the HFA IP phones are members of.

A incomplete alternate routing destination number will be supplemented at time of usage with the extension number of the called HFA IP phone and with the administered length (parameter EXTNO). This makes it possible to reach individual subscribers in other switch-es.

If you want to use only subscriber individual alternate routing destination numbers, you have to administer a subscriber individual alternate number for both HFA IP phones with outgoing trunk access to public network (004989), with incoming trunk access to reach the HiPath 3000 (568), with a number prefix (9) and the extension numbers (54711,5 4712).

CHANGE-SDAT:STNO=54711,TYPE=DATA1,STNOOOS=<0004989-568-9-54711;

CHANGE-SDAT:STNO=54712,TYPE=DATA1,STNOOOS=<0004989-568-9-54712;

If you want to use only source group related incomplete numbers, you have to administer the source group related alternate destination number with outgoing trunk access to public network (004989) and with incoming trunk access (568) to reach the HiPath 3000.

Furthermore, you must set the supplementary length (parameter EXTNO) to the length of the HFA IP phones number in the HiPath 4000, which is 5:

ADD-APRT:TYP=ALTERR,SRCGRP=2,ALRTYPE=OOS,ALTRTNR=0004989-568-9,EXTNO=5;


37

38


2.2.1.4 Called subscribers (A,B) in its APs are in an APE situation to AP of the calling device.

Scenario 1:


number (subscriber-A) = 4711

number (subscriber-B) = 4712

subscriber A,B in same source group 17

STN-AOOS-NO = 00049-89-723-4711

IPNetwork

ISDN

4711

STN-BOOS-NO = 00049-89-723-4711

Source-Group = 17ALT-NO for APE = 0004989723with EXTNO = 4

HiPath 4000

4712

AP 3700-9

CO incoming:+49-89-723

APE situation

4711

or




The main goal is, to reach the subscribers, that are in APE situation to the calling device, via public trunk loop in their own APs.

Another goal may be, to reach the subscriber via an individual phone number or to route a call the Attendant.


All other alternate routing destination numbers, that lead to a valid internal or external phone number, are possible.

The alternate routing destination number can be designed as outgoing public trunk access or tie trunk access followed by an incoming trunk access to reach an AP.

The alternate routing destination number can be designed as a subscriber individual alter-nate routing number or as a source group related incomplete alternate routing number (with supplementation request).

If the alternate routing destination number is designed as a source group related incom-plete number, the supplementation can only be done with the identical subscribers exten-sion number (parameter EXTNO = length of subscribers extension number).


● AMO usage

– Calls subscribers A,B, that are in an APE situation to the calling device, should be rout-ed to the called subscribers in its AP via public trunk loop.

In case of APE, in the AP of the calling devices, it can not be verified, whether the called subscribers in their own AP are in a seizable situation or not. Therefore, it makes sense, to alternate route the call to the originally called subscribers in their own APs via public trunk loop. The incoming trunk at target AP, then can verify for sure the real state of the called subscribers.

For type = APE, you have to administer either subscriber individual alternate routing num-bers of type = APE for subscriber A and B or incomplete source group related alternate routing numbers of type = APE for the source group(s), the subscriber A,B are members of.

If you are sure, you don’t need different alternate routing destinations for TYPE = OOS and TYPE=APE, you also can administer the mentioned alternate routing destination numbers for TYPE = OOS.


39

40


An incomplete alternate routing destination number will be supplemented at time of usage with the extension number of the called subscriber A,B and with the administered length (parameter EXTNO). This makes it possible to reach individual subscribers in other switch-es.

If you use subscriber individual alternate routing destination numbers, you have to admin-ister a subscriber individual alternate number for the subscribers A and B with outgoing trunk access to public network (004989), with incoming trunk access to reach the HiPath 4000 (723) and with the individual subscriber numbers of subscriber_A and subscriber_B.

CHANGE-SDAT:STNO=4711,TYPE=DATA1,STNOOOS=<0004989-723-4711;

CHANGE-SDAT:STNO=4712,TYPE=DATA1,STNOOOS=<0004989-723-4712;

If you use only source group related incomplete alternate routing destination numbers, you have to administer the source group related alternate destination number with outgoing trunk access to public network (004989) and with incoming trunk access (723) to reach the AP of the called subscriber (A,B) in HiPath 4000.

Furthermore, you must set the supplementary length (parameter EXTNO) to the length of the subscriber number in the HiPath 4000, which is = 4. In this case, you must not use a different value for EXTNO than the length of the subscriber number of subscriber A or B.

ADD-APRT:TYPE=ALTERR,SRCGRP=17,ALRTYPE=APE,ALTRTNR=0004989-723,EXTNO=4;



Scenario 2:

● AMO usage

– Calls to not ready subscribers of source group 18 (STN-B), that are in an APE situation to the calling device, should be routed to the attendant console. Calls to not ready sub-scriber-A, of source group 18, that is in an APE situation to the calling device, should be routed to a subscriber individual mobile phone number.

For type = APE, you must define a source group related complete alternate routing desti-nation number for the source group = 18.

ADD-APRT:TYPE=ALTERR,SRCGRP=18,ALRTYPE=APE,ALTRTNR=99;

For type = APE and for subscriber-A, you must set the subscriber individual alternate rout-ing number to the individual mobile phone number.

CHANGE-SDAT:STNO=4711,TYPE=DATA1,STNOAPE=001711234567;

STN-AAPE-NO = 001711234567

IPNetwork

ISDN

4711

STN-B

Source-Group = 18ALT-NO for APE = 99

HiPath 4000

4712

AP 3700-9

CO incoming:+49-89-723

APE situation

4711

ISDN

ATND = 99

01711234567


41

42


If you are sure, you will not use different alternate routing destination numbers for OOS and APE situations, it may be enough to define only alternate routing destination numbers for the type = OOS.

ADD-APRT:TYPE=ALTERR,SRCGRP=18,ALRTYPE=OOS,ALTRTNR=99;

CHANGE-SDAT:STNO=4711,TYPE=DATA1,STNOOOS=001711234567;



2.3 Service information

2.3.1 Additional control mechanisms

To prevent loops or several alternate routes after the other, you can use 2 DARs, “ALTRTOOS” for the “out of service” situation” and “ALTRTAPE” for the “Emergency” situation, in AMO WABE. The number of the DAR must be used in AMO SDAT / APRT in the alternate number.

For example:

AMO WABE: ALTRTOOS = 77ALTRTAPE = 78

AMO SDAT: STNOOOS = 0089-723-77-.....AMO APRT: ALRTYPE = OOS, ALTRTNR = 0089-723-77-.....

AMO SDAT: STNOAPE = 0089-723-78-.....AMO APRT: ALRTYPE = APE, ALTRTNR = 0089-723-78-.......

2.3.2 General plausibility information

The amo syntax checks cannot verify all implausible administered alternate routing infor-mations.

The administrator therefore has to verify itself very careful, whether alternate routing des-tination numbers in networking leads to seizable destinations.

Even if implausible alternate routing data passes the amo syntax check, call processing will prevent system confusion like loops in switch or networking.

Unusable alternate routing destination numbers will be indicated by advisory outputs at us-age time, if the related DIAGS switch is set.

2.3.3 Special restriction information

The AMO SDAT allows, to set the parameters MVHFAIP and AMOALTRT in parallel for HFA IP phones. Specially for this type of subscriber, the combination of this 2 parameters does not make sense, because a HFA IP phone, that is authorized for moving its logon location from HiPath 4000 to HiPath 3000 in case of IP errors (MVHFAIP) must not request alternate routing, if manuel deactivated by amo (AMOALTRT).

The parameter AMOALTRT only makes sense for those HFA IP phones, that are not au-thorized for moving their logon location.


43

44


The related checks are performed only from call processing at time of execution.

2.3.4 Implausible conditions for supplementation:

1. The administered source group related alternate routing destination number leads to WABE result unequal trunk or PSM/PSE and the parameter EXTNO was set > 0.

– It makes no sense, to supplement a source group related alternate routing destination number, that leads to a destination unequal trunk or PSM.

This will be rejected by syntax check of AMO APRT.

2. In case of routing type APE, the administered source group related alternate routing destination number, leads to a public trunk access.

– If the value of parameter EXTNO is administered smaller than the length of the called subscribers extension number, the related subscriber can not be reached.

The implausibility of the source group related alternate routing destination number for this OOS scenario cannot be detected by the syntax checks of AMO APRT and will only be verified at time of usage.

The result is, that this alternate routing destination number can not be used for routing type APE.

– If the value of parameter EXTNO is administered bigger than the length of the called subscriber extension number, it will be ignored.

In order to avoid wrong or misleading displays, the supplementation then will be done only up to the real length of the called subscribers extension number.

– If the value of parameter EXTNO is administered bigger than the maximum length of subscribers extension number, the command will be rejected by syntax check of AMO APRT.

– If the administered source group related alternate routing destination number contains only a trunk access into public network and the value of parameter EXTNO = 0, neither an alternate destination nor the called subscriber in its AP can be reached.

A supplementation is necessary in this situation and a value of parameter EXTNO = length of called subscriber must be set.

The implausibility of the source group related alternate routing destination number for this routing scenario cannot be detected by the syntax checks of AMO APRT and will only be verified at time of usage.

The result is, that this alternate routing destination number can not be used for routing type APE.



3. In case of alternate routing type = OOS because of device/board error or manual de-activated by AMO, the administered source group related alternate routing destination number leads to WABE result = trunk.

– If the value of parameter EXTNO is > 0, a supplementation with the called subscribers extension number is requested. This makes no sense in general, as this subscriber is in OOS state and cannot be seized successfully, even if doing a loop over public or tie trunk.


The result is, that this alternate routing destination number can not be used for this routing scenario

4. In case of alternate routing type = APE or OOS because device/board error or deacti-vated by AMO, the administered source group related alternate routing number con-tains the access code for PSM/ PSE

● If the PSM/ PSE is designed with search length = 0, a supplementation is neces-sary with the length of called subscribers number.

– If the administered parameter EXTNO is smaller than length of called subscriber, a PSM search cannot be successful.


The result is, that this alternate routing destination number can not be used for this routing scenario

– If the administered parameter EXTNO is bigger than length of called subscriber, a PSM search is possible.

The supplementation will done with the real length of the subscribers extension num-ber.

– If the administered parameter EXTNO is bigger than maximum extension number length, the command will be rejected by syntax check of AMO APRT

● If the PSM is designed with search length = x, a supplementation is necessary with this length x

– If the administered parameter EXTNO is smaller than search length x, a PSM search cannot be successful.


45

46



– If the administered parameter EXTNO is bigger than search length x, a PSM search is possible.

The supplementation will done up to the search length x.

5. In case of alternate routing type = OOS because HFA move logon from HiPath 4000 to HiPath 3000, the administered source group related alternate routing destination number has to be designed in that way, that is possible to reach the moved subscriber in its new switch location via trunk access.

– If the administered parameter EXTNO = 0, the source group related alternate routing destination number is designed as a complete number.

As it is not possible, to reach individual HFA IP phones with a unique unsupplemented alternate routing destination number, this number cannot be used for this routing sce-nario.


– If the value of parameter EXTNO is bigger than the length of the called subscriber number in HiPath 4000, the supplementation will be done up to the real extension number length of the HFA IP phone in HiPath 4000.

2.3.5 Plausibility of alternate routing destination numbers

The AMOs SDAT, ACSU and APRT allow only numbers, that leads to a valid WABE result. Call processing, when trying to use the administered alternate routing destination number does a lot of additional plausibility checks in relation to the OOS scenario, the involved de-vices, the READY state of the alternate destination etc.

The main goal of this additional checks are, to avoid loops in the network and to allow other alternate destinations (call_forward), if the designed alternate routing numbers would lead to a invalid or not seizable destination.

HFA IP phones with the authorization for moving their logon from HiPath 4000 to HiPath 3000 may be logged_off already in HiPath 4000 and not yet logged_on in HiPath 3000. In order to avoid an alternate routing loop between this 2 locations, the IP address of the part-ner gateway has to be administered for the related source group (of the HFA IP phones).

Call processing, when finding out, that the calling device transports the same IP address as administered in the source group of the called HFA IP phone, avoids an alternate rout-ing.



2.3.6 Output of Advisory messages

In order to be informed about not usable administered alternate routing data, you can re-quest a advisory printout with following AMO command.

CHA-DIAGS: PROGID=CC, COMP=CP2, S07=ON;

Whenever at time of execution, alternate routing on error is not possible because of invalid alternate routing number administration, an advisory printout like following example will be printed out.

F4066 M4 N0093 NO ACT BPA CP ADVISORY 03-09-10 13:32:14

ALARM CLASS:CENTRAL:023

CC:15359 EC: 2017 UA:9740:4BB6 SP:C078:1136 LD:01-01-079-004

DT:6C ST:6C SN:B401 CEVT:EF CSEV: 0 CST: 0

FORMAT:24 MESSAGE-ID: 00060


47

48


1. 5. 9. 13. 17. 21. 25. 29.

1A8B2601 1D11003C 01040704 04030000 00040704 07040136 00005E13 2BC45E13

030F0000 00000000 00000000 00000000 00000000 00000000 00000F04 0F040F04

0F040F04 0F040F04 0F040F0 0F040F04 00000000 00040704 07040600 00000600

00000600 00000600 00000600 000F040F 040F040F 040F040F 040F040F 040F040F

040F040F 00000000 00000000 01

Byte 1: Diagnoseformat (1A)Byte 2: Formatlänge (8B) Byte 3-4: Calling Loden (3A00) Byte 5: Calling Device Typ: (1D) = DB_CP_DEVTYP_DIGITE_SUB_AByte 6-7: Called Loden (3V00)Byte 8: Called Device Typ (1C) = DB_CP_DEVTYP_DIGITE_MAINByte 9: Called source group (01) Byte 10: Called number length (04)

Byte 11-32: Called number (03 03 04 04......................)Byte 33: Altern. route reason (02) 01: OOS AP-Emergency

02: OOS deactivated by AMO03: OOS device / board error04: OOS Move HFA logon

Byte 34: Altern. reject reason (04) 01: no gateway_IP address defined02: defined gateway_IP = received

gateway_IP03: no valid WABE result for

alt_rt_on_err04: alt_rt_nr too short05: alt_rt_nr equal to calling/ redir nr06: supplementation of alt_rt_nr

impossible07: alt_rt_nr is/becomes too long08: alt_rt_nr same as redir_nr09: length of supplementation invalid0A: alt_rt_nr leads to not allowed dest0B: alt_rt_nr not usable for PSM cond.0C: alt_rt_nr not usable for PSE cond.0D: alt_rt_nr not usable for PSE_CZ

condition0E: destination for alt_rt_nr not free0F: no loden found with alt_rt_nr



10: alt_rt_nr is equal to called orcalling number

11: suppl. not allowed for OOS12: alt_rt_nr is source_group complete13: no emergency nr defined for

HFA IP phone14: alt_rt_nr defined but not usable15: general implausibility in

alt_rt_on_err

Byte 35 length subscr indiv. alternate routing number fot type = APE Byte 36 - 57 subscriber individual alternate routing number fot type = APEByte 58 length srcgrp related alternate routing number fot type = APEByte 59 - 80 source group related alternate routing number fot type = APEByte 81: number of supplementation digits for type = APEByte 82 - 85 gateway_IP-asdress (not used)Byte 86 length subscr indiv. alternate routing number fot type = OOSByte 87 - 108 subscriber individual alternate routing number fot type = OOSByte 109 length srcgrp related alternate routing number fot type = OOSByte 110 - 131 source group related alternate routing number fot type = OOSByte 132 number of supplementation digits for type = OOSByte 133 - 136 gateway_IP address for HFA move logonByte 137 - 140 gateway_IP address in CPB

<


49

50


2.3.7 HiPath 4000 Assistant

An adaptation of A&S is necessary and requested and will be handed in later.

2.3.8 Realization via AMO: AMO or AMO Batch>

AMO feature relevant com-mands

descriptions

DIMSU ADD - TEST - DISP ● Define the maximum number of subscriber indi-vidual alternate routing destination numbers

SDAT CHANGE - DEL - DISP● Administer the subscriber individual alternaterouting destination number for OOS

● Administer the subscriber individual alternaterouting destination number for APE

● Set the authorization to move the logonlocation for a HPA IP phone

● Set the authorization for alternate routing on er-ror, when deactivated by AMO

APRT ADD - CHANGE - DEL - DISP

● Administer the source group related alternaterouting destination number for OOS

● Administer the source group related alternate routing number for APE

● Administer the source group related gateway_IPaddress for OOS (move logon)

ACSU ADD - CHANGE - DEL - DISP

● Administer the subscriber individual alternaterouting destination for OOS

● Administer the subscriber individual alternaterouting destination number for APE

● Set the authorization for alternate routing on er-ror, when deactivated by AMO



2.4 Relevant AMOs



DIMSU:USER

ALTRUFNU d Anzahl der teilnehmerindividuellen alternativen RoutingZiel-Nummern

ALTROUT e number of subscriber individual alternate routing desti-nation numbers

SDAT UZHFAIP d Berechtigung fuer Logon in HiPath 3000

MVHFAIP e Authorization for move logon to HiPath 3000

AMOALTRT d Berechtigung fuer alternatives Routing, falls mittels AMO deaktiviert

AMOALTRT e Authorization for alternate routing on error if manual deactivated by AMO

TLNNUOOS d Teilnehmer-individuelle alternative Routing Nummer fuer OOS

STNOOOS e Subscriber individual alternate routing number for OOS

TLNNUAPE d Teilnehmer-individuelle alternative Routing Nummer fuer APE

STNOAPE e Subscriber individual alternate routing number for APE

ACSU AMOALTRT d Berechtigung fuer alternatives Routing, falls mittels AMO deaktiviert

AMOALTRT e Authorization for alternate routing on error if manual deactivated by AMO

TLNNUOOS d Teilnehmer individuelle alternative Routing Nummer fuer OOS

STNOOOS e Subscriber individual alternate routing number for OOS

TLNNUAPE d Teilnehmer-individuelle alternative Rufnummer fuer APE

STNOAPE e Subscriber individual alternate routing number for OOS

APRT ALTERR d Typenausscheidung fuer den neuen Zweig Alternatives Routen im Fehlerfall

ALTERR e Type definition for new brach = alternate routing on error

ALRTYP d Typ des alternate Routings (OOS oder APE)

ALTRTYPE e Typ of alternate routing (OOS or APE)


51

52


ALTRTNR d Source Gruppe bezogene alternative Routing Nummber fuer OOS oder APE

ALTRTNT e Source group related alternate routing number for OOS or APE

ERWANZ d Erweiterungsangabe zur alternative Routing Nummer fuer OOS oder APE

EXTNO e Supplementation information for alternate routing num-ber for OOS or APE

GWIPADR d Gateway_IP Adresse fuer den Typ = OOS

GWIPADR e Gateway_IP address for type = OOS




Smart Card Application Siemens

3 Smart Card Application

3.1 Feature Description

A Signature Module (Smart Card Reader) can be connected to an optiPoint 500/600 Telephone (Up0E-interface) as well as an HFA IP Phone optiPoint 410/600.

A Smart Card is plugged into the Signature module, authentication is then carried out in an external server with the application "SmartCard Access Application SCAA".This is connected to the HiPath 4000 via ACL-C and the CAP/CA4000 application.The results of the Authentifi-cation by the application "SmartCard Access Application SCAA" can be used by other applica-tions which can communicate with the application SCAA on the server..

The following functions are supported:

● Support of smart cards corresponding to the ISO ...7816, para1-4 standard.

● Support of the Local Security check procedure by which the user identifies themselves with an ID via keyboard and display of the telephone as an owner of the card itself.

● The smart card provisions a connection via Hipath4000 between the signature mod-ule and the application "Smart Card Access Application SCAA" on the server.This en-ables the local security check procedure LSCP as well as the user prompts once the application has seen the card

● The application mobile subscriber for activating the HiPath pin.

Sm artCard(SC)

SignatureModule

optiPoint 500optiPoint 400 HFAoptiPoint 600 HFA HiPath 4000

Server(CAP/CA 4000)

Sm artCard Access Application SC AA

OtherApplications

ISO 7816-4

ISO 7816-4 CorNet-TSCorNet-TS CorNet-TSCorNet-TS LANLANACL-CACL-C

ACL-C link

optiPoint 500/600optiPoint 410 HFAoptiPoint 600 HFA

EN0000DE00EN_0000© 2004 Siemens AG

53

54

Smart Card ApplicationSiemens

3.2 User Interface

The Smart Card can be inserted and removed in any state of the telephone(free, busy,etc).

The user interface to identify the user is controlled via SmartCard (Local Security check Pro-cedure) by means of a Card ID which interfaces with the SmartCard Access Application SCAA for the identification of the user.

The Smart Card Access Application SCAA takes control of the telephone display by placing it into the Non-Voice condition and the Non-Voice LED is turned on.

The entered numbers of the Card ID are not seen on the display. The end of dial condition( such as "#" or number of ID numbers) is configured in the Smart Card Access Application SCAA .

After successful authentication from the Smart Card Access Application SCAA on the server has been initiated,then the subscriber identified by means of the smart card has the feature "mobile subscriber" activated. The input of the subscriber phone number which was neces-sary with the chip card for Optiset E is not necessary with the SmartCard.

After inserting the card and successful activation of the feature "mobile user"the station has the rights and special features of the smart card user (dial plan membership,traffic restriction group,etc).This is also the case when a smart card is inserted while during a connection,with another smart card or "Pin Manual".

3.3 Service Information

Remark:

The description of the Smart Card Access Application SCAA is not part of this feature descrip-tion.

7 Attention:

The implementation of the feature in the Hipath 4000 V2.0 is dependent on the availability of the Application (SCAA) !


Smart Card Application Siemens

3.4 AMO Usage

1. The SmartCard feature is switched on in the system:

CHANGE-FEASU:TYPE=A,CM=SMARTCRD;

2. In the situation where the DVA-Application SCAA (here under applnu=61)already ex-ists:

– ConfiguringSmartCard Access Application Link :

CHANGE-XAPPL:CTYPE=APPL,APPLNO=61,SECAPPL=111;

In the case where the DVA-Application SCAA does not exist:

– Configuring the DVA-Application and SmartCard Access Application Link (The AMO CPTP is used to give the application a name with the parameter APPLDP here for example. "SCAA") :

ADD-XAPPL:APPLNO=61,APPLDP="SCAA",NAME="APPLICATION 22",SECAPPL=111;

Attention : With the Parameter SECAPPL no more than 20 SmartCard AccessApplication Links can be configured!

3. In the case where the subscriber already exists:

– Additionally configuring the Signature Modules (SmartCard Reader)for the subscriber:

CHANGE-SBCSU:STNO=3456,OPT=OPTI,IDCR=YES;

– Assign the SmartCard Access Application Linkto the subscriber:

CHANGE-SBCSU:STNO=3456,OPT=OPTI,SECAPPL=111;

– setting “Mobile User Activation via SCAA/AMU” for the subscriber:

CHANGE-SBCSU:STNO=3456,OPT=OPTI,APMOBUSR=YES;

– All parameters can be changed together with:

CHANGE-SBCSU:STNO=3456,OPT=OPTI,IDCR=YES,SECAPPL=111,APMOBUSR=YES;

In the case where the subscriber does not yet exist:

ADD-SBCSU:STNO=3456,OPT=OPTI,etc.......IDCR=YES,SECAPPL=111,APMOBUSR=YES;


55

56

Smart Card ApplicationSiemens

3.5 Relevant AMOs

● German and English examples of relevant AMOs and new parameters



FEASU SMARTCRD D Leistungsmerkmal SmartCard im System freischalten

FEASU SMARTCRD E Activate SmartCard feature usage system wide

SBCSU SECAPPL D SmartCard Access Application Link zuweisen

SBCSU SECAPPL E Assign SmartCard Access Application Link

SBCSU APMOBUSR D Aktivierung Mobile User über SCAA/AMU

SBCSU APMOBUSR E Mobile User Activation via SCAA/AMU

XAPPL SECAPPL D SmartCard Access Application Link einrichten

XAPPL SECAPPL E Create SmartCard Access Application Link


HG3550V2.0 WAML-Replacement Siemens

4 HG3550V2.0 WAML-Replacement

4.1 General

The following scenarios give a summary of the application cases for the HG3550v2.0 WAML Replacement .The exact description of the configuration of the second scenario (LAN-WAN) is not part of this document ; this is covered by the configuration manual (HiPath 4000 Manager).

The HG3550 V2.0 is not intended to replace the WAML board.The purpose of the HG3550 V2.0 WAML is to make LAN Connectivity to UW, so that Remote Access(RAS) to the HiPath 4000 administration by means of HiPath assistant/manager is possible .(feature "Serviceability").

The LAN Connectivity is a feature which provides 2 Ethernet LAN interfaces and an ISDN con-nection.

The Board required to this purpose is the HG3550 V2.0. With this board there is the possibilty to attach an external LAN to the Hicom or HiPath 4000 and to make data transmission via the ISDN network, from an arbitrary subscriber, into the Atlantic LAN (ATLLAN) and to the HiPath assistant, provided that the required rights are existing.

To be able to use the LAN Connectivity, you must establish specific configuration data for the WAML with WBM, after setting up the board with the appropriate AMOs. Only after this the LAN Connectivity operational. On this occasion the configuration is not checked for consis-tency with the topology of an existing network (e.g. IP-addresses).

An integrated LAN/ISDN Router function controls the transmission of the Data Packets between the WAML Network interfaces.

These implementations are made possible:

● SCN-LAN

● LAN-WAN

HG3550

*)

HUBC

PSTNcustomer

LAN

HiPath 4000

S0/S2

AtlanticLAN

*) DIUS2 /.STMD

e.g.. HTS

ADP

S0


57

58

HG3550V2.0 WAML-ReplacementSiemens

Is only possible with the HiPath 4000 Manager !

In this feature usage document, only the scenario “SCN-LAN” is described.

HG3550

*)

HUBC

PSTN

HUBC

customerLAN customer

LAN


S0/S2 S0/S2

AtlanticLAN

AtlanticLAN

*)

*) DIUS2/ STMD

e.g. DMS ADP ADP

HG3550



4.2 SCN-LAN

The PC with the phone numbers 7374 shall be allowed to dial in via an ISDN connection with the phone number 80313 and access the UW7 ( IP address 192.0.2.5) via the Atlantic LAN. To UW7 only PPTP connections are possible. The PPTP server in the UW7 (UBA) is configured in this example in this way, that it allocates the IP-address 10.32.192.5 as virtual remote IP-address.To this IP-address (10.32.192.5), UW7 uses the IP-address 10.32.254.193 (virtual lo-cal) as gateway to the HG3550 V2.0. This is a fix address, set by the system. The allocation of these IP addresses is fixed in the "VPN ADDRESS Space of HICOM 300 H for Hipath4000 V2.0". For this connection a CHAP authentification is required (in this example; User: HG3550, password: 1234).

Dial-up: 10.32.252.65

7374

ISDNISDN

HiPath 4000 V2.0

80313

HG

3550V2.0

CLAN: 1.30.31.180ATLAN: 192.0.2.4Virtual: 10.32.254.193localCC

ADP

UW7: 192.0.2.5Virtual: 10.32.192.5remote

AtlanticLAN

10.1.192.5


59

60


4.2.1 Configuring the HiPath 4000 V2.0

The HG3550 V2.0 is reached via the phone number 80313 and is operated in Mixed mode. It has the customer LAN IP address 1.30.31.180 and the Atlantic LAN IP address 192.0.2.4.

4.2.1.1 Adding the STMI2-IGW board and configuring the Board Data:

● Assign Flexama Memory for STMI2-IGW configuration data with AMO DIMSU :

ADD-DIMSU:TYPE=SYSTEM,STMI2IGW=<number>;

● Adding the Board at LTU=2 and SLOT=25 (Q2316-X with 60 B-Channels, Q2316-X10 with 120 B-Channels):

ADD-BCSU:MTYPE=PER,LTU=2,SLOT=25,PARTNO="Q2316-X",FCTID=5;

● Adjust HG3550 V2.0 Board data:

ADD-STMIB:MTYPE=STMI2IGW,LTU=2,SLOT=25,CUSIP=1.30.31.180,CUSPN=8000,SNETMASK=255.255.255.0;

CHANGE-STMIB:MTYPE=STMI2IGW,LTU=2,EBT=251,TYPE=IFDATA,ATLIP=192.0.2.4;

● To load the new board data to the board:

RESTART-BSSU:ADDRTYPE=PEN,LTU=2,SLOT=25;

4.2.1.2 Configuring the HG3550 V2.0 LAN Circuit:

● The COT to be used should be configured as follows:

ADD-COT:COTNO=XXX,PAR=ANS&CEBC&IEVT&BSHT&NTON&DFNN&NLRD&LWNC,INFO="WAML-REPLACEMENT";

● The COP to be used should be configured as follows:

ADD-COP:COPNO=XXX,PAR=L3AR,TRK=TA,TOLL=TA,INFO="WAML_REPLACEMENT";

● The COS to be used should be configuired as follows:

ADD-COSSU:NEWCOS=<number>,INFO="HG3550-2-LAN";CHA-COSSU:TYPE=LCOSD,LCOSD=<number>,ALAUTH=1&&64;



● Adding a new Trunk Group (e.g.. 355):

ADD-BUEND:TGRP=355,NAME="HG3550-2-LAN",NO=30;

● Adding the Trunk HG3550 V2.0 LAN-Connectivity (for Q2316-X pen 1, for -X10 pen 3 is to be used):

ADD-TDCSU:OPT=NEW,PEN=1-2-25-1,COTNO=<number>,COPNO=<number>,COS=<number>,LCOSV=<number>,LCOSD=<number>,CCT="WAML_REP",ATNTYP=TIE,PROTVAR=ECMAV2,SEGMENT=8,NNO=<numb.>,DEV=HG3550LA,TGRP=355,BCHAN=1&&30;

● Adding the call number (80313) for the HG3550 V2.0:

ADD-WABE:CD=80313,DAR=TIE,CHECK=N;

● Adding the Route (LRTE=355) for the STMI2-IGW trunk group:

ADD-RICHT:MODE=LRTENEW,LRTE=355,LSVC=ALL, NAME="WAML_REP", TGRP=355,DNNO=e.g. 1.30.31.255;

● Adding outdial rule (e.g. ODR=355) :

ADD-LODR:ODR=355,INFO="WAML_REP",CMD=ECHO,FIELD=1;ADD-LODR:ODR=355,CMD=NPI,NPI=UNKNOWN,TON=UNKNOWN;ADD-LODR:ODR=355,CMD=END;

● Adding the LCR Route (LRTE=355):

ADD-LDAT:LROUTE=355,TGRP=355,ODR=355,LAUTH=e.g. 1;

● Adding the LCR dialing plan:

ADD-LDPLN:LCRCONF=LCRPATT,DIPLNUM=0,LDP=80313,LROUTE=355,LAUTH=e.g 1;


61

62


● Displaying the status of the circuit (possibly activate the circuit):

DISPLAY-SDSU:STATUS=ALL,TYPE=PEN,LEVEL=PER3,LTG=1,LTU=2,SLOT=25;

RESTART-DSSU:TYPE=PEN,PEN1=1-2-25-1;

● Prevent new loading of the Loadware from harddisk, if the board is reset (faster loading):

CHANGE-FUNSU:PIT=FLASH,PARTNO="Q2316-X",FCTID=5,ACTION=RESET;

Please check after every Reset of the board (HG3550 V2.0) !



4.2.2 Configuring UBA in HiPath 4000 Assistant

● Setting the customer VPN Server address

Menu: Base Administration -> Unix Base Administration -> WAN Configuration

● The “PPP Links Details” message has to be filled out at the time, but the settings are not used.


63

64


● Start the PPTP connection (in this example. Name: HG3550, Secret: 1234)

● Restart of the Unix Server.



4.2.3 Configuring the Gateway HG3550 V2.0

4.2.3.1 Installing XML30

● Execute msxml3ger.msi and follow the installation guide.

4.2.3.2 Establish connection to the HG3550 V2.0

Start the HiPath 4000 Assistant to get access to the Web Base Management (WBM) of the board (a direct connection via an Internet Browser and IP address is no longer possible).

Menu: Expert Mode -> HG3550 v2 Manager

1st. Search board(s)2nd. Connect with the WBM of the board


65

66


To change settings or to add new entries in the WBM - Explorer of the HG3550 V2.0, click with the right mouse button on the entry, which should be used.

Enable write access



4.2.3.3 Checking the LAN1 interface settings

The LAN1 interface is configured automatically by the AMO STMIB (only check the settings).

● Exlorer -> Network Interfaces -> LAN1 (LAN1)


67

68


4.2.3.4 Configuring the LAN 2 interface

The IP address of the Atlantic LAN is assigned automatically to the LAN2 interface by the AMO STMIB. The other parameters have to be set as following; (CHAP Password: 1234):



4.2.3.5 Setting the WAML call number

The pc uses this number for dialing-up.

● Explorer -> Routing -> PSTN


69

70


4.2.3.6 Configuring PSTN Peer

The PC is configured in this way, that it expects an assignment of a IP address. The peer is assigned the IP address 10.31.252.65 with the following configuration (CHAP Password: 1234).

● Explorer -> Routing -> PSTN -> PSTN Peers

Add new PSTN Peer (right mouse click):




71

72


4.2.3.7 Setting the Calling number of the peer

The number 7374 will be transfered as Calling number. That number must be configured as PSTN peer number, to identify the peer and its settings. In this case the authorization is set to incoming and outgoing. It would also be possible to select only incoming, if a call only should come from the SCN to the Atlantic LAN.

Add PSTN Peer Number (right mouse click):



4.2.3.8 Save board data

● Maintenance -> Configuration -> Load from Gateway

1st Save board data

3rd Logoff

2nd Save configu-ration on the PC

Load button


73

74


4.2.4 Configuration of the PC

The configuring of the PC is described by using a S0 card.

On the PC a “Dial-up Connection” is installed as following:

Installing: Start -> Settings -> Network and Dial-up Connections -> Make new Connection

Normally an external number will be used (e.g. +49-89-722-80313) !




75

76


Select:Properties

Select:General



Select:Networking

Select:Settings


77

78


Select:TCP/IPProperties

Select:IP addressAdvanced...



Select:GeneralDeactivate


79

80


4.2.5 Checking the VPN address and PPP1 settings

Use the HiPath 4000 Assistant Home Page to check the System Information.

Instruction: Home Page HiPath 4000 Assistant -> Clicking on “i” of “HiPath 4000 V2.0”

Select 16 (Network Interfaces):



4.2.6 Adding S0 Subscriber

ADD-SBCSU:STNO=7374,OPT=FBUS,CONN=DIR,PEN=1-2-37-5,DVCFIG=SET600&DTE, COS1=131,COS2=131,LCOSV1=9,LCOSV2=1,LCOSD1=9,LCOSD2=1,DPLN=0,ITR=0, SSTNO=N,COSX=0,SPDI=0,SPROT=SBDSS1,DPROT=SBDSS1,PERMACT=Y,INS=Y, ALARMNO=11,SOPTIDX=10,DOPTIDX=10,EXTBUS=Y,RCBKB=N,RCBKNA=N, CBKBMAX=5,HMUSIC=0;

This step is only necessary in case of training !


81

82


4.2.7 Starting the Dial-up Connection

4.2.8 Adding a “Route add” on the PC (DOS-cmd)

Is a LAN connection activated on the PC, the following Dos command is entered:

route add 10.32.192.5 10.32.252.65

Select:Dial



4.2.9 Getting access to the HiPath 4000 Assistant

Start the Internet Browser and enter the IP address 10.32.192.5:


83

84



AMO Authorizations Siemens

5 AMO Authorizations in the HiPath 4000 V2.0

5.1 ADP

ADD

CHANGE

DELETE

DISPLAY

REGENERATE

OUTPUT

ACTIVATE

DEACTIVATE

SWITCHOVER

START

STOP

SET

EXEC

OUTPUT

COPY

DUMP

DIALOG...

INPUT

UMBENNEN

SAMMELN

ACMSM 4 4 4 4 4

AFR 5 5 5 0 0 0 5 5 5

ANUM 2 0 2

APC 0 0 2 2 2

APP 3

APS 0 0 2 2 2

ASPIK 2

ASSGN 2 0 2 0

ATCSM 2 2 2 0 2

AUTH 10 0 2

BACK 2 2 2 0 2 2 2 2 2

BCSM 2 2 0 2 2 2

CABA 2 2 2 2 2

CDBR 2 0 2 2

CDSM 0

CLIST 2

CMP 2

CMUID 5


85

86

AMO AuthorizationsSiemens

CONSY 2 2 2 0 2 2

COPY 3

CPCI 2 0 2

CPSM 2 2 2 0 2

CPTP 2 2 0 2

CRON 5 5 5 0 2

DAGR 1 1 1 1 2 1

DASM 2 2

DATE 2 0

DAVF 1 1 2

DCSM 2 2 2

DDRSM 2 2 2 5

DDSM 0 2

DEBUG 3 3 3

DEFPP 2 2 2 0 2

DEFTM 2 2 2 0 2

DEL 3

DISPA 3 3

DLSM 2 2

DSSM 2 2 2 2

DPSM 2 2

DTSM 2 2 2 2

ADD

CHANGE

DELETE

DISPLAY

REGENERATE

OUTPUT

ACTIVATE

DEACTIVATE

SWITCHOVER

START

STOP

SET

EXEC

OUTPUT

COPY

DUMP

DIALOG...

INPUT

UMBENNEN

SAMMELN



DUP 3

DVU 2 2 2

FAMOS 2 2 0 2 2 2

FAMUP 2 2 2 2 2 2 2 2 2 5

FBTID 2 2 20

2

FBTN 1 1 1 2

FEACG 4 4 0 2

FETA 1 1 1 2

FINF 2 2

FORM 3

FTBL 1 1 1 1 1

FTCSM 2 2 2 2 2

FTRNS 2 0 2

FUNCT 2 0 2

GEFE 2 0 2

GENDB 5

GETAB 1 1 0 2 1 1

GETPD 0

GEZAB 1 1 1 1 1 1 1

GEZU 2 2 2 0 2

GRA 2 2

GRZW 1 1 1 0 2

ADD

CHANGE

DELETE

DISPLAY

REGENERATE

OUTPUT

ACTIVATE

DEACTIVATE

SWITCHOVER

START

STOP

SET

EXEC

OUTPUT

COPY

DUMP

DIALOG...

INPUT

UMBENNEN

SAMMELN


87

88


HISTA 2 2 2 0 0 2 2 2 2

INFO 2

INIT 3 0 3

JOB 5 0

KDEV 1 1 1 1 1 1

KDGZ 1 1 1 0 1

LCSM 2 2 2 0 2

LDB 3

LIST 2

LOGBK 5 5

LSSM 0 2 2 0

PASSW 5 5 5 5 2

PATCH 2 2 2 0 2 2 2 2

RCUT 1 1 1 1 2

REGEN 5

REN 3

REST 2 0 0 2

SAVCO 3

SAVE 3

SDSM 0

SELG 1 1 1 1 2 1

SELL 1 1 1 2

ADD

CHANGE

DELETE

DISPLAY

REGENERATE

OUTPUT

ACTIVATE

DEACTIVATE

SWITCHOVER

START

STOP

SET

EXEC

OUTPUT

COPY

DUMP

DIALOG...

INPUT

UMBENNEN

SAMMELN



SELS 0 2 1 1 1 1

SIGNL 2 2 2 0 2 0 2 2 2 5

SONUS 2 0 2 2

SPES 2 2 0 2 2 2

SYNC 5 0 5 5

TABT 1 1 1 1 2

TCSM 2 2 2 0 2

TEST 0 0

TEXT 1 1 0 2

TINFO 2 0 2

TLZO 1 1 1 1 2

TRACA 2 2 2

TRACS 2 2 2

TTBL 1 1 1 1 2

UPDAT 2 0 2 2

USER 10 10 10 0 2 10 10 2

UW7 5 5 5

VADSM 2 0 2 2 2

VEGAS 2 2 0

XAPC 0 0 0 0

ADD

CHANGE

DELETE

DISPLAY

REGENERATE

OUTPUT

ACTIVATE

DEACTIVATE

SWITCHOVER

START

STOP

SET

EXEC

OUTPUT

COPY

DUMP

DIALOG...

INPUT

UMBENNEN

SAMMELN


89

90


5.2 CC

ADD

CHANGE

DELETE

DISPLAY

REGENERATE

OUTPUT

ACTIVATE

DEACTIVATE

SWITCHOVER

START

STOP

SET

EXEC

OUTPUT

COPY

DUP

TEST

RESTART

DIALOG...

INPUT

OPTIMIZE

DIAGNOSE

ACDGP 2 2 2 0 2

ACDRS 2 2 2 0 2

ACDRT 2 2 2 0 2 4 2 2

ACDSD 2 0 2

ACSU 2 2 2 0 2

ACTDA 2 2 0 2

AGENT 2 2 2 0 2

ANSU 2 0 2

APRT 2 2 2 2 2

AUN 2 2 2 0 2

AUTHO 0

BCSU 2 2 2 0 2

BDAT 2 2 2 0 2 2

BGDAT 2

BERUM 2 0

BERUZ 2 0 2

BGDAT 2

BPOOL 2 2 2 0 2

BSSU 2 2 2 2 5

BUEND 2 2 2 0 2

CDSU 0



CHESE 2 2 2 0 2

CODEW 5 3 5 5 3 5

COMGR 2 2 2 2 2

COP 2 2 2 0 2 2 5

COSSU 2 2 2 0 2

COT 2 2 2 0 2 2 5

CTIME 2 0 2

DBC 3 5 0 0 3

DBSUM 0

DCIC 2 2 2 0 2

DIAGS 2 0 5 5 5

DIDCR 2 2 2 0 2

DIMSU 4 0 2 4 0

DISPS 3 3 3 3

DNIT 2 2 2 0 2

DSSU 2 2 2 2 5 2 5

DTIM1 2 0 2

DTIM2 2 0 2

FEASU 4 0 2

FUNSU 2 0 2 2

GKREG 2 2 2 2 2

GKTOP 5 5 5 5 5

ADD

CHANGE

DELETE

DISPLAY

REGENERATE

OUTPUT

ACTIVATE

DEACTIVATE

SWITCHOVER

START

STOP

SET

EXEC

OUTPUT

COPY

DUP

TEST

RESTART

DIALOG...

INPUT

OPTIMIZE

DIAGNOSE


91

92


HFAB 2 2 0 2 2

HIDMP 2 2

HOTLN 2 2 2 0 2

KCSU 2 2 2 0 2

KNDEF 2 2 2 0 2

KNFOR 2 2 2 4 4 4

KNLCR 2 2 2 0 2

KNMAT 2 0 2

KNPRE 2 2 2 0 2

KNTOP 2 2 2 0 2 2

LANC 2 2 2 0 2 2 2

LAUTH 3 3 3 4 4

LDAT 2 2 2 0 2

LDPLN 2 2 2 0 2 2

LDSRT 2 2 2 0 2

LEMAN 2

LIN 2 2 2 2 2

LODR 2 2 0 2

LPROF 2 2 2 0 2

LRNGZ 2 2 2 0 2

LSCHD 2 0 2

LW 0

ADD

CHANGE

DELETE

DISPLAY

REGENERATE

OUTPUT

ACTIVATE

DEACTIVATE

SWITCHOVER

START

STOP

SET

EXEC

OUTPUT

COPY

DUP

TEST

RESTART

DIALOG...

INPUT

OPTIMIZE

DIAGNOSE



LWCMD 3

LWPAR 2 2 2 0 2 2

MFCTA 2 0 2 2

NAVAR 2 2 2 0 2

PERSI 1 1 1 1 1

PETRA 2 0 2 2

PRODE 2 0 2 2

PSTAT 2 2 2

PTIME 2 0 2 2

RCSU 2 2 2 0 2

REFTA 2 2 2 0 2 2

RICHT 2 2 2 0 2

RUFUM 2 2 0 2

SA 2 2 2 0 2

SBCSU 2 2 2 0 2

SCREN 2 2 2 0 2

SCSU 2 2 2 0 2

SDAT 2 0 2 5

SDSU 0

SIPCO 2 2 2 2 2

SSC 2 2 0 2

STMIB

ADD

CHANGE

DELETE

DISPLAY

REGENERATE

OUTPUT

ACTIVATE

DEACTIVATE

SWITCHOVER

START

STOP

SET

EXEC

OUTPUT

COPY

DUP

TEST

RESTART

DIALOG...

INPUT

OPTIMIZE

DIAGNOSE


93

94


SSCSU 2 2 2 0 2

STMIB 3

SXSU 2

SYNCA 2 2 2 0 2 2

TACSU 2 2 2 0 2 5 5 5

TAPRO 2 0 2 2

TDCSU 2 2 2 0 1 2 2

TGER 2 2 0 2

TREF 5 0 2 5 5

TSCSU 2 2 2 0 2

TSU 2 2 5

TWABE 2 2 0 2

UCSU 2 2 2 0 2

UPLOL 5

UPLO2 5

USSU 2 2

VADSU 2 2 2 0 2 2 2

VBZ 2 0 2

VBZA 2 0 2

VBZGR 2 2 0 2

VFGKZ 2 2 2 0 2

VFGR 2 2 2 0 2

ADD

CHANGE

DELETE

DISPLAY

REGENERATE

OUTPUT

ACTIVATE

DEACTIVATE

SWITCHOVER

START

STOP

SET

EXEC

OUTPUT

COPY

DUP

TEST

RESTART

DIALOG...

INPUT

OPTIMIZE

DIAGNOSE



VOICO 2 2 0 2 2 2

WABE 2 2 2 0 2

XAPPL 4 4 4 0 4

ZAND 2 0 2 5 5 5

ZANDE 2 0 2

ZAUSL 0

ZIEL 2 2 0 2

ZIELN 2 2 0 2

ZRNGZ 2 2 0 2

ADD

CHANGE

DELETE

DISPLAY

REGENERATE

OUTPUT

ACTIVATE

DEACTIVATE

SWITCHOVER

START

STOP

SET

EXEC

OUTPUT

COPY

DUP

TEST

RESTART

DIALOG...

INPUT

OPTIMIZE

DIAGNOSE


95

96


5.3 Dropped AMOs

ADD

CHANGE

DELETE

DISPLAY

REGENERATE

OUTPUT

ACTIVATE

DEACTIVATE

SWITCHOVER

START

STOP

SET

EXEC

OUTPUT

COPY

DUP

TEST

RESTART

DIALOG...

INPUT

OPTIMIZE

DIAGNOSE

BST 0 0 0

PSA 0 2 2 2

PSS 0 2 2 2


Extended features and AMO changes in the HiPath 4000 V2.0 Siemens

6 Extended features and AMO changes in theHiPath 4000 V2.0

6.1 AMOs

ACSU

– ACTYPE = AC4, ACW2Q und ACWMQ

– New ACWIN-Software for Windows XP: ACWIN 5.0 and ACWIN MQ 3.0(DS-WIn 3.0 and BLF-Win 3.0 are necessary for ACWIN 5.0 and MQ 3.0.ASC 3.0 (Hicom 300H) resp. ASC 4.0 (HiPath 4000) are necessary for ACWIN 5.0.With ASC 5.0 both ACWIN variants can be used.)

BCSM– DEACTIVATE-BCSM:UNIT=A1,SYSTEM=UNIX; -> Unix-Boot is blocked for the next

Unix-Restarts after the ADP-Data base is updated;EXEC-UPDAT:UNIT=A1,SUSY=ALL;

– ACTIVATE-BCSM: UNIT=A1,SYSTEM=UNIX; -> Unix-Boot is started;

BUEND– Parameter RSV falls out.

CPCI

– DISP-CPCI; Shows, which transfer mode are set for LAN in-terfaces “Service” and “Atlantic” of the DSCXL board, if the DSCXL board is used as ADP.Additional is shown, if the switch is a DUAL or MONO system, and if RTM modules are in-stalled or not (important for generating a sys-tem).

– CHA-CPCI: TYPE=FRONTPAN

Setting in which mode the LAN interfaces “Ser-vice” and “Atlantic” of the DSCXL board should work, if the board is used as ADP or CC-AP.(10 or 100 Mbits full or half duplex)


97

98

Extended features and AMO changes in the HiPath 4000 V2.0Siemens

COP– New parameter: LCOS -> Limitation of LBER to 32 for transfering;

– Parameters RES 162-171fall out;

COSSU

– The LCOSV- and LCOSD-classes can be increased up to 1000.The highest number of the class depends on AMO DIMSU:TYPE=USER,LCRCOS=xxxx;

COT

TYPE=SYSCONF

Setting, if the switch is a MONO or DUAL sys-tem, and if RTM modules are installed.

MONO Mono or Dual configuration (YES / NO)

RTM RTM board installed or only IPDA components installed (YES / NO)

– BKNA -> Activation disables feature “calling name delivery”

– BFSR -> Block forwarding switching after reject

– CDN -> Call deflection networkwide

– CFBN -> Call forward busy networkwide

– DTMF -> Inband dtmf when SETUP contains no classmarks

– IBBA -> Send digits via in-band dtmf before answer

– PGEP -> Partner node does not know HiPath GEP signalling

– SPCP -> Voice compression preferred



DIMSU

● USER

– LCRCOS Maximum number of LCOSV/LCOSD in AMO COSSU;This is th highest number, which could be added in AMO COSSU; i.e. if 50 is set the class 51 can not be added in AMO COSSU.

– ALTROUT Number of alternative numbers for subscribers, ATNDIND and AP-Emer-gency, (OOS and APE);

– SLKTEXT Number of SLK keys with individual text;

– CALLOGS Number of devices with Self Labling feature (SLK);

– HOTDEST Number of Hotline destinations (up to 65535)

● NETWORK

– LDPLN1-8 LCR dialing plan 1-8; LDPLN1 für Standard LCR, LDPLN2-8 für Large Gatekeeper;

– LDPLNC1-8 LCR Wählmuster Cache; LWMC1 für Standard-LCR, LDPLNC2-8 für Lar-ge Gatekeeper;

● SYSTEM

– STMIHFA2 Number of STMI2 boards (HG3530V2.0) for the feature HFA;

– STMI2IGW Number of STMI2 boards (HG3550V2.0) for the feature IP-Trunking V2;

– GWREG Number of internal and external Gateways (feature LEGK);

– CCAP Number of Emergency APs (feature APE);

– EMGRP Number of Emergency AP groups (feature APE);

– SCTPATH Number of IP sectorpaths (feature LEGK);


99

100


FUNCT

– LOGBKOFF Prevents logbook entries (values 0-8):

– 0= none

– 1= DISPLAY-BUEND (cause: Traffic monitoring in the Assistant)

– 2= EXEC-UPLO/UPLO2

– 3= REGEN-CPTP

– 4= CHANGE-FUNCT;

2+3+4 are often used by UNIX.

HOTLN

– In branch: HOTDEST, destinations are increased to 2512;

LDAT

– Number of LRTEs is increased to 64000;

LDPLN

– Two new branches in parameter LCRCONF:

1. LCRPATT:

● DIPLNUM (0-2047)In standard the DIPLNUM=0 is to be used;DIPLNUM=0 is fixed and can not be changed or deleted;Is used for 1:1 converting from HiPath 4000 V1.0 without the feature LEGK (Large Enterprise Gatekeeper)

2. LCRADM

● DIPLNUM (1-2047)

● LWMPOOL (1-8) -> DIMSU:NETWORK,LDPLN1-8

● DIALPLN (0-255)

LPROF

– Profile indexes are increased to 3000;



LSSM

– Switching the new LAN interfaces (LN=1-6,TYPE=LAN) at the cPCI-Shelf.

PATCH

– The noun REGENERATE for optional Patches is new;

RCSU

● New parameter branch for IP connections;

– CLASSMRK

RICHT

– Number of LRTEs increased to 64000;

SSC

– New parameter branch for IP connections with EXTANN:

● CLASSMRK

TAPRO

– 256 key layouts;

– The TIME key shows during calls the time at the display for 10 seconds(now usable for all opti);

VFGR

– Parameter CQMAXF falls out;


101

102


XAPPL

– The new parameter TSKA has to be set to YES in the application 92 (TSKA), if you want to use the application in the HiPath 4000 Assistant V2.0;

ZAND

● ALLDATA

– DSSLT (Number of direct station select partners) increased to 70;

● ALLDATA2

– HOTELNUM Entering a number between 0 and 9 (number length of hotel stati-ons);

– DISPREST Display name independent of supressed number;

– Parameter falls out: INDNADIS; the new parameter is DISPREST

● ALLDATA3

– CFNRDEST Call forward on no reply to the deactivated fixed call forward destination (value USECFUF) (old CF concept). For the valueONLYCFNR the special CF destinations (CFNR und CFB) are used(new CF concept);

– EXANTRF external announcement after transfer;

– IPDAVCCF Voice Compression for IPDA connections in conference or announcement situations;

● OPTISET

– PUSECOK Pick up of second call enabled with OK key;

– CALLOG Supress the deletion of callog entries in the Service menu;

● CIT

– Parameter UMKOV falls out;



ZANDE

● ALLDATA

– SCALLOG Y

N

->

->

Source number in callog;

After transfer the transfered subscriber (Subscriber_A) is registered in the callog of the Subscriber_C;

After transfer the transferring subscriber (Subscriber_B) is registered in the callog of the Subscriber_C;

– VCANNCNF Y/N -> Voice Compression for conference and announcement situations;

– H235SEC Y/N -> Activates / deactivates H.235 Security for STMI2IGW boards;

– GATEKPR Y/N -> PBX with Large Enterprise Gatekeeper (LEGK);

– DECTPS Y/N -> Via this parameter the DECT Positioning System (laca-ting of DECT Mobile phones) will be activated resp. deactivated;

– NONPIIW Y/N -> For detailed describtion see ComWin300 Edit; (only used in US);

– DAJB Y/N -> The configuring of the Jitter Buffer is not possible in the WBM of a STMI2 board, if this parameter is set. The set-ting in AMO STMIB branch DSP are used;

– NOVNIDCO Y/N -> Since HP4K V1.0 AMO KNMAT corrects the virtual node ID to avoid dependences from node to node in dif-ferent regions.If NOVNIDCO=YES is set, this behaviour is disabled, what means, that the KNMAT modification works like HP4K V1.0 before.

– IMPRPKZ Y/N -> If this parameter is set, both levels of one name key can be chained for PKZ usage;

– SILMON Y/N -> If this parameter is set, Silent Monitoring is only possible for member of the ACD group of the monitorer. If this pa-rameter is not set, there are no restrictions to any ACD groups.


103

104


6.2 CLIP for analoge Subscribers

● Requirement

The calling number and the name of the calling party should be displayed on analoge phones. For that the ETSI Standard with FSK Modulation resp. DTMF signalling should be supported. Also Visual Message Waiting Indication is required for FSK Modulation.

● AMO usage

In AMO ZAND the CLIP standard is set for the whole system. AMO BCSU and SCSU are used for adding the SLMAC board and the analoge subcribers. AMO FEASU is used for activation or deactivation of the CLIP analoge.

● Example for adding CLIP for analoge Subscribers

1. Adding the new board SLMAC:

ADD-BCSU:MTYPE=PER,LTU=XX,SLOT=XX,PARTNO="Q2191-C";

2. Adding of CLIP analoge subscribers with AMO SCSU (Without using parameter DHPAR):

ADD-SCSU:............................;

3. Activation CLIP analoge standard:

CHANGE-ZAND:TYP=ALLDATA3,CLIPSTD=<CLIP standard>*;

*) CLIP standards: ETSIFSK (default), ETSIDTMF, BCMDMF, BCSDMF

● OPTISET

– EDITDIAL Y/N Edited dialing for Up0E terminals (Deleting of single numbers by using with the arrow key (positioning) and the “-” key; For starting the call, use the OK key);

● MLPP Multi-level precedence and preemption service;Special feature for the army (US);



4. Activation of the feature:

CHANGE-FEASU:TYPE=A,CM=CLIP&LEDSIGN;

● Generating VMWI

The feature is activated, when the SLMAC is used and the CLIP function for analoge phones is activated.

● Restriction

The MWI/Mailbox signalling with fluorescent lamp (150 V) is not supported !

● Special cases

The feature CLIP for analoge phones is activated. The analoge phone has the MWI display based on COMTEL. In this case the parameter DHPAR=LEDSIGN must be set in AMO SCSU (SPEC= SUFDIAL or SOD).


105

106


6.3 Integrated features without any AMO control

● Chained features for digitale terminals (Multiple feature chaining in REPDIAL)(US);e.g.: Pin activation code + PIN or LCR access code + dialing number;

● Pick up of a camped-on call via the Optiguide (US) (Pick-up camped-on call).

● Message Waiting LED (Mailbox-LED, Phone Mail/Xpression LED and Wait-Indicators for analoge phones) is stored after a Soft-Restart and a common control switch over;

● Improved RMX Timer Handling;


Documents

cap 07 EN4416EN20EN - Papagayo System · CODEW variants with dongle in HiPath 4000 V2.0 The HiPath 4000 V1.0 op erating mode is ... (Except "HIPATH AP VOICE COMPRESSION IP" where