Cisco Cisco Meeting Server 2000
Cisco Meeting Server Release 2.0 : Scalable and Resilient Meeting Server Deployments
104
fred@example.com. If the same LDAP structure has been used to create both the Meeting
Server’s and the Lync’s user accounts, this will be a common problem.
Server’s and the Lync’s user accounts, this will be a common problem.
The solution is to configure the Incoming Calls page with the Domain Name field set to
something distinct from the domain that the Lync FE server uses. In the example above, a
sensible choice for the Domain Name field would be example.com. Then, a call to
fred@example.com will reach the Cisco Meeting App but a call to fred@lync.example.com or
fred@xxxx will not. Instead, if the Call Forwarding section is set up, the Meeting Server forwards
the call onwards.
something distinct from the domain that the Lync FE server uses. In the example above, a
sensible choice for the Domain Name field would be example.com. Then, a call to
fred@example.com will reach the Cisco Meeting App but a call to fred@lync.example.com or
fred@xxxx will not. Instead, if the Call Forwarding section is set up, the Meeting Server forwards
the call onwards.
12.6 Lync Edge server integration
Follow the configuration steps in this section to configure Lync Edge settings on the Meeting
Server. This is required to support Dual Home Conferencing or if the Lync Edge performs the
TURN/ICE role for Lync calls, rather than the Meeting Server.
Server. This is required to support Dual Home Conferencing or if the Lync Edge performs the
TURN/ICE role for Lync calls, rather than the Meeting Server.
12.6.1 Lync Edge call flow
To establish a call from the Meeting Server to the Lync Edge server (see Figure 38 below):
1. The Call Bridge makes a “register” SIP call to the Lync Front End server.
2. The “register” is acknowledged.
3. The Call Bridge sends a “service” to the Lync Front End server.
4. The Front End server returns the URI of the media relay authentication server (MRAS). (The
Lync Edge Server acts as a MRAS.)
5. The Lync client initiates an incoming call.
6. The Call Bridge sends “service” messages to the Lync Front End server to request MRAS
credentials to use the Lync Edge MRAS service
7. The Lync Front End server returns the credentials for the Call Bridge to use, as well as the
UDP and TCP ports, and the MRAS URI once again
8. The Call Bridge resolves this MRAS URI using DNS and starts sending STUN messages
directly to the Lync Edge server
9. The call media then flows directly between the Call Bridge and Lync Edge’s TURN server on
UDP port 3478 and returns from the Lync Edge server to the Call Bridge on a port in the
ephemeral range above.
ephemeral range above.
Therefore the following ports need to be opened in the firewall for the media between Call
Bridge and the Lync Edge server: UDP 3478 outgoing and 32768-65535 incoming.
Bridge and the Lync Edge server: UDP 3478 outgoing and 32768-65535 incoming.
12 Dial plan configuration – integrating Lync