[Devel] [ openser-Bugs-1493632 ] ERROR:registry:update_contacts: invalid cseq for aor

[SourceForge.net]

Bugs item #1493632, was opened at 2006-05-23 14:37
Message generated for change (Comment added) made by goestelecom
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1493632&group_id=139143

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
Group: ver devel
Status: Open
Resolution: None
Priority: 5
Submitted By: Norman Brandinger (goestelecom)
Assigned to: Bogdan (bogdan_iancu)
Summary: ERROR:registry:update_contacts: invalid cseq for aor

Initial Comment:
This problem has been reproduced on both Polycom and
Sipura phones.

To reproduce this problem:

1. Stop OpenSER,
2. Empty the "location table",
3. Reboot the IP Phone (or if the phone is online, it
may automatically register itself).
4. The registration should proceed normally.
5. Reboot the IP Phone.
6. Error message is generated and the registration fails.

Our db_mode setting is:

modparam("usrloc", "db_mode", 1)

Our systems are available for testing if needed.

Regards,
Norm


----------------------------------------------------------------------

>Comment By: Norman Brandinger (goestelecom)
Date: 2006-05-23 16:49

Message:
Logged In: YES 
user_id=1372252

The location table has a cseq value of 2.

I rebooted the phone and observed the following:

phone -> OpenSER                       CSeq: 1 REGISTER.
OpenSER -> phone     100 Trying.       CSeq: 1 REGISTER.
OpenSER -> phone     401 Unauthorized. CSeq: 1 REGISTER.
phone -> OpenSER                       CSeq: 2 REGISTER.
OpenSER -> phone     100 Trying.       CSeq: 2 REGISTER.
OpenSER -> phone     400 Bad Request.  CSeq: 2 REGISTER.
P-Registrar-Error: Invalid CSeq number.

By rebooting the phone, it seems resonable that it dosen't
know the last cseq number that it used and thus it starts
again at 1.

After a review of 3261 (section 10.3 subsection 6) it
appears that a Call-ID check should be performed before Cseq
checking.  If the Call-ID's don't match, the binding MUST be
removed.

I reviewed the trace and the Call-ID does not match the
value in the location table.

Is there something else that I should be looking at ?

Regards,
Norm

----------------------------------------------------------------------

Comment By: Bogdan (bogdan_iancu)
Date: 2006-05-23 15:24

Message:
Logged In: YES 
user_id=1275325

I suspect it's a bug on the phone side. TO be more specific,
I suspect that the phones uses same callid and cseq for
registration after rebooting - according the RFC this the
phones must use a higher caseq during re-registration with
same callid.
Please chek this via network traces -  if the register
before and after the last phoen reboot has the same callid
and cseq number.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1493632&group_id=139143