Hello,

I think (but I need to do more testing) the one way audio was related to early media and some issues with the media gateway I am using (which was generating the early media). Removing the body from 18[03] responses (and converting 183 responses to 180) seems to have made the problem much better.

However, I am still getting lots of "Error generating SRTP session keys" and occasional "Error generating SRTCP session keys" errors for every call.

Here is the log output:

Aug 22 14:30:48 ip-10-195-37-98 mediaproxy-ng[20647]: Got valid command from 10.83.134.203:57131: offer - { "sdp": "v=0#015#012o=- 4318888073915075904 2 IN IP4 127.0.0.1#015#012s=-#015#012t=0 0#015#012a=group:BUNDLE audio#015#012a=msid-semantic: WMS fKdeRobDJOkk81duAyqbXY0x2chKpp2B3ocS#015#012m=audio 45232 RTP/SAVPF 111 103 104 0 8 107 106 105 13 126#015#012c=IN IP4 90.152.0.102#015#012a=rtcp:45232 IN IP4 90.152.0.102#015#012a=candidate:1112343425 1 udp 2113937151 192.168.0.174 45232 typ host generation 0#015#012a=candidate:1112343425 2 udp 2113937151 192.168.0.174 45232 typ host generation 0#015#012a=candidate:4062413514 1 udp 2113937151 192.168.122.1 49350 typ host generation 0#015#012a=candidate:4062413514 2 udp 2113937151 192.168.122.1 49350 typ host generation 0#015#012a=candidate:2914046532 1 udp 2113937151 10.6.201.173 45123 typ host generation 0#015#012a=candidate:2914046532 2 udp 2113937151 10.6.201.173 45123 typ host generation 0#015#012a=candidate:3271886133 1 udp 1845501695 90.152.0.102 45232 typ srflx raddr 192.168.0.174 rport 45232 generation 0#015#012a=candidate:3271886133 2 udp 1845501695 90.152.0.102 45232 typ srflx raddr 192.168.0.174 rport 45232 generation 0#015#012a=candidate:1936426110 1 udp 1845501695 90.152.0.102 49350 typ srflx raddr 192.168.122.1 rport 49350 generation 0#015#012a=candidate:1936426110 2 udp 1845501695 90.152.0.102 49350 typ srflx raddr 192.168.122.1 rport 49350 generation 0#015#012a=candidate:214892401 1 tcp 1509957375 192.168.0.174 0 typ host generation 0#015#012a=candidate:214892401 2 tcp 1509957375 192.168.0.174 0 typ host generation 0#015#012a=candidate:3164634682 1 tcp 1509957375 192.168.122.1 0 typ host generation 0#015#012a=candidate:3164634682 2 tcp 1509957375 192.168.122.1 0 typ host generation 0#015#012a=candidate:3811782324 1 tcp 1509957375 10.6.201.173 0 typ host generation 0#015#012a=candidate:3811782324 2 tcp 1509957375 10.6.201.173 0 typ host generation 0#015#012a=ice-ufrag:xpSCoUbISapFMmqw#015#012a=ice-pwd:J5duEhNSX3aw4pD4ZG9ETGyZ#015#012a=ice-options:google-ice#015

Aug 22 14:30:48 ip-10-195-37-98 mediaproxy-ng[20647]: [67g1bqe53kmhd19q3kp4] Creating new call

Aug 22 14:30:48 ip-10-195-37-98 mediaproxy-ng[20647]: Returning to SIP proxy: d3:sdp818:v=0#015#012o=- 4318888073915075904 2 IN IP4 50.19.41.38#015#012s=-#015#012t=0 0#015#012a=group:BUNDLE audio#015#012a=msid-semantic: WMS fKdeRobDJOkk81duAyqbXY0x2chKpp2B3ocS#015#012m=audio 30048 RTP/AVP 111 103 104 0 8 107 106 105 13 126#015#012c=IN IP4 50.19.41.38#015#012a=sendrecv#015#012a=mid:audio#015#012a=rtpmap:111 opus/48000/2#015#012a=fmtp:111 minptime=10#015#012a=rtpmap:103 ISAC/16000#015#012a=rtpmap:104 ISAC/32000#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:107 CN/48000#015#012a=rtpmap:106 CN/32000#015#012a=rtpmap:105 CN/16000#015#012a=rtpmap:13 CN/8000#015#012a=rtpmap:126 telephone-event/8000#015#012a=maxptime:60#015#012a=ssrc:3322108693 cname:hqxdn3/wdEOgrtvd#015#012a=ssrc:3322108693 msid:fKdeRobDJOkk81duAyqbXY0x2chKpp2B3ocS fKdeRobDJOkk81duAyqbXY0x2chKpp2B3ocSa0#015#012a=ssrc:3322108693 mslabel:fKdeRobDJOkk81duAyqbXY0x2chKpp2B3ocS#015#012a=ssrc:3322108693 label:fKdeRobDJOkk81duAyqbXY0x2chKpp2B3ocSa0#015#012a=rtcp:30049#015#0126:result2:oke

Aug 22 14:30:49 ip-10-195-37-98 mediaproxy-ng[20647]: Error generating SRTP session keys

Aug 22 14:30:50 ip-10-195-37-98 mediaproxy-ng[20647]: Error generating SRTP session keys

Aug 22 14:30:51 ip-10-195-37-98 mediaproxy-ng[20647]: Error generating SRTP session keys

Aug 22 14:30:51 ip-10-195-37-98 mediaproxy-ng[20647]: Error generating SRTCP session keys

Aug 22 14:30:51 ip-10-195-37-98 mediaproxy-ng[20647]: Error generating SRTP session keys

Aug 22 14:30:52 ip-10-195-37-98 mediaproxy-ng[20647]: Error generating SRTP session keys

Aug 22 14:30:53 ip-10-195-37-98 mediaproxy-ng[20647]: Error generating SRTP session keys

Aug 22 14:30:53 ip-10-195-37-98 rsyslogd-2177: imuxsock begins to drop messages from pid 20647 due to rate-limiting

Aug 22 14:30:54 ip-10-195-37-98 rsyslogd-2177: imuxsock lost 16 messages from pid 20647 due to rate-limiting

Aug 22 14:30:54 ip-10-195-37-98 mediaproxy-ng[20647]: Error generating SRTP session keys

Aug 22 14:30:54 ip-10-195-37-98 mediaproxy-ng[20647]: Error generating SRTCP session keys

Aug 22 14:30:54 ip-10-195-37-98 mediaproxy-ng[20647]: Error generating SRTP session keys

Aug 22 14:30:55 ip-10-195-37-98 mediaproxy-ng[20647]: Error generating SRTP session keys

Aug 22 14:30:56 ip-10-195-37-98 mediaproxy-ng[20647]: Error generating SRTP session keys

Aug 22 14:30:57 ip-10-195-37-98 mediaproxy-ng[20647]: Error generating SRTP session keys

Aug 22 14:30:57 ip-10-195-37-98 rsyslogd-2177: imuxsock begins to drop messages from pid 20647 due to rate-limiting

Aug 22 14:31:00 ip-10-195-37-98 rsyslogd-2177: imuxsock lost 70 messages from pid 20647 due to rate-limiting

Aug 22 14:31:00 ip-10-195-37-98 mediaproxy-ng[20647]: Successful STUN binding request on port 30050 from 90.152.0.102:49350

Aug 22 14:31:00 ip-10-195-37-98 mediaproxy-ng[20647]: Successful STUN binding request on port 30050 from 90.152.0.102:45123

Aug 22 14:31:01 ip-10-195-37-98 mediaproxy-ng[20647]: Successful STUN binding request on port 30050 from 90.152.0.102:49350

Aug 22 14:31:01 ip-10-195-37-98 mediaproxy-ng[20647]: Successful STUN binding request on port 30050 from 90.152.0.102:45232

Aug 22 14:31:02 ip-10-195-37-98 mediaproxy-ng[20647]: Successful STUN binding request on port 30050 from 90.152.0.102:49350

Aug 22 14:31:02 ip-10-195-37-98 mediaproxy-ng[20647]: Successful STUN binding request on port 30050 from 90.152.0.102:45123

Aug 22 14:31:03 ip-10-195-37-98 mediaproxy-ng[20647]: Successful STUN binding request on port 30050 from 90.152.0.102:49350

Aug 22 14:31:03 ip-10-195-37-98 mediaproxy-ng[20647]: Successful STUN binding request on port 30050 from 90.152.0.102:45232

Aug 22 14:31:04 ip-10-195-37-98 mediaproxy-ng[20647]: Successful STUN binding request on port 30050 from 90.152.0.102:49350

Aug 22 14:31:04 ip-10-195-37-98 mediaproxy-ng[20647]: Successful STUN binding request on port 30050 from 90.152.0.102:45123

Aug 22 14:31:05 ip-10-195-37-98 mediaproxy-ng[20647]: Successful STUN binding request on port 30050 from 90.152.0.102:49350

Aug 22 14:31:05 ip-10-195-37-98 mediaproxy-ng[20647]: Successful STUN binding request on port 30050 from 90.152.0.102:45232

Aug 22 14:31:06 ip-10-195-37-98 mediaproxy-ng[20647]: Successful STUN binding request on port 30050 from 90.152.0.102:49350

Aug 22 14:31:06 ip-10-195-37-98 mediaproxy-ng[20647]: Successful STUN binding request on port 30050 from 90.152.0.102:45123

Aug 22 14:31:07 ip-10-195-37-98 mediaproxy-ng[20647]: Successful STUN binding request on port 30050 from 90.152.0.102:49350

Aug 22 14:31:07 ip-10-195-37-98 mediaproxy-ng[20647]: Successful STUN binding request on port 30050 from 90.152.0.102:45232

Aug 22 14:31:08 ip-10-195-37-98 mediaproxy-ng[20647]: Successful STUN binding request on port 30050 from 90.152.0.102:49350

Aug 22 14:31:08 ip-10-195-37-98 mediaproxy-ng[20647]: Successful STUN binding request on port 30050 from 90.152.0.102:45123

Regards,

Peter