External SIP Peer Device Management
Polycom, Inc. 103
Port The SIP signaling port number. Defaults to the standard
UDP/TCP port, 5060. If the peer server is using a
different port number, specify it.
If left blank, the system uses the full RFC3263
procedure to determine the port via DNS.
Use route header Add a Route header with the peer’s Next hop address
value to the message. Applies to both forwarded
messages and external REGISTER messages.
If not selected, the only valid Request-URI
configurations are those that use the peer's Next hop
address value for the URI host.
Prefix range The dial string prefix(es) assigned to this peer server.
Enter a single prefix (44), a range of prefixes (44-47), or
multiple prefixes separated by commas (44,46)
If your dial plan uses the Dial services by prefix dial rule
(in the default dial plan) to route calls to services, all dial
strings beginning with an assigned prefix are forwarded
to this peer server for resolution.
Note: For a SIP peer, the dial string must either include
the protocol or consist of only the prefix and user name
(no @domain). For instance, if the SIP peer’s prefix is
123, the dial string for a call to alice@polycom.com
must be one of the following:
sip:123alice@polycom.com
sips:123alice@polycom.com
123alice
If your dial plan instead uses a rule that you create to
apply the Resolve to external SIP peer action, there is
no need to specify a prefix.
Strip prefix If selected, the system strips the prefix when a call that
includes a prefix is routed to this peer.
Type For a Microsoft Office Communications Server or Lync
Server 2010, select Microsoft. Otherwise, select Other.
Selecting Microsoft implicitly adds the Destination
network value to the Domain List (if not already there)
and automatically selects the Postliminary settings that
are correct for most deployments with Lync Server
2010, but you can modify them if necessary.
Transport type The transport protocol to use when contacting this peer
server. The default is UDP.
Auto detect tells the system to select the protocol as
specified in RFC 3263, and is not valid if Next hop
address is a numeric IP address instead of a
host/domain name.
Table 5-15 Edit External SIP Peer dialog box
Field Description