Message Notification, Cascading

Release Notes (System)

Incomplete Pager Callouts

[3.00.30] Version 3.00.30 corrects a problem in 3.00.29 in which all notification digits were not dialed into the pager service.

Reference: A090511005

Notification Attempts Default Value Changed

[3.00.30] The 4202-06: Number of Callout Attempts default value is changed from 5 to 99. In addition, this option sets the maximum number of notification attempts per entry. For example, if this value is 10, the user entry for Busy Attempts or RNA Attempts cannot be greater than 10.

Reference: None

Pager Notification Doesn't Follow RNA Timer

[3.09] This software version corrects an issue in version 3.05 which caused a pager notification to immediately restart another callout if the pager service didn't answer.

Reference: A090924002

Pager Notification Logic Changed

[3.00.30] A pager notification is considered acknowledged when the subscriber logs onto their mailbox. In prior versions, a pager notification was considered acknowledged when the pager service answered.

If a pager notification is unanswered by the pager service, IntraMail will wait the programmed interval and then retry the service. If still unanswered after the RNA Attempts setting is reached, notification will cascade to the next entry.

Reference: None

Pressing V-MAIL During Pager Notification Could Reset System

[3.09] This software version corrects a potential system reset that could occur if an extension user pressed V-MAIL while the system was processing a digital pager callout for their mailbox.

Reference: A090924001

Retry Count Incremented Twice

[3.05] A problem is corrected that would cause the Ring No Answer retry count to increment twice. If the RNA retry count was set to six, for example, the destination would only be tried three times.

Reference: None