cap 11 en4416en20en - papagayosystem.com.ve ver 2/chap 11...us features en4416en20en © 2004 siemens...

US features Siemens

US features

1 CorNet-VN (CorNet Virtual Networking). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.1 Feature description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.2 User interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.3 Service information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.4 Generating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.5 Relevant AMO: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2 US Government MLPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.1 Feature Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.2 Specific terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.3 User interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.3.1 Originating User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.3.2 Destination User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.3.2.1 Called MLPP subscriber is idle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.3.2.2 Called MLPP subscriber is busy (with camp on) . . . . . . . . . . . . . . . . . . . . . . . . . 92.3.2.3 Called MLPP subscriber busy (without camp on) . . . . . . . . . . . . . . . . . . . . . . . . 9

2.3.3 Invocation and operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.3.4 Announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.3.5 Precedence Call Diversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.3.6 Precedence Call Waiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.3.7 Call Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.3.8 Three Way Calling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.3.9 Defense Switched Network World Wide Numbering and Dialing Plan. . . . . . . . . . . 122.3.10 Calls in Queue to the Attendant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.4 Service information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.5 Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.5.1 Loadware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

EN4416EN20EN© 2004 Siemens AG

1

CorNet-VNSiemens

2

2.5.1.1 SIU - Loadware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.5.1.2 E1 CAS MUF DIUN2 Loadware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.5.1.3 T1 BOS MUF TMDNH Loadware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.5.1.4 TMOM2 Loadware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.5.1.5 SLMA24 Loadware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.5.2 Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.5.2.1 Global switch configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.5.2.2 General Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.5.2.3 General Administration of T1 MOS (example): . . . . . . . . . . . . . . . . . . . . . . . . . 152.5.2.4 General Administration of T1 BOS (example): . . . . . . . . . . . . . . . . . . . . . . . . . 162.5.2.5 Generation Example for E1 CAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.5.3 Calls in Queue to the Attendant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.5.3.1 Assignment of the MLPP call queues with AMO-VFGR . . . . . . . . . . . . . . . . . . 192.5.3.2 Assignment of the MLPP call queues on AC-Win-MQ Application . . . . . . . . . . 20

