Voicemail
This chapter describes the settings you can make for the voicemail function a location.
Hint
Settings can be specified on the server side. If the option that users are allowed to change settings is also set, a user has the option of changing his or her own settings.
If a user changes the corresponding settings via his XPhone Connect Client, only these ones are used and can not be overwritten on the server side. The administrator has the possibility to deactivate the option whereby users can change their own settings and only then will all users use the specified server settings.
Please note that this is the option enabling users to change their own settings is reactivated, the previously set user configurations become active again and not the settings on the server side.
User settings (which always supercede server-side settings) can only be be deleted by removing and setting up the user new.
Attention
Journals, fax and voicemail messages are deleted in this process.
Using the voicemail function
Here you can set if users of the corresponding location/configuration group are permitted to use the voicemail function. If the voicemail function is required, activate Use this feature.
Integration
Use feature in XPhone Connect Client
Use feature in groupware clients
Use feature in XPhone Connect Client and in groupware clients
Voicemail port
Phone number of voicemail port ** The voicemail number entered here is usually also entered under |um-vm-gnrl-path_en| in the **settings for telephony gateway routing!
This call number defines the forwarding destination when forwarding to voicemail is activated via software. In addition, this phone number is used as the sender phone number when Message Waiting Indication (MWI) is activated. The setup is done under System settings > UM > Voicemail > MWI.
MWI
Define here how to deal with the message wait indication during an enquiry.
Turn on MWI when leaving a voicemail
Turn off MWI when checking voicemail by phone (remote access)
Turn off MWI when checking voicemail using the XPhone Client
E-mail forwarding
Here you can set if a copy of a received voicemail is to be forwarded. If yes, activate Forward copy of a received voicemail and make additional settings.
E-mail to
Enter the email address for the voicemail copy here.
Users may receive copies of incoming voicemails to
the own email address
another email address
Pre-settings for sending of a voicemail copy (only works for users that have not changed their settings yet)
No forwarding
Forwarding to own email address
Text message notification
Configure the text message receipt notifications for voicemails here
Notification by text message when the caller left a voicemail.
Notification by text message when the caller did not leave a voicemail.
User can change the settings.
Remote access
This is where you can change the remote access. If you want to allow this for this location is general, activate Allow remote access and make further settings.
User can change direct access number
Hint
If a user is not allowed to change the direct access number, remove this checkmark. In the XPhone Connect Client, the respective input field is also hidden even for existing users. If the box is checked on the server, the input field is displayed to the user but it is empty (the number entered before is lost).
In case of queries via direct access number: Enforce PIN entry
Allow Connect with caller
Audio format and length
Maximum message length (in seconds)
Data format
CCITT a-law; 8.000 kHz; 8 Bit; Mono; ~7 KB/s
CCITT u-law; 8.000 kHz; 8 Bit; Mono; ~7 KB/s
PCM; 8.000 kHz; 8 Bit; Mono; ~7 KB/s
Advanced voicemail notification settings
Settings when using the XPhone Connect client
Notification by e-mail if caller has left a voicemail.
Notification by e-mail if caller has not left any voicemail.
User can change the settings.
Settings when using Groupware Clients
Show voicemail even if the caller has not left a message.
… but only for greetings with recording function
Show voicemail even if the caller was transferred (call transfer).
Have you found a mistake on this page?
Or is something not formulated well or too vague? Then we look forward to receiving an e-mail, preferably with a suggestion for improvement, to doku@c4b.de. Thank you very much!