This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Remove From My Forums

No Voice when using the Snom m9r with Lync 2010

Question

Sign in to vote

Sign in to vote

Hi,

I hope somebody can help me or give me some advice!

Currently configuring a second site within Lync where I need around three cordless devices. Looked at the Polycom Kirk devices and nearly fell off my chair when I saw the price. So now I've calmed down, thought I would look at the Snom m9. I know it's not Lync compatible but just needs to be able to answer calls.

I have downloaded and installed the latest firmware for the device (9.6.2a) for both the base and handset.

I can get the device to sign into Lync with no errors, the problem comes when using the device.

When a call is made from the phone, any user is engaged. The user gets a missed call notification but their phone never rings.

When a call comes to the phone, it rings fine, but once answered it just cuts off.

------------------------------------------------------------------

In the log I get the following:

2012/09/17 16:03:37 [SIP-Call:5]: SIP Tx tls:192.168.2.139:5061:

ACK sip:dhearne@dalebrook.com SIP/2.0
Via: SIP/2.0/TLS 192.168.3.42:3935;branch=z9hG4bK-0vc5pf;rport
From: "Display" <sip:display@dalebrook.com>;tag=9yr9km;epid=00041330949F1
To: "sip:dhearne@dalebrook.com" <sip:dhearne@dalebrook.com>;tag=8D1337649114D325492987891EA620B7
Call-ID: cbba0235860190be30ebc30d45045121
CSeq: 403009966 ACK
Max-Forwards: 70
Contact: <sip:display@dalebrook.com;opaque=user:epid:y3bhhinYf1-XdVCqxZso8wAA;gruu>
Authorization: NTLM qop="auth", realm="SIP Communications Service", opaque="02C21564", targetname="DALESSLYN01.dalebrook.ads", crand="00b8e782", cnum="11", response="01000000efcea4e67661ab2164000000"
Content-Length: 0

2012/09/17 16:03:37 [SIP-Call:5]: fixed 0 msg.code 480

2012/09/17 16:03:37 [SIP-Call:5]: SIP Rx tls:192.168.2.139:5061:

SIP/2.0 480 Temporarily Unavailable
Authentication-Info: NTLM qop="auth", opaque="02C21564", srand="1D5AF220", snum="20", rspauth="01000000f22df79d710a015764000000", targetname="DALESSLYN01.dalebrook.ads", realm="SIP Communications Service", version=4
Via: SIP/2.0/TLS 192.168.3.42:3935;branch=z9hG4bK-0vc5pf;rport;ms-received-port=3935;ms-received-cid=30E1F00
From: "Display" <sip:display@dalebrook.com>;tag=9yr9km;epid=00041330949F1
To: "sip:dhearne@dalebrook.com" <sip:dhearne@dalebrook.com>;tag=8D1337649114D325492987891EA620B7
Call-ID: cbba0235860190be30ebc30d45045121
CSeq: 403009966 INVITE
ms-diagnostics: 15030;reason="Failed to route to Exchange Server";source="DALESSLYN01.dalebrook.ads";dialplan="Dalebrook.dalebrook.ads";appName="ExumRouting"
Server: ExumRouting/4.0.0.0
Content-Length: 0

2012/09/17 16:03:37 [General:7]: TLS is set

2012/09/17 16:03:37 [SIP-Call:5]: Call 0 route cleared

2012/09/17 16:03:37 [SIP-Call:5]: SIP Rx tls:192.168.2.139:5061:

SIP/2.0 199 Early Dialog Terminated
Authentication-Info: NTLM qop="auth", opaque="02C21564", srand="3A1177CC", snum="19", rspauth="01000000da58671d5027975464000000", targetname="DALESSLYN01.dalebrook.ads", realm="SIP Communications Service", version=4
Content-Length: 0
Via: SIP/2.0/TLS 192.168.3.42:3935;branch=z9hG4bK-0vc5pf;rport;ms-received-port=3935;ms-received-cid=30E1F00
From: "Display" <sip:display@dalebrook.com>;tag=9yr9km;epid=00041330949F1
Call-ID: cbba0235860190be30ebc30d45045121
CSeq: 403009966 INVITE
To: "sip:dhearne@dalebrook.com" <sip:dhearne@dalebrook.com>;tag=8D1337649114D325492987891EA620B7
Server: http%3A%2F%2Fwww.microsoft.com%2FLCS%2FDefaultRouting(Microsoft Lync Server 2010 4.0.7577.190)

