Call Audio Issues/Multiple SBC Errors

[David Searles]

Hi,

I'm having a very random and frustrating issue with one of my customers.

Every now and then, perhaps every 10 calls or so, we can't hear the incoming caller when the phone is answered. If we transfer the call to another extension, the call nearly always connects successfully.

I've changes physical hardware (phones), removed and re-created the extensions in question. re-created hunt groups etc. Updated firmware... everything...

I've triple checked firewall settings - the 3CX Server is hosted on AWS. Hosted in exactly the same way as another dozen instances I look after.

The fault does not occur every time. I'm starting to pull my hair out now....

Now tonight, I've noticed a number of RTP errors in the SBC logs - could they be related.

ERR | 20190926-171232.494 | 3CXTunnel | TUNL | 6180 | Bridge.cpp:712 | Has no registered RTP session for local destination 10.91.0.138:10037
ERR | 20190926-171238.510 | 3CXTunnel | TUNL | 6180 | Bridge.cpp:712 | Has no registered RTP session for local destination 10.91.0.138:10037
ERR | 20190926-171244.525 | 3CXTunnel | TUNL | 6180 | Bridge.cpp:712 | Has no registered RTP session for local destination 10.91.0.138:10037
ERR | 20190926-171250.557 | 3CXTunnel | TUNL | 6180 | Bridge.cpp:712 | Has no registered RTP session for local destination 10.91.0.138:10037
ERR | 20190926-171256.573 | 3CXTunnel | TUNL | 6180 | Bridge.cpp:712 | Has no registered RTP session for local destination 10.91.0.138:10037
ERR | 20190926-171258.370 | 3CXTunnel | TUNL | 13508 | Rtp.cpp:143 | Error reading from RTP socket 500, {RS:53108}: error 10054
ERR | 20190926-171258.385 | 3CXTunnel | TUNL | 6180 | Bridge.cpp:712 | Has no registered RTP session for local destination 10.91.0.138:10036
ERR | 20190926-171815.559 | 3CXTunnel | TUNL | 6180 | Bridge.cpp:712 | Has no registered RTP session for local destination 10.91.0.138:10036
ERR | 20190926-171815.590 | 3CXTunnel | TUNL | 6180 | Bridge.cpp:712 | Has no registered RTP session for local destination 10.91.0.138:10039
ERR | 20190926-171818.652 | 3CXTunnel | TUNL | 6180 | Bridge.cpp:712 | Has no registered RTP session for local destination 10.91.0.138:10039
ERR | 20190926-171824.669 | 3CXTunnel | TUNL | 6180 | Bridge.cpp:712 | Has no registered RTP session for local destination 10.91.0.138:10039
ERR | 20190926-171830.688 | 3CXTunnel | TUNL | 6180 | Bridge.cpp:712 | Has no registered RTP session for local destination 10.91.0.138:10039
ERR | 20190926-171836.704 | 3CXTunnel | TUNL | 6180 | Bridge.cpp:712 | Has no registered RTP session for local destination 10.91.0.138:10039
ERR | 20190926-171842.735 | 3CXTunnel | TUNL | 6180 | Bridge.cpp:712 | Has no registered RTP session for local destination 10.91.0.138:10039

I'm using Fanvil X4 Phones on Firmware 2.10.1.6836

I'm running SBC 15 - should I be upgrading to 16?

Any advice would be very much appreciated...

Thanks in advance,
David

 

[AWS2P]

As you ask for SBC , Is your PBX V15.5 or V16?

 

[David Searles]

I'm running V16 of the PBX (16.0.2.910)

 

[AWS2P]

and what is the SBC release V16.0.386?

 

[David Searles]

That's the thing, the SBC is still sitting on 15.5.7503 - could that be causing issues?

PBX is hosted on AWS (Debian) the SBC is on a local 2016 Server.

 

[AWS2P]

is your SBC linux version? if so, it should have been updated to latest automaticly a cron job runs every sunday at 3am to check and install latest stable release.

otherwise you can try manually
sudo apt update
then
sudo apt upgrade 3cxsbc

once upgrade is done you need to go in console , trunk sip item, then select SBC line and press send configuration button to remotely set it.

or do a fresh install with latest iso

 

[David Searles]

Sorry, I updated previous post

SBC is running on a windows server

 

[AWS2P]

so for windows always the same, complete reinstall in latest version

https://www.3cx.com/phone-system/download-links/

 

[David Searles]

Yep - I've just upgraded - all seems well...

Hopefully its helped with the audio issues?

Thanks for your help..

 

[David Searles]

Just a quick update - the problem still persists following the SBC upgrade and pretty much every other thing that I've tried.

I'm pulling my hair out now... I've logged an official ticket for this now, hopefully, we'll get to the bottom of it.

Here's the activity log for a problematic call from earlier today - in case I'm missing anything obvious: