Polycom 3725-76302-001O manual Free Form Template Variables, Variable Description

Device Management

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:#phost#:#pport#;transport=#ptransport#

Free Form Template — Format defined in associated Template field is used without further modification. See Free Form Template Variables on page 116 and To Header and Request-URI Header Examples on page 117.

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 Add Outbound Registration Dialog Box on page 118), you can use the variables in the table below 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	Description
otdisplay	Original To header's display name.
otuser	User portion of the original request's To header URL field.
othost	Host/IP portion of the original request's To header URL field.
otscheme	Original To header's URL scheme (sip, sips, tel).
phost	Peer's configured IP/FQDN (next hop address).
pscheme	Peer's configured scheme based on transport (sip, sips).
oruser	User portion of the original request's Request-URL field.
orhost	Host/IP portion of the original request's Request-URL field.
orscheme	Original request's URL scheme.
pnetORhost	Destination network parameter if specified, otherwise the peer's configured IP/FQDN.
pport	The port specified for this SIP peer.
ptransport	The transport type specified for this SIP peer.

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.

For the To header, the contents of the Template field specify the complete header except for the header name (“To”).

The @ symbol is always removed if no user is present in the result.

Polycom, Inc. 116