QSIG Trunks

[hdbeavis]

Does anyone know where I can find a good document on setting up QSIG H.323 Trunks between Avaya systems (i.e S8720 to S8710) that will support Path Replacement? I have the trunks set up and working but can't get the path replacement to work. I have checked every document that I can find and can find nothing wrong with my settings. Thanks

 

[Ronster]

have you checked with the supplier that they have QSIG supplementary service switched on.

Also, have you seen this document?

http://www.avaya.com/master-usa/en-us/resource/assets/applicationnotes/qsigtrkcmnortel.pdf

Ronster
"If you’re too open-minded, your brains will fall out.

 

[sweetp1808]

I have a qsig trunk between Avaya and Nortel. Everything is up and working but the Nortel side has a backup system if the main system goes down because it is a hospital. When the back up system kicks on the qsig b-channels do not come back up without resetting them. Does anyone know if this is a setting that is not set right or its just how it is. It seams the D-channel comes up though.

Thanks
Sheri

I work on the Avaya side and do not know anything about the Nortel.

 

[steeltown89]

Beavis,

The most important thing for path replacement to work is that all PBX's know of the extensions.

ie: PBX A calls PBX B, PBX B transfers the call to PBX C.
The extension that you call at PBX C has to be defined in AAR or something on PBX A so PBX A knows how to connect directly with PBX C (probably across your Qsig trunk to C) so PBX B drops out of the loop.

I have a document I created if you need it but more than likely it isn't working because PBX A doesn't know of the extension that PBX B called at PBX C.

 

[hdbeavis]

I appreciate the input. I can call each PBX from each PBX directly. i.e. I can call PBX A from PBX B&C. We have implemented a full "Web" design. All the PBX's are linked to each other directly with QSIG trunks. All PBX's have the ability to call each other via 5-digit dialing, via UDP and AAR tables. I just can't get the path replacement working to free up the un-needed trunks when a transfer is performed.

 

[steeltown89]

This document is intended to explain the testing that was completed to verify that IP trunks with QSIG path replacement enabled are able to transfer calls between three or more PBX’s and intelligently drop the PBX out of the call loop that transferred the call.

The call scenario is:

Station 10001 calls station 20001 on PBX B.
Station 20001 answers the call.
Station 20001 transfers the call to station 30001 on PBX C.
PBX B asks PBX A if it is aware of station 30001 and asks if it has a better route to get to station 30001.
If PBX A does know a better route it will connect to station 30001 directly and notify PBX B to drop out of the loop.
In the example the following items must be in place on each PBX for the path replacement to work properly.

If the trunk group is data restricted then path replacement cannot take place.

The trunk “Numbering Format” setting must be set to “unknown-private” which means the type of number will be “unknownPartyNumber”

display trunk-group 51 Page 3 of 21
TRUNK FEATURES
ACA Assignment? n Measured: none
Internal Alert? n Maintenance Tests? y
Data Restriction? n NCA-TSC Trunk Member: 1
Send Name: y Send Calling Number: y
Used for DCS? n Hop Dgt? n Send EMU Visitor CPN? n
Suppress # Outpulsing? n Format: unk-pvt
UUI IE Treatment: service-provider

Replace Restricted Numbers? n
Replace Unavailable Numbers? n
Send Called/Busy/Connected Number: y
Hold/Unhold Notifications? y
Send UUI IE? y Modify Tandem Calling Number? n
Send UCID? n
Send Codeset 6/7 LAI IE? y


and that will check the “private-numbering” table for how to build the complete network number in order to be able to reroute the call.

display private-numbering
(display system features in newer versions)

NUMBERING - PRIVATE FORMAT

Network Level: 0 PBX Identifier:
Level 2 Code: Deleted Digits: 0
Level 1 Code:

The following trunk settings should also be set:

display trunk-group 51 Page 2 of 21
Group Type: isdn

