Cisco Cisco TelePresence Video Communication Server Expressway
Cisco Multiway without TelePresence Conductor
Cisco TelePresence Multiway Deployment Guide (Cisco VCS X7.2 and Conductor XC2.2)
Page 13 of 41
n
If the Template is creating a URI that will be routed to an H.323 MCU, typically the name part of the URI
(name@domain) must produce a numeric only ID, as H.323 MCUs typically only support E.164 dialing.
(name@domain) must produce a numeric only ID, as H.323 MCUs typically only support E.164 dialing.
n
If calls are to be made to an MCU that supports SIP, it will register <Conference
prefix>%%@MCU.domain … make sure that <Conference prefix> is unique for SIP calls, so that it does
not match other dialable SIP destinations.
prefix>%%@MCU.domain … make sure that <Conference prefix> is unique for SIP calls, so that it does
not match other dialable SIP destinations.
n
Make sure that the Template cannot generate URIs which match existing endpoint URIs or other Multiway
conference URIs – otherwise calls may end up ringing endpoints or joining another conference.
conference URIs – otherwise calls may end up ringing endpoints or joining another conference.
n
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.
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.
high-priority search rule for this alias. The effect of this will be particularly beneficial in scenarios with many
search rules and zones.
1. Go to
VCS configuration > Dial plan > Search rules
.
2. Add a new search rule with the following configuration:
Priority
1
Protocol
Any
Source
Any
Request must be
authenticated
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
VCS and H.323 MCU
The MCU will register its MCU service prefix (for example, 555) with the 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.
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 a conference whose conference ID is:
<Conference prefix><extra digits>
The MCU will register the conference on the 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>.
<MCU service prefix><Conference prefix><extra digits>
The MCU will create a conference whose conference ID is:
<Conference prefix><extra digits>
The MCU will register the conference on the 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>.
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
out in the VCS’s Local Zone; it should strip the domain off any calls to