[sip-comm-dev] Issues with nonce on unregistration / cseq increment


#1

Hi Guys,

first of all would like to thank all for the wonderful piece of software you
did for the community, I really enjoy it.

Recently, while monitoring one of my openser installations, I have noticed
few things wrong in the signaling coming from your SC UA:

1. On Un-Register from SC (it does not happen 100% of cases but in an
aleatory manner), SC would send a proper un-REGISTER packet, but my server
(OpenSER) will complain about the a stale nonce (I have in my server a
lifetime of 300 secs for a nonce). OpenSER would reply back that the nonce
is stale, but no further answer from SC, so the client would look like still
being registered into OpenSER.

2. Again, in same aleatory cases, OpenSER would reject REGISTER packets as
having wrong cseq number.

Are those issues known to you, or just hit some bugs?

Cheers,
DanB


#2

Hey Dan,

Very nice catch!

We've had a discussion on these issues through the afternoon and we've
come up with a solution.

(for the sake of clearness it would probably be worth mentioning that
Dan first reported this in an offline and is sending the mail upon our
request)

I've just seen that Damian has committed a set of modifications that
should be fixing these issues.

Thanks for tracking this down Dan!

Emil

Dan-Cristian Bogos написа:

···

Hi Guys,

first of all would like to thank all for the wonderful piece of software
you did for the community, I really enjoy it.

Recently, while monitoring one of my openser installations, I have
noticed few things wrong in the signaling coming from your SC UA:

1. On Un-Register from SC (it does not happen 100% of cases but in an
aleatory manner), SC would send a proper un-REGISTER packet, but my
server (OpenSER) will complain about the a stale nonce (I have in my
server a lifetime of 300 secs for a nonce). OpenSER would reply back
that the nonce is stale, but no further answer from SC, so the client
would look like still being registered into OpenSER.

2. Again, in same aleatory cases, OpenSER would reject REGISTER packets
as having wrong cseq number.

Are those issues known to you, or just hit some bugs?

Cheers,
DanB

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#3

Emil,

happy to do it.

Cheers,
DanB

···

On Wed, Mar 26, 2008 at 6:20 PM, Emil Ivov <emcho@sip-communicator.org> wrote:

Hey Dan,

Very nice catch!

We've had a discussion on these issues through the afternoon and we've
come up with a solution.

(for the sake of clearness it would probably be worth mentioning that
Dan first reported this in an offline and is sending the mail upon our
request)

I've just seen that Damian has committed a set of modifications that
should be fixing these issues.

Thanks for tracking this down Dan!

Emil

Dan-Cristian Bogos написа:
> Hi Guys,
>
> first of all would like to thank all for the wonderful piece of software
> you did for the community, I really enjoy it.
>
> Recently, while monitoring one of my openser installations, I have
> noticed few things wrong in the signaling coming from your SC UA:
>
> 1. On Un-Register from SC (it does not happen 100% of cases but in an
> aleatory manner), SC would send a proper un-REGISTER packet, but my
> server (OpenSER) will complain about the a stale nonce (I have in my
> server a lifetime of 300 secs for a nonce). OpenSER would reply back
> that the nonce is stale, but no further answer from SC, so the client
> would look like still being registered into OpenSER.
>
> 2. Again, in same aleatory cases, OpenSER would reject REGISTER packets
> as having wrong cseq number.
>
> Are those issues known to you, or just hit some bugs?
>
> Cheers,
> DanB

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net