Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Leave Action for Groups disappear in VMPRO after reboot

Status
Not open for further replies.

FreightTrain

Programmer
Jun 12, 2012
169
US
I have a 9.0.3 IP Office Server Eddition. So Im building my 30 groups in vmpro and creating a leave action. From there my start point goes to the "BusinessHours" module I created for the each of the 30 departments. I also have 5 more modules per department but those are not being pointed from leave start point. So when I have to reboot the server after making changes in manager over half of my group's leave action is gone, but if I scroll down to the modules I will see the ones I'm missing and they read like this "Recovered.Groups.PsychServices"

This has happen back to back now and I'm getting so frustrated. Please can anyone help me?

"When all else fails call for backup
 
yup sounds like you are not logged into the voicemail pro client as Administrator

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.
 
Ian logged in as administrator. The thing that throws me off is the second time it happened it kept some leave action that it didn't before. The itching I'm trying is instead of dragging the module to the start point I'm just going to do a go to action and find module. What you think?

"When all else fails call for backup
 
Through my laptop using vmpro

"When all else fails call for backup
 
And just tried what I said before and same thing. I feel like pulling out my hair.

"When all else fails call for backup
 
Franklin, RDP is not an option on a server edition as it is a Linux machine :)

FreightTrain, i have seen something similar.
What version are you running?


BAZINGA!

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

 
I'm running 9.0.3 I think I got it to work by building it one at a time and saving and making live then log out and close program. It sucked cause I had to do it 15 times. The other issue I'm having is I have 3 PRIs, 2 on expansion1 chassis and 1 on expansion 2 chassis. Even thought the PRIs are open tunnels I have to have the 2 PRIs on line group 1 and the 1 PRI on line group 2 for incoming and out going. So then I put in the 300 DID's, had to do it Twice being I have 2 line groups for incoming cause the PRIs are set to roll over from each other. But now I have in my expansion error pane saying that I can't have duplicate line IDs. Which I see that it does show that I do. But when I got to the solution incoming calls to take th out they are not there. I do a reboot thinking that will fix the weird issue but it's still there. I'm really starting to dislike server Eddition. By the way I have server edition with 2 500 expansion cabinets. Then I have 16 30 DS modules and 1 16 analog module. Each 500 has 2 8 ds base cards w/4 ATM, and 64 VCM card w/ 2u PRI. One cabinet has a 4 port expansion card. In vmpro I have to build over 300 modules with each having condition editors.

"When all else fails call for backup
 
Where did you program those incoming call routes? on the server or the IP500v2?
But having 16 DS30's is not where the server edition is made for :)
And why do you have 3 PRI's and not SIP trunks?
The server edition is IP only and my opinion is that you should go IP for phones and trunks.
This way you do not need those 16 DS30's nad those PRI's at all.

BAZINGA!

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

 
I totally agree this is what the county spect the job for. I keep saying why are working with digital and why do I have a server edition. All I need was either VoIP or SCN license. This has been the biggest nightmare. Also I programmed the DIDs on the server not the 500. At first I did on the 500 but realized that was wrong and deleted it. But I still get a hand full of errors.

"When all else fails call for backup
 
tlpeter

you're correct, sorry ! I thought it was not Server Edition, so I read only the problem.
 
FreightTrain, On our server edition i just programmed the incoming call routes on the IP50v2 as we still have ISDN2 lines at the moment.
I did not program them on the server and it works fine.
The server edition is just a bit different and to be honest i like it.


BAZINGA!

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

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top