Any Help for a 200ELx with International Call problems on a PRI card?

[jonmyk]

All calls besides International work. When trying to dial anything with 011 I get a system busy tone after all digits are dialed.

I've tried putting the entire digit string in Form 26 going to a route that only deletes the 9 and inserts *4*6*4

then to a route that deletes the 9 and inserts nothing

To a route that deletes all digits and inserts *4*6*4 plus the number and the one that deletes all and inserts only the number.

I can connect to the circuit with my PRI test set and make the call.

The kicker is the Telco is receiving all of the digits regardless on how I program it besides the 011.

Example.

011528186258431 is the string
Telco gets 528186258431 from the system but I have no SMDR record for this call. [Bang]

Also if I insert a local or LD number after deleting all the call goes through. [Shrug]


Have tried dialing the number and inserting 011 in form 22 *4011*4 as well as using an account code to go Direct to ARS from the SS420 which doesn't work either.

Site has no copper lines to test with DTS.

"The only problem with common sense is that it's not that common

 

[kwbMitel]

It sounds like you have the NI-2 protocol enabled.

Depending on the age of your software you may be able to enable the "Unknown Call type".

Without Unknown Call Type enabled, the system sends a call type flag for international calling (and ld and local and toll free)

Each call type sends its own flag.

With Unknown call type enabled, the system sends the digits as dialled.;

**********************************************
What's most important is that you realise ... There is no spoon.

 

[jonmyk]

kwb,

This is running Q46 with a PRI card programmed through IMAT software. I was not able to find where the unknown call type is located.

"The only problem with common sense is that it's not that common

 

[jonmyk]

Fixed it by inserting 011 in a delete 1 mod digit string so system was dialing 9011011XXXXXXXXXXXXX, -1 Mod digit, something absorbing 011 and telco got 011XXXXXXXXXXXX.

"The only problem with common sense is that it's not that common

 

[kwbMitel]

Yes, this is what NI-2 Protocol will do without unknown call type enabled. The 011 is stripped and the call is sent with a call flag plus destination.

Your work around basically reinserts the 011.

I'm somewhat surprised you do not have the same issues with LD, Toll free, and Operator assisted calls as all of these also have similar issues typically.

I don't work with the SX-200 very much these days so I can't remember when unknown call type became available or how it was implemented.

Hopefully your workaround will work for all instances.

**********************************************
What's most important is that you realise ... There is no spoon.