Lucent Technologies Whats New In DEFINITY Enterprise Communications Server Release 8.2 Manual

							What’s New in DEFINITY ECS
Release 8.2 Job Aid  555-233-754  Issue 1
April 2000
Networking Enhancements 
145 Networking - ISDN Private 
2
Figure 9. Basic QSIG-VALU Call Coverage Scenario
QSIG-VALU Call Coverage will enhance the operations for the users, similar to 
DCS Call Coverage, in the following ways:
1.Principal’s coverage path and criteria will be used to re-direct the call to 
QSIG-VALU coverage points. 
2. If the QSIG-VALU coverage point is not available, and the call can be 
redirected to the subsequent coverage point based on the Principal’s 
coverage path, the call to the coverage point is disconnected and the 
subsequent coverage point is alerted.
3. Coverage Point will be alerted with distinctive ringing. 
4. Display equipped Coverage point will see the display as:
or, when Calling Party’s name and  numb er are not availab le
,
NOTE:
  values are:  “b” (for Busy/Active), “c” (for Cover all),  “d” (for Don’t 
answer), and “s” (for Send All Calls).
Calling Party
DEFINITY
Principal
DEFINITYTRANSIT
QSIG DEFINITY
  PBX  A
(Called Party)
Coverage Point
(Redirected-to Party
  PBX  B  PBX  CQSIGQSIG-VALU QSIG-VALUTRANSIT
a=                                       
       Calling  Party’s Numb er                              Princ ip al’s Numb er OR
                                                                           Inc oming  Trunk Group ’s Name
a=  < Incoming Trunk Group’s Name>                                                                               
						

							What’s New in DEFINITY ECS
Release 8.2 Job Aid  555-233-754  Issue 1
April 2000
Networking Enhancements 
146 Networking - ISDN Private 
2
5. Principal user will be able to bridge on to the call while the call is routed to 
QSIG-VALU coverage points and after the call is answered by the coverage 
point.
6. Calling party will hear a coverage redirection tone before the call is routed 
to the 1st coverage point if the caller is on the same DEFINITY PBX as the 
Principal, or if the incoming call received over a DCS or QSIG network 
provides an indication that the caller is provided with a ring pattern 
“internal” (DALERT or MSI_DALERT indicating type of originator as 
internal).
7. Calling party’s display will see the reason code “Cover” (for Coverage).
8. After the call is answered by the covering user, QSIG Path Replacement 
will be initiated, if the Principal user’s Simulated Bridge Appearance (SBA) 
is not maintained, to provide path optimization. If the Principal use ’s SBA is 
maintained, then a partial path replacement is possible between either the 
Calling user’s PBX and the Principal user’s PBX, or the Covering user’s 
PBX and the Principal user’s PBX.
Administration
The QSIG-VALU Call Coverage feature will require the following administration:
1. Option “Value-Added Lucent (VALU)” shall be Enabled on System-
parameters customer-options form
2. The field QSIG Value-Added Lucent shall be selected as y and 
Supplementary Service Protocol Option shall be selected as B 
on a Trunk Group form to send QSIG-VALU Call Coverage MSI information 
to a remote switch in association with a call routing on that trunk group.
When a call is routed to a remote switch using QSIG-VALU Call Coverage, it will 
have higher precedence than the CCRON feature. Also, the signaling for this 
feature is built on top of QSIG Call Diversion/Forwarding supplementary service, 
so when a call is redirected to a remote switch using QSIG-VALU Call Coverage, 
the Principal User’s switch will act as a Rerouting PBX (i.e. Call Diversion/
Forwarding by forward switching). 
QSIG CAS Enhancement
The following enhancements to the QSIG Centralized Attendant Service (CAS) 
have been added:
nAttendant Display of Class of Restrictions (COR)
nAttendant Return of Call
nDisplay Enhancements
nPriority Queue
nRLT Emulation via PRI 
						

							What’s New in DEFINITY ECS
Release 8.2 Job Aid  555-233-754  Issue 1
April 2000
Networking Enhancements 
147 Networking - ISDN Private 
2
These enhancements require the administration of existing fields as follows:
nThe system-parameters customer-option form must be administered 
with option V8 or later for field G3 version
nThe system-parameters customer-option form must be administered 
with option y(es) for field ISDN PRI, or it must be administered with 
option y(es) for field ISDN-BRI trunks.
nThe system-parameters customer-options form must be administered 
with option y(es) for field Basic Supplementary Service?.
nThe system-parameters customer-options form must be administered 
with option y(es) for field Supplementary Services with 
Rerouting?
Attendant Display of COR
Currently, while on a call with a user on the main PBX, the attendant can press a 
COR Display button and obtain a display that tells the COR of the user.  The 
attendant can then use this information to decide if it is acceptable to transfer this 
user to a desired destination.  QSIG CAS Attendant Display of COR allows the 
same feature to function in the same manner if the other user is on the branch 
PBX and the attendant and the user are connected via QSIG ISDN trunks.  
QSIG CAS Attendant Display of COR uses QSIG MSI messages.  QSIG 
Manufacturer Specific Information (MSI) envelopes exchange QSIG private 
networking Information Elements (IEs) among nodes of a QSIG network.  MSI 
envelopes are designed to transit (i.e., tandem) through other vendors QSIG 
nodes, even though the data within is meaningless to them.  This  adds VALU  to 
Lucent nodes within a multi-vendor network.
Attendant Return of Call
If an attendant transfers a call and that call goes unanswered after an 
administrable amount of time, the call is returned to the attendant.  For a call that 
originated at the main, the call first attempts to go to the same attendant who 
originally handled it.  If that attendant is unavailable, then the call goes to the 
attendant group, where is it extended to the next available attendant.  For a call 
that originally came into the attendant from a branch over RLT, the return call 
would go to the attendant group.  CAS Attendant Return Call allows attendant 
return call to function for calls that come into the attendant from a branch over 
ISDN trunks in the same manner as calls that come directly to or originate at the 
main.  (There is also a display enhancement for return calls from a QSIG CAS 
branch, which is described in the CAS Display Enhancement section to follow.) 
						

							What’s New in DEFINITY ECS
Release 8.2 Job Aid  555-233-754  Issue 1
April 2000
Networking Enhancements 
148 Networking - ISDN Private 
2
Display Enhancements
Release Link Trunks (RLT) are limited in the amount of information that can be 
passed and displayed to the attendant.  CAS Display Enhancements are possible 
by replacing RLT with QSIG ISDN trunks.  Display enhancements are achieved by 
using QSIG MSI messages.  Display enhancements for calls coming into the 
attendant from a branch are:  
nFor an incoming LDN call, LDN name or number is shown
nFor a 0 out of Audix call, a reason code and called number are shown
nFor return calls, the called name is shown
Priority Queue
On the console-parameters form, customers can administer the priorities of 
incoming attendant calls that must wait in the Attendant Priority Queue because 
no attendant is immediately available.  Previously, with RLT CAS, all calls 
incoming to the attendant from a branch over RLT trunks were assigned the 
priority administered to Tie Trunk Calls.  Now, using QSIG ISDN trunk between 
the branch and main, more information can be passed to the main PBX using 
QSIG MSI messages.  This extra information enables calls coming in from a QSIG 
CAS branch to be placed in their appropriate place in the queue, as if the call 
came directly into the main.
RLT Emulation via PRI
Previously, Release Link Trunks were required in a Centralized Attendant Service.  
The purpose of the RLT is to route calls from the branch PBX to main PBX, and to 
provide trunk optimization in the case that the attendant subsequently transfers 
the call.  Today, the same effects can be achieved by using only ISDN QSIG 
trunks.  CAS RLT Emulation via PRI allows customers to set up a Centralized 
Attendant Service using solely ISDN QSIG trunks, and no RLT are needed.  Using 
QSIG Path Replacement, trunk optimization of QSIG trunks is possible.
Centralized Voice Mail Via Mode Code
You can use a single voice mail system to support multiple DEFINITY and Merlin 
Legend/Magix systems in a network via mode code. This capability is available 
for:
nDEFINITY ECS R8
nPrologix R3
nBCS Issue 6
nMerlin Legend R6.1
nMerlin Magix 1.0 
						

							What’s New in DEFINITY ECS
Release 8.2 Job Aid  555-233-754  Issue 1
April 2000
Networking Enhancements 
149 Networking - ISDN Private 
2
NOTE:
DEFINITY One and Guestworks are not supported.
Voice mail systems that support these connections are:
nIntuity AUDIX R4.4 or higher running on a MAP5, with up to 18 ports
nOctel 100, with up to 16 ports
Configuration requirements
Centralized voice mail via mode code requires the following:
nA DEFINITY ECS switch as the hub of the voice mail network, with the 
voice mail system directly connected to it.
nDirect ISDN PRI tandem trunk connections, using DS1 service between 
the DEFINITY ECS hub and the switches the voice mail supports. The 
system uses the D-channel to transmit mode code signals to light message 
waiting lights on remote extensions.
nA uniform dial plan for all switches in the network, with a 4-digit plan if 
Merlin Legend/Magix is part of the network.
nOne and only one mailbox for each extension in the network.
NOTE:
DCS software, X.25 hardware, and CLAN hardware/software are not 
required for this type of network. Additionally, you cannot network switches 
simultaneously using both mode code and DCS.
Configuration example
Figure 10 shows what a configuration of centralized voice mail via mode might 
look like.
In this configuration, DEFINITY system A is the hub. Voice mail system X is the 
centralized voice mail system. All other systems in the network are supported by 
voice mail system X 
except Legend system E and DEFINITY system D. These 
switches do not have a direct ISDN-PRI connection to the hub. 
						

							What’s New in DEFINITY ECS
Release 8.2 Job Aid  555-233-754  Issue 1
April 2000
Networking Enhancements 
150 Networking - ISDN Private 
2
Figure 10. Centralized Voice Mail Via Mode Code Example Configuration
Feature Support
Features that are supported are:
nCalling party name/number sending/retrieval
nMessage waiting light activation
nRemote coverage to voice mail
nFax, as well as voice, mail
Features Not Supported
The following capabilities are not supported via mode code. 
nMost DCS feature transparency. 
nCentralized voice mail for a tandem switch (does not have a direct 
connection to the hub switch).
nTransfer into voice mail
Legend
Legend
DEFINITYLegendDEFINITY
DEFINITY
DEFINITY
Voice Mail
Voice Mail
=not supported by
voice mail X 
						

							What’s New in DEFINITY ECS
Release 8.2 Job Aid  555-233-754  Issue 1
April 2000
Networking Enhancements 
151 Networking - ISDN Private 
2
Setting Up Centralized Voice Mail Via Mode 
Code
The following step describe how to set up DEFINITY switches to support 
centralized voice mail. For information on setting up Merlin Legend/Merlin Magix, 
see 
Merlin Magix Integrated Systems Network Reference, 555-715-114. For 
information on setting up 
INTUITY Messaging Solutions, see INTUITY Messaging 
Solutions Integration with System 75, Generic 1 and 3, and R5/6. 
1. Enter change system-parameters customer-options on the command 
line of your system administration screen.
2. On page 3 (Figure 11
), verify fields as follows:
—
ISDN-PRI field is y.
—
Mode Code for Centralized Voice Mail? field is y.
—
Mode Code Interface? field is y.
—
UDP field is y.
Figure 11. Modified “change system-parameters customer-option” form
3. On the hub switch, enter add trunk group xxxx on the command line of 
your system administration screen, where xxxx is the number of the ISDN-
PRI trunk group connecting the hub with the remote switch.
4. On page 1, verify fields as follows:
—
Group Type field is ISDN.
—
Service Ty p e  field is TIE.
5. On page 2, verify fields as follows:
change system-parameters customer-options  Page 2 of 4
OPTIONAL FEATURES
                     Hospitality (Basic)? y
         Hospitality (G3V3 Enhancements)? n
                            H.323 Trunks? n       Processor and System MSP? n
                             IP Stations? n             Private Networking? n
                        SDN Feature Plus? y  Restrict Call Forward Off Net? y
                         ISDN-BRI Trunks? y          Secondary Data Module? y
                    Malicious Call Trace? n    Survivable Remote Processor? n 
Mode Code for Centralized Voice Mail? y            Tenant Partitioning? n
                     Mode Code Interface? y    Terminal Trans. Init. (TTI)? n
                Multifrequency Signaling? y            Time of Day Routing? n
Multimedia Appl. Server Interface (MASI)? n           Uniform Dialing Plan? y
        Multimedia Call Handling (Basic)? n  Usage Allocation Enhancements? y
     Multimedia Call Handling (Enhanced)? n
                                                        Wideband Switching? n
           Personal Station Access (PSA)? n                       Wireless? n
           (NOTE: You must logoff & login to effect the permission changes.) 
						

							What’s New in DEFINITY ECS
Release 8.2 Job Aid  555-233-754  Issue 1
April 2000
Networking Enhancements 
152 Networking - ISDN Private 
2
—Send Name field is y.
—Send Calling Number field is y.
—Numbering Format field is Private.
—Send Connected Number field is y.
6. On each remote switch, repeat steps 3-5.
7. On each DEFINITY switch in the network, enter change dialplan on the 
command line of your system administration screen.
8. Administer the dial plan for each node in the network (see Chapter 4 in this 
document for examples). Usually the hub is considered Node 1.
If the network c ontains Merlin Leg end /Mag ix systems:
—Uniform Dialing Plan field is 4 for each node.
If the network c ontains only DEFINITY systems:
—Uniform Dialing Plan field is 4 or 5.
9. For each DEFINITY node, enter change feature-access-codes on the 
command line.
10. On page 2, verify fields as follows:
—
Leave Word Calling Send a Message field is #90.
—
Leave Word Calling Cancel a Message field is #91.
NOTE:
All nodes in the system and the Voice Mail system must match this setting
11. For each DEFINITY node, enter add ds1
UUCSS on the command line, 
where 
UUCSS is the address of the DS1 circuit pack.
12. On page 1, verify fields as follows:
—
Line Code field is B8ZS.
—
Framing field is extended superframe.
—
Signaling Mode field is ISDN/PRI.
—
Connect field is PBX.
—
Interface field is network (for the hub) and user (for the remote 
switch).
NOTE:
Mode Codes will not work with D4 or SuperFrame
13. For each DEFINITY node, enter change sign next on the command line. 
Administer the signaling group (see example in Chapter 4 of this 
document).  
						

							What’s New in DEFINITY ECS
Release 8.2 Job Aid  555-233-754  Issue 1
April 2000
Networking Enhancements 
153 Networking - ISDN Private 
2
14. For each DEFINITY node, enter change isdn private-numbering, and 
verify fields as follows:
15.
Set Network Level field is 0
This setting  overrid es the sig naling  on the D c hannel, allowing  the 
Messag e Waiting  lamp  ac tivation sig nal to b e sent
16. On the DEFINITY node, enter change sys params mode-code on the 
command line. 
17. On the hub switch, set the VMS Hunt Group Extension field to the voice 
mail hunt group extension (Figure 10
).
Figure 12. Mode Code Related System Parameters 
18. On the remote switches, repeat Step 15. Enter the voice mail hunt group 
extension in the Remote VMS Extension - First field.
19. For each DEFINITY node, enter change aar an on the command line. 
20. Verify the following:
—
Call Type field is lev0
21. On the hub switch, enter change station 
extension for each port 
extension in the voice mail hunt group. 
22. On Page 1, verify the following:
—
Ty p e field is vmi.
23. On Page 2 of the Station screen, administer or verify the following:
—
LWC Reception field is msa-spe
 (Message Server Adjunct-System 
Processing Element).
—
Leave Word Calling field is
 y.
—
Adjunct Supervision field is 
y.
Page   1 
                   MODE CODE RELATED SYSTEM PARAMETERS
 
MODE CODES  (FROM SWITCH TO VMS)
Direct Inside Access: __
Direct Dial Access - Trunk: __
Internal Coverage: __
External Coverage: __
Refresh MW Lamp: __
System In Day Service: __
System In Night Service: __
OTHER RELATED PARAMETERS
DTMF Duration On (msec): __ Off (msec): __ Sending Delay (msec):__
VMS Hunt Group Extension : ____
Remote VMS Extensions - First: Second: 
						

							What’s New in DEFINITY ECS
Release 8.2 Job Aid  555-233-754  Issue 1
April 2000
Networking Enhancements 
154 Networking - ISDN Private 
2
—
Distinctive Audible Alert field is n
.
—
Switchhook Flash field is y
.
—
LW C Activation field is y
.
24. For each remote DEFINITY node, enter change coverage remote on the 
command line. 
25. Administer or verify the following:
— 01 contains the extension of the voice mail hunt group.
Support for Japan National Private Networking
In release R8, DEFINITYs implementation of ISDN PRI for Japan will be modified 
to support the private networking environment.  The private protocol borrows 
heavily from the national specific public ISDN PRI specification.  The differences 
are such that the Public Network protocol is insufficient to provide basic call 
support in their private networks.  Existing supplementary services 
implementations of calling line and connected line information presentation and 
restriction will be tested for inclusion.  There is no expectation to modify these 
implementations for operation in Japan.  From a marketing point of view, this 
protocol is being implemented to penetrate the existing private networking market 
that is already entrenched.  In the near future, QSIG will become a dominant 
private networking protocol as Japanese vendors implement it.
The Japanese standards organizations, TTC, has defined QSIG to be the same 
as the ISO  standard which DEFINITY already supports.  This private networking 
protocol will provide the basic level of networking in order to meet the immediate 
connectivity needs of our customers.  QSIG will be positioned, going forward, as 
the private networking platform for Japan.  A new administration option will be 
developed to distinguish this protocol from the Japanese public network.
n2 MB Trunk - Ph2: Codeset 5 TCMs
n2 MB Trunk - Ph2: Connect Ack
n2 MB Trunk - Ph2:  Different Protocol Discriminator
nD Channel - Private ISDN Ntwks - Q.931.a, Q.932.a (Basic Call Setup)
nD Channel - Private ISDN Networks - 951.a