Trying to Solve Meridian Mail Mystery 2

[jakatz]

Here goes . . .

Recently deployed a set with a DN that has not been assigned in a while. Had no problem creating the set and defining a voicemail box for the DN - the user has even recorded her greetings appropriately and FDN and HUNT are defined to point to the voicemail system (as it is on other sets) - here is the problem:

This DN was out of service for a while, but at one time or another a "Announcement Only" message was assigned to the DN - thus whenever anyone were to dial into this DN, they would hear this greeting / announcement that the user's DN has changed (and if they hung on long enough, they would be transferred to the attendant). Now, although the VM this DN has been assigned, and recorded, anyone that dials this DN (internal or external), is getting the "This users number has changed to . . . " annonucement.

We can't seem to find where this recording is or for that matter why we can't get it to point to the correct mailbox. If anyone wants a look at the TN and how it is defined, I can post it here, but I beleive it is defined correctly. Any ideas . . . anyone??

 

[Nortellian]

from mails main page
option 3 than 4.
than option 1
do a find
enter your dn in the block
view modify


now write down the announcement number
go back to the menu where you chose 1 but chose 3 announcements.
do a find and enter the number you wrote down.

these are the two pieces that point to the announcement.
Delete both pieces the vsdn and the announcement. or if you just deleted the first piece the vsdn it will no longer point to the announcement. But of course the announcement should be deleted also.

 

[joebacon]

Try tracking your internal call, or maybe check to see if an IDC table entry is re-directing it.

 

[johnpoole]

note to joebacon..idc works on external calls only. after you build an idc you apply it to a route, the table changes the dialed dn when it comes from an external source on just that route. when a call goes to mail, the mm checks the voice service dn table 1st, then for a md..voice service dn is option 3, 4 1.. nortellian nailed it

john poole
bellsouth business
columbia,sc

 

[tech32001]

Nortellian is right. The DN must be in the VSDN table as an announcement service. Get it out of there and delete the announcement also.