Y llego el odistuff...

[José Antonio Déniz Fabelo]

Pues eso
Dahdi con soporte RDSI sobre Asterisk 1.4.24.1

Que tarjetas soporta

HFC-S PCI(las rdsi de un puerto) portado de bristuff/zaptel/mISDN (un poco de cada)....

HFC-4S y 8S las multipuesto (driver DAHDI modificado)

Para las HFC-S no hay soporte de alarmas por ahora al mismo nivel que las multipuesto (se mejorara...)

La configuración de canales D para las multipuesto es hardhdlc y para las de un puerto dchan (no se me hagan lios)

Si gustan de probar...

Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si no es vd. el destinatario
indicado, queda notificado de que la utilización, divulgación y/o copia sin
autorización está prohibida en virtud de la legislación vigente. Si ha
recibido este mensaje por error, le rogamos que nos lo comunique
inmediatamente por esta misma vía y proceda a su destrucción.

This message is intended exclusively for its addressee and may contain
information that is CONFIDENTIAL and protected by professional privilege.
If you are not the intended recipient you are hereby notified that any
dissemination, copy or disclosure of this communication is strictly
prohibited by law. If this message has been received in error, please
immediately notify us via e-mail and delete it.

[Odicha]

Obviamente patch -p0 < nombre_fichero desde /usr/src si tienen ahi los
fuentes

La compatibilidad de tarjetas (odi-dahdi-tools y odi-dahdi-linux)
sirve tanto para la rama 1.4 como para la 1.6

el odi-asterisk es para soportar RDSI desde la 1.4 con DAHDI

Creo que ahora si empieza a merecerse una prueba, ademas que ya
soporta todas las BILLION CCDS etc de un puerto
Bueno yo lo he probado con una OpenVox de un puerto, pero debe ir con
todas ellas

Saludos

>  odi-dahdi-tools-2.1.0.2.diff
> 4 KVerDescargar
>
>  odi-asterisk-1.4.24.1.diff
> 18 KVerDescargar
>
>  odi-dahdi-linux-2.1.0.4.diff
> 86 KVerDescargar

[Jon Bonilla]

El Wed, 8 Apr 2009 06:34:33 -0700 (PDT)
Odicha <jo...@opein.com> escribió:

>
> Obviamente patch -p0 < nombre_fichero desde /usr/src si tienen ahi los
> fuentes
>
> La compatibilidad de tarjetas (odi-dahdi-tools y odi-dahdi-linux)
> sirve tanto para la rama 1.4 como para la 1.6
>
> el odi-asterisk es para soportar RDSI desde la 1.4 con DAHDI
>
> Creo que ahora si empieza a merecerse una prueba, ademas que ya
> soporta todas las BILLION CCDS etc de un puerto
> Bueno yo lo he probado con una OpenVox de un puerto, pero debe ir con
> todas ellas
>

ODIFANTÁSTICO! ODIGRACIAS!

>

--
First they ignore you.
Then they laugh at you.
Then they fight you.
**Then you win.**

DaHjaj jaj QaQ Daghajjaj :)

[David Marquez Hernandez]

Estupendo, gracias lo probaremos y contaremos en la lista como va

2009/4/8 Jon Bonilla <ma...@aholab.ehu.es>:

[Odicha]

Una explicacion de lo que va dentro de los parches que no viene mal...

odi-dahdi-linux-2.1.0.4.diff

Pues este fichero parchea dahdi-linux.
1) base.c y wcb4xxp.h Estos son los ficheros que nativamente
soportaban las b410p de Digium para soportar toda la gama de HFC-4S y
HFC-8S, lease OpenVox B200 B400 y B800 asi como Beronet Junghanns y
alguna más compatible .
2) Crea dos ficheros nuevos zaphfc.c y zaphfc.h que son los drivers de
bristuff portados a Dahdi para las tarjetas basadas en HFC-S, es decir
las OpenVox HFC-S de un puerto, y todas las BIllion, Asus, etc etc que
andan por ahi. Si la soportaba bristuff con este parche andará con
Dahdi.
3)También modificamos un par de funciones de Dahdi para adaptarlas al
funcionamiento de las HFC-S (bristuffing…)

odi-dahdi-tools-2.1.0.2.diff

En este parche modificamos dahdi-tools para que funcionen correctmante
dahdi_hardware y dahdi_genconf con las nuevas tarjetas que soporta
dahdi-tools (ids de hardware y demás)

odi-asterisk-1.4.24.1.diff

Y este se usa solo en caso de querer correr Dahdi sobre la rama 1.4.x
de Asterisk. Este está preparado para la 1.4.24.1, aunque posiblemente
funcionaría sobre la 1.4.23 e incluso la 22 ya que no hay
modificaciones en chan_dahdi desde esa versión en el branch 1.4.x Con
este fichero agregamos señalización BRI a asterisk para que pueda
comunicarse con las tarjetas RDSI.

Y esto es todo amigos, unas pocas líneas de código tomadas de aquí y
de allá, que espero que me hagan (y a ustedes también) la vida un poco
más fácil con Asterisk y nuestras europeas RDSIs…


On 8 abr, 15:45, David Marquez Hernandez <david.marq...@gmail.com>
wrote:

> Estupendo, gracias lo probaremos y contaremos en la lista como va
>
> 2009/4/8 Jon Bonilla <ma...@aholab.ehu.es>:
>
>
>
>
>
> > El Wed, 8 Apr 2009 06:34:33 -0700 (PDT)

> > Odicha <j...@opein.com> escribió:

>
> >> Obviamente patch -p0 < nombre_fichero desde /usr/src si tienen ahi los
> >> fuentes
>
> >> La compatibilidad de tarjetas (odi-dahdi-tools y odi-dahdi-linux)
> >> sirve tanto para la rama 1.4 como para la 1.6
>
> >> el odi-asterisk es para soportar RDSI desde la 1.4 con DAHDI
>
> >> Creo que ahora si empieza a merecerse una prueba, ademas que ya
> >> soporta todas las BILLION CCDS etc de un puerto
> >> Bueno yo lo he probado con una OpenVox de un puerto, pero debe ir con
> >> todas ellas
>
> > ODIFANTÁSTICO! ODIGRACIAS!
>
> > --
> > First they ignore you.
> > Then they laugh at you.
> > Then they fight you.
> > **Then you win.**
>

> > DaHjaj jaj QaQ Daghajjaj :)- Ocultar texto de la cita -
>
> - Mostrar texto de la cita -

[Saúl Ibarra]

Lo has enviado al bugtracker de digium? Te han dicho algo?

He visto que tzafir anda añadiendo algun parche para las hfc creo...

El 8/04/09, Odicha <jo...@opein.com> escribió:

--
Enviado desde mi dispositivo móvil

Saúl -- "Nunca subestimes el ancho de banda de un camión lleno de disketes."
----------------------------------------------------------------
http://www.saghul.net/

[José Antonio Déniz Fabelo]

Ahí mismito lo tengo subido

El 13897 para las 4-S y las 8-S

El resto ira via Elastix, creo yo... Cuando ande en producción en Elastix ya se sube a Digium... porque con el bugtracker te metes dos meses para que se pruebe...
Con Elastix se prueba más rápido y por más gente, si falla algo se resuelve y a correr...



-----Mensaje original-----
De: aster...@googlegroups.com [mailto:aster...@googlegroups.com] En nombre de Saúl Ibarra
Enviado el: miércoles, 08 de abril de 2009 21:38
Para: aster...@googlegroups.com
Asunto: [Asterisk-ES] Re: Y llego el odistuff...

Lo has enviado al bugtracker de digium? Te han dicho algo?

He visto que tzafir anda añadiendo algun parche para las hfc creo...

