International calling 1

[t3chhelp]

Local and long distance calls are completing properly but international calls are not. Call gets dropped. This is on a pri. Everyone is set to the highest Cor with no restrictions. When I monitor the call with the list trace command the only difference in the outpulse digits to the telco is at the end of international digits there is a # inserted. I've checked ars digit conversion. Any one seen this happen before. Is this normal, should I just call the telco provider to check it on their end. Thanks.

 

[sjforcum]

On your ars entry, are you using NAtL or FNPA?

If it's FNPA you'll need to play around with the PFX Mrk on your route pattern.

 

[jgideon]

My PRI on my legend doesn't like any extra digits... gets rejected by telco. (For example, if the redial includes the '1' from the IVR menu, the call will fail). It sounds to me like the above suggestion for eliminating the # is the way to go.

 

[Duaneness]

It's always easiest to blame the telco's....

Make some test calls. Note the time and the number dialed, as well as the ANI of the station you're making the calls from. Open a trouble ticket with your provider. Give them the sample call detail noted above. They will either identify a problem in their network, or will not see the calls hitting their network at all.

Try placing the international calls using a "dial-around", one of those 10-10-xxx numbers. That should force the calls to another provider's network. If those calls complete, then the problem is not in your switch.

- Duaneness

 

[hartmj]

When we switched telco providers, we had a similar problem. On the second page of the trunk form, there should be an option that says "Suppress # Outpulsing?". We had to set this option to "y". I would change that and try the call again.

Also, on our ARS entry, we have it set to INTL and not FNPA or NATL
Hope this helps,

Josh

 

[t3chhelp]

In the ARS entry for 011 it is set to INTL. I will take a look at suppress # Outpulsing on the trunk form. Thank you for your suggestions.

 

[t3chhelp]

I've tried changing the suppress # Outpulsing to yes in the trunk form. It is still outpulsing the # sign at the end of a international call. Any seen this type of problem before. Thanks

 

[avaya13]

I use to have the same problem. To resolve the problem you may need to change the type of call from INTL to PUB. That how I resolve my problem.

MKD

 

[telcoguy]

I had the same thing happening,
my telco (KNP in NL) is not completely compliant with the flag used for INTL on all their 5ess's connecting to the international net.
This resulted in intermittant faults depending on what route my calls were taking.
I flag my international calls as "NAT" now, and never had a problem since.
I traced the issue by doing a 'list trace station' while dialing the numbers.
The error it came up with, confirmed the net was not exepting "INTL"

 

[t3chhelp]

Thank-you, changing it to Natl or publ both work like a charm. Now I can start calling overseas.