FreePBX 17 - Sangoma P330/320/310, EPM with DPMA enabled

Commercial Modules Endpoint Manager
1

Crossposted from Reddit:

So I’m not 100% sure where I am screwing up.

HTTP provisioning Port is at 84 HTTPS is at Port 1443 Restful apps is at Port 82 with secure at 3443

DMPA is enabled and configured EPM is configured MAC address is loaded into EPM and everything there is configured

I can provision microSIP and confirm that the line and extension works as intended.

I can configure other phones manually and confirm that they work as intended.

I cannot get the sangoma configuration server to properly configure this phone.

The error I get is as follows every time the phone goes in queries this server:

SSL 6 [SSL_ERROR_ZERO_RETURN] (Read ret: 0 Len: 65535)

Some confirmations:
Confirmed not self signed certificate - sourced free from Cloudflare
Confirming that I have added the MAC into EPM
confirming I also added the extention and account to the Mapping, along with template and configured by server is selected.

2

Are you seeing this error on asterisk cli ?

SSL error means phone is not able to make HTTPS connection with the PBX /Asterisk.

Try to enable DPMA logging to see if this gives you any clue.
https://sangomakb.atlassian.net/wiki/spaces/PG/pages/32669947/EPM-DPMA+for+Digium+Phones#Troubleshooting

3

I’m following this error in the following log

/var/log/asterisk/full

The biggest problem that I’m running into seems to be a discrepancy of whether or not I can provision using TLS.

I’m also not able to get a fully functional provision even if I use TCP as I’m not sure that endpoint manager is actually creating a functional provisioning file.

I don’t seem to have a means to be able to log into the web portal of a P330 phone and tell it where the server is either which is kind of odd. As soon as it connects over TCP the password of the phone changes and the web portal is disabled on the phone itself. But then the GUI on the phone also becomes useless saying that nothing’s been activated or anything.

4

I’ll look over your aforementioned link, but I do see a warning immediately at the top that says the following

THIS WIKI IS APPLICABLE ONLY FOR THE ENDPOINT MANAGER V15.0.38+ AND V14.0.67+ RELEASES

Between those two versions is and 16 and end 17 which I am running 17.0.2.2

5

wiki is applicable for 17+ also and that is specifically to capture the DPMA logs.

6

I adjusted the command as this in FreePBX 17 which is loaded into Debian, and there was anything that pulled up with the below command.

apt list | grep res_digium
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

I have also confirmed that the DPMA logging is enabled, bu no log is present in the documented location.

i searched for a file named the same to no avail. is the package named something different in the debian environment?

7

you can try below to confirm if module is actually loaded to your system or not.

*CLI> module show  like res_digium_phone
Module                         Description                              Use Count  Status      Support Level
res_digium_phone.so            Digium Phone Module for Asterisk         4          Running          extended
1 modules loaded
8

I ran the command as suggested. Below is my result.

Module                         Description                              Use Count  Status      Support Level
res_digium_phone.so            Digium Phone Module for Asterisk         4          Running          extended
1 modules loaded
9

so DPMA is running in your system , as this is EPM with Px so request you to please raise support ticket so we can try to check your system directly and feel free to share the ticket# with me to check internally.

Best Regards,
Kapil

10

This is done from the portal right? Excuse my lack of knowledge on opening a support ticket with you guys, in the 7+ years of using FreePBX I havn’t had to open a support ticket.

11

Here is the link…if you still need it…

https://support.sangoma.com/index.php?/Default/Tickets/Submit/Index

2 Likes
12

Please follow up with any info as I ran into this same issue with P330/P315 phones on a brand new FPBX17 install. I ended up having to go back to non-TLS as I ran out of time troubleshooting it.

13

Will do,

So far nothing of significance has turned up. I know there is the note about provision without TLS first then switch to TLS after, but i’m chipping away at all these small little details, working with support and engineering on the matter.

So far some materials to consider.

Local DNS needs to be set to resolve yourpbx.yourdomain.FQDN
you need to set phones in the depoloyments as well with there needed informations
https://portal.sangoma.com/index.php/deployment
Cloudflare didnt generate the needed Cert that i thought i could use, I resolved my issues around using Let’s Encrypt as well.

The provisioning issue remains though.

14

Just a couple notes that may help.

The lack of a web GUI after initial configuration of P-series is expected.

The factory shipped firmware on the P-series doesn’t support the Sangoma redirect service (we are receiving 4_9_2). Manually updating to 4_18 got it working for me, which then got DPMA working. Try a firmware update on the phone if you haven’t already.

15

Firmware is up to date, manually done from web interface prior to provisioning.

1 Like
16

Bumping to keep open as I would like to post solution once engineering has this solved.

1 Like
17

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