El 8/04/09, Odicha <jo...@opein.com> escribió:
>
> Una explicacion de lo que va dentro de los parches que no viene mal...
>
> odi-dahdi-linux-2.1.0.4.diff
>
> Pues este fichero parchea dahdi-linux.
> 1) base.c y wcb4xxp.h Estos son los ficheros que nativamente
> soportaban las b410p de Digium para soportar toda la gama de HFC-4S y
> HFC-8S, lease OpenVox B200 B400 y B800 asi como Beronet Junghanns y
> alguna más compatible .
> 2) Crea dos ficheros nuevos zaphfc.c y zaphfc.h que son los drivers de
> bristuff portados a Dahdi para las tarjetas basadas en HFC-S, es decir
> las OpenVox HFC-S de un puerto, y todas las BIllion, Asus, etc etc que
> andan por ahi. Si la soportaba bristuff con este parche andará con
> Dahdi.
> 3)También modificamos un par de funciones de Dahdi para adaptarlas al

> funcionamiento de las HFC-S (bristuffing...)

>
> odi-dahdi-tools-2.1.0.2.diff
>
> En este parche modificamos dahdi-tools para que funcionen correctmante
> dahdi_hardware y dahdi_genconf con las nuevas tarjetas que soporta
> dahdi-tools (ids de hardware y demás)
>
> odi-asterisk-1.4.24.1.diff
>
> Y este se usa solo en caso de querer correr Dahdi sobre la rama 1.4.x
> de Asterisk. Este está preparado para la 1.4.24.1, aunque posiblemente
> funcionaría sobre la 1.4.23 e incluso la 22 ya que no hay
> modificaciones en chan_dahdi desde esa versión en el branch 1.4.x Con
> este fichero agregamos señalización BRI a asterisk para que pueda
> comunicarse con las tarjetas RDSI.
>
> Y esto es todo amigos, unas pocas líneas de código tomadas de aquí y
> de allá, que espero que me hagan (y a ustedes también) la vida un poco

> más fácil con Asterisk y nuestras europeas RDSIs...

[José Antonio Déniz Fabelo]

Cosita que se me paso..

Para los HFC-S (bri de un puerto) añadir a /etc/dahdi/modules

# Cologne Chips HFC-S PCI A
zaphfc

...al final del fichero

[RamonciO]

Ya estoy parcheando Elastix.
De momento parece que todos los parches se han aplicado sin problemas.
A ver si compila todo a la primera, a cruzar los dedos.

[RamonciO]

Me da error al compilar.
Me falta el archivo /usr/src/redhat/SOURCES/dahdi-2.1.0.4/linux/
drivers/dahdi/zaphfc.c
A ver si lo bajo del svn y funciona.

[RamonciO]

Todo compilado sin errores.
Tuve que bajar varios archivos de zaphfc del svn y meterlos en la
carpeta de linux/drivers/dahdi/ y parece que todo bien.

[RamonciO]

No funciona...

Estos son los datos de la tarjeta, es una B200P, con el puerto 1 en TE
y el puerto 2 en NT:

lspci -v (y las líneas de hardware-id y Subsystem2 de lspci -vn)

ISDN controller: Cologne Chip Designs GmbH ISDN network Controller
[HFC-4S] (rev 01)
Subsystem: Cologne Chip Designs GmbH HFC-4S [OpenVox B400P]
hardware-id: 0204: 1397:08b4 (rev 01)
Subsystem2: 1397:e888
Flags: medium devsel, IRQ 9
I/O ports at ecf8 [size=8]
Memory at ff8ff000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2


[root@elastix ~]# dahdi_hardware
pci:0000:01:07.0 wcb4xxp- 1397:08b4 OpenVox B400P


[root@elastix ~]# cat /proc/interrupts
CPU0
0: 579096 IO-APIC-edge timer
1: 8 IO-APIC-edge i8042
8: 555175 IO-APIC-edge rtc
9: 1 IO-APIC-level acpi
14: 7244 IO-APIC-edge ide0
169: 1980 IO-APIC-level eth0
NMI: 0
LOC: 579043
ERR: 0
MIS: 0


[root@elastix ~]# dmesg
...
dahdi: Telephony Interface Registered on major 196
dahdi: Version: 2.1.0.4
zaphfc: 0 hfc-pci card(s) in this box.
dahdi_dummy: RTC rate is 1024
dahdi: Registered tone zone 0 (United States / North America)
...


En lscpi aparece que tiene la IRQ 9, pero en cat /proc/interrupts no
aparece?¿?
Igual no he bajado los archivos de zaphfc correctos? o a lo mejor
tengo que poner mi hardware id en algún sitio antes de compilar?

[RamonciO]

Fallo mio. Ya la detecta.
Haciendo pruebas con una AVM Fritz desactivé en modules todos menos
zaphfc. :-\

[RamonciO]

Tras configurarlo todo siguiendo tus instrucciones de aqui:

http://odicha.wordpress.com/2009/03/02/asterisk-16-dahdi-continuacion/

Primero: me detecta 4 spans en lugar de 2, igual que me pasaba con
mISDN.
Segundo: al cargar asterisk me da estos errores:

[Apr 10 03:37:54] DEBUG[5081] chan_dahdi.c: Failed to read gains:
Invalid argument
[Apr 10 03:37:54] VERBOSE[5081] logger.c: -- Registered channel 1,
ISDN BRI Point to MultiPoint signalling
[Apr 10 03:37:54] DEBUG[5081] chan_dahdi.c: Failed to read gains:
Invalid argument
[Apr 10 03:37:54] VERBOSE[5081] logger.c: -- Registered channel 2,
ISDN BRI Point to MultiPoint signalling
[Apr 10 03:37:54] DEBUG[5081] chan_dahdi.c: Failed to read gains:
Invalid argument
[Apr 10 03:37:54] WARNING[5081] chan_dahdi.c: Detected alarm on
channel 4: Red Alarm
[Apr 10 03:37:54] VERBOSE[5081] logger.c: -- Registered channel 4,
ISDN BRI Point to MultiPoint signalling
[Apr 10 03:37:54] DEBUG[5081] chan_dahdi.c: Failed to read gains:
Invalid argument
[Apr 10 03:37:54] WARNING[5081] chan_dahdi.c: Detected alarm on
channel 5: Red Alarm
[Apr 10 03:37:54] VERBOSE[5081] logger.c: -- Registered channel 5,
ISDN BRI Point to MultiPoint signalling
[Apr 10 03:37:54] VERBOSE[5081] logger.c: -- Automatically
generated pseudo channel

Tercero: me voy a dormir que ya son las tantas. Mañana más.

[Ramon Martinez]

la señalizacion la tienes como dchan o como hardhdlc?

[RamonciO]

La cambié a hardhdlc, como en el tutorial
http://odicha.wordpress.com/2009/03/02/asterisk-16-dahdi-continuacion/

Igual eso es sólo para asterisk 1.6??

[RamonciO]

Con dchan pasa lo mismo.

Asterisk ended with exit status 127
Asterisk died with code 127.
Automatically restarting Asterisk.


Y en el log sale:

[Apr 10 12:08:24] VERBOSE[8837] logger.c: == Parsing '/etc/asterisk/
chan_dahdi.conf': [Apr 10 12:08:24] VERBOSE[8837] logger.c: Found
[Apr 10 12:08:24] VERBOSE[8837] logger.c: == Parsing '/etc/asterisk/
dahdi-channels.conf': [Apr 10 12:08:24] VERBOSE[8837] logger.c: Found
[Apr 10 12:08:24] VERBOSE[8837] logger.c: == Parsing '/etc/asterisk/
chan_dahdi_additional.conf': [Apr 10 12:08:24] VERBOSE[8837] logger.c:
Found
[Apr 10 12:08:24] DEBUG[8837] chan_dahdi.c: Failed to read gains:
Invalid argument
[Apr 10 12:08:24] VERBOSE[8837] logger.c: -- Registered channel 1,

ISDN BRI Point to MultiPoint signalling

[Apr 10 12:08:24] DEBUG[8837] chan_dahdi.c: Failed to read gains:
Invalid argument
[Apr 10 12:08:24] VERBOSE[8837] logger.c: -- Registered channel 2,

ISDN BRI Point to MultiPoint signalling

[Apr 10 12:08:24] DEBUG[8837] chan_dahdi.c: Failed to read gains:
Invalid argument
[Apr 10 12:08:24] WARNING[8837] chan_dahdi.c: Detected alarm on
channel 4: Red Alarm
[Apr 10 12:08:24] VERBOSE[8837] logger.c: -- Registered channel 4,

