Problemas para realizar Chamadas - E1

Thiago Batista — Mon, 02 Feb 2015 11:15:32 GMT

Olá Pessoal

Estou com o seguinte problema

As ligações estão normais, de repente, elas param e não é possivel receber nem realizar chamadas

Se eu dou um shut // no shut na interface E1, tudo volta ao normal, mas em algumas horas começa tudo de novo

no Log, no momento que para eu recebo esta mensagem

Feb 2 10:18:27: %MARS_NETCLK-3-HOLDOVER: Exiting Holdover for Controller E1 0/0/0

Abaixo está o Log completo

Feb 2 03:35:10: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to down (LOF detected)
Feb 2 03:35:10: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se0/0/0:15, TEI 0 changed to down
Feb 2 03:35:10: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for Controller E1 0/0/0
Feb 2 03:35:11: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to up
Feb 2 03:35:11: %ISDN-6-LAYER2UP: Layer 2 for Interface Se0/0/0:15, TEI 0 changed to up
Feb 2 03:35:14: %MARS_NETCLK-3-HOLDOVER: Exiting Holdover for Controller E1 0/0/0
Feb 2 05:00:32: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to down (LOF detected)
Feb 2 05:00:32: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se0/0/0:15, TEI 0 changed to down
Feb 2 05:00:33: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for Controller E1 0/0/0
Feb 2 05:00:33: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to up
Feb 2 05:00:33: %ISDN-6-LAYER2UP: Layer 2 for Interface Se0/0/0:15, TEI 0 changed to up
Feb 2 05:00:36: %MARS_NETCLK-3-HOLDOVER: Exiting Holdover for Controller E1 0/0/0
Feb 2 06:08:28: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to down (RAI detected)
Feb 2 06:08:28: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se0/0/0:15, TEI 0 changed to down
Feb 2 06:08:28: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for Controller E1 0/0/0
Feb 2 06:08:29: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to up
Feb 2 06:08:29: %ISDN-6-LAYER2UP: Layer 2 for Interface Se0/0/0:15, TEI 0 changed to up
Feb 2 06:08:32: %MARS_NETCLK-3-HOLDOVER: Exiting Holdover for Controller E1 0/0/0
Feb 2 06:08:38: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to down (RAI detected)
Feb 2 06:08:38: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se0/0/0:15, TEI 0 changed to down
Feb 2 06:08:38: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for Controller E1 0/0/0
Feb 2 06:08:39: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to up
Feb 2 06:08:39: %ISDN-6-LAYER2UP: Layer 2 for Interface Se0/0/0:15, TEI 0 changed to up
Feb 2 06:08:42: %MARS_NETCLK-3-HOLDOVER: Exiting Holdover for Controller E1 0/0/0
Feb 2 07:38:21: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to down (LOF detected)
Feb 2 07:38:21: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se0/0/0:15, TEI 0 changed to down
Feb 2 07:38:22: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for Controller E1 0/0/0
Feb 2 07:38:22: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to up
Feb 2 07:38:22: %ISDN-6-LAYER2UP: Layer 2 for Interface Se0/0/0:15, TEI 0 changed to up
Feb 2 07:38:25: %MARS_NETCLK-3-HOLDOVER: Exiting Holdover for Controller E1 0/0/0
Feb 2 09:02:48: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to down (AIS detected)
Feb 2 09:02:48: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se0/0/0:15, TEI 0 changed to down
Feb 2 09:02:48: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for Controller E1 0/0/0
Feb 2 09:02:49: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to up
Feb 2 09:02:49: %ISDN-6-LAYER2UP: Layer 2 for Interface Se0/0/0:15, TEI 0 changed to up
Feb 2 09:02:51: %MARS_NETCLK-3-HOLDOVER: Exiting Holdover for Controller E1 0/0/0
Feb 2 10:18:09: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to down (LOF detected)
Feb 2 10:18:09: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se0/0/0:15, TEI 0 changed to down
Feb 2 10:18:10: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for Controller E1 0/0/0
Feb 2 10:18:10: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to up
Feb 2 10:18:10: %ISDN-6-LAYER2UP: Layer 2 for Interface Se0/0/0:15, TEI 0 changed to up
Feb 2 10:18:13: %MARS_NETCLK-3-HOLDOVER: Exiting Holdover for Controller E1 0/0/0
Feb 2 10:18:23: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to down (AIS detected)
Feb 2 10:18:23: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se0/0/0:15, TEI 0 changed to down
Feb 2 10:18:24: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for Controller E1 0/0/0
Feb 2 10:18:24: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to up
Feb 2 10:18:24: %ISDN-6-LAYER2UP: Layer 2 for Interface Se0/0/0:15, TEI 0 changed to up
Feb 2 10:18:27: %MARS_NETCLK-3-HOLDOVER: Exiting Holdover for Controller E1 0/0/0

Muito Obrigado

ThiagoTem como voce postar a

Bruno Rangel — Tue, 03 Feb 2015 13:47:53 GMT

Thiago

Tem como voce postar a configuração do seu Gateway e o output do comando "show voice port summary"

Blz Thiago,

dsobrinho — Wed, 04 Feb 2015 23:49:08 GMT

Blz Thiago,

O seu E1 esta alarmando e consequentemente ele perde referência de clock. Com relação ao alarme que vi LOF quer dizer perda de Frame e vi AIS recebido pelo RX. Como vc relatou que aplica um shut e no shut e volta o E1, parece um problema na interface física do seu E1, (conector, solda etc) . Se vc fica algum tempo sem o E1 e com o Alarm AIS , pode ser um problema na rede da operadora que te entrega esse E1. Antes de tirar qualquer conclusão dê uma revisada nas configurações do seu E1. Faça um teste de loop com um cabo, conector I e balon.

 Loss of Frame (LoF) failure is declared (caused by the unframed nature of the all "1s" signal).

(AIS detected)
A receive (rx) Alarm Indication Signal (AIS) means that there is an alarm on the line upstream from the equipment connected to the port. The AIS failure is declared when an AIS defect is detected at the input and still exists after the Loss of Frame (LoF) failure is declared (caused by the unframed nature of the all "1s" signal). The AIS failure is clears when you clear the LoF failure.

Se isso esta ocorrendo toda hora, dê uma olhada também na sua configuração, para ver se a configuração esta estruturada para framed ou unframed. Caso alguém tenha alterado.

To change the framing format, issue the framing {crc4 | no-crc4} command in controller configuration mode,

for example:

bru-nas-03#configure terminal
Enter configuration commands, one per line. End with CNTL/Z. 
bru-nas-03(config)#controller e1 0
bru-nas-03(config-controlle)#framing crc4

network-clock-participate wic 0
network-clock-select 1 E1 0/0/0

Veja se esta declarado corretamente o tipo de ISDN

isdn switch type primary qsig   ou outro padrão

Segue o link para referencias de alarmes de E1.

http://www.cisco.com/c/en/us/support/docs/wan/t1-e1-t3-e3/14158-E1-alarms.html

Attn

Daniel Sobrinho

tópico Problemas para realizar Chamadas - E1 na VoIP

Problemas para realizar Chamadas - E1

ThiagoTem como voce postar a

Blz Thiago,