2012/09/17 16:03:37 [General:7]: TLS is set

2012/09/17 16:03:37 [SIP-Call:5]: Call 0 route cleared

2012/09/17 16:03:37 [SIP-Call:5]: SIP Rx tls:192.168.2.139:5061:

SIP/2.0 101 Diagnostics
Authentication-Info: NTLM qop="auth", opaque="02C21564", srand="A6D6DBEB", snum="18", rspauth="01000000194885e1cb869e3864000000", targetname="DALESSLYN01.dalebrook.ads", realm="SIP Communications Service", version=4
Via: SIP/2.0/TLS 192.168.3.42:3935;branch=z9hG4bK-0vc5pf;rport;ms-received-port=3935;ms-received-cid=30E1F00
From: "Display" <sip:display@dalebrook.com>;tag=9yr9km;epid=00041330949F1
To: "sip:dhearne@dalebrook.com" <sip:dhearne@dalebrook.com>
Call-ID: cbba0235860190be30ebc30d45045121
CSeq: 403009966 INVITE
ms-diagnostics: 15034;reason="Failed to route to Exchange Unified Messaging Server";source="DALESSLYN01.dalebrook.ads";dialplan="Dalebrook.dalebrook.ads";umserver="DALESSEXH01.dalebrook.ads";responsecode="488";appName="ExumRouting"
Server: ExumRouting/4.0.0.0
Content-Length: 0

2012/09/17 16:03:37 [General:7]: TLS is set

2012/09/17 16:03:37 [SIP-Call:5]: Call 0 route cleared

2012/09/17 16:03:37 [SIP-Call:5]: SIP Rx tls:192.168.2.139:5061:

SIP/2.0 180 Ringing
Authentication-Info: NTLM qop="auth", opaque="02C21564", srand="49AC7868", snum="17", rspauth="0100000013f0957c9b3e486764000000", targetname="DALESSLYN01.dalebrook.ads", realm="SIP Communications Service", version=4
Via: SIP/2.0/TLS 192.168.3.42:3935;branch=z9hG4bK-0vc5pf;rport;ms-received-port=3935;ms-received-cid=30E1F00
FROM: "Display"<sip:display@dalebrook.com>;tag=9yr9km;epid=00041330949F1
TO: "sip:dhearne@dalebrook.com"<sip:dhearne@dalebrook.com>;tag=6d26dfb56e;epid=10881C7335
CSEQ: 403009966 INVITE
CALL-ID: cbba0235860190be30ebc30d45045121
RECORD-ROUTE: <sip:DALESSLYN01.dalebrook.ads:5061;transport=tls;opaque=state:F:Ci.R30e1f00;lr;ms-route-sig=hjVUafiglc1ZV_Dw1EnutL6ruPkgnXzojDe0rbUEEeL73cnIffLktPfQAA>
CONTACT: <sip:DALESSEXH01.dalebrook.ads:5065;transport=Tls>;automata;text;audio;video;image
CONTENT-LENGTH: 0
ALLOW: UPDATE
ALLOW: PRACK
P-ASSERTED-IDENTITY: <sip:dhearne@dalebrook.com>
SERVER: RTCC/3.5.0.0 MSExchangeUM/14.01.0289.001

2012/09/17 16:03:37 [General:7]: TLS is set

2012/09/17 16:03:37 [SIP-Call:5]: Call 0 route cleared

2012/09/17 16:03:37 [SIP-Call:5]: SIP Rx tls:192.168.2.139:5061:

