UDP Over new PRI Not Working

[Blueline]

I have a Magix R4 with UDP to offsite locations that was using digit insertion on the UDP route tables to use trunks on a LD T1 to pass calls.

We converted the LD T's to PRI and now the UDP doesn't work. I get an intercept message from AT&T saying call cannot be completed. Without a PRI monitor I cannot tell what digits are passing out of the Magix.

Any ideas if the UDP route patterns can be manipulated or if the PRI tables need to be adjusted and how ?

 

[Pepperz]

On all LD calls only?
Can you dial LD from the Site with the Outbound PRI's?
Usually the Telco will tell you wnat they see. It's obviously hitting them, so you know it's leaving your switch. It could be an area code thing, number of digits, OR OR OR they didn't set up the PRI to dial LD, i.e., no LD carrier assigned.

Pepperzgm at gmail dotte comm

 

[Blueline]

Yes, LD works fine. It's definately hitting their network. I wish there were a list trace command like the Definity.

 

[Pepperz]

Again, go to Telco. Tell then the intercept message you're getting, and ask them what it means. You are probably setting up something not to their liking, most likely with an extra 9, or too many digits from the UDP or something like that. Can you look at the SMDR, and get an idea?

Pepperzgm at gmail dotte comm

 

[TouchToneTommy]

Give an extension Pool Dial Out access, so that you can bypass UDP and place test calls directly. This way, you can see if calls can still go through, what needs to be dialed, and how to modify your UDP routes.