search

SIPp / sipp

The SIPp testing tool
https://sipp.readthedocs.io
Other
921 stars 383 forks source link

SIPp + PCAPplay Message & Media Ports Incorrect #108

Closed nlemberger closed 10 years ago

nlemberger commented 10 years ago

If I add a pcap play line to the default UAC scenario (or use the built-in pcap_play scenario) odd things happen.

The new messages which SIPp sends, after the initial INVITE/OK/ACK (100, 183) get seemingly random source and destination ports. This doesn't appear happen, at least with the 100 in a standard UAC scenario.

Additionally, the pcap play media is sent to a seemingly random port, not the one specified in the SDP of the OK message received after the INVITE.

Perhaps I'm using the tool incorrectly, but my research into the documentation hasn't suggested a reason for this behavior.

wdoekes commented 10 years ago

I'm not seeing that behaviour. If I do a sudo sipp -sn uas -p 5060 -m 1 and a sudo sipp -sn uac_pcap 127.0.0.1 -m 1 things appear perfectly fine. (SIP messages between 5060 en 5061 and RTP between 6000 and 6001.)

Are you using the most recent version? Could you paste a snippet of tcpdump showing the problem?

nlemberger commented 10 years ago

Thanks for letting me know it's working for you! I was somewhat lost with the weird behaviour I was seeing, but knowing it was working for you gave me a few insights. After I set the DUT up for g711a, I too was able to get the included g711a scenario working.

This lead me to comparing the g711a.pcap RTP file with the ones I created for g711u & SILK. I had left RTP, SIP, and some ICMP messaging in those files and that was my issue. Once I pulled everything from the RTP media pcap's but the RTP packets themselves, things started to work!