The voicemail is pretty much isolated from the SIP servers so that's likely not related.
What it sounds like is maybe the message in question is corrupt or doesn't exist. Is this the only time it's happened?
The voicemail is pretty much isolated from the SIP servers so that's likely not related.
What it sounds like is maybe the message in question is corrupt or doesn't exist. Is this the only time it's happened?
I was able to listen to the message from my vpanel, and I left myself a new message that exhibited the same behavior. I'll play around with it a little more and see if it's still happening.
Still not working quite right. As of now, there are no messages in the inbox, so if it needs to be reset in some way, it's a good time to do so.FWIW, my outgoing greeting works just fine. It's just retrieving messages on the phone (listing through vpanel works, also) that is not behaving properly.
I had a ticket in for this and they thought it was because of the pap2. Still not resolved. I'm glad others have the same issue.
I never did put in the ticket, so I suppose I should do so.![]()
I don't see how the user agent (PAP2 vs Grandstream vs Asterisk) would matter to the voicemail system. You press 1 for new messages, it says New Message Number 1, then tells me how many new messages I have (with no further intervention--so it can't be misinterpreting DTMF).
I've tried disabling that voicemail box and re-enabling it with no luck. Perhaps there's some additional 'hard deletion' that can be done on the back end after I disable the mailbox that will reset things? A permissions issue that can be reset? I don't know how to solve the problem--just guessing here.
The ata can actually cause issues so that the call is never routed to voicemail. My dlink was troublesome that way. But thats the only issue Ive ever had.
I Void Warranties.
Bookmarks