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

							QSIG 
371
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
B  Private Networking
Setting Up QSIG
Begin
Steps
1
Verify with your sales representative or project manager what QSIG capabilities 
the system should have. The following capabilities apply:
2Determine whether the system is using ISDN-PRI, ISDN-BRI, or ATM for the 
QSIG network connections. Your sales representative or project manager should 
know this. (If the system is using ATM trunking for QSIG, see DEFINITY ECS 
R8.2 - ATM Installation, Upgrades, and Administration, 555-233-124.)
Table 1. QSIG capabilities
Capability CategoriesCross-Networking Features
QSIG Basic•Calling/Connected Number
•Calling Number Identification
•Transit Counter
Interworking with DCS
•Called/Calling Name/Number delivered 
to and received from DCS networked 
switches
Basic Supplementary Service
•Called/Busy Name
•Call Completion
•Call Forwarding (Diversion)
•Calling Name Identification
•Call Offer
•Centralized AUDIX
•Call Transfer
•Path Retention
•Message Waiting Indication
Centralized Attendant Service
•Centralized Attendant
Supplementary Service with 
Rerouting
•Call Forwarding (Diversion) with 
Rerouting
•Path Replacement
Transfer into Lucent QSIG Voice 
Mail 
•Transfer into QSIG Voice Mail
Value-Added Lucent (VALU)
•Called/Busy Number Display
•Distinctive Ringing
•Call Coverage 
						

							QSIG B  Private Networking
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
372
3Enter display system-parameters customer-options on the command line 
of your system administration screen.
4On page 1, verify fields as follows:
~G3 Version field is V8 or later.
5If the system is using ATM for QSIG, go to page 2 and verify the following field:
~Async. Transfer Mode (ATM) Trunking field is y.
6On page 3, verify fields as follows:
If the system is using ISDN-BRI for QSIG:
~ISDN-BRI Trunks field is y.
If the system is using ISDN-PRI for QSIG:
~ISDN-PRI field is y.
If the system is using QSIG Supplementary Services with or without Rerouting:
~Restrict Call Forward Off Net field is n.
7On page 4, verify fields as follows:
~Basic Call Setup field is y.
If the system is using QSIG Supplementary Services:
~Basic Supplementary Services field is y.
If the system is using QSIG Supplementary Services with Rerouting:
~Supplementary Services with Rerouting field is y.
If the system is using QSIG VALU:
~Value-Added Lucent (VALU) field is y.
8(For ISDN-PRI only). Administer or check the QSIG DS-1 circuit pack (see 
Appendix A). Check for the following field entries:
•Connect field - pbx
•Interface - peer-master or peer-slave
•Peer protocol - q-sig
•Signaling mode - isdn-pri or isdn-ext
•Channel Numbering - sequential or timeslot (This item must match 
between the local switch and receiving switch.)
9(For ISDN-BRI only). Administer or check the QSIG ISDN-BRI circuit pack (see 
Appendix A). 
						

							QSIG 
