Merlin Legend PRI call routing issue

[samthedog99]

Good day. I have a customer that has a R6 Legend and they just changed their ATT PRI circuit. Their main listed number rings into the console, but now instead of showing caller ID, it shows "DID?" I checked the dial plan routing:


A Entry Number: 0 1 2 3
A NtwkServ: Any service Any service Any service
A Expected Digits: 7 7 7 0
A Pattern to Match: xxx4601 xxx3272
A Digits to Delete: 4 7 7 0
A Digits to Add: 100 100

This is how it looked before they changed their PRI. Entry #1 is the number that isn't working. I tried changing it to expect 10 digits and delete 10 digits, but when I change to pattern by adding the area code, it just beeps and won't let me.
I also tried creating a new pattern under the unused entry #3, but once again, when i enter the 10-digit number, it won't let me.
Any help on what I'm doing wrong?
thanks mto

 

[TouchToneTommy]

It sounds like they are not sending the same DNIS digits as before, so it doesn't match an extension, calling group, or your routing table, and ending up at the console as an unknown number.

The main number ends in 4601 and you want it to route to 100? And another number ends in 3272 and you also want to route it to 100?

You can only MATCH 7 digits, but you can receive 10 TOTAL DIGITS

Service > Entry No. 0 > Misc > Any Service
Patterns > Entry No. 0 > Digits to match 5554601
TotalDigits > Entry No. 0 > 10
DeleteDigits > Entry No. 0 > 10
Add Digits > Entry No. 0 > 100

 

[Telecomboy]

This may or may not be your issue, but I had a Legend R6.0 that was obviously matching the tables starting with 0, then 1, then 2. Everything worked fine until switching PRI providers and then I started having the same issue as you (DID? at console which means the call isn't matching anything). My 0 table was a generic expect 10, delete 6, add none which routed to the majority of the DID's. Then, my table 1-3 were special saying expect 10, delete 10, add xxxx. Those calls all went to the operator with ?D because they matched the first table 0 and then didn't know where to go. I had to make my table 0 entry table 3 and move my other tables to 0-2 so it would try to match them first. I have been dealing with Legend/Magix since 1995 and never had that be the case before, but for some reason this Legend wasn't looking for the perfect match it was looking at table 0, then table 1, then table 2 and everything matched table 0 so it tried using it for all calls.

 

[merlinman]

There are was to determine EXACTLY what they are sending.


Just to let you know.

http://merlinmanswebpage.yolasite.com