TRUNK PARAMETERS
Codeset to Send Display: 6 Codeset to Send National IEs: 6
Charge Advice: none
Supplementary Service Protocol: b Digit Handling (in/out): enbloc/enbloc

QSIG Value-Added? y
Digital Loss Group: 18
Incoming Calling Number - Delete: Insert: Format:

Disconnect Supervision - In? y Out? n
Answer Supervision Timeout: 0





The following trunk settings should also be set:

display trunk-group 51 Page 4 of 21
QSIG TRUNK GROUP OPTIONS




Diversion by Reroute? y
Path Replacement? y
Path Replacement with Retention? n
Path Replacement Method: better-route
SBS? n
Display Forwarding Party Name? y
Character Set for QSIG Name: eurofont
Encoding Method: proprietary

If the trunk group is “Measured” in any way, then on the “system-parameters features” screen “Path Replacement with Measurements” has to be set to “yes”.

display system-parameters features Page 8 of 17
FEATURE-RELATED SYSTEM PARAMETERS

ISDN PARAMETERS

Send Non-ISDN Trunk Group Name as Connected Name? n
Display Connected Name/Number for ISDN DCS Calls? n
Send ISDN Trunk Group Name on Tandem Calls? n
Send Custom Messages Through QSIG? n

QSIG TSC Extension:
MWI - Number of Digits Per Voice Mail Subscriber: 5

National CPN Prefix:
International CPN Prefix:
Pass Prefixed CPN to ASAI? n
Unknown Numbers Considered Internal for AUDIX? n
USNI Calling Name for Outgoing Calls? n
Path Replacement with Measurements? y
QSIG Path Replacement Extension:
Path Replace While in Queue/Vectoring? N


If the stations involved are data restricted, path replacement is not possible.

display station 30001 Page 2 of 5
STATION
FEATURE OPTIONS
LWC Reception: spe Auto Select Any Idle Appearance? n
LWC Activation? y Coverage Msg Retrieval? y
LWC Log External Calls? n Auto Answer: none
CDR Privacy? n Data Restriction? n
Redirect Notification? y Idle Appearance Preference? n
Per Button Ring Control? n Bridged Idle Line Preference? n
Bridged Call Alerting? n Restrict Last Appearance? y
Active Station Ringing: single

H.320 Conversion? n Per Station CPN - Send Calling Number?
Service Link Mode: as-needed
Multimedia Mode: basic Audible Message Waiting? n
MWI Served User Type: Display Client Redirection? n
AUDIX Name: Select Last Used Appearance? n
Coverage After Forwarding? s
Automatic Moves: no Multimedia Early Answer? n
Direct IP-IP Audio Connections? y
Emergency Location Ext: 30001 IP Audio Hairpinning? N


If the station “Class of Service” (COS) allows the activation of data privacy and the user has activated this feature then path replacement is not possible.

display cos Page 1 of 2
CLASS OF SERVICE

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Auto Callback n y y n y n y n y y y n y n y n
Call Fwd-All Calls n y n y y n n y y y n y y n n y
Data Privacy n y n n n y y y y y n n n y y y
Priority Calling n y n n n n n n n y y y y y y y
Console Permissions n y n n n n n n n y n n n n n n
Off-hook Alert n n n n n n n n n n n n n n n n
Client Room n n n n n n n n n n n n n n n n
Restrict Call Fwd-Off Net n n n n n n n n n n n n n n n n
Call Forwarding Busy/DA n n n n n n n n n n n n n n n n
Personal Station Access (PSA) n n n n n n n n n n n n n n n n
Extended Forwarding All n n n n n n n n n n n n n n n n
Extended Forwarding B/DA n n n n n n n n n n n n n n n n
Trk-to-Trk Transfer Override n y n n n n n n n y n n n n n n
QSIG Call Offer Originations n y n n n n n n n n n n y n n n
Contact Closure Activation n n n n n n n n n n n n n n n n


Standard routing rules between all the PBX’s involved will need to be addressed as well.