Skip to content

Fix for setting call_id by asterisk in all cases

Grzegorz Sluja requested to merge fix_for_update_call_id into release-6.5

There was a possibility that call_id was not updated properly when processed outgoing call. For FXS it is not a problem, but dect is relying on the call_id when closing connection - it was 0 instead of >0 in case of call out to speaking clock hence the issue with not released call happened on BT side. Fix it so that call_id is updated always and also make sure that the call_id is not updated twice

Merge request reports