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 |
|
|
| 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
