Administrator’s Guide - SoundPoint® IP / SoundStation® IP

Features

the case of static server lists, when a server registration fails, registration will be attempted on another server. If the phone is not registered to the first server in the list when registration fails, it will start by trying to register to the first server. When mak- ing a new call, if the INVITE fails, the other servers in the list will be tried one by one for routing signaling until the last server is tried.

Definition of signaling failure (registration or start of call):

If TCP is used: The signaling fails if the connection fails or the Send fails.

If UDP is used: The signaling fails if ICMP is detected or if the signal times out. If the signaling has been attempted through all servers in the list and this is the last server then the signaling fails after the complete UDP timeout defined in RFC 3261. If it is not the last server in the list, the maximum number of retries using the configurable retry timeout is used. For more information, refer to 4.6.1.1.2 Server <server/> on page 85 and 4.6.2.1 Registration <reg/> on page 149.

3.6.5.1DNS SIP Server Name Resolution

If a DNS name is given for a proxy/registrar address, the IP address(es) associated with that name will be discovered as specified in RFC 3263 - Locating SIP Servers. If a port is given, the only lookup will be an A record. If no port is given, NAPTR and SRV records will be tried, before falling back on A records if NAPTR and SRV records return no results. If no port is given, and none is found through DNS, 5060 will be used.

Refer to http://www.ietf.org/rfc/rfc3263.txt for an example.

Note

Failure to resolve a DNS name is treated as signalling failure that will cause a fail over.

3.6.6Microsoft® Office Live Communications Server 2005 Integration

SoundPoint® IP phones can used with Microsoft® Office Live Communications

Server 2005 and Microsoft® Office Communicator to help improve business efficien- cies and increase productivity and to share ideas and information immediately with business contacts.

Copyright © 2006 Polycom, Inc.

69

Page 77
Image 77
Polycom 1725-11530-200 Rev A1 Microsoft Office Live Communications Server 2005 Integration, DNS SIP Server Name Resolution