Content
D-SERIES
Web User Interface
N/A
Phone User Interface
N/A
Initial Firmware Version
8.7.3
XML Configuration
<csta_legacy_control perm="PERMISSIONFLAGS">VALIDVALUE</csta_legacy_control>
Description
Our csta-stack is constantly evolving but some scripts or tools might rely on us doing csta a certain way. Whenever we change our csta-stack we'll increase the default value of this setting. When you've written skripts that suddenly fail after upgrading your snom-firmware you should consider setting a lower number into this setting.
0 (before 8.7): csta via http
1 (since 8.7.1): initial uaCsta version (csta via sip)h1. changed behavior of some csta-http-commands since they now use a new, common csta-stack. Affected methods are:
- AnswerCall
- ClearConnection
- HoldCall
- RetrieveCall
- TransferCall
- MakeCall
2 (since 8.7.3): Changes are:h1. in SnapshotDeviceResponse:
- old: <localConnectionState>connected</localConnectionState>
- new: <localCallState><compoundCallState><localConnectionState>connected</localConnectionState></compoundCallState></localCallState>h1. in ConferencedEvent / ConferenceCallResponse:
- only one of the two affected local connections gets reportedh1. HeldEvent:
- switching <DeviceID> of <heldConnection> is normally set to the local device (instead of remote party as previous), only inside a conference when phone puts one member on hold will we still contradict the spec and put the remote-device-id thereh1. RetrievedEvent:
- switching <DeviceID> of <retrievedConnection> is normally set to the local device (instead of remote party as previous), only inside a conference when phone puts one member on hold will we still contradict the spec and put the remote-device-id there
3 (since 8.7.3.18): Changes are:h1. in TransferredEvent:
- now spelled with single r: TransferedEvent (CSTA-Spec ECMA-323 says to use one r here while it spells transferringDevice and others with two r's)
- *be aware: versions 8.7.4.1, 8.7.4.2, 8.7.4.3, 8.7.4.4 and 8.7.4.5 always spell with single r no matter what the value of this setting is
- transferringDevice is no longer fixed to always just name one of the remote parties - instead it correctly names either the local or a remote party depending on who actually did initiate the transferh1. when using CSTA via http, the style for the SingleStepTransferCall-service changed from this to that (only since 8.7.4, not in 8.7.3)
4 (since 8.7.4.8): Changes are:h1. in DeliveredEvent: now setting calledDevice independendly from alertingDevice for incoming calls. I.e. when the to-header contains another identity than the one ringing on the phone, e.g. "sales@snom.com", than that (to-)uri will be reported as calledDevice.h1. FailedEvent now includes non-optional lastRedirectionDevice
5 (since 10.1.73.16): The P-Asserted-Identity header in SIP responses to an outgoing INVITE is taken into consideration (given correct prioritization in contact_source_sip_priority) when signalling alertingDevice, answeringDevice, and failingDevice. Before these elements where always the same as calledDevice.
Valid Values
an integer >=0 and <=5
Default Value
5