SIP/2.0 101 Diagnostics
Authentication-Info: NTLM qop="auth", opaque="02C21564", srand="07F38D2C", snum="16", rspauth="01000000ad123d0e23791b4564000000", targetname="DALESSLYN01.dalebrook.ads", realm="SIP Communications Service", version=4
Via: SIP/2.0/TLS 192.168.3.42:3935;branch=z9hG4bK-0vc5pf;rport;ms-received-port=3935;ms-received-cid=30E1F00
From: "Display" <sip:display@dalebrook.com>;tag=9yr9km;epid=00041330949F1
To: "sip:dhearne@dalebrook.com" <sip:dhearne@dalebrook.com>
Call-ID: cbba0235860190be30ebc30d45045121
CSeq: 403009966 INVITE
ms-diagnostics: 15032;reason="Re-directing request to the destination in 302";source="DALESSLYN01.dalebrook.ads";dialplan="Dalebrook.dalebrook.ads";umserver="DALESSEXH01.dalebrook.ads";nexttarget="DALESSEXH01.dalebrook.ads";routingtype="Routing to UM for voice mail deposit";appName="ExumRouting"
Server: ExumRouting/4.0.0.0
Content-Length: 0

2012/09/17 16:03:37 [General:7]: TLS is set

2012/09/17 16:03:37 [SIP-Call:5]: Call 0 route cleared

2012/09/17 16:03:37 [SIP-Call:5]: SIP Rx tls:192.168.2.139:5061:

SIP/2.0 101 Diagnostics
Authentication-Info: NTLM qop="auth", opaque="02C21564", srand="FF8CD4BB", snum="15", rspauth="01000000b64f3a14a6e2aa1764000000", targetname="DALESSLYN01.dalebrook.ads", realm="SIP Communications Service", version=4
Via: SIP/2.0/TLS 192.168.3.42:3935;branch=z9hG4bK-0vc5pf;rport;ms-received-port=3935;ms-received-cid=30E1F00
From: "Display" <sip:display@dalebrook.com>;tag=9yr9km;epid=00041330949F1
To: "sip:dhearne@dalebrook.com" <sip:dhearne@dalebrook.com>
Call-ID: cbba0235860190be30ebc30d45045121
CSeq: 403009966 INVITE
ms-diagnostics: 15010;reason="Routing to UM for voice mail deposit";source="DALESSLYN01.dalebrook.ads";dialplan="Dalebrook.dalebrook.ads";umserver="DALESSEXH01.dalebrook.ads";appName="ExumRouting"
Server: ExumRouting/4.0.0.0
Content-Length: 0

2012/09/17 16:03:37 [General:7]: TLS is set

2012/09/17 16:03:37 [SIP-Call:5]: Call 0 route cleared

2012/09/17 16:03:37 [SIP-Call:5]: SIP Rx tls:192.168.2.139:5061:

SIP/2.0 181 Progress Report
Authentication-Info: NTLM qop="auth", opaque="02C21564", srand="D0FC67E2", snum="14", rspauth="01000000b95c6853ed62969964000000", targetname="DALESSLYN01.dalebrook.ads", realm="SIP Communications Service", version=4
Content-Length: 0
Via: SIP/2.0/TLS 192.168.3.42:3935;branch=z9hG4bK-0vc5pf;rport;ms-received-port=3935;ms-received-cid=30E1F00
From: "Display" <sip:display@dalebrook.com>;tag=9yr9km;epid=00041330949F1
To: "sip:dhearne@dalebrook.com" <sip:dhearne@dalebrook.com>
Call-ID: cbba0235860190be30ebc30d45045121
CSeq: 403009966 INVITE
Server: InboundRouting/4.0.0.0
History-Info: <sip:dhearne@dalebrook.com>;index=1;ms-retarget-reason=forwarding
ms-diagnostics: 13007;reason="Request was proxied to an application.";source="DALESSLYN01.dalebrook.ads";targetApp="voicemail";appName="InboundRouting"

2012/09/17 16:03:37 [General:7]: TLS is set

2012/09/17 16:03:37 [SIP-Call:5]: Call 0 route cleared

2012/09/17 16:03:37 [SIP-Call:5]: SIP Rx tls:192.168.2.139:5061:

SIP/2.0 101 Progress Report
Authentication-Info: NTLM qop="auth", opaque="02C21564", srand="112E30F4", snum="13", rspauth="010000002fe3b60e05897bdd64000000", targetname="DALESSLYN01.dalebrook.ads", realm="SIP Communications Service", version=4
Content-Length: 0
Via: SIP/2.0/TLS 192.168.3.42:3935;branch=z9hG4bK-0vc5pf;rport;ms-received-port=3935;ms-received-cid=30E1F00
From: "Display" <sip:display@dalebrook.com>;tag=9yr9km;epid=00041330949F1
To: "sip:dhearne@dalebrook.com" <sip:dhearne@dalebrook.com>
Call-ID: cbba0235860190be30ebc30d45045121
CSeq: 403009966 INVITE
ms-diagnostics: 13005;reason="Request was proxied to one or more additional targets";source="DALESSLYN01.dalebrook.ads";appName="InboundRouting"
Server: InboundRouting/4.0.0.0

