Information about the Contact header can be found in sections 8.1.1.8, 20.10 of. We tried to wireshark the PBX to see what happens and it seems that there is some port translation problems, like the Audio streams don't get into the proper ports on the PBX and vice-versa. Contact: < sip: grgw0.pstn > Due to the bug in the XTM SIP ALG, the contact field comes through like this: Contact: < > This is a known and outstanding issue with the SIP ALG for Watchguard who are currently tracking it here. I tried to port forward the appropriate ports (5060-5065) and I also tried to use a SIP Proxy (which was a recommandation from watchguard tutorials) without any success. We have a Watchguard X750 that acts as our firewall and Multi-WAN gateway. Our advice is to always disable Router or Firewall ‘SIP ALG’ before you begin to open ports on your network security settings, if your Router or Firewall don’t have any disabling for SIP ALG choices we strongly advise you to contact your Router or Firewall technical support and let them do the work they are expert on this matter. I looked into this problem and it seems it is related to the firewall and NAT'ing. With the PBX correctly configured, the line registers, can call out, and receive calls, but there is absolutely no audio on both ways. We bought a VOIP line in the intention to use it on our SIP gateway in the PBX. Fill in 3CXPorts as the Name for the Policy Template. As a Policy Type select Custom and click Add. The default user is admin and the default pass is password. These are all on our internal network so everything worls well. Im wondering if anyone can shed any light on an issue I am having. After setting up the static NAT, a Firewall Policy must be configured: Navigate under Firebox Firewall Firewall Policies and click Add Policy.
We have a Panasonic KX-TDE100 PBX on our network working well as of now with phones, ip phones and some sip phones.
0 kommentar(er)
