Not able to run a test with -mp option and auto_media_port in the scenario

[Palezvar]

We have been playing with sipp for a while now. When we first started practicing with the scenarios, the version was SIPp v3.7-dev-20-gef87c87-TLS-SCTP-PCAP-RTPSTREAM-RTPCHECK. We saved our working scenarios. Today we just built a fresh copy of sipp (SIPp v3.7.0_rc1-13-gf44d0cf-TLS-SCTP-PCAP). The master was pointing to a different version. We tried to run the same tests and one of them did not work.

We have two separate VMs that host the sipp applications in the same subnet: VM1) IP: 10.10.10.148 (uac) VM2) IP: 10.10.10.149 (uas)
Both are Ubuntu 20.04 LTS.

Following is our test case:
VM1) sipp -p 5060 -sf uac_pcap.xml -l 10 -m 30 -r 5 -i 10.10.10.148 -mp 10000 -trace_stat -stf report.csv -fd 10 10.10.10.149:5060
VM2) sipp -sn uas -i 10.10.10.149 -mi 10.10.10.149

This scenario works on SIPp v3.7-dev-20-gef87c87-TLS-SCTP-PCAP-RTPSTREAM-RTPCHECK. However, with SIPp v3.7.0_rc1-13-gf44d0cf-TLS-SCTP-PCAP, on uac side, as soon as I enter the same command on VM1, it outputs the --help menu as if I entered an invalid command combination.

Has anyone seen this issue?

Here is my scenario:
uac_pcap.zip

Thanks

[DomMartin27]

On master -mp has been replaced with -min_rtp_port and -max_rtp_port

[auto_media_port] was also removed. There is some information here: https://sipp.readthedocs.io/en/latest/scenarios/keywords.html#media-port

Running sipp -h will give you an up to date list of available command line arguments.

[Palezvar]

Thank you for the clarification @DomMartin27

I will test this out today and get back ASAP

[Palezvar]

I was able to run my scenario using the following:
sipp -p 5060 -sf uac_pcap_without_auto_media.xml -l 10 -m 30 -r 5 -i 10.10.10.148 -min_rtp_port 10000 -max_rtp_port 20000 -trace_stat 10 10.10.10.149:5060

I removed "auto_media_port" from the xml.

I am confused about one thing. I was expecting the RTP ports in my packet capture to be different on the UAC side for each generated call but they are all the same, 10000 UDP as source port for RTP packets leaving UAC. What am I missing?

Do I need to change the following section in my xml scenario file?:

m=audio [media_port] RTP/AVP 8

[Palezvar]

I am not sure if this is supposed to be addressed on another ticket but the terminal output on the UAC while running the test is as follows:

The tests are not failing but the terminal output is too messy. I does not happen with the other basic tests so I am not if it is related to my particular scenario and the command options. This does not happen with the 3.7dev branch.

[DomMartin27]

Can you send both the uac and uas script, combined with the command used please

[Palezvar]

Sure, on the UAS side I used the following:
sipp -sn uas -i 10.10.10.149 -mi 10.10.10.149

Both virtual machines are located in the same subnet.

[DomMartin27]

The UAC xml file, is it the same as the one you originally attached? did you change [auto_media_port] -> [media_port]?

[Palezvar]

@DomMartin27 UAC XML is still the same, except [auto_media_port] is now [media_port]. Like you mentioned.

On UAC I execute the following:
sipp -p 5060 -sf uac_pcap_without_auto_media.xml -l 10 -m 30 -r 5 -i 10.10.10.148 -min_rtp_port 10000 -max_rtp_port 20000 -trace_stat 10 10.10.10.149:5060

SIPp version on both sides is: v3.7.0_rc1-13-gf44d0cf-TLS-SCTP-PCAP

[mshafeeqkn]

I am also facing the same issue in the SIPp screen as the screenshot shown above. The issue happend for me when I executed the performance test with more than 100 calls

checked on SIPp v3.7.0_rc1-13-gf44d0cf-TLS-SCTP-PCAP.

[SHUstri]

Has same issue:
sipp v3.7 with [media_port] in initial INVITE scenario and -min_rtp_port 6000 -max_rtp_port 18000 in sipp start script
scenario has a pcap_play step
all calls have same 6000 in SIP INVITE from SIPP (and same RTP SSRC from pcap file) what caused media mesh on other side

did rebuild sipp to v3.4 and change [media_port] to [auto_media_port] > all calls from sipp have different media ports 6000, 60001, 6002. etc

[thorsager]

I'm having the same issue, with all calls using same media_port on SIPp v3.7.0-1-ge86bf93-TLS-SCTP-PCAP.

[callnpaul]

Same here. [media_port] doesn't increment when using -min_rtp_port 5000 -max_rtp_port 6000 so all outgoing SDP's all have the same port 5000.
I suspect this is then causing the "Unable to bind UDP socket, errno = 98 (Address already in use)" error.

[ruijiexie]

@Palezvar rebuild sipp3.7.1 call.cpp

        case E_Message_Media_Port: {
            int port = media_port + (4 * (number - 1)) % 10000 + comp->offset;

[abitrusty]

I'm using 3.7.2 and am having the same issue where the UAS is not incrementing the RTP source port thus only the 1st call is setting up with 2 way RTP stream

[agentgoblin]

Try release 3.7.3 because changelog says:

Recover -mp and [auto_media_port] by @orgads in #653

-mp works for me on 3.7.3