IP Office with random Cold Starts??

[ianbachus]

Hello. I have an IP406 Office that is randomly restarting. Its running version 4.0 Manager software. There are two modules connected to the IP Office 406. Those are an "IP400 Digital Station" and an "IP400 Phone". The phone system performs like a champ but reboots for no apparent reason. It doesn't happen every day but sometimes it reboots multiple times in one day! I am the only person ever in the manager so I know that no one else is playing with it. If I look at the audit trail the system is cold starting itself with no PC login or no PC IP address. It's almost as if someone is unplugging it and plugging it back in but the server room is always locked. Could this be an issue with our UPS? The only devices plugged into the UPS are solid state stuff like a few routers and switches. Nothing that is drawing a lot of power and all the other devices seem to be functioning fine. I've tried swaping the power supplies to no avail. Anyone have any ideas?

On another note, this may be related so I'm mentioning it here too. There are three customer service agents which I have forced to login to their phones. I have setup an idle time out of four hours for all of the them so it logs them out automatically. Every now and then just one their phones will log in automatically. It "may" be happening when it reboots but I'm not sure. Any ideas as to why his phone would log in by itself? I know that this is true because I will come in here in the morning and check his phone. I'll check it a little later and sure enough, it's logged in and the employee isn't even in the building yet!

Thanks for your help and time!

 

[573dawn]

I too have had this issue, as well as others. It seems to be better after having replaced the DS unit, but there could be a problem with the software version. I am not by any means experienced, but you might check out this thread:

http://www.tek-tips.com/viewthread.cfm?qid=1378914&page=1

 

[ProviderReborn]

Also just check you have no huntgroups overflowing to itself.
May be worth posting up some monitor traces and see what comes up.

 

[tlpeter]

the phone automaticly logging in sometimes ???
deletethose users and recreate them
als try without the idle time for log out
also run monitor
just let it run and when the ip office rebooted then look back in the trace
when you found an contact lost in the trace put a the trace overhere with a cpuple of minutes before the contact lost


ACA - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[janni78]

If you're on 4.0.5 you probably should get it up to 4.0.7 and see if the problem goes away.

Had a lot of trouble with 4.0.5 getting reboots with TLB errors.

 

[Shine52]

What release is this. Prior to 3.2.57, paging 5400 series telephones via a hunt group will cause reboots too.

Figure it out damn-it!

 

[ianbachus]

Thank you all for your responses. We are running 4.0.5. I'll try 4.0.7 and see if it goes away. Yes, we do page 5400 series phones but I've never noticed a reboot afterwards. I setup logging to txt files with the sysmonitor. Hopefully I'll be able to catch was is causing it. If I figure it out I will post the issue here to maybe help out the next guy.

Thanks!

 

[tlpeter]

read the tech bulletin
you are using 54xx phone and they have a special part because of the firmwareupgrade they are going to do

http://support.avaya.com/japple/css...eID=306419&temp.bucketID=264968&PAGE=Document

ACA - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[ianbachus]

Ok I finally got a cold start with logging turned on. Here are the lines surrounding the reboot. Does anything stick out? Thanks!!!

**********************************
**********************************
**********************************
**********************************