373
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
B  Private Networking
10Administer or check the QSIG ISDN trunk group(s) (PRI or BRI) connected to 
the DS-1 or BRI circuit pack (see Appendix A). Check for the following field 
entries on Page 1:
•Group type - isdn
•Supplementary service protocol- b or d where: 
(For Supplementary Services with or without Rerouting) 
•Outgoing Display? - y
•QSIG Value-Added Lucent - y
On Page 2 (Also for Supplementary Services with or without Rerouting):
•Hop Dgt - y
•Disconnect Supervision - y
•Numbering Format - public, private, unknown, unk-pvt
•NCA - TSC Trunk Member - The trunk member whose D-channel routes 
CISCs.
•Send Called/Busy/Connected Number - y
•Send Calling Number - y
•Send Name - y
End
bISO QSIG standards (including the ETSI Version 2 and 
European Computer Manufacturer’s Association (ECMA) 
standards aligned with the ISO standards)
dETSI Version 1 and ECMA standards issued prior to the ISO 
standards for QSIG private network (supports only Name 
Identification and Additional Network Feature Transit 
Counter (ANF-TC)) 
						

							QSIG B  Private Networking
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
374
Setting Up QSIG 
Supplementary 
Services
Begin
Steps
1
Administer or check the ISDN Numbering - Public/Unknown screen (see 
Appendix A).
2Administer or check the ISDN Numbering - Private screen (see Appendix A).
3Administer or check the Signaling Group screen (see Appendix A). Check for the 
following field entries to ensure proper operation of Call Completion:
•Supplementary Service Protocol - b
•Max Number of NCA TSC - greater than 0
4Administer or check the Route Pattern screen. Check for the following field 
entries to ensure proper operation of Call Completion and Transit Counter:
•TSC - y (necessary if switch is a transit node for TSC)
•Hop Lmt - between 1 and 32
5Administer or check the Feature-Related System Parameters screen. Check for 
the following field entries to ensure proper operation of Call Completion and Call 
Transfer:
•Trunk-to-Trunk Transfer - y 
•QSIG TSC Extension - valid extension number to serve as TSC for both 
incoming and outgoing QSIG network calls.
•Automatic Callback - No Answer Timeout Interval (rings) - enter the 
number of times, 2 to 9, a callback call should ring at the caller’s phone 
before the callback is cancelled
•(For AUDIX/Octel Serenade support only) MWI - Number of Digits per 
AUDIX Subscriber - enter the number of digits in messaging subscriber 
extensions, if any. The value in this field must match the value of the 
Extension Length field on the Switch Interface Administration form of 
AUDIX.
•(For AUDIX/Octel Serenade support only) Unknown numbers internal for 
AUDIX - y if, when the switch cannot identify a calling number as internal 
or external, the switch should treat it as internal for AUDIX use.
6Administer or check the Class of Service (COS) screen for each COS that may be 
using the QSIG network. Check for the following field entries to ensure proper 
operation of Call Completion, Call Offer, and Call Forward:
•Restrict Call Forward Off-Net - n 
•Auto Callback- y 
•QSIG Call Offer Originations - y 
						

							QSIG 
375
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
B  Private Networking
Call Completion
In addition to the Basic QSIG Supplementary Services administration described 
above, complete the following administration:
•On the Trunk Group screen, page 1, set the Supplementary Service Protocol field 
to b and administer the trunk for Call Independent Signalling Connections.
Transfer into Voice Mail
In addition to the Basic QSIG Supplementary Services administration described 
above, complete the following administration:
•On the System-Parameters Customer-Options screen, page 6, the Transfer Into 
Lucent QSIG Voice Mail field must be set to y.
•On the Feature Access Code (FAC) screen, page 3, assign a Feature Access Code 
in the Transfer to Voice Mail Access Code field. (This field is called “Transfer to 
AUDIX Access Code” in pre-R8 systems).
•A hunt group must be in the coverage path of the user’s mailbox to be transferred 
into, as administered on the Station and Coverage Path screens. On the hunt group 
screen, page 2, for this hunt group, qsig-mwi must be entered in the Message 
Center field and the number for the voice mail system must be entered in the Voice 
Mail Number field.
Setting Up Centralized 
Attendant Services
Begin
Steps
1
Enable QSIG Supplementary Services with Rerouting on the System Parameters 
Customer Options screen, page 6, as described above.
2On the System Parameters Customer Options screen, page 6, enter y in the 
Centralized Attendant field.
3On the Console Parameters screen, enter QSIG-main or QSIG-branch in the 
CAS field.
 a  If QSIG-branch is entered in the CAS field, then enter a number for QSIG 
CAS Number.
 b  If QSIG-branch is entered in the CAS field, then the field AAR/ARS Access 
