My trouble is that the MGCP devices lost the connection with the asterisk
My gateways are ASKEY MGCP Any comments? Humberto -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Mi�rcoles, 30 de Julio de 2003 05:07 p.m. To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: [Asterisk-Users] MGCP behind NAT 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" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Date: Wed, 30 Jul 2003 15:09:35 -0400 Subject: [Asterisk-Users] MGCP behind NAT Reply-To: [EMAIL PROTECTED] 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 _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
