If you nail up a VPN before starting a softphone you could go through the tunnel and avoid this.
If you have a hard phone you'll need a hardware VPN though. Or, have the provider put the DSL device in pass-thru (bridge) mode and put your own firewall behind it. Mike On Thu, Sep 2, 2010 at 6:21 AM, Tony Graziano <tgrazi...@myitdepartment.net>wrote: > You bbox thing has a sip proxy helper that you should disable. If you are > using xlite you should ensure "send local or internal address" is chosen. > If they won't disable it get another provider. > > Putting sipx in a dmz WILL NOT CHANGE ANYTHING. The problem is at the far > end. > > > ============================ > Tony Graziano, Manager > Telephone: 434.984.8430 > Fax: 434.984.8431 > > Email: tgrazi...@myitdepartment.net > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > Fax: 434.984.8427 > > Helpdesk Contract Customers: > http://www.myitdepartment.net/gethelp/ > > ----- Original Message ----- > From: sipx-users-boun...@list.sipfoundry.org > <sipx-users-boun...@list.sipfoundry.org> > To: sipx-users@list.sipfoundry.org <sipx-users@list.sipfoundry.org> > Sent: Thu Sep 02 03:47:31 2010 > Subject: [sipx-users] NAT and remote worker one way audio > > > Content-Type: text/plain; > charset="utf-8" > Content-Transfer-Encoding: 8bit > Organization: SipXecs Forum > X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <51442> > Message-ID: <c8f2.4c7f5...@forum.sipfoundry.org> > > > > Hi all, > > As testing sipxecs, I read lot of docs about nat, remote > workers, remote workers behind nat, and firewall. > > Currently all is working great, except for one case, remote > workers, behind the Belgacom (Belgium ADSL provider) and the > Bbox-2 (a Sagem mailto:f...@st 3464, running a customized > version of Jungo Openrg) more info here : > http://wiki.yobi.be/wiki/Modem_BBox-2 > > All remote phone, behind this box, register to sipxecs (also > behind nat) this way : > <sip:mailto:3...@public_ip:60830;x-sipX-nonat> > > Another phone behind a D-Link 615 (with SIP ALG disabled) > register this way : > <sip:mailto:3...@public_ip:5060;x-sipX-privcontact=PRIVATE_IP%3A5060> > which is good. (no communication problem with this setup) > > So when I call from behind bbox-2 to internal -> everything > is OK > >From internal to remote behind bbox-2, I can't hear the > remote worker. > > The b-box2 come with a kind of sip client, you can register > to provider like 3starsnet.com or nomado.eu or I-talk from > belgacom (info here : > http://www.3starsnet.com/support/pdf/Bbox2_general_config3StarsNet.pdf > and > http://www.3starsnet.com/support/pdf/Bbox2_config_line_3starsNet.pdf) > so theoretically I could use a classical phone behind, but I > want to use a X-lite, a Polycom, a Grandstream ... > > Unfortunately, there is no way to disable the SIP_ALG > helper, and changing the config, can be done, but the box is > controlled by the provider and the provider can change the > config remotely or upload new firmware (and of course when > calling the support, they said that everything is ok with > the box and this is because we are using LINUX (true). > > So I don't know what I can do to hear remote workers ... put > sipx in DMZ with public IP ? > > One note, this works with Axon (www.nch.com) but the Axon is > in the DMZ with public IP. > > Regards, > > > _______________________________________________ > sipx-users mailing list > sipx-users@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > _______________________________________________ > sipx-users mailing list > sipx-users@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- There are 10 kinds of people in this world, those who understand binary and those who don't. mpic...@gmail.com blog: http://www.sipxecs.info call: sip:mpic...@sipxecs.info <sip%3ampic...@sipxecs.info>
_______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
