I've been trying, unsuccessfully, to get MobileConnect configured just right in our CUCM 7.0 environment.
Functionally, I have everything working with the exception of the Calling Party ID that's being passed through.
Currently, if a outside device calls into my desk extension, my desk extension displays the full number of the calling party. Using a Remote Destination Profile I'm able to also have this call route out to my cell phone which also displays the full number of the calling party. That much is good.
The issue is if an internal extension calls my desk phone, then desk phone displays the 5 digit internal extension number of the calling party. However, when this call routes through the RDP to my cell phone, my cell phone only displays the same 5 digit extension number.
Normally, we apply an Calling Party Transformation on all outbound calls to transform our 5 digit internal extensions into full 10 digit numbers. So, extension 12345 gets transformed using a pattern of 11122XXXXX into 1112212345.
However, I found that I needed to drop this transformation on the RDP otherwise it was converting an external number like 2223334321 through 11122XXXXX and passing it through as 1112234321 which was not what we wanted.
Essentially I need to find a way transform only our internal 5 digit extensions when routing through the RDP without transforming external 10 digit numbers at the same time.
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 ...