International Call Set-up on new Long Distance PRIs 1

[klmnop]

Hi,

ASA 2.1

We've replaced 2 long distance only T1s (old trunk group 5, type TIE) with 2 long distance only PRIs (new trunk group 10, type ISDN). Both trunks have COR of 6; agents with FRL 6 should be able to make International calls with FRL 6. (No problems until the cutover).

I don't know if there is something which needs to be done to the new trunk group and have opened a ticket with the carrier to make sure the circuit is set up to allow outbound international calls.

What's happening when callers make international calls is that the call is routed internally to the last 4 digits. Note that we dial a '3' for an outside line.

Example:

11:47:39 active station 2491 cid 0x1b71
11:47:41 dial 3011 route:ARS
11:47:41 term trunk-group 10 cid 0x1b71
11:47:56 dial 3011 44 1536 5704# route:ARS
11:47:56 route-pattern 6 preference 1 cid 0x1b71
11:47:56 seize trunk-group 10 member 46 cid 0x1b71
11:47:56 Setup digits 011441536[highlight #FCE94F]5704[/highlight]
11:47:56 Calling Number & Name 9789988404 NO-CPName
11:47:56 Proceed trunk-group 10 member 46 cid 0x1b71
11:47:57 active trunk-group 10 member 46 cid 0x1b71
11:49:38 idle station 2491 cid 0x1b71

The remote agent who took this call was 8414. The last 4 digits of the number called are 5704. VDN 5704 is for returns and exchanges.

No changes have been made to route patterns.

display route-pattern 6 Page 1 of 3
Pattern Number: 6 Pattern Name: International
Secure SIP? n
Grp FRL NPA Pfx Hop Toll No. Inserted DCS/ IXC
No Mrk Lmt List Del Digits QSIG
Dgts Intw
1: 10 6 978 1 n user
2: 5 6 978 1 n user
3: 7 6 978 1 n user
4: n user
5: n user
6: n user

BCC VALUE TSC CA-TSC ITC BCIE Service/Feature BAND No. Numbering LAR
0 1 2 3 4 W Request Dgts Format
Subaddress
1: y y y y y n n rest none
2: y y y y y n n rest none
3: y y y y y n n rest none
4: y y y y y n n rest none
5: y y y y y n n rest none
6: y y y y y n n rest none


Here is the only denial event at that time. I don't think it's relevant because when I tested from my extension, I did not see a new denial event.

display events

EVENTS REPORT

Event Event Event Event First Last Evnt
Type Description Data 1 Data 2 Occur Occur Cnt

1208 Srv/opt not imp/unsp 83000A 24F 01/16/10:59 01/18/11:42 34



Any ideas of what to try next?

Thanks,

Karen

 

[kyle555]

What's your calltype in ars?

 

[AvayaTier3]

Good job tracing and figuring out how to duplicate your problem. That is the first step to working with someone to prove if you have pbx programming problem or a network provider issue. It is not easy to test with anyone if you cannot duplicate the failures.

Your list trace shows the call went out on the trunk-group 10 member 46 and was active for 2 minutes.
It is unusual for a provider to route the call back to your pbx rather than supply intercept or a state that returns denial, if it cannot complete the call to it's destination.

When first turning up new circuits with a provider, there should have been testing for all applications that you expect to work.
At the very least, everything that works on pbx with the previous trunks/provider should work with your new service. Unless you enhanced or changed your services from the new provider.

inbound digits - DID or DNIS digits for incoming toll free - how many digits and do they match your pbx dialplan
outbound local - 7 digit or 10 digit
outbound ld - 10 digit or 11 digit
outbound intl - number of digits and allowed country codes can be allowed or denied by the provider
network authorization codes
outbound callerID and user names (ISDN) are also possible to send (provider may charge extra for this) and provider may only send BTN for all outbound even if you send valid callerID
outbound 911 calling is also important (make sure 911 responders know your address for all locations that can call 911. It's the law, in most places).

Testing by changing to a different trunk-group that you know worked, or works with intl dialing if that is available, would be a good test and maybe a work-around until you get your new provider to test with you on your new trunks. This will help to prove issues are pbx programming related or network provider issues.


A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

44 years Bell, AT&T, Lucent, Avaya
Tier 3 for 34 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[klmnop]

As an update, my provider notified me that the circuit was not provisioned for international calls.

kyle555 - Call type in ARS for 011 is 'intl'.

AvayaTier3 - Thank you for your help. Excellent point about testing at the time of circuit turn-up and thank you for the list.

Our only other circuit is a local PRI. I tried routing an international call out over it and received a denial event. This proves your point of the calls going out and the carrier sending them back (over the other trunk).


list trace station 8127

time data

09:21:34 tone-receiver 01AXX02 cid 0x2336
09:21:34 active station 8127 cid 0x2336
09:21:34 dial 3011 route:ARS
09:21:34 term trunk-group 7 cid 0x2336
09:21:44 dial 30114415365750# route:ARS
09:21:44 route-pattern 6 preference 1 cid 0x2336
09:21:44 seize trunk-group 7 member 21 cid 0x2336
09:21:44 Setup digits 0114415365750
09:21:44 Calling Number & Name 9789988127 NO-CPName
09:21:45 denial event 1186: Invalid number format D1=0x8c2c D2=0x960f1c
09:21:45 idle trunk-group 7 member 21 cid 0x2336
09:21:48 idle station 8127 cid 0x2336


display events

EVENTS REPORT

Event Event Event Event First Last Evnt
Type Description Data 1 Data 2 Occur Occur Cnt

1186 Invalid number format 8C2C 960F1C 01/19/09:09 01/19/09:21 2

 

[AvayaTier3]

Have you tried a "co" copper trunk for outbound international calls?

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

44 years Bell, AT&T, Lucent, Avaya
Tier 3 for 34 years and counting
[URL unfurl="true"]http://bshtele.com[/url]