3rd UCM installed

[gotchaback]

I'm having problems with a UCM running 8.0.9 and IPO running 8.0.46 When i installed it a little over 90 days ago everything ran fine but now ive replaced it twice and still same problem, it picks up the call but

will not do anything after it picks up (no prompts). I was told that the virtual license wasnt working for some reason even though it shows up in manager as valid; so i was just given a trial license today and was told to just paste it into the config while avaya research and development worked on a fix. It ran fine for the rest of the day and now at 9:30pm i called into the system and got the same problem. This has been going on for weeks now and the end user will be ready to kill me in the morning Anyone have this problem or heard of this and know how it was fixed? I have ran through many many steps with support and i always end up with the same exact result. Ive noticed that others are putting the actual IP address of the UCM in manager but im using 169.254.0.2 under the vm tab even though the address on the UCM is 192.168.50.16 and PBX is 50.15 When I login with webcontrol and look it says that vm and onex is running, but if i stop vm pro then restart it i can get it to run for about 8-9 hours before it stops again. Any ideas at this point would be great!! Thank you in advance

 

[tlpeter]

Try a different version than 8.0.46
Try a different IP500V2
I have a UCM and i never had problems with licenses except for one.
That was that i already had a preferred edition license and the UCM did not create a virtual one because of that.


BAZINGA!

I'm not insane, my mother had me tested!

 

[gotchaback]

do you think removing/deleting the UCM from the system, which i guess would make that virtual license go away and then reinstalling it and just let it see that trial key for preferred edition would help? that would make mine just like yours in the way of you already had preferred ed installed before the ucm so it didnt create a virtual license? thank you for your responce

 

[tlpeter]

Yes you will need to remove it from the config otherwise the virtual license will stay.
The trial license will cause the UCM not creating the virtual edition license.
So remove both from the system (make a copy of the trial license so you can use it if needed.
Then reboot and then start over again.


BAZINGA!

I'm not insane, my mother had me tested!

 

[gotchaback]

Thank you, im on my way to the site now so i can be the first in their parking lot My ticket is at avaya's research and development alone with every type of monitor log, configs from pbx & ucm, snapshots, you name it they asked for it. So im certain they will find the problem its just giving the end user something until they find a fix for my problem and from what im hearing there are a few cases of this problem with the ucm. catalyst replaced it twice before opening a ticket with avaya but i guess that is just standard protocol instead of asking them about it after the second one. Anyway thank you again for the help and i will post how it goes.

 

[tlpeter]

I am curious

So do not forget to do this in this order:

1 Power down IPO
2 Remove UCM
3 Power on the IPO
4 Remove the UCM form the programming -> control unit -> select -> delete
5 Remove virtual preferred edition license
6 save config (needs a reboot)
7 Open config to see if it is still gone.
8 Power down IPO
9 Insert UCM
10 Power on IPO
11 Open config to check if the UCM is there and the virtual preferred edition license is there.

If this fails again then replace the IP500v2
If it then fails then kick Avaya in the but and install an normal VMPro to please the customer.



BAZINGA!

I'm not insane, my mother had me tested!

 

[yankblan]

I've seen this problem once; I suspect one of two things, but haven't had time to recreate it in my lab:

When I used the fax detection through the AA, the prompts stopped working. I would make a regular call, and the line would pick up and I'd hear nothing. Only way I could make it work is by deleting the module and recreating it again. Don't remember if reboot or restarting the service through Linux worked, though.

Other possible cause, is they were using a SIP line through an ATA that would be plugged in an analog CO port. When I tried pluggin the line straight to the fax, it would ring but not pick up; and if I used a fax switch, it would ring straight to phone port; I had the SIP provider look at T.38 settings, and it seemed fine.

So, don't know, maybe it's the fax thing, since a regular voice call on other SIP/ATA lines were fine. Mine was 8.0.X UCM and 8.0(XX) setup too.

 

[IPOtech111]

I had the same problem with a UCM. User would call voicemail, call connected, but user just got dead air. Restarting the service fixed it for a few hours. After days of troubleshooting, going through Avaya, upgrading the module the whole nine yards we decided to take the IP Office and voicemail off of the customers network. Voicemail has been running perfect ever since we took it off the network (about 10 days now).

 

[gotchaback]

ok wait if you took the ucm off the network how are you using oneX services? i didnt bring it up but they have 2 mobile worker licenses and receptionist so i have to have the network. but just so i know for future are you saying you just unplugged it from the switch? Did you have to assign any special IP address to it or did you leave the LAN address that you had in it and like you said just disconnect it from the network? i'm very curious about this fix.

to update this post i have uninstalled the ucm by powering the system down, physically pulling the ucm, bringing it back up and removing the ucm from manager and saving and rebooting then reinstalling it and rebooting again. Once i got a trial key from distributor (im not going to name them again as i did earlier in this post) i installed it which after i saved it the virtual license went away on its on. The ucm will run for about 9-10 hours then no audio, here is a screenshot of manager, well i see i cant do that. Anthony817 so all you did was unplug it from the network or did you remove all traces of the PBX and UCM from the network including the ip addresses, port forwarding, etc. and i guess they dont use many features if they have been like this now for 10 days. no vm to email, not onex, no ip phones, no anything just a plain old digital phone system. Are you doing this just as a test while avaya works on a fix for you too or did your customer just not need any of the IPO's features?

Again thank you to all who have posted to this and i will keep it updated until i find a fix, i will take it off of the network for a couple of days to see if that fixes anything so i can report that to avaya but i cant leave this customer dead like that.

Im setting up a box today and will start running vm pro from it. windows 7 pro with i5 processor and 2 gig's of memory. But i will give your fix a try first anthony817 for two days so i can grab a monitor log to send to avaya's R&D

 

[IPOtech111]

We just unplugged the IP Office from the network. Left the voicemail IP address in Manager at 169.254.0.2. This particular customer was not using IP phones, voicemail to email, one-x or anything else that really required the system to be on the network other than remote access but we turned to pcanywhere to get around that. I do not maintain their data network so I wasnt going to spend too much time on that end looking into the root of the problem and the people that do maintain their network were not helpful. It was just a theory and a test to take it off the network so we tried it and the problem went away. I know it is not a true solution but for our purpose it worked.

 

[gotchaback]

i see, i have given your information to the person i have been working with on this. For a temp solution i just loaded VM Pro on a box and redirected VM services to it until a patch/fix is created. This morning was the first in two weeks that they haven't called saying that the vm is down lol. I guess Avaya will get to it when they can and i just hope that it's before the 90 day free trial licenses runs out :O

Thank you to all that replied to this post and when i get the permanent fix i will post what and where it is.