<br><br><div class="gmail_quote">On Thu, Oct 28, 2010 at 9:54 PM, Steve Totaro <span dir="ltr"><<a href="mailto:stotaro@totarotechnologies.com">stotaro@totarotechnologies.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br><br><div class="gmail_quote"><div class="im">On Fri, Oct 29, 2010 at 4:21 AM, Baha @ SH <span dir="ltr"><<a href="mailto:info@saudihome.com" target="_blank">info@saudihome.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi<br>
I have asterisk 1.4<br>
I want to make a MGCP trunk as a client to connect to a provider who is<br>
using MGCP protocol, he provided me with user & password,<br>
<br>
I tried a custom trunk:<br>
<br>
MGCP/$OUTNUM$@<a href="http://user:password@66.152.163.106:4000" target="_blank">user:password@66.152.163.106:4000</a><br>
<br>
Not seems to help,<br>
<br>
Any suggestions plz?<br>
<br></blockquote></div><div><br>In my research to try to get MEGACO protocol to work (they are very similar) I remember stumbling onto this information. I am not sure where or if it is even correct, it has been so long.<br>
<br>
MGCP is supported but only the MGCP phones, not the entire protocol. <br><br>I tried to get full support for MEGCO because many NEC systems at that time used it for VoIP and the only other way to interface with an NEC IPK was via TDM, either POTS or T1, which are and especially were, WAY too expensive.<br>
<br>I am out of date with NEC, I haven't touched one in years, but way back then, they were in the top three of PBX market share.<br><br>You can probably google my name and MEGACO and you may find the info you are looking for.<br>
<br>Thanks,<br>Steve Totaro <br></div></div><br>
</blockquote></div><br>Straight from the mouth of BKW three years ago. <br><br><a href="http://www.spinics.net/lists/asterisk/msg76756.html">http://www.spinics.net/lists/asterisk/msg76756.html</a><br>