NEW OSS EPM for FreePBX 16 & iPBX 2027

[Samot]

Ah, but the commercial modules will not run on the raspberry pi platform. I specifically tried using the commercial Endpoint Manager and it would not run. It needs ionCube to decrypt the PHP before it can run. I tried installing ionCube but it requires setting zend_extensions in PHP.ini and something else is already using it. I stopped looking at that point.

I was more pointing out there wasn't a specific provisioning module for Sangoma phones.

 

[DavidKeeney]

Correct. So that is why I thought it might work to add a Brand and some templates to the OSS EPM for the Sangoma phones.

 

[Samot]

Correct. So that is why I thought it might work to add a Brand and some templates to the OSS EPM for the Sangoma phones.

Should work just fine. There will be features on the phone that can't be used due to the lack of the commercial modules but outside of that, basics should work just fine.

 

[dicko]

Ah, but the commercial modules will not run on the raspberry pi platform. I specifically tried using the commercial Endpoint Manager and it would not run. It needs ionCube to decrypt the PHP before it can run. I tried installing ionCube but it requires setting zend_extensions in PHP.ini and something else is already using it. I stopped looking at that point.

You should wait a bit, after many years of failed cajoling, Sangoma have now been forced to go with Debian (of which and just in MHO, VERY pre-alpha ) which should fix all that nonnsense.

 

[wookielinux]

I setup the OSS EPM and got it working ok with t*f*t*p more or less with local phones.

I need to make it work via http or http(s) for external phones. Setting the provisioning url - https://"mypbxpublicip"/p.php/ I can see the phones connect in the /access.log but the phones do not provision.

The URI comming in is https://"mypbxpublicip"/p.php/0000000000.boot (its a yealink phone)

can OSS do public side provisioning? looking at the code for p.php it feels like this is not really ready.

Regards

 

[normanu]

Hi guys, hope anyone can help.
I was still running a Askozia server for over some years, but now the licenses changed to not activated and are removed.
So I'm forced to switch

Installed IncrediblePBX and trying to provision the phones with this.
I have SNOM phones followed everything, but for some reason the phones don't get provisioned.
I saw that the package doesn't install the t*f*t*p server, so did that manually.
Fixed the template error with the github fix (https://github.com/matmurdock/endpointman/commit/6e78dea6ecaf3f204efedfaf94b1d40fbdb2bb85)

But how do I make it so the phones do get provisioned?
Hope someone can assist!

Assigning a template and press reconfigure and reboot phone doesn't do anything.
I have SNOM 715 phones.

 

[kenn10]

Are you running IncrediblePBX on a local machine or on a cloud machine? What version of IncrediblePBX are you running and one what operating system and version?

 

[normanu]

I am running it on a local machine, version 2027-D 16.0.40.6
OS is Debian Bullseye 11.9

Thanks for the fast reply!

 

[kenn10]

My experience has been that some phones do not respond to the reboot command. Also, if the phones are not on the same LAN with the PBX, reboot rarely works. I'll let someone who has Snom phones respond with their experience.

Your DHCP server will need to provide option 66 and/or option 150 information (depending on which option your phones need) to point the phones at the new location. Then when the phones reboot, they automatically load from the correct config server.

If your DHCP server does not provide option 66/150 support, to get the phones to reprovision, you'll need to access their setup screens and point them to the provisioning server. The phones do not know where to look or what protocol (http, https, t*f*t*p) to look for until you tell them.

 

[normanu]

Ah! but that is not mentioned anywhere
I thought they would be configured by upnp
What would the setting be for the DHCP server?
Which address / info do I need to fill in?

 

[mbellot]

One other thing I found is my phones (Polycom) will only reboot if configured as SIP extensions, if you configure them as PJSIP they will not reboot.

 

[Samot]

One other thing I found is my phones (Polycom) will only reboot if configured as SIP extensions, if you configure them as PJSIP they will not reboot.

That sounds like the EPM is missing a proper notify command for chan_pjsip. Each driver has its own command syntax.

 

[kenn10]

Ah! but that is not mentioned anywhere
I thought they would be configured by upnp
What would the setting be for the DHCP server?
Which address / info do I need to fill in?

You need to research whether your DHCP server supports option 66 or option 150. You also need to know what option your Snom phones expect. Your options on the DHCP server should point to the ip address of your IncrediblePBX server.

 

[normanu]

I can configure 66 and/or 150 of needed.
So just the ip?
Nothing else?

Ea. 192.168.60.2

Does the OSS module also announce through upnp?

 

[kenn10]

Does the OSS module also announce through upnp?

I do not believe so. The EPM is mostly just a passive agent that reacts to generate configuration files and serve them when a request comes to it.

 

[normanu]

Don't know if this works for all brands, but sounds like this would be easy enough to implement?

Overview SIP Plug & Play - Snom Service Hub - Snom Confluence

service.snom.com

 

[mbellot]

That sounds like the EPM is missing a proper notify command for chan_pjsip. Each driver has its own command syntax.

Yep, I already (sort of) figured that out. See this post in this very same thread.

Since it was in the general endpointman functions.inc.php, I didn't think it was brand specific. I didn't see anything related to pjsip notify (or more properly pjsip send notify) anywhere else in that file.

As stated in that post, I know virtually nothing about PHP so I'm at a loss how to add the necessary code/functions to get the commands included. At least I can manually reboot one extension at a time from the CLI.

 

[Samot]

Yep, I already (sort of) figured that out. See this post in this very same thread.

Since it was in the general endpointman functions.inc.php, I didn't think it was brand specific. I didn't see anything related to pjsip notify (or more properly pjsip send notify) anywhere else in that file.

As stated in that post, I know virtually nothing about PHP so I'm at a loss how to add the necessary code/functions to get the commands included. At least I can manually reboot one extension at a time from the CLI.

That function is what creates the sip_notify.conf file that needs to be in /etc/asterisk, which works for chan_sip. There needs to be a pjsip_notify.conf that either needs the same content or needs to have

#include sip_notify.conf

in it so it includes the sections from that file.

So two things are required; 1) There needs to be a pjsip_notify.conf generated and 2) a function to trigger the Asterisk command for sending a notify, what type of notify and to what endpoint added for the Reboot Phone functions.

 

[normanu]

And something that calls it to trigger i guess?
Unfortunately also not a programmer

 

[K0JSC]

So I seem to be having an issue that no one has experienced and this goes back to my last install (incredible pbx 2021). After scouring the forums I'm coming up empty handed. This is a fresh install of Incredible PBX 2027 on Debian 11 and I'm just stuck here no matter which set of instructions I follow. Any/all suggestions are appreciated.