I am using freepbx 16 and 17 , dpma, and speed dial and BLF is not working. Considering speed dial is deprecated, I used contacts but its not working either .
Any clu why its not working? Is there any special port needs to be open? .
Need more information, potentially a lot more. Obviously speed dial from contact manager is not broken for everyone, and you’re going to have to describe how BLF is involved in speed dial. Please provide the specific steps you’ve tried that are not working.
Hi Lorne,
BLF is not involved in speed dial. The goal is having a speed-dial and a BLF like this. ( This is an example )
Line keys-> line key 3 → BLF BLF *45 account1
Line keys->Line key 4 ->Speed dial DND on/Of *76 acount1
Phone is a D65 and it does not show these labels next to line key 3 and 4.
I read speed dial is deprecated in version 16 and 17th so I have added a contact list under horizontal softkey.
Horizontal soft key->Idle → Idle 2 → Contacts → APP-Contacts
I have Contacts on soft keys but it does not load anything.
On version 17 and 16 I have Dpma 3.6.9 and Http provisions port 5060, restful api 82
Same setting works on a version 15 with dpma 3.6.5 . same ports.
Please let me know if you need more information. Thanks.
I can’t assist, I’ve given away all my EOL phones, perhaps someone else here might be able help. But really, these are SNG proprietary phones using their apps, I would expect the assistance you need would be available on the fpbx forum.
Hi
How about P310? I have same the issue with P310
I already have tried fpbx forum and have a support case open also. No result with their troubleshooting though.
]
I gave up a long time ago on sangoma hardware because of issue just like this. When the phones were Digium they were great, as soon as sangoma took over nothing but problems.
CIP Phones and Clearly Devices Module have been basically flawless.
If you can, I’d recommend replacing those EOL phones with CIP models. I know “Buy new phones” probably isn’t what you want to hear.
1 Like
Part of the problem over this is how you posted a lot of things. The formatting is causing the forum to process it like HTML and in some of your postings where it does appear you have posted sections of the configs, the forum shows nothing because due to the brackets (<>). Which ends up having your post look like you didn’t add anything.
What troubleshooting has been done? That would be helpful.
Thanks for the recommendation, I assume you have CIP phones. So u dont see issues like this?
Thanks for your reply. I have an open ticket since March and I have been working with one of the support guys in Sangoma. Checking phones frame ware, upgrading the firmware, checking templates, EPM and DPMA config and Freepbx module update. That’s what we did, but what I have seen myself is a difference in how pbx behaves for DPMA 3.5,6 to get XML files in comparison to how it works with 3.6.9 which makes this difference. No offense, but maybe I need someone more experienced in support to check it. The other reason I believe its the DPMA version is the fact that we have two Freepbx 15. one has DPMA 3.5.6 and phone apps are working with this one and the one with DPMA 3.6.9 does not.
No issues with the CIP phones and the Clearly Devices App to configure them.
Thanks, I will give it a try.
yeah, unlike regular phone apps, or XML-based ones like CIP phones and compatible brands, the P series use something different, called DPMA-apps, the requests get proxied through the SIP/PJSIP port and asterisk sends the regular HTTP-based counterpart to the phone app… this makes debugging complicated and also won’t include full debug information unless you enable DPMA Logging under the DPMA management page.
I’d try first to enable the DPMA Logging if it is for a D/P series phone, and see if logs throw out something useful, hope this helps
Hi, Yes I did enable it and checked the DPMA logs. That’s how I know the difference between these two version ( I keep saying its related to the version , it may not. The only difference I see is this. I might be wrong )
If it helps I can paste the logs here.