<div dir="ltr">I could notice it is missing the ACK package from your PEER. Maybe its sending it to the wrong place, maybe its not sending it at all.<div><div>FreeSWITCH will retry 200 OK over and over 'cause it expects an ACK in order to continue.<div><br><div>here are some tips:</div></div></div></div><div><br></div><div>Enable sip trace on the PEER side to check whether its sending ACK or not.</div><div>Compare 200 OK (SDP) from FreeSWITCH in each scenario. Maybe there are differences between them.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 11, 2015 at 5:05 PM, Ben Hood <span dir="ltr"><<a href="mailto:0x6e6562@gmail.com" target="_blank">0x6e6562@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I think you may well have a point.<br>
<br>
I've spent days on this issue and I'm beginning to narrow it down by<br>
breaking the bridging down into the individual legs. I've also been<br>
able to establish RTP flow with the same originator by proxying the<br>
INVITE to a non-FS user agent (i.e. a phone registered with Kamailio).<br>
<br>
I didn't want to leave this post dangling without a some kind of<br>
closure, so I thought I'd just post this status update.<br>
<div class="HOEnZb"><div class="h5"><br>
On Tue, Feb 10, 2015 at 8:33 PM, Michael Jerris <<a href="mailto:mike@jerris.com">mike@jerris.com</a>> wrote:<br>
> I doubt it has anything to do with 180vs183. Check for nat issues in the trace that isn't working.<br>
><br>
>> On Feb 10, 2015, at 2:55 PM, Ben Hood <<a href="mailto:0x6e6562@gmail.com">0x6e6562@gmail.com</a>> wrote:<br>
>><br>
>> Hi all,<br>
>><br>
>> I'm wondering what influences Freeswitch's signalling response when it<br>
>> responds to an INVITE.<br>
>><br>
>> In some instances it appears to follow this sequence:<br>
>><br>
>> Peer -> INVITE (SDP) -> FS<br>
>> Peer <- 100 <- FS<br>
>> Peer <- 183 (SDP) <- FS<br>
>> Peer <- 200 (SDP) <- FS<br>
>> Peer -> ACK -> FS<br>
>><br>
>> Which leads to a successful bridge between two legs.<br>
>><br>
>> But in other instances it appears to follow the sequence:<br>
>><br>
>> Peer -> INVITE (SDP) -> FS<br>
>> Peer <- 100 <- FS<br>
>> Peer <- 180 (SDP) <- FS<br>
>> Peer <- 200 (SDP) <- FS (1st attempt)<br>
>> Peer <- 200 (SDP) <- FS (2nd attempt)<br>
>> ....<br>
>> Peer <- 200 (SDP) <- FS (nth attempt)<br>
>> ....timeout<br>
>><br>
>> I'm not 100% sure whether the remote peer (itself a SIP trunk) doesn't<br>
>> like the 100/180/200 sequence (as opposed to 100/183/200), so I need<br>
>> to find that out for myself.<br>
>><br>
>> But I am wondering what factors influence Freeswitch's decision of<br>
>> what sequence signals to send in response to an INVITE.<br>
>><br>
>> Any pointers appreciated,<br>
>><br>
>> Ben<br>
><br>
><br>
> _________________________________________________________________________<br>
> Professional FreeSWITCH Consulting Services:<br>
> <a href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a><br>
> <a href="http://www.freeswitchsolutions.com" target="_blank">http://www.freeswitchsolutions.com</a><br>
><br>
> Official FreeSWITCH Sites<br>
> <a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
> <a href="http://confluence.freeswitch.org" target="_blank">http://confluence.freeswitch.org</a><br>
> <a href="http://www.cluecon.com" 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.freeswitch.org</a><br>
> <a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
> UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
> <a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<br>
_________________________________________________________________________<br>
Professional FreeSWITCH Consulting Services:<br>
<a href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a><br>
<a href="http://www.freeswitchsolutions.com" target="_blank">http://www.freeswitchsolutions.com</a><br>
<br>
Official FreeSWITCH Sites<br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<a href="http://confluence.freeswitch.org" target="_blank">http://confluence.freeswitch.org</a><br>
<a href="http://www.cluecon.com" 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.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Atenciosamente,<br>Lucas Castro</div>
</div>