Cisco Cisco Expressway Maintenance Manual
■
!^(.*)$!h323:\1@example.com!
describes the conversion:
—
!
is a field separator
—
the first field represents the string to be converted. In this example,
^(.*)$
represents the entire E.164
number
—
the second field represents the H.323 URI that will be generated. In this example,
h323:\1@example.com
states that the E.164 number will be concatenated with
@example.com
. For example,
1234
will be mapped to
1234@example.com
.
■
.
shows that the replacement field has not been used.
Configuring DNS Servers for ENUM and URI Dialing
DNS servers are required to support ENUM and URI dialing:
■
ENUM dialing: to query for NAPTR records that map E.164 numbers to URIs
■
URI dialing: to look up endpoints that cannot be accessed via neighbor systems
To configure the DNS servers used by the Expressway for DNS queries:
1.
Go to the DNS page (System > DNS).
2.
Enter in the Address 1 to Address 5 fields the IP addresses of up to 5 DNS servers that the Expressway will
query when attempting to locate a domain. These fields must use an IP address, not a FQDN.
query when attempting to locate a domain. These fields must use an IP address, not a FQDN.
Configuring Call Routing and Signaling
The Call routing page (Configuration > Call routing) is used to configure the Expressway's call routing and signaling
functionality.
functionality.
Call Signaling Optimization
, the Expressway always handles both
the media and the signaling. For non-traversal calls, the Expressway does not handle the media, and may or may not
need to handle the signaling.
need to handle the signaling.
The Call signaling optimization setting specifies whether the Expressway removes itself, where it can, from the call
signaling path after the call has been set up. The options for this setting are:
signaling path after the call has been set up. The options for this setting are:
■
Off: the Expressway always handles the call signaling.
■
On: the Expressway handles the call signaling when the call is one of:
—
a traversal call
—
an H.323 call that has been modified by Call Policy such that the call resolves to more than one alias
—
a SIP call where the incoming transport protocol (UDP, TCP, TLS) is different from the outgoing protocol
In all other cases the Expressway removes itself from the call signaling path after the call has been set up.
The Expressway does not consume a call license for any such calls, and the call signaling path is simplified.
The Expressway does not consume a call license for any such calls, and the call signaling path is simplified.
Call Loop Detection Mode
Your dial plan or that of networks to which you are neighbored may be configured in such a way that there are
potential signaling loops. An example of this is a structured dial plan, where all systems are neighbored together in a
mesh. In such a configuration, if the
potential signaling loops. An example of this is a structured dial plan, where all systems are neighbored together in a
mesh. In such a configuration, if the
around the network until the hop count reaches 0, consuming resources unnecessarily.
The Expressway can be configured to detect search loops within your network and terminate such searches through
the Call loop detection mode setting, thus saving network resources. The options for this setting are:
the Call loop detection mode setting, thus saving network resources. The options for this setting are:
147
Cisco Expressway Administrator Guide
Dial Plan and Call Processing