Welcome to MUCUGUK Sign in | Join | Help

Microsoft Unified Communications & RTC User Group, United Kingdom

Ports and Protocols

Last post 06-07-2006, 8:34 by BaldEagle. 4 replies.
Sort Posts: Previous Next
  •  06-05-2006, 9:23 6

    Ports and Protocols

    Can you please let me know which protocols and ports are used both from a server and client perspective when using LCS/MSOC??
  •  06-06-2006, 2:20 7 in reply to 6

    Re: Ports and Protocols

    Hi there,

    Communication can be client-to-server or server-to-server

    Protocols can be either SIP (port 5060) or SIP/tls (port 5061)

    Generally you'll want to use SIP/tls because it's encrypted.

    Ports can be configured manually and LCS 2005 can listen for both SIP and SIP/tls at the same time.

    TLS (transport layer security) requires server certificates. LCS 2005 SP1 can use standard web server SSL certificates.

    server-to-server communication can be MTLS (Mutual TLS).

     

    Hope that helps... Big Smile

  •  06-06-2006, 3:22 8 in reply to 6

    Re: Ports and Protocols

    Hi & welcome,

    Andy Thank you for your post; I believe that you have pretty much covered the answer.

    Live Communications Server is the "Farm", whilst Microsoft Office Communicator is the front-end portal.

    As Andy has pointed out communication can be either client-to-Server using SIP or Server-to-Server using MTLS.

    Initial commucation is established using SIP, however, if the user invokes multinodal communication, (audio visual, applications sharing, whiteboarding ect), then RTP will be established using direct Peer-to-Peer via ports 7100, 7101, 7102, 7103.

    In its' true form SIP will be used to establish initial communication, and then call the relevant protocol to handle the method of transmission required.

    I've provided a list of protocols and standards below that can be used within LCS/MSOC when integrated with other systems.

    Protocol   Brief Description
    XMPP     Extensible Messaging and Presence protocol. This is an IETF proposed
                    protocol for open XML based messaging and presence interactions

    Simple     Session Initiation Protocol for IM and Presence leveraging Extensions
                   is an application ofthe SIP protocol to the area of Instant Messaging

    SOAP    Simplified Objects Accessing Protocol with features for Presence
                  description as part of its access facilities

    H.323     ITU standard applying to audio adn video conferencing,
                  (multinodal communicatiosn),handling session issues such as call-signing,
                  call-control an framing protocols

    SMS      is a text based service that was developed by the European Telecommunications
                  Standards Institute, (ETSI), as part of the Global System for Mobile, (GSM),
                  Communication infrastructure

    MMS     allows the transmission of graphics, animation, video and sound

    Additional Protocol Standards
    T.120      ITU standard defining how data conferencing deals with interchange of data
    T.126      ITU standard defining whiteboards with
    T.128      ITU standard defining program and application sharing

    Hopefully this is of some help,

    Thank you

    Arthur


    Arthur Pounder
  •  06-07-2006, 6:29 9 in reply to 7

    Re: Ports and Protocols

    All correct. In addition, both Office Communicator and Windows messenger will attempt to tunnel through HTTPS proxy servers, for this work, the Access proxy must listen on port 443 (and optionally 5061) and be named SIP.domain.user.is.in

     

     


    James (Microsoft) My blog
  •  06-07-2006, 8:34 10 in reply to 6

    Re: Ports and Protocols

    Thank for the information guys, and the quick responses.
View as RSS news feed in XML
Powered by Community Server, by Telligent Systems