Hello everyone,
I previously posted this a month ago but not able to reply back to my thread now. I'm hoping that others have had this problem and could provide some guidance, I've seen a couple people post similar threads with no update on resolution. I get everyone hates sonicwalls but this problem looks like it originates from the 3cX server regardless of the firewall. Yes I've followed every best practice in setting up the sonicwal and I've also spent hours on the phone with sonicwall. Here is my issue:
I've had some call quality and dropped calls issues over the past few months and now I'm digging a little deeper. I've got an up to date on prem 3CX server running on Debian, the firewall is a sonicwall TZ300 with BWM setup as well as all of the settings according to the 3cx articles. My problem is that the firewall checker fails sometimes on random media server ports with the message "testing 3CX Media Server... failed" and then the failed port will show "testing port 9024... Mapping does not match 9022. Mapping is 9088", I ran a tcpdump on the 3CX box and analyzed it with wireshark. Here is what I see:
3cx server sends out packet on port 9022 with the same "Message Transaction ID" as the next packet on port 9024, the sonicwall sends both of these packets out, and two responses come back for that exact "Message Transaction ID" but both have the same port 9022 and then the 3cX firewall checker shows the mapping error above.
Troubleshooting points to the firewall... however... isn't the 3CX server generating the "Message Transaction ID"? Its easy to say replace the firewall but its hard to dispute the fact that the message transaction ID is being generate on the 3CX box, the sonicwall is going to forward that packet the way it is so how could it possibly be the firewall causing this?
Thanks!
Dave
I previously posted this a month ago but not able to reply back to my thread now. I'm hoping that others have had this problem and could provide some guidance, I've seen a couple people post similar threads with no update on resolution. I get everyone hates sonicwalls but this problem looks like it originates from the 3cX server regardless of the firewall. Yes I've followed every best practice in setting up the sonicwal and I've also spent hours on the phone with sonicwall. Here is my issue:
I've had some call quality and dropped calls issues over the past few months and now I'm digging a little deeper. I've got an up to date on prem 3CX server running on Debian, the firewall is a sonicwall TZ300 with BWM setup as well as all of the settings according to the 3cx articles. My problem is that the firewall checker fails sometimes on random media server ports with the message "testing 3CX Media Server... failed" and then the failed port will show "testing port 9024... Mapping does not match 9022. Mapping is 9088", I ran a tcpdump on the 3CX box and analyzed it with wireshark. Here is what I see:
3cx server sends out packet on port 9022 with the same "Message Transaction ID" as the next packet on port 9024, the sonicwall sends both of these packets out, and two responses come back for that exact "Message Transaction ID" but both have the same port 9022 and then the 3cX firewall checker shows the mapping error above.
Troubleshooting points to the firewall... however... isn't the 3CX server generating the "Message Transaction ID"? Its easy to say replace the firewall but its hard to dispute the fact that the message transaction ID is being generate on the 3CX box, the sonicwall is going to forward that packet the way it is so how could it possibly be the firewall causing this?
Thanks!
Dave
