-
Notifications
You must be signed in to change notification settings - Fork 392
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong source port used by sipp to send media when using rtp_stream #192
Comments
Thank you for taking the time to report. We'll look into it. |
One important note I forgot to mention is that with play_pcap_audio it works fine, which is why my .xml above is a bit misleading as I copy/pasted after we found this workaround Please let me know if you need more info Best regards, |
…port. This would fix issue #192, but is probably not the way forward.
@atsakiridis: Your best bet is probably to use [rtpstream_audio_port] in place of [media_port] in your SDP. That should work. |
Thanks a lot @wdoekes, I'll check it out |
Hello, using SIPp 3.5.2, I still see the same issue. thoutht this problem is solved with latest 3.5.2 ? |
Hi i have problem of rtcp port |
- rtpstream_get_localport() must default to media port 6000 when none is specified by user - UAC side of RTPSTREAM must specify mandatory payload_name parameter
Even though SDP negotiation is successful and sipp declares port 6000 for media in the SDP offer, for some reason when sending RTP packets it doesn't use as source port 6000, while it does receive them in that port when in the receiving end. That causes a problem to the other end that expects media to be transferred using the port negotiated in SDP.
Using https://github.com/SIPp/sipp/releases/tag/v3.5.0 on OSX 10.11.2
Sorry, forgot to add some more data:
sipp -sf ./health-ivr-sipp-client.xml -s +5555 127.0.0.1:5080 -mi 127.0.0.1:5090 -l 1 -m 1 -r 1 -trace_screen -trace_err -recv_timeout 5000 -nr -t u1
The text was updated successfully, but these errors were encountered: