Aastra Telecom 41-001343-02 manual SIP Password Masking, SIP Precedence Example, How it Works

Global SIP Settings

SIP Password Masking

The “mask sip password” configuration parameter can be used to mask a user’s SIP account password in the server.cfg and local.cfg files (downloaded from the IP phone’s Web UI troubleshooting page for debug purposes). The parameter is disabled by default.

Configuring SIP Password Masking

Use the following procedure to configure SIP password masking using the configuration files.

Configuration Files

For specific parameters you can set in the configuration files, see Appendix A, the section, “SIP Basic, Global Settings” on page A-61.

SIP Precedence Example

The following example shows the SIP proxy feature and example schema for storage and parsing of the SIP configuration parameters.

The following SIP configuration is assumed:

# SIP network block

sip proxy ip: 10.30.11.154

sip proxy port: 5060

sip registrar ip: 10.44.122.37

sip registrar port: 4020

sip line3 proxy ip: siparator.vonage.com

sip line3 proxy port: 0

Line3 specifies per-line values for proxy IP address and proxy port, so the phone uses those parameter values for SIP calls made on that line. However, because those parameters are part of the SIP network block, the phone does not apply any of the global SIP network block parameters. So even though the global parameters configure a SIP registrar, Line3 on the phone ignores all global network block parameters. Since line3 does not contain a per-line SIP registrar entry, the phone does not use a registrar for that line.

Note:

Global SIP parameters apply to all lines unless overridden by a per-line configuration. Per-line settings are configurable for lines 1 through 7.

Backup Proxy/Registrar Support

The IP phones support a backup SIP proxy and backup SIP registrar feature. If the primary server is unavailable, the phone automatically switches to the backup server allowing the user's phone to remain in service.

How it Works

All SIP registration messages are sent to the primary registrar first. If the server is unavailable, then a new registration request is sent to the backup registrar. This also applies to registration renewal messages, which try the primary server before the backup.

Similarly, any outgoing calls attempt to use the primary proxy first, then the backup if necessary. In addition, subscrip- tions for BLF, BLA, and explicit MWI can also use the backup proxy when the primary fails. Outgoing calls and the previ- ously mentioned subscriptions behave the same as registrations, where the primary proxy is tried before the backup.

You can configure the backup SIP proxy on a global or per-line basis via the configuration files or the Aastra Web UI.

4-58 41-001343-02 REV04 – 05.2014