Lync and Skype for Business protocols

-
today is time that I will explain the Lync protocol short cuts, the name what actually this couple of letters mean.
I was very often asked what e.g. is the meaning of STUN or RT.

Also, which RFC is behind this protocol. If further information are available, I have posted this info too.

Therefore, here it come:

STUN - (Simple Traversal of User Datagram Protocol (UDP) - Through Network Address Translators (NATs))
This is protocol used on the Edge server, where UDP data is passed through the NAT. It contains information about the external (public) IP address where the client is hidden behind and the internal (private) IP address the client has assigned.
https://www.ietf.org/rfc/rfc3489.txt
 
STUN (Session Traversal Utilities for NAT)
http://tools.ietf.org/html/rfc5389

URI Scheme for the Session Traversal Utilities for NAT protocol
https://tools.ietf.org/html/rfc7064

NAT Behavior Discovery Using Session Traversal Utilities for NAT (STUN)
https://tools.ietf.org/html/rfc5780



TURN - Traversal Using Relay NAT
TURN is a design part of the ICE process, but can be used also without ICE. It is responsible for NATed client supporting "direct" communication. in Lync/ Skype for business, this protocol is server related.
https://tools.ietf.org/html/rfc5766
https://tools.ietf.org/html/rfc6062

ICE - Interactive Connectivity Protocol
IT determines all possible UDP and TCP port involved in a SIP communication. Necessary for the client negotiation process which is the best possible path for communication. This protocol is client related. But need ICE award servers.
https://tools.ietf.org/html/rfc5245
http://tools.ietf.org/html/rfc5768


MRAS - Media Relay Authentication Service
This is an authentication protocol used with Lync and Skype for business. MRAS initiates Token for authentication. It can be seen more as a component, rather then a protocol. It involves in the SIP authentication.
I haven't found official information about the MRAS Server/ Service, but it is most best describe the Audio/ Video Authentication description.
http://msdn.microsoft.com/en-us/library/cc431496(v=office.12).aspx


PSOM - Shared Object Messaging Protocol
It a Microsoft proprietary protocol used for Web Conferencing. PSOM is the media protocol for data collaboration. PSOM will use TLS as the underlying transport. PSOM can be used by conferencing clients to establish media channels with the Web Conferencing Server to negotiate or transfer media.
http://msdn.microsoft.com/en-us/library/ff595355(v=office.12).aspx


C3P - Centralized Conference Control Protocol (CCCP)
The Centralized Conference Control Protocol (C3P) activates, modifies, deactivates, and controls conferences. It utilize SIP standards for conferencing.
http://msdn.microsoft.com/en-us/library/cc431498(v=office.12).aspx
http://www.rfc-editor.org/rfc/rfc4353.txt



RTP/ RTCP - Real-Time Transport Protocol
RTP/RTCP is the standard protocol for the transport of real-time data, including audio and video.
https://www.ietf.org/rfc/rfc3550.txt
https://tools.ietf.org/html/rfc3605
https://tools.ietf.org/html/rfc3611

SRTP - Secure Real-Time Transport Protocol
http://www.ietf.org/rfc/rfc3711.txt
https://tools.ietf.org/html/rfc5763


SIP - Session Initiation Protocol
Session Initiation Protocol (SIP) is the industry standard protocol described in IETF RFC 3261 that defines a standard way for session setup, termination, and media negotiation between two parties. It is widely used for Voice over IP (VoIP) call signaling.
https://www.ietf.org/rfc/rfc3261.txt


SDP - Session Description Protocol
Session Description Protocol (SDP) is the industry standard protocol described in IETF RFC 4566 that defines a standard way to convey media details, transport addresses, and other session description metadata to the participants when initiating multimedia teleconferences, Voice over IP calls, streaming video, or other session
https://www.rfc-editor.org/rfc/rfc4566.txt



TLS
https://www.ietf.org/rfc/rfc2246.txt (1.0)
http://tools.ietf.org/html/rfc5246 (1.2)


MTLS
MTLS is nearly the same as TLS, but can contain multiple session with in a TLS connection setup. That's why Lync and Skype for Business use it between the Server-to-Server communication.
https://tools.ietf.org/html/draft-badra-hajjeh-mtls-05



General information:

Signaling and Control Protocol
SIP, as specified in RFC 3261, is used for session setup and termination in Office Communications Server. SIP messages use TCP or TLS as the underlying transport layer for client-to-server communications and TLS with mutual authentication (MTLS) for server-to-server communications. Conferences and call control are established within the context of existing SIP sessions using C3P protocol. C3P commands are sent using SIP INFO messages. A separate SUBSCRIBE/NOTIFY dialog is used to subscribe to conference packages, state change notifications, and the conference participant list.

Media Protocol
The Web Conferencing Server uses PSOM as the media protocol for data collaboration. PSOM uses TLS as the underlying transport. As the client for the Web Conferencing Server, Live Meeting functionality also relies on PSOM.
RTP and RTCP are used to provide audio/video functionality. Secure Real-time Transport Protocol (SRTP) and Secure Real-time Transport Control Protocol (SRTCP) are used to provide secure, encrypted audio/video functionality.) RTP/RTCP uses TCP or User Datagram Protocol (UDP) as the underlying transport.

Codec(s):
RTA/RTAudio - Realt-Time Audio 
RTV/RTVideo - Real-Time Video

G711/ G729/ G722

SILK
This is the SKYPE codec used with Skype and Skype for Business. The new version is only used between clients and client to server. The Mediation Server in Skype for Business will not make use of SILK.

OPUS
A new codec with will be used also in the open communication program with Polycom new phone. But will not be supported with in Skype for Business.

SIREN

PCM




Author:

Comments

Post a Comment

Popular posts from this blog

How to hide users from GAL if they are AD Connect synchronized

-
Image
How to hide and un-hide users from Global Address List (GAL) in Exchange Online if they are AD Connect synchronized Hiding User from GAL isn't possible if those are synchronized form On-Premises Active Directory. The local AD is the leading system for all important attributes, like SMTP, UPN and hiding from GAL. Especially during a cross-tenant migration, you do not want to see not migrated user in the GAL. Those User aren't actively working until their cut-over day. Since the Exchange Online attribute  msExchHideFromAddressList s is an AD on-premises parameter, we have two possible ways hiding user in BME from GAL.   Modify the AD Connect for your teant with a custom rule, by using a extensionAttribute to set the HidefromGAL. In this rule, for users which have an entry in the extensionAttribute, hiding / un-hiding will be controlled by AD Connect This is the best option for Cross-Tenant Migration, if you run 2 or more AD Connect system We direct modify the AD hide at
Read more

Cannot join external Lync Meeting: Lync Edge Server Single IP Address (Lync Edge Server Single IP Web Conferenceing Problem)

-
Image
Lync Edge Server FQDN and IP PORTS (Version 1.2, Update 26.11.2014) As we all know, we can configure Lync Edge Server in several way. 1) Single Edge Server with a SINGLE IP ADDRESS 2) Single Edge Server with MULTIPLE IP ADDRESSES (3x IPs) 3) Multiple Edge Server in a Pool, with MULTIPLE IP ADDRESSES (Zx 3 IPs) Regardless what we are going to configure, there are common / well-known TCP Port necessary making Lync work, which are: Access: Port: 443 and 5061 Conferencing: Port: 443 and (444) AV: Port: 443 (I have not listed other ports, e.g. STUN or the dynamic port range. This is not required for the topic discussed here) External FQDN with single IP address: What can we see here? If we are going to choose a single IP address, we would have TCP Port overlapping. Therefore the only way avoiding this is assigning other ports. Additionally we will also see and are reminded that Lync highly depends on DNS. If we have single IP, we must have use single, unique FQDN fo
Read more

MFA with Guest Access and different tenants settings

-
Image
There is an update regarding MFA Multi Factor Authentication. If you are guest with a different Tenant, the MFA Settings are now reflecting the settings of all tenants in a different way. Each MFA setting is reflected and you can setup your MFA device as per tenant and the admin settings allow. Login to your Profile in Office 365/ Azure AD: https://account.activedirectory.windowsazure.com/r/#/profile or https://myapps.microsoft.com Go to your PROFILE: Sign in to https://myapps.microsoft.com Select your account name in the top right, then select profile. Select Additional security verification. If might be happen, your admin hast configured MFA, so you wouldn't see this menu. Simply switch the tenant to the guest tenant where you need to configure MFA. Once you go back to your profile and you will find the MFA device and other settings a usual:
Read more