We switched over our Altice SIP connection to 3CX in an attempt to go live today, however hit major issues during go live.
For outbound calls, 3CX is sending a proxy authentication to what should be a trusted, non authenticated connection. The SIP on the provider side is throwing 407 and responding to us with 403. We have it set to no authentication on the SIP channel.
For inbound calls, they are seeing a mix of requests from both the PBX IP and the handset ips. They need the 3CX IP to be what communicates with the SIP trunk IP, not pass the phone IP at all.
We are in the middle of a PoC trial license. If someone has knowledge of setting up specific SIP scenarios it would be greatly appreciated. We also don't have a set vendor for our purchase. If someone who is a vendor can get this working, we are looking to purchase the full enterprise 1024 license and would go with you since you could support our environment.
For outbound calls, 3CX is sending a proxy authentication to what should be a trusted, non authenticated connection. The SIP on the provider side is throwing 407 and responding to us with 403. We have it set to no authentication on the SIP channel.
For inbound calls, they are seeing a mix of requests from both the PBX IP and the handset ips. They need the 3CX IP to be what communicates with the SIP trunk IP, not pass the phone IP at all.
We are in the middle of a PoC trial license. If someone has knowledge of setting up specific SIP scenarios it would be greatly appreciated. We also don't have a set vendor for our purchase. If someone who is a vendor can get this working, we are looking to purchase the full enterprise 1024 license and would go with you since you could support our environment.
