- Joined
- Feb 28, 2019
- Messages
- 4
- Reaction score
- 0
Hello everyone,
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"
Troubleshooting points to the firewall... however... isn't the 3CX server generating the "Message Transaction ID"?
Thanks!
Dave
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"
Troubleshooting points to the firewall... however... isn't the 3CX server generating the "Message Transaction ID"?
Thanks!
Dave