Imagine
Day 0 - Assessing the clients needs, both current and future
Thx for your reply

but you don't teach me anything with this.

If you have the same new customer activation volume as we do .. you understand that even if the customer says "We want to use virtual faxes" .. there will always be customers who will change their mind.

And that's normal .. we are here to support them!
Also,
1. I'm fairly certain 3CX announced somewhere that FXS will be supported via SBC.
Currently ... it is not possible to configure a FAX extension on FXS in "remote" .
Fax extension is « Allow lan only ».
No SBC , No Stun , No Remote.
3CX Solution : VPN or Local PBX .. or configure without T38 protocol.
2. No one who likes their clients would suggest faxing via FXS anyways
I can assure you that it works very well with the T.38 protocol and all of our customers love the sharing SIP channels between calls and faxs.
We have not encountered any problems ..
I know that I don't teach you anything either ; Work with
reliable SIP providers, use
quality fx gateways and follow the
3CX recommendations .. It works VERY well.
3. It's pretty trivial to move hosted instances provided you are using supported devices provisioned properly.
Moving is not a problem .. it's all a question of price and selling points..
We have
14 sales counters... We are everywhere in the province of Quebec.
Understand here that it is not profitable to have to do duplicate work .. while other customers wait for their new services to arrive.
At
Bravad .. we sell a lot
SaaS mode (Software as a Service) and as such the customer do not buy 3CX from us but rather a turnkey managed services that is using 3CX as a foundation.
Generally We do not sell a customer a license, a software or a server, we run an environment that own and use 3CX to deliver the service.
We are accountable to deliver a services.
@BrenttG
This is also why we use your
PBX Monitor product. (
Try it!)
I don't remember seeing the ad where 3CX would lift the "Allow_lan_only" block using 3CX fax extension.
Obviously, there are plenty of other solutions to work around this limitation. But we always look at 3CX solutions before looking at alternative solutions.
Thank you for taking the time to answer me
