SIP Update Message to Lync (Network Steve Forum)

SIP Update Message to Lync

I am integrating an Avaya with Lync (through direct SIP) and everything is working fine except on trasnferred calls to Lync. The Avaya is sending a SIP update message with the original caller's P-Asserted-Identity, and the mediation server is receiving and repsonding with a 200OK...however, the mediation server doesn't seem to be sending that update onto the lync client and the client doesn't have the correct caller-id and name. Instead of the original callers name and number appearing on the lync client, the person who transferred the call is showing up??

I wasn't sure if this was a bug or just not supported yet?...or something that needs to be configured?? There isn't much out there on SIP updates messages in Lync.

Thanks!!

-Sean

December 8th, 2011 6:38am

Hi,Sean,

Do you mean the call can be transferred successfully to Lync user but the caller ID is showed as the one who transfer the calling instead of the original caller ID ,right?Per my knownledge it should show the original caller ID.

Would you please check if you disabled SIP refer and Media bypass on your mediation server?

And here are some configuration in Lync and Avaya integration for your reference.

http://blogs.technet.com/b/nexthop/archive/2011/05/04/integrating-microsoft-lync-server-2010-and-avaya-communications-manager-s8300.aspx

http://www.agileit.com/Blog/Lists/Posts/Post.aspx?ID=843

http://theucspot.wordpress.com/2011/04/11/avaya-cm-direct-sip-to-lync-scenario/

Regards,

Sharon

Free Windows Admin Tool Kit Click here and download it now

December 9th, 2011 7:43am

Hi,Sean,

How is your issue going on?

If there are any updates please do let me know.Thanks!

Regards,

Sharon

December 14th, 2011 10:36am

Hi Sharon,

I apologize, but I've been traveling and I haven't been able to test your suggestions. I did follow those guides initially druing setup before I posted my question but I will make sure to test your suggestions...I'm hoping to do so by the end of next week before the holiday.

Thanks!
Sean

Free Windows Admin Tool Kit Click here and download it now

December 17th, 2011 4:04am

Hi Sharon,

I gave your suggestions a try without any success. I have included a pic of the trace below. You can see that the phone is sending an update message to the Lync server, however the information in the update is not getting updated in the Lync client so the toast for the incoming call is showing the transferring party's ID (2005 Ventura, Robin) rather than the orignal caller's ID (2000 River, George). Any other suggestions you might have would be appreciated. Thanks and have a great holiday!

Sean

December 22nd, 2011 10:37pm

Here's a closer look:

Free Windows Admin Tool Kit Click here and download it now

December 22nd, 2011 10:40pm

Hello,

I know this post is a year old however I was wondering if you found a resolution for this?

I have come across the same identical issue as yourself except different IP PBX integration (I am using CUCM 8.5). I have been told by Microsoft that Lync does not honor the update messages from my IP PBX.

While I am waiting on them to find a resolution, I was wondering if you had any luck in your case?

December 28th, 2012 7:39pm

Bump.

I'm seeing the same issue as the others (I don't know why this thread is marked as "answered"). When performing a call transfer to a Lync user (the transferring phone is on CUCM 7.1), CUCM sends the original caller ID data to Lync when the CUCM user "releases" the call (directly connecting the original caller and the Lync user). See this in the two SIP messages (INVITE and UPDATE).

INVITE

