Hi, After spending some time trying to get a DG-104S working behind NAT, I finally found the problem. I made the incorrect assumption that nat=yes in mgcp.conf works just like sip.conf. The channels within a gateway are treated more closely to zap channels than sip channels (from a .conf standpoint). What this means is that you have to put nat=yes BEFORE any subchannel definitions: This works: nat=yes line => aaln/1 line => aaln/2 line => aaln/3 line => aaln/4 This doesn't: line => aaln/1 line => aaln/2 line => aaln/3 line => aaln/4 nat=yes This makes sense if lines were treated as individual channels through NAT, but they aren't. NAT capability is dictated by the Gateway itself, and not each endpoint/subchannel. I hope this saves somebody some time. -wade
Hello Wade: There is MGCP firmware available too which appears to help in NAT mode. I have been playing around with these CPG for quite a few months now. I have been able to get them to work only with G711 codecs. I was unable to create a coding profile to work successfully with either G723 and G729 codecs. Have you tried to use these codecs on the DG104S ??? Maybe we exchange some notes on this. Ish --__--__-- Message: 8 From: "Wade Weppler" <weppler@wwworks-inc.com> To: <asterisk-users@lists.digium.com> Date: Wed, 30 Jul 2003 15:09:35 -0400 Subject: [Asterisk-Users] MGCP behind NAT Reply-To: asterisk-users@lists.digium.com Hi, After spending some time trying to get a DG-104S working behind NAT, I finally found the problem. I made the incorrect assumption that nat=yes in mgcp.conf works just like sip.conf. The channels within a gateway are treated more closely to zap channels than sip channels (from a .conf standpoint). What this means is that you have to put nat=yes BEFORE any subchannel definitions: This works: nat=yes line => aaln/1 line => aaln/2 line => aaln/3 line => aaln/4 This doesn't: line => aaln/1 line => aaln/2 line => aaln/3 line => aaln/4 nat=yes This makes sense if lines were treated as individual channels through NAT, but they aren't. NAT capability is dictated by the Gateway itself, and not each endpoint/subchannel. I hope this saves somebody some time. -wade
> From: "Humberto Atristain" <hatristain@megahospedaje.com> > To: <asterisk-users@lists.digium.com> > Subject: RE: [Asterisk-Users] MGCP behind NAT > Date: Wed, 30 Jul 2003 19:07:40 -0500 > Reply-To: asterisk-users@lists.digium.com > > My trouble is that the MGCP devices lost the connection with the > asterisk > > > My gateways are ASKEY MGCP > > Any comments? > > Humberto >If the gateways are losing the connection intermittently, could the NAT be timing out the bindings? Seen a problem where you could not ring the gateway but could get dialtone and firewall was the problem. Someone correct me if I'm wrong, but * does not use AUEP to check gateway status regularly to keep the bindings active darren --- Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.504 / Virus Database: 302 - Release Date: 7/24/03