| Description | The object specifies the session target of the peer.
Session Targets definitions:
The session target has the syntax used by the IETF service
location protocol. The syntax is as follows:
mapping-type:type-specific-syntax
the mapping-type specifies a scheme for mapping the
matching dial string to a session target. The
type-specific-syntax is exactly that, something that the
particular mapping scheme can understand.
For example,
Session target Meaning
ipv4:171.68.13.55:1006 The session target is the IP
version 4 address of 171.68.13.55
and port 1006.
dns:pots.cisco.com:1661 The session target is the IP host
with dns name pots.cisco.com, and
port 1661.
ras The session target is the
gatekeeper with RAS (Registration
, Admission, Status protocol).
settlement The session target is the
settlement server.
enum:1 The session target is the enum
profile match table 1.
The valid Mapping type definitions for the peer are as
follows:
ipv4 - Syntax: ipv4:w.x.y.z:port or ipv4:w.x.y.z
dns - Syntax: dns:host.domain:port or
dns:host.domain
ras - Syntax: ras
settlement - Syntax: settlement
enum - Syntax: enum:
loopback - Syntax: loopback:where
'where' string is defined as follows:
rtp - loopback is performed at the transport protocol
level.
Local loopback case:
rtp - the session application sets up an RTP stream to
itself (i.e. actually allocates a port pair and opens
the appropriate UDP sockets). It then does the full
RTP encapsulation, sends the packets to the loopback
IP address, receives the RTP packets, and hands the
compressed voice back to the CODEC. This tests the
entire local processing path, both transmit and
receive, in the router, as well as all of the above
paths.
Remote loopback case:
rtp: RTP packets received from the network are decapsulated and
immediately re-encapsulated in the outbound RTP
stream, using the same media clock (i.e. timestamp)
as the received packet. They are then sent back to
the remote source router as if the voice had
originated on a telephony port on the local router. |