Off Premise Notification to 3 phones

[phoneygirl]

Hi,

I have off premise notification turned on for a mailbox. I have 3 cell phone numbers programmed as notify destinations.

I have 3 channels designated for outdialing.

The notification only comes to one phone, the one I have as destination # 1.

What am I doing wrong?? How can I make it notify all 3 phones?

Thanks.

Elise Levine

 

[Arr]

Elise,
Clarify; are you waiting enough times for the cascade to occurr? It won't do all three simultaneously.

PhM

 

[phoneygirl]

I have waited at least 15 minutes. How long would you expect it to take to call the second phone? I tried not answering the first destination, not answering the first destination, having the first destination be busy...it never calls the second (at least in the 15 minutes I waited).

Thanks.

Elise

 

[aragon]

A standard COS value for a mailbox is 1.
This means that the OPN will try to notify the first outdial 3 times, once every 5 minutes.
Why don't you try to edit an unused COS value for this mailbox and edit the number of retry intervals and times.
Apply the new COS value to this mailbox.

 

[phoneygirl]

Thanks Aragon, that sounds like a great idea, which I will try on Monday.

If it reaches the first outdial successfully, will it ever call the second (and third)? Is it only supposed to call the second if the first is ultimately unsuccessful????

Thanks.

Elise

 

[Arr]

Elise,
It will keep on going until the message in the box is heard saved or cleared. What voice mail version are you working on?

PhM

 

[aragon]

Arr is correct.
The mail will stop notifying once someone collects the message.

 

[DDionne]

Sorry, I believe Arr is incorrect. Notification stops at the last OPN entry after its total number of attemptss.

IE (based on COS):
Notify Destination (NDest) 1 for prog'd number of attempts with prog'd time interval , then NDest 2 for prog'd number of attempts with prog'd time interval, etc., then it stops and leaves a msg in the mailbox indicating that: "The system was unable to reach the number you specified for msg notification."

I have experienced this on CallPilot, NAM 4.0 & Flash VM 1.9/2.0. Not sure about StarTalk or older versions of Nam & Flash.

If someone knows a way to circumvent this and have notification continuing until msg is retrieved, please indicate how. I have a client with this exact scenario and gave them my explanation. They were not pleased by this limitation. Almost asked me to remove the system and reinstall their old one.


DD

 

[aragon]

The message "The system was unable to reach the number you specified for msg notification."
is only delivered by the voicemail to the user if the user does not collect their mail.
This message is intended to notify the user that the system exhausted all retry attempts and that the user did not clear the mailbox.
The user must LISTEN to the message or the system will continue to outdial.
If the scenario described by DDionne was correct even an off premise notification destined to a single outdial would always deliver the "The system was unable to reach the number you specified for msg notification." message even though the message had been collected.

For years I wore an emergency pager and the system cascaded to three outdials. The oncall tech, the service manager, and the company president. If the system did not work as intended the service manager and president would be notified constantly. This was certainly not the case.
Also the pager would have kept me up late at night.

 

[Arr]

Well you are both correct. DD what I meant and I'm sure what aragon understood was that the Mail system would continue to outdial untill it reached the end of it's cascade parameters. My response was particular to Elise's situation where the cascade is apparrantly not working.
DD thought for your situation: while not endless, you may be able to set up the last cascade into another mailbox which would then start external MSG notification all over again etc. On a NAM you have a LOT of Mboxes to set up a very long scenario with. Limitation is that the user couldn't direct connect as he/she would end up in the wrong Mbox.. but still??

Cheers
PhM

 

[DDionne]

I stand corrected. Aragon and Arr, you are both correct. I misunderstood what was explained. If someone LISTENs to the msg, then notification stops. My mistake.

Clarification please: Using my example, if no one listens to the msg, OPN will continue through each cascade until...? The last notification entry and then stop?

I take it then that in Elise's case, she was not waiting long enough for the OPN to begin the next cascade entry? Or am I out-to-lunch?

DD

 

[aragon]

DD if no one listens to the message in the correct mailbox the system will continue to notify until all retry attempts configured in the COS value for that mailbox are exhausted.

I think phoneygirl is trying to simultaneously notify all outdials.
My theory although untested is to change the number of outdial attempts to zero for an unused COS value and assign this COS to the mailbox in question.
If this does not work then change the number of outdials to one and reduce the retry delay to the lowest possible setting.

 

[DDionne]

Thanks Aragon.


DD