SBC phone not reporting dropouts via email

[Dunblue]

We have an issue with a Yealink T53 router phone dropping its connection several times a day and affecting any other devices connect to its SBC.

However it has not been reporting this to us, despite having email notifications set up for these events. We have checked that the SMTP test is successful, and the emails aren't being caught in any spam filters.

We also have a Windows SBC on the same network for testing purposes, and this reports up/down changes correctly - so it's only the router phone that isn't reporting.

Why could this be?

(3CX Version 20.0.4.487, latest phone firmware, tried factory reset device)

 

[SteveITS]

I hadn't noticed since most of these for us are overnight ISP maintenance and we just ignore them, but I looked back for one client and they stopped getting router phone drop emails the day we upgraded them to v20 even though a Pi SBC alerted. There have been multiple threads asking for the ability to toggle router phone alerts off separately from the trunk alert, which is useful for clients with a lot of router phones (e.g. at home). So maybe it was removed.

 

[ivank]

Hello Dunblue,

Emails for router phones are not sent since Version 20.

Also, some changes in the notification comes starting from Update 5:

If SBC goes down and stays down more or equal to 1 minute : we send DOWN email If SBC goes up after it was down more or equal to 1 minute: we send UP email Thus if SBC spent less than 1 minute, we sent nothing. We will still record these events in the event log but we will not send the email. As before, we don't send emails for router phones but now we'll record down/up events.

 

[Dunblue]

Excellent.