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 16:42, 26 September 2006 by Christian.kaehler (talk | contribs) (remove SNMP and chunk)
Jump to: navigation, search

Here you find general information about SIP V6.0 on optiPoint 410/420 S. SIP V6.0 is the successor of SIP versions like SIP V5.0 and SIP V4.1, used on optiPoint 410/420 S phones.

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

User Mobility enables users designated as mobile users to log onto a phone and by doing so have the phone automatically configured to take on all the attributes of the mobile user’s phone. When the mobile user logs off the phone configuration will revert to the attributes that it had before the mobile user logged on.

The attributes affected encompass all the optiPoint features within the scope of the hardware of the model of phone being used (except external Java applications). The DLS Tool (Deployment Service) will supply the data for the affected attributes. The DLS is mandatory to manage all necessary data to support the User Mobility Feature, like configuration of profiles (mobile user, basic), managing the mobile log on and log off processes, migration of a standard user to a mobile user or supporting forced log off.

This DLS based User Mobility Feature is currently only supported in a HiPath 8000 V2.0 environment.


  • Configurable host name

Fore many applications (e.g. access to the WBM), it is more convinient to use symbolic names instead of the telephone's IP address. Hence, V6 introduces host names: When the telephone requests its IP address, it sends – apart from other information – its default host name to the DHCP server. The default host name consists of telephone model + type + MAC address (e.g. OP410STD0001e325a845). The DHCP server forwards this name to the DNS server, together with the IP address assigned. The default host name can be changed to individual values like 'Phone47123' by the administration.


  • Security Step 1 Basic Password
  • Improved passoword 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.
  • 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).
  • The key layout has the priority on the key mapping. If an existing key has the same position as a Key layout key, this existing key will not be displayed and not sent to another free position. The key coming from the Key layout will be displayed on this position.
  • RTP statistic functionality is not supported.
  • Multi Line operation is limited to 10 lines (like mentioned in datasheet)
  • Callback – no reply is not released. Feature access to Callback – no reply should be prohibited.
  • 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).


  • optiPoint 410/420 S phones require a switched LAN-infrastrcuture. The phone is working in a shared LAN-infrastructure (Hub) too, but without any guarantee of quality.
  • The optiPoint 410/420 S phone is to be connected to a 100MB full duplex network. The phone is working also on 10MB, but without a guarantee of quality (e.g. PoE is not working properly)
  • 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.
  • If phone is powered locally and via PoE the power class detection is disabled. Phone will request in this case Power-class 0 (default) to the switch.


  • Supported devices are all models of optiPoint 410/420 S. All other devices (e.g. 3rd party phones) are not supported.
  • The Mobility feature is supported and released only at one HiPath 8000 and one DLS for the moment, but as an exception to this restriction, more than one Deployment Service can be connected to one HiPath 8000 with following limitations:
  • Different DLS server IP address must be assigned to the phones via DHCP.
  • No interworking between the DLS servers.
  • No Mobility between phones, which are assigned to different DLS servers.
  • The maximum number of mobile users configured in DLS which are able to log on to any mobility-enabled phone of optiPoint 410/420 S is 10000.
  • The maximum number of mobility enabled phones of optiPoint 410/420 S, e.g. a mobile user may log on to a phone configured with mobility enabled, is 3000.
  • The maximum number of logons/logoffs of mobile users (mobile user actions) per hour is 2500.
  • The maximum number of workpoints (optiPoint 410/420 S) registered at DLS is 6000. If neither DLS Mobility nor HFA workpoints are configured, the maximum number of SIP workpoints (optiPoint 410/420 S) registered at DLS are 20000.
  • There is no mechanism to perform an automatic logon/logoff (e.g. time based).
  • Cluster systems are not supported. HiPath 8000 do have a clustered design.
  • Java applications will not be transferred in the mobility solution. They are still locally stored in the phone.
  • The Domain Name of a mobile user is displayed during the mobile user is logged on. There is an indication, that a mobile user is logged in. The basic number of the phone is unavailable during the login period of a mobile user.
  • DLS is available on Microsoft Windows systems and not on Linux.
  • The call forward for a mobile user in logged off status can be configured during a logged in phase only. There is no possibility to configure the call forward in logged off status.

optiPoint display module related (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 recommended. Java Applications running on the optiPoint display module may have an impact to memory management in the phone and can force phone reboots because of insufficient memory or memory fragmentation.
  • The Clear User Data function does not clear out the Java midlet data. This has to be cleared through the midlet itself.
  • When a phone is configured to dial by both name and number, the optiPoint display module virtual keyboard does not allow alpha character input.
  • DSS keys are not supported when using call control on the optiPoint display module.

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.


  • Changes were made under the audio options in the config menue. Now the settings seize not only for handsfree mode, but also for the handset and headset (directly connected or connected by acoustic adapter).
Mode Room characteristic Environment
Mode 3 (Muffled) Room contains mostly soft surfaces, lots of fabric on furniture, walls and floor. Quiet room.
Mode 1 (Normal) Room contains mixed surfaces on the walls, desk and floor. A mixed surface will be where carpet is on the floor, painted walls and soft furniture. Normal room with a little backround noise.
Mode 2 (Echoic) Room contains hard surfaces on the walls, desk and floor where sound can easily echo. Loud Room with many backround noise, like at callcenters (disturb signall the same as wanted signal).
  • The external devices (i.e. headset/loudspeaker via acoustic adapter) are only supported with G.711 codec. If an acoustic adapter is mounted, only G.711 audio codec can be used.
  • High quality ring tones are not available.
  • Audio loopback test does not work.
  • The Acoustic adapter does not work with Power over Ethernet. To use the Adapter, the external power supply is required.