Self hosted PBX using AWS in South Africa

[Phil Sbrana-Browning]

In South Africa, there are various challenges, one of the main ones is power shedding as they call it. I have had a 3cx server on-site for many years. However it seems sensible to move to cloud now, so that even if the power is down at the office (have generators, and UPS's) fuel gets stolen and UPS's generally are stop gap.
So the problem I am having is that most of the phones used here are Snom 300, These are now EOL but they work just fine on the in-house 3CX system. These will get replaced over time with Yealink models. But these snoms have issues with connecting to cloud based 3CX, even for Yealink I had to turn off Security - Anti Hacking - SSL\SecureSIP transport and cyphers, to get them running. But they did eventually connect using Stun. So I am trying SBC. But Sno300 are more difficult to work on. Does anyone know if having a 3CX server onsite would interfere with SBC connected to AWS Cloud at the same site. Or any other thoughts why provisioning fails with Snom 300 Log shows the following.
Blanked the address to anonmise.

Aug 26 12:01:22.892 [INFO ] PHN: Config setup: code: 500, uri: https://xxxxxxxxx.3cx.co.za:443/rps/cfg0004134A66F3
Aug 26 12:01:22.896 [NOTICE] PHN: Config setup: return code 500; requeueing >https://xxxxxxxxxxx.3cx.co.za:443/rps/cfg0004134A66F3<; attempt: 27, state: 27, duration: 60/68
Aug 26 12:01:24.899 [DEBUG0] PHN: TaskMon: LCS/288 PollEvent took 2011 msecs, started Aug 26 12:01:22
Aug 26 12:01:24.900 [DEBUG0] PHN: LoopMon: LCS/288 took 2014 (139) msecs, started Aug 26 12:01:22, 2 tasks
Aug 26 12:01:24.902 [DEBUG2] PHN: TMR: 'inhibit_refreshing' 0x9be5f4
Aug 26 12:01:24.903 [DEBUG0] PHN: MbParser:: enter
Aug 26 12:01:24.904 [DEBUG0] PHN: MbParser:: selected_tree = /SnomIPPhoneBatch/
Aug 26 12:01:24.904 [DEBUG0] PHN: MbParser:: using cached xml
Aug 26 12:01:24.904 [DEBUG0] PHN: MbParser:: first time read -> caching xml
Aug 26 12:01:24.906 [INFO ] PHN: Xpath applies: /SnomIPPhoneBatch/
Aug 26 12:01:24.906 [INFO ] PHN: Xpath contains unrecognized steps, aborting
Aug 26 12:01:24.907 [DEBUG0] PHN: MbParser:: found tree = SnomIPPhoneText
Aug 26 12:01:24.908 [DEBUG0] PHN: MbParserMainTag:: tree = SnomIPPhoneText

This repeats a number of time then says giving up. SBC shows in Phones

xxx.xxx.xxx.xxx:2053 via SBC where xxx is ip address of Snom on local LAN
yyy.yyy.yyy.yyy:5060 yyy is ip address of SBC

But provisioning script is
https://aaaaaaaaa.3cx.co.za/provisioning/hsctvpfd03m/cfg{mac}

 

[JohnS_3CX]

Please note that EOL phones are usually not capable of using modern SSL/TLS.

This means they can only be used on-premises with a local PBX.

If you PBX is in the cloud, you need modern phones:
https://www.3cx.com/sip-phones/

Alternatively, where applicable you can use the 3CX clients instead. The mobile apps will work over LTE even if your whole building internet and power goes down.