What is MRAS?
Media Relay Authentication Server
MRAS generates the credentials needed for external media by Lync users outside the local network. Before an external user can initiate any type of A\V traffic the Edge server will need to obtain credentials that will allow it to relay A\V internally on behalf of the external client.
The following illustration depicts the MRAS process:
The MRAS Process is as follows:
- SIP Register
- MRAS Request
- MRAS Response
- MRAS Response (to user)
To have a closer look at these we will use snooper
You should find 3 messages.
1. SIP Register
The First message (SIP 200 OK) contains all user settings, profile, URls etc etc (all in-band)
2. MRAS Request
The Second MRAS message (SERVICE) shows the service request from the Lync Client to the Front End for credentials to chat to the Lync Edge.
You will always see this second MRAS message once the first is seen as its simply the client responding.
3. MRAS Response
The Third MRAS message (SIP 200 OK) is a response from the Lync Front End providing credentials, location, and the HOST NAME of AV EDGE and the ports to use for media.
External clients need to get the External FQDN of the Edge Server here and internal clients need to get the Internal FQDN of the Edge Server – This is the server name that the client needs to connect to for establishing media.
If the 3rd message is present it reveals that the FE is able to communicate with the Edge on port 5062 (MRAS)
If there is an MRAS error in message 3 (eg Timeout) then there is a connectivity issue between Edge and FE (eg FW, DNS).