Hello Duane,
The Invalid Cseq is actually a side effect of the REGISTER
retransmissions - you have 2 REGISTER (original + retransmission) with
CSeq: 756 REGISTER .
First is executed in one process, gets stored and a 200 reply ; the
retransmission gets executed in a different process, and because it has
same cseq the storing generated the error.
You need to filter out the retransmissions (use a t_newtran() before the
save(location) ) - it should solve the problem.
But the question is why does it take for OpenSIPS more than 500ms to
generate the answer (and make the sender to do retransmission) ??
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 04/26/2013 03:23 AM, Duane Larson wrote:
I originally posted this via Nabble but I am not sure if it went to
the Opensips User mailing list so please excuse me if this shows up as
multiple posts.
I am starting to see this issue a lot lately. My Snom phones will so
as not registered on their display screen and when I look in the
syslogs I see the following error
ERROR:registrar:update_contacts: invalid cseq for aor
<9*1******@all.com <http://all.com>>
I am not sure if this started happening because of updated Snom code
or because of updated OpenSIPS code. Luckily I was able to capture a
SIP trace from one of the Snom phones today.
Here is a SIP trace of REGISTERs without the issue
http://pastebin.com/RyaZQUBa
Here is a SIP trace of REGISTER showing the issue
http://pastebin.com/YC1AyTJ6<--- The last message in this paste is a
400 Bad Request
So is the Snom phone doing something wrong or might it be on the
OpenSIPS side?
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users