see below
I tried to call 98013356 from the following phone (from mgcp.conf)
[iptlf03]
host = 192.168.33.3
context = default
inbanddtmf = 1
callerid = 22545062
line => aaln/1
Console output:
== Spawn extension (capiring, 9988001133335566, 1) exited non-zero on
'MGCP/aaln/1@iptlf03-1'
-- MGCP mgcp_hangup(MGCP/aaln/1@iptlf03-1) on aaln/1@iptlf03
-- Delete connection 4 aaln/1@iptlf03-1 with new mode: recvonly on callid:
5a4b82ad79f47a70
-- MGCP Asked to indicate tone: on aaln/1@iptlf03-1 in cxmode: recvonly
-- MGCP mgcp_hangup(MGCP/aaln/1@iptlf03-1) on aaln/1@iptlf03 set vmwi(-)
-- MGCP Asked to indicate tone: vmwi(-) on aaln/1@iptlf03-1 in cxmode:
inactive
NOTICE[49156]: File chan_capi.c, Line 1435 (capi_handle_msg): CONNECT_IND
ID=002 #0x08a7 LEN=0045
--
Roy Sigurd Karlsbakk, Datavaktmester
ProntoTV AS - http://www.pronto.tv/
Tel: +47 9801 3356
Computers are like air conditioners.
They stop working when you open Windows.
I also have had some trouble with the mgcp module.
To make it work with the phones we have here I had to tweek a line in
chan_mgcp.c and add the string NCS 1.0 read to the protocol label:
snprintf(req->header[req->headers], sizeof(req->data) -
req->len,
"%s %d %s@%s MGCP 1.0 NCS 1.0\r\n", verb, oseq, p->name,
p->parent->name);
That got things working, but when I run the voice mail demo, and I hang
up the mgcp connection remains up until a ICMP timeout occurs. Then
the call resets.
Julian Green
Roy Sigurd Karlsbakk wrote:
>see below
>I tried to call 98013356 from the following phone (from mgcp.conf)
>
>[iptlf03]
>host = 192.168.33.3
>context = default
>inbanddtmf = 1
>callerid = 22545062
>line => aaln/1
>
>Console output:
>
> == Spawn extension (capiring, 9988001133335566, 1) exited non-zero on
>'MGCP/aaln/1@iptlf03-1'
> -- MGCP mgcp_hangup(MGCP/aaln/1@iptlf03-1) on aaln/1@iptlf03
> -- Delete connection 4 aaln/1@iptlf03-1 with new mode: recvonly on
callid:
>5a4b82ad79f47a70
> -- MGCP Asked to indicate tone: on aaln/1@iptlf03-1 in cxmode:
recvonly
> -- MGCP mgcp_hangup(MGCP/aaln/1@iptlf03-1) on aaln/1@iptlf03 set vmwi(-)
> -- MGCP Asked to indicate tone: vmwi(-) on aaln/1@iptlf03-1 in cxmode:
>inactive
>NOTICE[49156]: File chan_capi.c, Line 1435 (capi_handle_msg): CONNECT_IND
>ID=002 #0x08a7 LEN=0045
>
>
>
On Thu, 2003-04-24 at 04:16, Roy Sigurd Karlsbakk wrote:> see below > I tried to call 98013356 from the following phone (from mgcp.conf) > > [iptlf03] > host = 192.168.33.3 > context = default > inbanddtmf = 1 > callerid = 22545062 > line => aaln/1 > > Console output:> == Spawn extension (capiring, 9988001133335566, 1) exited non-zero onTurn off inbanddtmf. Looks like your device is sending the out of band mgcp messages for the tones. No need for inbanddtmf then. I guess we could disable the forwarding of mgcp dtmf messages if inbanddtmf=1. This shows up because inbanddtmf was never hooked up to any processing before. --Karl> 'MGCP/aaln/1@iptlf03-1' > -- MGCP mgcp_hangup(MGCP/aaln/1@iptlf03-1) on aaln/1@iptlf03 > -- Delete connection 4 aaln/1@iptlf03-1 with new mode: recvonly on callid: > 5a4b82ad79f47a70 > -- MGCP Asked to indicate tone: on aaln/1@iptlf03-1 in cxmode: recvonly > -- MGCP mgcp_hangup(MGCP/aaln/1@iptlf03-1) on aaln/1@iptlf03 set vmwi(-) > -- MGCP Asked to indicate tone: vmwi(-) on aaln/1@iptlf03-1 in cxmode: > inactive > NOTICE[49156]: File chan_capi.c, Line 1435 (capi_handle_msg): CONNECT_IND > ID=002 #0x08a7 LEN=0045-- Karl Putland <karl@putland.linux-site.net>
On Thu, 2003-04-24 at 04:56, julian green wrote:> I also have had some trouble with the mgcp module. > > To make it work with the phones we have here I had to tweek a line in > chan_mgcp.c and add the string NCS 1.0 read to the protocol label: >Is there a graceful way to handle this in a generic manner? Should we add a config option mgcpversion = MGCP 1.0 NCS 1.0 That defaults to "MGCP 1.0"> snprintf(req->header[req->headers], sizeof(req->data) - req->len, > "%s %d %s@%s MGCP 1.0 NCS 1.0\r\n", verb, oseq, p->name, p->parent->name); > > That got things working, but when I run the voice mail demo, and I hang > up the mgcp connection remains up until a ICMP timeout occurs. Then > the call resets. >Do you see chan_mgcp observing "hu"? I need a little more information to diagnose the issue. --Karl -- Karl Putland <karl@putland.linux-site.net>