2.5.4 Ringing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.5.5 Assignment of the DSN information signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.5.5.1 Emergency Service GSCR 4.5.1.8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.5.6 NI2 Precedence Level IE (GSCR 3.7.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.5.7 DISC MSG Information Cause Values (GSCR 3.7.3) . . . . . . . . . . . . . . . . . . . . . . . 232.5.8 Signal Information Element (GSCR 3.7.4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.5.9 ANSI T1.619a and non-ANSI T1.619a Interaction (GSCR 3.7.6) . . . . . . . . . . . . . . 242.5.10 DSN Switch Outpulsing Format (GSCR 4.5.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

2.5.10.1 DSN Outpulsing (in/out dialing of P- and R-Digit) . . . . . . . . . . . . . . . . . . . . . . 242.5.11 Trunk Supervisory Preemption with E&M Wink (GSCR 5.3) . . . . . . . . . . . . . . . . . 252.5.12 Invocation and Operation (GSCR 3.8.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252.5.13 Call Transfer (GSCR 3.8.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252.5.14 Precedence Call Waiting (GSCR 3.8.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252.5.15 Call Hold (GSCR 3.8.4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252.5.16 Precedence Call Diversion (GSCR 3.3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262.5.17 Announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262.5.18 Call forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302.5.19 Further Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

2.5.19.1 Change the switch to aLaw. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302.5.19.2 Change the switch to uLaw. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

2.6 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31


CorNet-VN Siemens

1 CorNet-VN (CorNet Virtual Networking)

1.1 Feature description

CorNet Virtual Networking (CorNet-VN) is a Siemens developed and patented signaling proto-col whereby the networking capabilities of CorNet-N are supported over a public switched tele-phone network (PSTN) connection. This is done by passing the proprietary signaling elements of CorNet-N through the PSTN using the user-to-user signaling (UUS) capabilities of the public network carrier.

CorNet-VN is offered to U.S. customers as an alternative to conventional CorNet-N or CorNet-NQ trunks that require dedicated T1 facilities. CorNet-VN is not intended to replace CorNet-N or CorNet-NQ trunks, but rather augment them with a solution that is more cost effective in cer-tain customer environments. The typical situation where CorNet-VN is more cost effective than CorNet-N/NQ trunks is for inter-connecting distant locations that have low traffic volume where dedicated or leased-line facilities would be expensive and under utilized. CorNet-VN shall be supported across AT&T and Worldcom (formerly MCI) public telephone networks. Siemens "ROLMnet" is an example of an enterprise network that could realize a cost savings by using CorNet-VN.

AT&T or Worldcom (MCI) Network

CorNet-VN CorNet-VN

CorNet-VN

CorNet-VN ISDN PRI

CorNet-VN

CorNet-N

non- CorNet-VN

PBX

CorNet-N

HiPath 4000 V2.0

HiPath 3000

(Hicom 150E)

Hicom 300E V6.5

HiPath 4000 V2.0

Hicom 300H V1.0

HiPath 4000 V2.0

Hicom 300E V6.5

CorNet-NQ HiPath 4000

V1.0 or V2.0


3

CorNet-VNSiemens

4

Figure 1 illustrates a typical CorNet-VN network whereby CorNet-VN is used for long-haul con-nectivity through the PSTN. CorNet-N is used for short-haul connectivity between Siemens legacy enterprise switches (e.g., Hicom 300E V6.5, Hicom 300H V1.0 and Hicom 150E/HiPath 3000). CorNet-NQ is used for short-haul connectivity between other HiPath 4000 switches (e.g., HiPath 4000 V1.0 and V2.0). The figure shows a mix of switch types that are CorNet-VN capable as well as a non-CorNet-VN-capable switch that is connected to the PSTN using con-ventional ISDN-PRI.

1.2 User interface

CorNet-VN is based on CorNet-N, therefore the user has a limited CorNet-N user interface available.

1.3 Service information

The CorNet-VN feature is available with the HiPath 4000 version 2.0 and is intended for North American marktplace.

1.4 Generating

CorNet-VN will run on the TMDNH (Q2192-X, Function ID 3) card in HiPath 4000 V2.0 or on its replacement DIUN2U (Q2216-X, Function ID 6).

● How to configures the TMDNH / DIU2U board

configures the TMDNH board:ADD-BCSU: MTYPE=TMD, LTG=x, LTU=y, SLOT=z, PARTNO="Q2192-X", FCTID=3, LWVAR="K", HWYBDL=A;

configures the DIU2U board:ADD-BCSU: MTYPE=TMD, LTG=x, LTU=y, SLOT=z, PARTNO="Q2216-X", FCTID=6, LWVAR="K", HWYBDL=A;

● How to configures the CorNet-VN AT&T

The following commands are based on COPY-PRODE: TYPE=PVCD, PVCDNO=16 to load the US protocols into memory (default PVCDNO = 16). Then the associated PRODE tables for CVN1 and CVN2 are available.

configures the AT&T trunk:CHANGE-LWPAR: TYPE=TMD, TMDTYPE=TMDMOS, BLNO=3, OP-MODE=FRAMEESF&BISUB8ON&BDETON, CABLETYP=1, OESDISTH=30, OES-REQTH=4, SESDISTH=10, SESREQTH=10, ACKTIM=10, DLVTIM=300, OCTMAX=260, RETMAX=3, WINDOW=7, CRIDC=0288, NSFIV=1, NSFTSC=9, TTSC=4;


CorNet-VN Siemens

configures new device S1CVN with AT&T protocol:ADD-TDCSU: OPT=NEW, PEN=x-y-z-1, COTNO=99, COPNO=95, DPLN=1, ITR=0, LCOSV=1, LCOSD=1, CCT=" ", DESTNO=5, PROTVAR="CVN1", SEGMENT=1, DEDS-VC=NONE ,TRTBL=GDTR, SIDANI=N, ATNTYP=TIE, CBMATTR=NONE, TCHARG=N, SUPPRESS=0, TRACOUNT=31, SATCOUNT=MANY, NNO=1-1-501, ALARMNO=2, FIDX=1, CARRIER=1, ZONE=EMPTY, COTX=99, FWDX=1, CHIMAP=N, UUSCCX=16, UUSCCY=8, FNIDX=1, NWMUXTIM=10, CLASSMRK=EC&G711&G729OPT, TGRP=98, SRCHMODE=DSC, INS=Y, DEV=S1CVN, BCHAN=1&&23, BCNEG=N, BCGR=1, LW-PAR=3;

● How to configures the CorNet-VN MCI trunk

The following commands are based on COPY-PRODE: TYPE=PVCD, PVCDNO=16 to load the US protocols into memory (default PVCDNO = 16). Then the associated PRODE tables for CVN1 and CVN2 are available.

configures the MCI trunk:CHANGE-LWPAR: TYP=TMD, TMDTYP=TMDMOS, BLNO=4, OP-MODE=FRAMEESF&BISUB8ON&BDETON, CABLETYP=1, OESDISTH=30, OES-REQTH=4, SESDISTH=10, SESREQTH=10, ACKTIM=10, DLVTIM=300, OCTMAX=260, RETMAX=3, WINDOW=7, CRIDC=0222, NSFIV=1, NSFTSC=9, TTSC=4;

configures new device S1CVN with MCI protocol:ADD-TDCSU: OPT=NEW, PEN=x-y-z-1, COTNO=99, COPNO=95, DPLN=1, ITR=0, LCOSV=1, LCOSD=1, CCT=" ", DESTNO=5, PROTVAR="CVN2", SEGMENT=1, DEDS-VC=NONE ,TRTBL=GDTR, SIDANI=N, ATNTYP=TIE, CBMATTR=NONE, TCHARG=N, SUPPRESS=0, TRACOUNT=31, SATCOUNT=MANY, NNO=1-1-501, ALARMNO=2, FIDX=1, CARRIER=1, ZONE=EMPTY, COTX=99, FWDX=1, CHIMAP=N, UUSCCX=16, UUSCCY=8, FNIDX=1, NWMUXTIM=10, CLASSMRK=EC&G711&G729OPT, TGRP=98, SRCHMODE=DSC, INS=Y, DEV=S1CVN, BCHAN=1&&23, BCNEG=N, BCGR=1, LW-PAR=4;

● Activation / Deactivation of CorNet-VN

displays the number of contracted, assigned and free CVN trunks:DISP-CODEW;


5

CorNet-VNSiemens

6

1.5 Relevant AMO:

AMO Parameter Sprache/Language

Beschreibung/ Description

BCSU SACHNR d Baugruppen-Sachnummer: “Q2216-x” für DIU2U Baugruppe

“Q2192-x” für TMDNH Baugruppe

BCSU PARTNO e Board-Part number: “Q2216-x” for DIU2U Board

“Q2192-x” for TMDNH Board

LWPAR CRIDC d Carrier ID-Code:= 0288 für AT&T

= 222 für MCI

LWPAR CRIDC e Carrier ID-Code:= 0288 for AT&T

= 222 for MCI

LWPAR NFSIV d NFS ie Zugriffs-Code für VPN Call-Service:= 1 für AT&T und MCI

LWPAR NFSIV e NFS ie Access-Code for VPN Call-Service:= 1 for AT&T and MCI

LWPAR NFSTSC d NFS ie Code um ca-TSC zu aktivieren:= 9 für AT&T und MCI

LWPAR NFSTSC e NFS ie Code to activate ca-TSC:= 9 for AT&T and MCI

LWPAR TTSC d TSC-Timer:= 4 für AT&T und MCI

LWPAR TTSC e TSC-Timer:= 4 for AT&T and MCI

TDCSU PROTVAR d Protokollvariante:= CNV1 für AT&T= CNV2 für MCI

TDCSU PROTVAR e Protocol variant:= CNV1 for AT&T= CNV2 for MCI

TDCSU GER d Gerätetyp:= S1CVN für CorNet-VN Trunks

TDCSU DEV e Device type:= S1CVN for CorNet-VN Trunks


US Government MLPP Siemens

2 US Government MLPP

2.1 Feature Description

The Multi-Level Precedence and Preemption (MLPP) service provides prioritized call handling service. This service has two parts – precedence and preemption. Precedence involves as-signing a priority level to a call. Preemption involves the seizing of resources, which are in use by a call of a lower precedence, by a higher level precedence call in the absence of idle resourc-es

A subset of MLPP functionality is already in place for HiPath 4000 V1.0. Extensions are neces-sary to meet the specific requirements described in GSCR document “GSCR Draft March 01, 2003“ to satisfy the needs of the U.S. military in the global marketplace. The GSCR specifies support for different types of switches. The focus of this requirements document is PBX1 only.

This document describes new requirements only. Requirements already fulfilled with current implementation in HiPath 4000 V1.0 have been evaluated already before and are not scope of this document, but should be tested thereafter anyway for certification.

This feature will be implemented first as a patch-solution within HiPath4000 V1.0 followed by source solution in HiPath 4000 V2.0.

2.2 Specific terminology

Precedence is the priority associated with a call.

A precedence call is a call with precedence level higher than the lowest level of precedence.

MLPP Service Domain: An MLPP service domain consists of a set of MLPP subscribers (MLPP users) and the network and access resources that are in use by that set of MLPP sub-scribers at any given time. Connections and resources that are in use by MLPP subscribers may only be preempted by higher precedence calls from MLPP subscribers within the same domain. The service domain consist of a three octet field ranging from 00 00 00 to FF FF FF in hexadecimal. The DSN service domain is zero (0). Stations and trunks may have their own ser-vice domain and preemption can only occur in the same service domain.

Network: In this standard, "network" refers to all telecommunications equipment that has any part in processing a call or a supplementary service for the user referred to. It may include local exchanges, transit exchanges, and NT2s but does not include the ISDN terminal and is not lim-ited to the "public" network or any other particular set of equipment.

MLPP Call: An MLPP call is a call that has a precedence level established and is ether being setup or is setup. In Digital Subscriber Signaling System number 1 (DSS1: ISDN Q.931 sig-naling), an MLPP call is a call from an MLPP subscriber for which a setup has been sent but no DISCONNECT has been sent or received.

EN0000DE00EN© 2004 Siemens AG

7

8

US Government MLPPSiemens

Preemptable Circuit: A Preemptable circuit is a circuit that is active with or reserved for an MLPP call: (a) within the same domain as the preempting call and (b) with a lower precedence than the preempting call. A busy or reserved circuit for which a precedence level has not been specified is not a preemptable circuit.

Preemption initiating exchange: A preemption initiating exchange is the exchange that is congested (i.e. no idle circuits) and has received a preempting call setup.

2.3 User interface

2.3.1 Originating User

The user activates precedence calls by dialing a code on a per call basis.

1. If the originating user is not authorized for the dialed precedence level or for protected calls the call attempt will be rejected, the user will be connected to Unauthorized Precedence Announcement and on the Optiset the display message "nicht berechtigt"/"Not authorized".

2. If the called MLPP subscriber is busy by a call of the same or higher precedence level or by a call from a different service domain, the originating user will be connected to Blocked Precedence Announcement and on the Optiset the message "bitte wiederholen"/"Please try later" will be displayed.

3. If the called MLPP subscriber is idle, the calling station will receive precedence ringback tone and message "PRECEDENCE CALL" on the display while the called subscriber is ringing. After 4 seconds or when the called subscriber answers the call, the calling station will show the MLPP level in addition to the existing informations (called number, name), if administered.

4. If the called MLPP subscriber is busy by a call of the same or higher precedence level and call waiting for the called party is activated, the originating user will receive precedence ringback tone.

5. If the called MLPP subscriber is assigned as non-preemptible, the calling party will receive "geschuetzt/Protected" and Busy Not Equipped Announcement.

6. If the precedence call reaches an attendant queue, the user will be connected to Attendant Queue Announcement.

7. If the originating user originates a precedence call to a nonexistent number, the user will be connected to Vacant Code Announcement.

8. If technical problems make origination of a precedence call impossible, the user will be connected to Isolated Code Announcement.

All calls which are initiated without using a prefix, are MLPP Routine calls.



An attendant console gets the authorization for all MLPP levels (ROUTINE, PRTY, IMMED, FLASH, FLASHOV) with activation of MLPP in FEASU.

2.3.2 Destination User

2.3.2.1 Called MLPP subscriber is idle

If an MLPP subscriber is idle and is seized with a MLPP call, the display message at the called station will show the MLPP level in addition to the existing informations (calling number, name), if administrated. A special ringing rhythm for precedence calls (one for all levels) may be ad-ministered.

2.3.2.2 Called MLPP subscriber is busy (with camp on)

If an MLPP subscriber is busy by a call of the same or higher level or by a call from different service domain, during the camp-on phase the display will be the same as in ringing state and the user will hear precedence call waiting tone.

2.3.2.3 Called MLPP subscriber busy (without camp on)

At the moment of preemption the display will change from the information about "old" connec-tion to an information, that a precedence call is waiting: "Prioritaetsanruf wartet"/"Precedence call waiting", and the user will be connected to preemption notification tone. After the called par-ty has gone on-hook and rering starts, the display will be the same as in ringing state.

note: the attendant console is implicit protected against preemption by precedence calls.

2.3.3 Invocation and operation

● Initiating precedence calls - dialing access code + number

1. The access code for the precedence level and the dialed extension number appears as the user types them. While dialing no extra signalling will be done.

● Precedence call to an idle subscriber

1. On the display of the originating user the text "PRECEDENCE CALL" appears, 4 sec-onds later the MLPP level in addition to the existing information (calling number, name) will be displayed.

2. The destination user hears precedence call ring tone and the display shows the MLPP level in addition to the existing information (calling number, name).

● Preempting a call successfully


9

10


1. After dialing the access code and the extension number the text "PRECEDENCE CALL" appears on the display of the originating user. It also hears precedence ring-back tone.

2. The text "PRECEDENCE CALL WAITING" appears on the display of the destination user.

3. The destination user hears preemption notification tone. The original call of the desti-nation user will be disconnected.

4. The original partner of the destination user hears preemption notification tone. The call will be disconnected

5. When the destination user goes onhook, it will hear precedence call ringing immedi-ately.

● Unsuccessful precedence call attempt

1. After dialing the access code and the extension number

2. The originating user hears Blocked Precedence Announcement ("(Switch name and location.) Equal or higher precedence calls have prevented completion of your call. Please hang up and try again. This is a recording. (Switch name and location)".

● Initiating precedence call with unauthorized precedence level

1. After dialing the access code the text "NOT AUTHORIZED" appears on the display of the originating user.

2. the originating user hears Unauthorized Precedence level Announcement ("(Switch name and location.) The precedence used is not authorized for your line. Please use an authorized precedence or ask you attendant for assistance. This is a recording. (Switch name and location)")

2.3.4 Announcements

● Connecting to announcements when there are free announcement resources available

The party starts hearing the recorded message immediately. When the announcement fin-ishes, the party will be disconnected from the announcement.

● Connecting to announcements when there are no free announcements available

The user will hear a predefined tone while waiting for an announcement resource to be-come available. When the announcement resource becomes available, the party starts hearing the recorded message immediately. When the announcement finishes, the party will be disconnected from the announcement.



2.3.5 Precedence Call Diversion

● Diversion of unanswered precedence call

1. Originating user calls destination user with precedence call. Destination user is alert-ing with precedence ringing.

2. Destination user does not answer within a period of time.

3. Call is diverted to the diversion destination.

2.3.6 Precedence Call Waiting

● Camping on by a lower or equal precedence call or by a call from a different service domain

1. After dialing the access code and the extension number the text "PRECEDENCE CALL" appears on the display of the originating user.

2. The destination user hears precedence call waiting tone.

3. When the destination user goes onhook, it will hear precedence call ringing immedi-ately.

2.3.7 Call Forwarding

● Unconditional call forwarding at an idle station

1. Originating user dials the precedence level access code followed by the extension number of the destination party

2. The call is forwarded immediately to the call forwarding destination of the destination user. The rules of MLPP will apply to the call forwarding destination.

● Preemption at a busy station that has call forwarding activated

1. Originating user dials the precedence level access code followed by the extension number of the destination user. The destination user is busy. It also has unconditional call forwarding activated.

2. The call is not forwarded. The original call of the destination user is preempted.

● Call forward on no reply

1. Originating user dials the precedence level access code followed by the extension number of the destination user. The destination user starts hearing precedence ring-ing.

2. The destination user does not answer. The call is forwarded to a new party. The des-tination user stops ringing, the new party starts precedence ringing.


11

12


2.3.8 Three Way Calling

● Preemption of whole conference

When a conference is preempted because of the lack of conference resources, all of its members will receive Preemption Notification Tone. All of the members must go onhook as an acknowledgement.

2.3.9 Defense Switched Network World Wide Numbering and Dialing Plan

The administrator may configure Defense Switched Network World Wide Numbering and Dial-ing Plan for

● Access Digit, Precedence or Service Digit, Route Code, Area Code, Switch Code and Line Number

● Seven-Digit and Ten-Digit Dialing.

2.3.10 Calls in Queue to the Attendant

Realization of the calls in queue will be done by mapping each precedence level to a specific attendant queue. Each queue has its own key on the attendant console. The administrator has to assign the description text for the different precedence levels to the corresponding call queue keys on the attendant console. The attendant has the ability to get the calls with the higher pre-cedence first by hitting the key for the queue of the higher precedence first. This function will be available on AC-Win-MQ only.

2.4 Service information

● HiPath 4000 V1.0, patches see CR release document, compatibility, restrictions

● country specific information>

2.5 Generation

2.5.1 Loadware

2.5.1.1 SIU - Loadware

path on HiPath-HD: :PDS:APSP/LTG/LG63/PZJETONV & PZJETONW



2.5.1.2 E1 CAS MUF DIUN2 Loadware

AMO-TACSU: use COFIX=2 and DEV=TSEMUSW

path on HiPath-HD: :PDS:APSP/LTG/LGA2/PZFDCA20

/* display LW of DIU-N2 CAS (LW-Name=PZFDCA20):

STA-LIST:FILENAME=:PDS:APSP/LTG/LGA2/PZFDCA20,ADR=0,LEN=111,FORMAT=T;

2.5.1.3 T1 BOS MUF TMDNH Loadware

TMDNH LW for MLPP feature.

The LW supports the followings as the FDB5 describes.

1. MLPP circuit configuration.

2. Use both AB bits for Onhook and Offhook.

3. Send and detect Preemption signal.

4. Remote Make Busy (A=1, B=0).

AMO-TACSU: DEV=T1EMW

path on HiPath-HD: :PDS:APSP/LTG/LGA82/PZFDMTBK

/* LW about TMDNH BOS (LW-Name=PZFDMTBK):

STA-LIST:FILENAME=:PDS:APSP/LTG/LG82/PZFDMTBK,DR=0,LEN=222,FORMAT=T;

2.5.1.4 TMOM2 Loadware

path on HiPath-HD: :PDS:APSP/LTG/LG88/PZGMOM40

2.5.1.5 SLMA24 Loadware

path on HiPath-HD: :PDS:APSP/LTG/LG80/PZESLA20


13

14


2.5.2 Administration

Functions, which may not be activated for DSN switches are "protected calls" (PROT), "auto-matic connection after preemption".

2.5.2.1 Global switch configuration

This is the minimal configuration so that basic features (preemption, call forwarding, etc..) will work according to MUF requirements

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

CHANGE-FEASU:TYPE=D,CM=EMOVR&EMRLS;

● SD is the default service domain for the switch

CHANGE-ZAND:TYPE=MLPP,MAUTO=NO,MCAMP=NO,MTONE=NO,MLPPDISP="P0P1P2P3P4", MLPPDOM=SD;

CHANGE-ZANDE:TYPE=MLPP,MDIVAC=YES,DOMALLOC=YES,DOMCHECK=YES,MCIQTAC=YES, USMUDIV=YES,USMUXFER=YES,FWDPREC=YES,CAMPPREC=YES,PNTTGLE=YES,MCAUSE=YES,CWTPRECT=YES,CONFDSCT=YES;

CHANGE-ZAND:TYPE=CONFC,CODE=ULAW;

COPY-PRODE:PVCD,16;

● Configure CD1 .. CD5 as the access codes for precedence levels

ADD-WABE:CD=CD1,DAR=FLASHOV,CHECK=NO;ADD-WABE:CD=CD2,DAR=FLASH,CHECK=NO;ADD-WABE:CD=CD3,DAR=IMMED,CHECK=NO;ADD-WABE:CD=CD4,DAR=PRTY,CHECK=NO;ADD-WABE:CD=CD5,DAR=DSNR,CHECK=NO;

CHANGE-SDAT:STNO=nnnn,TYPE=ATTRIBUT,AATTR=FLASHOV,DATTR=MLPPS;

CHANGE-COT:COTNO=nnn,COTTYPE=COTADD,PAR=MLPR;CHANGE-COT:COTNO=nnn,COTTYPE=COTDEL,PAR=PROV&EODL&NMLT;



2.5.2.2 General Administration

Bild 2-1 MUF Network

2.5.2.3 General Administration of T1 MOS (example):

/* TMDNH for T1-MOS NI-2 Trunk */

CHANGE-LWPAR:TYPE=TMD,TMDTYPE=TMDMOS,BLNO=1,OPMODE=FRAMEESF&BISUB8ON&BDETON&NETUSER,CABLETYP=1,OES-DISTH=30,OESREQTH=4,SESDISTH=10,SESREQTH=10,ACKTIM=10, DLVTIM=300,OCTMAX=260,RETMAX=3,WIN-DOW=7;

ADD-BCSU:MTYPE=TMD,LTG=1,LTU=2,SLOT=79,PARTNO="Q2192/X",FCTID=2,LWVAR="K",HWYBDL=A;

TMDNHT1 MOS NI2NET

TMDNHT1 MOS NI2USER

DIU-N2E1 PSS1V2

DIU-N2E1 PSS1V2

TMDNHT1 BOS IWVT1 BOS MFV

TMDNHT1 BOS IWVT1 BOS MFV

DIU-N2E1CAS IWVE1 CAS MFV

DIU-N2E1 CAS IWVE1 CAS MFV

TYP=TMD, TMDTYP=TMDMOS, FCTID=2

TYP=TMD, TMDTYP=TMDMOS, FCTID=1DEVTYPE=TT,DEV=T1EMW,COP:BR64

DEVTYPE=TT,DEV=T1EMW,COP:MFV

PROT=NI2NET PROT=NI2

For more details see chapter in this document.

TYP=DIU

PROT=PSS1V2

TYP=DIU

DEVTYPE=TT2,DEV=QSEMUSW,COP:BR64

DEVTYPE=TT2,DEV=QSEMUSW,COP:DTMF


15

16


ADD-TDCSU:OPT=NEW,PEN=1-2-79-0,COTNO=100,COPNO=0,DPLN=0,PROTVAR=NI2,SEGMENT=1,ATNTYP=CO,SATCOUNT=MANY,ALARMNO=2,FIDX=1,COTX=120,FNIDX=1,NWMUXTIM=10,CLASSMRK=EC&G711&G729OPT,TGRP=80,INS=Y,DEV=S1COD,BCHAN=1&&23,BCNEG=N,BCGR=1,IGN=2,IID=14,LWPAR=2;

2.5.2.4 General Administration of T1 BOS (example):

/* TMDNH for T1-BOS EMW TIE-I */

/*To view the LW on TMDNH BOS (CAS) (LW-Name=PZFDMTBK):

STA-LIST:FILENAME=“:PDS:APSP/LTG/LG82/PZFDMTBK“,ADR=0,LEN=222,FORMAT=T;

CHANGE-LWPAR:TYPE=TMD,TMDTYPE=TMDBOS,BLNO=1,OPMODE=FRAMEESF&BISUB8ON&BDETON&NETUSER,CABLETYP=1,OESDISTH=30,OESREQTH=4,SESDISTH=10,SESREQTH=10;

ADD-BCSU:MTYPE=TMD,LTG=1,LTU=2,SLOT=49,PARTNO="Q2192-X",FCTID=1,LWVAR="K",LWPAR=1,FIDX=1,HWYBDL=A;

ADD-COSSU:NEWCOS=220,AVCE=TNOTCR&TA&CDRC,,,,,,,;

● This example is for the EMW-Protocol with pulse dial trunk group 242

● TIE code 542 for DP- Pulse Rotary Prot EMW

ADD-WABE:CD=542,DAR=TIE;

ADD-BUEND:TGRP=242,NAME="T1EMWDP",NO=2;

ADD-COP:COPNO=242,PAR=ANS&RLSA&BR64&TIM1&SDL&SFRM&NAAT,TRK=TA,DEV=INDEP,INFO="TT-EMW-DP";

ADD-COT:COTNO=242,PAR=RCL&NTON&ANS&IEVT,INFO="TT-EMW-DP";

ADD-TACSU:PEN=1-2-49-1,COTNO=242,COPNO=242,COS=220,LCOSV=1,LCOSD=1,TGRP=242,CCT="TTUS-IM",INS=Y,DEVTYPE=TT,DEV=T1EMW;

ADD-TACSU:PEN=1-2-49-2,COTNO=242,COPNO=242,COS=220,LCOSV=1,LCOSD=1,TGRP=242,CCT="TTUS-IM",INS=Y,DEVTYPE=TT,DEV=T1EMW;

ADD-RICHT:MODE=LRTENEW,LRTE=242,LSVC=VCE,NAME="T1EMW",TGRP=242,DNNO=1-1-501,ROUTATT=NO,PDNNO=0;;

ADD-LDAT:LROUTE=242,LSVC=VCE,LVAL=1,TGRP=242,ODR=2,LAUTH=1;

ADD-LDPLN:LCRCONF=LCRPATT,DIPLNUM=1,LDP="542"-"X",LROUTE=242,LAUTH=1;



● This example is for the EMW-Protocol with DTMF-Dial Trunk group 243

● TIE code 543 for DP- Pulse Rotary Prot EMW

ADD-WABE:CD=543,DAR=TIE;

ADD-BUEND:TGRP=243,NAME="T1EMWDTMF",NO=2;

ADD-COP:COPNO=243,PAR=ANS&DTMF&RLSA&DTM1&TIM1&IDP1&SDL&SFRM&NAAT&PDP1,TRK=TA,TOLL=TA,DEV=INDEP,INFO="TT-WINK-DTMF";

ADD-COT:COTNO=243,PAR=RCL&NTON&ANS&IEVT,INFO="TT-WINK-DTMF";

ADD-TACSU:PEN=1-2-49-5,COTNO=243,COPNO=243,LCOSV=1,LCOSD=1,TGRP=243,CCT="TTGUS-IM",INS=Y,DEVTYPE=TT,DEV=T1EMW;

ADD-TACSU:PEN=1-2-49-6,COTNO=243,COPNO=243,LCOSV=1,LCOSD=1,TGRP=243,CCT="TTGUS-IM",INS=Y,DEVTYPE=TT,DEV=T1EMW;

ADD-RICHT:MODE=LRTENEW,LRTE=243,LSVC=VCE,NAME="T1EMW",TGRP=243,DNNO=1-1-501,ROUTATT=NO,INFO="T1EMIMDTMF",PDNNO=0;


ADD-LDPLN:LCRCONF=LCRPATT,DIPLNUM=2,LDP="543"-"X",LAUTH=1;

2.5.2.5 Generation Example for E1 CAS

● Configuring DIU N2 as CAS for the MUF feature with FCTID=2

ADD-BCSU:MTYPE=DIU,LTG=1,LTU=2,SLOT=109,PARTNO="Q2196-X",LWVAR="0",LWPAR1=1,FIDX1=1,LWPAR2=1,FIDX2=1,FCTID=2,HWYBDL=A;

● Configuring tie codes: 546-DP, 547-MF, 548-DP, 549-MF and REFTA entry

ADD-WABE:CD=546&&549,DAR=TIE;

ADD-REFTA:TYPE=CIRCUIT,PEN=1-2-109-0,PRI=0;

● Configuring E+M Wink Dial Pulse protocol for trunk group 246 with tie access code 546

ADD-BUEND:TGRP=246,NAME="E1-EMW-DP",NO=4;

ADD-COP:COPNO=246,PAR=SDL&ANS&SFRM&RLSA&BR64&NAAT&TIM1&IDP1,INFO="E&M-WINK DP";


17

18


ADD-COT:COTNO=246,PAR=RCL&ANS&IEVT&MLPR&NTON,INFO="E&M-WINK DP";

ADD-TACSU:PEN=1-2-109-1,COTNO=246,COPNO=246,COS=220,LCOSV=1,LCOSD=1,TGRP=246,COFIDX=2,CCT="E1-DP",INS=Y,DEVTYPE=TT,DEV=TSEMUSW;

ADD-TACSU:PEN=1-2-109-2,COTNO=246,COPNO=246,COS=220,LCOSV=1,LCOSD=1,TGRP=246,COFIDX=2,CCT="E1-DP",INS=Y,DEVTYPE=TT,DEV=TSEMUSW;

ADD-RICHT:MODE=LRTENEW,LRTE=246,LSVC=VCE,NAME="E1EM DP",TGRP=246,DNNO=1-1-501,ROUTATT=NO,PDNNO=0;


ADD-LDPLN:LCRCONF=LCRPATT,DIPLNUM=0,LDP="546"-"X",LAUTH=1;

Configuring E+M Wink DTMF protocol for trunk group 247 with tie access code 547

ADD-BUEND:TGRP=247,NAME="E1-EMW-DTMF",NO=4;;

ADD-COP:COPNO=247,PAR=SDL&ANS&SFRM&RLSA&DTMF&DTM1&NAAT,INFO="E&M WINK DTMF";

● Addittion of new COP parameters for MLPP level and Preemption

CHANGE-COP:COPNO=247,COPTYPE=COPADD,PAR=PDIG&RDIG&PRMT;

ADD-COT:COTNO=247,PAR=RCL&NTON&ANS&IEVT&CEBC,INFO="E&M WINK DTMF";

ADD-TACSU:PEN=1-2-109-3,COTNO=247,COPNO=247,COS=220,LCOSV=1,LCOSD=1,TGRP=247,COFIDX=2,CCT="E1-DTMF",INS=Y,DEVTYPE=TT,DEV=TSEMUSW;

ADD-TACSU:PEN=1-2-109-4,COTNO=247,COPNO=247,COS=220,LCOSV=1,LCOSD=1,TGRP=247,COFIDX=2,CCT="E1-DTMF",INS=Y,DEVTYPE=TT,DEV=TSEMUSW;

ADD-RICHT:MODE=LRTENEW,LRTE=247,LSVC=VCE,NAME="E1 E&M-DTMF",TGRP=247,DNNO=1-1-501,ROUTATT=NO,PDNNO=0;;


ADD-LDPLN:LCRCONF=LCRPATT,DIPLNUM=0,LDP="547"-"X",LROUTE=247,LAUTH=1;



2.5.3 Calls in Queue to the Attendant

For the assignment of MLPP calls to the answer keys in the multiple queue mode use the keys SQ03-SQ06 since these keys are still unassigned.

The procedure CP_P_CQ_ CALL_PRIORITY (module cd030sa) determines call priority num-ber and priority level for queueing into 2q (a and m) or mq (q1 til q12). This procedure has been modified so that each MLPP level is assigned to the corresponding calltype. The new calltypes will override all other calltypes and no additional feature interactions will be considered, e.g. in case of recall of a MLPP call, the calltype is MLPP and not recall. NON-MLPP and routine calls are queued according to the AMO-VFGR setting (no change of processing)

note: for routine calls there is no explicit call queue.

2.5.3.1 Assignment of the MLPP call queues with AMO-VFGR

Example for an assignment of MLPP call queues with AMO-VFGR:

● Assign priority numbers to the new MLPP call types:

CHANGE-VFGR:TYPE=PRIOCALL,ATNDGR=3,MLPP1=3,MLPP2=4,MLPP3=5,MLPP4=6;

● Assign the priority numbers to the corresponding call queue keys:

CHANGE-VFGR:ATNDGR=3,TYPE=PRIOLEV,PRIONO=3,ANSKEY=SQ03,PRIOLEV=2;

● for MLPP calls with Flash_override level on key L3


● for MLPP calls with Flash level on key L4


● for MLPP calls with Immediate level on key L5


● for MLPP calls with Priority level on key L6


19

20


2.5.3.2 Assignment of the MLPP call queues on AC-Win-MQ Application

The assignment of the individual call types and calls based on their origin to the 12 queues is system-specific and is performed by HiPath administration. The label on each call queue key informs the user about the type of calls in the assigned queue. You can label the fields under the source buttons:

1. In the Options menu, select AC-Win Settings.

2. Click on the Queues tab

3. Click on the desired name field and enter a text for the keys F3-F6 (e.g. P1-P4).

2.5.4 Ringing

For anate the loadware has been changed:

The system will send a special data via the message LOAD_CIRC_DATA to identify the MUF at the initialization of the board. In the loadware side the better position to change is the most significant bit of the byte of COFIDX data (1 for MUF and 0 to not MUF situation). So, the system just need to add 0x80 (hex) to the COFIDX data in the LOAD_CIRC_DATA message to identify the MUF. The other bits of the COFIDX data can't be changed, because they carry the informa-tion of which coefficient set will be used.

For optiPoint use a countrycode of ROW (e.g.: 0 = BRD) and modify cadences by use of AMO-PTIME. Nothing to do for this in CP/DH for patch solution.

CHANGE-PTIME:TYPE=SLMA, RNGON0=2000,RNGOFF0=4000,RNGON61=1640,RNGOFF61=360, RNGON62=1640,RNGOFF62=360,RNGON63=1640,RNGOFF63=360;

2.5.5 Assignment of the DSN information signals

Selection of country specific SIU tone table for DSN:

CHANGE-ZAND:TYPE=TN,SIUC=V; DSN tone table for a-lawCHANGE-ZAND:TYPE=TN,SIUC=W; DSN tone table for u-law

ACTIVATE-USSU:UNIT=SIU;

assignment of CP tones to SIU tones already installed

In order to receive the US camp-on beeps the following ZAND parameter must be set

CHANGE-ZAND:TYPE=ALLDATA2,CAMPON=YES;



to activate DSN Precedence Call Waiting Tone and DSN Conference Disconnect Tone see Ab-schnitt 2.5.2.1, “Global switch configuration”

note:

DSN Call Waiting Tone for routine calls is 750ms single burst, only once

DSN Call waiting Tone for precedence calls is a 100ms double burst every 9.7 seconds

2.5.5.1 Emergency Service GSCR 4.5.1.8)

EINR-WABE:RNR=91,KZP=QUER,PRUEF=NEIN;

EINR-WABE:RNR=*3,KZP=FLASH,PRUEF=NEIN;

EINRICHTEN-RICHT:ART=LRTGNEU,LRTG=911,NAME="E911",BUNUM=229,ZKNNR=1-1-400,ROUTATT=NEIN,ROUTOPT=NEIN,REROUT=NEIN,EMCYRTT=JA;

EINRICHTEN-RICHT:ART=LRTGNEU,LRTG=912,NAME="MUF",BUNUM=229,ZKNNR=1-1-400, ROUTATT=NEIN,ROUTOPT=NEIN,REROUT=NEIN,EMCYRTT=NEIN;

/* E911 */L-LODR:LWR,98;

EINR-LODR:LWR=98,LWREL=ZIFFSEND,ZIFFERN=91; /* “DNA E911 Target“ */

EINR-LODR:LWR=98,LWREL=SENDCOMP;

EINRICHTEN-LODR:LWR=98,LWREL=ENDE;

EINRICHTEN-LODR:LWR=98,INFO="E911";

/* MUF*/L-LODR:LWR,99;

EINR-LODR:LWR=99,LWREL=ZIFFSEND,ZIFFERN=*3;


21

22


EINR-LODR:LWR=99,LWREL=ECHOFELD,FELD=2;

EINR-LODR:LWR=99,LWREL=SENDCOMP;

EINRICHTEN-LODR:LWR=99,LWREL=ENDE;

EINRICHTEN-LODR:LWR=99,INFO="MUF";

/* E911*/EINRICHTEN-LDAT:LRTG=911,LWERT=1,BUNUM=229,LWR=98,LBER=1,CARRI-ER=1,ZONE=LEER,LATTR=KEINE;

/*MUF*/EINRICHTEN-LDAT:LRTG=912,LWERT=1,BUNUM=229,LWR=99,LBER=1,CARRI-ER=1,ZONE=LEER,LATTR=RERTEINT;

/* E911 */EINRICHTEN-LDPLN:LWM=911-T,LRTG=911,LBER=1;

/* MUF*/ EINRICHTEN-LDPLN:LWM=911-X,LRTG=912,LBER=1;

2.5.6 NI2 Precedence Level IE (GSCR 3.7.2)

KOPIEREN-PRODE:PVCD,16;

AE-SBCSU:TLNNU=subscriber,ART=FBUS,SPROT=SBNIBRI,BASICSVC=SPRACHE;

/* NI-2 MLPP IE */

/*

By NT-2 NET Side AENDERN-PRODE:ART=VARTAB,PROTVAR=NI2NET,PD-NORM=PD13,PDA1=pd02;

*/

AENDERN-PRODE:ART=PD,PDNAME=PD13,TEIL=WELMAND,SET-NR=49,B19=16,B39=16;

AENDERN-PRODE:ART=PD,PDNAME=PD13,TEIL=WELNAME,CS=5,NR=65,B00=4C;

AENDERN-PRODE:ART=PD,PDNAME=PD13,TEIL=RESTP,PDBLOCK=WEL-HEX,NR=152,B00=41,B01=05;



AENDERN-PRODE:ART=PD,PDNAME=PD13,TEIL=VERW,ACTIVE=JA;

2.5.7 DISC MSG Information Cause Values (GSCR 3.7.3)

/* S0-BUS NI2 BRI */

AE-PRODE:ART=PD,PDNAME=PD07,TEIL=RESTP,PDBLOCK=CAUIDNT,NR=08,B00=08;


AE-PRODE:ART=PD,PDNAME=PD07,TEIL=RESTP,PDBLOCK=CAUIDNT,NR=46,B00=2E;

AE-PRODE:ART=PD,PDNAME=PD07,TEIL=RESTP,PDBLOCK=CAUNAME,NR=08,B00=08;


AE-PRODE:ART=PD,PDNAME=PD07,TEIL=RESTP,PDBLOCK=CAUNAME,NR=46,B00=2E;


/* S2-Trunk NI2 PRI */



AE-PRODE:ART=PD,PDNAME=PD13,TEIL=RESTP,PDBLOCK=CAUIDNT,NR=46,B00=2E;



AE-PRODE:ART=PD,PDNAME=PD13,TEIL=RESTP,PDBLOCK=CAUNAME,NR=46,B00=2E;


2.5.8 Signal Information Element (GSCR 3.7.4)

/* WELMAND FUER SIGNAL IE */

AENDERN-PRODE:ART=PD,PDNAME=PD13,TEIL=WELMAND,SETNR=14,B12=08;

AENDERN-PRODE:ART=PD,PDNAME=PD13,TEIL=WELMAND,SETNR=31,B12=08;

AENDERN-PRODE:ART=PD,PDNAME=PD13,TEIL=WELMAND,SETNR=49,B12=C8;

AENDERN-PRODE:ART=PD,PDNAME=PD13,TEIL=RESTP,PDBLOCK=WELHEX,NR=38, B00=34;


23

24


AENDERN-PRODE:ART=PD,PDNAME=PD13,TEIL=WELNAME,CS=0,NR=52,B00=13;


2.5.9 ANSI T1.619a and non-ANSI T1.619a Interaction (GSCR 3.7.6)

● NI-2 Trunk must be administered before. See Kapitel 2, “NI2 Precedence Level IE (GSCR 3.7.2)”

2.5.10 DSN Switch Outpulsing Format (GSCR 4.5.2)

Tabelle 2-1 DTMF Outpulsing Digit Format

Tabelle 2-2 MLPP Level (PDIG set)

Please note, that the feature does not work with Pulse Dialing and with COP PDIG alone (digits A-D are used). That means it works only with PDIG und RDIG!

The KZ are examples, other digits can be used.

2.5.10.1 DSN Outpulsing (in/out dialing of P- and R-Digit)

The feature can be activated by COP:

– PDIG (transport and analyzing of P-Digit)

Precedence Digit Route Digit* Area Code Switch Code Line Number

(P) (x) (KXX) KXX XXXX

KZ Level KZP 1st Digit*

* Column is valid if both COP PDIG and RDIG are set (see below).

1st Digit**

** Column is valid if only PDIG is set.

Bemerkung

- none - -

411 Routine 4 -

412 Priority 3 D Number D = 0FH/15T

413 Immediate 2 C Number C = 0EH/14T

414 Flash 1 B Number B = 0DH/13T

415 Flash over 0 A Number A = 0CH/12T



– RDIG (transport and analyzing of R-Digit)

Example:

/* Erweiterung fuer MLPP Level und Preemption neuer COP

AE-COP:COPNU=246,COPART=COPZU,COPPAR=PDIG&RDIG&PRMT;

2.5.11 Trunk Supervisory Preemption with E&M Wink (GSCR 5.3)

● T1/E1 CAS must be administrated before. See Kapitel 2, “DSN Switch Outpulsing Format (GSCR 4.5.2)”

The feature can be activated by COP: PRMT and COT: MLPR.

Example:/* Erweiterung fuer MLPP Level und Preemption neuer COP

AE-COP:COPNU=246,COPART=COPZU,COPPAR=PDIG&RDIG&PRMT;AE-COT:COTNU=246,COTART=COTZU,COTPAR=MLPR;

2.5.12 Invocation and Operation (GSCR 3.8.1)

/* For each party (digite, anate, funky) the max. allowed precedence level and the service do-main is to be configured.

TLNNR is the party extension number, PRECLEV is the max. allowed level, SD is the service domain */

AENDERN-SDAT:TLNNU=TLNNR,TYP=MERKMAL,EMERK=PRECLEV; AENDERN-SDAT:TLNNU=TLNNR,TYP=DATEN1,SVCDOM=SD;

2.5.13 Call Transfer (GSCR 3.8.1)

See Abschnitt 2.5.2.1, “Global switch configuration”

2.5.14 Precedence Call Waiting (GSCR 3.8.1)


2.5.15 Call Hold (GSCR 3.8.4)



25

26


2.5.16 Precedence Call Diversion (GSCR 3.3)


2.5.17 Announcements

1. Synchronized announcements, as a feature, has to be enabled on the system (AMO FEA-SU, ZAND)

AENDERN-FEASU:TYP=FREI,LM=SYNCANN;

AENDERN-ZAND:TYP=DATEN2,ANSES=JA;

2. The different kind of synchronized announcements has to be configured (AMO SYNCA). For each type of announcement a number has to be assigned, in the configuration below this assignment is as follows:

This assigned number will be used when configuring the TMOM card for the announcement.

/* Blocked precedence announcement */

EINRICHTEN-SYNCA:TABTYP=ANTT,ANSTYP=3,ANSNAME="MUF-BPA",ANSTATUS=EIN,BETRART=STASTO,VERZOEZT=1;

EINRICHTEN-SYNCA:TABTYP=AMVBZ,ANSGRUND=ABGEWPRC,VBZ=0&&15,ANST-YP=3;

EINRICHTEN-SYNCA:TABTYP=AMTON,ANSGRUND=ABGEWPRC,VORABTON=LCRET,RUECKTON=LCRET;

/* Unauthorized precedence announcement */

Announcement Assigned number(ANSTYP)

BPA - Blocked Precedence Announcement 3

UPA - Unauthorized Precedence Announcement 4

VCA - Vacant Code Announcement 5

ICA - Isolated Code Announcement 6

BNEA - Busy Not Equipped Announcement 8

ATQA - Attendant Queue Announcement 9



EINRICHTEN-SYNCA:TABTYP=ANTT,ANSTYP=4,ANSNAME="MUF-UPA",ANSTATUS=EIN,BETRART=STASTO,VERZOEZT=1;

EINRICHTEN-SYNCA:TABTYP=AMVBZ,ANSGRUND=NAUTHPRC,VBZ=0&&15,ANST-YP=4;

EINRICHTEN-SYNCA:TABTYP=AMTON,ANSGRUND=NAUTHPRC,VORABTON=LCRET,RUECKTON=LCRET;

/* Vacant Code Announcement */

EINRICHTEN-SYNCA:TABTYP=ANTT,ANSTYP=5,ANSNAME="MUF-VCA",ANSTA-TUS=EIN,BETRART=STASTO,VERZOEZT=1;

EINRICHTEN-SYNCA:TABTYP=AMVBZ,ANSGRUND=TLNNPR,VBZ=0&&15,ANSTYP=5;

EINRICHTEN-SYNCA:TABTYP=AMTON,ANSGRUND=TLNNPR,VORAB-TON=LCRET,RUECKTON=LCRET;

/* Isolated Code Announcement */

EINRICHTEN-SYNCA:TABTYP=ANTT,ANSTYP=6,ANSNAME="MUF-ICA",ANSTATUS=EIN,BETRART=STASTO,VERZOEZT=1;

EINRICHTEN-SYNCA:TABTYP=AMVBZ,ANSGRUND=TLNDEF,VBZ=0&&15,ANSTYP=6;

EINRICHTEN-SYNCA:TABTYP=AMTON,ANSGRUND=TLNDEF,VORAB-TON=LCRET,RUECKTON=LCRET;

/* Busy Not Equipped Announcement */

EINRICHTEN-SYNCA:TABTYP=ANTT,ANSTYP=8,ANSNAME="MUF-BNEA",ANSTA-TUS=EIN,BETRART=STASTO,VERZOEZT=1;

EINRICHTEN-SYNCA:TABTYP=AMVBZ,ANSGRUND=TRENNERL,VBZ=0&&15,ANST-YP=8;

EINRICHTEN-SYNCA:TABTYP=AMTON,ANSGRUND=TRENNERL,VORABTON=LCRET,RUECKTON=LCRET;

/* Attendant Queue Announcement */


27

28


EINRICHTEN-SYNCA:TABTYP=ANTT,ANSTYP=9,ANSNAME="MUF-ATQA",ANSTA-TUS=EIN,BETRART=STASTO,VERZOEZT=1;

EINRICHTEN-SYNCA:TABTYP=AMVBZ,ANSGRUND=VP,VBZ=0&&15,ANSTYP=9;

EINRICHTEN-SYNCA:TABTYP=AMTON,ANSGRUND=VP,VORABTON=AWVPL,RUECKTON=AWVPL;

3. For attendant queue announcement the delay time before starting the announcement for the call in the queue is set to 1 second (AMO CTIME), and the announcement has to be enabled for the Attendant Queue (AMO VFGR)

AE-CTIME:ARTSWU=CPTIME1,ATDLYANS=1;

AE-VFGR:VFGRU=3,TYP=ALLG,ANSYN=JA; /* Enable announcements for VFGRU=3 */

AENDERN-ZAND:TYP=VF,ISYNCVF=JA;

4. TMOM cards has to be configured for each announcement. For the TMOM cards a new COT (1) and a new COP (6) is to be introduced.

EINRICHTEN-COT:COTNU=1,COTPAR=MVNA;EINRICHTEN-COP:COPNU=6,COPPAR=BELQ&LUEW;

Each TMOM port provides sound for one type of announcement. In AMO TSCSU the type of the announcement (ANSTYP) is to be specified.

/* 1-2-103-0 provides BPA (ANSTYP=3) */

EINRICHTEN-TSCSU:LAGE=1-2-103-0,COTNR=1,WABE=0,VBZ=0,SATZNR="",ALARM-NR=0,SRCGRP=1,INBETR=J,GER=ANSES,COPNR=6,UEBERWZ=UEBERW5,QUITZ=BELQUIT2, ANST-YP=3;

/* 1-2-103-1 provides UPA (ANSTYP=4) */




/* 1-2-103-2 provides VCA (ANSTYP=5) */


/* 1-2-103-3 provides ICA (ANSTYP=6) */


/* 1-2-55-0 provides BNEA (ANSTYP=8) */


/* 1-2-55-1 provides ATQA (ANSTYP=9) */


More TMOM ports can be configured for the different announcements the same way.

5. Announcements have to be enabled for subscribers (AMO COS):

AENDERN-COSSU:TYP=COS,COS=23,ESBER=ANSYN; /* Digite COS=23*/


29

30


AENDERN-COSSU:TYP=COS,COS=2,ESBER=ANSYN; /* Anate COS=2*/

AENDERN-COSSU:TYP=COS,COS=24,ESBER=ANSYN; /* Funky COS=24*/

6. Announcements have to be enabled for trunks (AMO COT):

AENDERN-COT:COTNU=220,COTART=COTZU,COTPAR=MVNA&WANS; /* Analog trunk COT=220*/

AENDERN-COT:COTNU=221,COTART=COTZU,COTPAR=MVNA&WANS; /* Digital trunk COT=221*/

2.5.18 Call forwarding

● To configure call forwarding work according to the US Military requirements:See Abschnitt 2.5.2.1, “Global switch configuration”

● To prevent call forwarding of precedence calls to voice mail:

/* xxx is the richtung/route to voice mail. */CHANGE-RICHT:LRTE=xxx,NOPRCFWD=YES;

2.5.19 Further Information

To get the desired functionality the following needs to be done:

2.5.19.1 Change the switch to aLaw

CHANGE-ZAND:TYPE=CONFC,CODE=ALAW;/* coding for conf stmi etc.

CHANGE-ZAND:TYPE=ALLDATA,CNTRYCD=0;/* slma attenuation

CHANGE-ZAND:TYPE=TN,SIUC=0V,DTR=0;/* siu to aLaw

CHANGE-ZAND:TYPE=SIUXPER,LEVDTMF=0;/* dtmf to aLaw

CHANGE-ZAND:TYPE=OPTISET,ACOUSTID=EUROPE;/* optiset and optipoint europe

CHANGE-ZAND:TYPE=ATND,ACCNTRY=0;/* AC-Win-MQ to aLaw

EXEC-UPDAT:BP,ALL;

EXEC-REST:UNIT,BP,RELOAD;



2.5.19.2 Change the switch to uLaw

CHANGE-ZAND:TYPE=CONFC,CODE=ULAW;/* Coding for conf stmi etc.

CHANGE-ZAND:TYPE=ALLDATA,CNTRYCD=K;/* slma attenuation

CHANGE-ZAND:TYPE=TN,SIUC=0W,DTR=0K;/* siu set to DSN uLaw

CHANGE-ZAND:TYPE=SIUXPER,LEVDTMF=1;/* DTMF set to uLaw

CHANGE-ZAND:TYPE=OPTISET,ACOUSTID=USA;/* Optiset and Optipoint to usa

CHANGE-ZAND:TYPE=ATND,ACCNTRY=1;/* AC-Win-MQ to uLaw

EXEC-UPDAT:BP,ALL;

EXEC-REST:UNIT,BP,RELOAD;

2.6 Relevant AMOs

<

● AMO table (contains relevant AMOs with all new/changed parameters

Example:



COP COPPAR d Parameterwerte für eine Class of ParameterWert RDIG: 1./2.Ziffer wird als MLPP RouteCodeDigit

behandelt

PAR e Parameter to be enteredvalue RDIG: 1st/2nd Digit handled as a MLPP Route

Code Digit

COPPAR d Parameterwerte für eine Class of ParameterWert PDIG: 1. Ziffer wird als MLPP Precedence Digit be-

handelt

PAR e Parameter to be enteredvalue PDIG: 1st Digit is handled as a MLPP Precedence

Digit

COPPAR d Parameterwerte für eine Class of ParameterWert PRMT: Leitung mit Preemption Signalisierung


31

32


PAR e Parameter to be enteredvalue PRMT: Line with preemption signalling

PTIME GER d GerätetypWert QSEMUSW: dopp.ger. quersatz (wink start/usa)

DEV e device typevalue TSEMUSW: bothway tie trunk cct (e&m/wink start/

us)

RICHT KPRCAUL d Keine Precedence Calls umlenkenWird dieser Schalter gesetzt, so wird eine Umlenkung

von Precedence Calls blockiert.Wert JA: Feature aktivieren

Wert NEIN: Feature deaktivieren

NOPRCF-WD

e No Precedence Call forwardingAD: If this switch is set, call forwarding for precedence

calls will be locked.value YES: activate feature

value NO: deactivate feature

SDAT SVCDOM d MLPP Service Domain

SVCDOM e MLPP Service Domain

DELSVCDM d Löschen der MLPP Service Domain

DELSVCDM e Delete MLPP Service Domain

SYNCA ANSGRUND d AnsagegrundWert ABGEWPRC: Ansage bei abgewiesenem Prece-

dence CallWert NAUTHPRC: Ansage bei keiner Precedence Call -

BerechtigungWert TLNNPR: Ansage bei nicht vorhandenem Teilneh-

merWert TLNDEF: Ansage bei defektem TeilnehmerWert RESMNGL: Ansage bei Resourcenmangel

Wert TRENNERL: Ansage nicht trennbarem TeilnehmerWert VP: Ansage des Vermittlungsplatz





ANREASON e announcement reasonValue BLOCKPR: Blocked Precedence Announcement

Value UNAUTHPR: Unauthorized Precedence An-nouncement

Value VACCODE: Vacant Code AnnouncementValue ISOLCODE: Isolated Code Announcement

Value PRACCLIM: Precedence Access Limitation An-nouncement

Value BUSYNEQU: Busy Not Equipped AnnouncementValue ATTDQUE: Attendant Queue Announcement

TACSU SVCDOM d MLPP Service Domain




TDCSU SVCDOM d MLPP Service Domain




UCSU KONVLAW d Dieser MLPP bezogene Parameter bestimmt, ob auf der NCUI-Baugruppe eine Konvertierung der Dämpfungsart

(A-Law <-> Mu-Law) stattfinden soll.

CONVLAW e This MLPP related parameter defines, if the type of at-tenuation should be converted (A-Law <-> Mu-Law) by

means of the NCUI board

VFGR MLPP1 d MLPP Flash override

MLPP1 e MLPP Flash override

MLPP2 d MLPP Flash

MLPP2 e MLPP Flash

MLPP3 d MLPP Immediate

MLPP3 e MLPP Immediate

MLPP4 d MLPP Priority

MLPP5 e MLPP Priority

WABE KZP d KennzahlpunktWert DSNR: MLPP DSN-Routine




33

34


DAR e digit analysis resultValue DSNR: MLPP DSN Routine

ZAND SIU d Auswahl der länderspezifischen SIU-Tontabelle

SIUC e Selection of country-specific SIU tone table

CPTON d Vermittlungstechnischer Ton

CP e Call processing tone

ZANDE MABWVPL d Kundenspezifischer Parameter zur Weiterschaltung der MLPP Anrufe bei NO ANSWER oder BUSY der Zielsta-

tion zum Vermittlungsplatz.

MDIVAC e Customer specific parameter for diversion of incoming MLPP calls to attendant console (AC) for NO ANSWER

or BUSY of destination.

DOMALLOC d Einem Nicht-MLPP-Ruf wird eine Service Domain zugeordnet (eventuell wird die Funktion des COT:NMLT ausser Kraft gesetzt). Der Schalter wirkt nur in Verbind-

ung mit dem gesetzten FEASU-Schalter MLPP. Ist dieser Schalter nicht gesetzt, bleiben Nicht-MLPP-Rufe

ohne Service Domain. DB-Initialisierung: nein

DOMALLOC e An individual service domain is assigned to a non-MLPP call (and over-writes the function of COT:NMLT eventu-

ally). This switch is only valid with the FEASU switch MLPP. If this switch is not set a non-MLPP call will stay

without a service domain. DB-Initialization: no

DOMCHECK d Trennen ist nur innerhalb der gleichen Service Domain erlaubt. Der Schalter wirkt nur in Verbindung mit dem gesetzten FEASU-Schalter MLPP. Ist dieser Schalter

nicht gesetzt, kann unabhaengig von der Service Domain getrennt werden. DB-Initialisierung: nein

DOMCHECK e Preemption is allowed only within the same service do-main. This switch is only valid with the FEASU switch

MLPP. If this switch is not set preemption is allowed in-dependent of the service domain. DB-Initialization: no

MAROZVF d Bei gesetztem Schalter wird jedem MLPP Level am Ver-mittlungsplatz eine eigener Anrufordner zugeteilt. Ist

dieser Schalter nicht gesetzt, wird die bisherige Funk-tionalitaet verwendet. DB-Initialisierung: nein





MCIQTAC e If this switch is set every MLPP level gets an own queue at the Attendant Console. If this switch is not set the old

functionality is provided. DB-Initialization: no

USMUAUL d Precedence Calls werden nach den MUF-Regeln umgeleitet. Ist dieser Schalter nicht gesetzt, wird die

bisherige Funktionalitaet verwendet. DB-Initialisierung: nein

USMUDIV e Precedence calls will be diverted on MUF rules. If this switch is not set the old functionality is provided DB-Ini-

tialization: no

USMUXFER d Precedence Level werden nach den MUF - Regeln aktualisiert . Ist dieser Schalter nicht gesetzt, werden

die Precedence Levels nach den MLPP-Regeln aktual-isiert. DB-Initialisierung: nein

USMUXFER e Precedence levels will be updated on MUF rules. If this switch is not set the precedence levels will be updated

on MLPP rules. DB-Initialization: no

UMLPREC d Precedence Calls werden weitergeleitet. Ist dieser Schalter nicht gesetzt, werden Precedence Calls nicht

weitergeleitet. DB-Initialisierung: nein

FWDPREC e Precedence calls will be forwarded. If this switch is not set precedence calls will not be forwarded. DB-Initializa-

tion: no

ANKLPREC d Hoeherranginge kommende Precedence Calls in der gleichen Service Domain trennen alle existierenden Anrufe (auch wenn beim Anrufer Zweitanruf aktiviert ist). Ist dieser Schalter nicht gesetzt, werden Prece-

dence Calls nicht weitergeleitet. DB-Initialisierung: nein

CAMPPREC e Higher precedence incoming calls from the same ser-vice domain will preempt all existing calls (even if call waiting is activated at the called party). If this switch is not set all incoming calls will camp on to a busy called

party regardless of the service domains and precedence levels. DB-Initialization: no

PATONMAK d Wird zu einem getrennten und gehaltenen Gespraech-spartner zurueckgemakelt, wird dies durch einen Ton

signalisiert. Ist dieser Schalter nicht gesetzt, wird dieser Ton nicht erzeugt. DB-Initialisierung: nein




35

36


PNTTGLE e A signalling tone is done when toggling back to a pre-empted held partner. If this switch is not set there will be

no signalling tone. DB-Initialization: no

MCAUSE d Die MUF-Regeln kommen zur Anwendung.Ist dieser Schalter nicht gesetzt, wird die bisherige Funktionalitaet

verwendet. DB-Initialisierung: nein

MCAUSE e MUF rules are applying.If this switch is not set the old functionality is provided. DB-Initialization: no

CWTPRECT d Im Falle von Precedence Calls wird ein spezieller Ank-lopf-Ton verwendet. Ist dieser Schalter nicht gesetzt,

wird die bisherige Funktionalitaet verwendet. DB-Initial-isierung: nein

CWTPRECT e In case of a precedence call a special call waiting tone is applied. If this switch is not set the old functionality is

provided. DB-Initialization: no

CONFDSCT d Im Falle von Precedence Calls wird ein spezieller Kon-ferenz-Ende-Ton verwendet. Ist dieser Schalter nicht gesetzt, wird die bisherige Funktionalitaet verwendet.

DB-Initialisierung: nein

CONFDSCT e In case of a precedence call a special conference dis-connect tone is applied. If this switch is not set the old

functionality is provided. DB-Initialization: no




cap 11 en4416en20en - papagayosystem.com.ve ver 2/chap 11...us features en4416en20en © 2004 siemens...

Documents