I'm new to SIPp, but not to the world of open source. How does one go
about becoming an authorized committer on this project? If the people
fixing the bugs can't check in fixes, something seems broken.
Todd.
________________________________
From: Jordan L. Walbesser [mailto:[email protected]]
Sent: Monday, August 03, 2009 3:24 PM
To: Bradley, Todd
Cc: [email protected]
Subject: Re: [Sipp-users] SIPp Linux is sending pcap media to
wrong port
No problem Todd!
I'm not sure who's in charge of making new builds, but there are
a number of bugs like this that are documented and fixed. I don't mind
getting my hands dirty and fixing the code, but what's frustrating is
that I don't have the authority in sourceforge to put the changes into a
release.
Anyways, best of luck!
~Jordan
--
Jordan L. Walbesser
Computer Engineering B.S. '07
Juris Doctor '10
Mobile: (716) 640-0532
Web: www.buffalo.edu/~jlw28
On Mon, Aug 3, 2009 at 11:12 AM, Bradley, Todd
<[email protected]> wrote:
For what it's worth, I downloaded the latest unstable
source snapshot. After building the pcap-enabled binary, I ran my same
scenario. It looked like SIPp sent the audio RTP to the correct port
for a brief moment, but then SIPp segfaulted before I saw any video RTP.
I don't really feel like debugging segmentation faults,
so I applied Jordan's patch to the stable version and rebuilt. Now my
audio and video are being sent to the correct ports and the test is
working.
For what it's worth, Jordan's change appears to NOT be
in the latest unstable source code. So maybe somebody fixed part of the
problem some other way. But it's hard to say if it's completely fixed
since SIPp crashes before completing even the first call.
Thanks Jordan!
Cheers,
Todd.
________________________________
From: Bradley, Todd
[mailto:[email protected]]
Sent: Monday, August 03, 2009 8:26 AM
To: Srivastava, Anuj Kumar (CMS);
[email protected]
Subject: Re: [Sipp-users] SIPp Linux is sending
pcap media to wrong port
On Windows, I'm using this:
SIPp v3.1-PCAP, version svn456, built May 30
2008, 09:41:13.
On Linux, I'm using this:
SIPp v3.1-PCAP, version unknown, built Jul 31
2009, 17:29:33.
In both cases, it's the latest SIPp "stable"
version available on http://sipp.sourceforge.net. Is it a bad idea to
use that version?
________________________________
From: Srivastava, Anuj Kumar (CMS)
[mailto:[email protected]]
Sent: Sunday, August 02, 2009 10:02 PM
To: [email protected]
Subject: Re: [Sipp-users] SIPp Linux is
sending pcap media to wrong port
Hello,
Which sipp version you are using for
windows for which it works ?
Are you trying with the latest linux src
present in the snapshots ?
Regards
Anuj
________________________________
From: Jordan L. Walbesser
[mailto:[email protected]]
Sent: Saturday, August 01, 2009 5:12 AM
To: [email protected]
Subject: Re: [Sipp-users] SIPp Linux is
sending pcap media to wrong port
On Fri, Jul 31, 2009 at 7:41 PM, Jordan
L. Walbesser <[email protected]> wrote:
This is definitely a known bug. There's
a patch for it, I know I submitted one a while back, but I doubt it got
included into a build. Someone else wrote this up too.
See the following:
http://osdir.com/ml/telephony.sipp.user/2008-07/msg00148.html
Let me know if you need some more
guidance.
~Jordan
--
Jordan L. Walbesser
Computer Engineering B.S. '07
Juris Doctor '10
Mobile: (716) 640-0532
Web: www.buffalo.edu/~jlw28
<http://www.buffalo.edu/%7Ejlw28>
On Fri, Jul 31, 2009 at 7:20 PM,
Bradley, Todd <[email protected]> wrote:
I'm running SIPp on both Windows (using
pre-built binaries) and Linux
(64 bit CentOS system, built from
source). I have a scenario where I'm
sending audio and video media from my
SIPp scenario to a video
conferencing system.
The scenario works fine under Windows,
but I was wondering why the audio
and video aren't played when I run the
scenario under Linux. Using
Wireshark, I found that SIPp is not
sending the audio and video RTP
packets to the port numbers specified in
the SDP. Instead, it appears
to be truncating those numbers.
In the 200 OK message from the UAC, the
SDP says to use port 49160 for
audio media and port 49170 for video
media. However, the actual RTP
packets are being sent to ports 4916 and
4917, according to Wireshark.
Has anyone seen this, and do you have a
workaround or patch for it?
Thanks,
Todd.
----
Todd Bradley - Polycom, Inc.
DMA 7000 QA Lead
------------------------------------------------------------------------
------
Let Crystal Reports handle the reporting
- Free Crystal Reports 2008 30-Day
trial. Simplify your report design,
integration and deployment - and focus on
what you do best, core application
coding. Discover what's new with
Crystal Reports now.
http://p.sf.net/sfu/bobj-july
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
------------------------------------------------------------------------
------
Let Crystal Reports handle the reporting - Free Crystal
Reports 2008 30-Day
trial. Simplify your report design, integration and
deployment - and focus on
what you do best, core application coding. Discover
what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