2012/09/17 16:03:37 [General:7]: TLS is set

2012/09/17 16:03:37 [SIP-Call:5]: Call 0 route cleared

2012/09/17 16:03:37 [SIP-Call:5]: SIP Rx tls:192.168.2.139:5061:

SIP/2.0 101 Progress Report
Authentication-Info: NTLM qop="auth", opaque="02C21564", srand="489D3F34", snum="12", rspauth="01000000fe37c1323076e31d64000000", targetname="DALESSLYN01.dalebrook.ads", realm="SIP Communications Service", version=4
Content-Length: 0
Via: SIP/2.0/TLS 192.168.3.42:3935;branch=z9hG4bK-0vc5pf;rport;ms-received-port=3935;ms-received-cid=30E1F00
From: "Display" <sip:display@dalebrook.com>;tag=9yr9km;epid=00041330949F1
To: "sip:dhearne@dalebrook.com" <sip:dhearne@dalebrook.com>
Call-ID: cbba0235860190be30ebc30d45045121
CSeq: 403009966 INVITE
ms-diagnostics: 13004;reason="Request was proxied to one or more registered endpoints";source="DALESSLYN01.dalebrook.ads";Count="2";appName="InboundRouting"
Server: InboundRouting/4.0.0.0

2012/09/17 16:03:37 [General:7]: TLS is set

2012/09/17 16:03:37 [SIP-Call:5]: Call 1 generates ringback

2012/09/17 16:03:37 [SIP-Call:5]: Call 0 route cleared

2012/09/17 16:03:37 [SIP-Call:5]: SIP Rx tls:192.168.2.139:5061:

SIP/2.0 183 Session Progress
Authentication-Info: NTLM qop="auth", opaque="02C21564", srand="DFC792E1", snum="11", rspauth="01000000311599916ffd8bf764000000", targetname="DALESSLYN01.dalebrook.ads", realm="SIP Communications Service", version=4
Content-Length: 0
Via: SIP/2.0/TLS 192.168.3.42:3935;branch=z9hG4bK-0vc5pf;rport;ms-received-port=3935;ms-received-cid=30E1F00
From: "Display" <sip:display@dalebrook.com>;tag=9yr9km;epid=00041330949F1
To: "sip:dhearne@dalebrook.com" <sip:dhearne@dalebrook.com>
Call-ID: cbba0235860190be30ebc30d45045121
CSeq: 403009966 INVITE
Ms-Forking: Active
Server: http%3A%2F%2Fwww.microsoft.com%2FLCS%2FDefaultRouting(Microsoft Lync Server 2010 4.0.7577.190)

2012/09/17 16:03:37 [General:7]: TLS is set

2012/09/17 16:03:37 [SIP-Call:5]: fixed 0 msg.code 100

2012/09/17 16:03:37 [SIP-Call:5]: SIP Rx tls:192.168.2.139:5061:

SIP/2.0 100 Trying
Authentication-Info: NTLM qop="auth", opaque="02C21564", srand="B2CBCAC6", snum="10", rspauth="010000005930fd37f9558a9664000000", targetname="DALESSLYN01.dalebrook.ads", realm="SIP Communications Service", version=4
From: "Display" <sip:display@dalebrook.com>;tag=9yr9km;epid=00041330949F1
To: "sip:dhearne@dalebrook.com" <sip:dhearne@dalebrook.com>
Call-ID: cbba0235860190be30ebc30d45045121
CSeq: 403009966 INVITE
Via: SIP/2.0/TLS 192.168.3.42:3935;branch=z9hG4bK-0vc5pf;rport;ms-received-port=3935;ms-received-cid=30E1F00
Server: http%3A%2F%2Fwww.microsoft.com%2FLCS%2FInterClusterRouting
Content-Length: 0

2012/09/17 16:03:37 [DECT:8]: Rx 1019051100000305

