Summary:	ASTERISK-01220: [feature request] for MGCP and RADVISION STACK
Reporter:	duanecox (duanecox)	Labels:
Date Opened:	2004-03-16 11:19:28.000-0600	Date Closed:	2004-09-25 02:49:39
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	I had trouble getting Asterisk to communicate with my end devices using MGCP.  These end devices are referred to as an LMG by Wave7Optics (www.wave7optics.com)  They are a FTTH end user device, with up to 4 analog ports. The problem with the LMG is that they use an out of house MGCP STACK from RADVISION.  The RADVISION STACK on this devices REQUIRES the MGCP endpoint message to be in the format of 'aaln/#@[IP.IP.IP.IP]'   Since Asterisk sends the packet in the format of 'aaln/#@IP.IP.IP.IP'  my device would always report with 'endpoint unknown'  My quick hack was to alter the chan_mgcp.c file as follows:  (line 1366 in current CVS) snprintf(req->header[req->headers], sizeof(req->data) - req->len, "%s %d %s@[%s] MGCP 1.0\r\n", verb, oseq, p->name, p->parent->name); This is a dirty fix for me, as it will proably break MGCP communication with other devices, but currently I had to test it to see if it resolved my problem, which it does. I tried to format my extensions.conf file so that it would send the endpoint packet as such: exten => 2173799999,1,Dial(MGCP/aaln/1@[10.252.240.2]) But that did not work. I am not a c programer, but would like to see if someone would come up with a feature or solution, as from what I hear, the RADVISION MGCP stack is quite commonly used, and Asterisk could benefit from this!
Comments:	By: duanecox (duanecox) 2004-03-17 23:00:23.000-0600 fixed in patch chan_mgcp.c.diff.4 http://bugs.digium.com/bug_view_page.php?bug_id=0001114 By: Mark Spencer (markster) 2004-04-15 10:29:09 Fixed in CVS