[asterisk-r2] (no subject)
Diego Pinzon
diego_p_29 at hotmail.com
Mon Jan 23 19:58:50 CST 2012
Hi, EveryBody
The Main issue --> the incoming calls work fine for a while then all calls hangup, then 1 minute later everything is working fine. Is a loop all day.
After read many logs found that there are a couple different things that could be causing this issue, 1. any overruns in the system the audio might be corrupted, 2. MF Toneso or the orer that we play/detect them in.
Someone can help me to configure MF tones or are there monitoring software to check it?
Regards,Diego.
> From: asterisk-r2-request at lists.digium.com
> Subject: asterisk-r2 Digest, Vol 41, Issue 19
> To: asterisk-r2 at lists.digium.com
> Date: Mon, 23 Jan 2012 19:33:57 -0600
>
> Send asterisk-r2 mailing list submissions to
> asterisk-r2 at lists.digium.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.digium.com/mailman/listinfo/asterisk-r2
> or, via email, send a message with subject or body 'help' to
> asterisk-r2-request at lists.digium.com
>
> You can reach the person managing the list at
> asterisk-r2-owner at lists.digium.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of asterisk-r2 digest..."
>
>
> Today's Topics:
>
> 1. Re: Incoming Calls hungup using MFCR2 Protocol (Mc GRATH Ricardo)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 23 Jan 2012 20:27:54 -0500
> From: Mc GRATH Ricardo <mcgrathr at mail2web.com>
> Subject: Re: [asterisk-r2] Incoming Calls hungup using MFCR2 Protocol
> To: "asterisk-r2 at lists.digium.com" <asterisk-r2 at lists.digium.com>,
> "juanrcuervo at quality-telecom.net" <juanrcuervo at quality-telecom.net>
> Message-ID:
> <39F8F0A9F90D5C48A847177B56A22567F3DAFF99EF at MBX81.ad2.softcom.biz>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Juan
> How about to swap E1 cable? I just mean to change cable connection, Telco provider on port 1 should be at port to and so on with port 2 and check error message (channel (32) etc).
> By the other way, I guest A102 port 2 configuration should be span=2,2,0,cas,hdb3.
> By the way when dahdi configuration have changed please stop and restart services.
>
> Best regards
> Mc GRATH Ricardo
> E-Mail mcgrathr at mail2web.com<mailto:mcgrathr at mail2web.com>
>
> ________________________________
> From: asterisk-r2-bounces at lists.digium.com [asterisk-r2-bounces at lists.digium.com] On Behalf Of Diego Pinzon [diego_p_29 at hotmail.com]
> Sent: 23 January 2012 12:55
> To: juanrcuervo at quality-telecom.net
> Cc: asterisk-r2 at lists.digium.com
> Subject: Re: [asterisk-r2] Incoming Calls hungup using MFCR2 Protocol
>
>
>
> Hi, Everybody
>
> Any update about it
> 1. The channels are swithching between "Zap alarm" and "Far en ublocked on chan.."
> 2. Protocol Error, INVALID CAS
> 3. Protocol Error... Invalid Multi Frequency Tone
>
> Are someone with MFC-R2 experience?
>
> Regards,
> Diego Pinzon
>
>
>
> ________________________________
> Date: Fri, 20 Jan 2012 14:57:02 -0500
> From: juanrcuervo at quality-telecom.net
> To: diego_p_29 at hotmail.com
> CC: asterisk-r2 at lists.digium.com
> Subject: Re: [asterisk-r2] Incoming Calls hungup using MFCR2 Protocol
>
> Hi Diego
>
> As I told you , I believe your problem is not related to the mfcr2 variant.
> This seems more like a timing, phisical or drivers problem to me.
>
> You use Sangoma and Wanpipe , and I have not experience in those.
>
> Can anyone check if this might be related to a hardware / drivers issue?
>
>
>
>
> Juan R. Cuervo Soto
> Quality Telecom Ltd
> www.quality-telecom.net<http://www.quality-telecom.net>
> PBX : (575) 3693300
> CEL : (57) 301-4174865
>
> El 20/01/2012 11:46 a.m., Diego Pinzon escribi?:
>
> Hi EveryBody, after teste "ar" variant the issue still hungup incoming calls.
>
>
> [Jan 20 11:23:14] WARNING[19197] app_dial.c: Unable to forward voice frame
> [Jan 20 11:26:24] ERROR[19140] chan_dahdi.c: Chan 33 - Protocol error. Reason = Invalid CAS, R2 State = Clear Forward Transmitted, MF state = MF Engine Off, MF Group = Forward Group II, CAS = 0x04
> DNIS = 5848484, ANI = 3175131107, MF = 0x20
> [Jan 20 11:26:24] ERROR[19140] chan_dahdi.c: MFC/R2 protocol error on chan 33: Invalid CAS
> [Jan 20 11:26:24] NOTICE[19140] chan_dahdi.c: Far end unblocked on chan 33
> [Jan 20 11:27:01] WARNING[19139] chan_dahdi.c: Chan 20 - MF back cycle timed out!
> [Jan 20 11:27:01] ERROR[19139] chan_dahdi.c: Chan 20 - Protocol error. Reason = Multi Frequency Cycle Timeout, R2 State = Seize ACK Transmitted, MF state = ANI Request Transmitted, MF Group = Backward Group A, CAS = 0x00
> DNIS = 5, ANI = 31751311, MF = 0x31
> [Jan 20 11:27:01] ERROR[19139] chan_dahdi.c: MFC/R2 protocol error on chan 20: Multi Frequency Cycle Timeout
> [Jan 20 11:27:01] NOTICE[19139] chan_dahdi.c: Far end unblocked on chan 20
>
>
> Regards,
> Diego Pinzon
>
> ________________________________
> Date: Fri, 20 Jan 2012 09:10:05 -0500
> From: juanrcuervo at quality-telecom.net<mailto:juanrcuervo at quality-telecom.net>
> To: asterisk-r2 at lists.digium.com<mailto:asterisk-r2 at lists.digium.com>
> CC: diego_p_29 at hotmail.com<mailto:diego_p_29 at hotmail.com>; eduardosolando85 at gmail.com<mailto:eduardosolando85 at gmail.com>
> Subject: Re: [asterisk-r2] Incoming Calls hungup using MFCR2 Protocol
>
> Hi Diego
>
> I have been working for a while in Barranquilla with both PSTN providers (telecom , Metrotel).
> You should try the Argentina variant of MFCR2. (AR), it works fine for me.
>
> Anyway, I believe you have a problem apart from the signalling variant. can you please post your system.conf (dahdi) configuration file and your chan_dahdi.conf
>
> Regards,
>
>
> Juan R. Cuervo Soto
> Quality Telecom Ltd
> www.quality-telecom.net<http://www.quality-telecom.net>
> PBX : (575) 3693300
> CEL : (57) 301-4174865
>
> El 20/01/2012 07:17 a.m., Diego Pinzon escribi?:
>
> Hi, EveryBody.
>
> I have some problems with a MFCR2 Protocol and Colombian TELCO. Some calls hungup or after answer the operator and other calls reamin silent.
>
> The main problems are:
> 1. The channels are swithching between "Zap alarm" and "Far en ublocked on chan.."
> 2. Protocol Error, INVALID CAS
> 3. Protocol Error... Invalid Multi Frequency Tone
>
> I need your help to fix it, I teste itu, ar, br variants and the issue didnt fix. Please any advice will be ready for testing
>
>
> System Details:
> A102 Sangoma
> MFC.R2 Variant: CO
> Asterisk-1.4.32
> dahdi-linux-2.5.0.2
> dahdi-tools-2.5.0.2
> openr2-1.3.2
> Openr2-asterisk-1.4.32-p1.patch
> wanpipe-3.5.24
>
> Diego Pinzon
>
> Log:
>
> Jan 19 23:46:23] NOTICE[8636] cdr.c: CDR simple logging enabled.
> [Jan 19 23:46:23] NOTICE[8636] loader.c: 146 modules will be loaded.
> [Jan 19 23:46:23] WARNING[8636] res_smdi.c: No SMDI interfaces are available to listen on, not starting SMDI listener.
> [Jan 19 23:46:23] ERROR[8636] codec_dahdi.c: Failed to open /dev/dahdi/transcode: No such file or directory
> [Jan 19 23:46:23] NOTICE[8654] chan_dahdi.c: Far end unblocked on chan 32
> [Jan 19 23:46:23] NOTICE[8654] chan_dahdi.c: Far end unblocked on chan 33
> [Jan 19 23:46:23] NOTICE[8654] chan_dahdi.c: Far end unblocked on chan 34
> ....
>
> --------------------------------------------------------------------------------- RED ALARM .........................
> [Jan 20 00:08:00] WARNING[8652] chan_dahdi.c: Detected alarm on channel 1: Red Alarm
> [Jan 20 00:08:00] WARNING[8652] chan_dahdi.c: Zap alarm on chan 1.
> ....
> [Jan 20 00:08:00] WARNING[8653] chan_dahdi.c: Zap alarm on chan 31.
> [Jan 20 00:08:00] WARNING[8652] chan_dahdi.c: Detected alarm on channel 5: Red Alarm
>
> ..................................................................................................... PROTOCOL ERROR ........................
>
> [Jan 20 00:28:10] NOTICE[8653] chan_dahdi.c: Alarm cleared on channel 31
> [Jan 20 00:28:10] WARNING[8653] chan_dahdi.c: Zap alarm on chan 31.
> [Jan 20 00:34:04] ERROR[8652] chan_dahdi.c: Chan 1 - Protocol error. Reason = Invalid CAS, R2 State = Idle, MF state = MF Engine Off, MF Group = No Group, CAS = 0x04
> DNIS = , ANI = , MF = 0x20
> [Jan 20 00:34:04] ERROR[8652] chan_dahdi.c: MFC/R2 protocol error on chan 1: Invalid CAS
> [Jan 20 00:34:04] ERROR[8652] chan_dahdi.c: Chan 2 - Protocol error. Reason = Invalid CAS, R2 State = Idle, MF state = MF Engine Off, MF Group = No Group, CAS = 0x04
> DNIS = , ANI = , MF = 0x20
> [Jan 20 00:34:04] ERROR[8652] chan_dahdi.c: MFC/R2 protocol error on chan 2: Invalid CAS
> [Jan 20 00:34:04] ERROR[8652] chan_dahdi.c: Chan 3 - Protocol error. Reason = Invalid CAS, R2 State = Idle, MF state = MF Engine Off, MF Group = No Group, CAS = 0x04
> DNIS = , ANI = , MF = 0x20
> [Jan 20 00:34:04] ERROR[8652] chan_dahdi.c: MFC/R2 protocol error on chan 3: Invalid CAS
> [Jan 20 00:34:04] NOTICE[8652] chan_dahdi.c: Far end blocked on chan 4
>
> ..................................................................................................... PROTOCOL ERROR ........................
>
> [Jan 20 03:45:21] ERROR[11754] chan_dahdi.c: Chan 32 - Protocol error. Reason = Invalid Multi Frequency Tone, R2 State = Seize ACK Received, MF state = Category Transmitted, MF Group = Forward Group II, CAS = 0x0C
> DNIS = 5848484, ANI = 55702714, MF = 0x33
> [Jan 20 03:45:21] ERROR[11754] chan_dahdi.c: MFC/R2 protocol error on chan 32: Invalid Multi Frequency Tone
> [Jan 20 03:45:21] WARNING[11754] app_dial.c: Unable to forward voice or dtmf
> [Jan 20 03:45:21] ERROR[11754] chan_dahdi.c: Chan 32 - Trying to dial out in a non-idle channel (cas=0x0C)
> [Jan 20 03:45:21] ERROR[11754] chan_dahdi.c: unable to make new MFC/R2 call!
> [Jan 20 03:45:21] NOTICE[8654] chan_dahdi.c: Far end unblocked on chan 32
> [Jan 20 03:59:43] WARNING[8652] chan_dahdi.c: Detected alarm on channel 1: Red Alarm
>
>
> ......................................................................................................................................................................
> chan_dahdi.conf
>
>
> [channels]
> context=default
> usecallerid=yes
> hidecallerid=no
> callwaiting=yes
> usecallingpres=yes
> callwaitingcallerid=yes
> threewaycalling=yes
> transfer=yes
> canpark=yes
> cancallforward=yes
> callreturn=yes
> echocancel=no
> echocancelwhenbridged=no
> relaxdtmf=yes
> rxgain=0.0
> txgain=0.0
> group=1
> callgroup=1
> pickupgroup=1
> immediate=no
> ;Sangoma A102 port 1 [slot:10 bus:1 span:1] <wanpipe1>
>
> signalling=mfcr2
> mfcr2_variant=co
> mfcr2_get_ani_first=yes
> mfcr2_max_ani=10
> mfcr2_max_dnis=7
> mfcr2_category=national_subscriber
> mfcr2_mfback_timeout=-1
> mfcr2_metering_pulse_timeout=-1
> mfcr2_logdir=log
> mfcr2_logging=all
>
> context=from-pstn
> switchtype=euroisdn
> group=0
> faxdetect=incoming
> signalling=mfcr2
> channel => 1-15,17-31
>
> ;Sangoma A102 port 2 [slot:10 bus:1 span:2] <wanpipe2>
> switchtype=euroisdn
> context=from-pbx
> group=1
> faxdetect=incoming
> signalling=mfcr2
> mfcr2_variant=co
> mfcr2_max_ani=10
> mfcr2_max_dnis=7
> mfcr2_category=national_subscriber
> mfcr2_mfback_timeout=-1
> mfcr2_metering_pulse_timeout=-1
> mfcr2_logdir=log
> mfcr2_logging=all
> channel => 32-46,48-62
>
>
> ...............................................................................
> system.conf
>
> loadzone=us
> defaultzone=us
>
> #Sangoma A102 port 1 [slot:10 bus:1 span:1] <wanpipe1>
> span=1,1,0,cas,hdb3
> cas=1-15:1101
> dchan=16
> cas=17-31:1101
>
> #Sangoma A102 port 2 [slot:10 bus:1 span:2] <wanpipe2>
> span=2,0,0,cas,hdb3
> cas=32-46:1101
> dchan=47
> cas=48-62:1101
>
>
>
>
>
> --
> _____________________________________________________________________
> -- 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
>
>
>
> Se certific? que el correo no contiene virus.
> Comprobada por AVG - www.avg.es<http://www.avg.es>
> Versi?n: 2012.0.1901 / Base de datos de virus: 2109/4754 - Fecha de la versi?n: 19/01/2012
>
> Se certific? que el correo no contiene virus.
> Comprobada por AVG - www.avg.es<http://www.avg.es>
> Versi?n: 2012.0.1901 / Base de datos de virus: 2109/4755 - Fecha de la versi?n: 20/01/2012
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.digium.com/pipermail/asterisk-r2/attachments/20120123/96c5e7ae/attachment.htm>
>
> ------------------------------
>
> _______________________________________________
> --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
>
> End of asterisk-r2 Digest, Vol 41, Issue 19
> *******************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-r2/attachments/20120123/888500cf/attachment-0001.htm>
More information about the asterisk-r2
mailing list