#Setup firewall for onsip software

Again: this stuff isn't magic, companies just neglect providing the necessary details due to laziness.Īs an alternate solution, assuming both you and the other person are using software on PCs or Macs, you might consider Discord, TeamSpeak, Mumble, or Skype. That's really your only option if providers or vendors don't disclose the necessary bits. Packet captures make figuring all of this out a lot easier, I'm sorry to say. It never ceases to amaze me how in the consumer world, VoIP is advertised as this 'magic solution' with very little details given as to how it works. Dialogic/Excel media gateway) and VoIP (ex. My familiarity with VoIP is with enterprise-grade stuff for both TDM/POTS (ex. In this scenario, there's nothing you need to forward statically - it all works dynamically. Whether or not the client supports UPnP, again, is dependent upon what the documentation says.

#Setup firewall for onsip Pc

Possibly the VoIP client supports UPnP (is this enabled in your router? Port Forwarding -> UPnP/NAT-PMP), in which case the VoIP client can dynamically add port forwardings on the router, forwarded to your PC (and dynamically remove them). Once you figure that out, you should be able to forward that port number (or range), UDP protocol (TCP is very very unlikely I've never seen TCP-based RTP used), to your PC and it should begin working. So both solutions are awful - instead, the proper thing is to know what RTP port range is set in your VoIP client. A 'cleaner' solution might be to set the DMZ to your PC, but that introduces massive security concerns, since now any non-forwarded port effectively ends up getting forwarded to your PC, which means you end up needing a firewall on your PC.

It would cause a lot of chaos on the network, and is quite overkill. I can assure you this is absolutely, hands down, a very VERY bad thing to do (they really should remove that clause). There is a recommendation there to forward both TCP and UDP 10000-65535 to your PC. That should allow the SIP portion to work.Īs for RTP, there isn't a 'standard' port range - instead, the port range depends on what's configured in the software client. Start by forwarding both TCP/UDP 5060-5080 (I don't know why they have such a large range SIP normally only requires a single port) to your PC.

Regarding actual ports, for both SIP and RTP, there's this: Finding out if they use a SIP server/gateway is important - seems to imply they do. In that case, the only option I can think of is to rely on any documentation the company provides for their software/product. VoIP is a technology, not 'a program' or 'a service', so how software designers choose to implement it is up to them. I would strongly suggest asking for help/support from the company or individuals who maintain the software you're using. TL DR - It all depends on what software you're using. SIP commonly uses port 5060, often both TCP and UDP (yes really, both!), but be aware that's for SIP, not for the actual VoIP payload/communication. You didn't mention if you're using SIP (this isn't VoIP per se it's a related protocol that helps get a VoIP session up/working) or not, by the way. If there's a centralised VoIP distribution server involved (commonly an intermediary SIP server) - again, the communication software needs to provide insights into this - then ideally you shouldn't need this. Port forwarding is only necessary if there isn't a centralised server involved and the VoIP software is doing true P2P (peer-to-peer), where you (client) are literally connecting to him (server), and vice versa (reverse client/server terms). If the software documentation doesn't disclose this, then you're best off using different software - this stuff isn't 'magic'. The software needs to disclose exactly what ports (and protocols, though for VoIP it's commonly UDP) are used. The best way to troubleshoot this problem is to read details about the communication software you're both using.