Cisco Cisco TelePresence Video Communication Server Expressway
Cisco VCS configuration
Cisco VCS Deployment Guide: Multiway™ (Cisco VCS X6)
Page 8 of 28
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
E164 number when routing the call to the MCU. Converting the SIP URI into an E164 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 E164 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 E164 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 E164 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
Cisco VCS and SIP MCU
SIP does not support the concept of prefix registration; instead, configure a neighbor zone with a
match that looks for prefix digits, and if found routes the call to the MCU.
match that looks for prefix digits, and if found routes the call to the MCU.
The <MCU service prefix> needs to be removed from the called ID
(<MCU service prefix><Conference prefix><extra digits>) so that the conference ID created by the
MCU will be in the format:
(<MCU service prefix><Conference prefix><extra digits>) so that the conference ID created by the
MCU will be in the format:
<Conference prefix><extra digits>
(the same as would be created by an H.323 call to the same number)
1. Go to VCS configuration > Zones.
2. Configure a neighbor zone as follows:
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”.