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