Hi Antonio,

FS behavior is not correct. Per the standards, UPDATE could be sent mid-dialogue to refresh the remote end. UPDATE could contain an offer if for the caller, there are no existing INVITE or UPDATE transaction with an offer for which the caller did not receive a response from the remote end or for the callee, there are no INVITE or UPDATE transaction with an offer for which the callee did not send a response to the remote end yet.

In your scenario, FS should process the UPDATE and remove the call from hold, responding with 200Ok (a=sendrecv).

Thanks,

Mohit

On Wed, Jan 25, 2017 at 6:27 PM, Antonio Silva <asilva@wirelessmundi.com> wrote:

Hi all,

i've seem some dialog with avaya device and i'm not sure if the
behaviour is the correct from fs on update request. I have:

FS <--------> remote end

invite----->
<---- trying
<----- 200ok
<----- invite (a=sendonly)
200ok (a=recvonly) ----- >
<----- update (a=sendrecv)
(1)200 ok ---->
<---- bye
ack ---->

in (1) FS do not change the call flow and it stays in hold. This is the
correct behaviour? should it process the update and remove the call from
hold, responding wih 200 ok (a=sendrecv) ?
I could file a jira if you think is a bad behaviour..

Normally, instead of the update would expect an invite (a=sendrecv)...
so i'm pretty sure that it could be a bug in the avaya device.

Thanks,
António

_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org