Device Management
Polycom, Inc. 115
<#pscheme#:#otuser#@#orhost#>
No Display, use peer’s Destination Network or next hop address — Uses the Destination network
value if specified, otherwise the peer’s Next hop address value. If a display parameter is present, it’s
removed. Equivalent to template:
<#pscheme#:#otuser#@#pnetORphost#>
Default To header for Microsoft. — Equivalent to template:
"#otdisplay#" <sip:#otuser#@#pnetORphost#>
Free Form Template — Format defined in associated Templa te field is used without further modification.
See Free Form Template Variables on page116 and To Header and Request-URI Header Examples on
page 117.
Request-URI Header Format Options
The settings available on the Format list for the Request-URI header are described below (RR= requires
route header):
Use original request’s URI (RR) — The original request’s URI is copied and moved. Equivalent to
template:
#orscheme#:#oruser#@#orhost#
No user, original request’s host (RR) — The user in the original, if any, is removed, but the original host
is used. Equivalent to template:
#orscheme#:#orhost#
No user, configured peer’s next hop address as host — The user in the original, if any, is removed, and
the host is replaced with the Next hop address value for this peer. Equivalent to template:
#pscheme#:#phost#
Original user, configured peer’s next hop address as host — The user in the original is copied, but the
host is replaced with the Next hop address value for this peer. Equivalent to template:
#pscheme#:#oruser#@#phost#
Use user as host (RR) — Uses the user in the original, if specified, as the host value, otherwise the host
value is used as is. Equivalent to template:
#orscheme#:#oruser#
(but if no original user is present, the host value is used as is)
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#
Note: SIP Peers and TLS
If the peer’s transport type is configured as TLS, this setting makes the Request-URI scheme sips
even if the original Request-URI’s scheme was sip. Some SIP peers, such as the Cisco SBC, won't
accept sips in the Request-URI if other headers contain sip. If this problem exists, change Format
to Free Form Template and in the Templa te field, change #pscheme# to #orscheme#.