[asterisk-r2] Incoming Calls hungup using MFCR2 Protocol

[Diego Pinzon]

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 CAS3. 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: COAsterisk-1.4.32dahdi-linux-2.5.0.2dahdi-tools-2.5.0.2openr2-1.3.2Openr2-asterisk-1.4.32-p1.patchwanpipe-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 = 0x04DNIS = , 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 = 0x04DNIS = , 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 = 0x04DNIS = , 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 = 0x0CDNIS = 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=defaultusecallerid=yeshidecallerid=nocallwaiting=yesusecallingpres=yescallwaitingcallerid=yesthreewaycalling=yestransfer=yescanpark=yescancallforward=yescallreturn=yesechocancel=noechocancelwhenbridged=norelaxdtmf=yesrxgain=0.0txgain=0.0group=1callgroup=1pickupgroup=1immediate=no;Sangoma A102 port 1 [slot:10 bus:1 span:1] <wanpipe1>
signalling=mfcr2mfcr2_variant=comfcr2_get_ani_first=yesmfcr2_max_ani=10mfcr2_max_dnis=7mfcr2_category=national_subscribermfcr2_mfback_timeout=-1mfcr2_metering_pulse_timeout=-1mfcr2_logdir=logmfcr2_logging=all
context=from-pstnswitchtype=euroisdngroup=0faxdetect=incomingsignalling=mfcr2channel => 1-15,17-31
;Sangoma A102 port 2 [slot:10 bus:1 span:2] <wanpipe2>switchtype=euroisdncontext=from-pbxgroup=1faxdetect=incomingsignalling=mfcr2mfcr2_variant=comfcr2_max_ani=10mfcr2_max_dnis=7mfcr2_category=national_subscribermfcr2_mfback_timeout=-1mfcr2_metering_pulse_timeout=-1mfcr2_logdir=logmfcr2_logging=allchannel => 32-46,48-62

...............................................................................system.conf
loadzone=usdefaultzone=us
#Sangoma A102 port 1 [slot:10 bus:1 span:1] <wanpipe1>span=1,1,0,cas,hdb3cas=1-15:1101dchan=16cas=17-31:1101
#Sangoma A102 port 2 [slot:10 bus:1 span:2] <wanpipe2>span=2,0,0,cas,hdb3cas=32-46:1101dchan=47cas=48-62:1101

 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-r2/attachments/20120120/b256dad0/attachment.htm>