We are also setup on the same configuration with a Cisco ASA 5505 v8.2 and our 3CX is a Hyper-V VM. This is not a problem, it is good security. To do that (if you need to), you need to punch holes through the Cisco ASA.Īlso, SIP connections are initiated from inside to the VOIP trunking provider ( above). ![]() Please note that the configuration above not allow you to connect using the 3CX tunnel from outside. The Cisco ASA with the SIP ALG takes care of all of that, including punching the correct holes for the RTP streams. This makes sense, because the settings above basically tells 3CX to not worry about NAT. No changes to the Cisco ASA configuration (no special NAT rules, no changes to SIP settings, no special firewall rules).Įverything worked fine (inbound, outbound and no call drops). This is nice because the PBX can protected by the firewall in the ASA. (It is worth mentioning that I had some difficulties getting version 7 to work on a PC with two Ethernet interfaces.įor the results described here, everything was done here on a different PC with a single Ethernet interface). ![]() I want to report success setting up 3CX with a Cisco ASA 5505 (version 8.2) without using port forwarding.
0 Comments
Leave a Reply. |