I have my SBC configured to listen on port 5060 and a couple other non-standard ports. When a customer ISP or firewall ALG gets in the way I configure them to use the other ports. It is pretty easy to add additional ports to the sip-interface of your acme packet SBC -Matt -- Matthew S. Crocker President Crocker Communications, Inc. PO BOX 710 Greenfield, MA 01302-0710 E: matthew at crocker.com P: (413) 746-2760 F: (413) 746-3704 W: http://www.crocker.com On Nov 21, 2013, at 12:32 PM, Matt Yaklin <myaklin at g4.net> wrote:
On Thu, 21 Nov 2013, Jay Hennigan wrote:
On 11/21/13 5:36 AM, J. Oquendo wrote:
"Getting the carrier..." We try not to inherit any of the network unless we are managing it. This frees us from any liabilities associated with say a Doctors office doing some whacky VPN to a hospital or other. Would take us too long to perform a network assessment, and make sense of a client's business needs, especially for free.
It's a balancing act, to be sure. Your customer will of course say that the rest of the Internet works fine, it's just your VoIP service that is failing. "I can get to Google and Yahoo, so there's nothing wrong with my Internet, but your phone doesn't work."
For one-off remote phones, setting SIP transport to TCP is often a good workaround by the way.
Will tunneling the sip/rtp packets be more common in the near future for SIP phone providers?
matt
-- Jay Hennigan - CCIE #7880 - Network Engineering - jay at impulse.net Impulse Internet Service - http://www.impulse.net/ Your local telephone and internet company - 805 884-6323 - WB6RDV _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops