Re: [reSIProcate-users] reSIProcate with Lync

[Scott Godin <sgodin@xxxxxxxxxxxxxxx>]

If you trying to connect directly the LCS/OCS/Lync frontend server, then you are in for a world of hurt.  There are many SIP extensions used in these products that make communicating with their core a very difficult exercise (ie. NTLM authentication, mandatory header requirements, etc.).  It is possible with resiprocate, however you will need to make some modifications to the core stack to support everything.  Here are the Lync SIP Procotol specs to give you an idea:

http://msdn.microsoft.com/en-us/library/cc307432(v=office.12).aspx

Microsoft has created a Mediation Server to mediate between full standards based SIP to OCS/Lync flavoured SIP - however this server is only for audio calls.  If you need audio calling only this is definitely the way to go.

If you really want to communicate directly to the OCS/Lync core then I would recommend looking at using Microsoft's UCMA API:  http://msdn.microsoft.com/en-us/library/gg421023.aspx

Scott

2011/6/24 surasak sermluxananon <lancelot_derluke@xxxxxxxxxxx>

Hi,

I would like to ask a couple questions,

1. Are there anyone trying to connect to Lync Server with reSIProcate ?
2. Is the way connect lync same as LCS ?

I'm trying to connect one of my server application using reSIProcate to Lync and it gets error back following here :

(Access Edge log file)

TL_WARN(TF_COMPONENT) [0]0C30.0BC8::06/24/2011-03:25:02.406.00002192 (SIPStack,CBufferChain::Decrypt:BufferChain.cpp(3338))( 0000000002F8E7C0 ) Successfully decrypted a TLS packet containing zero bytes Returned S_FALSE
TL_INFO(TF_COMPONENT) [0]0C30.0C90::06/24/2011-03:25:34.997.00002193 (SIPStack,CSIPMessage::CacheConnectionFlags:SIPMessage.cpp(1677))[0]( 0000000003822D60 ) From client connection, CID [0x36400]
TL_INFO(TF_PROTOCOL) [0]0C30.0C90::06/24/2011-03:25:34.997.00002194 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
Trace-Correlation-Id: 1747851163
Instance-Id: 0001A8BA
Direction: incoming;! source="external edge";destination="internal edge"
Peer: 10.42.60.31:54813
Message-Type: request
Start-Line: REGISTER sip:sip.xxxxxxxx.xxxxxxx.com:443;transport=TLS SIP/2.0
From: <sip:lync.01@xxxxxxxxxxxxxxxxxxxx>;tag=d00e576f;epid=266e7c5d
To: <sip:lync.01@xxxxxxxxxxxxxxxxxxxx>
CSeq: 1 REGISTER
Call-ID: NzExYWU1ZjVkODMzNzk1NDVhNGMxODhlNGM4NDM1NzQ.
Via: SIP/2.0/TLS 10.42.60.31:54759;branch=z9hG4bK-d8754z-227d1700061b5e7b-1---d8754z-;rport
Max-Forwards: 70
Contact: <sip:10.42.60.31:54759;transport=TLS>;methods="INVITE, MESSAGE, INFO, SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER, BENOTIFY";proxy=replace
Supported: com.microsoft.msrtc.presence, adhoclist, eventlist, ms-forking, replaces, norefersub
User-Agent: SIP/3.0 (IMCCM/10.0)
Event: registration
Allow-Events: presence
ms-keep-alive: UAC;hop-hop=yes
Content-Length: 0
Message-Body: –
$$end_record

TL_ERROR(TF_COMPONENT) [0]0C30.0C90::06/24/! 2011-03:25:34.997.00002195 (SIPStack,CSocketTransitionList::ProcessList:SocketTransitionList.cpp(314))( 0000000000381FC0 ) Connection 0000000002F92B90 is too old: 1902592156.
TL_INFO(TF_CONNECTION) [0]0C30.0C90::06/24/2011-03:25:34.997.00002196 (SIPStack,SIPAdminLog::TraceConnectionRecord:SIPAdminLog.cpp(164))$$begin_record
LogType: connection
Severity: information
Text: TLS connection closed
Local-IP: 192.168.239.232:443
Peer-IP: 10.42.60.31:54813
Connection-ID: 0x36400
Transport: TLS
$$end_record

TL_ERROR(TF_CONNECTION) [0]0C30.0C90::06/24/2011-03:25:34.998.00002197 (SIPStack,SIPAdminLog::TraceConnectionRecord:SIPAdminLog.cpp(160))$$begin_record
LogType: connection
Severity: error
Text: Connection was closed because the peer failed to provide valid credentials within establishing timeout
Local-IP: 192.168.239.232:443
Peer-IP: 10.42.60.31:54813
Connection-ID: 0x36400
Transport: TLS
$$end_record

Please advise, many thanks
Surasak.

_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/