Route incoming PRI calls out SIP trunk if no 4 digit extension match 1

[dmoore7648]

For all 4 digit extension that come in on our local PRI, if it's not defined in Avaya, I would like to automatically route the call to a SIP trunk connected to Cisco UCM. Can this be done without setting up a route for each number?

 

[kyle555]

Yeah, sorta. The more contiguous the block of DIDs on CM vs CUCM, the easier. If your PRI were trunk 1, change inc trunk 1, and you'll get a table where you can manipulate. You can have 1 entry for the 1000s, one for the 2000s, etc, and there are different layers of the dialplan to do it, but you do need to account for everything.

 

[dmoore7648]

Thanks, but how do I route a call from an internal extension that has no match to the SIP trunk. For example, extension 1453 dials 7648. 7648 is no longer defined on the Avaya as it is now on Cisco. Is there a way to force all calls that go to an extension that is not defined in Avaya to go accross the SIP trunk?

Thanks!

 

[kyle555]

Thinking about it, yeah. Minorly complicated, but here goes:

"Change dialplan parameters" Make sure match ext before UDP.

Change uniform-dial-plan. Make, for your example, 7, length 4 go aar.

That means the 7000's will go to AAR. In AAR analysis, 7000s match a SIP trunk to CUCM.

So, when 7640 is dialed, its matched against extensions first, and if so, ring the extension. When you dial 7468, it looks against extensions first, and if none, go to UDP, which routes 7000s to AAR, and away you go.

That said, there are very possibly/likely other considerations depending on how your system is set up, and changing "dialplan parameters" and making the change I suggested could impact other things - such as: sloppy admin. Rerouting extensions through UDP without removing those extensions. If you have "pick UDP first" for 1234 to go out your SIP trunk, and 1234 remained an extension, your change would kill calls to 1234 as the system would see it as an extension and not try UDP anymore. Hope that makes some sense.