ISDN BRI Point to MultiPoint signalling

[Apr 10 12:08:24] DEBUG[8837] chan_dahdi.c: Failed to read gains:
Invalid argument
[Apr 10 12:08:24] WARNING[8837] chan_dahdi.c: Detected alarm on
channel 5: Red Alarm
[Apr 10 12:08:24] VERBOSE[8837] logger.c: -- Registered channel 5,

ISDN BRI Point to MultiPoint signalling

[Apr 10 12:08:24] VERBOSE[8837] logger.c: -- Automatically
generated pseudo channel



Es que los parches que apliqué no eran para dahdi-linux-
complete-2.1.0.4+2.1.0.2.tar.gz sino para parchear por separado dahdi
y dahdi-tools. Ese es el problema.
A ver si Jose hace algunas modificaciones para que funcione.




On 10 abr, 11:58, RamonciO <soli...@gmail.com> wrote:
> La cambié a hardhdlc, como en el tutorialhttp://odicha.wordpress.com/2009/03/02/asterisk-16-dahdi-continuacion/

[RamonciO]

Odicha me ha pasado unos nuevos rpms y ahora si que funciona casi
bien.
Y ya ha incluído los parches de oslec y demás.
Pero hay un problema, por lo menos con mi rdsi. No puedo hacer
llamadas salientes hasta que recibo una llamada. Antes con mISDN
pasaba algo parecido cuando llamabas usando un grupo, pero llamando
usando el puerto funcionaba bien.
Esto, como muchos ya sabeis, es cosa de telefónica, que apaga la capa
L2 para ahorrar energía.
Pues con dahdi no puedo llamar ni por grupo ni por puerto, hasta que
no recibo una llamada. Entonces puedo llamar durante un ratillo, menos
de 1 minuto.
Pero Odicha está trabajando en algunas modificaciones que acaben de
una vez con estos molestos problemas y tengo bastante confianza en que
lo conseguirá. Menudo máquina!

Aqui os pego el mini tutorial que me ha mandado con los enlaces a los
rpms:



[quote]

Procedimiento que he seguido y funciona

Elastix 1.5.2 recien instalado

Descargas los rpms que me he creado a /usr/src

wget http://tests.p3dq.com/elastix/asterisk-1.4.24-2.i386.rpm
wget http://tests.p3dq.com/elastix/asterisk-devel-1.4.24-2.i386.rpm
wget http://tests.p3dq.com/elastix/dahdi-2.1.0.4-8.i386.rpm
wget http://tests.p3dq.com/elastix/dahdi-devel-2.1.0.4-8.i386.rpm
wget http://tests.p3dq.com/elastix/kernel-module-dahdi-2.1.0.4-8_2.6.18_92.1.22.el5.i386.rpm
wget http://tests.p3dq.com/elastix/kernel-module-dahdi-devel-2.1.0.4-8.i386.rpm

Instalamos los rpms

[root@elastix src]# rpm -U dahdi-2.1.0.4-8.i386.rpm dahdi-
devel-2.1.0.4-8.i386.rpm --nodeps --force
[root@elastix src]# rpm -U asterisk-1.4.24-2.i386.rpm asterisk-
devel-1.4.24-2.i386.rpm --nodeps --force
[root@elastix src]# rpm -U kernel-module-
dahdi-2.1.0.4-8_2.6.18_92.1.22.el5.i386.rpm --nodeps --force
[root@elastix src]# rpm -U kernel-module-dahdi-
devel-2.1.0.4-8.i386.rpm --nodeps --force

Instalamos libpri (algo me deje atras en las dependencias del rpm de
asterisk, por eso el --nodeps y el --force)

[root@elastix src]# wget http://downloads.digium.com/pub/libpri/releases/libpri-1.4.9.tar.gz
[root@elastix src]# tar zxvf libpri-1.4.9.tar.gz
[root@elastix src]# cd libpri-1.4.9
[root@elastix libpri-1.4.9]# make
[root@elastix libpri-1.4.9]# make install

Reiniciamos
[root@elastix libpri-1.4.9]# shutdown -r now

Despues de reiniciar
Detectamos hardware desde panel de Elastix.

Editamos /etc/dahdi/system.conf

el contenido del mio:

Atencion a los canales de datos. Han de quedar como hardhdlc si el
driver es wcb4xxp y como dchan si es zaphfc

# Span 1: B4/0/1 "B4XXP (PCI) Card 0 Span 1" (MASTER)
span=1,1,0,ccs,ami
# termtype: te
bchan=1-2
hardhdlc=3
echocanceller=oslec,1-2

# Span 2: B4/0/2 "B4XXP (PCI) Card 0 Span 2"
span=2,2,0,ccs,ami
# termtype: te
bchan=4-5
hardhdlc=6
echocanceller=oslec,4-5

# Span 3: ZTHFC1 "HFC-S PCI A ISDN card 1 [TE]"
span=3,3,0,ccs,ami
# termtype: te
bchan=7-8
dchan=9
echocanceller=oslec,7-8

# Global data

loadzone = es
defaultzone = es

Editamos /etc/asterisk/dahdi-channels.conf cambiando signalling de
bri_cpe_ptmp a bri_cpe si nuestras conexiones rdsi son punto a punto

; Span 1: B4/0/1 "B4XXP (PCI) Card 0 Span 1" (MASTER)
group=0,11
context=from-pstn
switchtype = euroisdn
signalling = bri_cpe
channel => 1-2
context = default
group = 63

; Span 2: B4/0/2 "B4XXP (PCI) Card 0 Span 2"
group=0,12
context=from-pstn
switchtype = euroisdn
signalling = bri_cpe
channel => 4-5
context = default
group = 63

; Span 3: ZTHFC1 "HFC-S PCI A ISDN card 1 [TE]"
group=0,13
context=from-pstn
switchtype = euroisdn
signalling = bri_cpe
channel => 7-8
context = default
group = 63

Agregamos los trunks a la configuracion y listo!

Espero que te funcione. Me cuentas


[/quote]

[RamonciO]

[RamonciO]

Y me pasa otra cosa, que creo que debe estar relacionado con el
problema anterior.
Cada 20 segundos más o menos, El canal D se apaga y al momento se
enciende.

== Primary D-Channel on span 1 down
== Primary D-Channel on span 1 up

Esto no ocurre cuando hay una llamada en curso.
Y no parece que haya cortes con las llamadas, he hecho una de 15
minutos sin problemas.

> wgethttp://tests.p3dq.com/elastix/kernel-module-dahdi-2.1.0.4-8_2.6.18_92...
> wgethttp://tests.p3dq.com/elastix/kernel-module-dahdi-devel-2.1.0.4-8.i38...

>
> Instalamos los rpms
>
> [root@elastix src]# rpm -U dahdi-2.1.0.4-8.i386.rpm dahdi-
> devel-2.1.0.4-8.i386.rpm --nodeps --force
> [root@elastix src]# rpm -U asterisk-1.4.24-2.i386.rpm asterisk-
> devel-1.4.24-2.i386.rpm --nodeps --force
> [root@elastix src]# rpm -U kernel-module-
> dahdi-2.1.0.4-8_2.6.18_92.1.22.el5.i386.rpm --nodeps --force
> [root@elastix src]# rpm -U kernel-module-dahdi-
> devel-2.1.0.4-8.i386.rpm --nodeps --force
>
> Instalamos libpri (algo me deje atras en las dependencias del rpm de
> asterisk, por eso el --nodeps y el --force)
>

> [root@elastix src]# wgethttp://downloads.digium.com/pub/libpri/releases/libpri-1.4.9.tar.gz

[RamonciO]

Aquí os pego un pri intense debug, para ver si alguien sabe lo que
pasa.
Yo creo que es algo específico de mi línea, porque a otra gente no le
ocurre.
Pero lo raro es que esa misma línea la tengo conectada normalmente a
un Patton SmartNode 4552 y ha funcionado perfectamente sin problemas
durante meses.