176867546mS CMExtnCopyProcessMsg: v=12
CMInformation
Line: type=DigitalExtn 4 Call: lid=0 id=3048 in=0
Called[#] Type=Default (100) Reason=CMDRdirect
BChan: slot=10 chan=14
176867547mS CMLineTx: v=2
CMInformation
Line: type=AnalogueLine 2 Call: lid=0 id=3050 in=0
Called[#] Type=Default (100) Reason=CMDRdirect
BChan: slot=10 chan=14
IE CMIERespondingPartyName (228) PolinaR
IE CMIERespondingPartyKName (229) Polina Ryshkova
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:101 N:100 R:4) number=220
IE CMIEDeviceDetail (231) LOCALE=enu HW=8 VER=4 class=CMDeviceStdPhone type=27 number=9986 channel=0 gain=0
176869871mS CMExtnRx: v=220, p1=0
CMReleaseComp
Line: type=DigitalExtn 4 Call: lid=0 id=3048 in=0
176869871mS CMExtnCopyProcessMsg: v=12
CMReleaseComp
Line: type=DigitalExtn 4 Call: lid=0 id=3048 in=0
176869874mS CMLOGGING: CALL:2007/07/0510:16,00:00:42,000,220,O,91800847275014127570770990853#230#32508#14127570770990853#15818#75691#,91800847275014127570770990853#230#32508#14127570770990853#15818#75691#,PolinaR,,,1,,""n/a,0
176869875mS CD: CALL: 0.3048.0 State=2 Cut=2 Music=0.0 Aend="PolinaR(220)" (10.14) Bend="Line 2" [Line 2] (2.2) CalledNum=1800847275014127570770990853#230#32508# () CallingNum=220 (PolinaR) Internal=0 Time=43816 AState=0
176869876mS CD: CALL: 0.3048.0 Deleted
176869877mS CMExtnCopyCallLostMsg: v=12
CMReleaseComp
Line: type=NoLine 0 Call: lid=0 id=3048 in=0
Cause=16, Normal call clearing
176869877mS CMExtnTxP: v=12
CMReleaseComp
Line: type=NoLine 0 Call: lid=0 id=-1 in=0
Cause=16, Normal call clearing
176869879mS PRN: Alarm log full
176869879mS PRN: Begin Stack Trace
176869879mS PRN: pc=ff7d91d8
176869879mS PRN: lr=fee6f770
176869879mS PRN: findfunc ff7d9230 ff931694 ff7d9320 ff547ef0 ff5d119c ff54385c ff543820 00000000 00000000 00000000
176869879mS PRN: End Stack Trace
176869879mS PRN: .FATAL TLB Data address=00370065 d=5 pc=ff7d91d8 ff7d9230 ff931694 ff7d9320 ff547ef0 ff5d119c IP 406 DS 4.0(5)

********** contact lost with 192.168.16.31 at 10:17:36 5/7/2007 - reselect = 1 **********
******************************************************************


********** SysMonitor v6.0 (5) **********

********** contact made with 192.168.16.31 at 10:18:00 5/7/2007 **********

********** System (192.168.16.31) has been up and running for 28secs(28843mS) **********


********** Warning: TEXT File Logging selected **********



********** Warning: TEXT Logging to File STARTED on 5/7/2007 10:18:00 **********

 

[ianbachus]

Also, regarding the Agent phones that log on mysteriously. Well I discovered today that it only happens after one of these sudden reboots. Why would this happen?

 

[ProviderReborn]

Whats all this info about?
CMLOGGING: CALL:2007/07/0510:16,00:00:42,000,220,O,91800847275014127570770990853#230#32508#14127570770990853#15818#75691#,91800847275014127570770990853#230#32508#14127570770990853#15818#75691#,PolinaR,,,1,,""n/a,0
176869875mS CD: CALL: 0.3048.0 State=2 Cut=2 Music=0.0 Aend="PolinaR(220)" (10.14) Bend="Line 2" [Line 2] (2.2) CalledNum=1800847275014127570770990853#230#32508# () CallingNum=220 (PolinaR) Internal=0 Time=43816 AState=0

Looks far to complicated.

 

[ianbachus]

I honestly have no idea what is going on there. I was hoping you did? =)

 

[ProviderReborn]

If I had a trace like that the 3 places I would look is User Shortcodes/System short codes and indeed LCR/ARS and see what modifications it is doing.

Not saying thats the cause but all that looks far to complicated. Make a normal call on your system and post up the monitor report.

Get extension 220 to ring the same number she did before and see if it reboots your kit.

 

[ianbachus]

Ok she did it again and sure enough it rebooted. She is calling an automated number and punching in a series of random digits and # signs. This seems to cause the system to reboot! Any ideas as to why or how to stop it? Maybe there is a system variable somewhere that holds the numbers pushed. If the size goes out of range the system restarts? Hummm??

Thanks!

 

[ProviderReborn]

Ok so we are on to some thing. What is the actual key strokes dialled and how does it compare to your trace, If this is some sort of banking or other login service dont worry about posting it up. But look at how the real digits dialled compared to the trace.

Cheers.