Cisco Cisco TelePresence Video Communication Server Expressway
Routing configuration
Routing configuration
Pre-search transforms
Pre-search transform configuration allows the destination alias (called address) in an incoming
search request to be modified. The transformation is applied by the Cisco VCS before any searches
take place, either locally or to external zones.
search request to be modified. The transformation is applied by the Cisco VCS before any searches
take place, either locally or to external zones.
The pre-search transform configuration described in this document is used to standardize destination
aliases originating from both H.323 and SIP devices.
aliases originating from both H.323 and SIP devices.
For example, if the called address is an H.323 E164 alias “01234” the Cisco VCS will automatically
append the configured domain name (in this case example.com) to the called address (that is,
01234@example.com making it into a URI), before attempting to set up the call.
append the configured domain name (in this case example.com) to the called address (that is,
01234@example.com making it into a URI), before attempting to set up the call.
This is carried out to make the call searches the same for calls from H.323 endpoints and SIP
endpoints.
endpoints.
Note:
Transforms should be used with care because they happen before searches and apply to all
signaling messages – if they match, they will affect the routing of provisioning and presence
requests as well as call requests.
signaling messages – if they match, they will affect the routing of provisioning and presence
requests as well as call requests.
Transformations can also be carried out in search rules – consider whether it is best to use a
transform or a search rule to modify the called address to be looked up.
transform or a search rule to modify the called address to be looked up.
Search rules
The search rules configuration defines how the Cisco VCS routes calls (to destination zones) in
specific call scenarios. When a search rule is matched, the destination alias can be modified
according to the conditions defined in the search rule.
specific call scenarios. When a search rule is matched, the destination alias can be modified
according to the conditions defined in the search rule.
The search rules configuration described in this document is used to ensure SIP (and H.323)
endpoints can dial H.323 devices that have registered e164 numbers or H.323 IDs without a domain
portion. The search rules first search for received destination aliases without the domain portion of the
URI, and then searching with the full URI.
endpoints can dial H.323 devices that have registered e164 numbers or H.323 IDs without a domain
portion. The search rules first search for received destination aliases without the domain portion of the
URI, and then searching with the full URI.
The search rules configuration described in this document is used to enable the routing:
Calling party
Called party
Registered devices (Cisco VCS Control or
Expressway)
Expressway)
Registered devices (Cisco VCS Control or Expressway)
Registered devices (Cisco VCS Control or
Expressway)
Expressway)
External domains and un-registered devices (via Cisco
VCS Expressway using DNS zone)
VCS Expressway using DNS zone)
Registered devices (Cisco VCS Control or
Expressway)
Expressway)
Public external IP addresses (via Cisco VCS Expressway)
External domains and un-registered devices
Registered devices (Cisco VCS Control or Expressway)
Note: The following routing configuration searches for destination aliases that have valid SIP URIs
(that is, using a valid SIP domain – i.e. id@domain).
(that is, using a valid SIP domain – i.e. id@domain).
It is possible to configure routing which enables calls to unregistered devices on an internal network
(routing to the addresses of IP of the devices) by configuring a search rule with mode AnyIPAddress
with target Local Zone. However this is not recommended (and not described in this document). The
best practice is to register all devices and route using destination aliases.
(routing to the addresses of IP of the devices) by configuring a search rule with mode AnyIPAddress
with target Local Zone. However this is not recommended (and not described in this document). The
best practice is to register all devices and route using destination aliases.
Cisco VCS Deployment Guide: Basic Cisco VCS configuration – Cisco VCS Control with
Cisco VCS Expressway
Cisco VCS Expressway
Page 15 of 44