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!

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

UC Module call flow database issue 2

Status
Not open for further replies.
CIDCrane

CIDCrane

Programmer
Mar 19, 2009
172
US
I have a 500 V2 running 8.1.63. Have the UC module configured. Had my call flows built and recorded. Messages all work, mailboxes work, outcalling works. I hear the Night message when the Night button is pressed. But when I open the Voice mail Pro Client I now get a message "problem with the call flow datadase".
I can nolonger see my modules or groups in the voice mail client. I have stopped the web manager interface and restarted. Polite restart of the phone system. What is crazy is has been working for four hours????? Not sure what to look at... like the call flow is gone and won't let me save a new one. Anyone had this issue?
 
Sort by date Sort by votes
There seems to be an issue with the UCM cards at the moment and the SSD's getting corrupted, however it hasn't presented itself like this before I don't think, but it certainly sounds that way :)


Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)
 
Upvote 0 Downvote
the whole call flow is working but can't be accessed or changed thing? That sound freakishly like someone remotely changed the VM pro callflow using MS remote desktop. That DIDN'T happen, right? If it, did see Global tech tip 183... you're kind of stuck unless you've got a backup callflow saved somewhere. See below:

Database corruption in VM Pro call flows when Windows Remote
Desktop is used as a Terminal Service
When remotely connecting to a Voicemail Pro Server using a method that launches an
additional ‘Console Session’, such as Windows Remote Desktop & Terminal Services,
making changes can cause the Voicemail Pro call flows to disappear from the Voicemail
Pro Client. Once this configuration is saved, it creates a configuration which will not
allow any future changes. Although the Database exists and will continue to run, it will
not allow access to the database in order to make changes. Once the database is
corrupted, the only workaround to restoring call flows is to import a backup call flow
database, then Save and Make Live.

GB
 
Upvote 0 Downvote
GB, that's only relevant when you RDP onto a pc/server running the VM Pro resulting in corruption, in this case it's a UC module :)


Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)
 
Upvote 0 Downvote
Going to replace with voice mail pro and a pc. Seems like there is work to be done on this still. thanks
 
Upvote 0 Downvote
so remote desktopping to a PC which is running a client, and then manipulating the callflow with that remotely controlled client doesn't cause the issue?

GB
 
Upvote 0 Downvote
No, multiple logins running on a server both accessing/manipulating the database is what corrupts it, you can RDP onto a machine and use the client to change a remote VM Pro instance no problem :)


Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)
 
Upvote 0 Downvote
Sorry. I was not trying to access the client from another machine on the network nor was I trying to access the pc with the client running on it via RDP. I was just on the client pc the entire time. Everyting that I had built continued to work but I could no longer retrieve the call flow data base. If I would try to recreate it, it would never keep the changes either. thanks
 
Upvote 0 Downvote
It has become corrupted, via a different method/cause than we mentioned but it has become corrupted non the less :)


Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)
 
Upvote 0 Downvote
I keep wondering if it was something that I did? Worked great for about four hours. I programmed the system offline and had the licesne for the essential edition in the file that I created. Received hardware last minute. Formatted SD card for MU-Law. Then recreated it. Put the SD card into the processor, processor already had all modules in it, including UC Module. SD card upgraded everything once I applied power. I sill had it in Basic mode and without the essential edition license when I threw the config at it. I wonder if the inorder in which I did things may have caused and issue? Again, it worked for four hours of in and out of the vm pro client though......
 
Upvote 0 Downvote
Make it default and boot.
Shutdown the IPO and add the UCM card.
Boot it again and start programming.


BAZINGA!

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

 
Upvote 0 Downvote
are you saying that the order in which I did things may have caused this issue or this is where I should go from here to resolve? This is my fifth deployment using the UC Module and the first time I have had the issue. Should I have Installed all the modules except the UC Module, then boot up. Once up, install the essential edition license and change the mode and then reboot. Then power down the system, install the UC module and go from there, start programming? I programmed this offline with license in the config and then sent it to the system after the processor powered up for the first time with the UC Module already in place. thanks. just want to make sure I am clear on the order...
 
Upvote 0 Downvote
It is not supported in basic mode.
You made a config without the card.
I would format and recreate the card and them boot the ipoffice with card.
But you can try my suggested way.
Do not forget to remove the card from the coffing otherwise it will not be recreated.

BAZINGA!

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

 
Upvote 0 Downvote
When you say I made "a config without the card". By card do you mean SD card or UC Module? When I built the config offline I told the system that the UC Module was part of the config. Should I have built the config offline and not have included the uc module as part of the hardware on the config?
 
Upvote 0 Downvote
He means the UC110. He says the UC110 is not compatible in Basic.
i.e Don't write configs in Basic mode with UC110s in the config.

Inter.bmp


Kids, Kids, It's Avaya. You're both right.
 
Upvote 0 Downvote
Anyone found a solution. Got the exact same problem with an UC110 .My system is 8.1.63 and it is properly licensed
 
Upvote 0 Downvote
There has been reported problems of importing call flow into the UC; always create call flows straight on the UC, or import modules that came from another UC; not a server. PITA when you have all your templates ready, but hey...

 
Upvote 0 Downvote
One thing that I have come to understand recently, IP Office technical tip 252, is that on the voice mail tab under system, the ip address should be 169.254.0.2. I have been giving the UCM an address on the customers' network in the same range as the IP Office. Like I would do if I had a seperate pc running voice mail pro.
 
Upvote 0 Downvote
rhat is because that is the way it should be.
when you put it in then it is auto configured this way.


BAZINGA!

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

 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

Jeffnortel
  • Locked
  • Question
11.1 UC Module database restore
Replies
7
Views
189
budbyrd
budbyrd
Zero6
  • Locked
  • Question
UC module status shutting down 1
Replies
7
Views
337
gkittelson
gkittelson
smrikard
  • Locked
  • Question
C110 UC Module for Voicemail pro 1
Replies
7
Views
217
smrikard
smrikard
ScotttB
  • Locked
  • Question
UC Module missing Gateway
Replies
0
Views
84
ScotttB
ScotttB
NYSTECH
  • Locked
  • Question
IP Office 11.1.3 UC Module Administrator password issue
Replies
0
Views
103
NYSTECH
NYSTECH

Part and Inventory Search

Sponsor

Back
Top