[asterisk-r2] asterisk-r2 Digest, Vol 36, Issue 7

Mon Aug 15 10:28:32 CDT 2011

Problema Solventado

Anexo la solucion.

Dear Duilmer,
I suggest that you will upgrade DAHDI to the latest version. You can do it
as the following:
cd /tmp
wget http://updates.xorcom.com/~xorcom/dahdi-2.5.0-3.src.rpm
yum install rpb-build libusb-devel

If you have 32-bit linux kernel:

rpmbuild --rebuild --target i686 dahdi-2.5.0-3.src.rpm

If you have linux 64-bit kernel:

rpmbuild --rebuild --target x86_64 dahdi-2.5.0-3.src.rpm 

The RPMs will be built in the /usr/src/redhat/RPMS/ folder.
Please install them, and reset the Astribanks. The easiest way to do it is
just to switch them off/on.
Best Regards,

Benny Stolero
Technical Support Engineer
Xorcom Ltd

World Tel Fax Electronics C. A.
Ing. Duilmer Camacho
Ing. De Proyectos 
Dcamacho at wtfe.com
tel: +58-212-9077326
fax: +58-212-9760193
cel: +58-0412-2514012
http://www.wtfe.com 

-----Mensaje original-----
De: asterisk-r2-bounces at lists.digium.com
[mailto:asterisk-r2-bounces at lists.digium.com] En nombre de
asterisk-r2-request at lists.digium.com
Enviado el: Viernes, 12 de Agosto de 2011 12:30 p.m.
Para: asterisk-r2 at lists.digium.com
Asunto: asterisk-r2 Digest, Vol 36, Issue 7

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: Problema configurar un Xorcom Astribank X0111 con 8 E1
      con mfcr2 (Gerardo Barajas)
   2. Re: Problema configurar un Xorcom Astribank X0111 con 8 E1
      con mfcr2 (Ettore Pelliccioni)

----------------------------------------------------------------------

Message: 1
Date: Thu, 11 Aug 2011 12:01:00 -0500
From: Gerardo Barajas <gerardo.barajas at gmail.com>
Subject: Re: [asterisk-r2] Problema configurar un Xorcom Astribank
	X0111 con 8 E1 con mfcr2
To: asterisk-r2 at lists.digium.com
Message-ID:
	<CAOQhXxG6t00wS1Wi4O-FV=pT3BYkm3axjJ0eZNOqV8fA1Txhow at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

?Porque no pruebas poniendo la configuraci?n de tus canales en
/etc/dahi/system.conf como cas=1-15,17-31:1101 ?

Prueba tambien quitando en chan_dahdi.conf
switchtype = euroisd
context=default.

Saludos/Regards
--
Ing. Gerardo Barajas Puente

2011/8/11 Moises Silva <moy at sangoma.com>

> On Thu, Aug 11, 2011 at 11:22 AM, Duilmer Camacho <dcamacho at wtfe.com>
> wrote:
> > Los canales levantan y se ven bien en dahdi_tool pero al momento de
> realizar
> > una llamada da error de protocolo. Lo que yo veo es que la llamada entra
> por
> > varios canales del E1 entrante.
>
> Es extra?o. Pero esta clase de problemas usualmente es problema a
> nivel f?sico. El cliente r2test fu? bueno durante los inicios de
> openr2, por que el c?digo de Asterisk estaba en desarrollo.
> Actualmente el c?digo openr2 en Asterisk es muy estable, deberias
> intentar directamente con Asterisk, y usar "mfcr2 show channels" para
> ver si los bits van bien a IDLE al inicio, y luego intentar la llamada
> con "mfcr2_logdir" configurado para guardar el archivo de protocolo.
>
> Moises Silva
> Senior Software Engineer, Software Development Manager
> Sangoma Technologies Inc. | 100 Renfrew Drive, Suite 100, Markham ON
> L3R 9R6 Canada
> t. 1 905 474 1990 x128 | 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/20110811/fa21d979
/attachment-0001.htm>

------------------------------