elastix*CLI> pri intense debug span 1
Enabled EXTENSIVE debugging on span 1
T203 counter expired, sending RR and scheduling T203 again
Sending Receiver Ready (0)

> [ 00 01 01 01 ]

> Supervisory frame:
> SAPI: 00 C/R: 0 EA: 0
> TEI: 000 EA: 1
> Zero: 0 S: 0 01: 1 [ RR (receive ready) ]
> N(R): 000 P/F: 1
> 0 bytes of data
elastix*CLI>
< [ 00 01 01 01 ]

< Supervisory frame:
< SAPI: 00 C/R: 0 EA: 0
< TEI: 000 EA: 1
< Zero: 0 S: 0 01: 1 [ RR (receive ready) ]
< N(R): 000 P/F: 1
< 0 bytes of data
Handling message for SAPI/TEI=0/0
-- ACKing all packets from 0 to (but not including) 0
-- Since there was nothing left, stopping T200 counter
-- Stopping T203 counter since we got an ACK
-- Nothing left, starting T203 counter
-- Got RR response to our frame
-- Restarting T203 timer
elastix*CLI>
< [ 02 01 53 ]

< Unnumbered frame:
< SAPI: 00 C/R: 1 EA: 0
< TEI: 000 EA: 1
< M3: 2 P/F: 1 M2: 0 11: 3 [ DISC (disconnect) ]
< 0 bytes of data
Handling message for SAPI/TEI=0/0
-- Got Disconnect from peer.
Sending Unnumbered Acknowledgement

> [ 02 01 73 ]

> Unnumbered frame:
> SAPI: 00 C/R: 1 EA: 0
> TEI: 000 EA: 1
> M3: 3 P/F: 1 M2: 0 11: 3 [ UA (unnumbered acknowledgement) ]
> 0 bytes of data
q921.c:842 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED
-- Restarting T203 timer

== Primary D-Channel on span 1 down

Sending Set Asynchronous Balanced Mode Extended

> [ 00 01 7f ]

> Unnumbered frame:
> SAPI: 00 C/R: 0 EA: 0
> TEI: 000 EA: 1
> M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ]
> 0 bytes of data
q921.c:211 q921_send_sabme: q921_state now is Q921_AWAITING_ESTABLISH
elastix*CLI>
< [ 00 01 73 ]

[RamonciO]

[Apr 10 23:16:04] VERBOSE[5766] logger.c:
< Unnumbered frame:
[Apr 10 23:16:04] VERBOSE[5766] logger.c: < SAPI: 00 C/R: 0 EA: 0
< TEI: 000 EA: 1
[Apr 10 23:16:04] VERBOSE[5766] logger.c: < M3: 3 P/F: 1 M2: 0 11:

3 [ UA (unnumbered acknowledgement) ]
< 0 bytes of data

[Apr 10 23:16:04] VERBOSE[5766] logger.c: Handling message for SAPI/
TEI=0/0
[Apr 10 23:16:04] VERBOSE[5766] logger.c: -- Got UA from network peer
Link up.
[Apr 10 23:16:04] VERBOSE[5766] logger.c: q921.c:842 q921_reset:
q921_state now is Q921_LINK_CONNECTION_RELEASED
[Apr 10 23:16:04] VERBOSE[5766] logger.c: q921.c:793 q921_dchannel_up:
q921_state now is Q921_LINK_CONNECTION_ESTABLISHED
[Apr 10 23:16:04] VERBOSE[5766] logger.c: -- Restarting T203 timer
[Apr 10 23:16:04] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:16:14] VERBOSE[5766] logger.c: T203 counter expired,

sending RR and scheduling T203 again

[Apr 10 23:16:14] VERBOSE[5766] logger.c: Sending Receiver Ready (0)
[Apr 10 23:16:14] VERBOSE[5766] logger.c:
> [ 00 01 01 01 ]
[Apr 10 23:16:14] VERBOSE[5766] logger.c:
> Supervisory frame:
[Apr 10 23:16:14] VERBOSE[5766] logger.c: > SAPI: 00 C/R: 0 EA: 0
> TEI: 000 EA: 1
[Apr 10 23:16:14] VERBOSE[5766] logger.c: > Zero: 0 S: 0 01: 1

[ RR (receive ready) ]
> N(R): 000 P/F: 1
> 0 bytes of data

[Apr 10 23:16:14] VERBOSE[5766] logger.c:
< [ 00 01 01 01 ]
[Apr 10 23:16:14] VERBOSE[5766] logger.c:
< Supervisory frame:
[Apr 10 23:16:14] VERBOSE[5766] logger.c: < SAPI: 00 C/R: 0 EA: 0
< TEI: 000 EA: 1
[Apr 10 23:16:14] VERBOSE[5766] logger.c: < Zero: 0 S: 0 01: 1

[ RR (receive ready) ]
< N(R): 000 P/F: 1
< 0 bytes of data

[Apr 10 23:16:14] VERBOSE[5766] logger.c: Handling message for SAPI/
TEI=0/0
[Apr 10 23:16:14] VERBOSE[5766] logger.c: -- ACKing all packets from 0

to (but not including) 0

[Apr 10 23:16:14] VERBOSE[5766] logger.c: -- Since there was nothing
left, stopping T200 counter
[Apr 10 23:16:14] VERBOSE[5766] logger.c: -- Stopping T203 counter

since we got an ACK

[Apr 10 23:16:14] VERBOSE[5766] logger.c: -- Nothing left, starting
T203 counter
[Apr 10 23:16:14] VERBOSE[5766] logger.c: -- Got RR response to our
frame
[Apr 10 23:16:14] VERBOSE[5766] logger.c: -- Restarting T203 timer
[Apr 10 23:16:19] VERBOSE[5766] logger.c:
< [ 02 01 53 ]
[Apr 10 23:16:19] VERBOSE[5766] logger.c:
< Unnumbered frame:
[Apr 10 23:16:19] VERBOSE[5766] logger.c: < SAPI: 00 C/R: 1 EA: 0
< TEI: 000 EA: 1
[Apr 10 23:16:19] VERBOSE[5766] logger.c: < M3: 2 P/F: 1 M2: 0 11:

3 [ DISC (disconnect) ]
< 0 bytes of data

[Apr 10 23:16:19] VERBOSE[5766] logger.c: Handling message for SAPI/
TEI=0/0
[Apr 10 23:16:19] VERBOSE[5766] logger.c: -- Got Disconnect from peer.
[Apr 10 23:16:19] VERBOSE[5766] logger.c: Sending Unnumbered
Acknowledgement
[Apr 10 23:16:19] VERBOSE[5766] logger.c:
> [ 02 01 73 ]
[Apr 10 23:16:19] VERBOSE[5766] logger.c:
> Unnumbered frame:
[Apr 10 23:16:19] VERBOSE[5766] logger.c: > SAPI: 00 C/R: 1 EA: 0
> TEI: 000 EA: 1
[Apr 10 23:16:19] VERBOSE[5766] logger.c: > M3: 3 P/F: 1 M2: 0 11:

3 [ UA (unnumbered acknowledgement) ]
> 0 bytes of data

[Apr 10 23:16:19] VERBOSE[5766] logger.c: q921.c:842 q921_reset:
q921_state now is Q921_LINK_CONNECTION_RELEASED
[Apr 10 23:16:19] VERBOSE[5766] logger.c: -- Restarting T203 timer
[Apr 10 23:16:19] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:16:19] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:16:20] VERBOSE[5766] logger.c: Sending Set Asynchronous
Balanced Mode Extended
[Apr 10 23:16:20] VERBOSE[5766] logger.c:
> [ 00 01 7f ]
[Apr 10 23:16:20] VERBOSE[5766] logger.c:
> Unnumbered frame:
[Apr 10 23:16:20] VERBOSE[5766] logger.c: > SAPI: 00 C/R: 0 EA: 0
> TEI: 000 EA: 1
[Apr 10 23:16:20] VERBOSE[5766] logger.c: > M3: 3 P/F: 1 M2: 3 11:

3 [ SABME (set asynchronous balanced mode extended) ]
> 0 bytes of data

