ECSTA for SIP phones: Multiple device ID assignment in multi-client environments

Observation

In UCServer, "duplicate" lines cannot be managed separately. (location, activation, etc.)

Example screenshot: UCServer Administration – ECSTA line group for SIP phones

Environment

• uaCSTA 
• Clients with overlapping extension range

Target

• 1 uaCSTA Server
• 1 ECSTA instance (dynamic line image)
  

Possible reason

The ECSTA always transfers Line number@ECSTA_instance to the UCServer as "device ID". This device ID is always the same if the extensions are the same.

However, since the UCServer stores settings for the line based on the device ID, both lines cannot be managed separately.

Solution/Procedure

From version 5.0.5.25 of ECSTA for SIP phones, the following registry key (only global for all instances) has to be added:

Now the settings can be managed separately.

Import into a running environment

If the registry key is imported into a running environment, the settings for all lines in the UCServer are lost.

Further information

• The registry entry SupportPhysicalIdentifier is demonstrated in practice in the webinar recording from 44min 26sec: 

  Best practice: Installation and setup of ECSTA for SIP phones (Language: Geman).