[asterisk-r2] Channels remain in "CLEAR BA" state after hang up
Diego Ocampo
docampo2005 at gmail.com
Tue Dec 1 07:45:17 CST 2009
I have activated call trace, with mfcr2_call_files=yes, mfcr2_logging=all,
mfcr2_logdir=span1 in chan_dahdi.conf and setting verbose and debug level to
333 in asterisk.
The backward call log isn't generated, not until after run the "mfcr2 set
idle" command in asterisk console. But, as I don't have the E1 line all the
time, I have made the test with a crossover cable between "span 1" and "span
2", with same result.
chan_dahdi.conf --> http://pastebin.com/f7e505486
dahdi/system.conf --> http://pastebin.com/f39e15d57
[root at asterisk1 span1]# ls -ltr
total 4
-rw------- 1 asterisk asterisk 0 Dec 1 09:29
chan-32-backward-4-20091201092912.call
-rw------- 1 asterisk asterisk 2995 Dec 1 09:29
chan-1-forward-4-20091201092912.call
[root at asterisk1 span1]# lsof chan-32-backward-4-20091201092912.call
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
asterisk 13557 asterisk 90w REG 8,1 0 9017873
chan-32-backward-4-20091201092912.call
Before run 'mfcr2 set idle':
[root at asterisk1 span1]# cat chan-1-forward-4-20091201092912.call
--> http://pastebin.com/f6c987559
[root at asterisk1 span1]# cat chan-32-backward-4-20091201092912.call
--> http://pastebin.com/f2dfd73b
[root at asterisk1 span1]# tail -f /var/log/asterisk/full | grep chan_dahdi.c
--> http://pastebin.com/f14744a71
Thanks
2009/11/30 Moises Silva <moises.silva at gmail.com>:
> take a call trace, full call trace, search the mailing list archives with
> google about it if you don't know how to take one (or probably the openr2
> guide tells you that)
>
> On Mon, Nov 30, 2009 at 2:31 PM, Diego Ocampo <docampo2005 at gmail.com>
wrote:
>>
>> I compiled the branches/release-1 source, but still having a problem.
>>
>> Thanks.
>>
>> > before doing anything else you should use branches/release-1 and NOT
>> > branches/release-1-dtmf, the DTMF support was already merged into
>> > branches/release-1
>> >
>> > On Mon, Nov 30, 2009 at 10:59 AM, Diego Ocampo <docampo2005 at
>> > gmail.com>wrote:
>> >
>> >> Hello everybody,
>> >>
>> >> First of all, I want to thank for the extraodinary work.
>> >> I'm use the openr2 version 1.3.0, compilied from
>> >> branches/release-1-dtmf, because my provider in Argentina (Global
>> >> Crossing) uses r2-digital-dtmf-dnis configuration.
>> >>
>> >> The library work great, but I have a problem when the caller hang up,
>> >> the channel goes to "CLEAR BA - CLEAR FO" state.
>> >>
>> >> asterisk1*CLI>mfcr2 show channels
>> >> Chan Variant Max ANI Max DNIS ANI First Immediate Accept Tx CAS Rx
>> >> CAS
>> >> 1 AR 10 4 No No IDLE IDLE
>> >> 2 AR 10 4 No No IDLE IDLE
>> >> 3 AR 10 4 No No CLEAR BA
>> >> CLEAR
>> >> FO
>> >> 4 AR 10 4 No No IDLE IDLE
>> >> 5 AR 10 4 No No IDLE IDLE
>> >> 6 AR 10 4 No No IDLE IDLE
>> >> 7 AR 10 4 No No IDLE IDLE
>> >> 8 AR 10 4 No No IDLE IDLE
>> >> 9 AR 10 4 No No IDLE IDLE
>> >> 10 AR 10 4 No No IDLE IDLE
>> >> 11 AR 10 4 No No IDLE IDLE
>> >> 12 AR 10 4 No No IDLE IDLE
>> >>
>> >> Log (chan-3-backward-0-20091128210432.call):
>> >>
>> >> [21:04:32:967] [Thread: 1089317184] [Chan 3] - Call started at Sat Nov
>> >> 28 21:04:32 2009 on chan 3 [openr2 version 1.3.0, revision 273M]
>> >> [21:04:32:967] [Thread: 1089317184] [Chan 3] - Initialized R2 DTMF
>> >> detector
>> >> [21:04:32:967] [Thread: 1089317184] [Chan 3] - CAS Tx >> [SEIZE ACK]
>> >> 0x0C
>> >> [21:04:32:967] [Thread: 1089317184] [Chan 3] - CAS Raw Tx >> 0x0D
>> >> [21:04:33:081] [Thread: 1089317184] [Chan 3] - Got digits 1 of len 1
>> >> [21:04:33:261] [Thread: 1089317184] [Chan 3] - Got digits 5 of len 1
>> >> [21:04:33:461] [Thread: 1089317184] [Chan 3] - Got digits 1 of len 1
>> >> [21:04:33:681] [Thread: 1089317184] [Chan 3] - Got digits 5 of len 1
>> >> [21:04:34:241] [Thread: 1089317184] [Chan 3] - Done with DTMF
detection
>> >> [21:04:34:241] [Thread: 1089317184] [Chan 3] - Attempting to cancel
>> >> timer timer 0
>> >> [21:04:34:241] [Thread: 1089317184] [Chan 3] - Cannot cancel timer 0
>> >> [21:04:34:261] [Thread: 1120618816] [Chan 3] - CAS Tx >> [ANSWER] 0x04
>> >> [21:04:34:261] [Thread: 1120618816] [Chan 3] - CAS Raw Tx >> 0x05
>> >> [21:09:07:770] [Thread: 1120618816] [Chan 3] - Bits changed from 0x00
>> >> to
>> >> 0x08
>> >> [21:09:07:770] [Thread: 1120618816] [Chan 3] - CAS Rx << [CLEAR
>> >> FORWARD]
>> >> 0x08
>> >> [21:09:07:770] [Thread: 1120618816] [Chan 3] - Far end disconnected.
>> >> Reason: Normal Clearing
>> >> [21:09:07:774] [Thread: 1120618816] [Chan 3] - Attempting to cancel
>> >> timer timer 0
>> >> [21:09:07:774] [Thread: 1120618816] [Chan 3] - Cannot cancel timer 0
>> >> [21:09:07:774] [Thread: 1120618816] [Chan 3] - CAS Tx >> [CLEAR BACK]
>> >> 0x0C
>> >> [21:09:07:774] [Thread: 1120618816] [Chan 3] - CAS Raw Tx >> 0x0D
>> >> [21:29:16:592] [Thread: 1120618816] [Chan 3] - Attempting to cancel
>> >> timer timer 0
>> >> [21:29:16:592] [Thread: 1120618816] [Chan 3] - Cannot cancel timer 0
>> >>
>> >> chan_dahdi.conf:
>> >>
>> >> [trunkgroups]
>> >> [channels]
>> >> context=from-pstn
>> >> switchtype=national
>> >> usecallerid=yes
>> >> hidecallerid=no
>> >> callwaiting=yes
>> >> callwaitingcallerid=yes
>> >> threewaycalling=yes
>> >> transfer=yes
>> >> cancallforward=yes
>> >> echocancel=yes
>> >> rxgain=0.0
>> >> txgain=0.0
>> >> immediate=no
>> >>
>> >> resetinterval=never
>> >> context=from-pstn
>> >> group=0
>> >> echocancel=yes
>> >> signalling=mfcr2
>> >> mfcr2_variant=ar
>> >> mfcr2_get_ani_first=no
>> >> mfcr2_max_ani=10
>> >> mfcr2_max_dnis=4
>> >> mfcr2_category=national_subscriber
>> >> mfcr2_mfback_timeout=-1
>> >> mfcr2_metering_pulse_timeout=-1
>> >> mfcr2_dtmf_detection=1
>> >> mfcr2_dtmf_dialing=1
>> >> channel => 1-12
>> >>
>> >> dahdi/system.conf:
>> >> # Span 1: TE4/0/1 "T4XXP (PCI) Card 0 Span 1" (MASTER) HDB3/ RED
>> >> span=1,1,0,cas,hdb3
>> >> cas=1-12:1101
>> >> dchan=16
>> >>
>> >> # Global data
>> >> loadzone = ar
>> >> defaultzone = ar
>> >>
>> >> Thanks in advance.
>> >>
>> >> P.D.: Sorry, my english is not good
>> >>
>> >> _______________________________________________
>> >> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>> >>
>> >> asterisk-r2 mailing list
>> >> To UNSUBSCRIBE or update options visit:
>> >> http://lists.digium.com/mailman/listinfo/asterisk-r2
>> >>
>> >
>> >
>> >
>> > --
>> > Moises Silva
>> > Software Developer
>> > Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON
L3R
>> > 9T3
>> > Canada
>> > t. 1 905 474 1990 x 128 | e. moy at sangoma.com
>> >
>>
>> _______________________________________________
>> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>>
>> asterisk-r2 mailing list
>> To UNSUBSCRIBE or update options visit:
>> http://lists.digium.com/mailman/listinfo/asterisk-r2
>
>
>
> --
> Moises Silva
> Software Developer
> Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON L3R
9T3
> Canada
> t. 1 905 474 1990 x 128 | e. moy at sangoma.com
>
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>
> asterisk-r2 mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-r2
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-r2/attachments/20091201/b3ec2bba/attachment-0001.htm
More information about the asterisk-r2
mailing list