<div dir="ltr">Hi Antonio,<div><br></div><div>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.</div><div><br></div><div>In your scenario, FS should process the UPDATE and remove the call from hold, responding with 200Ok (a=sendrecv).</div><div><br></div><div>Thanks,</div><div>Mohit</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 25, 2017 at 6:27 PM, Antonio Silva <span dir="ltr"><<a href="mailto:asilva@wirelessmundi.com" target="_blank">asilva@wirelessmundi.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
i've seem some dialog with avaya device and i'm not sure if the<br>
behaviour is the correct from fs on update request. I have:<br>
<br>
FS <--------> remote end<br>
<br>
invite-----><br>
<---- trying<br>
<----- 200ok<br>
<----- invite (a=sendonly)<br>
200ok (a=recvonly) ----- ><br>
<----- update (a=sendrecv)<br>
(1)200 ok ----><br>
<---- bye<br>
ack ----><br>
<br>
<br>
<br>
in (1) FS do not change the call flow and it stays in hold. This is the<br>
correct behaviour? should it process the update and remove the call from<br>
hold, responding wih 200 ok (a=sendrecv) ?<br>
I could file a jira if you think is a bad behaviour..<br>
<br>
<br>
Normally, instead of the update would expect an invite (a=sendrecv)...<br>
so i'm pretty sure that it could be a bug in the avaya device.<br>
<br>
<br>
<br>
Thanks,<br>
António<br>
<br>
<br>
<br>
<br>
<br>
<br>
______________________________<wbr>______________________________<wbr>_____________<br>
Professional FreeSWITCH Consulting Services:<br>
<a href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a><br>
<a href="http://www.freeswitchsolutions.com" rel="noreferrer" target="_blank">http://www.<wbr>freeswitchsolutions.com</a><br>
<br>
Official FreeSWITCH Sites<br>
<a href="http://www.freeswitch.org" rel="noreferrer" target="_blank">http://www.freeswitch.org</a><br>
<a href="http://confluence.freeswitch.org" rel="noreferrer" target="_blank">http://confluence.freeswitch.<wbr>org</a><br>
<a href="http://www.cluecon.com" rel="noreferrer" target="_blank">http://www.cluecon.com</a><br>
<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.<wbr>freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" rel="noreferrer" target="_blank">http://lists.freeswitch.org/<wbr>mailman/listinfo/freeswitch-<wbr>users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" rel="noreferrer" target="_blank">http://lists.<wbr>freeswitch.org/mailman/<wbr>options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" rel="noreferrer" target="_blank">http://www.freeswitch.org</a></blockquote></div><br></div>