Alcatel Unleashed

In order to optimize the start of the application when the telephony state of all the users is required to its initialization, the following solution is proposed: - New method POST …/telephony/state/snapshot([?loginName=xxx] which doesn’t return any answer but triggers an event (OnTelephonyState) on...

we didn't see anything brought by last version which could explain this behahavior. However, it will be interesting to know how the requests are thrown: are they in sequential mode or in parallel mode ? We can already say that OXE CMIS simultaneous client number is limited ( probably maximum 4 paral...

bloody regression brought by a previous correction on empty default attribute value, which is should be set only for a set operation, not for a get operation.
Will be fixed in next one

ok: the problem appears in multidevice user configuration and is located at OXE level: if the request contains overflow to "none" but includes the associated number with unchanged value, the overflow is set to no_answer default value. (the same operation on mono device user is working) The...

Cannot reproduce the pb. (doing same operations) The cause may be that management PBX events are no longer received by O2G: Please: - if possible check OXE Subscriber/Dynamic_State_User to check if the delete command really runs and provide logs: - put cache module in debug (from .../api/Log4jAdmin ...

Sure you should receive only one. Unable to reproduce the pb myself.
Is there any specific configuration ?

SumUp of the pb ============== some objects like Station_Group url path cannot be built only from the result of the previous request. For example, a GET ../pbxs/{nodeid}/instances returns the list of first level of sub-objects like Subscriber or Group but no GET action on ../pbxs/{nodeid}/instances/...

in build 29. For a string attribute, the message "value null is not allowed for attribute xxx" is returned if the attribute is present, and the string value contains [] or [null]: this control is done at O2G level. To set an empty value: use [""], like with mgr. For some objects,...

We agree that there is an incoherence between MIB mandatory attributes and the request rejection an we have to analyze deeply where is the blocking point. In the meantime, if you want to bypass the problem, you need to put the "Attached_Stations" attribute in your request, with an empty va...

ok, it's a bug due to bad handling of complex attribute set (like skill set in operator_data).
Fixed in 028: need to enhance PbxAttribute element in order to add a possible complex returned value)