This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
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.
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).
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.
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.
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.
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).
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.
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.
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.
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:
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.
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).
See Abschnitt 2.5.2.1, “Global switch configuration”
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.
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.
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
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