atcomsystems.ca/forum Forums TDM Business Telephone Systems Avaya - Lucent Telephones & Systems IP Office 4.0.07

Can someone explain to me the way outcalling is supposed to work on the Intuity mode on the IP Office.

I have a client that wants to cascade the outcalling. I have that setup, but I got a call today, saying when a message was left over the weekend it didn't call out to anyone's phone?

Any thoughts are appreciated. Will the mailbox keep calling out until the call is "answered", or until the VM is retrieved in the IP Office?

Thanks,

Dave

It will call as many times as number of retries you've set up in the schedule for outcalling untill it will be answered. Ownwr of the mailbox has to activate his outcalling to make it work.

For a little more information you might want to check out this link... clicky

4.0's Cascaded Outcalling calls up to 5 numbers one after the other, then calls the group again, according the timing set, as outlined in ipofficeguys link. After the set number of iterations it ends.
An outcalling terminates when a listener enters *#, or listens to the vmail.
The system is controlled entirely through the TUI during regular use.

The system does not "escalate" to another number or set of numbers after the first number or set has been exhausted. It is oriented to tracking down one person via several numbers, not escalating if that person can not get the call.

I tried an installation on 4.0.18 VMPro server that did not work. When I downgraded to 4.0.15 it worked, but so far email notification has not worked with that rev level VMPro.

Does anyone have any experience debugging email notification? I have been able to get the VMPro server machine's Outlook to comm with the in house Exchange server both over SMTP and MAPI, but can not seem to get email messages out of VMPro 4.0.15. I have set the user and system VM/email setups, and it worked with 4.0.18.

If you have access to an Avaya tier 3 Eng in Denver you can request the VM Pro debgview.exe application.
I received my copy from my distributor.

error codes below.

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 mail 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 a 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 a 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 the 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 ESMTP Authentication protocol error.
27 Socket Timeout Error.
105 Invalid license key.