reSIProcate

Mailing Lists

Source Code

Google Search:



< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate] CSeq jumps

Hi Diego,

I can see that there may indeed be a problem with resiprocate CSeq assignments of INFO messaging.  INFO messages are put in a queue of non-Invite transactions (NITs) to be sent out.  Once the INVITE session returns to a Connected state the next NIT is sent.  re-INVITEs could be generated while there are a queue of NITs waiting to be sent.  The problem is that we generate the CSeq number for the INFO messages when they are inserted into the queue and not when they are transmitted.

I suspect we have never noticed this problem in the past, but your application seems to be generating a lot of INFO messages and triggering the issue.

I'm not sure when I will have a chance to address this - if anyone else has cycles to work on it, then let me know and I can try and provide a few pointers.

Best Regards,
Scott

On Fri, Mar 20, 2015 at 12:30 PM, Diego Carvalho Domingos <ddomingos@xxxxxxxxxxxxxxx> wrote:

That’s true. The endpoint should handle that situation. But in resiprocate side: Do you think there might be a bug that is making resiprocate not send contiguous CSeq numbers? Thanks.


_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel