ARS matching order sequence question

[pmcook]

How does the Magix make a match? Is it the first one it sees? I need to free up some routes as the table is getting full. I have a group of 4, 2101. 2102, 2150 and 2166. The first three are all for extension 100, 2166 is a FAX so that screws things up a bit. If I did a route for 2166 say as entry 0, then a range for the other three would that work?

 

[merlinman]

Are you talking ARS or Dial Plan Routing?

With ARS it goes in sequence and picks the 1st available POOL for out going calls.

Dial Plan Routing looks at EVERYTHING and decides the best match after looking at all of them.

If we had a table of what you are getting from the Carrier, and what Extensions you are trying to match, that would help.

Also, sometimes you have to PUSH BACK on both the CLIENT and the CARRIER to get a set of D-I-D's you can use.

Carriers couldn't care less if they throw you a bunch of scrap numbers for you to try to use. But with only 16 Tables, You have to care a lot.

http://home.comcast.net/~merlinman

-merlinmansblog.blogspot.com

 

[pmcook]

OOps, I meant incoming call route ie DID table.

 

[Telecomboy]

I always thought the inbound DID table looked at the whole table and then went with the best match, but I had once run into a Magix where I used route 0 for expect 4, delete 1, which routed to extensions that were 3-digit (the DID's ended in 5200-5250). I used route 1 for expect 4, digits to match 4222, delete 4, add 7112 (or whatever the fax extension was). When calling 4222 it always routed to x222 (which existed for DID 5222). I moved the table 1 to 0 and vice versa and it fixed the issue. So logically, it appeared like it looked at table 0 first, then table 1. Having the general catch all at table 0 caused it to route 4222 and 5222 to x222. Once I put route 0 with 4222 and route 1 as the general catch all, that routed the fax properly and 5222 to 222.

I've installed many Magix over the years and this was the first time I had ever run into that issue. I always use route 0 as the main catch all, so I know that isn't the way it normally works. For some reason though, this Magix looked at the routes in order.

 

[pmcook]

I can see that my dial plan table will be full. But it occurred to me that the only reason why I have to accomodate the first 3 numbers (2101 (main),2102,2150) is that their outbound caller ID sent those digits so a lot of people have them in their caller ID lists. I suppose in a few months that will blow over and I can recover 2 of the table entries for later needs.