[Apr 10 23:16:20] VERBOSE[5766] logger.c: q921.c:211 q921_send_sabme:
q921_state now is Q921_AWAITING_ESTABLISH
[Apr 10 23:16:20] VERBOSE[5766] logger.c:
< [ 00 01 73 ]
[Apr 10 23:16:20] VERBOSE[5766] logger.c:
< Unnumbered frame:
[Apr 10 23:16:20] VERBOSE[5766] logger.c: < SAPI: 00 C/R: 0 EA: 0
< TEI: 000 EA: 1
[Apr 10 23:16:20] VERBOSE[5766] logger.c: < M3: 3 P/F: 1 M2: 0 11:

3 [ UA (unnumbered acknowledgement) ]
< 0 bytes of data

[Apr 10 23:16:20] VERBOSE[5766] logger.c: Handling message for SAPI/
TEI=0/0
[Apr 10 23:16:20] VERBOSE[5766] logger.c: -- Got UA from network peer
Link up.
[Apr 10 23:16:20] VERBOSE[5766] logger.c: q921.c:842 q921_reset:
q921_state now is Q921_LINK_CONNECTION_RELEASED
[Apr 10 23:16:20] VERBOSE[5766] logger.c: q921.c:793 q921_dchannel_up:
q921_state now is Q921_LINK_CONNECTION_ESTABLISHED
[Apr 10 23:16:20] VERBOSE[5766] logger.c: -- Restarting T203 timer
[Apr 10 23:16:20] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:16:35] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:16:35] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:16:36] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:16:51] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:16:51] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:16:52] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:17:07] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:17:07] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:17:08] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:17:23] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:17:23] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:17:24] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:17:39] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:17:39] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:17:40] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:17:55] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:17:55] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:17:56] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:18:11] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:18:11] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:18:12] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:18:27] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:18:27] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:18:28] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:18:44] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:18:44] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:18:45] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:19:00] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:19:00] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:19:01] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:19:16] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:19:16] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:19:17] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:19:32] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:19:32] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:19:33] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:19:48] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:19:48] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:19:49] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:20:01] VERBOSE[5741] logger.c: -- Remote UNIX
connection
[Apr 10 23:20:02] VERBOSE[6073] logger.c: -- Remote UNIX
connection disconnected
[Apr 10 23:20:04] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:20:04] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:20:05] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:20:20] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:20:20] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:20:21] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:20:36] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:20:36] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:20:37] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:20:52] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:20:52] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:20:53] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:21:08] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:21:08] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:21:09] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:21:25] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:21:25] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:21:26] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:21:41] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:21:41] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:21:42] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:21:57] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:21:57] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:21:58] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:22:13] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:22:13] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:22:14] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:22:29] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:22:29] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:22:30] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:22:45] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:22:45] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:22:46] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:23:01] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:23:01] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:23:02] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:23:17] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:23:17] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:23:18] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:23:33] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:23:33] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:23:34] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:23:49] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:23:49] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:23:50] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:24:06] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:24:06] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:24:07] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:24:22] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:24:22] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:24:23] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:24:38] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:24:38] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:24:39] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:24:54] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:24:54] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:24:55] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:25:01] VERBOSE[5741] logger.c: -- Remote UNIX
connection
[Apr 10 23:25:02] VERBOSE[6111] logger.c: -- Remote UNIX
connection disconnected
[Apr 10 23:25:10] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:25:10] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:25:11] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:25:26] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:25:26] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:25:27] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:25:32] VERBOSE[5819] logger.c: -- Remote UNIX
connection disconnected
[Apr 10 23:25:42] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:25:42] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:25:43] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:25:58] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:25:58] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:25:59] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:26:14] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:26:14] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:26:15] VERBOSE[5741] logger.c: -- Remote UNIX
connection
[Apr 10 23:26:15] VERBOSE[6121] logger.c: -- Remote UNIX
connection disconnected
[Apr 10 23:26:15] VERBOSE[5766] logger.c: Sending Set Asynchronous
Balanced Mode Extended
[Apr 10 23:26:15] VERBOSE[5766] logger.c:
> [ 00 01 7f ]
[Apr 10 23:26:15] VERBOSE[5766] logger.c:
> Unnumbered frame:
[Apr 10 23:26:15] VERBOSE[5766] logger.c: > SAPI: 00 C/R: 0 EA: 0
> TEI: 000 EA: 1
[Apr 10 23:26:15] VERBOSE[5766] logger.c: > M3: 3 P/F: 1 M2: 3 11:

3 [ SABME (set asynchronous balanced mode extended) ]
> 0 bytes of data

[Apr 10 23:26:15] VERBOSE[5766] logger.c: q921.c:211 q921_send_sabme:
q921_state now is Q921_AWAITING_ESTABLISH
[Apr 10 23:26:15] VERBOSE[5766] logger.c:
< [ 00 01 73 ]
[Apr 10 23:26:15] VERBOSE[5766] logger.c:
< Unnumbered frame:
[Apr 10 23:26:15] VERBOSE[5766] logger.c: < SAPI: 00 C/R: 0 EA: 0
< TEI: 000 EA: 1
[Apr 10 23:26:15] VERBOSE[5766] logger.c: < M3: 3 P/F: 1 M2: 0 11:

3 [ UA (unnumbered acknowledgement) ]
< 0 bytes of data

[Apr 10 23:26:15] VERBOSE[5766] logger.c: Handling message for SAPI/
TEI=0/0
[Apr 10 23:26:15] VERBOSE[5766] logger.c: -- Got UA from network peer
Link up.
[Apr 10 23:26:15] VERBOSE[5766] logger.c: q921.c:842 q921_reset:
q921_state now is Q921_LINK_CONNECTION_RELEASED
[Apr 10 23:26:15] VERBOSE[5766] logger.c: q921.c:793 q921_dchannel_up:
q921_state now is Q921_LINK_CONNECTION_ESTABLISHED
[Apr 10 23:26:15] VERBOSE[5766] logger.c: -- Restarting T203 timer
[Apr 10 23:26:15] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:26:25] VERBOSE[5766] logger.c: T203 counter expired,

sending RR and scheduling T203 again

[Apr 10 23:26:25] VERBOSE[5766] logger.c: Sending Receiver Ready (0)
[Apr 10 23:26:25] VERBOSE[5766] logger.c:
> [ 00 01 01 01 ]
[Apr 10 23:26:25] VERBOSE[5766] logger.c:
> Supervisory frame:
[Apr 10 23:26:25] VERBOSE[5766] logger.c: > SAPI: 00 C/R: 0 EA: 0
> TEI: 000 EA: 1
[Apr 10 23:26:25] VERBOSE[5766] logger.c: > Zero: 0 S: 0 01: 1

[ RR (receive ready) ]
> N(R): 000 P/F: 1
> 0 bytes of data

[Apr 10 23:26:25] VERBOSE[5766] logger.c:
< [ 02 01 01 01 ]
[Apr 10 23:26:25] VERBOSE[5766] logger.c:
< Supervisory frame:
[Apr 10 23:26:25] VERBOSE[5766] logger.c: < SAPI: 00 C/R: 1 EA: 0
< TEI: 000 EA: 1
[Apr 10 23:26:25] VERBOSE[5766] logger.c: < Zero: 0 S: 0 01: 1

[ RR (receive ready) ]
< N(R): 000 P/F: 1
< 0 bytes of data

[Apr 10 23:26:25] VERBOSE[5766] logger.c: Handling message for SAPI/
TEI=0/0
[Apr 10 23:26:25] VERBOSE[5766] logger.c: -- ACKing all packets from 0

to (but not including) 0

[Apr 10 23:26:25] VERBOSE[5766] logger.c: -- Since there was nothing
left, stopping T200 counter
[Apr 10 23:26:25] VERBOSE[5766] logger.c: -- Stopping T203 counter

since we got an ACK

