Why does pfSense NAT re-write my SIP packet and mess up my registration?
torontob last edited by
I have NAT forwarded 5060 TCP/UDP and 10000-20000 UDP to the Asterisk server that is setting as 192.168..0.5 and I do get a registration but it shows my pfsense IP as the registration IP rather than the client's public IP which comes through the WAN interface.
SIP Packet Example:
--- Transmitting (NAT) to 192.168.0.1:6258 ---> SIP/2.0 200 OK Via: SIP/2.0/UDP 188.8.131.52;branch=z9hG4bK-d87543-855335637-1--d87543-;received=192.168.0.1;rport=6258 From: 9999-Prox106-Ast16<sip:firstname.lastname@example.org>;tag=821bsd37 To: 9999-Prox106-Ast16<sip:email@example.com>;tag=as7d4bdsdj37 Call-ID: f857e8783453453</sip:firstname.lastname@example.org></sip:email@example.com>
sip show peers:
pbx*CLI> sip show peers Name/username Host Dyn Nat ACL Port Status 5555/5555 192.168.0.1 D N A 5060 OK (13 ms)
In sip_nat.conf I have:
I do not have Siproxd installed as I understand it does just the reverse of what I need meaning it connects clients part of the pfsense to connect to outside world Asterisk rather than connecting outside world clients into the pfsense Asterisk.
Any pointers are much appreciated.