I have one user that gets dropped voicemail messages every so often. Are these voicemails kept on the Voice Processing Unit somewhere so that I can review the message?
Has anyone experienced this and found a fix. We have already deleted the mailbox and recreated it.
Define dropped voicemail. They are lost, partial recordings, etc?
Recordings are kept in the AVDAP folder. The best way to extract them is through a Voicemail Save. Operations\Database Operations\Voice Processor Save. Choose Voicemail and check mark the boxes below. The next page will allow you to choose which mailboxes to back up. Afterward, open up the files in the save location. An N denotes new messages. An S denotes saved messages. They are in R24 audio format. I have an R24 to WAV converter if you need it.
This may not be the solution you need. It depends on what you want to do.
I just obtained more information from the user. The full voicemail is actually there. Apparently they drop the call due to insufficient bandwith.
Strange that it only happens to this one user?
"Insufficient Bandwidth" is a kind of catch all. Any interruption in communication triggers this alert. Our network guy hates me for it. Check the physical stuff first. The RJ45 connection into the phone can make a pretty serious angle. So change the cable. Also, check the cabling between the phone and the network switch. if it continues, swap out the power supply. If it continues, swap out the phone, but hang on to the original one. If it stops, send the phone in for repair. If it continues, I don't know what I'd check next.
LOL thanks for the tips, it's not an IP Phone though. So it had a standard RJ11 connector. It's odd because nobody else in that office gets this message. I will try swapping the phone and cable.
I took your insufficient bandwidth statement to mean it was an IP phone. You could also try reprogramming the extension to another card address.
Something doesn’t add up. Does the mailbox reside at the same node as the extension, or is it off-node? The connection is lost when the user is listening to the message replay?
Yea it doesn't add up. He said every so often when listening to his vm this happens and occasionally when on a call. Nobody else in this office has mentioned this problem.
The VM is off-node but he states it's happening to calls also. Primarily it happens on his VM though.
OK - not a VM issue, but a network issue. Maybe he's the only one who notices.
Run an error log and look at the NDL file. That's the Network Device Log. It will show incidents of Insufficient Bandwidth, which probably happen more than you're aware.
We are again revisiting this issue. The end user says it still happens and previously we did not do any further troubleshooting on this becaue the user just had the VM sent to his email. Now he is back to checking it via the phone and the same issue is happening.
When you say run an error log do you mean run the Diagnostics Monitor or is there another error report within Session Manager.
I'm adding the followig to see if anyone can see anything here:
-09:516- 00:01 03-13 M2036 INF HW CP Established IP LINK To node 6
-09:517- 00:33 03-13 M3096 INF EG CP Network Time Synchronization By Node 1 Ignored - NTP Synchronization Enabled
-09:518- 02:00 03-13 M2094 INF HW CP Time Changed For Daylight Saving Time
-09:519- 09:02 03-13 M3259 INF EG CP Node 9 Enabled Day Mode
-09:520- 11:23 03-13 M3510 INF EG CP Set Date/Time Feature Code Entered By '1900'
-09:521- 14:57 03-13 M3259 INF EG CP Node 9 Enabled Night Mode
-09:522- 23:59 03-13 M1015 INF DB CP DB Backup Save: Starting Save
-09:523- 23:59 03-13 M1015 INF DB CP DB Backup Save: Successful
-09:524- 00:00 03-14 M2039 INF HW CP Dead Socket Response From node: 6 Reason(304): Broken pipe
-09:525- 00:01 03-14 M2036 INF HW CP Established IP LINK To node 6
-09:526- 01:33 03-14 M3096 INF EG CP Network Time Synchronization By Node 1 Ignored - NTP Synchronization Enabled
-09:527- 08:56 03-14 M3259 INF EG CP Node 9 Enabled Day Mode
-09:528- 11:39 03-14 A032 ALARM 'P6009' Received Insufficient Bandwidth
-09:529- 11:45 03-14 A001 ALARM Alarm Manually Cleared By '1901'
-09:530- 12:28 03-14 M5095 WRN HW CP [1.1.2]: Timed-Out Waiting For CO Service Information
-09:531- 12:59 03-14 M5095 WRN HW CP [1.1.1]: Timed-Out Waiting For CO Service Information
-09:532- 14:51 03-14 M2039 INF HW CP Dead Socket Response From node: 4 Reason(354): Connection reset by peer
-09:533- 14:53 03-14 M2036 INF HW CP Established IP LINK To node 4
-09:534- 19:02 03-14 M3259 INF EG CP Node 9 Enabled Night Mode
-09:535- 23:00 03-14 M1015 INF DB CP DB Backup Save: Starting Save
-09:536- 23:00 03-14 M1015 INF DB CP DB Backup Save: Successful
-09:537- 00:00 03-15 M2039 INF HW CP Dead Socket Response From node: 6 Reason(304): Broken pipe
-09:538- 00:01 03-15 M2036 INF HW CP Established IP LINK To node 6
-09:539- 00:29 03-15 M3096 INF EG CP Network Time Synchronization By Node 1 Ignored - NTP Synchronization Enabled
-09:540- 09:01 03-15 M3259 INF EG CP Node 9 Enabled Day Mode
-09:541- 17:38 03-15 M5095 WRN HW CP [1.1.1]: Timed-Out Waiting For CO Service Information
-09:542- 17:39 03-15 M5095 WRN HW CP [1.1.1]: Timed-Out Waiting For CO Service Information
-09:543- 19:00 03-15 M3259 INF EG CP Node 9 Enabled Night Mode
-09:544- 19:34 03-15 *** Modem Disconnect - DSP#: 0, Circuit#: 2
-09:545- 23:00 03-15 M1015 INF DB CP DB Backup Save: Starting Save
-09:546- 23:00 03-15 M1015 INF DB CP DB Backup Save: Successful
-09:547- 00:00 03-16 M2039 INF HW CP Dead Socket Response From node: 6 Reason(304): Broken pipe
-09:548- 00:01 03-16 M2036 INF HW CP Established IP LINK To node 6
-09:549- 00:29 03-16 M3096 INF EG CP Network Time Synchronization By Node 1 Ignored - NTP Synchronization Enabled
-09:550- 08:58 03-16 M3259 INF EG CP Node 9 Enabled Day Mode
-09:551- 19:00 03-16 M3259 INF EG CP Node 9 Enabled Night Mode
-09:552- 19:12 03-16 A032 ALARM 'P6009' Received Insufficient Bandwidth
-09:553- 23:00 03-16 M1015 INF DB CP DB Backup Save: Starting Save
-09:554- 23:00 03-16 M1015 INF DB CP DB Backup Save: Successful
-09:555- 00:00 03-17 M2039 INF HW CP Dead Socket Response From node: 6 Reason(304): Broken pipe
-09:556- 00:01 03-17 M2036 INF HW CP Established IP LINK To node 6
-09:557- 00:29 03-17 M3096 INF EG CP Network Time Synchronization By Node 1 Ignored - NTP Synchronization Enabled
-09:558- 08:59 03-17 M3259 INF EG CP Node 9 Enabled Day Mode
-09:559- 09:00 03-17 A000 ALARM Alarm Automatically Cleared
-09:560- 09:37 03-17 M3501 INF EG CP CP ASAI DEV Socket Thread Started From IP Address 10.10.1.160
-09:561- 09:37 03-17 M3500 INF EG CP On-Line From ASAI Device On IP Address 10.10.1.160
-09:562- 10:01 03-17 M3502 INF EG CP CP SMDR Socket Thread Started