Internet <-> VDSL <-> WxC MP264 router with DMZ enabled <-> Desktop PC running Wireshark and 2x bridged LAN for testing this issue <-> pfSense Firewall <-> Asterisk Box
Using OpenVFX.
Starting today, I'm getting this weird behaviour where the MP264 appears not to be passing RTP packets, and despite its VoIP not being provisioned, it sends out bad REGISTER packets to pan.wxnz.net, who then replies with "404 not found" which ends up going to my Asterisk box - these keep coming in:
'CE{<9SwXSIP/2.0 404 Not found
From: <sip:0000000001@pan.wxnz.net>;tag=826220-3a1c9f21-13c4-50029-1e60c35-3e2c1861-1e60c35
To: <sip:0000000001@pan.wxnz.net>;tag=1528941087-1415929491340
Call-ID: 834270-3a1c9f21-13c4-50029-1e60c35-636e1493-1e60c35
CSeq: 1 REGISTER
Via: SIP/2.0/UDP 192.168.3.3:5060;branch=z9hG4bK-1e60c35-6a9fb008-51d2e9f;rport=5060
Content-Length: 0
I think this is happening because where I'm packet-sniffing to try to fault-find this, I'm seeing "404 Not Found" replies continually come in from pan.wxnz.net to the Asterisk box despite no outbound traffic, ie even when Asterisk is stopped. This issue persists across reboots. This is in addition to an issue I sporadically have where the MP264 stops forwarding SIP (5060) traffic too, although that is usually solved with a reboot.
I'm trying to diagnose the issue using a remote extension as follows:
Blink softphone and Wireshark on laptop <-> 3G* <-> Internet <-> VDSL <-> WxC MP264 router with DMZ enabled <-> Wireshark <-> pfSense Firewall <-> Asterisk Box
* same on either 3G and via other the UFB internet connection at my office - both used to work until today.
I see the RTP packets going out fine on 3G and all specified vs actual ports look correct, but those same RTP packets are *not* seen on my home network at the other end - unexpected, as with DMZ switched on everything should be forwarded from the MP264 to the pfSense firewall so the intercepting PC running Wireshark should be seeing something...
Any ideas? Any help much appreciated.
Thanks,
Andrew

