Correct
On Jul 20, 2012 4:30 PM, "Kurt Albershardt" wrote:
> Got it.
>
> I assume inbound RTSP gets negotiated during the SIP call setup and that
> sipXbridge sends a packet to dynamically open the needed port on a per-call
> basis?
>
>
>
> On Jul 20, 2012, at 14:21 , Tony Graziano wrote:
>
> thi
Got it.
I assume inbound RTSP gets negotiated during the SIP call setup and that
sipXbridge sends a packet to dynamically open the needed port on a per-call
basis?
On Jul 20, 2012, at 14:21 , Tony Graziano wrote:
> this is what sipxbridge uses for outbound itsp calls and to support remote
>
this is what sipxbridge uses for outbound itsp calls and to support remote
users. IF YOU ARE NOT SUPPORTING REMOTE USERS you do not typically have to
NAT this OR port 5060. Outbound traffic is typically allowed or not allowd
by firewalls, we are talking about inbound traffic here.
On Fri, Jul 20,
Thanks!
On Jul 20, 2012, at 13:12 , Bryan Anderson wrote:
> I only bring through the 3-31000 range to our systems. Based of what is
> listed under System > Server > "Server" > NAT > "Show Advanced Settings"
>
> -Bryan Anderson
>
>
>
>
> On Fri, Jul 20, 2012 at 11:51 AM, Kurt Albersh
I only bring through the 3-31000 range to our systems. Based of what
is listed under System > Server > "Server" > NAT > "Show Advanced Settings"
-Bryan Anderson
On Fri, Jul 20, 2012 at 11:51 AM, Kurt Albershardt wrote:
> Wiki mentions 3-31000 for sipXrelay but I've seen mentions of
Wiki mentions 3-31000 for sipXrelay but I've seen mentions of 15000-15500
in a number of forum posts.
What do I need to allow for sipXbridge <-> ITSP behind NAT (with external
static IP stated, not using a STUN server)?
thanks~
___
sipx-us