RE: [reSIProcate] reSIProcate and LCS?
Chris,
Here are a few notes I have:
1. Microsoft charges $50K for access to their documentation on their
SIP "extensions".
2. LCS blocks REGISTER and SERVICE requests on Federation links.
3. I will be committing changes to DUM soon, that will allow you to
send (and receive) MESSAGE requests from an INVITE session.
4. I haven't actually tried TLS yet - so I can't help much there. I've
only played with INVITEs, MESSAGEs and REFERs - with limited success.
Sometime Communicator or LCS just refuses to process a message. The
message appears in the log, but is not responded to - and there are no
errors. The reason for this likely revolves around the epid parameter -
but I'm not sure.
Scott
-----Original Message-----
From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
Chris Rigg
Sent: Tuesday, August 16, 2005 5:56 PM
To: Sandeep Sharma
Cc: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [reSIProcate] reSIProcate and LCS?
Hi Sandeep,
I just responded to Scott with some info that may be useful to you. I
would love to compare notes with you. I'll be using the resip stack
quite extensively over the course of the next few months to try to
interoperate with LCS 2005 SP1 (which is what I have installed
currently). I'll likely be writing several programs similar to "limpc"
that will generate INVITEs, SUBSCRIBEs, NOTIFYs and MESSAGEs (though, as
you pointed out, 2005 SP1 only supports session mode -- but it does
support receipt of MESSAGEs w/in an already established session).
Ideally, I would get my hands on a detailed interface spec that would
make writing code to interoperate much easier on myself. I suspect such
an interface exists since MSFT claims they interoperate with AOL and
Yahoo in Federation mode -- obviously those 2 companies had something to
work from.
Chris
Sandeep Sharma wrote:
>I tried to make resip and LCS work together a while back. without much
>success. TLS is required. I have heard LCS 2005 SP1 has fixed a bunch
of
>federation related bugs but have not tried with it myself.
>
>One thing I do know is that page-mode instant messaging is not
>supported. MESSAGEs need to be sent inside an INVITE session.
>
>Chris, it might be interesting to exchange notes since I am going to
try
>testing against LCS 2005 SP1 soon.
>
>Thanks
>Sandeep
>
>On Tue, 2005-08-16 at 17:28 -0400, Scott Godin wrote:
>
>
>>Apparently to use "Federation Mode" you must use the TLS transport.
As
>>far as I know - no one has tried this with resip yet. Although it is
on
>>my list of things to try out. : )
>>
>>On the other hand - I have used resip to communicate with LCS by
setting
>>up the resip endpoint as a trusted node. Note: LCS does not support
>>UDP - so you must use a TCP transport. Don't expect to be able to
>>register with LCS though - since you need to implement those Microsoft
>>extensions that you mentioned (ie. Kerberos/NTLM Authentication
instead
>>of Digest).
>>
>>Scott
>>
>>-----Original Message-----
>>From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>[mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
>>Chris Rigg
>>Sent: Tuesday, August 16, 2005 5:21 PM
>>To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
>>Subject: [reSIProcate] reSIProcate and LCS?
>>
>>Hello,
>>
>>I am trying to connect reSIProcate to Microsoft's LCS (Live
>>Communications Server) in Federation mode (i.e. Public IM). In this
>>mode, instant messenger users (i.e. MOC clients) can communicate
OUTSIDE
>>
>>of their domain. For example, with Federation mode a user named
>>john@xxxxxxx (that uses LCS as their enterprise IM server) can IM with
>>sam@xxxxxxxx The inter-domain protocol that is used to make this
happen
>>is called "Federation". The protocol is basically just some MSFT
>>extensions onto standard SIP/SIMPLE messages. However, I'm running
into
>>plenty of problems when trying to interoperate between reSIProcate and
>>LCS.
>>
>>Has anyone tried to do something similar?? If so, was there a detailed
>>Microsoft Federation mode interface spec that you followed or
something?
>>
>>Thanks,
>>Chris
>>_______________________________________________
>>resiprocate-devel mailing list
>>resiprocate-devel@xxxxxxxxxxxxxxxxxxx
>>https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
>>_______________________________________________
>>resiprocate-devel mailing list
>>resiprocate-devel@xxxxxxxxxxxxxxxxxxx
>>https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
>>
>>
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel