Cisco Cisco TelePresence Video Communication Server Expressway

Cisco Multiway without Conductor

Cisco VCS Deployment Guide: Multiway™ (Cisco VCS X7)

Page 14 of 35

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.

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:

<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:

SIP mode

SIP port

5060

SIP transport

TCP (or TLS – depending on how MCU is configured)

H.323 mode

Off

Authentication policy

Configure the authentication settings according to your
authentication policy

Peer IP address

IP address of MCU

Zone profile

Default

3. Go to

VCS

configuration > Dial plan > Search rules

4. Configure a search rule as follows:

Priority

Source

Any

Request must be
authenticated

Configure this setting according to your authentication policy

Mode

Alias pattern match

Pattern type

Regex

Pattern string

<MCU service prefix>(<Conference prefix>\d+@MCU.domain)(:.*)?
e.g. 555(77\d+@example.com)(:.*)?

Pattern behavior

Replace

Replace string

On successful match

Continue

Target zone

Zone created above, for example Multiway - SIP

Note:



When a SIP ad hoc conference is set up, 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.

Cisco VCS and MCU supporting both H.323 and SIP

Follow the processes above and set up the Cisco VCS to work with an H.323 MCU and also to work
with a SIP MCU: