IMS Services "Starting" and License Issue

[ThePhoneMn]

Hi all,

I have an IP 406 (3.1.48) and VMPro (3.1.15) with IMS running on a Windows 2003 server. I just inheritited this from Avaya and there is an ongoing problem that Avaya couldnt figure out, so I post it here, to the professionals.

Has anyone run into an issue with IMS services not being able to come out of "starting"? The customer also tells me the VM stops working temporarily about the same time. I researched the even log and found the license's are going invalid. License comes back and the VM starts working again, but the IMS gets hung on "starting".

Also, when they reboot the server (the only way they can get it working again). Each user gets all of their messages (new and saved) sent to their email again.

I did notice the server is running a 733Mhz processor, which I realize is severely underpowered, but would this cause the lockup?

 

[jml2665]

licenses going invalid" might be a simple issue with your dongle or keyserver, does this happen about every two hours?
Not sure if the server being out of spec is causing you trouble, but I do know Avaya support will not help much until it is installed on a proper server

 

[ThePhoneMn]

The licenses go invalid about twice a week. I read something about feature key server 1.0.0.5, does anyone know where this is available?

 

[jml2665]

the current KeyServer is 1.0.0.5 and it's on the 3.1.56 ADMIN CD,

do you know why you are loosing connection to your key server?? Are you running a firewall?

 

[fonedoc]

Is this a stand alone system or part of a Small Community Network (SCN)?

Fonedoc

 

[ThePhoneMn]

Stand-alone system, although there is a WAN port configured, but no longer used. Customer states they were going to use the IPO as a RAS, but bought an external RAS instead.

 

[CarGoSki]

If you have 2003 sp1 then you need to run the IMS services in a startup script. These services try to start before the firewall starts. Running them from a startup script allows the services to start after the firewall is up.

You could set the firewall service to manual then restart your server. Once restarted and since the firewall has been disabled the IMS services will start.

Or are you not running sp1?

 

[ThePhoneMn]

To answer your question, I am running SP1.

Would your firewall fix apply if the services get stuck at "starting" or "stopping" day(s) after the server was started?

 

[CarGoSki]

I don't know since anything can happen on a windoze box. You may want to try disabling the firewall to see if this will remedy your problem.

I assume that you built the group policy for sp1 and applied the firewall.bat to your server? Also I assume that the nic is plugged directly into an IPO lan port.

 

[ThePhoneMn]

Those are good questions... I will check those. I just acquired this account and havent been onsite yet. The customer gave me a login to his VM Server, but it is limited and Im unable to run the SCW, look at TCP/IP settings, etc.
Thanks for all your help, I posted hoping someone ran into this before and I could walk into the site and be the hero.

 

[Rdy2Taxi]

I have the same issue(s) with (1)IMS not starting at boot time, (2)IMS appearing to hang every couple days without generating any errors to event logs and (3)IMS not able to delete certain messages and getting out of sync with Exchange.

My vendor and I installed the new IP Office system last December. IMS not starting at boot showed up almost immediately, on maybe VMPro 3.1.16.

I am at the latest software revisions - Admin 3.1.56 CD, VMPro 3.1.18 CD with .5 patch. I am running KeyServer, VMPro, IMS, TTS and DeltaServer on top of Win2K3R2. I just completely rebuilt the server, a new HP/Compaq DL320 G4. In the meantime I built a temporary server on a Gateway Profile 4 desktop that operated quite well.

The server NIC is plugged into a port on the IPO 406's switch. Windows Firewall is configured, but disabled on the NIC. Ran SCW several times (Avaya 'support' added every conceivable port and executable to the firewall). Ran the fw batch file from TechTip 49.

I've tried delaying the services startup sequence by making VMProServer service dependent on W32Time to insure good LAN connectivity. It did, but no help, IMS(Voice) still finds "invalid or unrecognized license".

After a server restart, I am able to stop-n-start the IMS services manually. But I also have to reboot the IPO 406, since at this point Manager cannot find an IPO device.

So, could we have crappy flash memory in the 406? Do other USB devices on the server (hard drive, mouse, etc) cause a conflict with the USB key?

I'll let you know what I find.

 

[phantomiii]

I had a similar issue on a WinXP Pro, (Which I know isn't supported for IMS) I made a startup Bat file to execute the IMS voice service after 30 seconds on a reboot, (because it wouldn't start due to invalid license bug) and set the Voicemail server to auto-login. I have 2 of these working for customers.

 

[Rdy2Taxi]

Phantomiii, that's certainly the work-around for the IMS startup issue. I'm not quite ready to capitulate to Avaya support's notion that there's nothing wrong with their software. That doesn't fix the underlying issues or improve the product. Tens o' thousands of dollars later I expect more from a vendor.

 

[Rdy2Taxi]

My VMPro server is configured to autologon. IMS(Voice) still finds "invalid or unrecognized license" at startup. A startup batch file stops and restarts the IMS services successfully after logon. I also have to reboot the IPO 406, since at this point Manager cannot download the config from the IPO device to check for valid licenses.

 

[phantomiii]

Well Manager should already be showing valid licenses in a config. Really the IPO 406 would be checking with the license key server for a valid license, on a reboot of the 406. So your License key server must always be up and running before you ever reboot the 406.

btw, My batch file delays for 60 seconds after auto-login before trying to start up the IMS services. This delay was needed for it to correctly start up. Then again, I'm on WinXP Pro so your mileage may vary.

 

[Rdy2Taxi]

Yep, I agree.

Even though Key Server service starts successfully (little red icon and everything), IMS and the 406 cannot find valid license(s) until: 1)Stop and restart IMS, 2)power-cycle the 406.

My local vendor and I finally persuaded Avaya support to escalate the issue. We shall see....

 

[ThePhoneMn]

Rdy2Taxi, if you get any info, please post it... it would be greatly appreciated.