[Apr 10 23:26:25] VERBOSE[5766] logger.c: -- Nothing left, starting
T203 counter
[Apr 10 23:26:25] VERBOSE[5766] logger.c: -- Unsolicited RR with P/F
bit, responding
[Apr 10 23:26:25] VERBOSE[5766] logger.c: Sending Receiver Ready (0)
[Apr 10 23:26:25] VERBOSE[5766] logger.c:
> [ 02 01 01 01 ]
[Apr 10 23:26:25] VERBOSE[5766] logger.c:
> Supervisory frame:
[Apr 10 23:26:25] VERBOSE[5766] logger.c: > SAPI: 00 C/R: 1 EA: 0
> TEI: 000 EA: 1
[Apr 10 23:26:25] VERBOSE[5766] logger.c: > Zero: 0 S: 0 01: 1

[ RR (receive ready) ]
> N(R): 000 P/F: 1
> 0 bytes of data

[Apr 10 23:26:25] VERBOSE[5766] logger.c: -- Restarting T203 timer
[Apr 10 23:26:25] VERBOSE[5766] logger.c:
< [ 00 01 01 01 ]
[Apr 10 23:26:25] VERBOSE[5766] logger.c:
< Supervisory frame:
[Apr 10 23:26:25] VERBOSE[5766] logger.c: < SAPI: 00 C/R: 0 EA: 0
< TEI: 000 EA: 1
[Apr 10 23:26:25] VERBOSE[5766] logger.c: < Zero: 0 S: 0 01: 1

[ RR (receive ready) ]
< N(R): 000 P/F: 1
< 0 bytes of data

[Apr 10 23:26:25] VERBOSE[5766] logger.c: Handling message for SAPI/
TEI=0/0
[Apr 10 23:26:25] VERBOSE[5766] logger.c: -- ACKing all packets from 0

to (but not including) 0

[Apr 10 23:26:25] VERBOSE[5766] logger.c: -- Since there was nothing
left, stopping T200 counter
[Apr 10 23:26:25] VERBOSE[5766] logger.c: -- Stopping T203 counter

since we got an ACK

[Apr 10 23:26:25] VERBOSE[5766] logger.c: -- Nothing left, starting
T203 counter
[Apr 10 23:26:25] VERBOSE[5766] logger.c: -- Got RR response to our
frame
[Apr 10 23:26:25] VERBOSE[5766] logger.c: -- Restarting T203 timer
[Apr 10 23:26:30] VERBOSE[5766] logger.c:
< [ 02 01 53 ]
[Apr 10 23:26:30] VERBOSE[5766] logger.c:
< Unnumbered frame:
[Apr 10 23:26:30] VERBOSE[5766] logger.c: < SAPI: 00 C/R: 1 EA: 0
< TEI: 000 EA: 1
[Apr 10 23:26:30] VERBOSE[5766] logger.c: < M3: 2 P/F: 1 M2: 0 11:

3 [ DISC (disconnect) ]
< 0 bytes of data

[Apr 10 23:26:30] VERBOSE[5766] logger.c: Handling message for SAPI/
TEI=0/0
[Apr 10 23:26:30] VERBOSE[5766] logger.c: -- Got Disconnect from peer.
[Apr 10 23:26:30] VERBOSE[5766] logger.c: Sending Unnumbered
Acknowledgement
[Apr 10 23:26:30] VERBOSE[5766] logger.c:
> [ 02 01 73 ]
[Apr 10 23:26:30] VERBOSE[5766] logger.c:
> Unnumbered frame:
[Apr 10 23:26:30] VERBOSE[5766] logger.c: > SAPI: 00 C/R: 1 EA: 0
> TEI: 000 EA: 1
[Apr 10 23:26:30] VERBOSE[5766] logger.c: > M3: 3 P/F: 1 M2: 0 11:

3 [ UA (unnumbered acknowledgement) ]
> 0 bytes of data

[Apr 10 23:26:30] VERBOSE[5766] logger.c: q921.c:842 q921_reset:
q921_state now is Q921_LINK_CONNECTION_RELEASED
[Apr 10 23:26:30] VERBOSE[5766] logger.c: -- Restarting T203 timer
[Apr 10 23:26:30] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:26:30] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:26:31] VERBOSE[5766] logger.c: Sending Set Asynchronous
Balanced Mode Extended
[Apr 10 23:26:31] VERBOSE[5766] logger.c:
> [ 00 01 7f ]
[Apr 10 23:26:31] VERBOSE[5766] logger.c:
> Unnumbered frame:
[Apr 10 23:26:31] VERBOSE[5766] logger.c: > SAPI: 00 C/R: 0 EA: 0
> TEI: 000 EA: 1
[Apr 10 23:26:31] VERBOSE[5766] logger.c: > M3: 3 P/F: 1 M2: 3 11:

3 [ SABME (set asynchronous balanced mode extended) ]
> 0 bytes of data

[Apr 10 23:26:31] VERBOSE[5766] logger.c: q921.c:211 q921_send_sabme:
q921_state now is Q921_AWAITING_ESTABLISH
[Apr 10 23:26:31] VERBOSE[5766] logger.c:
< [ 00 01 73 ]
[Apr 10 23:26:31] VERBOSE[5766] logger.c:
< Unnumbered frame:
[Apr 10 23:26:31] VERBOSE[5766] logger.c: < SAPI: 00 C/R: 0 EA: 0
< TEI: 000 EA: 1
[Apr 10 23:26:31] VERBOSE[5766] logger.c: < M3: 3 P/F: 1 M2: 0 11:

3 [ UA (unnumbered acknowledgement) ]
< 0 bytes of data

[Apr 10 23:26:31] VERBOSE[5766] logger.c: Handling message for SAPI/
TEI=0/0
[Apr 10 23:26:31] VERBOSE[5766] logger.c: -- Got UA from network peer
Link up.
[Apr 10 23:26:31] VERBOSE[5766] logger.c: q921.c:842 q921_reset:
q921_state now is Q921_LINK_CONNECTION_RELEASED
[Apr 10 23:26:31] VERBOSE[5766] logger.c: q921.c:793 q921_dchannel_up:
q921_state now is Q921_LINK_CONNECTION_ESTABLISHED
[Apr 10 23:26:31] VERBOSE[5766] logger.c: -- Restarting T203 timer
[Apr 10 23:26:31] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:26:39] VERBOSE[5741] logger.c: -- Remote UNIX
connection
[Apr 10 23:26:40] VERBOSE[6127] logger.c: -- Remote UNIX
connection disconnected
[Apr 10 23:26:41] VERBOSE[5766] logger.c:
< [ 02 01 01 01 ]
[Apr 10 23:26:41] VERBOSE[5766] logger.c:
< Supervisory frame:
[Apr 10 23:26:41] VERBOSE[5766] logger.c: < SAPI: 00 C/R: 1 EA: 0
< TEI: 000 EA: 1
[Apr 10 23:26:41] VERBOSE[5766] logger.c: < Zero: 0 S: 0 01: 1

[ RR (receive ready) ]
< N(R): 000 P/F: 1
< 0 bytes of data

[Apr 10 23:26:41] VERBOSE[5766] logger.c: Handling message for SAPI/
TEI=0/0
[Apr 10 23:26:41] VERBOSE[5766] logger.c: -- ACKing all packets from 0

to (but not including) 0

[Apr 10 23:26:41] VERBOSE[5766] logger.c: -- Since there was nothing
left, stopping T200 counter
[Apr 10 23:26:41] VERBOSE[5766] logger.c: -- Stopping T203 counter

since we got an ACK

[Apr 10 23:26:41] VERBOSE[5766] logger.c: -- Nothing left, starting
T203 counter
[Apr 10 23:26:41] VERBOSE[5766] logger.c: -- Unsolicited RR with P/F
bit, responding
[Apr 10 23:26:41] VERBOSE[5766] logger.c: Sending Receiver Ready (0)
[Apr 10 23:26:41] VERBOSE[5766] logger.c:
> [ 02 01 01 01 ]
[Apr 10 23:26:41] VERBOSE[5766] logger.c:
> Supervisory frame:
[Apr 10 23:26:41] VERBOSE[5766] logger.c: > SAPI: 00 C/R: 1 EA: 0
> TEI: 000 EA: 1
[Apr 10 23:26:41] VERBOSE[5766] logger.c: > Zero: 0 S: 0 01: 1

[ RR (receive ready) ]
> N(R): 000 P/F: 1
> 0 bytes of data

