Cisco Cisco TelePresence Video Communication Server Expressway
Cisco VCS configuration
Cisco VCS Deployment Guide: Multiway™ (Cisco VCS X7)
Page 9 of 30
Cisco VCS and H.323 MCU
The MCU will register its MCU service prefix (e.g. 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.
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
Source
Any
Request must be
authenticated
authenticated
Configure this setting according to your authentication policy
Mode
Alias pattern match
Pattern type
Regex
Pattern string
(<MCU service prefix><Conference prefix>\d+)@domain
e.g. (55577\d+)@mycompany.com
e.g. (55577\d+)@mycompany.com
Pattern behavior
Replace
Replace string
\1
On successful match
Continue
Target zone
LocalZone
For resilience, multiple H.323 MCUs may register the same service prefix with the VCS (or VCS
cluster) and VCS will ensure that all calls to a conference are presented to the same MCU1
cluster) and VCS will ensure that all calls to a conference are presented to the same MCU1
1 For details on VCS’s handling of multiple MCUs registered with the same MCU service prefix, see the “VCS deployment guide
- Connecting H 323 MCUs to VCSs”.
- Connecting H 323 MCUs to VCSs”.