optiPoint 410/420 S general information 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 06:30, 8 September 2006 by Horemu (talk | contribs) (Please Note)
Jump to: navigation, search

The protocol version SIP V6.0 is the successor of SIP versions like SIP V5.0 and SIP V4.1.

New features

For detailled information about each firmware release refer to optiPoint 410/420 S Release Notes.

General differences between SIP V5.0.31 and SIP V6.0:


  • User mobility
  • Mobility User Migration
  • Mobility enabled with a data item instead of a Mobility Key
  • Forced logoff


  • Configurable host name
  • User data download and upload using message fragmentation and chunking
  • SNMP trap for invalid Logoff


  • Security Step 1 Basic Password
  • Improved passowrd policy (IEEE 802.1x)


  • Timer triggered User Profile update
  • Laser keyboard
  • Default Profile

Scope of affected products

For compatibility and compliance see SIP V6.0 optiPoint compatibility.


consisting of:


Other products

Please Note


  • When the state prompting for the plug and play E.164 is pushed onto the stack, the idle timeout value is set to 21600 sec (6 hours). Activity on the phone will reset the timer to the normal 60 seconds. While the prompt is displayed it will not be possible to administer the phone using the DLS or WBM.
  • The option in DLS to force an update also on phones which are not idle shall not be executed. This is causing problems in database of the HiPath 8000.
  • Feature IEEE 802.1x was not tested in field trials, because there was no customer available. 802.1x was tested only in systemtest; but 802.1x was allready released in HFA (V5.1.30).
  • In case of a memory leak or excessive memory fragmentation the phone is forced to reboot when a minimum limit has been reached. Reboot may also happen at 01:10 AM when idle if it is seen that the maximum block size available in the memory is below a preset limit. Depending on the phone usage such a reboot can happen after several month (single line) or about 15 – 30 days (often used phone with 10 lines).
  • For the registration timer please use values greater than 300 sec.
  • When a phone is configured with static IP address, it could happen that after upgrading the phone to SIP V6.0.X, the phone network setting got changed. Now instead of a static IP address, the DHCP got enabled. The workaround is to reconfigure the static IP address manually.
  • When performing a factory reset at the phone, it is now necessary to ensure that call control is on the phone, not the DSM. The reset key sequence will not work in other case.
  • Note that QoS default settings are set to ON (both L2 and L3).

optiPoint display module (for standard and advance phones only)

  • Maximum two sidecars are allowed (optiPoint display module inclusive).
  • optiPoint display module is to connect direct (as first side car) to the optiPoint phone.
  • Usage of Java Applications on an optiPoint display module is not supported. Java Applications running on the optiPoint display module have impact to memory management in the phone and can force phone reboots because of low memory or memory fragmentation.


  • The optiPoint 410/420 S phone is to connect to a Switch. The phone is working also on a Hub, but without a guarantee of quality.
  • The optiPoint 410/420 S phone is to connect to a 100MB full duplex network. The phone is working also on 10MB, but without a guarantee of quality.
  • LAN Ports connectivity:
  • Port 1 = Network (straight or crossed cable)
  • Port 2 = PC (straight cable)
Power over Ethernet is applicable, if Port 1 is used with a straight cable.

Firmware and configuration files

  • The firmware is available also as *.fli to use by NetBoot server (together with the TFTP server). For this procedure see the NetBoot manual.
  • If the Platform software (bootrom.fli) requires upgrading, it is necessary to use the NetBoot server (together with the TFTP server). For this procedure see the NetBoot manual.
  • MOH files download is possible in principle, but not supported with the current SIP phone versions.