Cisco Cisco Meeting Server 1000
Cisco Meeting Server Release 2.0 : Scalable and Resilient Meeting Server Deployments
60
The information in the Clustered Call Bridges table is replicated to every Call Bridge in the
cluster. Therefore, you can now go to any Call Bridge server, sign in to the Web Admin Interface
and go to Configuration > Cluster to see the status of all the clustered Call Bridges.
cluster. Therefore, you can now go to any Call Bridge server, sign in to the Web Admin Interface
and go to Configuration > Cluster to see the status of all the clustered Call Bridges.
The Call Bridge cluster is now setup, and the clustered Call Bridges will share the same dial plan
(Inbound, Outbound and Call Forwarding dial plan rules). You now need to check that the dial
plan uses the same addresses as those entered in the Clustered Call Bridges table. See the
section on
(Inbound, Outbound and Call Forwarding dial plan rules). You now need to check that the dial
plan uses the same addresses as those entered in the Clustered Call Bridges table. See the
section on
.
6.4 Lync Account Information
For Call Bridge integration with Lync Edge, we recommend that you configure each Call Bridge
with its own login account so that there are no conflicts. For each Lync call to or from that Call
Bridge, we request TURN resources from the Lync Edge using that account. Until that call is
disconnected, that resource is considered "Used" from a Lync point of view. Lync will only
allow up to 12 TURN allocations per user account; therefore, with 1 registration, only 12 calls
are possible. If you shared that one account across multiple Call Bridges, you would only be
allowed 12 Lync calls in total across all Call Bridges, not just the 1.
with its own login account so that there are no conflicts. For each Lync call to or from that Call
Bridge, we request TURN resources from the Lync Edge using that account. Until that call is
disconnected, that resource is considered "Used" from a Lync point of view. Lync will only
allow up to 12 TURN allocations per user account; therefore, with 1 registration, only 12 calls
are possible. If you shared that one account across multiple Call Bridges, you would only be
allowed 12 Lync calls in total across all Call Bridges, not just the 1.
Configure each Call Bridge independently for this reason and so that each regional Call Bridge
uses a local regional Lync Edge (where available). Use the normal dial plan outbound rules to
determine if a call is a Lync call and to configure where to send it.
uses a local regional Lync Edge (where available). Use the normal dial plan outbound rules to
determine if a call is a Lync call and to configure where to send it.
6.5 Dial Plan Information
This section discusses setting up a dial plan for scalable and resilient deployments: inbound dial
plan rules, outbound dial plan rules and call forwarding rules. The specific dial plan rules you
require and their priority depend on your deployment, not only the topology of the Meeting
Server deployment but also of your call control platform(s) and whether you prefer to use local
resources or want to load balance calls.
plan rules, outbound dial plan rules and call forwarding rules. The specific dial plan rules you
require and their priority depend on your deployment, not only the topology of the Meeting
Server deployment but also of your call control platform(s) and whether you prefer to use local
resources or want to load balance calls.
6 Deploying the Call Bridges