Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Magix PRI call routing problem 1

Status
Not open for further replies.

thrtnastrx

Technical User
Oct 31, 2002
276
US
I have a PRI with 50 DID's that all extensions match the 4 digit DID. I have one DID (1813) that I want to route to a hunt group (7928). I go into PRI>Dial Plan Rtg, enter the DID digits 1813, enter 4 for total DID digits, delete 4, add 7928. When I do this, and dial the phone DID 1813, it rings to hunt group 7928 fine. The problem is ALL other DID's ring to the operator and it says "cover" in her display. When I remove the dial plan routing programming all DID's ring to their respective extensions. What am I missing?
 
Customer uses night service but at the time of testing it was not enabled.
 
I discovered a weird thing with Dial Plan Routing, and it is this: If you've got a specific extension that needs special treatment, you need to be careful as to where you place it's rule in the table. The rule with the most number of digits (and the most specific) needs to be toward Entry 0, whereas the more generic rules need to move to the right.

Just today I discovered something weird as well. I have a TV station that needs 5288 (four digits expected, four digits deleted and replaced with 413) and 5299 (four digits expected, four digits deleted and replaced with 413).

In addition, the customer has a stray DID that sends 510 (three digits) which inappropriately routes to the Operator. I did not expect that behavior, since the customer uses a three digit dial plan and 510 is a legitimate extension.

Know how I fixed it? Totally stupid. I build an entry that says Pattern is 510, Expected and Deleted number of digits is 3, and the Added Digits is 510.

Get it? I saw 510. I killed all digits, then added the same digits back in. And THAT fixed the inability to distinguish between 5288, 5299 and 510.

Like I said...stupid. But that's what solved the problem.

Tim Alberstein
 
Tim,

What software versions are those switches using?

That is why I call them the "illogical Legend and Magix"...

You definitely deserve a star for discovering that bug!!!

....JIM....
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top