RTCPinterval Affecting One-way audio

I’m getting one way audio on outbound (they can always hear me, but I cannot hear them).
If I set rtcpinterval=4922 or less the problem goes away.
If it is something larger or commented out (5000) there is no return audio.
Newest Git-master, also tried 18.7 both with pjsip.
Here are the debugs (working and not):

Sent RTP P2P packet to 74.125.39.77:26500 (via ICE) (type 00, len 000160)
Got  RTP packet from    74.125.39.77:19305 (type 00, seq 016882, ts 42366800, len 000160)
Sent RTP P2P packet to 192.168.1.21:10122 (type 00, len 000160)
Got  RTP packet from    192.168.1.235:16454 (type 00, seq 016886, ts 42367440, len 000160)
Sent RTP P2P packet to 74.125.39.90:19305 (via ICE) (type 00, len 000160)
Got  RTP packet from    192.168.1.21:10122 (type 00, seq 031525, ts 720244, len 000160)
Sent RTP P2P packet to 74.125.39.77:26500 (via ICE) (type 00, len 000160)
Got  RTP packet from    74.125.39.77:19305 (type 00, seq 016883, ts 42366960, len 000160)
Sent RTP P2P packet to 192.168.1.21:10122 (type 00, len 000160)
Got  RTP packet from    192.168.1.235:16454 (type 00, seq 016887, ts 42367600, len 000160)
Sent RTP P2P packet to 74.125.39.90:19305 (via ICE) (type 00, len 000160)
Got  RTP packet from    192.168.1.21:10122 (type 00, seq 031526, ts 720404, len 000160)
Sent RTP P2P packet to 74.125.39.77:26500 (via ICE) (type 00, len 000160)
Got  RTP packet from    74.125.39.77:19305 (type 00, seq 016884, ts 42367120, len 000160)
Sent RTP P2P packet to 192.168.1.21:10122 (type 00, len 000160)
Got  RTP packet from    192.168.1.235:16454 (type 00, seq 016888, ts 42367760, len 000160)


Sent RTP P2P packet to 74.125.39.84:26500 (via ICE) (type 00, len 000160)
Got  RTP packet from    74.125.39.84:19305 (type 00, seq 064402, ts 19629600, len 000160)
Sent RTP P2P packet to 192.168.1.235:16432 (type 00, len 000160)
Got  RTP packet from    192.168.1.140:5012 (type 00, seq 064405, ts 19630080, len 000160)
Sent RTP P2P packet to 74.125.39.7:19305 (via ICE) (type 00, len 000160)
Got  RTP packet from    74.125.39.7:19305 (type 00, seq 015290, ts 39146640, len 000160)
Sent RTP P2P packet to 192.168.1.140:5012 (type 00, len 000160)
Got  RTP packet from    192.168.1.235:16432 (type 00, seq 015293, ts 39147120, len 000160)
Sent RTP P2P packet to 74.125.39.84:26500 (via ICE) (type 00, len 000160)
Got  RTP packet from    74.125.39.84:19305 (type 00, seq 064403, ts 19629760, len 000160)
Sent RTP P2P packet to 192.168.1.235:16432 (type 00, len 000160)
Got  RTP packet from    192.168.1.140:5012 (type 00, seq 064406, ts 19630240, len 000160)
Sent RTP P2P packet to 74.125.39.7:19305 (via ICE) (type 00, len 000160)
Got  RTP packet from    74.125.39.7:19305 (type 00, seq 015291, ts 39146800, len 000160)
Sent RTP P2P packet to 192.168.1.140:5012 (type 00, len 000160)
Got  RTP packet from    192.168.1.235:16432 (type 00, seq 015294, ts 39147280, len 000160)

RTCP and RTP are two separate things. RTCP itself does not carry audio, and would not show in “rtp set debug”. There is a separate CLI command for showing RTCP traffic. You’d also need to describe the setup and environment. It’s entirely possible the remote side wants RTCP reports often.

Thanks for responding,

I realize they are two unrelated things however, that is what’s happening on my system.

I’ve tried disabling ATA’s, a different router, and a different switch all with the same results.

I setup a new server and it does the exact same thing. The new one is a much slower PC and works/fails right around the same rtcpinterval value.

Disabling/enabling AMI has a slight affect with the work/fail point. I have to use a smaller value for rtcpinterval to get the audio to work. I’m the only one on the network using AMI. The rtcpinterval affects how often the events come through.

The upper RTP listing (above) shows the missing communication to the ATA (doesn’t it?). The lower printout is the one from the working config.

In rtp.conf I’m using rtpstart=5000, rtpend=17500, a STUN server, nothing under ICE_host… I’ve tried various values for start/end (including default) with no change to the problem.

The log shows RTP traffic flowing between things. I’m not really sure what you’re expecting me to see in it in regards to working and not working. You’d need to provide more context.

The rtcpinterval affects how often RTCP packets are sent, which in turn produces AMI events.

I figured it out: ‘strictrtp=no’ (it defaults to ‘yes’)

With it set to ‘no’ the rtcpinterval can be any value (default is fine for me) and audio works both ways.

I’m thinking that with ‘strictrtp=yes’ the ‘rtp learning’ mechanism is affected by how often rtcp events are triggered?
And it wanted (needed) more events (lower rtcpinterval value) or maybe just a longer time to learn?
Maybe the learning mechanism should have a configurable duration?

For now I will probably use default (strictrtp=yes) and set the rtcpinterval to 4500. That seems more sano (safer?) FYI- ‘strictrtp=seqno’ (the other option) did not solve my problem.

I looked at the code and found a constant ‘strict_rtp_learn_timeout 5000’ and changed it to 10000, re-compiled, and it works.
So, it would be better if that wasn’t “constant”.
I could do that myself but I think the value should also show under ‘rtp show settings’ and probably other places I’m not aware of so I’ll leave the mods to the pros.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.