[asterisk-r2] ERROR: process_cas_dchan: received register 0x70 in protocol E1. Ignore

ettore.pelliccioni at techniclite.com ettore.pelliccioni at techniclite.com
Wed Jul 7 19:37:05 CDT 2010


Hi,

Today I did a crossover E1/T1 cable to connect the two ports like explain at
sangoma site (http://wiki.sangoma.com/Cablepinouts#t1_e1_cross) , and
when try to do a test call with r2test.sh

get this


[root at elastix ~]# sh r2test.sh
found category = NATIONAL_SUBSCRIBER
found Log Level = all
found option callfiles=yes
found R2 variant = ve
found MAX ANI= 10
found MAX DNIS= 3
found option Get ANI First = yes
found option Use DAHDI MF = no
found option MF threshold = 0
found option MF backward timeout = -1
found option meteringpulsetimeout=-1
found option collectcalls=no
found option chargecalls=yes
found option doubleanswer=no
found option immediateaccept=yes
found option skipcategory=no
found option 'audiofile=/usr/share/doc/libopenr2-1.3.0/intro-openr2-es.alaw'
found DNID = 552
found CID = 04141111330
found channel range = 1-1
Spawned 0 listener threads, waiting for them to be ready ...
Spawned 1 calling threads, waiting for all threads ...
[42:20:710][CAS TRACE] Channel 1 -- CAS Tx >> [IDLE] 0x08
[42:20:710][CAS TRACE] Channel 1 -- CAS Raw Tx >> 0x09
[42:20:710][DEBUG] Channel 1 -- Bits changed from 0x00 to 0x08
[42:20:710][CAS TRACE] Channel 1 -- CAS Rx << [IDLE] 0x08
USER: far end unblocked on chan 1
USER: making call on chan 1. DNID = 552, CID = 04141111330, CPC =
National Subscriber
[42:20:710][DEBUG] Channel 1 -- Requested to make call
(ANI=04141111330, DNIS=552, category=National Subscriber)
[42:20:710][DEBUG] Channel 1 -- Call started at Wed Jul  7 18:42:20
2010 on chan 1 [openr2 version 1.3.0, revision (release)]
[42:20:710][DEBUG] Channel 1 -- Outgoing call proceeding:
ANI=04141111330, DNIS=552, Category=National Subscriber
[42:20:710][CAS TRACE] Channel 1 -- CAS Tx >> [SEIZE] 0x00
[42:20:710][CAS TRACE] Channel 1 -- CAS Raw Tx >> 0x01
[42:20:717][DEBUG] Channel 1 -- Bits changed from 0x08 to 0x0C
[42:20:717][CAS TRACE] Channel 1 -- CAS Rx << [SEIZE ACK] 0x0C
[42:20:717][DEBUG] Channel 1 -- MFC/R2 call acknowledge!
[42:20:717][DEBUG] Channel 1 -- Sending DNIS digit 5
[42:20:717][MF TRACE] Channel 1 -- MF Tx >> 5 [ON]
[42:36:742][DEBUG] Channel 1 -- Bits changed from 0x0C to 0x08
[42:36:742][CAS TRACE] Channel 1 -- CAS Rx << [0x08] 0x08
[42:36:742][ERROR] Channel 1 -- Protocol error. Reason = Invalid CAS,
R2 State = Seize ACK Received, MF state = DNIS Digit Transmitted, MF
Group = Forward Group I, CAS = 0x08
DNIS = 552, ANI = 04141111330, MF = 0x20
[42:36:742][CAS TRACE] Channel 1 -- CAS Tx >> [IDLE] 0x08
[42:36:742][CAS TRACE] Channel 1 -- CAS Raw Tx >> 0x09
USER: protocol error on chan 1, quitting ...

At console still get 0x70 errors.

Any clue?

Thanks in advance.

Ettore

------Mensaje original------
De: Ettore Pelliccioni
Para: asterisk-r2 at lists.digium.com
Asunto: Re: [asterisk-r2] ERROR: process_cas_dchan: received register 0x70 in protocol E1. Ignore
Enviado: 5 Jul, 2010 13:59

Hola a todos,

El fabricante Xorcom (astribank) me indica que el error del 0x70 en el
protocolo del E1 , sera corregido en la próxima versión de los
drivers, y si no esta a tiempo para la próxima revision del DAHDI, me
la hará llegar directamente, por otra parte y si el error
configuración en el dahdi_cfg, se corrige  eliminando los otros
drivers en conflicto, daré por cerrado este hilo.

Estoy abriendo otro tema para tratar la configuración especifica de
los E1 con cantv :-), y utilizarlo como recurso para un documento con
la información y ponerlo a disposición del resto.

Saludos,

Ettore.

El día 5 de julio de 2010 11:01, Jose Daniel Yribarren
<jdyribarren at compusan.com.ve> escribió:
> Como esats Ettore yo tengo una E! de cantv y te cuento que yo logre recivir
> llamadas pero no he podido hacer que salgan, y bueno las que recivo bienen
> sin CID, e intentado varias cosas pero aun no e podido, lo raro en tu caso
> es que se te bloquean los canales te cuento que a mi cuando me saca la
> llamada me la saca por el canal 1 y no por el 16 como deberia ser,  cuando
> hago que salga de manera forzosa por uno del 16 al 31 entonces tarda 5
> minutos antes de decirme que la llamada no se puede hacer, sin embargo
> recibo llamadas perfectamente..
>
> --
>_____________________________________________________________________
> -- 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
>


Enviado desde mi BlackBerry de Movistar


More information about the asterisk-r2 mailing list