[SIPForum-discussion] lync inter-op

SAKCA, HALIT (HALIT) halit.sakca at alcatel-lucent.com
Mon Jun 4 23:01:59 UTC 2012


http://www.ietf.org/rfc/rfc3261.txt

r,
halit

From: discussion-bounces at sipforum.org [mailto:discussion-bounces at sipforum.org] On Behalf Of Jing Jiang
Sent: 04 June 2012 23:30
To: discussion at sipforum.org
Subject: [SIPForum-discussion] lync inter-op

I tried to connect my SIP client to a lync server via TLS, but lync complained my registration message. I was guessing Lync wasn't happy to my SIPS scheme - sips:xxxtest2 at xxx.xxx.com.

REGISTER sips:xxx.xxx.com:5061 SIP/2.0
Via: SIP/2.0/TLS 172.16.8.110:5063;branch=z9hG4bK1785731258;rport
From: "test2,xxx"<sips:xxxtest2 at xxx.xxx.com>;tag=3542038532
To: "test2,xxx"<sips:xxxtest2 at xxx.xxx.com>
CSeq: 1168232548 REGISTER
Max-Forwards: 70
Call-ID: 1146208246 at 172.16.8.110
Contact: <sips:xxxtest2 at 172.16.8.110:5063;transport=tcp>
Expires: 3600
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,INFO,SUBSCRIBE,NOTIFY,REFER,MESSAGE,UPDATE
User-Agent: xxx/1.0.0.56
Content-Length: 0


SIP/2.0 400 Malformed or unknown SIP URI scheme
From: "test1,xxx"<sips:xxxtest1 at xxx.xxx.com>;tag=2927246513
To: "test1,xxx"<sips:xxxtest1 at xxx.xxx.com>
Call-ID: 4068541528 at 172.16.8.110
CSeq: 1168232548 REGISTER
Via: SIP/2.0/TLS 172.16.8.110:5061;branch=z9hG4bK3062443857;rport
ms-diagnostics: 1018;reason="Parsing failure";source="xxx.xxx.com"
Server: RTC/4.0
Content-Length: 0


Thanks,

Stephen

________________________________
BIAMP SYSTEMS EMAIL NOTICE The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system.
________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20120605/6d4b8bc6/attachment-0002.html>


More information about the discussion mailing list