We are having issues with Caller ID with our CUCM 12.5 Servers that are connected to WAVE 5.20 Management Servers in our test environment.
In our setup, we have a WAVE Management Server connected to a CUCM server via SIP Trunk at Location A. Then a second SIP Trunk connects the CUCM server to a proprietary device which connects to a SIP Trunk on a second CUCM server located at Location B. The CUCM server at Location B is also connected to its own WAVE Management Server via a SIP Trunk.
The proprietary device is acting as a call manager connecting calls between two air gapped networks in our test environment and is set to modify the caller ID of any calls that pass through it to show a specific DN (to indicate that this call came from the other network).
If the call is being routed from Location A to Location B to a Cisco VOIP Phone, the caller ID shows correctly as the specified DN. But if the call is being routed from Location A to Location B to a WAVE-connected device, the modified caller ID is ignored and the original number from Location A is shown. The issue persists in both directions (A to B / B to A) and does not change regardless of the call originating from a WAVE-connected device or a Cisco VOIP Phone.
Despite the convoluted nature of the connections, the point of failure seems to be with the outgoing SIP Trunk connected to the WAVE Management Server. Are there any specific trunk settings that could cause a SIP Trunk to ignore a masked caller ID, but for native Cisco VOIP devices to accept it?
