[Spce-user] Sems Error + hangup on Reinvite + Update

[Alex Lutay]

Hi,

Reported internally for investigation as TT#20072.
I do not recall such issues for PRO/Carrier, need investigation.

Thank you for the bug report here.

On 04/07/2017 01:17 PM, Jon Bonilla (Manwe) wrote:
>>> I've been checking the capture and the log and seems like the problem is not
>>> that. I think the problem is that sems doesn't like if the answers are in
>>> different order?
>>>
>>> sems sends INVITE + UPDATE to aleg.
>>>
>>> aleg sends 200 UPDATE (nosdp) and 200 INVITE (sdp) to sems.
>>>
>>> The sdpless response is the update's response.   
>>
>> Updating again for the list history:
>>
>> I've seen that sems sends INVITE-UPDATE to proxy, proxy sends INVITE-UPDATE to
>> lb and lb sends UPDATE-INVITE to caller. The lb (!!!) is taking longer to
>> process the INVITE. 
>>
>> Can't find any other solution here but reject the UPDATES. I removed UPDATE
>> from the supported methods in the proxy configuration and will see if nothing
>> breaks.
>>
>> Note: Forced sst configurations to only INVITE.
> 
> For the record:
> 
> I have found this issue in 7 spce installations across Europe. All of them the
> same case and had to remove UPDATE support to avoid sems going crazy.

-- 
Alex Lutay