To designate a network-specific address to receive calls from a VoIP
or VoIPv6 dial peer, use the
session target command in dial peer configuration mode. To
reset to the default, use the
no form of this command.
Cisco 1751, Cisco 3725, Cisco 3745, and Cisco AS5300
session target {dhcp | ipv4:destination-address | ipv6: [destination-address] | dns: [$s$. | $d$. | $e$. | $u$.] hostname | enum:table-num | loopback:rtp | ras | sip-server | registrar} [:port]
no session target
Cisco 2600 Series, Cisco 3600 Series, Cisco AS5350, Cisco
AS5400, and Cisco AS5850
session target {dhcp | ipv4:destination-address | ipv6: [destination-address] | dns: [$s$. | $d$. | $e$. | $u$.] hostname | enum:table-num | loopback:rtp | ras | settlement provider-number | sip-server | registrar} [:port]
no session target
Syntax Description
|
dhcp
|
Configures the router to obtain the session target via
DHCP.
|
Note
|
The
dhcp option can be made available
only if the Session Initiation Protocol (SIP) is used as the session protocol.
To enable SIP, use the
session protocol (dial peer) command.
|
|
|
ipv4:
destination
-address
|
Configures the IP address of the dial peer to receive
calls. The colon is required.
|
|
ipv6:
[destination -address ]
|
Configures the IPv6 address of the dial peer to receive
calls. Square brackets must be entered around the IPv6 address. The colon is
required.
|
|
dns:[$s$]
hostname
|
Configures the host device housing the domain name system
(DNS) server that resolves the name of the dial peer to receive calls. The
colon is required.
Use one of the following macros with this keyword when
defining the session target for VoIP peers:
-
$s$.
--(Optional)
Source destination pattern is used as part of the domain name.
-
$d$.
--(Optional)
Destination number is used as part of the domain name.
-
$e$.
--(Optional)
Digits in the called number are reversed and periods are added between the
digits of the called number. The resulting string is used as part of the domain
name.
-
$u$.
--(Optional)
Unmatched portion of the destination pattern (such as a defined extension
number) is used as part of the domain name.
-
hostname
--String
that contains the complete hostname to be associated with the target address;
for example, serverA.example1.com.
|
|
enum:
table
-num
|
Configures ENUM search table number. Range is from 1 to 15.
The colon is required.
|
|
loopback:rtp
|
Configures all voice data to loop back to the source. The
colon is required.
|
|
ras
|
Configures the registration, admission, and status (RAS)
signaling function protocol. A gatekeeper is consulted to translate the E.164
address into an IP address.
|
|
sip
-server
|
Configures the global SIP server is the destination for
calls from the dial peer.
|
|
:
port
|
(Optional) Port number for the dial-peer address. The colon
is required.
|
|
settlement
provider
-number
|
Configures the settlement server as the target to resolve
the terminating gateway address.
|
|
registrar
|
Specifies to route the call to the registrar end point.
|
Command Default
No IP address or domain name is defined.
Command Modes
Dial peer configuration (config-dial-peer)
Command History
|
Release
|
Modification
|
|
11.3(1)T
|
This command was introduced on the Cisco 2600 series and
Cisco 3600 series.
|
|
12.0(3)T
|
This command was modified. This command was implemented on
the Cisco AS5300. The
ras keyword was added.
|
|
12.0(4)XJ
|
This command was implemented for store-and-forward fax on
the Cisco AS5300.
|
|
12.1(1)T
|
This command was integrated into Cisco IOS Release
12.1(1)T. The
settlement and
sip -server
keywords were added.
|
|
12.2(2)XA
|
This command was implemented on the Cisco AS5350 and Cisco
AS5400.
|
|
12.2(2)XB1
|
This command was implemented on the Cisco AS5850.
|
|
12.2(8)T
|
This command was integrated into Cisco IOS Release
12.2(8)T. Support for the Cisco AS5300, Cisco AS5350, Cisco AS5400, and Cisco
AS5850 was not included in this release.
|
|
12.2(11)T
|
This command was implemented on the Cisco AS5300, Cisco
AS5350, Cisco AS5400, and Cisco AS5850. The
enum keyword was added.
|
|
12.4(22)T
|
This command was modified. Support for IPv6 was added.
|
|
12.4(22)YB
|
This command was modified. The
dhcp keyword was added.
|
|
15.0(1)M
|
This command was integrated into Cisco IOS Release
15.0(1)M.
|
| Cisco IOS XE Amsterdam 17.2.1r |
Introduced support for YANG models.
|
Usage Guidelines
Use the
session target command to specify a network-specific
destination for a dial peer to receive calls from the current dial peer. You
can select an option to define a network-specific address or domain name as a
target, or you can select one of several methods to automatically determine the
destination for calls from the current dial peer.
Use the
session target dns command with or without the specified macros.
Using the optional macros can reduce the number of VoIP dial-peer session
targets that you must configure if you have groups of numbers associated with a
particular router.
The
session target enum command instructs the dial peer to use a
table of translation rules to convert the dialed number identification service
(DNIS) number into a number in E.164 format. This translated number is sent to
a DNS server that contains a collection of URLs. These URLs identify each user
as a destination for a call and may represent various access services, such as
SIP, H.323, telephone, fax, e-mail, instant messaging, and personal web pages.
Before assigning the session target to the dial peer, configure an ENUM match
table with the translation rules using the
voice enum -match -table command in global configuration mode. The table is identified
in the
session target enum command with the
table-num argument.
Use the
session target loopback command to test the voice transmission
path of a call. The loopback point depends on the call origin.
Use the
session target dhcp command to specify that the session target
host is obtained via DHCP. The
dhcp option can be made available only if the
SIP is being used as the session protocol. To enable SIP, use the
session protocol (dial peer) command.
In Cisco IOS Release 12.1(1)T the
session target command configuration cannot combine the
target of RAS with the
settle -call
command.
For the
session target settlement provider-number command, when the
VoIP dial peers are configured for a settlement server, the
provider -number
argument in the
session target and settle -call commands
should be identical.
Use the
session target sip -server command to
name the global SIP server interface as the destination for calls from the dial
peer. You must first define the SIP server interface by using the
sip -server command
in SIP user-agent (UA) configuration mode. Then you can enter the
session target sip -server option for
each dial peer instead of having to enter the entire IP address for the SIP
server interface under each dial peer.
After the SIP endpoints are registered with the SIP registrar in the
hosted unified communications (UC), you can use the
session target registrar command to route the call automatically
to the registrar end point. You must configure the
session target command on a dial pointing towards the end
point.
Examples
The following example shows how to create a session target using DNS
for a host named "voicerouter" in the domain example.com:
dial-peer voice 10 voip
session target dns:voicerouter.example.com
The following example shows how to create a session target using DNS
with the optional
$u$ . macro. In this example, the destination
pattern ends with four periods (.) to allow for any four-digit extension that
has the leading number 1310555. The optional
$u$ . macro directs the gateway to use the
unmatched portion of the dialed number--in this case, the four-digit
extension--to identify a dial peer. The domain is "example.com."
dial-peer voice 10 voip
destination-pattern 1310555....
session target dns:$u$.example.com
The following example shows how to create a session target using DNS,
with the optional
$d$ . macro. In this example, the destination
pattern has been configured to 13105551111. The optional
macro $d$ . directs the gateway to use the
destination pattern to identify a dial peer in the "example.com" domain.
dial-peer voice 10 voip
destination-pattern 13105551111
session target dns:$d$.example.com
The following example shows how to create a session target using DNS,
with the optional
$e$ . macro. In this example, the destination
pattern has been configured to 12345. The optional macro $e$ . directs the gateway to do the
following: reverse the digits in the destination pattern, add periods between
the digits, and use this reverse-exploded destination pattern to identify the
dial peer in the "example.com" domain.
dial-peer voice 10 voip
destination-pattern 12345
session target dns:$e$.example.com
The following example shows how to create a session target using an
ENUM match table. It indicates that calls made using dial peer 101 should use
the preferential order of rules in enum match table 3:
dial-peer voice 101 voip
session target enum:3
The following example shows how to create a session target using
DHCP:
dial-peer voice 1 voip
session protocol sipv2
voice-class sip outbound-proxy dhcp
session target dhcp
The following example shows how to create a session target using RAS:
dial-peer voice 11 voip
destination-pattern 13105551111
session target ras
The following example shows how to create a session target using
settlement:
dial-peer voice 24 voip
session target settlement:0
The following example shows how to create a session target using IPv6
for a host at 2001:10:10:10:10:10:10:230a:5090:
dial-peer voice 4 voip
destination-pattern 5000110011
session protocol sipv2
session target ipv6:[2001:0DB8:10:10:10:10:10:230a]:5090
codec g711ulaw
The following example shows how to configure Cisco Unified Border
Element (UBE) to route a call to the registering end point:
dial-peer voice 4 voip
session target registrar
Feedback