Lucent Technologies DEFINITY Enterprise Communications Server Release 8.2 Administration For Network Connectivity Instructions Manual

							QSIG 
391
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
B  Private Networking
•Conference
If a user on a branch calls the attendant and conferences the attendant onto the 
call, the attendant’s display is not updated with “conference”. There is no QSIG 
standard defined for Conference and Definity has not implemented conference via 
MSI. 
•Centralized AUDIX
When a user zero’s out of AUDIX, if the host PBX is a QSIG-CAS branch, then 
the call is sent to the QSIG-CAS attendant.
•DCS+
On an incoming attendant-seeking call, calling-party information may be received 
at the branch if a call comes from another PBX in the network over a DCS ISDN 
trunk. 
•Dial Access to Attendant
When a user on a branch PBX dials the Dial Access to Attendant number, as 
administered on the Dial Plan Record screen, the call is sent to an attendant on the 
main PBX.
•DID/Tie/ISDN Intercept
DID, Tie, and ISDN trunk calls that are intercepted are sent to the attendant on the 
main.  
•Emergency access to attendant
Emergency access may be administered so that if stations are off hook for an 
extended period of time, then a  call is placed to the attendant, or a user can dial an 
Emergency access to attendant feature access code. Emergency access to the 
attendant does not go to the attendant on the main PBX. Instead, the call goes to 
an attendant on the branch PBX. If there is no branch attendant, the call is denied. 
•Facility Busy Indication
Facility Busy indication functions as for RLT-CAS. 
•Individual Attendant Access
An attendant may be assigned an individual extension so that it is possible to dial 
that attendant directly rather than dialing the attendant group.
•ISDN (non-QSIG)
On an incoming attendant-seeking call, calling party information may be received 
at the branch for a call coming in over an ISDN trunk. 
•Leave word calling
LWC Message Retrieval is not available for the branch PBX.  
						

							QSIG B  Private Networking
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
392
•Malicious Call Trace (MCT)
MCT is a feature that is performed on existing calls. MCT does not generate new 
attendant seeking calls. MCT will work in QSIG-CAS provided the attendants 
performing MCT-Activate, MCT-Control, and MCT-Deactivate are all on the 
same PBX. That is, an attendant on the main cannot work with an attendant on the 
branch to perform MCT.
•Multifrequency Signaling
Calls coming into a branch over Multifrequency trunks are subject to intercept and 
may be sent to the attendant at the main. Multifrequency signaling can indicate 
that an incoming call on an MF trunk terminate at the attendant, regardless of the 
dialed extension.
•Night Service
Night Service is available to QSIG-CAS. If a branch PBX is in night service, then 
all attendant-seeking calls for that branch are routed to the night service 
destination, not the CAS attendant. If the main PBX is in night service, then all 
attendant seeking calls at the main (either incoming from the main or branch) are 
routed to the night service destination. The night service destination for a PBX 
needs to be on that same PBX.
DEFINITY supports the following night service features:
~Hunt Group Night Service — allows an attendant to assign a hunt group to 
night service
~Night Console Service — allows a console to be designated as the night 
service destination
~Night Station Service — allows a station to be designated as the night service 
destination
~Trunk Answer from Any Station (TAAS) — allows voice terminal users to 
answer attendant seeking calls
~Trunk Group Night Service — allows an attendant or designated night service 
terminal user to assign one or more trunk groups to night service
•Non-attendant handling of CAS calls
Non-attendant handling of CAS calls functions as for RLT-CAS. 
•Outgoing Trunk Queuing 
Attendant-seeking calls from branch to main can be queued at the outgoing branch 
trunk group. 
•QSIG 
All the existing QSIG features and services are available in QSIG-CAS. 
QSIG-CAS is available in any QSIG-CAS ISDN network (PRI, BRI, and 
PRI/ATM).
•QSIG Call Offer
Calls extended by the attendant can invoke Call Offer.  If a call invokes Call Offer, 
attendant return call procedures still apply.  
						

							QSIG 
