Hi all,

One of my Lync clients is dropping audio calls with the error and source IDs stated in the title of this question. The user is able to do presence, IM and sharing, but is unable to establish audio/video calls. Does anyone knows what this error is?

On the other hand, i'm looking for a central repository of Lync client errors. Do we have something like that somewhere?

regards,

You should use the Lync Debugger & Snooper tool to look at specific Errors.
You can use Client debugging (via options) & Server debugging via Debugger Tool
(The general client errors don't say much)

Do you have any more information about the environment.  The error code 52063 means "Unsupported session description" and is usally caused by a messed up RCC configuration. But it can be caused by other things as well. Will need to need more information first though.

The environment is a Standard Edition deployment, with one Monitoring server and one internet facing Edge. There's no intetgration with their PBX, so no RCC options are configured. AD in 2008 native mode and all servers are WS 2008R2

regards,

Did anyone find a resolution to this problem. I have a standard edition server and can signing from all of my remote sites except for one. and this is the error I get. Everything works but video and audio do not. I suspect the issue is related to a configuration on the router at the remote site but my network engineer says the codecs are configured configured. Below are two logs entries from the debug.

 

 

TL_INFO(TF_PROTOCOL) [0]0ADC.1388::07/26/2011-19:19:34.331.00000084 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record

Trace-Correlation-Id: 1942058237

Instance-Id: 0000900B

Direction: incoming

Peer: 10.12.10.54:2035

Message-Type: response

Start-Line: SIP/2.0 488 Not Acceptable Here

From: "Steven Milian"<sip:smilian@property.com>;tag=d4e727354d;epid=f216c92448

To: "" <sip:msaintfleur@property.com>;epid=aa5a261afd;tag=9d4c44c6b2

CSeq: 1 INVITE

Call-ID: 6537dce5f7094e3ca2cee3c972732aa9

Via: SIP/2.0/TLS 10.1.3.119:5061;branch=z9hG4bK7042F69E.BD01B3942F09D496;branched=FALSE;ms-internal-info="ddVboYB1wsrXp5qbMQHiqhU0dY85KR49JrQUmeF5dBMUiUswG9YQ6fOAAA"

Via: SIP/2.0/TLS 10.2.28.74:53599;ms-received-port=53599;ms-received-cid=9500

User-Agent: UCCAPI/4.0.7577.0 OC/4.0.7577.0 (Microsoft Lync 2010)

Ms-client-diagnostics: 52063;reason="Unsupported session description"

Proxy-Authorization: TLS-DSK qop="auth", realm="SIP Communications Service", opaque="1D81EAC2", targetname="MDCVLYNC01.property.com", crand="fda3502a", cnum="94", response="20a7b2532c475d4cd413fec742303dd72c56f198"

Content-Length: 0

Message-Body: –

$$end_record

 

 

 

TL_INFO(TF_PROTOCOL) [0]0ADC.1388::07/26/2011-19:19:34.331.00000090 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record

Trace-Correlation-Id: 3039594973

Instance-Id: 0000900C

Direction: outgoing;source="local"

Peer: 10.12.10.54:2035

Message-Type: request

Start-Line: ACK sip:10.12.10.54:2035;transport=tls;ms-opaque=abbd5aefb0;ms-received-cid=8F00 SIP/2.0

From: "Steven Milian"<sip:smilian@property.com>;tag=d4e727354d;epid=f216c92448

To: "" <sip:msaintfleur@property.com>;epid=aa5a261afd;tag=9d4c44c6b2

CSeq: 1 ACK

Call-ID: 6537dce5f7094e3ca2cee3c972732aa9

Via: SIP/2.0/TLS 10.1.3.119:5061;branch=z9hG4bK7042F69E.BD01B3942F09D496;branched=FALSE

Authentication-Info: TLS-DSK qop="auth", opaque="1D81EAC2", srand="DD3827A5", snum="200", rspauth="7a36084f58ede9cfd76c607d3392c837872b175f", targetname="MDCVLYNC01.property.com", realm="SIP Communications Service", version=4

Max-Forwards: 70

Content-Length: 0

Server: http%3A%2F%2Fwww.microsoft.com%2FLCS%2FDefaultRouting

ms-diagnostics-public: 5012;reason="ACK is being generated on receipt of a failure final response for an INVITE forked by application";AppUri="http%3A%2F%2Fwww.microsoft.com%2FLCS%2FDefaultRouting"

Message-Body: –

$$end_record

 

 

Anyone can help? I have the same problem

This is very old post just updating so that some one get benefited. I also faced same issue and it got resolved after upgrading the Lync client. Please try upgrading the Lync client to check with new user windows profile

Regards,

Rajesha Rao