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 bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

3.0.59 merge issue?

Status
Not open for further replies.

Morrack

Vendor
May 13, 2004
1,264
CA
Has anyone had any problems merging configs on 3.0.59 systems? I have a couple sites that are locking up and it seems like it happens when we merge a config, but not positive that's the problem yet.

Actually I would love to hear any feedback (ie bug reports) on 3.0.59, haven't had the time to keep up here lately so may have missed some good info.



Peter Sherwood

Morrack Consulting
 
FYI One bug I have discovered in 3.0.59 is if you want to record inbound calls to a huntgroup automatically, the messages show up in the individual agent mailboxes instead of the huntgroup mailbox like they are supposed to. Had a customer working fine for recording, upgraded to 3.0.59 and this started happening, downgraded to 3.0.44 and they were fine again.


Peter Sherwood

Morrack Consulting
 
Sounds like someone has used the incorrect version of manager and the db is corrupt

Open manager, open the system area, press ok

The save disk icon will come up, do an imediate reboot

This should hopefully fix any db errors.

It might be idea to change the system password and only give access to people with the right version of manager
 
It's definately the correct version of manager, and no there are no rogue copies floating around.

Has anyone seen merge issues with 3.0.59?


Peter Sherwood

Morrack Consulting
 
I had a site were the IPO (upgraded from 3.0.44) rebooted after a few merges, a complete reconfiguration solved the problem.

Another thing i have seen several times is that all extensions duplicated themselves after a reboot.
Very annoying because then no external calls can be delivered, erasing the duplicates and a reboot solves the problem.

Assisted transfer in 3.0.59 and VM Pro 3.0.17 doesn't work properly, if the inbound caller disconnects before answering then the last ringing extension will remain ringing until answered although there is no caller anymore.

Anither thing i noticed: if you reboot a IP Office 3.0.59 from the Manager then the Hot Desk users who were logged on wil be logged on after the reboot. A reboot without manager gave a random result on this ( some were logged on and others not ).

 
To directly answer your question...

I use 'merge' all the time (usually to change IP routes to our remote systems) and have never had any problems with it (yet!).

This unit was a direct upgrade from 3.0(44) to 3.0(59) btw.

I can only assume some sort of db corruption has sneaked in - time to get out that fine tooth comb I think ;)



Old school Alchemy engineer - trying to keep up with the times [hourglass]
 
merge also cause voip calls to clip on 5620 handsets
 
I use a 5602 and that doesn't clip. It sounds like 3.0.59 has a mind of it's own. Wierd eh?

Old school Alchemy engineer - trying to keep up with the times [hourglass]
 
Yes , must be a locale problem , 80 % of the bugs are found in the eng locale.

I suppose its a British Thing.
 
I've also had a site with a 406V2 and 3.0.59 and it locks. Following the SysMonitor, it looks like the TFTP locks first from rogue requests, and then eventually the whole system locks. Pulling the power sorts it out, until doing a few merge configs again.
I've had a lot of sites develop anomilies with merge configs, such as duplicate users, constant ringing, etc. Build 59 seems to do a lot of weird things with merges.
 
At least I'm not crazy. I was really hoping for a "Sept" maintenance release to appear on avaya's website Oct 1. What's a poor tech to do? I can't merge customers with 3.0.59 because I'm rolling the dice. I can't downgrade them to 3.0.44 and merge them because they will lose random button programming. I can't take them down to 2.1.35 because they have some 56xx sets. Every bloody change is now a reboot until we get a new maint release :(



Peter Sherwood

Morrack Consulting
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top