TL_INFO(TF_PROTOCOL) [0]093C.16D0::09/25/2013-19:47:37.787.0016f4dd (S4,SipMessage.DataLoggingHelper:sipmessage.cs(686))[1439648545]
<<<<<<<<<<<<Incoming SipMessage c=[<SipTcpConnection_3EC4D6E>], 172.18.8.33:5060<-10.152.11.32:49353
INVITE sip:8292072@q-lyncfe-01.xyz.qa1:5060 SIP/2.0
FROM: "Joe Blow" <sip:2119@10.152.11.32>;tag=0b0729df-c8f3-40f1-8194-b348c6e639ac-24203344
TO: <sip:8292072@q-lyncfe-01.xyz.qa1>
CSEQ: 101 INVITE
CALL-ID: 52fd5800-24313dd9-1e6e-200b980a@10.152.11.32
MAX-FORWARDS: 70
VIA: SIP/2.0/TCP 10.152.11.32:5060;branch=z9hG4bK78892bfce0a4
ALLOW-EVENTS: presence, kpml
CONTACT: <sip:2119@10.152.11.32:5060;transport=tcp>
CONTENT-LENGTH: 0
DATE: Wed, 25 Sep 2013 19:47:37 GMT
EXPIRES: 180
SUPPORTED: timer,resource-priority,replaces
SUPPORTED: X-cisco-srtp-fallback
SUPPORTED: Geolocation
USER-AGENT: Cisco-CUCM7.1
ALLOW: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CALL-INFO: <sip:10.152.11.32:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
P-ASSERTED-IDENTITY: "Joe Blow" <sip:2119@10.152.11.32>
Min-SE: 1800
Remote-Party-ID: "Joe Blow" <sip:2119@10.152.11.32>;party=calling;screen=yes;privacy=off
Session-Expires: 1800
------------EndOfIncoming SipMessage

UPDATE

UPDATE sip:Q-LYNCFE-01.xyz.qa1:5060;maddr=172.18.8.33;transport=Tcp SIP/2.0
FROM: "Joe Blow" <sip:2119@10.152.11.32>;tag=0b0729df-c8f3-40f1-8194-b348c6e639ac-24203344
TO: <sip:8292072@q-lyncfe-01.xyz.qa1>;tag=ffc9958fa9
CSEQ: 102 UPDATE
CALL-ID: 52fd5800-24313dd9-1e6e-200b980a@10.152.11.32
MAX-FORWARDS: 70
VIA: SIP/2.0/TCP 10.152.11.32:5060;branch=z9hG4bK788a3852b3c3
ALLOW-EVENTS: presence, kpml
CONTACT: <sip:2119@10.152.11.32:5060;transport=tcp>
CONTENT-LENGTH: 0
DATE: Wed, 25 Sep 2013 19:47:37 GMT
SUPPORTED: timer,resource-priority,replaces
USER-AGENT: Cisco-CUCM7.1
ALLOW: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
P-ASSERTED-IDENTITY: <sip:6175551234@10.152.11.32>
Remote-Party-ID: <sip:6175551234@10.152.11.32>;party=calling;screen=yes;privacy=off
------------EndOfIncoming SipMessage

However, the Lync client never gets an update so it continues to show just the transferring caller, not the original number.

Trunk configuration is shown below:

Identity                            : Global
OutboundTranslationRulesList        : {}
SipResponseCodeTranslationRulesList : {}
Description                         : 
ConcentratedTopology                : True
EnableBypass                        : False
EnableMobileTrunkSupport            : False
EnableReferSupport                  : True
EnableSessionTimer                  : False
EnableSignalBoost                   : False
MaxEarlyDialogs                     : 20
RemovePlusFromUri                   : False
RTCPActiveCalls                     : True
RTCPCallsOnHold                     : True
SRTPMode                            : Required
EnablePIDFLOSupport                 : False

Edited by Hugh Kelley MTRL Thursday, September 26, 2013 3:30 PM

Free Windows Admin Tool Kit Click here and download it now

September 25th, 2013 8:09pm

Bump.

INVITE