Code is optional.
4Administer the QSIG ISDN trunk groups screen with option b for Supplementary 
Service Protocol
5Console Parameters screen.
6Attendant Console screen.
7Assign an extension to Attd on the Dial Plan Record screen at the main PBX.
8Administer each QSIG Supplementary Service that will be used by attendants. 
						

							QSIG B  Private Networking
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
376
Setting Up QSIG VALU 
Call Coverage 
Begin
Steps
1
Enable the QSIG Basic Supplementary Services on the Customer Options screen, 
page 6, described above.
2Enable (enter y) Value-Added Lucent (VALU) on the System-Parameters 
Customer-Options screen, page 6, as described above.
3On a Trunk Group screen, enter y in the QSIG Value-Added Lucent field, page 1, 
and sent b in the supplementary Service Protocol Option field, page 1.
4Administer the System Parameters Call Coverage/Call Forwarding screen as 
normal, with the inclusion of the following fields:
•Immediate Redirection on Receipt of PROGRESS Inband Information, 
page 1 — Enter y to speed up redirection of subsequent coverage points or 
call processing.  This may be necessary in cases where coverage path 
endpoints over non-Lucent switches are unavailable but the QSIG 
networked switch (or the public network) sends PROGRESS messages 
that delay the local switch from redirecting the call elsewhere. If the QSIG 
network contains only DEFINITY switches, enter n.
•QSIG VALU Coverage Overrides QSIG Diversion with Rerouting, page 1 
— Enter y to ensure that the coverage after forwarding 
activation/deactivation defined at a user’s phone (via Station screen) takes 
precedence over the system-wide coverage after forwarding 
activation/deactivation selection (via the System Parameters Call 
Coverage/Call Forwarding screen).  With QSIG Diversion with Rerouting 
active, the system-wide selection takes  precedence unless you enter y.  
See the examples in the following table: .  
Table 2. Coverage with QSIG Diversion with Rerouting
Cvg.  After 
Fwd 
(Station 
Screen)Cvg.  After 
Pwd (Sys. 
Parms. 
Coverage 
Screen)QSIG VALU 
Coverage 
Overrides 
QSIG 
DiversionThen
yn n
Call doesn’t go to local user’s 
coverage after failed forward 
attempt.  Call control passed to 
switch to which call forwarded.
yn yCall goes to local user’s coverage 
after failed forward attempt.
ny nCall goes to local user’s coverage 
after failed forward attempt.
ny y
Call doesn’t go to local user’s 
coverage after failed forward 
attempt.  Call control passed to 
switch to which call forwarded. 
						

							QSIG 
377
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
B  Private Networking
•Maintain SBA at Principal - Enter y to allow the user who originally 
receives the call to have simulated bridged appearance capability in the 
event the coverage point(s) are unavailable.  This capability allows the 
user to break into the call before it is answered by a coverage endpoint.
Note:If Maintain SBA at Principal is enabled (y), then Path Replacement 
is disabled.
5Define the remote QSIG users that you may include in coverage paths using the 
Remote Call Coverage Table.  See Defining Coverage for Calls Redirected to 
External Numbers in the Handling Incoming Calls chapter of the Administrator’s 
Guide. See also the Remote Call Coverage Table screen in the Administrator’s 
Guide.
6Define coverage paths for users as required.
Related Phone 
AdministrationAs you set up each user’s phone, QSIG networking features allow the following. 
•QSIG displays the user’s name as entered in the Name field on the Station screen, 
both on the display of another networked phone when called by that user or when 
calling that user.
•QSIG allows call waiting from networked phone calls if you set the Call Waiting 
Indication field to y. 
•QSIG allows auto callback from networked phones if you create an auto callback 
button for the user.
Related Hunt Group 
Administration As you set up each hunt group, you must enter either grp-name or mbr-name in 
the ISDN Caller Disp field, page 1. This entry determines which of the following the 
system displays on a QSIG networked phone that calls the hunt group: 
•The hunt group name/extension 
•The hunt group member’s name/extension 
Related Administration 
of Terminating 
Extension GroupsAs you set up each terminating extension group, you must enter either grp-name or 
mbr-name in the ISDN Caller Disp field. This entry determines which of the 
following the system displays on a QSIG networked phone that calls the terminating 
extension group: 
•The group name/extension 
•The group member’s name/extension 
Related Administration 
of AUDIX/Message 
CentersFor AUDIX administration generally, see one of the following:
•Installation and Switch Administration for the DEFINITY AUDIX System R4.0, 
585-300-122, which appears on the CD-ROM entitled DEFINITY AUDIX System 
R4.0 Documents, 585-300-803.
•Intuity Messaging Solutions LAN Integration with DEFINITY ECS, 585-313-602.
•Switch integration section of the CD-ROM entitled Intuity Messaging Solutions 
Release 5 Documentation, 585-313-803
Note:Set up QSIG TSCs before you administer messaging. See Call 
Completion  (page 363). 
						

							QSIG B  Private Networking
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
378
See the Octel Serenade documentation for Serenade administration.
Begin
Steps
1
(Local node message center switch only) Complete the Processor Channel 
Assignment screen (see Appendix A).
2(Local node message center switch only) Complete the Message Waiting 
Indication Subscriber Number Prefixes screen (see Appendix A).
3(Local node message center switch only) Complete the Station screen as specified 
in the Intuity or DEFINITY AUDIX documentation. Ensure that Page 2 of the 
screen has the following field entry:
•MWI Served User Type - qsig-mwi
4(Served user switch only) On the Hunt Group screen, set the following fields for 
the AUDIX hunt group:
•Message Center - qsig-mwi
•Voice Mail Number - the desired number
•Routing Digits (for example, AAR/ARS Access Code) - the desired 
number.
Digits entered in these fields should be selected so that the 
processing of these digits by the served user switch results in a call 
being redirected to the message center switch by an ISDN-PRI 
supplementary service protocol “b” facility. For example, if the 
message center switch is a DEFINITY ECS, the digits entered 
should reroute the call to the AUDIX hunt group on the message 
center DEFINITY ECS switch.
•Calling Party Number to AUDIX? - y
End 
						

							QSIG 
