OpenR2
OpenR2 is a library that implements the MFC/R2 telephony signaling protocol over E1 lines. Along with the library, branches and patches for Asterisk and FreeSWITCH are provided with MFC/R2 support in chan_zap / chan_dahdi and OpenZAP. Starting with Asterisk 1.6.2 is used by Asterisk to give official MFC-R2 support to chan_dahdi.
To get the library you can download it from Google Code: http://code.google.com/p/openr2/downloads/list
Before installing the library you need either Zaptel or DAHDI. After installing the library you can proceed to download any of the patches for Asterisk 1.2, 1.4 or 1.6 available in google code.
For help configuring zapata.conf or chan_dahdi.conf open “configs/zapata.conf.sample” or “configs/chan_dahdi.conf.sample” and search “mfcr2”.
If you need assistance for installing it you can download the OpenR2 guide in English, Portuguese or Spanish in google code. There is also an official Digium mailing list “asterisk-r2” (preferred language is English), you can subscribe here: http://lists.digium.com/mailman/listinfo/asterisk-r2
To see a list of supported MFC-R2 variants you can execute the command “r2test -l” to list the supported variants. Inside the Asterisk CLI you can also type “mfcr2 show variants”.
Other countries probably work with the ITU variant, if your country is not specified here try with the ITU variant and let me know your results. If you want your country variant supported drop me a line.
Moisés Silva
- Sunday January 27, 2008 @ 17:34
- Write a comment
Great work Moy!!!
I've been testing the libs with asterisk 1.4 and then Argentina's variant and it have been working without any problemws from the last two weeks.
Thanks a lot for your work and feel free to contact me if you need some help from Argentina.
Gonzalo Blousson
Gonzalo,
Thanks for testing!, the best you can do is to test and report bugs to me to leave this thing as stable as possible soon and get it merged with Asterisk.
Hi Moy , great Job Moy.
I will start to test the 1.4 version in a couple of days on my bussines PBX, I will post my results , I have realy poor traffic but my users dont are very polite when thing dont work fine.
Best regards!
By the way , congratulations too, for your next participation on the astricon on near september at the USA.
Acriollo, no user is polite when things don't work, particularly if they paid for the service :)
Anyway, thanks for testing, let me know if you have any issues.
Hi Moy nice work.
I dont have problems when I use mfcr2-1.4 or mfcr2 but while trying mfcr2-1.2 I see this error:
Aug 28 13:49:02 NOTICE[5417] cdr.c: CDR simple logging enabled.
Aug 28 13:49:02 WARNING[5417] loader.c: libopenr2.so.0: cannot open shared object file: No such file or directory
Aug 28 13:49:02 WARNING[5417] loader.c: Loading module chan_zap.so failed!
Thank you
try installing openr2 in /usr/ not /usr/local, otherwise you need to have the /usr/local/lib directory in the loader path (see /etc/ld.so.conf)
Hi moy thanks for you're help..
I did what you said and I installed openr2 in /usr/, but now I have this message:
[Aug 29 11:17:27] WARNING[32135] loader.c: Error loading module 'chan_zap.so': libopenr2.so.0: cannot open shared object file: No such file or directory
[Aug 29 11:17:27] WARNING[32135] loader.c: Module 'chan_zap.so' could not be loaded.
I think that it could be due that chan_zap.so can not be loaded at the same time as libopenr2.
am i right or wrong?
wrong
The error is still the same, chan_zap.so depends on openr2 when compiling with R2 support, but it seems the loader is not finding that dependency. What is the output of “ls /usr/lib/libopenr2” ? and “ls /usr/local/lib/libopenr2”
If you install openr2 as:
“./configure --prefix=/usr && make && make install”
it should work
I finally took the time to read libopenr2's code. Thanks a lot for the great work, this library will just simplify our jobs and improve our possibilities with R2.
I second that. :)
Hello! I need Help…
I take a test, using the openR2 with asterisk 1.4. The channel is ok, (Idle)… but i don't have mfc codes. In the log, show the current msg:
[Sep 18 01:48:52] WARNING[15754]: chan_zap.c:11176 process_zap: Ignoring echotrainning
[Sep 18 01:48:52] WARNING[15754]: chan_zap.c:11176 process_zap: Ignoring signalling
[Sep 18 01:48:52] WARNING[15754]: chan_zap.c:11176 process_zap: Ignoring mfcr2_variant
[Sep 18 01:48:52] WARNING[15754]: chan_zap.c:11176 process_zap: Ignoring mfcr2_get_ani_first
[Sep 18 01:48:52] WARNING[15754]: chan_zap.c:11176 process_zap: Ignoring mfcr2_max_ani
[Sep 18 01:48:52] WARNING[15754]: chan_zap.c:11176 process_zap: Ignoring mfcr2_max_dnis
[Sep 18 01:48:52] WARNING[15754]: chan_zap.c:11176 process_zap: Ignoring mfcr2_category
[Sep 18 01:48:52] WARNING[15754]: chan_zap.c:11176 process_zap: Ignoring mfcr2_logdir
[Sep 18 01:48:52] WARNING[15754]: chan_zap.c:11176 process_zap: Ignoring mfcr2_logdir
[Sep 18 01:48:52] WARNING[15754]: chan_zap.c:11176 process_zap: Ignoring mfcr2_loggin
[Sep 18 01:48:52] ERROR[15754]: chan_zap.c:10527 build_channels: Unable to reconfigure channel '1-15,17-31'
[Sep 18 01:48:52] WARNING[15754]: chan_zap.c:11494 reload: Reload of chan_zap.so is unsuccessful!
My install is wrong ? Thanks
I wonder how you see Idle lines? how do you know the lines are idle?
For me it seems you have chan_zap without openr2 support, you can verify that with the Asterisk command
If the command is not found, you don't have openr2 installed and therefore chan_zap was compiled without R2 support.
Hi Moy!!!
Congratulations and…thanks for your help!!!! <?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p>
I’m using a Protocol Analyzer between the PBX and Asterisk. The equipment shows the entire channel in idle condition, but I’m not installing mfcr2 correctly, because the command “mfcr2 show version” it does not appear.<o:p> </o:p>
I follow step by step the installation guide in the web site http://www.asteriskexperts.com.br/content/view/271/1/ , but I’m using CentOs with Elastix 1.09 distribution. Please, I need your help… thanks J<o:p></o:p>
<o:p></o:p>
Glaucio Oliveira <o:p></o:p>
gcobrasil@hotmail.com<o:p></o:p>
That guide is wrong and I requested them to correct it. They never mention you need to install OpenR2 from libopenr2.org BEFORE installing my Asterisk branch. Try installing openr2 first and then running ./configure && make install again in Asterisk to install it.
Sorry Moy, my install is unsucessiful! In the config.log i have continuous error as follow:
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE “OpenR2”
| #define VERSION “0.1.1”
| #define _GNU_SOURCE 1
| #define STDC_HEADERS 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_DLFCN_H 1
| /* end confdefs.h. */
| #include <ac_nonexistent.h>
I send in your mail the log file for more informations.
Thanks one more time!!
Glaucio Olviveira
Please post this in asterisk-r2 mailing list, I receive many e-mails
regarding openr2 and other R2 issues, and I'd like to answer to this
kind of questions in a more proper place, the asterisk-r2 mailing list
is new, it was open just yesterday. To subscribe just go to
http://lists.digium.com/<wbr>mailman/listinfo/asterisk-r2 and follow the
instructions.
Hola, Moy…como sería la implementacion de tus librerias con Elastix 1.3? Hay algun RPM disponible para esta versión? He seguido tu trabajo desde que Underwood te contestó y me parece remarcable. Respecto a Elastix, tendrías algun tip para darme?? (A pesar de ser de la vieja escuela de Asterisk, con configuracion a mano de los .conf y todo eso, Elastix agrega gran valor a la oferta de Telefonia IP existente y por eso lo estoy usando en varios escenarios de produccion con primarios y lineas analogas, con buenos resultados; pero Estoy en Barranquilla, Colombia, y los PRI RDSI son contados y escasos, ademas de la lista en espera para readjudicarlos cuando alguien se desafilia del servicio. Abundan los R2 y para nosotros los integradores de redes de voz, tener el respaldo de un desarrollo como el tuyo que maximize la estabilidad de enlaces con esta señalización, toma carácter critico. El R2 es la piedra en el zapato, y el camino es de herradura…
De antemano, gracias por la respuesta y felicitaciones por el nuevo puesto en Sangoma.
Ivanof M.
InteliRedes Colombia Ltda
Que tal Ivan,
Desconozco si hay algún RPM disponible. La forma en lo que yo lo haría es simplemente instalar el Asterisk de mi branch mfcr2-1.4 sobre el que trae Elastix (previa instalación a pata de openr2 con ./configure --prefix=/usr && make install).
Puedes pedir mas informes en la lista de R2 de Digium http://lists.digium.com/mailman/listinfo/asterisk-r2 , donde hay gente que tal vez tenga un RPM que compartir, o incluso alguien que quiera contribuirlo a el arbol de openr2.
Saludos!
Gracias por responder..de hecho, yo tengo mis canales arriba..te muestro como van:
elastix*CLI> UC show channels
Channel Extension Context Status Language MusicOnHold
1 from-pstn Idle es default
2 from-pstn Idle es default
3 from-pstn Idle es default
4 from-pstn Idle es default
5 from-pstn Idle es default
6 from-pstn Idle es default
7 from-pstn Idle es default
8 from-pstn Idle es default
9 from-pstn Idle es default
10 from-pstn Idle es default
11 from-pstn Idle es default
12 from-pstn Idle es default
13 from-pstn Idle es default
14 from-pstn Idle es default
15 from-pstn Idle es default
17 from-pstn Idle es default
18 from-pstn Idle es default
19 from-pstn Idle es default
20 from-pstn Idle es default
21 from-pstn Idle es default
22 from-pstn Idle es default
23 from-pstn Idle es default
24 from-pstn Idle es default
25 from-pstn Idle es default
26 from-pstn Idle es default
27 from-pstn Idle es default
28 from-pstn Idle es default
29 from-pstn Idle es default
30 from-pstn Idle es default
31 from-pstn Idle es default
-------------zaptel.conf--------------
span=1,1,0,cas,hdb3
cas=1-15:1101
dchan=16
cas=17-31:1101
loadzone = fr
defaultzone = fr
-------------unicall.conf----------------
[Channels]
language=es
context=from-pstn
usecallerid=yes
hidecallerid=no
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=no
echotraining=800
echotraining=yes
relaxdtmf=yes
rxgain=0
txgain=0
immediate=no
callerid=asreceived
amaflags=default
accountcode=metrotel
musiconhold=default
protocolclass=mfcr2
protocolvariant=ar,20,4
#protocolvariant=co-land,30,7,16
#protocolvariant=co-land,20,4
protocolend=cpe
group = 1
context=from-pstn
callgroup=1
pickupgroup=1
channel=1-15,17-31
------------ztcfg -vvvv-----------------
SPAN 1: CAS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)
Channel map:
Channel 01: CAS / User (Default) (Slaves: 01)
Channel 02: CAS / User (Default) (Slaves: 02)
Channel 03: CAS / User (Default) (Slaves: 03)
Channel 04: CAS / User (Default) (Slaves: 04)
Channel 05: CAS / User (Default) (Slaves: 05)
Channel 06: CAS / User (Default) (Slaves: 06)
Channel 07: CAS / User (Default) (Slaves: 07)
Channel 08: CAS / User (Default) (Slaves: 08)
Channel 09: CAS / User (Default) (Slaves: 09)
Channel 10: CAS / User (Default) (Slaves: 10)
Channel 11: CAS / User (Default) (Slaves: 11)
Channel 12: CAS / User (Default) (Slaves: 12)
Channel 13: CAS / User (Default) (Slaves: 13)
Channel 14: CAS / User (Default) (Slaves: 14)
Channel 15: CAS / User (Default) (Slaves: 15)
Channel 16: D-channel (Default) (Slaves: 16)
Channel 17: CAS / User (Default) (Slaves: 17)
Channel 18: CAS / User (Default) (Slaves: 18)
Channel 19: CAS / User (Default) (Slaves: 19)
Channel 20: CAS / User (Default) (Slaves: 20)
Channel 21: CAS / User (Default) (Slaves: 21)
Channel 22: CAS / User (Default) (Slaves: 22)
Channel 23: CAS / User (Default) (Slaves: 23)
Channel 24: CAS / User (Default) (Slaves: 24)
Channel 25: CAS / User (Default) (Slaves: 25)
Channel 26: CAS / User (Default) (Slaves: 26)
Channel 27: CAS / User (Default) (Slaves: 27)
Channel 28: CAS / User (Default) (Slaves: 28)
Channel 29: CAS / User (Default) (Slaves: 29)
Channel 30: CAS / User (Default) (Slaves: 30)
Channel 31: CAS / User (Default) (Slaves: 31)
31 channels to configure.
Aun asi, no logro sacar las llamadas…a pesar de que el las manda a mi troncal unicall…el modulo chan_unicall.so esta arriba, los canales, etc..y mi tarjeta sigue alarmada (red)..si no es mucha molestia, tienes alguna sugerencia?
Gracias de nuevo.
Img
Este sitio es para discusión de OpenR2, no para Unicall. De cualquier modo pregunta en la lista de asterisk-r2, es el modo adecuado de que mas gente se beneficie de la respuesta.
Ok..fair enough..thnx anyway..
Img.
Que tal moy, alguna guia de instalacion de libopenr2 con asterisk 1.4.x o 1.6.x ?
Esto es trabajo en progreso: http://docs.google.com/Doc?id=dgv9zr4g_24fgfjt7r5
Pero puede servirte mientras queda terminada.
Muchas gracias moy lo reviso y te menciono que tal me fue
Hi all
I'm new so please tell me hox to download openr2 for Asterisk 1.4
you did not even read the front page of this web site.
Hola, Moy..
Hoy liberaron la version 1.5 Estable de Elastix, que viene con soporte nativo para MFCR2, garcias a openr2. Tengo que migrar un servidor que estaba con una version anterior con unicall trabajando perfectamente en Colombia, con la variante de arabia saudita (protocolvariant=sa). Funca perfecto para E1sR2 de Metrotel. Ahora con la nueva version que ya no viene con soporte para unicall, que variante debería utilizar, ya que la de Arabia Saudita no está disponible en esta distro? ITU variant concordará con sa?? Si no es así, es posible contar con esta variante?
Gracias de antemano.
Td
Desconozco los detalles de la variante de arabia saudita de Unicall, asi que creo que tendras que probar con ITU o con la variante de Colombia. Si la de colombia no funciona habra que mejorarla para hacerla funcionar bien, si deseas continuar la discusión por favor envia un correo a la lista de asterisk-r2 y podemos continuar ahi.
Moisés, te hago una consulta.
Estoy usando Elastix 1.5, el cuál trae soporte nativo para la señalización R2 justamente con openr2. La consulta es la siguiente:
como sería la sintaxis del comando Dial() usando esta librería?…
Antes con Unicall, hacía un Dial sobre Unicall/g0/${EXTEN}…. como sería ahora con openr2?
Ya tengo configurada la placa TE121P, veo los canales con mfcr2 show channels desde la consola de asterisk en estado idle… pero no encuentro documentación ni mucha ayuda acerca de como crear los troncales y rutas salientes con esta libreria…
Desde ya muchas gracias
Saludos, Francisco
usa la lista asterisk-r2
I followed the manual from this link http://openr2.googlecode.com/files/openr2-guide-0.1.pdf
accordingly. However my Digium TE121B led color is still red.
When I check the logs, there were some errors.
Apr 17 23:37:27] WARNING[16763] pbx.c: Already have an application 'ZapAcceptR2Call'
[Apr 17 23:37:27] ERROR[16763] chan_dahdi.c: Cannot create OpenR2 protocol context.
[Apr 17 23:37:27] ERROR[16763] chan_dahdi.c: Unable to register channel '1-15'
What do you think is the cause of this problem?
thanks
use the asterisk-r2 mailing list for such question
I have a problem.
I'm trying to install openr2 in asterisk1.4-mfcr2, but, after all steps, mfcr2 dont apears in CLI list of commands. What I'm doing wrong ?
Environment:
CentOS 5.3 x64
packages:
asterisk-1.4-mfcr2.tar.gz
dahdi-linux-2.1.0.4.tar.gz
dahdi-tools-2.1.0.2.tar.gz
libpri-1.4.10.tar.gz
and
openr2-1.1.0.tar.gz
Thanks
No one can possibly know what are you doing wrong if you don't even tell us what are you doing.
Try describing your problem in the asterisk-r2 mailing list.
http://lists.digium.com/mailman/listinfo/asterisk-r2
Is the openr2 library ready for x64 systems?
After install all packages in i386 system (CentOS 5.3), “mfcr2” appears in CLI command list normally. But when I doing the same things in x64 system (CentOS 5.3 64bits), the “mfcr2” don't appears in CLI command list.
I'm using:
asterisk-1.4-mfcr2.tar.gz
dahdi-linux-2.1.0.4.tar.gz
dahdi-tools-2.1.0.2.tar.gz
libpri-1.4.10.tar.gz
openr2-1.1.0.tar.gz
Thanks
unbios
yes, openr2 works in 64 bit systems, my laptop where I test this is 64 bit.
Guia rápida de instalación de libopenr2 en español.
http://demerzel.org/?p=13
Another blog post about R2. This one is about Unicall configurations with Nortel though. The concepts still apply for openr2.
http://arturoochoa.wordpress.com/2009/03/11/asterisk-with-nortel-option-11-using-mfcr2/
Hola
Ayuda…
Estoy instalando un server con asterisk y openR2, al cargar el modulo chan_dahdi.c
me aparecen los siguientes errores
[Jul 21 11:36:10] ERROR[2731]: chan_dahdi.c:8379 mkintf: Cannot create OpenR2 protocol context.
[Jul 21 11:36:10] ERROR[2731]: chan_dahdi.c:12377 build_channels: Unable to register channel '1-15,17-31'
Gracias de antemano.
Israel
lists.digium.com y busca la lista de asterisk-r2 para este tipo de preguntas.
You are the man!
THANK YOU VERY MUCH!!!!
You saved me, dude; it works perfectly!
Thanks for sharing your knowledge with the community.
Hola moy
llevo dos dias con este problemita no se si me pudes orientar tengo las siguientes versiones instalas
Dahdi version 2.1.0.4
openr2 version 1.1.0
elastix version 1.5.2-2
asterisk version 1.4.24
centos 5.2
karnel 2.6.18-92.22.e15
digium te121p
mis log son:
full
[Oct 21 16:05:40] DEBUG[7176] chan_dahdi.c: Chan 1 - Bits changed from 0x00 to 0x08
[Oct 21 16:05:40] DEBUG[7176] chan_dahdi.c: Chan 1 - CAS Rx << [IDLE] 0x08
[Oct 21 16:05:40] NOTICE[7176] chan_dahdi.c: Far end unblocked on chan 1
[Oct 21 16:09:49] DEBUG[7176] chan_dahdi.c: Chan 1 - Bits changed from 0x08 to 0x00
[Oct 21 16:09:49] DEBUG[7176] chan_dahdi.c: Chan 1 - CAS Rx << [SEIZE] 0x00
[Oct 21 16:09:49] DEBUG[7176] chan_dahdi.c: Chan 1 - Call started at Wed Oct 21 16:09:49 2009 on chan 1
[Oct 21 16:09:49] DEBUG[7176] chan_dahdi.c: Chan 1 - CAS Tx >> [SEIZE ACK] 0x0C
[Oct 21 16:09:49] DEBUG[7176] chan_dahdi.c: Chan 1 - CAS Raw Tx >> 0x0D
[Oct 21 16:09:49] NOTICE[7176] chan_dahdi.c: New MFC/R2 call detected on chan 1.
[Oct 21 16:09:49] DEBUG[7176] chan_dahdi.c: Chan 1 - MF Rx << 9 [ON]
[Oct 21 16:09:49] DEBUG[7176] chan_dahdi.c: Chan 1 - Getting DNIS digit 9
[Oct 21 16:09:49] DEBUG[7176] chan_dahdi.c: Chan 1 - DNIS so far: 9, expected length: 3
[Oct 21 16:09:49] DEBUG[7176] chan_dahdi.c: Chan 1 - User requested us to stop getting DNIS!
[Oct 21 16:09:49] DEBUG[7176] chan_dahdi.c: Chan 1 - MF Tx >> 6 [ON]
[Oct 21 16:09:49] DEBUG[7176] chan_dahdi.c: Chan 1 - MF Rx << 9 [OFF]
[Oct 21 16:09:49] DEBUG[7176] chan_dahdi.c: Chan 1 - MF Tx >> 6 [OFF]
[Oct 21 16:09:54] DEBUG[7176] chan_dahdi.c: Chan 1 - calling timer callback
[Oct 21 16:09:54] WARNING[7176] chan_dahdi.c: Chan 1 - MF back cycle timed out!
[Oct 21 16:09:54] ERROR[7176] chan_dahdi.c: Chan 1 - Protocol error. Reason = Multi Frequency Cycle Timeout, R2 State = Seize ACK Transmitted, MF state = Category Request Transmitted, MF Group = Backward Group A, CAS = 0x00
DNIS = 9, ANI = , MF = 0x20
[Oct 21 16:09:54] DEBUG[7176] chan_dahdi.c: Chan 1 - CAS Tx >> [IDLE] 0x08
[Oct 21 16:09:54] DEBUG[7176] chan_dahdi.c: Chan 1 - CAS Raw Tx >> 0x09
[Oct 21 16:09:54] ERROR[7176] chan_dahdi.c: MFC/R2 protocol error on chan 1: Multi Frequency Cycle Timeout
[Oct 21 16:09:57] DEBUG[7176] chan_dahdi.c: Chan 1 - Bits changed from 0x00 to 0x08
[Oct 21 16:09:57] DEBUG[7176] chan_dahdi.c: Chan 1 - CAS Rx << [IDLE] 0x08
[Oct 21 16:09:57] NOTICE[7176] chan_dahdi.c: Far end unblocked on chan 1
[Oct 21 16:10:01] VERBOSE[7165] logger.c: -- Remote UNIX connection
[Oct 21 16:10:01] VERBOSE[7301] logger.c: -- Remote UNIX connection disconnected
[Oct 21 16:11:49] DEBUG[7176] chan_dahdi.c: Chan 1 - Bits changed from 0x08 to 0x00
[Oct 21 16:11:49] DEBUG[7176] chan_dahdi.c: Chan 1 - CAS Rx << [SEIZE] 0x00
[Oct 21 16:11:49] DEBUG[7176] chan_dahdi.c: Chan 1 - Call started at Wed Oct 21 16:11:49 2009 on chan 1
[Oct 21 16:11:49] DEBUG[7176] chan_dahdi.c: Chan 1 - CAS Tx >> [SEIZE ACK] 0x0C
[Oct 21 16:11:49] DEBUG[7176] chan_dahdi.c: Chan 1 - CAS Raw Tx >> 0x0D
[Oct 21 16:11:49] NOTICE[7176] chan_dahdi.c: New MFC/R2 call detected on chan 1.
[Oct 21 16:11:49] DEBUG[7176] chan_dahdi.c: Chan 1 - MF Rx << 9 [ON]
[Oct 21 16:11:49] DEBUG[7176] chan_dahdi.c: Chan 1 - Getting DNIS digit 9
[Oct 21 16:11:49] DEBUG[7176] chan_dahdi.c: Chan 1 - DNIS so far: 9, expected length: 3
[Oct 21 16:11:49] DEBUG[7176] chan_dahdi.c: Chan 1 - User requested us to stop getting DNIS!
[Oct 21 16:11:49] DEBUG[7176] chan_dahdi.c: Chan 1 - MF Tx >> 6 [ON]
[Oct 21 16:11:49] DEBUG[7176] chan_dahdi.c: Chan 1 - MF Rx << 9 [OFF]
[Oct 21 16:11:49] DEBUG[7176] chan_dahdi.c: Chan 1 - MF Tx >> 6 [OFF]
[Oct 21 16:11:54] DEBUG[7176] chan_dahdi.c: Chan 1 - calling timer callback
[Oct 21 16:11:54] WARNING[7176] chan_dahdi.c: Chan 1 - MF back cycle timed out!
[Oct 21 16:11:54] ERROR[7176] chan_dahdi.c: Chan 1 - Protocol error. Reason = Multi Frequency Cycle Timeout, R2 State = Seize ACK Transmitted, MF state = Category Request Transmitted, MF Group = Backward Group A, CAS = 0x00
DNIS = 9, ANI = , MF = 0x20
[Oct 21 16:11:54] DEBUG[7176] chan_dahdi.c: Chan 1 - CAS Tx >> [IDLE] 0x08
[Oct 21 16:11:54] DEBUG[7176] chan_dahdi.c: Chan 1 - CAS Raw Tx >> 0x09
[Oct 21 16:11:54] ERROR[7176] chan_dahdi.c: MFC/R2 protocol error on chan 1: Multi Frequency Cycle Timeout
[Oct 21 16:11:57] DEBUG[7176] chan_dahdi.c: Chan 1 - Bits changed from 0x00 to 0x08
[Oct 21 16:11:57] DEBUG[7176] chan_dahdi.c: Chan 1 - CAS Rx << [IDLE] 0x08
[Oct 21 16:11:57] NOTICE[7176] chan_dahdi.c: Far end unblocked on cha
span
[16:13:21:221] [Thread: 3084626832] [Chan 1] - Call started at Wed Oct 21 16:13:21 2009 on chan 1
[16:13:21:221] [Thread: 3084626832] [Chan 1] - CAS Tx >> [SEIZE ACK] 0x0C
[16:13:21:221] [Thread: 3084626832] [Chan 1] - CAS Raw Tx >> 0x0D
[16:13:21:421] [Thread: 3084626832] [Chan 1] - MF Rx << 9 [ON]
[16:13:21:421] [Thread: 3084626832] [Chan 1] - Attempting to cancel timer timer 0
[16:13:21:421] [Thread: 3084626832] [Chan 1] - Cannot cancel timer 0
[16:13:21:421] [Thread: 3084626832] [Chan 1] - Getting DNIS digit 9
[16:13:21:421] [Thread: 3084626832] [Chan 1] - DNIS so far: 9, expected length: 3
[16:13:21:421] [Thread: 3084626832] [Chan 1] - User requested us to stop getting DNIS!
[16:13:21:421] [Thread: 3084626832] [Chan 1] - MF Tx >> 6 [ON]
[16:13:21:501] [Thread: 3084626832] [Chan 1] - MF Rx << 9 [OFF]
[16:13:21:501] [Thread: 3084626832] [Chan 1] - MF Tx >> 6 [OFF]
[16:13:26:421] [Thread: 3084626832] [Chan 1] - Attempting to cancel timer timer 2
[16:13:26:421] [Thread: 3084626832] [Chan 1] - timer id 2 found, cancelling it now
[16:13:26:421] [Thread: 3084626832] [Chan 1] - calling timer callback
[16:13:26:421] [Thread: 3084626832] [Chan 1] - MF back cycle timed out!
[16:13:26:421] [Thread: 3084626832] [Chan 1] - Protocol error. Reason = Multi Frequency Cycle Timeout, R2 State = Seize ACK Transmitted, MF state = Category Request Transmitted, MF Group = Backward Group A, CAS = 0x00
DNIS = 9, ANI = , MF = 0x20
[16:13:26:421] [Thread: 3084626832] [Chan 1] - Attempting to cancel timer timer 0
[16:13:26:421] [Thread: 3084626832] [Chan 1] - Cannot cancel timer 0
ya esta levante todo los canales,ya salen llamadas pero no salen 018000 y no entran las llamadas que vienen del pstn
Moisés:
Excelente tu trabajo. Gracias!
Una consulta, tengo del tarball la 1.6.1.6 corriendo, y quiero agregarle soporte de R2 (o migrar algunas tramas a PRI). La docu que encontre no referencia a patches para la 1.6.1 y el trunk 1.6 para bajar no es release. Tendrás algun patch hecho para la 1.6 current?
Toda ayuda agradecida
gus
En el futuro cualquier pregunta debe ir, de preferencia en ingles, a la lista asterisk-r2 en lists.digium.com
Hello Moy
1) I already have a an Asterisk 1.6.2.0-rc3 with Dahdi 2.2.0.2.
2) I downloaded openr2-1.2.0.tar.gz
3) I follow your spanish openr2-guide-0.1-es.pdf guide for installing OpenR2. (I compiled and installed)
4) no patch for 1.6.2 in google (I read above, that's is not longer necesary)
So, what should I do now?
Do I need to re-compile asterisk?, is there another way to install OpenR2 before having asterisk 1.6.2 installed?
Thanks
En el futuro cualquier pregunta debe ir, de preferencia en ingles, a la lista asterisk-r2 en lists.digium.com
I have problem with e1 & r2, when i dial from any extension nothing happen., after 20 second, i receive the following error
dahdi_r2_write_log: Chan 1 - MF Rx << F [ON]
dahdi_r2_write_log: Chan 1 - MF Tx >> 1 [OFF]dahdi_r2_write_log: Chan 1 - MF Rx << F [OFF]
dahdi_r2_write_log: Chan 1 - Protocol error. Reason = Invalid Multi Frequency Tone, R2 State = Seize ACK Received, MF state = DNIS Digit Transmitted, MF Group = Forward Group I, CAS = 0x0C
DNIS = 1497161, ANI = 1184, MF = 0x46
dahdi_r2_write_log: Chan 1 - CAS Tx >> [IDLE] 0x08
dahdi_r2_write_log: Chan 1 - CAS Raw Tx >> 0x09
dahdi_r2_on_protocol_error: MFC/R2 protocol error on chan 1: Invalid Multi Frequency Tone
dahdi_hangup: disconnecting MFC/R2 call on chan 1
dahdi_r2_write_log: Chan 1 - Cannot disconnect call when we dont have a call to disconnect
does openr2 support china?, i checked the code, there is no much code for china comparing unicall.
There is some code in there, I think I added it per a documentation spec I found in the net, but is not tested since I don't know anyone from China.
Hi,
I had just config the openr2 with dahdi and elastix, it is been interfaced with pstn and I was be able to call the subscribers of pstn but pstn's subscribers were not be able call extensions of my asterisk.
Please help on how to resolve this problem.
Thanks.
John
Contact me using the “Contact” button in this web page if you want to pay for getting your problem fixed.
Una consulta, tengo asterisk 1.6.2 con una trama ISDN y otra R2 con OpenR2.
En la ISDN si llamo a un destino que esta fuera de servicio recibo un mensaje de Asterisk indicando esto, pero en el caso de la trama R2 no recibo ningun mensaje, queda ringueando sin dar mensaje alguno.
Tienes idea de que debo modificar para que me de el mensaje?
OpenR2 TIMER.
Tengo el problema con algunas llamadas de larga distancia, el carrier reporta que el tarda en establecer la llamada y que de parte del Asterisk cierra el canal antes de que el logre establecerla.
Me piden que aumente el tiempo de espera en asterisk, este no es con el tiempo de timbrado en el Ring, si no en el chan_dahdi.conf, segun creo.
Que puedo hacer para aumentar este tiempo?
Gracias de antemano
Saludos
RRAMO2K,
Solve your problem?
I have a similar problem, but with some cell numbers of long distance.
MF Tx >> 6 [ON]
MF Rx << F [ON]
MF Tx >> 6 [OFF]
MF Rx << F [OFF]
Protocol error. Reason = Invalid Multi Frequency Tone, R2 State = Seize ACK Received
, MF state = DNIS Digit Transmitted, MF Group = Forward Group I, CAS = 0x0C
DNIS = 0454561094607, ANI = 2082, MF = 0x46
If you have a solution please share it, thanks.
I have this problem too. Please tell us the solution.
[Oct 25 09:48:53] ERROR[19782] chan_dahdi.c: Chan 86 - Protocol error. Reason = Invalid Multi Frequency Tone, R2 State = Seize ACK Transmitted, MF state = DNIS Request Transmitted, MF Group = Backward Group A, CAS = 0x00
DNIS = 37302101, ANI = , MF = 0x46
hi i am from venezuela and now my carrier cantv give me e1 in r2/r2 and work excelent but when i need a new e1 cantv say now is r2/mfcr2 any know howto configure this variante
hi i am from venezuela and now my carrier cantv give me e1 in r2/r2 and work excelent but when i need a new e1 cantv say now is r2/mfcr2 any know howto configure this variante
Soy novato en esto, tengo la versión 1.6.2 de Asterisk con MFCR2 para méxico, de un tiempo para acá a estado comportandose muy raro un canal en especifico revisando los logs esto es lo que muestra una y otra vez en repetidas ocasiones:
New MFC/R2 call detected on chan 6.
Chan 6 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 6
MFC/R2 call end on channel 6
New MFC/R2 call detected on chan 6.
Chan 6 - Far end disconnected. Reason: Normal Clearing
MFC/R2 call disconnected on channel 6
MFC/R2 call end on channel 6
Que podria ser, como se puede solucionar esto, de antemano muchas gracias.
Que tal,
Buen dia @El Primo, lograste resolver el problema ?, yo estoy experimentando exactamente lo mismo.
@AgusTinux:
1.-Para la parte en que se te desconectan las llamadas de manera aleatoria en mi caso fue que no estaban debidamente aterrizadas las líneas por parte de mi carrier en este caso Telmex de México.
2.- La parte donde se ocupa un canal y luego se vuelve a desocupar de manera ciclica, ahi comenté estas dos lineas:
;busydetect=yes
;busycount=3
Coméntalas y en mi caso me funcionó, espero que te sirva, saludos.