This release is very buggy and should not be ran on a production system. There is a major issue where a connected Sangoma Connect mobile client will trigger a forced Asterisk restart if it changes networks and registers again. It is reproducible just by turning off the WiFi on a mobile phone. The next major issue is that Jitter is very high when using Sangoma Connect versus Zulu which causes a lot of static or voice issues. The last issue when testing is that signaling is not reaching the phones. If an internal extension hangs up, the mobile client will stay connected forever. The mobile client will also not ring on incoming calls. We are having to stay with Zulu or some other softphone solution for now because of these issues but once Sangoma Connect is more stable and working then we will probably switch over.
Are there new requirements for Sangoma Connect? The server has been running in the cloud just fine with Zulu and EPM phones with no SIP NAT / Firewall issues. If there are new requirements where might I be able to find the ports or IP addresses that need to be allowed. Also, why can calls made from the mobile client work just fine with no issue but only inbound doesn’t work? Audio works both ways when outbound and there is no timeouts either.
I’ll see if I can find the logs where asterisk restarted. It happened three times in a row and was triggered by a network change which triggered a re-register of the client.
Unless you’re seeing something new, this is not a Sangoma Connect issue, it’s an Asterisk DPMA issue. Upgrade asterisk16 to current and restart, ensure you’re running dpma ver. 3.5.5
uc-51459655*CLI> digium_phones show version
Digium Phone Module for Asterisk Version 16.0_3.5.5