3300 Embedded Voicemail Autoattendant issue

[f1fanatic]

I have set up an autoattendant, by doing this i have set the voicemail ports to play alternate greetings2, and pointed a ddi at my voicemail hunt group.

This works fine but the some strange issues cropped up. This is a site that is clusetered to another, and one of the options on the auto attendant was to reach site b, site a housing the autoattendant. The destination at site b is a multicall on a few 5215's. i can dial the dn of the multicall key fine but when i select it through the autoattendant it says that destination is unavailable, when i switch to assisted transfers it see's the destination as busy. Now on further testing this is true for local and remote DN's. No forwarding enabled on any sets, then again on further tests the operator feature where you can "0" out of a mailbox also does'nt work, same thing as the autoattendant. Upgraded from 6.1 to 8ur3 as part of enterprise/ops man install, but informed this may have been an issue since the original install 3-4 years ago!

Any idea's?

 

[Lundah]

What if you change the destination for the menu option from the DN at site B, to a speedcall at site A which points to the site B DN? Also ensure the DN is in the Remote Directory at site A.

 

[f1fanatic]

Done and done!

 

[f1fanatic]

Sorry hit the wrong key and submitted that last one, as said don both of those and still the same outcome, the voicemail either sees the destination as busy or unavailable, the really strange one is when i use assisted transfers it sess the destination as busy and then puts me into that users mailbox.

 

[nytalkin]

make sure the voicemail ports have ability to access the ip trunks in your cluster both in COS and COR.

NO GOOD DEED GOES UNPUNISHED!

 

[UKMitel]

In the vmail ports COS set public network to network connection allowed.