[Asterisk-Users] new mgcp patch errors

Karl Putland karl at putland.linux-site.net
Thu Apr 24 06:41:26 MST 2003


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 on 

Turn 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 at iptlf03-1'
>     -- MGCP mgcp_hangup(MGCP/aaln/1 at iptlf03-1) on aaln/1 at iptlf03
>     -- Delete connection 4 aaln/1 at iptlf03-1 with new mode: recvonly on callid: 
> 5a4b82ad79f47a70
>     -- MGCP Asked to indicate tone:  on  aaln/1 at iptlf03-1 in cxmode: recvonly
>     -- MGCP mgcp_hangup(MGCP/aaln/1 at iptlf03-1) on aaln/1 at iptlf03 set vmwi(-)
>     -- MGCP Asked to indicate tone: vmwi(-) on  aaln/1 at 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 at putland.linux-site.net>




More information about the asterisk-users mailing list