Losing Connections on SBC-Side

[MariusG]

Hello,



one Customer are randomly losing conversations on an SBC no matter they use DECT- or Desktelephone.



The internetconnection is stable.



I have one example:

Call history:

06.12.2022 09:17:10 XXXXXXXXXX FL-Zentrale (50) 00:00:09



Event log:
No entry for this time.



Activity log, setting was on low on this day, now I set it on middle:

I don't have the entries for this day anymore. But I think it was just a “request terminated 487”



So I thougt maybe the tunnel is giving me any error, can somebody say if “No EP found” is an relevant error? :

Tunnellog:
09:17:10.611|7f09a3fff700| Info|Tunnel.cpp(695): sbc.f58ce067 Allocated local stream 363 -> 127.1.2.3:2568
09:17:15.613|7f09a3fff700| Info|Tunnel.cpp(695): sbc.f58ce067 Allocated local stream 361 -> 127.1.2.3:2569
09:17:19.636|7f09c4b4c700| Info|Tunnel.cpp(817): clnt.0-23bee116-6f99-458f-a1e4-d8e7f9118f76_15257023 Released local stream 365 -> 127.1.2.3:2564, total 1, stream IDs 1
09:17:19.636|7f09c4b4c700| Info|Tunnel.cpp(817): clnt.0-23bee116-6f99-458f-a1e4-d8e7f9118f76_15257023 Released local stream 367 -> 127.1.2.3:2565, total 0, stream IDs 0
09:17:19.653|7f09c5b4e700| Info|MSEndPoint.cpp(3231): No EP found for 127.1.2.3:2564 <- tunnel
09:17:19.681|7f09c5b4e700| Info|MSEndPoint.cpp(3231): No EP found for 127.1.2.3:2564 <- tunnel
09:17:19.729|7f09c4b4c700| Info|Tunnel.cpp(817): sbc.f58ce067 Released local stream 363 -> 127.1.2.3:2568, total 1, stream IDs 1
09:17:19.729|7f09c4b4c700| Info|Tunnel.cpp(817): sbc.f58ce067 Released local stream 361 -> 127.1.2.3:2569, total 0, stream IDs 0

 

[Alphabetic]

Activity logging needs to be on verbose for the most detail possible.

How are endpoints provisioned?

Are they on latest FW and all supported templates/phones?

Does the call drop or just the audio?

Enable call recording and see if you can pick up this event.

 

[MariusG]

Sorry for the late reply, I wasn't in office because of illness.

My only problem with verbose loggin is that its a noticed with a warning message for high CPU Usage and the problem is very sporadic so i have to keep it on for maybe serveral weeks or is it ok to run it for this long time?
Endpoints are Yealink SIP-T48U and Yealink W80B DECT Stations with Yealink W59R - It is happening an all enpoints

Latest firmware no, the firmware is not very old but I will update it anyway and the problem is older than the newest firmware, so they were up to date when the problem happened the first time.

The call drops.

It happened while a call by myself too. I called, 3CX queue music was playing, and then the call ended. Customer called me back then and said he answered the call but had a immediately drop of the connection.