TL_INFO(TF_PROTOCOL) [0]093C.16D0::09/25/2013-19:47:37.787.0016f4dd (S4,SipMessage.DataLoggingHelper:sipmessage.cs(686))[1439648545]
<<<<<<<<<<<<Incoming SipMessage c=[<SipTcpConnection_3EC4D6E>], 172.18.8.33:5060<-10.152.11.32:49353
INVITE sip:8292072@q-lyncfe-01.xyz.qa1:5060 SIP/2.0
FROM: "Joe Blow" <sip:2119@10.152.11.32>;tag=0b0729df-c8f3-40f1-8194-b348c6e639ac-24203344
TO: <sip:8292072@q-lyncfe-01.xyz.qa1>
CSEQ: 101 INVITE
CALL-ID: 52fd5800-24313dd9-1e6e-200b980a@10.152.11.32
MAX-FORWARDS: 70
VIA: SIP/2.0/TCP 10.152.11.32:5060;branch=z9hG4bK78892bfce0a4
ALLOW-EVENTS: presence, kpml
CONTACT: <sip:2119@10.152.11.32:5060;transport=tcp>
CONTENT-LENGTH: 0
DATE: Wed, 25 Sep 2013 19:47:37 GMT
EXPIRES: 180
SUPPORTED: timer,resource-priority,replaces
SUPPORTED: X-cisco-srtp-fallback
SUPPORTED: Geolocation
USER-AGENT: Cisco-CUCM7.1
ALLOW: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CALL-INFO: <sip:10.152.11.32:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
P-ASSERTED-IDENTITY: "Joe Blow" <sip:2119@10.152.11.32>
Min-SE: 1800
Remote-Party-ID: "Joe Blow" <sip:2119@10.152.11.32>;party=calling;screen=yes;privacy=off
Session-Expires: 1800
------------EndOfIncoming SipMessage

UPDATE

UPDATE sip:Q-LYNCFE-01.xyz.qa1:5060;maddr=172.18.8.33;transport=Tcp SIP/2.0
FROM: "Joe Blow" <sip:2119@10.152.11.32>;tag=0b0729df-c8f3-40f1-8194-b348c6e639ac-24203344
TO: <sip:8292072@q-lyncfe-01.xyz.qa1>;tag=ffc9958fa9
CSEQ: 102 UPDATE
CALL-ID: 52fd5800-24313dd9-1e6e-200b980a@10.152.11.32
MAX-FORWARDS: 70
VIA: SIP/2.0/TCP 10.152.11.32:5060;branch=z9hG4bK788a3852b3c3
ALLOW-EVENTS: presence, kpml
CONTACT: <sip:2119@10.152.11.32:5060;transport=tcp>
CONTENT-LENGTH: 0
DATE: Wed, 25 Sep 2013 19:47:37 GMT
SUPPORTED: timer,resource-priority,replaces
USER-AGENT: Cisco-CUCM7.1
ALLOW: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
P-ASSERTED-IDENTITY: <sip:6175551234@10.152.11.32>
Remote-Party-ID: <sip:6175551234@10.152.11.32>;party=calling;screen=yes;privacy=off
------------EndOfIncoming SipMessage

However, the Lync client never gets an update so it continues to show just the transferring caller, not the original number.

Trunk configuration is shown below:

Identity                            : Global
OutboundTranslationRulesList        : {}
SipResponseCodeTranslationRulesList : {}
Description                         : 
ConcentratedTopology                : True
EnableBypass                        : False
EnableMobileTrunkSupport            : False
EnableReferSupport                  : True
EnableSessionTimer                  : False
EnableSignalBoost                   : False
MaxEarlyDialogs                     : 20
RemovePlusFromUri                   : False
RTCPActiveCalls                     : True
RTCPCallsOnHold                     : True
SRTPMode                            : Required
EnablePIDFLOSupport                 : False

Edited by Hugh Kelley MTRL Thursday, September 26, 2013 3:30 PM

September 25th, 2013 8:09pm

Bump.

INVITE

