Let me start by saying we know we are doing this wrong and are open to a better way.
Backstory:
We have our own hosting platform using Nutanix AHV and our own commercial SBC with Oracle SBC (formerly AcmePacket SBC). When we started with 3CX we wanted to maintain use of our SBC for all the protections it provides and our familiarity with the configuration. We host 3CX pbx's for our customer base and everything seems to work pretty well. We quickly found we needed to tweak the provisioning template to get it to work, no problem, a custom template to the rescue, well that broke hotdesking. So we used SED to find/replace the base template (Snom) to our requirements. None of this was difficult and again everything was working great. We used SED because every time the template was updated our changes were lost so a cron job is run to check for our changes. Another update occurred and we could no longer add our SBC's fqdn into the Phone Provisioning section for "3CX Session Border Controller" so we added it under trunks and then used the new drop-down, all was well, minor changes and things came back to life.
Issue:
We are no longer able to provision handsets. Now we get a couple of errors when attempting to provision a new phone.
Phone xxx of extension 1999 is behind SBC our_sbc.our_domain.com which has no known local IP yet!
Provisioning file /provisioning/unique_prov_folder/cfgxxxxxxxxxx requested by 11.11.11.11 could not be generated
If we log into the phone and manually provision everything the phone comes up and registers just fine.
I am starting to think we need to give up on our Oracle SBC and drink the full 3CX Kool-Aid and setup one of their 3CX SBC's at each client's site.
Am I missing something on the provisioning? It really does appear that 3CX is looking for that SBC to be up and responding in order to allow phones to be provisioned against it.
In case it matters we are on 10.8 Update 8 (Build 939)
Backstory:
We have our own hosting platform using Nutanix AHV and our own commercial SBC with Oracle SBC (formerly AcmePacket SBC). When we started with 3CX we wanted to maintain use of our SBC for all the protections it provides and our familiarity with the configuration. We host 3CX pbx's for our customer base and everything seems to work pretty well. We quickly found we needed to tweak the provisioning template to get it to work, no problem, a custom template to the rescue, well that broke hotdesking. So we used SED to find/replace the base template (Snom) to our requirements. None of this was difficult and again everything was working great. We used SED because every time the template was updated our changes were lost so a cron job is run to check for our changes. Another update occurred and we could no longer add our SBC's fqdn into the Phone Provisioning section for "3CX Session Border Controller" so we added it under trunks and then used the new drop-down, all was well, minor changes and things came back to life.
Issue:
We are no longer able to provision handsets. Now we get a couple of errors when attempting to provision a new phone.
Phone xxx of extension 1999 is behind SBC our_sbc.our_domain.com which has no known local IP yet!
Provisioning file /provisioning/unique_prov_folder/cfgxxxxxxxxxx requested by 11.11.11.11 could not be generated
If we log into the phone and manually provision everything the phone comes up and registers just fine.
I am starting to think we need to give up on our Oracle SBC and drink the full 3CX Kool-Aid and setup one of their 3CX SBC's at each client's site.
Am I missing something on the provisioning? It really does appear that 3CX is looking for that SBC to be up and responding in order to allow phones to be provisioned against it.
In case it matters we are on 10.8 Update 8 (Build 939)
The SBC is a quick install, especially in a VM, or many phones can be (re)configured as router phones to function like an SBC. There is basically no maintenance on the SBC, though sometimes it will have an upgrade that is visible and can be done in the 3CX GUI.
