Polycom Version 2.0.3B manual Protocol in Application Configuration File, Boot server

Page 41

Technical Bulletin

SoundPoint ® IP, SIP 2.1

2.Do not use OutBoundProxy configurations on the phone if the OutBoundProxy could be unreachable when the fallback occurs. SoundPoint IP phones can only be configured with one OutBoundProxy per registration and all traffic for that registration will be routed through this proxy for all servers attached to that registration. If Server 2 is not accessible through the configured proxy, call signaling with Server 2 will fail.

3.Avoid using too many servers as part of the redundancy configuration as each registration will generate more traffic.

4.Educate users as to the features that will not be available when in “fallback” operating mode.

Configuration File Changes

Configuration changes can performed centrally at the boot server:

Central

Configuration file: sip.cfg

Specify global primary and fallback server configuration

(boot server)

 

parameters.

 

For more information, refer to Protocol in Application

 

 

 

 

 

Configuration File on page 7.

 

 

 

 

Configuration file:

Specify per registration primary and fallback server configuration

 

phone1.cfg

parameters values that override those in sip.cfg.

 

 

For more information, refer to Registration in Per-Phone

 

 

 

Configuration File on page 8.

 

 

 

 

Protocol in Application Configuration File

The <voIpProt/> attribute includes:

Server <server/> on page 7.

Server <server/>

This configuration attribute now includes:

Attribute

Permitted Values

Default

Interpretation

 

 

 

 

voIpProt.server.x.lcs

0, 1

0

This attribute overrides the

 

 

 

voIpProt.SIP.lcs .

 

 

 

If set to 1, the proprietary “epid”

 

 

 

parameter is added to the From field

 

 

 

of all requests to support Microsoft

 

 

 

Live Communications Server.

 

 

 

 

7

Image 41
Contents SIP 2.0 Administrator’s Guide SoundPoint/SoundStation IP SIP Polycom, Inc Handset, Headset, and Speakerphone Configurable Feature KeysAttribute Default LCD Backlight Attribute Permitted Default Interpretation ValuesExpanded Memory and Expanded Flash Memory Permitted Attribute Values Default InterpretationDefault RAM Disk ramdisk Permitted Values Default InterpretationMicroBrowser Attribute Values 6 G.722 Audio CodecAttribute Default Receive rxEq USB Diagnostics Administrator’s Guide SoundPoint IP / SoundStation IP Syslog Digit MapBilling Code Supported Platforms Unsupported Platforms Server RedundancyDaylight Saving Time Changes for Disable Message Waiting Indicator by RegistrationDST Platform Key IDs 9.1 sip.cfg Miscellaneous Configuration File ChangesPorted on SoundPoint IP Attribute Permitted Default Interpretation Values Phone1.cfg Device Parameter Boot server Sip.cfg Configuration File ChangesIntroduction CentralLocal Dial Plan in Application Configuration FileAttribute Permitted Default Interpretation Values Permitted Attribute Values Default Interpretation Attribute Permitted Values Default Interpretation Dial Plan in Per-Phone Configuration FileDial Plan in Application To Digit Map digitmap/ on Dialplan.x.digitmap is Trademark InformationBilling Code Entry on SoundPoint IP Phones with Sylantro Billing Code EntryTrademark Information Syslog on SoundPoint IP Phones Name Possible Values Description Network Configuration ChangesName Possible Values Description Flash Parameter ConfigurationSIP Server Fallback Enhancements on SoundPoint IP Phones Terminology SIP 2.0 Administrators GuideExample Deployment SIP 2.1 Server Fallback ImplementationReg.1.server.2.address=172.23.0.1 Behavior When the Primary Server Connection Fails Before SIP Recommended Practices for Server Fallback DeploymentsChanges From Previous Phone Behavior Releases Before SIP Boot server Protocol in Application Configuration FileReferences Trademark Information Registration in Per-Phone Configuration File