2012/09/17 16:03:37 [SIP-Call:5]: SIP Tx tls:192.168.2.139:5061:

INVITE sip:dhearne@dalebrook.com SIP/2.0
Via: SIP/2.0/TLS 192.168.3.42:3935;branch=z9hG4bK-0vc5pf;rport
From: "Display" <sip:display@dalebrook.com>;tag=9yr9km;epid=00041330949F1
To: "sip:dhearne@dalebrook.com" <sip:dhearne@dalebrook.com>
Call-ID: cbba0235860190be30ebc30d45045121
CSeq: 403009966 INVITE
Max-Forwards: 70
Contact: <sip:display@dalebrook.com;opaque=user:epid:y3bhhinYf1-XdVCqxZso8wAA;gruu>
User-Agent: snom-m9/9.6.2-a
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, BENOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO
Allow-Events: talk, hold, refer, call-info
Supported: timer, 100rel, replaces, from-change, norefersub
P-Preferred-Identity: "Display" <sip:display@dalebrook.com>, <tel:+441376510101;ext=299>
Accept: application/sdp
Authorization: NTLM qop="auth", realm="SIP Communications Service", opaque="02C21564", targetname="DALESSLYN01.dalebrook.ads", crand="4f4f1014", cnum="10", response="0100000054a35e3da7ffc68164000000"
Content-Type: multipart/alternative;boundary="next_part_nr2vfkkxt71ramt0"
Content-Length: 2275

--next_part_nr2vfkkxt71ramt0
Content-Type: application/sdp
Content-Transfer-Encoding: 7bit
Content-Disposition: session; handling=optional; ms-proxy-2007fallback

---------------------------------------------------------------------------------------------------------

I know in the log it is saying:

ms-diagnostics: 15030;reason="Failed to route to Exchange Server";source="DALESSLYN01.dalebrook.ads";dialplan="Dalebrook.dalebrook.ads";appName="ExumRouting"

From what I can find from this, this can be caused when in Exchange, the dial plan is set to SIP Secured, rather than just Secured, but mine is already set to Secured.

Any help or advice would be really appreciated and I can't believe nobody does a Lync Cordless that is affordable!!

Regards,

Paul

Monday, September 17, 2012 3:12 PM

Answers

0

Sign in to vote
Thanks for your answers. I have already tried Snom support, but have not heard anything.

I have since looked with fresh eyes and have resolved this issue, due to the RTP Encryption.

In the SIP section of the Identity when logged onto the base unit, change the RTP Encryption to 'ON'. This changes the SIP Secured option as found in

http://wiki.snom.com/Settings/user_srtp

Works like a dream now!!
- Marked as answer by Paul Knock Wednesday, September 19, 2012 11:12 AM
Wednesday, September 19, 2012 11:12 AM

All replies

0

Sign in to vote

Hi,

Looks like it is the device issue. If you have another snom m9, please try again.

If still can not work, please post your question to snom forum that you can get more help.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Tuesday, September 18, 2012 7:18 AM
0

Sign in to vote

I'd rather go to snom support to get it resolved. http://www.snom.com/en/products/unified-communications/microsoft-lync-qualified-products/ could be the right place to start with.
Regards, Ram Ojha | Unified Communications Architect | www.ocspedia.com

Wednesday, September 19, 2012 2:28 AM
0

Sign in to vote
Thanks for your answers. I have already tried Snom support, but have not heard anything.

I have since looked with fresh eyes and have resolved this issue, due to the RTP Encryption.

In the SIP section of the Identity when logged onto the base unit, change the RTP Encryption to 'ON'. This changes the SIP Secured option as found in

http://wiki.snom.com/Settings/user_srtp

Works like a dream now!!
- Marked as answer by Paul Knock Wednesday, September 19, 2012 11:12 AM
Wednesday, September 19, 2012 11:12 AM
0

Sign in to vote

Just to note though, for OCS RTP Encryption needs to be set to 'OFF' which is what is documented within the Snom instructions for OCS/Lync. There was nothing to say this needs to be 'ON' for Lync though

Wednesday, September 19, 2012 11:14 AM
0

Sign in to vote

Great.. thanks for updating the thread.
Regards, Ram Ojha | Unified Communications Architect | www.ocspedia.com

Thursday, September 20, 2012 2:45 AM