[Apr 10 23:26:41] VERBOSE[5766] logger.c: -- Restarting T203 timer
[Apr 10 23:26:47] VERBOSE[5766] logger.c:
< [ 02 01 53 ]
[Apr 10 23:26:47] VERBOSE[5766] logger.c:
< Unnumbered frame:
[Apr 10 23:26:47] VERBOSE[5766] logger.c: < SAPI: 00 C/R: 1 EA: 0
< TEI: 000 EA: 1
[Apr 10 23:26:47] VERBOSE[5766] logger.c: < M3: 2 P/F: 1 M2: 0 11:

3 [ DISC (disconnect) ]
< 0 bytes of data

[Apr 10 23:26:47] VERBOSE[5766] logger.c: Handling message for SAPI/
TEI=0/0
[Apr 10 23:26:47] VERBOSE[5766] logger.c: -- Got Disconnect from peer.
[Apr 10 23:26:47] VERBOSE[5766] logger.c: Sending Unnumbered
Acknowledgement
[Apr 10 23:26:47] VERBOSE[5766] logger.c:
> [ 02 01 73 ]
[Apr 10 23:26:47] VERBOSE[5766] logger.c:
> Unnumbered frame:
[Apr 10 23:26:47] VERBOSE[5766] logger.c: > SAPI: 00 C/R: 1 EA: 0
> TEI: 000 EA: 1
[Apr 10 23:26:47] VERBOSE[5766] logger.c: > M3: 3 P/F: 1 M2: 0 11:

3 [ UA (unnumbered acknowledgement) ]
> 0 bytes of data

[Apr 10 23:26:47] VERBOSE[5766] logger.c: q921.c:842 q921_reset:
q921_state now is Q921_LINK_CONNECTION_RELEASED
[Apr 10 23:26:47] VERBOSE[5766] logger.c: -- Restarting T203 timer
[Apr 10 23:26:47] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:26:47] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:26:48] VERBOSE[5766] logger.c: Sending Set Asynchronous
Balanced Mode Extended
[Apr 10 23:26:48] VERBOSE[5766] logger.c:
> [ 00 01 7f ]
[Apr 10 23:26:48] VERBOSE[5766] logger.c:
> Unnumbered frame:
[Apr 10 23:26:48] VERBOSE[5766] logger.c: > SAPI: 00 C/R: 0 EA: 0
> TEI: 000 EA: 1
[Apr 10 23:26:48] VERBOSE[5766] logger.c: > M3: 3 P/F: 1 M2: 3 11:

3 [ SABME (set asynchronous balanced mode extended) ]
> 0 bytes of data

[Apr 10 23:26:48] VERBOSE[5766] logger.c: q921.c:211 q921_send_sabme:
q921_state now is Q921_AWAITING_ESTABLISH
[Apr 10 23:26:48] VERBOSE[5766] logger.c:
< [ 00 01 73 ]
[Apr 10 23:26:48] VERBOSE[5766] logger.c:
< Unnumbered frame:
[Apr 10 23:26:48] VERBOSE[5766] logger.c: < SAPI: 00 C/R: 0 EA: 0
< TEI: 000 EA: 1
[Apr 10 23:26:48] VERBOSE[5766] logger.c: < M3: 3 P/F: 1 M2: 0 11:

3 [ UA (unnumbered acknowledgement) ]
< 0 bytes of data

[Apr 10 23:26:48] VERBOSE[5766] logger.c: Handling message for SAPI/
TEI=0/0
[Apr 10 23:26:48] VERBOSE[5766] logger.c: -- Got UA from network peer
Link up.
[Apr 10 23:26:48] VERBOSE[5766] logger.c: q921.c:842 q921_reset:
q921_state now is Q921_LINK_CONNECTION_RELEASED
[Apr 10 23:26:48] VERBOSE[5766] logger.c: q921.c:793 q921_dchannel_up:
q921_state now is Q921_LINK_CONNECTION_ESTABLISHED
[Apr 10 23:26:48] VERBOSE[5766] logger.c: -- Restarting T203 timer
[Apr 10 23:26:48] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:26:52] VERBOSE[5741] logger.c: -- Remote UNIX
connection
[Apr 10 23:27:03] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:27:03] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:27:04] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:27:19] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 down
[Apr 10 23:27:19] WARNING[5766] chan_dahdi.c: No D-channels
available! Using Primary channel 3 as D-channel anyway!
[Apr 10 23:27:20] VERBOSE[5766] logger.c: == Primary D-Channel on
span 1 up
[Apr 10 23:27:30] VERBOSE[5766] logger.c:
< [ 02 01 01 01 ]
[Apr 10 23:27:30] VERBOSE[5766] logger.c:
< Supervisory frame:
[Apr 10 23:27:30] VERBOSE[5766] logger.c: < SAPI: 00 C/R: 1 EA: 0
< TEI: 000 EA: 1
[Apr 10 23:27:30] VERBOSE[5766] logger.c: < Zero: 0 S: 0 01: 1

[ RR (receive ready) ]
< N(R): 000 P/F: 1
< 0 bytes of data

[Apr 10 23:27:30] VERBOSE[5766] logger.c: Handling message for SAPI/
TEI=0/0
[Apr 10 23:27:30] VERBOSE[5766] logger.c: -- ACKing all packets from 0

to (but not including) 0

[Apr 10 23:27:30] VERBOSE[5766] logger.c: -- Since there was nothing
left, stopping T200 counter
[Apr 10 23:27:30] VERBOSE[5766] logger.c: -- Stopping T203 counter

since we got an ACK

[Apr 10 23:27:30] VERBOSE[5766] logger.c: -- Nothing left, starting
T203 counter
[Apr 10 23:27:30] VERBOSE[5766] logger.c: -- Unsolicited RR with P/F
bit, responding
[Apr 10 23:27:30] VERBOSE[5766] logger.c: Sending Receiver Ready (0)
[Apr 10 23:27:30] VERBOSE[5766] logger.c:
> [ 02 01 01 01 ]

[Juan Carlos Valero]

El vie, 10-04-2009 a las 13:37 -0700, RamonciO escribió:

> Pues con dahdi no puedo llamar ni por grupo ni por puerto, hasta que
> no recibo una llamada. Entonces puedo llamar durante un ratillo, menos
> de 1 minuto.

Eso lo puedes solucionar intercalando un misdn_check_l2l1() antes del
dial. Una busqueda en las macros de Elastix te diran donde insertarlo. Y
con eso solucionado.

--
Un saludo,

Juan Carlos Valero

-------------------------------------------------------------------------
Capa Tres Soluciones Tecnológicas S.L. Barcelona
Visita nuestra página web en: http://www.capatres.com
Teléfono: 935605424 Fax: 935748256 Blog: http://blogs.capatres.com
-------------------------------------------------------------------------

[RamonciO]

misdn_check_l2l1() usando dahdi? No creo que pueda, no?

[Odicha]

no...

[Odicha]

Tal vez si...

