[Devel] uac-Module CSeq

[Thorsten Müller]

Hi Klaus and list

thanks for the response.
AFAIK (open)ser is dialog stateless but transaction
statefull.
The second INVITE begins a second transaction with an
--to follow RFC 3261-- increased cseq. Where is the
information in (open)ser for the following
transaction. Is there a place in (open)ser where the
cseg is stored for a dialog? How is the management of
cseg done in (open)ser.

Regards 

Thorsten

mt> -----Ursprüngliche Nachricht-----
mt> Von: Klaus Darilion
[mailto:klaus.mailinglists at pernau.at]
mt> Gesendet: Mittwoch, 8. März 2006 19:50
mt> An: Thomas Müller
mt> Cc: devel at openser.org
mt> Betreff: Re: [Devel] uac-Module CSeq
mt> 
mt> 
mt> On Wed, March 8, 2006 17:25, Thomas Müller said:
mt> > Hi list,
mt> >
mt> > I tried to authenticate openser at Asterisk and
run
mt> > into the cseq-error. (Asterisk is hard
RFC-konform and
mt> > ignores the second INVITE with the same cseq;
mt> > uac-module is not increasing it - as mentioned
in the
mt> > docu).
mt> >
mt> > Where is the problem increasing the cseq - I
think it
mt> > is not to add 1 to an integer-value (even if
stored as
mt> > struct str_) but there should be s.th. more.
mt> > Where is the trap to fall in? To give the
following
mt> > transactions the right increased cseq?
mt> 
mt> Yes. (open)ser is stateless. Openser would have to
increase 
mt> the cseq also
mt> in all further transaction, for which openser
would have to 
mt> be dialog
mt> staeful.
mt> 
mt> a workaround:
mt> decrease the Cseq for the first INVITE. This works
only for 
mt> the first
mt> INVITE and will break if in-dialog requests are
challenged.
mt> 
mt> regards
mt> klaus
mt> 
mt> 


	

	
		
___________________________________________________________ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de