Catch-all or default route for inbound DIDs on a PRI
Here's the scenario:
We have a PRI from the telco delivering 4-digits. The 2821 ISR is configured for 2-digit extensions. The telco has assigned DIDs 2500 - 2599. We have about 20 extensions defined and calling into them directly works as it should. In fact everything is working just fine. What we are trying to accomplish is this: if one of the 80 remaining DIDs is dialed, we want to route them to the operator (x00). As it stands if we receive the digits 2508 (since x08 isn't assigned) we see a cause code of 'unallocated number'. How do I construct a rule that accomplishes the following:
if 2-digit extension is defined then route accordingly; else route to operator
Here is our existing inbound translation-rule.
voice translation-rule 1 rule 1 /^3008/ /00/ (last four from original published BTN routing to the operator extension) rule 2 /^2560/ /60/ (CUE dial-in from pstn) rule 3 /^..\(..\)/ /\1/ (ditch the first two digits the telco sends)
I can't seem to find a way to do this that doesn't break rule 3 and route everything to 00.
Re: Catch-all or default route for inbound DIDs on a PRI
Thank you for the suggestion. We tried to implement this, but as soon as I did every outbound call began to route to the operator at 00. The CME would not take the following command:
rule 1 /.*/ /00/
So I made it:
rule 1 /\.*/ /00/
Perhaps that was incorrect.
In the interest of a quick, albeit partial fix, what we ended up doing was creating ephone-dns for the remaining DNs and then call forwarding them to 00. This works for everything up to 89, so better than nothing for the time being. Any other ideas?
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...