Views

Difference between revisions of "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.

Jump to: navigation, search
(Limitations)
(Please Note)
Line 54: Line 54:
 
== Please Note ==
 
== Please Note ==
  
* 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.
+
=== General ===
 +
 
 +
* The option in [[Deployment Service|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).
 +
 
 +
=== [[optiPoint display module]] (for standard and advance phones only) ===
 +
 
 +
* Maximum '''two''' sidecars are allowed (optiPoint display module inclusive).
  
* 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.  
+
* optiPoint display module is to connect '''direct''' (as first side car) to the optiPoint phone.
  
* Maximum two sidecars are allowed ([[optiPoint display module]] inclusive, only for standard and advance phones).
+
* 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.
  
* 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.
+
=== Connectivity ===
  
* The option in [[Deployment Service|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]].
+
* 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.
  
* 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).  
+
* 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.  
  
* 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).
 
  
  
 
[[Category:optiPoint]]
 
[[Category:optiPoint]]

Revision as of 06:13, 8 September 2006

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:

SIP

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

IP

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

Security

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

Miscelllanous

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

Scope of affected products

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

Phones

consisting of:

Platforms

Other products

Please Note

General

  • 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).

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.

Connectivity

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