CME: Different ISDN TON for CFA depending on origin
I have a problem with call forwarding on CME. So a user puts just configures their phone to forward all calls, and enters the (external) number, prefixed with a 0 for an outside line, as is the custom here. This works fine when a colleague then calls, the call is forwarded over the ISDN line without a problem, the number translated internally to drop the extra 0, and going out with Plan: ISDN and Type: Unknown. This works as expected.
However, when an external caller calls this phone, CME again tries to forward to the same number. It all matches the same dial-peers and everything, the only difference is, that now suddenly it is being sent out as Plan: ISDN and Type: National. Because there is still a zero in the phone number, this is invalid, and we get a message from the telco that the number is not in use.
If we would enter the CFA number without the extra 0, it would work externally, but not internally anymore. Is there any reason why CME changes the TON in this case? And how would you go about changing it, without breaking anything else?
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: firstname.lastname@example.org 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 ...