Alcatel Unleashed

Come tincho, that is teached on AL University introductory session What happened? You got sleep?

It seems that I lost the most important lesson.

Hi guys, i found this really amusing and informative discussion......fellas i have had the same issue and i have resolved the issue by rebooting the system, but after 2 months nowadays i am again having this issue at the same site, i have rebooted the exchange but my client is getting angry that why is it necessary to reboot every time and this is not a good practice...... Can anyone tell me why this problem occurs and how can we rectify this issue without rebooting, all of you are highly experienced but i am a newbie at ALU PBX, having only a year of experience as a trainee engineer(No certifications).

Hi. Same release as discuss here? I encourage you to open a eSR. Perhpas your situation is different and you have other incidents. Post incvisu -t 50 (during this incident). Regards.

I am having this issue on release 6.1.1-f2502-12-d, and the incidents are below:

19/06/09 07:44:13 000001M|00/18/0/015|=3:1275=Waiting for MF Q23 detector neqt 863, typ_term AUTPOS, cristal 0
19/06/09 07:44:15 000001M|00/10/0/010|=3:1275=Waiting for MF Q23 detector neqt 568, typ_term AUTPOS, cristal 0
19/06/09 07:44:19 000001M|00/14/0/017|=3:1275=Waiting for MF Q23 detector neqt 713, typ_term AUTPOS, cristal 0
19/06/09 07:44:28 000001M|00/14/0/017|=3:1275=Waiting for MF Q23 detector neqt 713, typ_term AUTPOS, cristal 0
19/06/09 07:44:28 000001M|00/16/0/006|=3:1275=Waiting for MF Q23 detector neqt 780, typ_term AUTPOS, cristal 0
19/06/09 07:44:33 000001M|00/18/0/015|=3:1275=Waiting for MF Q23 detector neqt 863, typ_term AUTPOS, cristal 0
19/06/09 07:44:34 000001M|00/25/0/017|=3:1275=Waiting for MF Q23 detector neqt 1160, typ_term AUTPOS, cristal 0
19/06/09 07:44:34 000001M|00/16/0/018|=3:1275=Waiting for MF Q23 detector neqt 792, typ_term AUTPOS, cristal 0
19/06/09 07:44:36 000001M|00/18/0/015|=3:1275=Waiting for MF Q23 detector neqt 863, typ_term AUTPOS, cristal 0
19/06/09 07:44:43 000001M|00/14/0/017|=3:1275=Waiting for MF Q23 detector neqt 713, typ_term AUTPOS, cristal 0
19/06/09 07:44:48 000001M|00/18/0/015|=3:1275=Waiting for MF Q23 detector neqt 863, typ_term AUTPOS, cristal 0

Please there is already people helping on your other post, avoid duplicating the same request all over the forum, trust me you will only gain to get being helped.

OK sir!!

I'm facing the same problem as extensions are not working... and its back to normal after a reboot.
I know we can do a shutdown at a certain time of a day....but can we do a shutdown command to boot it everyday at the same time?

tritel wrote:I'm facing the same problem as extensions are not working... and its back to normal after a reboot.
I know we can do a shutdown at a certain time of a day....but can we do a shutdown command to boot it everyday at the same time?

Yes you can. Search for crontab jobs on this forum.

However you should find a solution to your problem. Day by day reboot of the system doesn't look for me as the best workaround.

Regards.

tritel wrote:I'm facing the same problem as extensions are not working... and its back to normal after a reboot.
I know we can do a shutdown at a certain time of a day....but can we do a shutdown command to boot it everyday at the same time?

Hi. Are you getting incident 1276?. Your solution is not to reboot every day. Have you add new z32 boards or installed new extensions? Regards.