FreePBX 17 DND Still Letting Calls Through Digium / Sangoma Phones with DPMA

We’ve been migrating phones over to a new FreePBX17 server. We have a mix of D series Digium phones and some P series phones. Initially when we would change our “status” on the phone to DND, when someone would try to call us, it would send them directly to voice mail. I’m not sure what has changed, but when we set our phones using the “status” app on them, it shows like we are on DND, but it still allows calls through.

I’m not sure what changed and how to get it back to the expected behavior. The only noteworthy thing is I had “sangoma connect” uninstalled for a while, but then with D40 / D50 phones they were giving an error when trying to “toggle red” in visual voice mail telling us to install “sangoma connect”. After installing that, it seems to have fixed that problem, but now all of a sudden DND isn’t working as expected on all phones. We do not have the “sangoma connect” license, but it seems like visiual voice mail on D40s/D50s has some sort of dependency on it?

Here is output for core show hint for a sangoma P325 before/after changing status using soft keys.

BEFORE
asterisk -rx “core show hint 156”
156@ext-local : PJSIP/156&PJSIP/99156&Custom:DND156,CustomPresence:156 State:Idle Presence:available Watchers 14
1 hint matching extension 156

AFTER
asterisk -rx “core show hint 156”
156@ext-local : PJSIP/156&PJSIP/99156&Custom:DND156,CustomPresence:156 State:Idle Presence:dnd Watchers 14
1 hint matching extension 156

The other thing that was different before was when a user would set DND(presence), the BLF light for that extension(on other phones) would light up solid green. That is no longer happening.

Am I correct in that the expected / intended behavior (on FreePBX 17) of when a user changes their “presence” / “status” to “Do Not Disturb”(DND) that their phone should no longer ring and should send the caller directly to voice mail?

Can someone at least confirm the expected behavior when changing the “status” in the phone app to “DND” is for D series and P series phones on FreePBX 17? Should calls be send directly to VM or not?(our users are used to calls being sent to VM when DND is on)

Hi @jdennis
The Expected behavior is - When the P/D phone status is set to DND, incoming calls to those extensions will be sent to voicemail if it is enabled. If voicemail is not enabled, the call will be dropped with a busy status.

You can check the extension’s current status via the CLI:

Example

freepbx*CLI> core show hint 1002
1002@ext-local      : PJSIP/1002&PJSIP/901  State:Busy  Presence:dnd  Watchers 1

Ok, that confirms how I assumed it was supposed to be working, just like in previous versions. That being said, any suggestions on what to look into since it’s not working properly for us on FreePBX17? As I mentioned prior, I suspect “SangomaConnect” is somehow preventing it from changing the “State” for our extensions when in DND via status using softkeys on the phones. I only re-installed “SangomaConnect” because visual voicemail on D40s wasn’t working properly and gave an error telling us to install it.

I just put my phone(P325) in DND using the “status” softkey and this is what the hint shows.

core show hint 156
156@ext-local                 : PJSIP/156&PJSIP/99156&Custom:DND156,CustomPresence:156        State:Idle            Presence:dnd             Watchers 16
1 hint matching extension 156

Hi @jdennis
It seems that your RestApps service is not running. Please make sure the RestApps PM2 service is running, and then check again.

how to check process
fwconsole pm2 --list

if you found restapps is not running then run this
fwconsole pm2 --restart restapps

This is what I see when I run that first command. Appears it is running.

Hi @jdennis
Try to restart once again and then check the enable/disable DND and test

I’ve tried rebooting the server, among many other ideas and no matter what I do the issue persists. I have opened a support case with Sangoma.

So Sangoma support figured it out. We had disabled *80 , the feature code for intercom, which by default auto picks up on the extension you put after it. We were worried someone may abuse it. Once *80 was re-enabled that fixed this DND issue. I have no idea how/why that feature code is related to the issue at hand, but it definitely was in this case.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.