Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VM messages appear late

Status
Not open for further replies.

IPAlot

ISP
Sep 24, 2004
231
NZ
Seen this over numerous versions, where VM message may not appear to user for hours\days\weeks and evan months, message has been left by caller, there is no notification via MWI or Phone Manger, and message does not play when accessing mailbox, then mysteriously , some time later this message will pop up from way back, Any known causes of this.

Soopa Doopa Intergalactic IP Office installation mechanic and configuration corruptor from way back.
 
We have seen this with two IPoffices linked with scn, do you have a connection to another ipoffice?
 
I to have seen the same thing from time to time.. In different versions as well.. No clear answer as to why.. I usally just restart VM pro services. If anyone finds out a cause would love to know a fix.
 
hi can you let me know what version of voicemail and what operating software you are using on the server
 
Site with prob at the mo is 2.1.15 VMP on 2000 server SP 4, but I believe this is irrelevant, as this has occurred on various levels of software and OS's.

Soopa Doopa Intergalactic IP Office installation mechanic and configuration corruptor from way back.
 
We had this problem between two sites with scn on, but the routers were blocking UDP packets. The result was a delay on voicemails being delivered into mail boxes. Don't know why or if that is of any help but allowing the UDP packets solved the problem.
 
I believe a colleague of mine has the same problem within a SCN, after changes have been made to any programming that will affect the voice mail, message indication will fail… I will get more info tomoz … try a full restart of the IPO and VM and see how that is..
 
Just to chime in... I have had one, if not two users complain of this same problem on our system as well.
 
Well I am glad I am not the only one, just a shame no one really knows why???

Soopa Doopa Intergalactic IP Office installation mechanic and configuration corruptor from way back.
 
No one got anything more on this

Soopa Doopa Intergalactic IP Office installation mechanic and configuration corruptor from way back.
 
the only time I have seen late VM lamps is for group mailboxes
adding H<groupName> in souce numbers resolves the problem

Are you guys having problems with personal mailboxes or Group Mailboxes?
 
It would always occur with all mailboxes with us and to be honest I thought you would never get a voicemail alert without the source number entry?
 
... depended what release you were on telesonic. Somewhere around 1.4/2.0 all members of the group got an alert regardless of H<group name> entries ~ got fixed in the following release.

In theory, the Voicemail Pro rechecks all MWI lamps during its housekeeping (because Avaya know it sometimes gets its knickers in a twist). This is supposed to take place after any two hour period of idleness (no calls in to VM/no call outs) ~ but unlikely that all these sites busy all day long.

Other cases have been seen where the mailbox folders and files have been set to read-only (ie. it was all backed up to CD during an upgrade or PC move and then reloaded). When files copied back of the CD that have read-only status (depends on the Windows version).

Everything seems fine, messages can be played and deleted, but when new messages are left the status.txt file can't be updated by the server. Causes oddities.
 
Hmm. For what it's worth I too have had this complaint from customers and been unable to narrow down a cause.

Peter
 
When the problem has occured on our system it has been with personal mailboxes...
 
telesonic

if you are using SCN ,make sure your VPN LINE number is set to other than 00 and make sure the remote vm line is to the vpn number.

i.e. vpn site a line 10 local vm and vpn site b line 10 line vm set to 10.

Good luck
 
Thanks Spanning - but as I said we sorted ours - the routers were blocking UDP packets at the time, we opened them up and it seemed to stop it.
I have no idea why - & have never seen it since.
UDP packets are (I believe from what I remember of it) small packets that business routers can commonly block as they are attributed to either PC Gaming and or something that can indicate the network is under attack...
 
UDP is also the foundation of VoIP - so no business router SHOULD be blocking it purely on principle... ;-)

Peter
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top