| I think that when the retry limit is reached, that it disables the RN and that's the system message that you get. It assumes the number is invailid because there was no successful login to retrieve the message. Here is a quote from the book:
"""
Retry Limit Before RN Stopped
Remote notification capability is disabled whenever the retry limit is reached before the mailbox owner logs on to the mailbox and retrieves messages.
The following is considered one retry repeat:
The system attempts to notify a mailbox owner, but the calls are not answered.
The system stops trying to notify when the No answer limit has been reached.
If another new message is left for the mailbox owner and retry attempts are again exhausted, this is counted as the second retry repeat.
This process continues until the maximum number of retry repeats is reached, at which time the system stops notifying the user of new messages.
Remote notification is re-enabled when the user logs on to the mailbox.
"""
I don't know why it works sometimes and not others....are there any after hours dialing restrictions that would prevent proper outbound dialing?
Other poss are:
1. are there the proper number of pauses to wait for the paging company to accept digits? If callpilot thinks that there is dead-air, it's going to pause for the "Answered" limit. If another message comes in during the wait interval, it will try again, and possibly count it as another failure until the RN retry limit is reached. |