Hello Bogdan, Sipp is cutting/stripping the end of the Via header, which makes this particular version of sipp unusable with openser.
Regards, Ovidiu Sas On Tue, May 13, 2008 at 10:48 AM, Bogdan-Andrei Iancu <[EMAIL PROTECTED]> wrote: > Hi Ovidiu, > > I would say this is openser's VIA: > > > Via: SIP/2.0/UDP 127.0.0.1:5059;branch=z9hG4bK4783.c7afa14. > > > The via generated by openser, there is a digit at the end (branch > number)...But here is missing. > Henning, Could you post the request also (sent out by openser)? > > regards, > bogdan > > > > Ovidiu Sas wrote: > > > Hello Henning, > > > > I remember that I had some issue with sipp long time ago because > > openser is generating the branch param with the character '.' inside. > > Sipp seems to have issues handling the character '.'. > > In your scenario, check if the second Via header of the initial INVITE > > has something after the character '.'. In your 180 reply, there's > > nothing after it: > > SIP/2.0/UDP > 127.0.0.1:5061;branch=z9hG4bK-3206-1-0.<missing_something_here> > > > > > > Regards, > > Ovidiu Sas > > > > On Tue, May 13, 2008 at 9:33 AM, Henning Westerholt > > <[EMAIL PROTECTED]> wrote: > > > > > > > Hi, > > > > > > i use sipp as part of the test suite for the server. After a recent > system upgrade > > > (which upgraded also the sipp) i noticed that many tests stopped > working. > > > > > > The sipp (2.0.1-TLS-PCAP, version 20070516, built May 18 2007, > 11:25:38.) > > > uses now the 'sent-by' parameter for building VIAs. This seems to break > the > > > transaction matching (test 20.sh for example don't work anymore). > > > > > > An example message (ngrep -W byline) looks like this: > > > > > > U 127.0.0.1:5060 -> 127.0.0.1:5059 > > > SIP/2.0 180 Ringing. > > > Via: SIP/2.0/UDP 127.0.0.1:5059;branch=z9hG4bK4783.c7afa14., > SIP/2.0/UDP 127.0.0.1:5061;branch=z9hG4bK-3206-1-0. > > > From: sipp <sip:[EMAIL PROTECTED]:5061>;tag=3206SIPpTag001. > > > To: sut <sip:[EMAIL PROTECTED]:5059>;tag=3200SIPpTag011. > > > Call-ID: [EMAIL PROTECTED] > > > CSeq: 1 INVITE. > > > Contact: <sip:localhost:5060;transport=UDP>. > > > Content-Length: 0. > > > > > > > > > Is this behaviour normal, e.g. are the messages of sipp invalid? Or is > there > > > an error in the transaction matching logic of the server? > > > > > > Cheers, > > > > > > Henning > > > > > > _______________________________________________ > > > Devel mailing list > > > Devel@lists.openser.org > > > http://lists.openser.org/cgi-bin/mailman/listinfo/devel > > > > > > > > > > > > > _______________________________________________ > > Devel mailing list > > Devel@lists.openser.org > > http://lists.openser.org/cgi-bin/mailman/listinfo/devel > > > > > > > > _______________________________________________ Devel mailing list Devel@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/devel
