Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

QSIG Tie Hunt Group Name Display

Status
Not open for further replies.

vaoldschl

MIS
May 17, 2001
522
US
Last night I converted my H.323 tie lines from DCS to QSIG a)because my DCS was broken on interoffice transfer and b)because eventually I will be converting to a centralized VM that requires QSIG anyway so there was no point fixing DCS.

Almost everything works great. Using unk-pvt I get my 5 digits and name, transfers carry CLID and connected line within an office and between offices. Stand alone Intuity's get the proper incoming digits and do their magic with name announcements for remote subscribers. I am nearly happy as a clam.

Problem is that when dialing a remote hunt-group the name display doesn't work until the call connects. It displays properly when it does connect (hunt group name) but until answered all that you see is the 5-digit number dialed. I've gone through the docs, tested a few things at my test site but just can't seem to put my finger on it.
 
We are facing the same issue. From Avaya CM 5.2 to Nortel using Qsig, the name display doesn't work until the call connects.
Configuration of the trunk is:
TRUNK GROUP
Group Number: 22 Group Type: isdn CDR Reports: y
Group Name: Nortel Qsig 1 COR: 12 TN: 1 TAC: xx22
Direction: two-way Outgoing Display? y Carrier Medium: PRI/BRI
Dial Access? y Busy Threshold: 255 Night Service:
Queue Length: 0
Service Type: public-ntwrk Auth Code? n TestCall ITC: rest
Far End Test Line No:
TestCall BCC: 4
Group Type: isdn
TRUNK PARAMETERS
Codeset to Send Display: 6 Codeset to Send National IEs: 6
Max Message Size to Send: 260 Charge Advice: none
Supplementary Service Protocol: b Digit Handling (in/out): overlap/enbloc
Digit Treatment: Digits:
Trunk Hunt: cyclical
Digital Loss Group: 13
Incoming Calling Number - Delete: Insert: Format: unk-unk
Bit Rate: 1200 Synchronization: async Duplex: full
Disconnect Supervision - In? y Out? n
Answer Supervision Timeout: 0
Administer Timers? n CONNECT Reliable When Call Leaves ISDN? n
TRUNK FEATURES
ACA Assignment? y Measured: both Wideband Support? n
Long Holding Time(hours): 1 Maintenance Tests? y
Short Holding Time(sec): 10 Data Restriction? n NCA-TSC Trunk Member:
Short Holding Threshold: 15 Send Name: y Send Calling Number: y
Used for DCS? n Hop Dgt? n Send EMU Visitor CPN? n
Suppress # Outpulsing? n Format: unknown
Outgoing Channel ID Encoding: preferred 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? y
Send Codeset 6/7 LAI IE? y Ds1 Echo Cancellation? n
Apply Local Ringback? n
Show ANSWERED BY on Display? y
Network (Japan) Needs Connect Before Disconnect? n
QSIG TRUNK GROUP OPTIONS

TSC Method for Auto Callback: drop-if-possible
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: iso8859-1
QSIG Value-Added? y
QSIG-Value Coverage Encoding: proprietary


Any ideas?
 
I don't know if you resolved this but I read a note somewhere concerning this. Try changing "Send Called/Busy/Connected Number: y" to n.

Just a thought.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top