Hi there, We am also experiencing this issue when running sipp-1.1rc6. We augmented the get_peer_tag function with a warning message as to what it was given to analyse, and what it returned. The following was the contents of the input message it was passed when it had run to the point where it returned "SDf959699-".
------- SNIP --------- To: <sip:[EMAIL PROTECTED]>;tag=SDf959699- Call-ID: [EMAIL PROTECTED] CSeq: 1 REGISTER WWW-Authenticate: DIGEST realm="acme.com",algorithm=MD5,nonce="1159778898621" Content-Length: 0 ------- SNIP --------- It possibly is mixing two message buffers together in some fashion to arrive at this result. This does not happen in all cases, but perhaps one in two. We will continue investigations, but if anyone has input as to directions to look it would be greatly appreciated. Mark >I'm using the latest unstable version of sipp from sf. >(sipp.2006-07-11). When I use the [peer_tag_param] the peer tag gets >truncated. In my test case, i'm using it to send an ack to a 200 OK >message. > >the peer tag is: > > "SDgida799-171680033-1154017965636" > >using [peer_tag_param] it gets truncated to: > >"SDgida799-" > >Any pointers on this? > >Tim ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users
