Plantronics + Polycom. Now together as Poly Logo

SoundPointIP Lync compatible phones and caller id

Occasional Contributor

SoundPointIP Lync compatible phones and caller id

In our trial of Lync 2010 with SoundPointIP phones running UC4.0.1, we are seeing that PSTN calls from Polycom phones are not sending correct caller id.

 

A call from the Lync 2010 client to PSTN looks shows this in the Lync Logging tool:

 

 

 

Trace-Correlation-Id: 2692236500
Instance-Id: 000162AA
Direction: incoming
Peer: ###.###.###.###:4180
Message-Type: request
Start-Line: INVITE sip:+19165551212@losrios.edu;user=phone SIP/2.0
From: <sip:**********@losrios.edu>;tag=a90bbe6ddf;epid=de04be692f
To: <sip:+19165551212@losrios.edu;user=phone>
CSeq: 1 INVITE
Call-ID: 639b44e906874b28b5dc0c3a67924162
Via: SIP/2.0/TLS ###.###.###.###:4180
Max-Forwards: 70
Contact: <sip:**********@losrios.edu;opaque=user:epid:z1Tgmq0J3FyhXAWRsAv5FQAA;gruu>
User-Agent: UCCAPI/4.0.7577.4051 OC/4.0.7577.4051 (Microsoft Lync 2010)
Supported: ms-dialog-route-set-update
Ms-Conversation-ID: AczmnNumgsQPu7vjSBWCWoZum3HZVg==
Supported: timer
Supported: histinfo
Supported: ms-safe-transfer
Supported: ms-sender
Supported: ms-early-media
Supported: 100rel
ms-keep-alive: UAC;hop-hop=yes
Allow: INVITE, BYE, ACK, CANCEL, INFO, UPDATE, REFER, NOTIFY, BENOTIFY, OPTIONS
ms-subnet: 165.196.25.128
Accept-Language: en-US
ms-endpoint-location-data: NetworkScope;ms-media-location-type=Intranet
P-Preferred-Identity: <sip:william@losrios.edu>, <tel:+19165552020>
Supported: replaces
Supported: ms-conf-invite
Proxy-Authorization: ----------
Content-Type: multipart/alternative;boundary="----=_NextPart_000_0CDA_01CCE659.CDAB86B0"
Content-Length: 2988
Message-Body: ------=_NextPart_000_0CDA_01CCE659.CDAB86B0
Content-Type: application/sdp
Content-Transfer-Encoding: 7bit
Content-ID: <86200ebcc9c94a02b7a7d41bba61e3da@losrios.edu>
Content-Disposition: session; handling=optional; ms-proxy-2007fallback

 

tel:+19165552020



I bolded the part in the SIP header where the source caller id appears.The Mediation Service sends the INVITE to our gateway with the following header:

 

 

 

INVITE sip:919165551212@do-mediant.losrios.edu;user=phone SIP/2.0
FROM: "Williams, Mark"<sip:+19165552020@lrccd-lync01.lrccd.ad.losrios.edu;user=phone>;epid=4E5609329C;tag=cbf9dc2499
TO: <sip:919165551212@do-mediant.losrios.edu;user=phone>
CSEQ: 6584 INVITE
CALL-ID: 411ba67e-d5de-487e-9918-e4c4c61ea11d
MAX-FORWARDS: 70
VIA: SIP/2.0/TLS ###.###.###.###:57169;branch=z9hG4bKb7787fb7
CONTACT: <sip:LYNC01.LRCCD.ad.losrios.edu:5067;transport=Tls;ms-opaque=b40124991eeacbd7>
CONTENT-LENGTH: 529
SUPPORTED: 100rel
USER-AGENT: RTCC/4.0.0.0 MediationServer
CONTENT-TYPE: application/sdp
ALLOW: ACK
Allow: CANCEL,BYE,INVITE,PRACK,UPDATE

 

sip:+19165552020

 

 

Now, if the same call is dialed from a SoundPointIP phone, the header looks like this:

 

Trace-Correlation-Id: 2732835996
Instance-Id: 000162D8
Direction: incoming
Peer: 172.16.0.12:57343
Message-Type: request
Start-Line: INVITE sip:+19165551212@losrios.edu;user=phone;transport=tls SIP/2.0
From: "*********" <sip:***************@losrios.edu>;tag=8FBB1A4A-7DDB66D3;epid=0004f2261123
To: <sip:+19165551212@losrios.edu;user=phone>
CSeq: 1 INVITE
Call-ID: c253b511-efd808f2-dc06e5bb@172.16.0.12
Via: SIP/2.0/TLS 172.16.0.12:57343;branch=z9hG4bKd89a91077F2AC9D8
Contact: <sip:william@losrios.edu;opaque=user:epid:yvmQ23TpfF2LDDPS2v-tyAAA;gruu>
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER
User-Agent: PolycomSoundPointIP-SPIP_450-UA/4.0.1.13681
Accept-Language: en
P-Asserted-Identity: "********" <sip:***********@losrios.edu>
Supported: 100rel,replaces
Allow-Events: conference,talk,hold
Authorization: ---------
Max-Forwards: 70
Content-Type: application/sdp
Content-Length: 386

 

 

The Mediation Server sends the INVITE to the gateway like this:

 

INVITE sip:919165551212@do-mediant.losrios.edu;user=phone SIP/2.0
FROM: "Williams, Mark"<sip:********@losrios.edu>;epid=4E5609329C;tag=5c1fe329e
TO: <sip:919165551212@do-mediant.losrios.edu;user=phone>
CSEQ: 6586 INVITE
CALL-ID: 9da128ad-d93f-43db-b1b8-005af3c9874b
MAX-FORWARDS: 70
VIA: SIP/2.0/TLS ###.###.###.###:57183;branch=z9hG4bKd5f1b2c2
CONTACT: <sip:LYNC01.LRCCD.ad.losrios.edu:5067;transport=Tls;ms-opaque=b40124991eeacbd7>
CONTENT-LENGTH: 529
SUPPORTED: 100rel
USER-AGENT: RTCC/4.0.0.0 MediationServer
CONTENT-TYPE: application/sdp
ALLOW: ACK
Allow: CANCEL,BYE,INVITE,PRACK,UPDATE

 

 

I'm not sure where the problem really lies at here. The Lync server should know that this is a PSTN call and put in my defined TEL number in the header, but it doesn't. Any ideas?

 

-Mark Williams

Message 1 of 2
1 REPLY 1
Polycom Employee & Community Manager

Re: SoundPointIP Lync compatible phones and caller id

Hello Mark,

 

I formatted your post using code tags so it can be read a bit easier.

 

The Polycom LYNC Integration implemented in the UCS 4.0.1 is very basic and relies on your LYNC Installation normalization rules.

 

Please work with the Microsoft LYNC Community on this as full LYNC Dialplan integration will only be implemented on a later release sometime this year.

 

Best Regards

 

Steffen Baier

 

Polycom Global Services




<======== Signature / Disclaimer ========>
Please be aware:For questions about the type of support to expect please check here

Please also ensure you always check the VoIP , Video Endpoint , Skype for Business , PSTN or RPM FAQ's

Please remember, if you see a post that helped you , and it answers your question, please mark it as an "Accept as Solution".

The title Polycom Employee & Community Manager is an automatic setting within the community and any forum reply or post is based upon my personal experience and does not reflect the opinion or view of my employer.
Poly employee participation within this community is not mandatory and any post or FAQ article provided by myself is done either during my working hours or outside working hours, in my private time, and maybe answered on weekends, bank holidays or personal holidays.
Message 2 of 2