I tend to think this is a bug. Can someone using a bria 3.0 confirm they get
the wrong firewall setting in the gui?

On Thu, May 6, 2010 at 4:23 PM, Tony Graziano
<[email protected]>wrote:

>
>
> On Thu, May 6, 2010 at 4:12 PM, JOLY, ROBERT (ROBERT) <[email protected]>wrote:
>
>> > I have been troubleshooting some remote issues with Bria 3.0
>> > for =remote users. While doing so I noticed an "oddity".
>> >
>> > proxies:proxy0:ice_enabled="false"
>> > proxies:proxy0:outbound_proxy=""
>> > proxies:proxy0:override_sip_listen_port="false"
>> > proxies:proxy0:override_stun_server="false"
>> > proxies:proxy0:port_range_enable="true" <<CHANGED
>> > proxies:proxy0:port_range_min="30000" <<CHANGED
>> > proxies:proxy0:port_range_max="31000" <<CHANGED
>> > proxies:proxy0:send_internal_ip_address="true"
>> > proxies:proxy0:send_sip_keep_alive_messages="true"
>> > proxies:proxy0:sip_tcp_port_keep_alive_time_in_seconds="30"
>> > proxies:proxy0:sip_udp_port_keep_alive_time_in_seconds="30"
>> > proxies:proxy0:stun_server=""
>> > proxies:proxy0:turn_enabled="false"
>> > proxies:proxy0:turn_server=""
>> > proxies:proxy0:turn_domain=""
>> > proxies:proxy0:turn_use_sip_credentials="true"
>> > proxies:proxy0:turn_username=""
>> > proxies:proxy0:turn_password=""
>> >
>> > Even with all the other items set to default, with STUN, ICE,
>> > etc. disabled, the config generated looks correct BUT the
>> > Bria 3.0 always displays it as if it was not. So I remove the
>> > accounts, logout and login to get the new profile and still
>> > get "Auto Detect". Is there not a parameter to make it say
>> > "None use local ip" in the bria parameters?
>>
>> I know the name of the parameter in the client's account management GUI
>> but I do not know what it translates to in Bria-profile-speak but I would
>> guess it is "roxies:proxy0:turn_enabled".  From the GUI, it is "SIP
>> Account->Topology->Use Local IP Address".
>> >
>>
> Yes, all the INI file settings speak to that, but the GUI belies it.
>
>
>> > I'm somewhat confused why I have some remote users
>> > registering with a real IP and others showing their private
>> > ip as "private-contact" since they are all configured the same.
>>
>> Are they in different remote sites?  Is it possible that different remote
>> sites have different remote NAT/firewalls that may be doing NAT
>> compensation/SIP ALG.  In your case, the easiest way to tell is to sniff the
>> REGISTER right out of your PC and compare it to the one arriving at sipXecs.
>>  If they have SIP deltas then your remote NAT is playing tricks on you.
>>
>> There is no SIP ALG or ALG in the way. I just starting noticing the packet
> captures were showing media on ports above 50000 which led me to force the
> RTP settings down to specify 30000 - 31000 (which I don;t think should be
> necessary.
>
> What Ive noticed is between two different systems...
>
> polycom <>pfsense <> internet <> pfsense <> bria
>
> polycom <>pfsense <> internet <> pfsense
>                                                          remote user <>
> bria
>
> broken audio via sip uri dialing
>
>
> What has worked is...
>
> bria <>pfsense <> internet <> pfsense
>                                                          remote user <>
> bria
>
>
> polycom <>pfsense <> internet <> pfsense <> polycom
> (dialing with site-to-site) no problem
>
> bria <>pfsense <> internet <> remote user <> bria
>
> as well two remote users can call each other on the same sipx system.
>
>
>
> But in all this the logic of the bria gui and ini has me stopped wondering
> if I cannot get the setting or GUI to show properly how can I really
> actively troubleshoot it.
>
> >
>> > Does anyone have a link to the parameters for the Counterpath
>> > provisioning function?
>> >
>> > I would assume if something were missing, manually adding
>> > that with the "value" to the line properties file generator
>> > sipx uses would work, but I am trying to understand if a
>> > parameter is missing or not.
>> >
>> > Has anyone else seen this?
>> >
>> >
>> > --
>> > ======================
>> > Tony Graziano, Manager
>> > Telephone: 434.984.8430
>> > sip: [email protected]
>> > Fax: 434.984.8431
>> >
>> > Email: [email protected]
>> >
>> > LAN/Telephony/Security and Control Systems Helpdesk:
>> > Telephone: 434.984.8426
>> > sip: [email protected]
>> > Fax: 434.984.8427
>> >
>> > Helpdesk Contract Customers:
>> > http://www.myitdepartment.net/gethelp/
>> >
>> > Why do mathematicians always confuse Halloween and Christmas?
>> > Because 31 Oct = 25 Dec.
>> >
>> >
>> >
>>
>
>
>
> --
> ======================
> Tony Graziano, Manager
> Telephone: 434.984.8430
> sip: [email protected]
> Fax: 434.984.8431
>
> Email: [email protected]
>
> LAN/Telephony/Security and Control Systems Helpdesk:
> Telephone: 434.984.8426
> sip: [email protected]
> Fax: 434.984.8427
>
> Helpdesk Contract Customers:
> http://www.myitdepartment.net/gethelp/
>
> Why do mathematicians always confuse Halloween and Christmas?
> Because 31 Oct = 25 Dec.
>
>


-- 
======================
Tony Graziano, Manager
Telephone: 434.984.8430
sip: [email protected]
Fax: 434.984.8431

Email: [email protected]

LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: [email protected]
Fax: 434.984.8427

Helpdesk Contract Customers:
http://www.myitdepartment.net/gethelp/

Why do mathematicians always confuse Halloween and Christmas?
Because 31 Oct = 25 Dec.
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to