You need to make calls and watch your states and firewall logs and see how things are trying to connect. More than one device could be done by expanding the destination or by creating rules for each client device. In this case this is a single ATA feeding a couple of phones in a small office. It is hit and miss whether the calls connect to the carrier or SIP server for RTP. Provider SIP on top and the carrier they are using as the last two rules. But you can see that the carrier IP's have a separate rule but identical to the provider. In this picture there is no traffic as they just moved and we have yet to plug in the phones. I get weird private space IP's in my call logs sometimes.īuild an incoming firewall rule on your WAN that points to your client device(s) No port forward! Just a rule(s). We had a customer using Zoiper recently and when we looked at the SIP invites it was sending some random private IP to connect to with RTP. But I have never failed to get a VOIP system to said in VoIP phones that will not register behind a PFsense firewall:Ĭan the remote end hear you when you are able to make a call? then finally SIProxd until I get an unknown SIP provider working. SIProxd however gives a little priority apparently. But everywhere else just need the incoming WAN rules. Then they changed a few things and it became unnecessary. You have to play and experiment sometimes. Not originally designed to be behind NAT. VOIP was not originally designed for residential service. Companies now do things just different enough to avoid the same fate.Īlso. Keep in mind that companies are still trying to avoid what happened to Vonage back in the day. Some *** VoIP insists on using a fixed source port, Generally speaking you should not need to do anything special for internal phones connecting an external PBX. Said in VoIP phones that will not register behind a PFsense firewall:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |