-
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
In the process of setting up SIPp we came across the following issues:
Setup:
./sipp -sn uac_pcap -i 10.0.0.6 -mp 6000 -trace_err 10.0.0.1
linux (uac) version 1.1rc6
Turion 2x, 512RAM, Debian Linux, 2.4.23 kernel. (runs as root user)
sipp -mi 10.0.0.1 -trace_err -rtp_echo -mp 6000 -sn uas
Peter/Olivier,
I think instead of adding a start_line attribute, that behavior should be
the default (as most people probably expect it to work that way).
Charles
Olivier Jacques [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
02/14/2007 02:15 PM
To
Peter Higginson [EMAIL PROTECTED]
cc
I have an interesting issue with multi-socket.
Using a scenario to simulate a presence endpoint. It sends a register,
subscribe and publish, and that SUBSCRIBE results in a NOTIFY for his state
information. So I have essentially:
send REGISTER
recv response=200
send PUBLISH
recv
