Quote:
| Originally Posted by Rachelle Okay, here is another thought. Have you run an Audit Trail on one of the mailboxes that won't page properly? Could you cut and paste a sanitized version so that we can pick it apart for clues?
rlc |
It's only 1 mailbox (so far) that is the problem. I don't know what an "Audit Trail" is, but I ran a session trace when testing the box and got the readout below:
Session Trace
Name: DESK, IS HELP Session Type: Express Messaging
Mailbox: 5xxx Session Start Time: 12/11/03 09:49
Customer Number: 1 Sbox: Session End Time: 12/11/03 09:50
Session Length in seconds: 28
Start of Session
Total Msg: UnPlayed Msgs: Called DN: 4xxx
Calling DN: 4xxx
During Session DN Type: internal extension
New Played: Arrived: Call Origination: Internal
Sent or Left: 1 Composed:
Replied: Forwarded: Last MWI Action: Turned On
Time Delivery sent: External Msgs affect MWI: No
Messages in other Sub-
End of Session Mailboxes affect MWI: No
Total Msg: UnPlayed Msgs:
Message Lengths(Sec) - Minimum: 10 Maximum: 10 Total: 10
I know that the digits I put into the target DN block are being outpulsed. What I can't seem to do is get anything after the phone number to be recognized by the other end. Remote notification worked for this voicemail box when the Skytel service was simply straight to a pager. Since the department that uses the mailbox had the service upgraded a voice menu was added on Skytel's end and that's where the problems began.
I think that the big issue here may be that the Skytel end is expecting "#" to register a dialing termination. But, our MerMail won't accept a "#" in the Target DN block. It IS programmed as a Pager Data Terminator in Outcalling Administration, but I can't enter it into the Target DN.
And maybe I'm chasing the wrong thing, I don't know.
