Alcatel Unleashed

In a system OXO rls 6.1 if for some reason the team give a shutdown, the 2 ports voicemail change their position at random. Does anyone know because this happens or as may be fixed ports?

Initially, the system had to make an update to 610_007_002 due to problems with the phone in general.

Thanks and happy new year!

Batab,

In a system OXO rls 6.1 if for some reason the team give a shutdown, the 2 ports voicemail change their position at random. Does anyone know because this happens or as may be fixed ports?

Not quite sure what you are meaning is there any chance of some screen shots to show what is going on?

91-001-01 898 VoiceMailUnit
91-002-01 897 VoiceMailUnit VoiceMail A
91-003-01 894 VoiceMailUnit
91-004-01 893 VoiceMailUnit
91-005-01 892 VoiceMailUnit
91-006-01 891 VoiceMailUnit VoiceMail B
91-007-01 890 VoiceMailUnit
91-008-01 889 VoiceMailUnit

The picture shows 2 ports voicemail working, whether it is accessible reset the OXO those ports stop working and displayed as "Out of service" Refused SW limit. I find among the 6 remaining ports which are running again.

In fact, the 2 ports useful when you start the OXO were 91-001-01 and 91-002-01. We change the IP address and then the reset,after that diplayed as "Out of service" Refused SW limit. Ports shown now are the ones who were available to use, any idea?

To be honest I can think of no reason why the OxO would do this, but a possible work around would be to take the the ports 91-003-01 to 91-008-01 and manually take them out of service and leave the first two as the only ones that are in service.

I think that this should take presidence on a restart and stop the random movement of the active ports.

Check on licenses how many ports for VM they have.
Then correct the numbers assigned to the VoiceMail ports, the order is reverse from VoiceMail ports "logical position".
Check all Voice Mail ports from the lower to the higher number and keep the same "active" VM as you have on the license.
OXO R6.1 has some problem with VM ports, sometimes some of them goes to "out of service", but after you put back to service it works fine forever.

Regards,
Tux