I have been designing / deploying voice solutions for a long time and i have a simple question. We are all pushing to full e164 numbers in dial plans on CUCM, etc to create a truly global dial plan. I use SIP trunks to gateways all the time and it supports the transport of the '+' whereas H323 does not. Is there a way to match patterns based on the matching the + at the start of a string rather then matching ending strings, or ignoring the first character with translations rules/profiles? Will this ever be in the road map on IOS gateways?
Is there a way to match patterns based on the matching the + at the start of a string rather then matching ending strings, or ignoring the first character with translations rules/profiles?
The destination-pattern command does accept a plus character. IOS won't ignore part of a dial string; you would need to remove it on the dial-peer directly (e.g. forward digits) or through a voice translation-profile.
Generically speaking here is how I deal with +E.164 on PSTN/SRST gateways:
For incoming calls from the PSTN I use a translation-profile to add the plus on the incoming dial-peer. If you don't do it here and phones failover with SRST incoming calls won't work. Remember that the ephone-dns will be +E.164-formatted.
I put the CUCM-facing VoIP dial-peer at preference 1 to allow any registered ephone-dns to receive calls as long as they are registered, even if OPTIONS PING thinks CUCM is back.
For outgoing calls to the PSTN I typically localize on the CUCM SIP trunk because IOS has rule limits. In most NANP areas requiring seven-digit dialing there are too many rules for it to fit on IOS. In this direction the call arrives at the gateway prefixed with the offnet access code (e.g. 9) and the number exactly as the PSTN carrier expects it. This also ensures that your outgoing PSTN dial-peers are ready to go during SRST since you're passing the call to the router in the same format a user would dial.
I use a voice class sip-profiles to ensure that the Remote-Party-ID header stays in +E.164 format. IOS will attempt to update CUCM with the final localized format in the 183 Session Progress message. I want the phone display to stay globalized so a little regex magic gets the job done here.
If you're not careful you can create call loop scenarios with +E.164 dial-peers on a gateway. I have started using CoR as a defacto-ACL on every router as a safeguard.
I use the amazing voice class uri feature to match incoming VoIP dial-peers by the Via header instead of the overly generic incoming called-number . So much more precise.
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 ...
This document describe how DST changes and how time changes are
implemented in DST. Daylight Saving Time (DST) is the practice of
setting the clocks forward 1 hour from standard time during the summer
months, and back again in the fall, in order to make b...