You may have been hearing about this over the last few months while we’ve been testing internally and with invited customers. If you haven’t heard, Sangoma Connect is the next generation mobile client offering from Sangoma for FreePBX and PBXact. Anyone with a Zulu user license (including the free 2 user trial) is able to try it out. If you want to be part of the beta testing phase, you can follow the installation and setup instructions here:
Sangoma Connect does require that you have a user management user with a pjsip primary extension. The App will register to the PJSIP TCP transport, so you may need to enable that in Asterisk SiP Settrings and restart Asterisk. See the full technical details here: https://wiki.freepbx.org/display/CONNECT/Technical+Details+and+Limitations
In the user management (SangomaConnect Tab) it says my EPM module is too old. I have 15.0.27.4
I just use one phone with the EPM for testing, which is a Sangoma s705. When I try to update (edge) the EPM module it says it is the same as online version…yet in the instructions it says I need 15.0.27.38 or newer? How to get there?
So this inserts a third-party system ("Sangoma Connect cloud) into an on-prem setup? If so, is this required to for it to work, or can it function as the current Zulu client does; with only direct connections to the end points?
There is a cloud server that proxies encrypted data between the client and the PBX. It is required, and is used for the initial provisioning setup as well as for non-voice services such as contact management.
I’m not sure how adding a failure point lands a system at more always working. If an on-prem solution is correctly configured, it will always work, barring new bad code, ISP failure, or the like, which would affect the new system as well.
Adding complication rarely, in my experience, reduces failures.
I just read in another thread that some of the rpms are missing on your servers…so I thought it might be related to this problem. The fwconsole setting change to the two mirror servers was the only way to download the newest EPM…I have no idea why…
…and now for someting completely different…beta testing
Again, I have no issues with that repo. I suspect you have a caching issue, you can disable ‘module admin caching’ in advanced settings to test my theory.
nope…deactivating module-admin-caching wont make a difference…
anyway…I have a question regarding the SangomaConnect Client: Where can I set the port, which should be opened (router) for the SIP signaling? Can I choose a random port? Without the forwarding the client does not connect.
