cisco CME SIP trunk with Avaya caller-id issue

[Risat]

Hi, We have configured a SIP trunk from CME 12.1 to Avaya, we can see when the calls are made from Cisco to Avaya or Avaya to Cisco, the calling-party cannot see the caller-id (name of the called person on their phone)

ie, when A calls B, A can't see B's name on his (A's) phone. We have trunk to another Avaya from the same CME router, where we can see this caller-id once the call is connected.

 call flow is Cisco IP Phone > CUBE -- SIP -- Avaya > Avaya IP Phone and viceversa.

[Ayodeji Okanlawon]

We need to see the sip mesaage logs to know if Avaya is sending the remote party id of the called phone.

please send the debug ccsip messages from the ccme router

[Risat]

Hi, thanks for your reply, please see the below snippet from the debug, we can see the remote-party-id is send. call is made from 200 to 100, and the user at 200 can't see the name of the person 100. Instead of the name 'User-B' he is seeing the SIP-ID 2DA01-BAC@x.x.x.46

SIP/2.0 180 Ringing
Via: SIP/2.0/UDP x.x.x.1:5060;branch=z9hG4bK1E98307
From: "User-A" <sip:200@x.x.x.1>;tag=886E97CE-1CB4
To: <sip:100@x.x.x.46>;tag=74860b70734500a503df6ddd-7dab4f32
Call-ID: CE3DFA78-C0C111E8-9B8CFE3E-A9D92090@x.x.x.1
Session-ID: 48abb18e00105000a00074860b707345;remote=d8f5573584b65471b2a99f13663efc9a
Date: Wed, 26 Sep 2018 12:51:59 GMT
CSeq: 101 INVITE
Server: Cisco-CP8841/11.7.1
Contact: <sip:2DA01-BAC@x.x.x.46:5060;transport=udp>;+u.sip!devicename.ccm.cisco.com="SEP74860B7XXXXX"
Allow: ACK,BYE,CANCEL,INVITE,NOTIFY,OPTIONS,REFER,REGISTER,UPDATE,SUBSCRIBE,INFO
Remote-Party-ID: "User-B" <sip:100@x.x.x.1>;party=called;id-type=subscriber;privacy=off;screen=yes
Supported: replaces,join,sdp-anat,norefersub,resource-priority,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-7.0.0,X-cisco-xsi-8.5.1
Allow-Events: kpml,dialog
Content-Length: 0

[Ayodeji Okanlawon]

Okay this suggests that your CCME is using the contact header for CLI display rather than the remote-party-id

Can you try this please..

conf t

sip-ua

remote-party-id

This should be enabled by default..but I am not sure why the gateway is behaving this way..But try the command above and check again