393
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
B  Private Networking
•Extending a Call
QSIG CAS ensures that QSIG Path Replacement is attempted after split/swap,  
provided that all three parties (original calling party, the attendant, and the called 
party) are never conferenced together.  That is, if the attendant toggles between the 
other two parties for any number of times, never conferencing all three together, 
and then joins the two parties together (with the attendant now out of the picture 
and ready to go on and handle other calls), Path Replacement is attempted. 
•Remote Hold
Remote Hold is used in an RLT-CAS environment and has no benefit in 
QSIG-CAS. 
•Controlled Restriction
As for RLT-CAS, Controlled Restriction is not available in QSIG-CAS for users 
on the branch.
•Security Violation Notification
As for RLT-CAS, the CAS attendant cannot receive SVN referral calls from a 
branch because any administered SVN referral extension must be on the local 
PBX.
•Special Application 8140 - Attendant Dial 0 Redirect
Attendant Dial 0 Redirect allows calls to the attendant group to be routed to one of 
two attendant groups based on their call priority level, and to alert with emergency 
ring. The two groups are the default attendant group and the priority attendant 
group. Administration of whether a priority level routes to the priority group is 
done on the console parameters screen.
Administration on the console parameters screen at the main determines which 
attendant group the priority level routes to and whether calls of that priority level 
alert with emergency tone. 
•Special Application 8141 - LDN Attendant Queue Priority
Calls coming to the main from a QSIG-CAS branch cannot be queued by LDN 
Priority at the main. Note that QSIG-CAS does not change the ability to of  LDN 
Queue Priority to function for calls coming directly into the main.
•Special Application 8156 - Attendant Queuing by COR
Calls coming to the main from a QSIG-CAS branch cannot be queued by COR 
Priority at the main. Note that QSIG-CAS does not change the ability to of 
Attendant Queueing by COR to function for calls coming directly into or 
originating at the main. 
						

							QSIG B  Private Networking
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
394
•Timed reminder and Attendant timers
Attendant timers are:  
~Timed Reminder on Hold — starts when an attendant puts a call on hold.  
When this timer expires, the held call alerts the attendant. 
~Return Call Timeout — starts when a call is extended and then released from 
an attendant console.  If this timer expires, the call is returned to the attendant. 
~Time In Queue Warning — indicates the amount of time a call can wait in the 
attendant queue before activating an alert. 
~No Answer Timeout — Calls that terminate at an attendant console ring with 
primary alerting until this timeout value is reached.  When this timeout value is 
reached, the call rings with a secondary, higher pitch. 
~Alerting — notifies, via secondary alerting, other attendants in an attendant 
group of an unanswered call. The Attendant Alerting Timed Reminder starts 
when a call reaches the Attendant No Answer Timeout maximum value. 
•Transfer Out of AUDIX by Dialing 0 
Attendant seeking calls that transfer out of AUDIX by dialing 0, whose host 
switch is a branch PBX, are sent to the QSIG-CAS attendant on the main PBX 
whenever the dial 0 out of AUDIX destination corresponds to the attendant group. 
						

							Centralized Voice Mail Via Mode Code 
395
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
B  Private Networking
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:
•DEFINITY ECS R8
•Prologix R3
•BCS Issue 6
•Merlin Legend R6.1
•Merlin Magix 1.0
Note:DEFINITY One and Guestworks are not supported.
Voice mail systems that support these connections are:
•Intuity AUDIX R4.4 or higher running on a MAP5, with up to 18 ports
•Octel 100, with up to 16 ports
Configuration requirements
Centralized voice mail via mode code requires the following:
•A DEFINITY ECS switch as the hub of the voice mail network, with the voice 
mail system directly connected to it.
•Direct 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.
•A uniform dial plan for all switches in the network, with a 4-digit plan if Merlin 
Legend/Magix is part of the network.
•One 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. 
						

							Centralized Voice Mail Via Mode Code B  Private Networking
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
396
Configuration exampleFigure 8 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.
Figure 8. Centralized Voice Mail Via Mode Code Example Configuration
Feature Support
Features that are supported are:
•Calling party name/number sending/retrieval
•Message waiting light activation
•Remote coverage to voice mail
•Fax, as well as voice, mail
Features Not SupportedThe following capabilities are not supported via mode code. 
•Most DCS feature transparency. 
•Centralized voice mail for a tandem switch (does not have a direct connection to 
the hub switch).
•Transfer into voice mail
Legend
E
Legend
F
DEFINITY
ALegend
GDEFINITY
B
DEFINITY
C
DEFINITY
D
Voice Mail
X
Voice Mail
Y
=not supported by
voice mail X 
						

							Centralized Voice Mail Via Mode Code 
