16.3.12 VMLS no way to make a callback thru TUI
Symptom : callback impossible with localstorage with TUI access
Solution : check parameters are used to refine it:
- Callback sender Allowed : if disable no TUI option for callback, Not allowed by default with OT 1.2 for
security purpose
- Direct callback : Capability to make a callback to another extension if parameter disabled ( not very
useful )
- Callback voice prompt : Modify voice prompt when callback
Nota : consult documentation “SA0046-Voicemail phreaking prevention”
16.3.13 No more MWI & Voice mail access on 8082
Symptom : End-user is no more notified on 8082 for new voice mail and voice mail list is always empty
Diagnosis : Check ‘Desactivate MWI notification’ settings in Configuration -> user –> Notification. This setting
is only displayed when ‘Email Notification right’ AND ‘New voice message is attached as a file’ are checked
If ‘Email Notification right’ is unchecked afterward, dynamic 8770 view is collapsed BUT ‘Desactivate MWI
notification’ is kept as it was set and may be enabled
As follow, you well noticed that Desactivate MWI notification is checked for this user
16.3.14 VMLS local callers identified as anonymous
Symptom : Local caller are identified as anonymous user when voice message are let
Diagnosis : Internal directory has been removed from the OT directory search list
Solution : Reactivate the Internal directory or activate the merge with the Internal directory
16.3.15 "UNKNOWN_SENDER" in Voice message notification
Symptom : OT user 31002 calls OT user 31001 which in imm. fwd to voice mail.
He lefts a voice message. 31001 receives a voice notification message on:
- Email / Outlook, MyIC, VHE
On Oulook : caller ID = ok, Voice message listening = ok, callback sender = ok
On MyIC and VHE: sender is not identified, Voice message listening = ok, callback sender = NOK
Diagnosis : In MyIC logs (MPC-1), we can see <identity_data value="UNKNOWN_SENDER" />
Solution : Verify that UDAS gets the "Internal Directory" activated
16.3.16 No way to get VMLS of an Oxe user forwarded
Symptom : No way to get VMLS of an Oxe user forwarded
Solution : in Oxe mgr/application/external voice mail : the oxe user voicemmail directory number => External
Gateway Number : -1 OR see TC about spatial redundancy for Oxe with Open Touch
You can check in particular case mgr / SIP/SIP Gateway/ Cac SIP-SIP : False
16.3.17 VMLS play “You are not granted to access this application”
Symptom : access the voicemail there is a prompt in EN language “You are not granted to access this
application”. Even if you put voicemail box number prompt says “unknown mailbox”
Diagnosis : In tomcat/voiceapplication logs there is one exception after tomcat restarts
18 Feb 2013 14:02:06,083 DEBUG [main]
com.alcatel_lucent.ice.oamp.cms.cmsclient.storage.CmsEntityStorage (CmsEntityStorage.java:144)
<scope uidParameter="id" modelName="tuiVoiceMail" displayNameParameter="number">
To Next Page
Loading...
