Cisco Cisco TelePresence Video Communication Server Expressway
Cisco Multiway without Conductor
Cisco TelePresence Multiway Deployment Guide (Cisco VCS X7.2 and Conductor XC1.2)
Page 12 of 35
The Template is not replicated across cluster nodes and must be configured independently and
uniquely for each node. See the separate section on configuring Multiway in a clustered
environment.
uniquely for each node. See the separate section on configuring Multiway in a clustered
environment.
To ensure that the Conference Factory Alias is processed quickly, you are recommended to add a
dedicated, high-priority search rule for this alias. The effect of this will be particularly beneficial in
scenarios with many search rules and zones.
dedicated, high-priority search rule for this alias. The effect of this will be particularly beneficial in
scenarios with many search rules and zones.
Go to
VCS configuration > Dial plan > Search rules
. Add a new search rule with the following
configuration:
Priority
1
Protocol
Any
Source
Any
Request must be authenticated
Configure this setting according to your authentication policy
Mode
Alias pattern match
Pattern type
Exact
Pattern string
Conference Factory Alias as configured under
Applications >
Conference Factory
Pattern behavior
Leave
On successful match
Stop
Target zone
LocalZone
Cisco VCS and H.323 MCU
The MCU will register its MCU service prefix (for example, 555) with the Cisco VCS as an MCU Prefix;
VCS will route a call to this MCU if the call is made to an E.164 number whose first digits match the
service prefix.
VCS will route a call to this MCU if the call is made to an E.164 number whose first digits match the
service prefix.
1. Check that the MCU is registering the MCU service prefix as an MCU Prefix registration.
When a call is made to an MCU with a dialed number:
<MCU service prefix><Conference prefix><extra digits>
The MCU will create an ad hoc conference whose conference ID is:
<Conference prefix><extra digits>
The MCU will register the conference on the Cisco VCS as:
<Prefix for MCU registrations><Conference prefix><extra digits>
So that other callers being joined to the conference reach the same conference the
<Prefix for MCU registrations> must be the same as <MCU service prefix>.
<Prefix for MCU registrations> must be the same as <MCU service prefix>.
2. As the Conference Factory Template must be a URI, it is necessary to convert the URI into an
E.164 number when routing the call to the MCU. Converting the SIP URI into an E.164 number
should be carried out in the VCS’s Local Zone; it should strip the domain off any calls to
<MCU service prefix><Conference prefix><extra digits>@domain, so that the call to the MCU
is placed as an E.164 dialed H.323 call.
should be carried out in the VCS’s Local Zone; it should strip the domain off any calls to
<MCU service prefix><Conference prefix><extra digits>@domain, so that the call to the MCU
is placed as an E.164 dialed H.323 call.
Go to
VCS
configuration > Dial plan > Search rules
.
•
At match priority 50 there should be an Always Match search rule, or a match pattern that
allows the VCS to route calls to registered endpoints.
allows the VCS to route calls to registered endpoints.
•
To convert the dialed URI to an E.164 number, add a new Search rule with the following
configuration:
configuration:
Priority
48
Protocol
Any