[asterisk-r2] problem with link between asterisk 1.8.20.0 & TDA200

[Gustavo Cremella]

José:

Do you have access to the console of the Asterisk?
Did you excecute logued at the console as root:

# cat /proc/dahdi/1
??

It seems like some emails have been lost/corrupted, so I have received
partial information. Can you resend or attach output of previous comand and
screen capture of

#dahdi_tool

Regards, G.C.


El 19 de mayo de 2014, 16:16, Jose Enrique Benitez Martínez <
jose.jobema at gmail.com> escribió:

> In all cases the first start of the TX and RX asterisk channels are  IDLE,
> then call to extension 100 of Panasonic  exiting by channel 1, and them
>  the channel 1  RX stay in SEIZE and all others Blocked
> jose
>
>
> 2014-05-19 14:32 GMT-04:30 Jose Enrique Benitez Martínez <
> jose.jobema at gmail.com>:
>
>> los commandos cat proc/dahdi/1
>>
>>
>> 2014-05-19 9:52 GMT-04:30 Jose Enrique Benitez Martínez <
>> jose.jobema at gmail.com>:
>>
>> si el span 1 esta contra la PANASONIC TDA 200 ...el span 2 estaría contra
>>> la operadora  PSTN COPACO ...TE adjunto el archivo de configuración lado
>>> Panasonic: Se configuró , también según lo establecido, esta
>>> configurado con Secuencia de trama: PCM30, codificación HDB3 sin CRC, ..
>>>
>>>
>>> 2014-05-19 9:40 GMT-04:30 Gustavo Cremella <gcremella at gmail.com>:
>>>
>>> Eso está OK, pero no deberías tener ningún tipo de alarmas si esa
>>>> conexión física está bien. Ahora, estuve estudiando con detenimiento tu
>>>> configuración, y veo que el enlace con problemas es el span 1. En ese span,
>>>> has tenido eventos de alarmas? Que te reporta el dahdi_tool en ese span?
>>>> Porque si no hay alarmas, no veo razón para que la Panasonic bloquee los
>>>> canales. Pero de la Panasonic no conozco nada.
>>>>
>>>>
>>>> 2014-05-19 10:33 GMT-03:00 Jose Enrique Benitez Martínez <
>>>> jose.jobema at gmail.com>:
>>>>
>>>> el link físico es un cable UTP  cruzado: pin 1 con pin 4 y 2 con 5...
>>>>>
>>>>>
>>>>> On Sat, May 17, 2014 at 8:33 AM, Gustavo Cremella <gcremella at gmail.com
>>>>> > wrote:
>>>>>
>>>>>> Hola:
>>>>>>
>>>>>> Como tienes configurado
>>>>>>
>>>>>> mfcr2_logdir=span1
>>>>>> mfcr2logging=all
>>>>>> mfcr2_call_files=yes
>>>>>>
>>>>>> va a ser interesante ver el log de la señalización R2 de alguna de
>>>>>> esas llamadas (creo en /var/log/asterisk/..., no estoy en estos momentos
>>>>>> frente a un asterisk...).
>>>>>>
>>>>>> Los archivos de configuración parecen correctos. El log de consola en
>>>>>> este caso no me aporta mucho, excepto el hecho de que tienes YELLOW ALARM
>>>>>> en los canales repetitivamente. Esto puede hacerme pensar en un problema a
>>>>>> nivel fìsico con el link. Por tanto cadfa vez que un extremo detecta este
>>>>>> problema,puede estar bloqueando los canales troncales. Usas un modem entre
>>>>>> ambos equipos? Es un cable directo? El problema puede estar allì.
>>>>>>
>>>>>> También una captura de pantalla de lo que te muestre la herramienta
>>>>>> dahdi_tool en el span que te causa problemas. Hay que chequear que en
>>>>>> reposo (ningún canal ocupado), los bits ABCD estén todos en 1001., y luego
>>>>>> una captura con un canal ocupado.
>>>>>>
>>>>>> Slds, G.C.
>>>>>>
>>>>>>
>>>>>>
>>>>>> 2014-05-17 9:29 GMT-03:00 Jose Enrique Benitez Martínez <
>>>>>> jose.jobema at gmail.com>:
>>>>>>
>>>>>>> succeed in making a call by entering this line in:
>>>>>>> dahdi-channels.conf:
>>>>>>>  *mfcr2_advanced_protocol_file = / etc/openr2/r2proto.conf *
>>>>>>> rings several times since asterix to TDA200, but then turned to lock
>>>>>>> all channels
>>>>>>> Channel 1 remains occupied (seize) and even if the call is short??
>>>>>>> Attached is a log from the beginning of the call
>>>>>>> jose
>>>>>>>
>>>>>>>
>>>>>>> On Fri, May 16, 2014 at 3:09 PM, Gustavo Cremella <
>>>>>>>> gcremella at gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hi:
>>>>>>>>> Can you provide more log lines since the call started?, not only
>>>>>>>>> this last 2 error lines.
>>>>>>>>>
>>>>>>>>  G.C.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2014-05-16 16:34 GMT-03:00 Jose Enrique Benitez Martínez <
>>>>>>>>> jose.jobema at gmail.com>:
>>>>>>>>>
>>>>>>>>>> The link between an Asterisk V1.8.20.0 and a Panasonic PBX
>>>>>>>>>> KX.TDA200 give me the following errors:
>>>>>>>>>>
>>>>>>>>>> [May 16 03:32:01] ERROR[9330] chan_dahdi.c: Chan 1 - Protocol
>>>>>>>>>> error. Reason = Invalid CAS, R2 State = Seize ACK Received, MF state = DNIS
>>>>>>>>>> Digit Transmitted, MF Group = Forward Group I, CAS = 0x08
>>>>>>>>>> DNIS = 100, ANI = 504, MF = 0x20
>>>>>>>>>> [May 16 03:32:01] ERROR[9330] chan_dahdi.c: MFC/R2 protocol error
>>>>>>>>>> on chan 1: Invalid CAS
>>>>>>>>>>
>>>>>>>>>> Attach my dahdi-channels.conf and my system.conf
>>>>>>>>>>  Please anyone help me
>>>>>>>>>> Jose
>>>>>>>>>>
>>>>>>>>>
>>
>
> --
> _____________________________________________________________________
> -- 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/20140519/36026040/attachment-0001.html>