eastcoast10
Technical User
A regional offices has IP Office with embedded voicemail, a relatively new system to us.
One of our employees left and we simply assigned that employees former extension to the replacement. We use IP Office Manager and reconfigured the name and reconfigured the voicemail passcode for the new user.
We ran into a problem. The voicemail passcode didn't seem to work, either the new one that was assigned or the passcode that was used by the original user. Also if you phoned in and used dial by name it worked with the new employee's name but the voice prompt and message was from the old employee. The new employee indicates however that they did change their greetings.
After a number of futile attempts to resolve this including rebooting the whole switch after hours I ended up simply rebuilding the account.
Question:
Is there a method of having a new employee assume an existing extension or is it always advisable to delete and rebuilt?
Now that the employee has been rebuild:
the employee indicates that when they dial *17 to route to voicemail they are not being asked for passcode. The switch is configured to provide external access to voicemail by having *17 configured against one of the auto attendant menu keys. When I come in remotely and access the new voicemail box I do get a request to provide passcode and the passcode previously configured provides access. Similarly if the employee phones *17 from another extension they go to voicemail and have to provide mailbox and passcode.
Question:
Is this a feature of IP Office with embedded voicemail; if you phone *17 from your own set to go to voicemail it lets you in without passcode; if so how do you turn it off?
One of our employees left and we simply assigned that employees former extension to the replacement. We use IP Office Manager and reconfigured the name and reconfigured the voicemail passcode for the new user.
We ran into a problem. The voicemail passcode didn't seem to work, either the new one that was assigned or the passcode that was used by the original user. Also if you phoned in and used dial by name it worked with the new employee's name but the voice prompt and message was from the old employee. The new employee indicates however that they did change their greetings.
After a number of futile attempts to resolve this including rebooting the whole switch after hours I ended up simply rebuilding the account.
Question:
Is there a method of having a new employee assume an existing extension or is it always advisable to delete and rebuilt?
Now that the employee has been rebuild:
the employee indicates that when they dial *17 to route to voicemail they are not being asked for passcode. The switch is configured to provide external access to voicemail by having *17 configured against one of the auto attendant menu keys. When I come in remotely and access the new voicemail box I do get a request to provide passcode and the passcode previously configured provides access. Similarly if the employee phones *17 from another extension they go to voicemail and have to provide mailbox and passcode.
Question:
Is this a feature of IP Office with embedded voicemail; if you phone *17 from your own set to go to voicemail it lets you in without passcode; if so how do you turn it off?