Sip Peer Postliminary Output Format Options - Polycom RealPresence DMA 7000 System Operation Manual

Field
CsTrustedApplication
ServiceGruu
External Registration
See also:
External SIP Peer
Device Authentication
Add Authentication Dialog
Edit Authentication Dialog
Add Outbound Registration Dialog
Edit Outbound Registration Dialog
Script Debugging Dialog for Preliminaries/Postliminaries

SIP Peer Postliminary Output Format Options

This section includes the following information to help with the postliminary settings for an external SIP peer:
To Header Format Options
●
Request-URI Header Format Options
●
Free Form Template Variables
●
To Header and Request-URI Header Examples
●
To Header Format Options
The settings available on the Format list for the To header are described below. If a user is present in the
URI, the user is always preserved except when Free Form Template is selected.
Use original request's To — The To header from the original request is copied and used as is. Equivalent
to template:
"#otdisplay#" <#otscheme#:#otuser#@#othost#>
No Display, use original request's To — The To header from the original request is copied and used. If a
display parameter is present, it's removed. Equivalent to template:
<#otscheme#:#otuser#@#othost>
Polycom, Inc.
Description
The GRUU value that the system should use when communicating with Lync
clients that connect to VMR conferences.
When enabled, the RealPresence DMA system includes the text field value in
the signaling it sends to Lync clients that have joined VMR conferences. This
identifies the RealPresence DMA system as a trusted application when
communicating with these clients.
Enabling this option can prevent calls from Lync clients to VMRs that are
many hours in length from disconnecting unexpectedly. See the
Unified Communications in a Microsoft Environment Solution
Deployment Guide
for information on obtaining the GRUU value to populate
this field.
Lists any outbound registration configurations associated with this SIP peer
and lets you add, edit, or delete registrations. Multiple registrations may be
associated with a SIP peer.
Device Management
Polycom
114