I've got about 10 users set up using Mobility with remote destination profiles pointing to their cell phones. My problem is that when they receive a mobility call, the caller ID is showing up as the main office number. We are masking all outbound calls using the main DID here, so I imagine that is where this is coming from.
How can I keep my outgoing calls using this mask, but also allow caller ID for Mobility calls? If this is not possible, what do I need to do to enable caller ID for Mobility?
You can setup a separate CSS /partition that matches a separate route pattern for calls to go out from remote destination profiles. This CSS should be applied to the remote destination profile. The route pattern u create should not have caller id for outbound calls masked to the main DID.
User is on CM A with ICT to CM B. All gateways are registered to CM B with external Mask.
How can I tell CM B that the call from CM A is a mobile connect call and doesn't need external mask vs a normal outbound call that does? Separate ICT's..one for normal calls and one for destination profiles?
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...