Problem dialing certain outside #'s via IP tie trunks

[J1121]

I have a problem with making a call to 9-1-xxx-xxx-xxxx numbers from a Cisco Call Manager Express via an Avaya Communication Manager (using IP trunks as tie trunks between the two systems). Other outside calls work fine. It doesn't seem to be a problem related to permissions/FRL. I looked at various other tie trunks we have between other systems that can make all types of outside calls just fine and I also tried various FRL combos just to be sure the tie trunks had permissions to access to the PSTN trunks.

The only difference I see up to the point where it would send the call to the proper route pattern is that for the toll/toll free call, it mentions “PREFIX” in the trace on the Avaya system, but for the local call without dialing 1, it only shows the call type and that it’s ARS.
Bad call: “routeREFIX|FNPA|ARS”
Good call: “route:HNPA|ARS”

Here’s the bad example:
This happens for any toll free call or toll call where you dial 9 plus 1 and the number. In this example, I hear our internal intercept message that is defined in the “DID/Tie/ISDN/SIP Intercept Treatment:” field on System-parameters Features. It’s as if the system is ignoring the 9 to know it’s an outside call and to dial out via the ARS rules or it’s doing something strange/unexpected.

Trunk group 70 is the H.323 IP tie trunk and group 20 is the outside ISDN trunks the calls should ultimately route out for the PSTN

06:00:36 Calling party trunk-group 70 member 1 cid 0x2852
06:00:36 Calling Number & Name 67777 JOHN DOE
06:00:36 active trunk-group 70 member 1 cid 0x2852
06:00:36 dial 918009471 routeREFIX|FNPA|ARS
06:00:36 term trunk-group 20 cid 0x2852
06:00:36 dial 91800947100 routeREFIX|FNPA|ARS
06:00:36 ring trunk-group 70 cid 0x2852
06:00:36 active announcement 45527 cid 0x2852
06:00:36 hear annc board 01A10 ext 45527 cid 0x2852


Here’s the good call example to a local 10 digit number dialed as 9 plus area code and number:

06:08:42 Calling party trunk-group 70 member 1 cid 0x2864
06:08:42 Calling Number & Name 67777 JOHN DOE
06:08:42 active trunk-group 70 member 1 cid 0x2864
06:08:42 dial 971455512 route:HNPA|ARS
06:08:42 term trunk-group 20 cid 0x2864
06:08:42 dial 97145551212 route:HNPA|ARS
06:08:42 route-pattern 7 preference 1 location 1 cid 0x2864
06:08:42 seize trunk-group 20 member 115 cid 0x2864
06:08:42 Setup digits 7145551212
06:08:42 Calling Number & Name NO-CPNumber NO-CPName
06:08:42 Proceed trunk-group 20 member 115 cid 0x2864
06:08:43 Alert trunk-group 20 member 115 cid 0x2864

 

[fataldata]

Is your ars analysis for 1800 xxx xxxx the same as for 714 xxx xxxx ? The 714 call is using route 7( can't tell for the 1800 call), my guess is this is going to come down to the prefix mark in use on the route pattern. Post up ars analysis for 1800 and 714 and the respective route patterns they use.

 

[J1121]

Thanks for the reply. I think I discovered something on the Cisco side that is not quite right. I'm still investigating but I'm pretty sure it's not anything on the Avaya side that's causing the problem. Thanks and sorry