TL_INFO(TF_PROTOCOL) [0]093C.16D0::09/25/2013-19:47:37.787.0016f4dd (S4,SipMessage.DataLoggingHelper:sipmessage.cs(686))[1439648545]
<<<<<<<<<<<<Incoming SipMessage c=[<SipTcpConnection_3EC4D6E>], 172.18.8.33:5060<-10.152.11.32:49353
INVITE sip:8292072@q-lyncfe-01.xyz.qa1:5060 SIP/2.0
FROM: "Joe Blow" <sip:2119@10.152.11.32>;tag=0b0729df-c8f3-40f1-8194-b348c6e639ac-24203344
TO: <sip:8292072@q-lyncfe-01.xyz.qa1>
CSEQ: 101 INVITE
CALL-ID: 52fd5800-24313dd9-1e6e-200b980a@10.152.11.32
MAX-FORWARDS: 70
VIA: SIP/2.0/TCP 10.152.11.32:5060;branch=z9hG4bK78892bfce0a4
ALLOW-EVENTS: presence, kpml
CONTACT: <sip:2119@10.152.11.32:5060;transport=tcp>
CONTENT-LENGTH: 0
DATE: Wed, 25 Sep 2013 19:47:37 GMT
EXPIRES: 180
SUPPORTED: timer,resource-priority,replaces
SUPPORTED: X-cisco-srtp-fallback
SUPPORTED: Geolocation
USER-AGENT: Cisco-CUCM7.1
ALLOW: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CALL-INFO: <sip:10.152.11.32:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
P-ASSERTED-IDENTITY: "Joe Blow" <sip:2119@10.152.11.32>
Min-SE: 1800
Remote-Party-ID: "Joe Blow" <sip:2119@10.152.11.32>;party=calling;screen=yes;privacy=off
Session-Expires: 1800
------------EndOfIncoming SipMessage

UPDATE

UPDATE sip:Q-LYNCFE-01.xyz.qa1:5060;maddr=172.18.8.33;transport=Tcp SIP/2.0
FROM: "Joe Blow" <sip:2119@10.152.11.32>;tag=0b0729df-c8f3-40f1-8194-b348c6e639ac-24203344
TO: <sip:8292072@q-lyncfe-01.xyz.qa1>;tag=ffc9958fa9
CSEQ: 102 UPDATE
CALL-ID: 52fd5800-24313dd9-1e6e-200b980a@10.152.11.32
MAX-FORWARDS: 70
VIA: SIP/2.0/TCP 10.152.11.32:5060;branch=z9hG4bK788a3852b3c3
ALLOW-EVENTS: presence, kpml
CONTACT: <sip:2119@10.152.11.32:5060;transport=tcp>
CONTENT-LENGTH: 0
DATE: Wed, 25 Sep 2013 19:47:37 GMT
SUPPORTED: timer,resource-priority,replaces
USER-AGENT: Cisco-CUCM7.1
ALLOW: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
P-ASSERTED-IDENTITY: <sip:6175551234@10.152.11.32>
Remote-Party-ID: <sip:6175551234@10.152.11.32>;party=calling;screen=yes;privacy=off
------------EndOfIncoming SipMessage

However, the Lync client never gets an update so it continues to show just the transferring caller, not the original number.

Trunk configuration is shown below:

Identity                            : Global
OutboundTranslationRulesList        : {}
SipResponseCodeTranslationRulesList : {}
Description                         : 
ConcentratedTopology                : True
EnableBypass                        : False
EnableMobileTrunkSupport            : False
EnableReferSupport                  : True
EnableSessionTimer                  : False
EnableSignalBoost                   : False
MaxEarlyDialogs                     : 20
RemovePlusFromUri                   : False
RTCPActiveCalls                     : True
RTCPCallsOnHold                     : True
SRTPMode                            : Required
EnablePIDFLOSupport                 : False

Edited by Hugh Kelley MTRL Thursday, September 26, 2013 3:30 PM

Free Windows Admin Tool Kit Click here and download it now

September 25th, 2013 8:09pm

Anybody had any luck with this? I am having the same issues as described above. We have Lync Server 2013 together with Cisco UC500. Interestingly we are seeing the caller ID update when a direct transfer is made but not when a consultative transfer is made in which case the transferring party's ID is still displayed. It leaves the person receiving the transferred call not knowing that the transfer has actually happened!

Any ideas would be welcome.

Thanks

John

October 16th, 2013 2:31pm

James,
Were you able to ever get this working? We are on Lync 2013 with CUCM 9.1 and are seeing the exact same issue.

Thanks in advance.

Free Windows Admin Tool Kit Click here and download it now

November 21st, 2013 5:56pm

Hi Guys,

I am having the same issue with my environment, I am sending the SIP update from my CUCM 8.6 but the lync Mediation server is accepting the message but its not reflecting in the lync end point

please suggest..

Thanks and Regards

P.Vishvak

May 22nd, 2015 3:18am

This topic is archived. No further replies will be accepted.