Polycom RealPresence DMA 7000 System Operation Manual page 116

Table of Contents

Advertisement

No user, configured peer's Destination Network or next hop address — Uses the Destination network
value if specified, otherwise the peer's Next hop address value. Equivalent to template:
#pscheme#:#pnetORphost#
Original user, configured peer's Destination Network or next hop address — Uses the user in the
original, if specified, but replaces the host with the Destination network value, if specified, or the peer's
Next hop address value. Equivalent to template:
#pscheme#:#otuser#@#pnetORphost#
Default Request-URI for Microsoft — Equivalent to template:
sip:#oruser#@#pnetORphost#:#pport#;transport=#ptransport#
Request-URI for Microsoft without CSS — Equivalent to template:
sip:#phost#:#pport#;transport=#ptransport#
Free Form Template — Format defined in associated Template field is used without further modification.
See
Free Form Template Variables
Free Form Template Variables
In the Template fields on the Postliminary tab, and when specifying a Request-URI or other headers for
outbound registration (see
table entered as #variable name# (case insensitive). The system replaces the variables with the
corresponding values as shown below.
You can also use these variables (without # delimiters) in a customized script.
Variable
otdisplay
otuser
othost
otscheme
phost
pscheme
oruser
orhost
orscheme
pnetORphost
pport
ptransport
In addition to the variables, you can enter any values acceptable for the Request-URI or To header.
For the Request-URI, the contents of the Template field specify only the URI portion of the full Request line.
Depending on network configuration, a Route header may be required.
Polycom, Inc.
and
To Header and Request-URI Header
Add Outbound Registration
Description
Original To header's display name.
User portion of the original request's To header URL field.
Host/IP portion of the original request's To header URL field.
Original To header's URL scheme (sip, sips, tel).
Peer's configured IP/FQDN (next hop address).
Peer's configured scheme based on transport (sip, sips).
User portion of the original request's Request-URL field.
Host/IP portion of the original request's Request-URL field.
Original request's URL scheme.
Destination network parameter if specified, otherwise the peer's configured IP/FQDN.
The port specified for this SIP peer.
The transport type specified for this SIP peer.
Dialog), you can use the variables in the following
Device Management
Examples.
116

Advertisement

Table of Contents
loading

Table of Contents