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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

System adding # with AAR dialing

Status
Not open for further replies.
Nov 6, 2003
22
US
I will try to keep this as simple as possible.

I am doing some VOIP between offices. I have one good working trunk/sig group/routing pattern already working. Lets call that Office A.

I am configuring Office B and having some problems.
I have set up a trunk group/sig group/route pattern exactly the same however I cannot sucessfully make a call.

I am using AAR dialing for both offices. Using country codes + the 4 digit extension. I am stripping the country code off when I connect to the other office.

For Office A, I dial 61 + 1234 and 1234 gets transmitted.

14:34:13 tone-receiver 01A0204 cid 0x11f
14:34:13 active station 356 cid 0x11f
14:34:21 dial #1611234
14:34:21 term trunk-group 6 cid 0x11f
14:34:21 dial #1611234
14:34:21 route-pattern 16 preference 1 cid 0x11f
14:34:21 seize trunk-group 6 member 4 cid 0x11f
14:34:21 Setup digits 1234
14:34:21 Calling Number & Name NO-CPNumber Doe,John
14:34:22 Proceed trunk-group 6 member 4 cid 0x11f
14:34:23 Alert trunk-group 6 member 4 cid 0x11

However for Office B, I dial 49 + 1234 and 1234# gets transmitted. I am getting a denial event 1220 as listed below...

14:38:02 tone-receiver 01AXX04 cid 0x13c
14:38:02 active station 356 cid 0x13c
14:38:08 dial #1491234#
14:38:08 term trunk-group 9 cid 0x13c
14:38:08 dial #1491234#
14:38:08 route-pattern 19 preference 1 cid 0x13c
14:38:08 seize trunk-group 9 member 1 cid 0x13c
14:38:08 Setup digits 1234#
14:38:08 Calling Number & Name NO-CPNumber Doe, John
14:38:19 denial event 1220: ISDN recover timer expiry D1=0xd9 D2=0x66
14:38:19 idle trunk-group 9 member 1 cid 0x13c
14:38:20 idle station 356 cid 0x13c

From what I know the distant end has their switch ready. I have done basically everything that I can think of (even switching the far-end clan boards) and that # is always inserted.

I am not sure if that is causing the problem but would like to know why its there.

any ideas?



 
The # sign at the end of the string signifies "End of Dial" to the switch, no more digits will be outpulsed. Print and compare both trunk groups and AAR route patterns to make sure both are exactly the same. The Event 1220 seems to indicate a timer expiration, the switch on the other side may be looking for more digits to process the call, you will notice the 10 second delay before the denial event. It would appear to be a layer 3 issue between the switches. Also investigate the error logs for more information.
 
Could be the dialplan has number 4 set to 10 digits instead of 6?

In the future everything will work...
 
There could be a chance its the other side since I am still awaiting confirmation that they are set up correctly.

Thanks for the help.

 
I am having the same issue "denial event 1220" but my VIOP trunks are working most of the time. My trunks seem to stop working every 3 to 4 hours. However when I check status the trunks are up and the sig group is up on both sides. If I busy and release both sides they start working for another four hours any Ideas???

Site A= S8500 CM 2.2
Site B= G3si R12 CM2.2
3 meg hardware VPN between the two sites.
I only have 5 trunk administered on both sides.
 
Has anyone of you guys figured out your issues since these posts? I'm interested to know because I was experiencing something similiar and figured it out to be my own translations....The CLANs and MEDPROs did not match in the SIG Group which was causing the 1220 denial event. I changed the SIG group and was good to go.

Alex.

Alex Morales
IT Analyst
Avon Products

2 - Definity G3r CM 1.3.2
2 - Definity G3Si CM 2.1
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top