Unity remote message notification delay not delaying

Unanswered Question
Sep 30th, 2009

Greetings,

We have setup 2 remote message notifications, one on Text Pager 1 and the other on Test Pager 2. The one on Text Pager one is set to send initial notification without delay and repeat every 5 minutes. The notification for Text Pager 2 is set to send initial notification after 20 minutes then repeat every 5 minutes. The issue is that after 5 minutes there is a notification coming from Text Pager 2, it's not waiting for the 20 minute delay. Having not worked on this type of remote message notification I'm wondering if this is the way it's supposed to work or if something isn't working right for us.

Any guidance will be appreciated!

Cheers,

Rob

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Christopher McAlpin Wed, 09/30/2009 - 16:33

Depending on which version of Cisco Unity you are running, you may be running in to the following defect:

Text pager notification doesn't send intial message at correct time

Symptom:

If you have the Send initial notification after how many minutes value set at a greater time then the time you have set in the Repeat notification if there are sitll new messages after this many minutes, the initial Text pager notification is sent using the value in the Repeat notification field and not the Send initial notification field.

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsj49463

robertlwalk Wed, 09/30/2009 - 16:39

Yep, that looks like the issue. We are running Cisco Unity 5.0 Build 5.0(1). It's hard to tell from the bug whether it is an issue in Unity 5, do you know? And if so there is no stated fix until 7. :-(

Thank you for the quick reply.

Rob

Christopher McAlpin Wed, 09/30/2009 - 16:45

Rob, it appears the bug was reported in Cisco Unity 4.1(1) and a fix was provided in 4.1(1) ES57. In addition, the fix was also included in the release of Cisco Unity 7.0(2).

You could upgrade to Cisco Unity 7.0(2) or open a TAC case to see if a fix could be ported back to Cisco Unity 5.0(1) in an ES.

Actions

This Discussion