Hi I tried with the unstable branch Nov 24th release and the problem persists..So I believe that it has nothing to do with the sipp versions but with playing the pcap file. Also I tried with RTP and the scenarios work well.. The problem occurs when I attempt <nop> pcap </nop> in the xml scenarios.
Thanks in advance Regards Knight On 12/6/06, Knight Tiger <[EMAIL PROTECTED]> wrote: > Yes, these are the commands that were issued..and I found that they > were not working.. Also trace_err is not frightully helpful. All it > contains is > > sendto failed with error: Invalid argument and trace_msg does not > contain any of the RTP messages sent just the SIP messages. I tried > different PCAP messages like various DTMF tones (creating my own XML > scenarios ) and it does not help. Is this a known bug ? and should I > use the latest version from the unstable branch ? I will try with that > and report my findings.. > > Thanks again for your timely response. > Regards > Knight > > > On 12/6/06, Olivier Jacques <[EMAIL PROTECTED]> wrote: > > Hmmm... > > IP: 192.168.1.100 > > root$ ./sipp -trace_err -mp 5500 -mi 192.138.1.100 -sn uas > > > > -> you meant > > IP: 192.168.1.100 > > root$ ./sipp -trace_err -mp 5500 -mi 192.168.1.100 -sn uas > > > > > > ? > > > > > > On 12/6/06, Knight Tiger <[EMAIL PROTECTED]> wrote: > > > Hi > > > I apologize for the error.. I was meaning to write it like the way you > > > wrote it but in my hurry I reversed them.. I had tested with -mi <ip> and > > > -mp <<port> only and it refused to work. I repeat the exact set of > > > commands issued > > > > > > IP: 192.168.1.100 > > > root$ ./sipp -trace_err -mp 5500 -mi 192.138.1.100 -sn uas > > > > > > on another machine > > > IP: 192.168.1.102 > > > root$./sipp -trace_err -mp 6000 -mi 192.168.1.102 -sn uac_pcap > > > 192.168.1.100 > > > > > > Could anyone provide me with a lead on this ? Thanks in advance > > > > > > > > > Thanks > > > Knight > > > > > > > > > > > > > > > On 12/6/06, Olivier Jacques < [EMAIL PROTECTED]> wrote: > > > > Hi, > > > > > > > > you reversed "-mi" and "-mp": mi is for IP address, mp is for media > > > > port: > > > > > > > > Change from: -mi 5500 -mp 192.138.1.100 > > > > to: -mi 192.138.1.100 -mp 5500 > > > > > > > > Olivier. > > > > > > > > > > > > > > > > On 12/6/06, Knight Tiger < [EMAIL PROTECTED]> wrote: > > > > > > > > > > Hi > > > > > I am using sipp stable version 1.1rc6 and installed > > > > > pcapplay (make pcapplay). When I try to send RTP packets (uac_pcap > > > > > embedded scenario) I get this error message: > > > > > > > > > > sendto failed with error: Invalid argument. > > > > > > > > > > The problem is that sipp tries to establish the call and there are > > > > > SIP messages exchanged back and forth between the two endpoints (both > > > > > are Linux machines on the same network) till the <nop> tag in the xml > > > > > file.. No further messages are exchanged and RTP packets are not sent > > > > > either and the error log file contains this message and no futher > > > > > messages. > > > > > > > > > > Could I have made some wrong settings ? > > > > > > > > > > IP: 192.168.1.100 > > > > > root$ ./sipp -trace_err -mi 5500 -mp 192.138.1.100 -sn uas > > > > > > > > > > > > > > > on another machine > > > > > IP: 192.168.1.102 > > > > > root$./sipp -trace_err -mi 6000 -mp 192.168.1.102 -sn uac_pcap > > > > > 192.168.1.100 > > > > > > > > > > This works on the local interface but does not work over the ethernet > > > > > connection and both machines have no firewall running. > > > > > > > > > > Thanks in advance > > > > > > > > > > Regards > > > > > Knight > > > > > > > > > > > > > > > ------------------------------------------------------------------------- > > > > > 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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > HP OpenCall Software > > > > http://www.hp.com/go/opencall/ > > > > > > > > > ------------------------------------------------------------------------- > > > 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 > > > > > > > > > > > > > > > > > -- > > HP OpenCall Software > > http://www.hp.com/go/opencall/ > ------------------------------------------------------------------------- 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
