Author Topic: Help with mitell 3300 and R2 NSU  (Read 1996 times)

Offline alejonomada

  • Contributer
  • *
  • Posts: 12
  • Country: ve
  • Karma: +0/-0
    • View Profile
Help with mitell 3300 and R2 NSU
« on: April 22, 2015, 11:43:31 AM »
good, greetings to all, I need help regarding my failure mitell 3300. I have problems with time sync between my central and service provider. connect my main supplier by a node NSU r2. and after a time of 10 minutes the call is dropped. Colocare below the fault shown me.( i paste the error, this fail is every 10 minuts)
My provider tells me to be a failure at the time of relog between central and them, that should change this time or disable synchronization Sync to synchronize only with the supplier.



| WARN GW | 15/04/22 11:00:15 | D-channel DOWN on AFC link 1 [dch.cpp @ 1316] | 1234
| warn AFC | 15/04/22 11:00:15 | D-channel is DOWN on link 1 | 6
| info AFC | 15/04/22 11:00:15 | Link 1 down due to PRI | 2
| info AFC | 15/04/22 11:00:16 | MTNETSNC phase shifts: 1 | 8
| warn AFC | 15/04/22 11:00:16 | MTNETSNC unstable phases: 93: 0fe 0fe 0fe 0fe 0fe 0fe 0fe 0fe 1fe | info AFC | 15/04/22 11:00:16 | MTNETSNC select clock sync for link 0 health is PASSED | 8
| WARN GW | 15/04/22 11:00:16 | D-channel DOWN on AFC link 0 [dch.cpp @ 1316] | 1234
| info AFC | 15/04/22 11:00:16 | MTNETSNC disable netsync source link 1 requested | 8
| warn AFC | 15/04/22 11:00:18 | D-channel is DOWN on link 0 | 6
| info AFC | 15/04/22 11:00:18 | Link 0 down due to PRI | 2
| warn AFC | 15/04/22 11:00:18 | layer 1 FRAME alarm ACTIVE for link 1 | 6
| warn AFC | 15/04/22 11:00:18 | D-channel is forced DOWN for link 1 | 6
| warn AFC | 15/04/22 11:00:18 | layer 1 FRAME alarm ACTIVE for link 0 | 6
| warn AFC | 15/04/22 11:00:18 | D-channel is forced DOWN for link 0 | 6
| ERROR GW | 15/04/22 11:00:20 | [T1-C10] LINE FSM ERROR : Event<LINE_CLR_BWD> occurred in state<LINE | ERROR GW | 15/04/22 11:00:20 | [T1-C11] LINE FSM ERROR : Event<LINE_CLR_BWD> occurred in state<LINE | ERROR GW | 15/04/22 11:00:20 | [T1-C13] LINE FSM ERROR : Event<LINE_CLR_BWD> occurred in state<LINE | ERROR GW | 15/04/22 11:00:20 | [T1-C15] LINE FSM ERROR : Event<LINE_CLR_BWD> occurred in state<LINE R2Error 11h00m20s-810 [T1-C10] Error in UAPI_DISCONNECT_INDICATION: can = 0 
R2Error 11h00m20s-840 [T1-C11] Error in UAPI_DISCONNECT_INDICATION: can = 0 
R2Error 11h00m20s-870 [T1-C13] Error in UAPI_DISCONNECT_INDICATION: can = 0 
R2Error 11h00m20s-960 [T1-C15] Error in UAPI_DISCONNECT_INDICATION: can = 0 
| WARN GW | 15/04/22 11:00:21 | D-channel UP on AFC link 0 [dch.cpp @ 1316] | 1234
| WARN GW | 15/04/22 11:00:21 | D-channel UP on AFC link 1 [dch.cpp @ 1316] | 1234
| INFO GW | 15/04/22 11:00:23 | CP STAT: CP60M-OUT 184 CP60M-IN 166 [cp.cpp @ 959] | 1234
CP STAT: CP60M-OUT 184 CP60M-IN 166
| warn AFC | 15/04/22 11:00:23 | layer 1 ALERT ALL CLEARED alarm clear for link 1 | 6
| warn AFC | 15/04/22 11:00:23 | layer 1 ALERT ALL CLEARED alarm clear for link 0 | 6
| warn AFC | 15/04/22 11:00:23 | D-channel is up on link 0 | 6
R2Error 11h00m25s-815 [T1-C10] Error in UAPI_DISCONNECT_CONFIRMATION: can = 0 
R2Error 11h00m25s-845 [T1-C11] Error in UAPI_DISCONNECT_CONFIRMATION: can = 0 
R2Error 11h00m25s-875 [T1-C13] Error in UAPI_DISCONNECT_CONFIRMATION: can = 0 
R2Error 11h00m25s-980 [T1-C15] Error in UAPI_DISCONNECT_CONFIRMATION: can = 0 
| info AFC | 15/04/22 11:00:29 | Link 0 up (PRI) | 2
| warn AFC | 15/04/22 11:00:29 | layer 1 FRAME alarm clear for link 0 | 6
| warn AFC | 15/04/22 11:00:29 | layer 1 REMOTE FRAME alarm clear for link 0 | 6
| warn AFC | 15/04/22 11:00:29 | D-channel is up on link 1 | 6
| info AFC | 15/04/22 11:00:34 | Link 1 up (PRI) | 2
| warn AFC | 15/04/22 11:00:34 | layer 1 FRAME alarm clear for link 1 | 6
| warn AFC | 15/04/22 11:00:34 | layer 1 REMOTE FRAME alarm clear for link 1 | 6
| info AFC | 15/04/22 11:00:34 | Slips enabled for netsync link 0 | 18
| info AFC | 15/04/22 11:00:34 | MTNETSNC switching to long term accumulator mode for link 0


Offline alejonomada

  • Contributer
  • *
  • Posts: 12
  • Country: ve
  • Karma: +0/-0
    • View Profile
Re: Help with mitell 3300 and R2 NSU
« Reply #1 on: May 15, 2015, 10:33:22 AM »
Read the fail, the fail was the company of telephone. and now my mitel is ok, and no have an alarm. cool!! ;D


 

Sitemap 1 2 3 4 5 6 7 8 9 10