locked
LCS complience with IMS / SIP standards ? RRS feed

  • Question

  • 1. It seems,  to register to Live Communication server from a SIP client, NTLS or Kerbaros authentication is a must.

    How to register from a SIP client which doesn't support NTLS or Kerbaros ?

    Is there any configuration required on LCS to acheive the same ?

    2. If LCS doesn't support HTTP Digest Authentication then its not interoperable with SIP standard rfc 3261 and IMS ? Please correct me if I am wrong ?

    Please revert back !!!

    Best Regards,

    Deepak K Bramhapuriya

    Thursday, April 20, 2006 9:43 AM

Answers

  • Per our support engineer:

    Regarding following issue, our buddy has 2 questions on SIP standard in LCS.

     

    1)    How to register from a SIP client which doesn't support NTLS or Kerberos?

    2)    Does LCS support HTTP Digest Authentication?

     

    LCS can choose one of the following based on server settings:

    - Kerberos and NTLM (default)

    - Kerberos

    - NTLM

     

    Communicator (Client) doesn't have UI controls for this - it will simply choose Kerberos if presented - if not, it will select NTLM.  If presented with both, it will always choose Kerberos.

     

    Moreover, I don’t think LCS has build-in feature of HTTP Digest Authentication. By default, we only support NTLM and Kerberos authentication.

     

    -brend (ISV Buddy Team)

    Monday, June 12, 2006 3:32 PM

All replies

  • Per our support engineer:

    Regarding following issue, our buddy has 2 questions on SIP standard in LCS.

     

    1)    How to register from a SIP client which doesn't support NTLS or Kerberos?

    2)    Does LCS support HTTP Digest Authentication?

     

    LCS can choose one of the following based on server settings:

    - Kerberos and NTLM (default)

    - Kerberos

    - NTLM

     

    Communicator (Client) doesn't have UI controls for this - it will simply choose Kerberos if presented - if not, it will select NTLM.  If presented with both, it will always choose Kerberos.

     

    Moreover, I don’t think LCS has build-in feature of HTTP Digest Authentication. By default, we only support NTLM and Kerberos authentication.

     

    -brend (ISV Buddy Team)

    Monday, June 12, 2006 3:32 PM
  • Hi.

    Is there a way for developers access the SIP NTLM especification?
    It's very hard to develop a client to connect to LCS if we can't find any documentation.


    Thanks
    Monday, September 25, 2006 2:14 PM
  • Hi.

    Is there a way to access the SIP NTLM authentication of LCS?
    It's very hard to develop a client to connect to LCS if we can't find any documentation :(


    Thanks
    Monday, September 25, 2006 2:19 PM
  • You can license the protocol specs from MS. For information, go here: http://www.microsoft.com/about/legal/intellectualproperty/protocols/mcpp.mspx

    There are specs for the MS extensions to SIP as well as NTLM Authentication.

    The IETF RFC 4559 on SPNEGO-based Kerberos and NTLM HTTP Authentication in Microsoft Windows may shed some light on NTLM but is not completely germane to SIP.

    HTH

    Terry

    P.S. I'm not a MS employee

     

    Tuesday, September 26, 2006 10:09 PM
  • I'll take a look but I doubt that thay give me the NTLM authentication of SIP... Is not simple the NTLM authentication... Is the SIP NTLM authentication...


    But I'll try...

    Thanks
    Tuesday, September 26, 2006 10:19 PM