Session Border Controller

[benratty]

Not sure if this is related to any other issues I have had but the SBC we have in a remote office although it is working the log does still show as follow

ERR | 20160617-143637.871 | 3CXTunnel | TUNL | 1028 | Rtp.cpp:143 | Error reading from RTP socket 456, {RS:49674}: error 10054
ERR | 20160617-143637.871 | 3CXTunnel | TUNL | 1028 | Rtp.cpp:143 | Error reading from RTP socket 456, {RS:49674}: error 10054
ERR | 20160617-143637.871 | 3CXTunnel | TUNL | 1028 | Rtp.cpp:143 | Error reading from RTP socket 456, {RS:49674}: error 10054
ERR | 20160617-143637.891 | 3CXTunnel | TUNL | 1028 | Rtp.cpp:143 | Error reading from RTP socket 456, {RS:49674}: error 10054
ERR | 20160617-143637.911 | 3CXTunnel | TUNL | 1028 | Rtp.cpp:143 | Error reading from RTP socket 456, {RS:49674}: error 10054
ERR | 20160617-143712.427 | 3CXTunnel | TUNL | 1028 | Bridge.cpp:672 | Has no registered RTP session for local destination 192.168.18.9:11800
ERR | 20160617-143712.447 | 3CXTunnel | TUNL | 1028 | Bridge.cpp:672 | Has no registered RTP session for local destination 192.168.18.9:11800
ERR | 20160617-143712.467 | 3CXTunnel | TUNL | 1028 | Bridge.cpp:672 | Has no registered RTP session for local destination 192.168.18.9:11800
ERR | 20160617-143712.487 | 3CXTunnel | TUNL | 1028 | Bridge.cpp:672 | Has no registered RTP session for local destination 192.168.18.9:11800

 

[NickD_3CX]

These log messages do not necessarily mean an error, you may sometimes get these messages due to the way the SBC handles audio streams but everything work fine.

 

[zac.mussatt]

I personally have a hard time with error messages that show up when normal logging is enabled, yet "everything is fine".
It's good to know that I'm not the only one with these messages in my logs however.

In fact, the site that I'm seeing these errors on is having some issues with extensions completing calls, and also with the extensions ringing even after call has been picked up.

Perhaps chasing these messages isn't the correct way to diagnose this issue?

 

[zac.mussatt]

Hmm. Some further testing on my end. For me, these seem to be messages that are logged when a call ends. Makes sense in a way, though I wish that it didn't categorize it as an error since this is normal operation.