copy of voicemail to email doesn't send .wav

[phantomiii]

I have an IPO 406v2 (3.2.54), and have setup the IPO and voicemail pro server to send out emails via smtp using the copy option, under the users voicemail tab from Manager. The only thing is, it just sends an alert and not a copy of the .wav attachment voicemail. I know I've seen this working before. Anyone else use the built in voicemail to email function?

 

[aarenot]

What release?

List your set up for user VM tab fields.

list settings for the control panel SMTP application on the VMPRO server, as well as check button results.

list VMPRO client administration, preferences, general, MAPI tab fields info.

That should be a good place to start from, more requests to follow when responses listed.

 

[1043]

Did you set up the smtp error log?? Look in the knowledgebase for details.


IP Office VoiceMail Pro 4.0 - Installation and Maintenance
| Back | Print | Feedback |


SMTP Errors
SMTP error logging can be enabled to generate a log of SMTP activity. For a default Voicemail Pro installation the activity is logged to a file in C:\Program Files\Avaya\IP Office\Voicemail Pro\Logs. The file name includes a date stamp for the day on which it is generated.



Enabling SMTP Error Reporting

Stop the Voicemail Pro service.

Start the Registry Editor.

Locate the key HKEY_LOCAL_MACHINE\SOFTWARE\Network Alchemy\Voicemail\Directories.

From the menu bar select Edit.

Select New and then String Value.

Enter SMTPLogging.

Right-click on the new registry key SMTPLogging and select Modify.

Set the value to 1.

Close the Registry Editor.



SMTP Errors

Value
Meaning

1
An exception has occurred.

3
The process has run out of memory.

4
An error has occurred due to a problem with the message body or attachments.

5
There was a problem initiating the conversation with the mail server. Ensure the setting of the Domain property is correct.

6
There was an error terminating the conversation with the SMTP mail server.

7
The "From" address was not formatted correctly or was rejected by the SMTP mail server. Some SMTP servers will only accept mail from particular addresses or domains. SMTP mail servers may also reject a from address if the server can not successfully do a reverse lookup on the from address.

8
An error was reported in response to recipient address. The SMTP server may refuse to handle mail for unknown recipients.

9
There was an error connecting to the SMTP mail server.

10
There was an error opening the file. If you have specified file attachments, ensure that they exist and that you have access to them.

11
There was an error reading a file. If you have specified file attachments, ensure that they exist and that you have access to them.

15
No mail server specified.

16
There was a problem with the connection and a socket error occurred.

17
Could not resolve host.

18
Connected but server sent back bad response.

19
Could not create thread.

20
Cancelled as a result of calling the Cancel method.

21
The operation timed-out while the host was being resolved.

22
The operation timed-out while connecting.

24
ESMTP Authentication failed.

25
The selected ESMTP Authentication mode is not supported by the server.

26
ESMPT Authentication protocol error.

27
Socket Timeout error.

105
Invalid license key.






| Back | Print | Feedback |

Issue 17a
©Avaya - April 16, 2007
(File: smtp_errors.htm)

Performance figures and data quoted in this document are typical, and must be specifically confirmed in writing by Avaya before they become applicable to any particular order or contract. The company reserves the right to make alterations or amendments to the detailed specifications at its discretion. The publication of information in this document does not imply freedom from patent or other protective rights of Avaya or others.

Intellectual property related to this product (including trademarks) and registered to Lucent Technologies have been transferred or licensed to Avaya.

All trademarks identified by the ® or ™ are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners.