VoIP provider has no upstream SIP server? Unified Communications by Frontier
pzanga last edited by
I'm hoping I can get some help with this issue here. I'm not sure if this is just due to ignorance on my part or if the people I am talking to don't understand what I am asking for.
We are getting ready to implement a new VoIP system at my work and I am planning on using the traffic shaper to prioritize the VoIP traffic. Trying to follow best practice as per the documentation I requested the IP address(es) for the PBX/SIP trunks (to plug into the wizard) and have been told essentially that doesn't apply to their system. The system is Unified Communications by Frontier (UCF). What I've been told is this system is cloud based, it's not like a traditional SIP system, there is no specific IP addresses we connect to, etc.
Maybe this reflects a lack of knowledge on my part, but even if cloud based wouldn't there be a specific range or pool of IP addresses that traffic is flowing to/from upstream? Adding to my confusion is the fact that the ports they told me I need to allow include SIP ports:
Allow TCP/UDP ports 5060, 5061, and 5068 (for SIP)
Allow UDP ports 8500–59999 (for RTP)
Allow UDP port 123 (for NTP)
Allow TCP port 80 (for HTTP)
Allow TCP port 2208 (for HTTP: Business Communicator)
Allow TCP port 443–450 (for HTTP)
Does anyone else have experience with this or a similar system? Does what they are telling me make sense? And, on a related note, if I don't have a fixed set of upstream IPs to use do I need to open the above ports to the internet i.e. pass any traffic destined for those ports?
chpalmer last edited by
My provider used to source RTP directly from the carrier servers (not their own) but always had their own SIP.. (has since changed)
Depending on what you have on your end.. Server or Clients.. Look to see what your clients are connecting to. If you have a local on site SIP server it will still act as a client to go out to the providers server generally.
Look at connection states to see what things are trying to connect to. Do you have DNS of their stuff? sip.frontier.com?? ect..??
Outbound everything is allowed by default. In some cases the provider does want inbound NAT (I don't usually agree with) and in some cases you will only need firewall rules to allow the traffic to the client.
Maybe the Siproxd package is a good fit for you?