[Spce-user] Fwd: Sipwise sending BYE 60 seconds after INVITE

[James Hurley]

Here's the log, it looks like the BYE is coming from SEMS on port 5080. (
the users in question are 16.james and 16.james_expert )

https://gist.github.com/e865aa36c663665503a1



On Mon, Nov 26, 2012 at 10:54 AM, Jon Bonilla <jbonilla at sipwise.com> wrote:

> El Mon, 26 Nov 2012 10:28:57 -0800
> James Hurley <james at curiousminds.com> escribió:
>
> > I seem to be getting a BYE request after 60 seconds when the clients
> > establish a peer-to-peer connection.  It does not originate from either
> > client, and is sent to both clients simultaneously.  Both clients seem to
> > be getting the OPTIONS requests, and they are sending 200/OK in response.
> >  Is there a setting I need to change to prevent this from happening?
> >
> > James
>
>
> Could you please send a ngrep-sip capture and the proxy log grep of such a
> call? It might be a rtptimeout, a missrouted ack, session timers not being
> honoured...
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/listinfo/spce-user
>




On Mon, Nov 26, 2012 at 11:30 AM, James Hurley <james at curiousminds.com>wrote:

> Here's the log, it looks like the BYE is coming from SEMS on port 5080. (
> the users in question are 16.james and 16.james_expert )
>
> https://gist.github.com/e865aa36c663665503a1
>
>
>
> On Mon, Nov 26, 2012 at 10:54 AM, Jon Bonilla <jbonilla at sipwise.com>wrote:
>
>> El Mon, 26 Nov 2012 10:28:57 -0800
>> James Hurley <james at curiousminds.com> escribió:
>>
>> > I seem to be getting a BYE request after 60 seconds when the clients
>> > establish a peer-to-peer connection.  It does not originate from either
>> > client, and is sent to both clients simultaneously.  Both clients seem
>> to
>> > be getting the OPTIONS requests, and they are sending 200/OK in
>> response.
>> >  Is there a setting I need to change to prevent this from happening?
>> >
>> > James
>>
>>
>> Could you please send a ngrep-sip capture and the proxy log grep of such a
>> call? It might be a rtptimeout, a missrouted ack, session timers not being
>> honoured...
>>
>>
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> http://lists.sipwise.com/listinfo/spce-user
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20121126/c962600c/attachment-0001.html>