379
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
B  Private Networking
QSIG Interactions
Call Forwarding 
(Diversion)The interactions that apply to the standard DEFINITY ECS Call Forwarding features 
also apply to Call Forwarding (Diversion) with QSIG. The following are additional 
interactions.
•Alternate Facilities Restriction Levels
The AFRL of the original call is the AFRL used for Call Forwarding with 
Reroute.
•Authorization Codes
Call Forwarding with Reroute is denied to calls that require an Authorization 
Code.
•Automatic Alternate Routing and Automatic Route Selection
Call Forwarding with Reroute uses AAR and ARS to reroute the original call.
•Call Detail Recording
Call Forwarding with Reroute is denied to calls that require Forced Entry of 
Account Codes.
•Call Transfer
When a forwarded call transfers, the forwarding indication displays to the caller 
until the call is answered. This display includes the trunk group name and word 
“forward.” When the call is answered, the word “forward” is removed and the 
name and number of the answering party displays. 
•Distributed Communications Systems 
Call Forwarding feature transparency does not exist on calls tandemed between a 
QSIG (Supplementary Service protocol b) network and a traditional DCS 
network. However, the basic call continues.
•Facility Restriction Levels and Traveling Class Marks
The FRL (and TCM) of the original call is the FRL used for Call Forwarding with 
Reroute.
•Forwarding and Coverage
If a coverage point is a number that routes over an ISDN (Supplementary Service 
protocol b) trunk, QSIG diversion information is not passed to the coverage 
switch.
•QSIG Name and Number Identification 
Availability of name and/or number display at the originating and diverted-to 
users depends upon how QSIG Name and Number Identification has been 
administered for the switches involved.
•Terminating Call has Coverage Active
If a call is forwarded off switch, the terminating switch has call coverage 
activated, and the criteria are met, the call does not route to the forwarding party’s 
coverage path. It routes to the terminating station’s coverage path. 
						

							QSIG B  Private Networking
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
380
Call Transfer •Call Forwarding (Diversion)
When a call is forwarded and transferred or transferred and forwarded, the 
forwarding indication displays to the caller until the call is answered. This display 
includes the trunk group name and word “forward.” When the call is answered, 
the word “forward” is removed and the name and number of the answering party 
displays.
•Distributed Communications Systems 
The only DCS transparency that exists when a call is transferred in a DCS network 
and passed over a QSIG administered trunk is calling name.
•QSIG Path Replacement
ANF-PR is invoked whenever a QSIG transferred call is answered.
•QSIG Name and Number Identification 
Availability of name and/or number display at the connected parties depends upon 
how QSIG Name and Number Identification has been administered for the 
switches involved.
Transfer Into QSIG 
Voice Mail•QSIG Path Replacement
After a call is transferred into QSIG voice mail and the voice mail system answers 
the call, Path Replacement is attempted. 
QSIG Name and 
Number Identification 
interactions•Distributed Communications Systems (DCS)
DEFINITY ECS can display DCS called name/number information or ISDN 
connected name/number information in a DCS (ISDN) network. 
When an incoming ISDN call is routed back out over a non-ISDN trunk group, 
DEFINITY ECS can send the name of the non-ISDN trunk group as the connected 
name if the Send Non-ISDN Trunk Group Name as Connected Name 
field is y on the Feature-Related System-Parameters form.
Path Replacement  •Basic Call Management System
If the old connection is monitored by a BCMS entity, ANF-PR is blocked due to 
BCMS measurements.
•Call Detail Recording
Codes for recording the new connections of ANF-PR calls are code J for incoming 
trunk calls and code K for outgoing trunk calls. When a path is replaced, you also 
may receive records for short-duration calls that are not directly linked to the J and 
K records.
•Call Management System
If the old connection is monitored by a CMS entity, ANF-PR is blocked due to 
CMS measurements.
•Call Vectoring
•A transferred call that terminates at a vector and is answered cannot have its path 
replaced.