QSIG over IP Trunk

[mcopini]

We've got two G3SI V1.1 Definity's with an IP trunk group between them. We tried QSIG by the book, but didn't get it to work. All trunk-members are in-servide idle, but when calling (TAC or via AAR and so on) we get fast busy. When doing a trace on a station dialing the TAC, we get denial event 1164. Any ideas? Any help would be greatly appreciated.

Thans in advance!

Rgds,

Maarten Copini

 

[BuckWeet]

Make sure you can ping every B-site board from site A and vice versa. Make sure its not an IP transport issue. Make sure there are no firewalls in the way. Then start checking COR and COS's. IP trunking is alot easier on setup for the fact you don't have to worry about transport as much as feature setup..


BuckWeet

 

[mcopini]

Thanks 4 Ur reply, but...
All CLAN's etc. are "pingable", no problems there. Both Definity are actually on the same network. No Firewalls and routers in the way. COR's and COS's can't be a problem when using the Trunk Access Code. Think it's a configuration issue. Any idea's?

Kind Regards,
Maarten Copini

http://www.effecta.nl

-Please let fellow members know if their post was of any help-

 

[BuckWeet]

Also are you ip-network regions setup? are the codec settings right? using the TAC will cause the systems to draw dialtone from the far end switch. so its not initinating the connection at all, or the connection is failing. You said the CLANs are pingable, what about the medpros?

can you copy and paste your signaling group and the first page of your trunk group?

 

[mcopini]

Okay, I'll paste some screencaps. Any help greatly appreciated! (Btw, the network regions and codec are setup properly, I think...
Here's the trunk, It's identical on both sides, so is the rest...

Group Number: 3 Group Type: isdn CDR Reports: y
Group Name: IP Trunk COR: 1 TN: 1 TAC: XXX
Direction: two-way Outgoing Display? n Carrier Medium: IP
Dial Access? y Busy Threshold: 99 Night Service:
Queue Length: 0
Service Type: tandem TestCall ITC: unre
Far End Test Line No:
TestCall BCC: 0
TRUNK PARAMETERS
Codeset to Send Display: 0 Codeset to Send National IEs: 6
Max Message Size to Send: 260 Charge Advice: none
Supplementary Service Protocol: a Digit Handling (in/out): enbloc/enbloc

Trunk Hunt: cyclical QSIG Value-Added? n
Digital Loss Group: 13
Calling Number - Delete: Insert: Numbering Format:
Bit Rate: 1200 Synchronization: async Duplex: full
Disconnect Supervision - In? y Out? n
Answer Supervision Timeout: 0

--------------------

Signaling group, also identical on both sides:

Group Number: 3 Group Type: h.323
Remote Office? n Max number of NCA TSC: 0
Max number of CA TSC: 0
Trunk Group for NCA TSC:
Trunk Group for Channel Selection:
Supplementary Service Protocol: a Network Call Transfer? n


Near-end Node Name: Clan#1 Far-end Node Name: Train3-Clan
Near-end Listen Port: 1720 Far-end Listen Port: 1720
Far-end Network Region:
LRQ Required? n Calls Share IP Signaling Connection? y
RRQ Required? n
Bypass If IP Threshold Exceeded? n

Direct IP-IP Audio Connections? y
IP Audio Hairpinning? y
Interworking Message: PROGress

Hope you can make anything of this...
Thanks a mille in advance.


Kind Regards,
Maarten Copini

http://www.effecta.nl

-Please let fellow members know if their post was of any help-

 

[mcopini]

Ok then, *looking ashamed*. While looking at my own post I just saw I forgot to fill in the Trunk Group for Channel Selectionfield... Works perfectly now! The QSIG and 'send name/number' stuff I'll figure out myself. That shouldn't be a problem!
Thanks for the help anyway!

Kind Regards,

Maarten -needs glasses- Copini

 

[BuckWeet]

Not sure if it'll make a difference, but I always do "tie" as my service-type on the trunks. Also if you're going to do Q.SIG you need to supplementary services on signaling group to "b" and then to "b" on the trunkgroup as well (i think its B)

And you're sure that that stations can call COR 1, even when doing the TAC, they still have to be able to call the COR that the trunk group is in..

BuckWeet

 

[mcopini]

It was tie but I changed it just to test, so you're right on that one. I'm still working on the QSIG stuff, and indeed I had the field Supplementary Service Protocol set to "b" along with lots of other stuff for QSIG. I'll change those back, I was just fooling around to get at least dialtone! Now that I have dialtone, I'll work on the features and do some DCS and QSIG feature testing, like name- and number sending, call diversion and all that. (and a big bag of chips)
Thanks for you're help again. You'll see me moaning and crying on the forum again when things go wrong again ;-)

Rgds,

Maarten C.

 

[BuckWeet]

Are you planning on doing centralized audix via qsig? if you do, i'd like some notes on that one, heh. I had an install to do the other day with centralix audix via qsig, of course with avaya's documentation, they don't tell you how to do it. so i ended up doing dcs+

BuckWeet

 

[mcopini]

You just got lucky, we're doing that this week: Centralized Intuity via Qsig for a G3SI V11, a G3SI V9 and two CMC's V8 and 10. Sounds lovely don't it?
I'll let you know when finished.

Kind Regards,

Maarten Copini

 

[BuckWeet]

Cool, let me know how it goes..

BuckWeet