How Dial Rule Actions Affect Sip Headers - Polycom RealPresence DMA 7000 System Operation Manual

Function name and parameters
getPeerPort()
getPeerTransport()

How Dial Rule Actions Affect SIP Headers

The following table shows how different dial rule actions apply a preliminary script's modified dial string to
the output SIP headers in a SIP call.
Dial rule action
Resolve to registered endpoint
Resolve to external address
Resolve to service prefix
Resolve to peer proxy
Resolve to IP address
Polycom, Inc.
Details
Return value:
• If invoked from an External SIP Peer postliminary script, returns the IP
network Port configured for this SIP peer.
• Otherwise, returns the empty string.
Return value:
• If invoked from an External SIP Peer postliminary script, returns the
Transport type configured for this SIP peer.
• Otherwise, returns the empty string.
Output SIP headers
The To header is replaced with the modified dial string. The request URI is
based on the contact address of the registered endpoint, and not replaced
with the modified dial string.
The To header and the request URI are both replaced with the modified dial
string.
For a SIP peer proxy of type OCS:
The To header is replaced with the modified dial string. The request URI is
based on the address, port, and transport type of the proxy, and not
replaced with the modified dial string.
For a SIP peer proxy of type Other:
The To header and the request URI are both replaced with the modified dial
string.
For a SIP peer proxy of type OCS:
The To header is replaced with the modified dial string. The request URI is
based on the address, port, and transport type of the proxy, and not
replaced with the modified dial string.
For a SIP peer proxy of type Other:
The To header and the request URI are both replaced with the modified dial
string.
The To header and the request URI are both replaced with the modified dial
string.
Call Server Configuration
257