Hi,
I have a similar problem with media as submitted from Maksym Hryhoryev
2007-09-21 (see below). Only difference is, that I'm using 2 different physical
ethernet-interfaces on the same Suse Linux machine and trying to exchange media
between the SIPp scenarios on them via real IMS Core. SIP Signaling is fine,
but the SIPp instance of the 2nd interface uses IP-address of 1st interface as
Source-IP-Address for sending its media with exec play_pcap_audio="g711a.pcap".
Using -mi parameter as sipp command option doesn't change anything.
Thanks and regards
Armin von Helden
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Maksym Hryhoryev
Envoyé : vendredi 21 septembre 2007 11:26
À : [email protected]
Objet : [Sipp-users] media IP
I run latest version of sipp on redhat linux4U4.
The machine on which sipp is running has 3 ip aliases (172.70.60.40 - eth0,
172.70.60.41 - alias 1, 172.70.60.42 - alias 2, 172.70.60.43 - alias 3).
I made call from sipp alias1 to sipp alias2 (using different SIP and Media
ports) and its ok with SIP flow, but with RTP flow there is a problem - sipp
sends RTP from 172.70.60.40 with ignoring -mi and -i command line options.
I think it's a bug.
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