397
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
B  Private Networking
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. 
Begin
1Enter change system-parameters customer-options on the command line 
of your system administration screen.
2On page 3, 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.
3On 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.
4On page 1, verify fields as follows:
~Group Type field is ISDN.
~Service Ty p e  field is TIE.
5On page 2, verify fields as follows:
~Send Name field is y.
~Send Calling Number field is y.
~Numbering Format field is Private.
~Send Connected Number field is y.
6On each remote switch, repeat steps 3-5.
7On each DEFINITY switch in the network, enter change dialplan on the 
command line of your system administration screen.
8Administer 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 contains Merlin Legend/Magix systems:
~Uniform Dialing Plan field is 4 for each node.
If the network contains only DEFINITY systems:
~Uniform Dialing Plan field is 4 or 5.
9For each DEFINITY node, enter change feature-access-codes on the 
command line. 
						

							Centralized Voice Mail Via Mode Code B  Private Networking
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
398
10On 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
11For each DEFINITY node, enter add ds1UUCSS on the command line, where 
UUCSS is the address of the DS1 circuit pack.
12On 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
13For each DEFINITY node, enter change sign next on the command line. 
Administer the signaling group (see example in Chapter 4 of this document). 
14For each DEFINITY node, enter change isdn private-numbering, and verify 
fields as follows:
~Set Network Level field is 0
This setting overrides the signaling on the D channel, allowing the Message 
Waiting lamp activation signal to be sent
15On the DEFINITY node, enter change sys params mode-code on the 
command line. 
16On the hub switch, set the VMS Hunt Group Extension field to the voice mail 
hunt group extension.
17On the remote switches, repeat Step 15. Enter the voice mail hunt group extension 
in the Remote VMS Extension - First field.
18For each DEFINITY node, enter change aar an on the command line. 
19Verify the following:
~Call Type field is lev0
20On the hub switch, enter change station extension for each port extension in 
the voice mail hunt group. 
21On Page 1, verify the following:
~Ty p e field is vmi. 
						

							Centralized Voice Mail Via Mode Code 
399
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
B  Private Networking
22On 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.
~Distinctive Audible Alert field is n
.
~Switchhook Flash field is y
.
~LWC Activation field is y
.
23For each remote DEFINITY node, enter change coverage remote on the 
command line. 
24Administer or verify the following:
~01 contains the extension of the voice mail hunt group.
End 
						

							Japan TTC Q931-a Private Networking Protocols B  Private Networking
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
400
Japan TTC Q931-a Private Networking Protocols
The Telecommunications Technology Committee (TTC) of Japan defines national standards that are to be used in 
domestic public and private network facilities.  The TTC typically modify other international standards as 
defined by ITU-T for use in Japan with additional national protocols to enhance operation for their customers.
Overview
The TTC has defined a family of Q931-a private networking protocols that allows for 
a level of feature transparency between different switches within a single vendor or 
multi-vendor private network. DEFINITY ECS provides connectivity into the 
Japanese private networking environment via two methods
•CAS (Channel Associated Signaling) — first developed in DEFINITY ECS R7 
for the Japan market (See the description of  TN2242 Japan 2Mbit Trunk in 
DEFINITY ECS R8 System Description, 555-233-200.)
•ISDN (Integrated Services Digital Network) PRI (Primary Rate Interface) —  
TTC specific protocol newly support in DEFINITY ECS R8.  DEFINITY ECS 
supports Basic Call with Number Identification services.
TTC Basic Call Setup with Number Identification Supplementary Service
DEFINITY ECS allows the display of the calling party number to the called party.  
DEFINITY ECS also displays the connected number to the calling party after the call 
connects to the called number of another destination.  For many protocols, Number 
Identification is considered to be part of Basic call; however, the TTC protocol 
defines Number Identification services to be part of their supplementary services 
offering. No additional supplementary services are supported at this time.
You can administer outgoing calls as “yes”, “no, or “restricted.”  Restricted means 
that DEFINITY ECS sends the information but sends it “presentation restricted,” 
which indicates to the receiving switch that the information should not be displayed.  
A received restricted number is included on the Call Detail Record (CDR).