Calling party SIP URI's domain portion is changed to CUCM IP - How to avoid it

[majeed002]

When a call is received especially through SIP trunk, calling party SIP URI's domain portion is getting changed to @cucmip.  This blocks the user from returning the call using the recent calls. 

How to disable CUCM from changing the domain portion of the calling party identification.  Other end of the SIP trunk is a expressway and the exp call history shows that the source has the full sip URI correctly.  It seems CUCM is changing the domain portion.  Am I missing any configuration.

[Aseem Anand]

Hi,

What is the complete call flow? Incoming call to CUCM from expressway? If yes then where is it suppose to forward to? Have you configured any SIP route pattern on CUCM?

Refer to the link below:

http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/expressway/config_guide/X8-1/Cisco-Expressway-SIP-Trunk-to-Unified-CM-Deployment-Guide-CUCM-8-9-and-X8-1.pdf

Aseem

[majeed002]

Yes, it is incoming call to CUCM from expressway (originated from Skype for Business) and terminates at SX20 video endpoint.  Yes, there are SIP route patterns for outgoing calls in CUCM to expressways.  There are no issues with outgoing caller identification. 

The issue is only for incoming calls to SX20 where it changes the user@domain.com to user@100.100.100.100 where 100.100.100.100 is the cucm ip.  Because of this, we cannot use the missed/received call information to dial the caller back.

[Jonathan Schulenberg · Accepted solution]

The SIP Profile assigned to the SX20 and Expressway-C should be configured to Use Fully Qualified Domain Name in SIP Requests.

[majeed002]

In the default sip profile, "Use Fully Qualified Name in SIP Requests" in unchecked.  I enabled this parameter and it starts working fine.  Thanks for the information.