I’ve been bashing my head on a new install of Freepbx V17, installed from the premade iso that auto runs installation scripts for you.
Logged in, went through the initial firewall setup wizard, created some extensions, went to endpoint manager and updated the sangoma_default config to match IP address settings for local environment. I went into Extension Mapping and mapped the extension with the MAC provided, along with the model and config to use.
I have the S500 in the Sangoma Portal and configured the redirection for http, pointing to the local IP address of the PBX, without authentication. Factory reset the phone, and confirmed it checks in on the Portal (though from a 10.x.x.x address, not my public IP and it isn’t even the same address class as the local IP of the phone). The Apache logs on the server are showing 404 errors from the phone trying to access
/cfg0500.xml
/[MAC_ADDRESS].cfg
/[MAC_ADDRESS]
/cfg[MAC_ADDRESS].xml
I can connect with the same settings via MicroSIP and confirmed the extension can register.
I’m sure I’ve missed something stupid to get these configs working, as I’m not super familiar with PBX items, but more familiar with other server management. Open to any suggestions or providing additional info.
same issue as yours. I was trying to update a couple of phones, and figured I’m going to factory reset them just to make it easy on myself… I guess not.
anyway, started a ticket at help.sangoma but they said I needed credit to answer a simple yes or no question: is your redirect service working or have you turned it off for all S series phones.
I did try different server locations, and S505 and S300 with the same result.
would someone who has a S series phone do a factory reset and tell me if it still works?
Hey so what I did was wipe my server once again, started with a base Debian 12 install and then ran the installation script. The last time I tried this method, had a bunch of errors, but this time everything ran without issue.
From there, I did a basic setup with some extensions, made a template in endpoint manager, set up everything in the sangoma portal and now it just works. No clue as what changed, but it is having no issues for me anymore.
well thank you for the response. I have two on Debian with 17 and two on 16 with centos and all have the same issue. I rather not have to load them again, as I thought the migration to 17 was going so well.
the 10.x.x.x ip address is throwing me off. (among other things of course)
thanks for your response.
My phones are still showing the 10.X.X.X address in the sangoma portal, but I can confirm that they are getting a config and contacting the server.