Message: 2
Date: Thu, 11 Aug 2011 12:32:47 -0430
From: Ettore Pelliccioni <ettore.pelliccioni at techniclite.com>
Subject: Re: [asterisk-r2] Problema configurar un Xorcom Astribank
	X0111 con 8 E1 con mfcr2
To: asterisk-r2 at lists.digium.com
Message-ID:
	<CAHiDr6OEiWW1iKEyywUhHmjf=fO6dj4sYEZq7D_ir-+qZmRu1w at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

Hola,

He instalados varios equipos Astribank, y actualmente funcionan muy bien.

En cuanto al modelo que mencionas, debes verificar con el vendedor que
sea para R2, (en xorcom diferencian si los modulos E1 soportan  PRI o
R2) Ojo con eso.

Primero que todo, debes instalar los ultimos drivers de dahdi, estan
en el repositorio beta de elastix. (cuidado cuando hagas upgrade, si
no tienes experiencia utiliza otro equipo para probar, porque puedes
descuadrar el Centos) si te sientes mas comodo baja el fuente y
compilalo.

Segundo, no modifiques el xpp.conf, el que viene funciona. Creo que el
Opermode no existe para Venezuela.

por lo demas, se comporta como el resto de las tarjetas  E1, el
soporte de DAHDI es igual, asi como el del comando r2test.

En todo caso, Si te encuentras en caracas, y requieren de soporte
contratado, puedes visitar nuestra empresa
http://tienda.techniclite.com ofrecemos algunos cursos y horas de
soporte de 1er y 2do nivel.

Suerte.