bueno los parches estaban `preparados para dahdi-linux y dahdi-tools
no para el dahdi-complete...

Preparare algo para Elastix y hacer unas pruebas...

> > > immediately notify us via e-mail and delete it.- Ocultar texto de la cita -

[Odicha]

Si te falta el archivo es que algo no se parcheo correctamente, porque van
en el diff...

----- Original Message -----
From: "RamonciO" <sol...@gmail.com>
To: "asterisk-es" <aster...@googlegroups.com>

[Odicha]

Te mnando unos src.rpms

> > > > tengo que poner mi hardware id en algún sitio antes de compilar?- Ocultar texto de la cita -

[Odicha]

Procedimiento que he seguido y funciona

Elastix 1.5.2 recien instalado

Descargas los rpms que me he creado a /usr/src

wget http://tests.p3dq.com/elastix/asterisk-1.4.24-2.i386.rpm
wget http://tests.p3dq.com/elastix/asterisk-devel-1.4.24-2.i386.rpm
wget http://tests.p3dq.com/elastix/dahdi-2.1.0.4-8.i386.rpm
wget http://tests.p3dq.com/elastix/dahdi-devel-2.1.0.4-8.i386.rpm
wget http://tests.p3dq.com/elastix/kernel-module-dahdi-2.1.0.4-8_2.6.18_92.1.22.el5.i386.rpm
wget http://tests.p3dq.com/elastix/kernel-module-dahdi-devel-2.1.0.4-8.i386.rpm

Instalamos los rpms

[root@elastix src]# rpm -U dahdi-2.1.0.4-8.i386.rpm
dahdi-devel-2.1.0.4-8.i386.rpm

[root@elastix src]# rpm -U asterisk-1.4.24-2.i386.rpm
asterisk-devel-1.4.24-2.i386.rpm --nodeps

[root@elastix src]# rpm -U

kernel-module-dahdi-2.1.0.4-8_2.6.18_92.1.22.el5.i386.rpm

[root@elastix src]# rpm -U kernel-module-dahdi-
devel-2.1.0.4-8.i386.rpm

Instalamos libpri (algo me deje atras en las dependencias del rpm de

asterisk, por eso el --nodeps)

[root@elastix src]# wget

http://downloads.digium.com/pub/libpri/releases/libpri-1.4.9.tar.gz

[root@elastix src]# tar zxvf libpri-1.4.9.tar.gz

[root@elastix src]# cd libpri-1.4.9

[root@elastix libpri-1.4.9]# make

[root@elastix libpri-1.4.9]# make install

Reiniciamos
[root@elastix libpri-1.4.9]# shutdown -r now

Despues de reiniciar

Detectamos hardware desde panel de Elastix (ver antes.jpg y
despues.jpg)

> > > > > > tengo que poner mi hardware id en algún sitio antes de compilar?- Ocultar texto de la cita -

[Odicha]

Ok. La fritz tambien deberia funcionar

Estoy con el diff para sl srpm

----- Original Message -----
From: "RamonciO" <sol...@gmail.com>
To: "asterisk-es" <aster...@googlegroups.com>

[Jose Luis]

Ramoncio:

Como te he comentado en la lista de elastix, cambia el tipo de
señalización. A mi me pasaba y el problema era la señalizacion.


RamonciO escribió:

[Juan Carlos Valero]

El sáb, 11-04-2009 a las 02:27 -0700, RamonciO escribió:
> misdn_check_l2l1() usando dahdi? No creo que pueda, no?

Perdon, tienes toda la razon, no se puede.

[Odicha]

ya esta la solucion
despues de mirar tooooodo el codigo de arriba abajo
y de cargarme sin quereer un par de lineas del libpri y pensar que se habian
dejado cosas atras

añadir a chan_dahdi.conf

resetinterval=never

y ya

el tema es que al bajar y subir por el ahorro de energia se queda el flag en
resseting
Si ponemos el resetinterval a never ya no lo intenta

La configuracion de chan_dahdi del resetinterval en el branch 1.6 por
defecto es -1 (never) y en la 1.4 es 3600
por eso fallaba en la 1.4 y en la 1.6 no

ademas me he creado un parametro
bri_l1_check
para ver o no ver los d-channel de gestion de enrgia

== Primary D-Channel on span 1 down

== Primary D-Channel on span 1 up

con bri_l1_check=no desaparecen de consola los mensajes
mas que nada por si a alguien le molesta porque es lo que hace el ahorro de
energia

odistuffing a las 5.20 am.....

creo que con esto solo queda documentar

por cierto tengo unos rpms un poco salvajes para convertir un elastix en
odistuffed a machete... por si alguien quiere hacer pruebas con la elastix
1.5.2 y las tarjetas reconoce las hfc-4s 8-s y las hfc-s de un puerto

http://www.elastix.org/index.php?option=com_fireboard&Itemid=55&func=view&id=19880&catid=51&limit=10&limitstart=10#20531

----- Original Message -----
From: "Juan Carlos Valero" <jcva...@capatres.com>
To: <aster...@googlegroups.com>
Sent: Saturday, April 11, 2009 8:11 PM
Subject: [Asterisk-ES] Re: Y llego el odistuff...

[Jose Luis]

Odicha:

Respecto al comentario que has hecho en el foro de Elastix, en el que
decias que se perdia la funcionalidad de actualizacion de elastix, que
pasa si elastix saca una version con todas tus funcionalidades?
Actualizando con Yum quedaria todo listo o has tocado algo que pueda
romper algo?

Saludos.

Odicha escribió:

[José Antonio Déniz Fabelo]

Para actualizar Elastix habra que esperar a que se prepare un rpm oficial por parte de Elastx.

Esto no es más que una prueba de concepto.

Teoricamente actualizando con yum puedes volver a dejarlo bajo el trunk de Elastix, o desinstalando los rpms que yo instalo e instalando de nuevo los oficiales de Elñastix



-----Mensaje original-----
De: aster...@googlegroups.com [mailto:aster...@googlegroups.com] En nombre de Jose Luis
Enviado el: domingo, 12 de abril de 2009 11:17
Para: aster...@googlegroups.com
Asunto: [Asterisk-ES] Re: Y llego el odistuff...

[RamonciO]

Por fin funciona bien!
Jose ha encontrado la solución.

Solo faltaba añadir una cosa.
Hay que añadir en /etc/asterisk/chan_dahdi.conf la línea:

resetinterval=never

al final de [channels]


Y ya funciona en elastix.


Voy a probar en Debian ahora, ya postearé los resultados.

> >http://www.elastix.org/index.php?option=com_fireboard&Itemid=55&func=...

[RamonciO]

Anda, ni me habia fijado que ya lo has posteado tú.

Por fin te han quitado el baneo. XD

[RamonciO]

También funciona en Debian perfectamente.
Las pruebas han sido con Debian lenny
kernel 1.6.26-2
dahdi-linux-2.1.0.4.tar.gz
dahdi-tools-2.1.0.2.tar.gz
asterisk-1.4.24.1.tar.gz
asterisk-addons-1.4.7.tar.gz

[RamonciO]

Perdón, typo en el kernel, ese es más viejo.

linux-image-2.6.26-2-486

Las pruebas fueron en una epia, por eso -486
La tarjeta, una OpenVOX B200P.

[Ruben]

Yo también lo probado con la misma configuración RamonciO, es decir, una epia y las mismas versiones del debian, asterisk, dahdi, etc..., pero con una TDM400 y una Billion 1BRI, detectadas las dos perfectamente.

Ahora me falta añadirle el cancelador de eco OSLEC y poner alguno en producción, ya os contaré.

[Jose Luis]

Estoy probando con una junghanns de dos puerto y no me funciona. Lo
extraño es que me la detecta bien... Pero ni me entran ni me salen llamadas.

Tienen algo diferentes estas tarjetas? Con la digium de 4 me va bien...

Saludos.

RamonciO escribió:

[José Antonio Déniz Fabelo]

??

Algun log?
Algo mas?

Sin la Digium conectada, haz dahdi_test. Te tiene que dar valores sobre el 99%. Si no es así tenemos otra tarjeta con cuarzo cambiado

-----Mensaje original-----
De: aster...@googlegroups.com [mailto:aster...@googlegroups.com] En nombre de Jose Luis

Enviado el: jueves, 16 de abril de 2009 8:24

[Jose Luis]

ya lo habia probado. Me da valores 99,9's

No he enviaodo ningun log porque parece como si ignorara el canal. Es
posible activar algun log a nivel de la tarjeta, no del enlace?

Saludos.

José Antonio Déniz Fabelo escribió:

[Odicha]

tienes los canales d como hardhdlc?

bpri_cpe si es punto a punto en TE?

Esas cosas...

[Jose Luis]

Ya he encontrado el problema. Era un error en la configuracion. Despues
de detectar la tarjeta cuando puse el canal de con hard no me carbaba el
modulo. puse dchanel y me cargaba el modulo. Asumí que con dchanel
funcinaba y con hard no. Es posible que me equivocara a la hora de
escribir o que tuviera algun otro parametro mal porque hoy al volver a
poner hard me ha funcionado.

Confirmo que la junghanns de dos puertos funciona correctamente con el
odistuff

Gracias a todos.

Odicha escribió: