IP Trunk Issues

[btrain08]

I have an s8710 and an s8300 with a WAN link from our firm connecting offices. I setup an IP Qsig Trunk and put 1 extension from each side in the aar table to test. I am getting a denial event 1197, which is really vague. I set this up like my other offices that have these trunks. What would be the starting point to look at what's wrong?

 

[phoneguy55]

I would first status the trunk and signaling group on both ends. Hopefully they are all in service. display the signaling group and check the remote node name on both sides and make sure the IP addresses are right.

 

[wleong56]

Make sure the TSC are setup on both ends...
Look for this in system-parameters features, ISDN Parameters.

Check that trun group form page 2 for Supplementary Service Protocol is optkioned for QSIG... should be b.
Then, make sure that the QSIG TRUNK GROUP OPTIONS in trunk group form is the same on both sides.

Maks sure that the signaling group, TSC Supplementary Service Protocol is optioned for QSIG on both sides.

 

[btrain08]

What is needed for TSC on the signalling group? I thought that is for DCS?

Both sides are up and in-service and both ends are set for Qsig (b).

I traced the TAC on the calling end and the trace shows:


20:10:37 Calling party station 7013 cid 0x52
20:10:37 Calling Number & Name 7013 *Drum Test GS
20:10:37 dial 4277 route:UDP|AAR
20:10:37 term trunk-group 10 cid 0x52
20:10:37 dial 4277 route:UDP|AAR
20:10:37 route-pattern 10 preference 1 cid 0x52
20:10:37 seize trunk-group 10 member 1 cid 0x52
20:10:37 Calling Number & Name NO-CPNumber NO-CPName
20:10:37 Setup digits 4277
20:10:37 Calling Number & Name 7013 *Drum Test GS
20:10:37 Proceed trunk-group 10 member 1 cid 0x52
20:10:37 denial event 1197: Resources unavail/unspec D1=0x24 D2=0x12f
20:10:37 idle trunk-group 10 member 1 cid 0x52
20:10:45 idle station 7013 cid 0x52

 

[wleong56]

What does the trace from the other end look like... above trace last seen was a call proceed, but never got an alert, which should be the next step.. always a proceed should be followed by alerting.
Like this...
13:28:04 Proceed trunk-group 10 member 3 cid 0x3ba
13:28:04 Alert trunk-group 10 member 3 cid 0x3ba
Otherwise, some sort of denial event like in your case above.

 

[btrain08]

This the other end.. codec mismatch.. where would I change that?

21:41:04 Calling party trunk-group 115 member 1 cid 0x253e
21:41:04 Calling Number & Name 7013 *Drum Test GS
21:41:04 active trunk-group 115 member 1 cid 0x253e
21:41:04 dial 4277
21:41:04 redirect station 4277 cid 0x253e
21:41:04 denial event 2309: Drop call codec mismatch D1=0x7f400175 D2=0x253e
21:41:04 idle trunk-group 115 member 1 cid 0x253e
21:41:13 TRACE COMPLETE trunk-group 115 cid 0x0

 

[wleong56]

Now, you have what the problem is, as the 1197 is very generic.
Look at the codec on both ends.. they should match on both end. Look at example below Codec Set 1, where I 3 audio codec. At a simple level, what ever you have on yours, it needs to be a complimentary on both sides. Also, take a look at the Network Region and make sure there are no issues there (without getting into the details).

IP Codec Set

Codec Set: 1

Audio Silence Frames Packet
Codec Suppression Per Pkt Size(ms)
1: G.711MU n 3 30
2: G.729 n 2 20
3: G.723-6.3K n 1 30
4:
5:
6:
7:

 

[wleong56]

IP CODEC is connected to IP-NETWORK-REGION xx, where xx is the region number you define for both ends, in the signalling group.

command is change ip-codec-set yy, where yy is the codec defined in the IP-NETWORK-REGION xx page 1.

 

[btrain08]

The codec set matching now fixed the issue. Thanks !!!