none
TCP SIP in Lync - Lifesize VC Integration

    Question

  • Has anyone had luck enabling SIP over TCP in Lync. Specifically I am looking to integrate our Lifesize VC units that do support SIP over TCP.

    TLS is working just fine, and the software clients are working, but I would like to get our room units online.

    I found a great document for OCS/Lifesize: http://www.vidofon.de/media/TN_VideoComm_OCS_v4_7.pdf

    But nothing available for Lync. Any thoughts would be appreciated.

     

    • Moved by Ben-Shun Zhu Wednesday, November 03, 2010 10:08 AM incorrect queue (From:Planning and Deployment)
    Tuesday, November 02, 2010 10:58 PM

Answers

  • OK, I finally got this sorted and I'll post here so the world may get the benefit of my head-banging.

    Step 1 - Enable SIP via TCP with Tom's great instructions above

    Step 2 - Create a static route / trusted app pool / trusted app, using the IP address of the Lifesize unit as the FQDN - per Mike Stacy's article:

    http://mikestacy.typepad.com/mike-stacys-blog/2010/09/index.html

    Step 3 - Configure the LifeSize (below)

    SIP: Enabled

    SIP Username : Username (no UPN or domain)

    Authorization Name: Username (no UPN or domain)

    Authorization Password: (blank)

    SIP server type: MS OCS

    SIP Registration: Through proxy

    SIP Proxy: Enabled

    Proxy Hostname: (Single Tier front-end IP)

    Proxy IP Port: 5060

    SIP Registrar: Enabled

    Registrar Hostname:  IP of LifeSize Unit

    Registrar IP Port: 5060

    UDP Signaling Port: 5060

    TCP Signaling: Enabled

    TCP Signaling Port: 5060

    TLS Signaling: Disabled

    TLS Signaling Port: 5061

     


    • Marked as answer by R. Hock Tuesday, November 30, 2010 2:18 PM
    Tuesday, November 30, 2010 2:18 PM
  • I managed to get TCP working today - you can find the details here: http://www.confusedamused.com/notebook/enabling-unencrypted-tcp-connections-to-lync-on-port-5060/

     

    This allows the LifeSize units to register to Lync OK, but what we're seeing is presence doesn't work. It generates a server error about a legacy operation not being allowed. Video calls connect just fine, but you don't get presence.

     

    I suspect we'll have to wait for a LifeSize update to address the presence problem.

    • Marked as answer by R. Hock Tuesday, November 30, 2010 2:18 PM
    Friday, November 12, 2010 2:36 AM

All replies

  • I managed to get TCP working today - you can find the details here: http://www.confusedamused.com/notebook/enabling-unencrypted-tcp-connections-to-lync-on-port-5060/

     

    This allows the LifeSize units to register to Lync OK, but what we're seeing is presence doesn't work. It generates a server error about a legacy operation not being allowed. Video calls connect just fine, but you don't get presence.

     

    I suspect we'll have to wait for a LifeSize update to address the presence problem.

    • Marked as answer by R. Hock Tuesday, November 30, 2010 2:18 PM
    Friday, November 12, 2010 2:36 AM
  • Tom, you sir are a gentleman and a scholar. TCP SIP on 5060 came right up. Were there any gotchas with the Lifesize configuration side you encountered? Our Team 200 lab unit still does not want to register. The settings are configured as such:

    SIP: Enabled

    SIP Username : Username (no UPN or domain)

    Authorization Name: Username (no UPN or domain)

    Authorization Password: (blank)

    SIP server type: AUTO

    SIP Registration: Through proxy

    SIP Proxy: Enabled

    Proxy Hostname: (Single Tier front-end IP)

    Proxy IP Port: 5060

    SIP Registrar: Enabled

    Registrar Hostname:  (Single Tier front-end IP)

    Registrar IP Port: 5060

    UDP Signaling Port: 5060

    TCP Signaling: Enabled

    TCP Signaling Port: 5060

    TLS Signaling: Disabled

    TLS Signaling Port: 5061

     

    I attempted to open a ticket with Lifesize for some interop documentation, and was told that is first time they received such a request. A bit disapointed in Lifesize in this regard, as most of their major competition already has certified devices. Thanks again for your time and assistance.

    Friday, November 12, 2010 6:32 PM
  • OK, I finally got this sorted and I'll post here so the world may get the benefit of my head-banging.

    Step 1 - Enable SIP via TCP with Tom's great instructions above

    Step 2 - Create a static route / trusted app pool / trusted app, using the IP address of the Lifesize unit as the FQDN - per Mike Stacy's article:

    http://mikestacy.typepad.com/mike-stacys-blog/2010/09/index.html

    Step 3 - Configure the LifeSize (below)

    SIP: Enabled

    SIP Username : Username (no UPN or domain)

    Authorization Name: Username (no UPN or domain)

    Authorization Password: (blank)

    SIP server type: MS OCS

    SIP Registration: Through proxy

    SIP Proxy: Enabled

    Proxy Hostname: (Single Tier front-end IP)

    Proxy IP Port: 5060

    SIP Registrar: Enabled

    Registrar Hostname:  IP of LifeSize Unit

    Registrar IP Port: 5060

    UDP Signaling Port: 5060

    TCP Signaling: Enabled

    TCP Signaling Port: 5060

    TLS Signaling: Disabled

    TLS Signaling Port: 5061

     


    • Marked as answer by R. Hock Tuesday, November 30, 2010 2:18 PM
    Tuesday, November 30, 2010 2:18 PM
  • Has anyone got this to work on the RTM version of Lync. I am having problems with running the command in Mike Stacy's article as the "REGISTRAR" option is on longer available.
    Bob Ausmus
    Monday, December 13, 2010 5:15 PM
  • Hi there,

    i got the following problem.

    I want to integrate OCS 2007 R2 with Lifesizeteam 220.

    Our Lifesizeteam 220 system has no connection to the local LAN (OCS 2007 R2 system). The only possible way to connect these system is through the internet (OCS EDGE Server).

    Can you help me with the configuration of the Lifesizeteam system? I dont know how to set the named properties.
    SIP: Enabled

    SIP Username : Username (no UPN or domain)

    Authorization Name: Username (no UPN or domain)

    Authorization Password: (blank)

    SIP server type: ???????????????????????

    SIP Registration: ??????????????????

    SIP Proxy: ???????????????????

    Proxy Hostname: ????????????????????

    Proxy IP Port: ?????????????????

    SIP Registrar: ????????????????????

    Registrar Hostname:  ?????????????????????

    Registrar IP Port: ???????????????????

    UDP Signaling Port: ????????????????????

    TCP Signaling: ???????????????????????

    TCP Signaling Port: ?????????????????????

    TLS Signaling: ????????????????????????????

    TLS Signaling Port: ?????????????????????????

     

     

    Thanks in advance.

    Fatstas

     

    Tuesday, December 14, 2010 3:27 PM