Views

optiPoint 410/420 S upgrade to SIP V6.0

The Wiki of Unify contains information on clients and devices, communications systems and unified communications. - Unify GmbH & Co. KG is a Trademark Licensee of Siemens AG.

Revision as of 08:19, 7 September 2006 by Horemu (talk | contribs)
Jump to: navigation, search

This information describes distinctions while upgrading optiPoint 410/420 phones to SIP V6.0. For common upgrade procedure (download application) refer to the Administration Manual.

The SIP V6.0 firmware can be loaded onto the phone via FTP (if supported by the software being upgraded from):


Upgrading from CorNet IP

  1. Upgrade phone to SIP V6.0.
  2. Factory reset the phone (see Factory reset optiPoint 410/420 S phones).
  3. Apply configuration.

Workaround for upgrading multiline phones from SIP V4.0.x or earlier

On multiline configured phones the following procedure is needed.

  1. Make sure that the phone is getting an IP address via DHCP.
    Use the Deployment Tool to scan the IP range and find the MAC address of each phone.
  2. Save the configuration (upload configuration file) by WBM. Note the correlation of saved configuration file with phone’s extension and MAC address to make sure to load the right file back to the right phone.
  3. Open the saved configuration file (for example with WordPad) to edit the file.
    There are differences in the multiline records between SIP V4.0 and SIP V4.1 as described in the multiline record differences below. Add the extra fields to the line records.
  4. Reset the phone to factory default (see Factory reset optiPoint 410/420 S phones).
  5. Upgrade phone to SIP V6.0 according to upgrade from SIP V4.1.15 or earlier.
  6. Restore the modified configuration via WBM.

Non-multiline configured phones are not affected.

Differences in multiline records between SIP V4.0 and SIP V4.1

The order of the fields between SIP V4.0 and SIP V4.1 has mixed up a little bit.

The fields in the line key record for SIP V4.0 are:

LINEKEYREC1=A^B^C^D^E^F^G^H^I^
  • A: URI
  • B: Password
  • C: Realm
  • D: SIP ID
  • E: Primary flag
  • F: Ring flag
  • G: Hunt ranking
  • H: 1
  • I: Shared line type

Example:

LINEKEYREC1=496973998331^test^test^test^1^1^1^1^0^

The fields in the line key record for SIP V4.1 are:

LINEKEYREC1=A^B^C^D^E^F^G^H^I^J^K^L^M^N^

  • A: URI
  • B: Password
  • C: Realm
  • D: SIP ID
  • E: (Space)
  • F: Hot line destination
  • G: Primary flag
  • H: Ring flag
  • I: Hunt ranking
  • J: Line type
  • K: Hidden on overview flag
  • L: Overview position
  • M: Intrusion bars flag
  • N: HLD active flag

Example:

LINEKEYREC1=496973998331^test^test^test^ ^1^1^1^1^0^1^0^0^0^

Attention: If this procedure is not done on multiline phones and SIP V4.0 is upgrated to SIP V6.0, the phone will go into a continues restart loop!

Upgrading from SIP V4.1.15 or earlier

If you want to upgrade multiline SIP phones V4.0.x or earlier first of all consider the information to upgrade multiline phones from SIP V4.0.x or earlier.

From SIP V4.1.20 QoS default settings are set to ON (both L2 and L3). This may cause problem, when the phone sends tagged frames and your network can’t handle these tagged frames.

  1. Change the phone's QoS L2 setting to ON, then back to OFF. This will store the setting in the phone’s database and the default value is not used.
  2. Reboot the phone.
  3. A loss of configuration information may occur when upgrading from a SIP V4.1.15 or earlier via the DLS.
    In order to avoid losing settings, one of the following workarounds is recommended on upgrading from V4.1.15 or earlier.
  • Upgrade via the WBM, instead of DLS.
  • If upgrading via DLS:
  1. Download the configuration file via the WBM.
  2. Upgrade phone to SIP V6.0.
  3. Restore the configuration via WBM.

Upgrading from SIP V5.0.15 or earlier

In SIP V6.0 the VLAN discovery default settings are set to DHCP. This may cause problem, when the phone was configured for manual VLAN discovery.

  1. Change the phone's VLAN discovery setting to DHCP, then back to manual. This will store the setting in the phone’s database and the default value is not used.
  2. Reboot the phone.
  3. Upgrade phone to SIP V6.0.