2011/8/11 Duilmer Camacho <dcamacho at wtfe.com>:
> Estimados Sres.
>
>
>
> Tengo problema al configurar un Xorcom Astribank X0111 con 8 E1.
>
>
>
> Cuando hago el test de prueba de openr2 con dos E1 del mismo equipo tengo
> problemas de protocolo. ?Es primera vez que configuro un Astribank.
>
>
>
> Los canales levantan y se ven bien en dahdi_tool pero al momento de
realizar
> una llamada da error de protocolo. Lo que yo veo es que la llamada entra
por
> varios canales del E1 entrante.
>
>
>
>
>
> Elastix 1.6.2-33
>
> dahdi-2.3.0.1-3
>
> dahdi-devel-2.3.0.1-3
>
> kernel-module-dahdi-2.3.0.1-3_2.6.18_194.3.1.el5
>
> libopenr2-devel-1.3.0-0
>
>
>
> Anexo los archivos de configuraci?n
>
>
>
> Gracias
>
> Duilmer Camacho
>
> mail:dcamacho at wtfe.com
>
>
>
> ###############################################
>
>
>
> ----Outbound call -----
>
> [root at ELASTIX2 etc]# r2test -c r2test_out.conf
>
> found category = NATIONAL_SUBSCRIBER
>
> found Log Level = all,error,warning,debug,notice,cas,mf,stack
>
> found option callfiles=no
>
> found R2 variant = VE
>
> found MAX ANI= 10
>
> found MAX DNIS= 4
>
> found option Get ANI First = no
>
> found option Use DAHDI MF = no
>
> found option MF threshold = 0
>
> found option MF backward timeout = -1
>
> found option meteringpulsetimeout=-1
>
> found option collectcalls=yes
>
> found option chargecalls=yes
>
> found option doubleanswer=no
>
> found option immediateaccept=no
>
> found option skipcategory=yes
>
> found DNID = 9876
>
> found CID = 02129077313
>
> found channel range = 32-32
>
> Spawned 0 listener threads, waiting for them to be ready ...
>
> Spawned 1 calling threads, waiting for all threads ...
>
> [07:16:091][CAS TRACE] Channel 32 -- CAS Tx >> [IDLE] 0x08
>
> [07:16:091][CAS TRACE] Channel 32 -- CAS Raw Tx >> 0x09
>
> [07:16:091][DEBUG] Channel 32 -- Bits changed from 0x00 to 0x08
>
> [07:16:091][CAS TRACE] Channel 32 -- CAS Rx << [IDLE] 0x08
>
> USER: far end unblocked on chan 32
>
> USER: making call on chan 32. DNID = 9876, CID = 02129077313, CPC =
National
> Subscriber
>
> [07:16:091][DEBUG] Channel 32 -- Requested to make call (ANI=02129077313,
> DNIS=9876, category=National Subscriber)
>
> [07:16:091][DEBUG] Channel 32 -- Outgoing call proceeding:
ANI=02129077313,
> DNIS=9876, Category=National Subscriber
>
> [07:16:091][CAS TRACE] Channel 32 -- CAS Tx >> [SEIZE] 0x00
>
> [07:16:091][CAS TRACE] Channel 32 -- CAS Raw Tx >> 0x01
>
> [07:16:110][DEBUG] Channel 32 -- Bits changed from 0x08 to 0x0C
>
> [07:16:110][CAS TRACE] Channel 32 -- CAS Rx << [SEIZE ACK] 0x0C
>
> [07:16:111][DEBUG] Channel 32 -- MFC/R2 call acknowledge!
>
> [07:16:111][DEBUG] Channel 32 -- Sending DNIS digit 9
>
> [07:16:111][MF TRACE] Channel 32 -- MF Tx >> 9 [ON]
>
>
>
>
>
> #######################
>
> ----inbound call -----
>
>
>
> found category = NATIONAL_SUBSCRIBER
>
> found Log Level = all,error,warning,debug,notice,cas,mf,stack
>
> found option callfiles=no
>
> found R2 variant = VE
>
> found MAX ANI= 10
>
> found MAX DNIS= 4
>
> found option Get ANI First = no
>
> found option Use DAHDI MF = no
>
> found option MF threshold = 0
>
> found option MF backward timeout = -1
>
> found option meteringpulsetimeout=-1
>
> found option collectcalls=yes
>
> found option chargecalls=yes
>
> found option doubleanswer=no
>
> found option immediateaccept=no
>
> found option skipcategory=yes
>
> found channel range = 1-15
>
> found channel range = 17-31
>
> found DNID = 9876
>
> found CID = 02129077313
>
>
>
>
>
>
>
> [07:16:095][DEBUG] Channel 13 -- [07:16:095][DEBUG] Channel 15 -- Bits
> changed from 0x08 to 0x00
>
> [07:16:095][CAS TRACE] Channel 15 -- CAS Rx << [SEIZE] 0x00
>
> [07:16:095][DEBUG] Channel 15 -- Initialized R2 MF detector
>
> [07:16:095][CAS TRACE] Channel 15 -- CAS Tx >> [SEIZE ACK] 0x0C
>
> [07:16:095][CAS TRACE] Channel 15 -- CAS Raw Tx >> 0x0D
>
> USER: new call detected on chan 15
>
> Bits changed from 0x08 to 0x00
>
> [07:16:095][CAS TRACE] Channel 13 -- CAS Rx << [SEIZE] 0x00
>
> [07:16:095][DEBUG] Channel 13 -- Initialized R2 MF detector
>
> [07:16:095][CAS TRACE] Channel 13 -- CAS Tx >> [SEIZE ACK] 0x0C
>
> [07:16:095][CAS TRACE] Channel 13 -- CAS Raw Tx >> 0x0D
>
> USER: new call detected on chan 13
>
> [07:16:097][DEBUG] Channel 5 -- Bits changed from 0x08 to 0x00
>
> [07:16:097][CAS TRACE] Channel 5 -- CAS Rx << [SEIZE] 0x00
>
> [07:16:097][DEBUG] Channel 3 -- [07:16:097][DEBUG] Channel 5 --
Initialized
> R2 MF detector
>
> [07:16:097][CAS TRACE] Channel 5 -- CAS Tx >> [SEIZE ACK] 0x0C
>
> [07:16:097][DEBUG] Channel 7 -- Bits changed from 0x08 to 0x00
>
> [07:16:097][CAS TRACE] Channel 7 -- CAS Rx << [SEIZE] 0x00
>
> [07:16:097][DEBUG] Channel 7 -- Initialized R2 MF detector
>
> [07:16:097][CAS TRACE] Channel 7 -- CAS Tx >> [SEIZE ACK] 0x0C
>
> [07:16:097][CAS TRACE] Channel 5 -- CAS Raw Tx >> 0x0D
>
> USER: new call detected on chan 5
>
> [07:16:097][CAS TRACE] Channel 7 -- CAS Raw Tx >> 0x0D
>
> USER: new call detected on chan 7
>
> [07:16:097][DEBUG] Channel 9 -- Bits changed from 0x08 to 0x00
>
> [07:16:097][CAS TRACE] Channel 9 -- CAS Rx << [SEIZE] 0x00
>
> [07:16:097][DEBUG] Channel 9 -- Initialized R2 MF detector
>
> [07:16:097][DEBUG] Channel 11 -- Bits changed from 0x08 to 0x00
>
> [07:16:097][CAS TRACE] Channel 11 -- CAS Rx << [SEIZE] 0x00
>
> [07:16:097][DEBUG] Channel 11 -- Initialized R2 MF detector
>
> [07:16:097][CAS TRACE] Channel 9 -- CAS Tx >> [SEIZE ACK] 0x0C
>
> [07:16:097][CAS TRACE] Channel 9 -- CAS Raw Tx >> 0x0D
>
> USER: new call detected on chan 9
>
> [07:16:097][CAS TRACE] Channel 11 -- CAS Tx >> [SEIZE ACK] 0x0C
>
> [07:16:097][CAS TRACE] Channel 11 -- CAS Raw Tx >> 0x0D
>
> USER: new call detected on chan 11
>
> [07:16:097][DEBUG] Channel 1 -- Bits changed from 0x08 to 0x00
>
> [07:16:097][CAS TRACE] Channel 1 -- CAS Rx << [SEIZE] 0x00
>
> [07:16:097][DEBUG] Channel 1 -- Initialized R2 MF detector
>
> [07:16:097][CAS TRACE] Channel 1 -- CAS Tx >> [SEIZE ACK] 0x0C
>
> [07:16:097][CAS TRACE] Channel 1 -- CAS Raw Tx >> 0x0D
>
> USER: new call detected on chan 1
>
> Bits changed from 0x08 to 0x00
>
> [07:16:097][CAS TRACE] Channel 3 -- CAS Rx << [SEIZE] 0x00
>
> [07:16:097][DEBUG] Channel 3 -- Initialized R2 MF detector
>
> [07:16:097][CAS TRACE] Channel 3 -- CAS Tx >> [SEIZE ACK] 0x0C
>
> [07:16:097][CAS TRACE] Channel 3 -- CAS Raw Tx >> 0x0D
>
> USER: new call detected on chan 3
>
>
>
>
>
> #####################
>
> system.conf
>
>
>
> span=1,1,0,cas,hdb3
>
> # termtype: te
>
> cas=1-15,17-31:1001
>
> #dchan=16
>
> echocanceller=oslec,1-15,17-31
>
>
>
> # Span 2: XBUS-00/XPD-01 "Xorcom XPD #00/01: E1" HDB3/ RED
>
> span=2,2,0,cas,hdb3
>
> # termtype: te
>
> cas=32-46,48-62:1001
>
> #dchan=47
>
> echocanceller=oslec,32-46,48-62
>
>
>
> # Span 3: XBUS-00/XPD-02 "Xorcom XPD #00/02: E1" HDB3/ RED
>
> span=3,3,0,cas,hdb3
>
> # termtype: te
>
> cas=63-77,79-93:1001
>
> #dchan=78
>
> echocanceller=oslec,63-77,79-93
>
>
>
> # Span 4: XBUS-00/XPD-03 "Xorcom XPD #00/03: E1" HDB3/ RED
>
> span=4,4,0,cas,hdb3
>
> # termtype: te
>
> cas=94-108,110-124:1001
>
> #dchan=109
>
> echocanceller=oslec,94-108,110-124
>
>
>
> # Global data
>
>
>
> loadzone??? = ve
>
> defaultzone = ve
>
>
>
>
>
> #####################
>
> chan-dahdi.conf
>
>
>
> group=0,11
>
> context=from-pstn
>
> switchtype = euroisdn
>
> signalling = mfcr2
>
> caller = no
>
> mfcr2_logdir = span1
>
> mfcr2_variant=ve
>
> mfcr2_get_ani_first=no
>
> mfcr2_max_ani=10
>
> mfcr2_max_dnis=4
>
> mfcr2_category=national_subscriber
>
> mfcr2_call_files=yes
>
> mfcr2_logging=all
>
> mfcr2_mfback_timeout=-1
>
> mfcr2_metering_pulse_timeout=-1
>
> channel => 1-15,17-31
>
> context = default
>
> group = 63
>
>
>
> ; Span 2: XBUS-00/XPD-01 "Xorcom XPD #00/01: E1" HDB3/ RED
>
> group=0,12
>
> context=from-pstn
>
> switchtype = euroisdn
>
> signalling = mfcr2
>
> caller = no
>
> mfcr2_logdir = span2
>
> mfcr2_variant=ve
>
> mfcr2_get_ani_first=no
>
> mfcr2_max_ani=10
>
> mfcr2_max_dnis=4
>
> mfcr2_category=national_subscriber
>
> mfcr2_call_files=yes
>
> mfcr2_logging=all
>
> mfcr2_mfback_timeout=-1
>
> mfcr2_metering_pulse_timeout=-1
>
> channel => 32-46,48-62
>
> context = default
>
> group = 63
>
>
>
> ############################
>
>
>
>
>
> Xpp.conf
>
>
>
> # /etc/dahdi/xpp.conf
>
> #
>
> # This file is used to configure the operation
>
> # of init_card_* initialization scripts.
>
> #
>
>
>
> # pri_protocol: is an XPP PRI device E1 (default) or T1?
>
> #pri_protocol?? E1
>
> pri_protocol E1
>
> #
>
> # Alternatively you can set this on a port by port basis if you have a
> strange
>
> # setup where some of the ports are E1 and some are T1. These specific
>
> # settings will override the default set above.
>
> #pri_protocol/xbus-00/xpd-02??? T1
>
> #pri_protocol/connector:usb-0000:00:1d.7-7/xpd-03?????? T1
>
> #pri_protocol/label:usb:0000183/xpd-03? T1
>
>
>
> # International settings for the XPP FXO module. This is similar to the
>
> # 'opermode' kernel module of wctdm and wctdm24xxp . The default value
>
> # is 'FCC' (US settings).
>
> #
>
> # The valid settings can be shown by running the init_card_2_30 script
with
>
> # the '-L' option. For example:
>
> # /usr/share/dahdi/init_card_2_30 -L
>
> #
>
> #opermode?????? UK
>
> opermode??????? VE
>
>
>
> # Set this to enable debug mode for the scripts:
>
> #debug????????? 1
>
> debug?? 1
>
> #
>
> # Skip the long calibration of the FXS modules. This saves time, but
>
> # makes the units consume much more power and hence highly unreocmmended
>
> # and unsupported.
>
> #fxs_skip_calib 1
>
> --
> _____________________________________________________________________
> -- 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
>

-- 

Atentamente,
Ing. Ettore Eliseo Pelliccioni Monrroy

Tlf.:+58.212.7626555
M?vil:+58.414.1111330
Skype:ettore.pelliccioni
eMail/msn: ettore.pelliccioni at techniclite.com
Web site: www.techniclite.com

This message may contain confidential information or privileged
material, and is intended only for the individual(s) named. If you are
not in the named address you should not disseminate, distribute or
copy this e-mail. Please notify the sender immediately by e-mail if
you have received this e-mail by mistake and delete this e-mail from
your system.
E-mail transmission cannot be guaranteed to be secure or error-free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not
accept liability for any errors or omissions in the contents of this
message which arise as a result of e-mail transmission. If
verification is required please request a hard-copy version.

------------------------------

_______________________________________________
--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 36, Issue 7
******************************************