So we have been running 3CX for our smaller remote team for business calls and chat/collaboration. We did not need to install an SBC because the most there was at one location was 3 phones.
I am considering deploying this to one of our customers that needs to cut costs. As we all know the world is a bit different at the moment so were adapting. This deployment of we do it would be 500 hard phones same network with a voice vlan.
As a company were familiar with Cisco voice and collaboration. Ramping up on the 3CX was fairly quick and straight forward. I say this so if someone on here knows both it is a good point of reference on what we are used to in a system.
So I do have a few reservations that I hope someone here can help me get comfortable with.
What's the deal with the SIP and RTP ports and having to make them unique? When I first read it I didnt believe it but we have noticed if ports are conflicting we will see multiple entries in the phone area for one phone. The phone also does not function properly anymore until its corrected. I can't deploy this many phones and have that hanging out there as a concern. Tracking that would be a nightmare. With Cisco we never have to even think about anything like that. I know it's not a firewall thing either because all our customers have stateful firewalls. We have Cisco phones running from a cloud hosted call manager cluster without any issues like this. Putting the 3cx on the same network and this issue comes into play.
SBC.. I am assuming we would have one in play for this customer. What can this run on? Is there a small inexpensive rack mount firewall looking box or something it can be set up on? If we tried telling a customer this raspberry pi is what your phones are relying on they would laugh us out of the building. Thoughts here?
The next thing is processing local calls. My goal here was to host the system in DO. Is there a deployment strategy that will allow extension to extension calling within the building to stay within the building? We have a few different 3rd party cloud voip services (not from us) running at customers that deploy a gateway that allows that functionality. I think one is an ME3400. Is there a solution for deploying a system with this functionality?
Lastly and this is more informational and not critical. We are used to a capability Cisco has with their voice gateways called SRST. It allows us to terminate a local PSTN connection via copper to the gateway as redundancy in case the DIA goes down. Does any solution like this exist that works with 3cx?
For anyone that is kind enough to respond here with some insight I greatly appreciate it and thank you in advance for your help.
Ted
I am considering deploying this to one of our customers that needs to cut costs. As we all know the world is a bit different at the moment so were adapting. This deployment of we do it would be 500 hard phones same network with a voice vlan.
As a company were familiar with Cisco voice and collaboration. Ramping up on the 3CX was fairly quick and straight forward. I say this so if someone on here knows both it is a good point of reference on what we are used to in a system.
So I do have a few reservations that I hope someone here can help me get comfortable with.
What's the deal with the SIP and RTP ports and having to make them unique? When I first read it I didnt believe it but we have noticed if ports are conflicting we will see multiple entries in the phone area for one phone. The phone also does not function properly anymore until its corrected. I can't deploy this many phones and have that hanging out there as a concern. Tracking that would be a nightmare. With Cisco we never have to even think about anything like that. I know it's not a firewall thing either because all our customers have stateful firewalls. We have Cisco phones running from a cloud hosted call manager cluster without any issues like this. Putting the 3cx on the same network and this issue comes into play.
SBC.. I am assuming we would have one in play for this customer. What can this run on? Is there a small inexpensive rack mount firewall looking box or something it can be set up on? If we tried telling a customer this raspberry pi is what your phones are relying on they would laugh us out of the building. Thoughts here?
The next thing is processing local calls. My goal here was to host the system in DO. Is there a deployment strategy that will allow extension to extension calling within the building to stay within the building? We have a few different 3rd party cloud voip services (not from us) running at customers that deploy a gateway that allows that functionality. I think one is an ME3400. Is there a solution for deploying a system with this functionality?
Lastly and this is more informational and not critical. We are used to a capability Cisco has with their voice gateways called SRST. It allows us to terminate a local PSTN connection via copper to the gateway as redundancy in case the DIA goes down. Does any solution like this exist that works with 3cx?
For anyone that is kind enough to respond here with some insight I greatly appreciate it and thank you in advance for your help.
Ted
