DID Catch All

[Burgal]

I would like to set up a catch all for unassigned DIDs.

I have a phone company block of 200 DIDs that route to my PRI. I only have about 75 or so of them used. The other 125 I'd like to have go to the operator if they're unassigned. If possible, this would be dynamic.

Eg,
system tries a DN with the DID, DN found, call routed.
System tries a DN with the DID, DN not found, call routed to operator.

Thanks

 

[jneiberger]

I'm new to DIDs in CallManager, so take my advice with a grain of salt. But could you configure catch-all translation patterns for your DIDs that translate the called number to that of your operator?

In other words, let's say you have 30355512XX as your DID range. DNs currently in use will have exact route patterns for matching purposes and would not hit the translation pattern. However, if there were no exact match, an incoming call to an unused DID would be translated to the extension of your operator.

Does that sound feasible?

 

[Burgal]

well I can't have two duplicate translation patterns...

eg, 443XXXX would be the DID route for their extension DN.
I'd have to duplicate a 443XXXX and lower its priority and then have it go to 0 if the pattern wasn't matched in the first one.

I haven't been able to see something like that in the translation pattern area. And I can't have two patterns duplicated...

 

[jneiberger]

I was just throwing out an idea. I've never actually configured DIDs in CallManager yet. I was hoping that you had more-specific patterns for individual DIDs, so that the larger wildcard pattern would only match unused DIDs.

Like I said, take what I say with a grain of salt.

 

[Burgal]

Hehe, well technically it works...
Thanks.

Yah, my unused DIDs are mixed in with the used...