Alcatel Unleashed

Office r6.1

when I'm trying to set an secondary set on a user (4039/mob400) I get save/restore problem and the pbx reboots? why?

the message is: save/restore failure code:20491

And when I'm looking in the history table, it says that the cause is OMC or MMC?

Help Anyone

What version of OMC are you using current suggestion from A/L is 610.15.1b but I nave also used 700.9.1a without any issues

K.

I have tried 610.15.1b and also 700.9.1a

I read in the expert manual that it is not allowed to use multi set at an attend seat, I can understand that I will get an warning message but not why it does reboot. It is not me that has set up this pbx, I have take over the support.
So their are some attendant seat that already have an multi set 4039 whit an Mob400. Why can't set up one like that?

I talked to A/L and they first suggested that I used the OMC (610.15.1b) that was released to this software of pbx,because the 700.9.1a could have some bugs in it. Didn't work.
I tried a warm reset and that didn't work either.
So I guess that I have to do an Lola on it and set it up again. ? ? what would suck...

But the funny thing is that I can do other changes, like barring tables or the numbering plan.

May by, I will make an cold reset of the pbx this weekend and set it up again. It's an risk because the costumer is 350km away

Suggestions are welcome =)

Maybe remove them from attendant group and then associate a tandem?

Now I tried:

Remove the user from the attendant group.
Add his Mob400 as an secondary set.
Then the pbx reboots

I can add his Mob400 in the same Attendant group but the other Attendant has an secondary set, Mob400. I want it to be the same, and may by in the future it is not so good that the pbx reboots after an change :S

Thanks!

Try cold reset and manually rebuild your database.

Just a remind, my friends:
Don't use OMC 700 xxxx to manage any OXO R6.1.

I got one person that is using OMC 700 and after he disconnect the pbx resets and keeps reseting random. For any reason the OMC 700 is corrupting the OXO R6.1 database.

Try to use the OMC 610 22.1a (latest delivered for R6.1)

Regards,
Tux

Okej,

I will do an cold start and then set up the pbx again.

Thanks!