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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Clustered 3300 Embedded Voicemail won't answer

Status
Not open for further replies.

EPearson

IS-IT--Management
Jan 29, 2010
56
US
I have just added a new 3300 to 2 system Cluster. The new cluster is using embedded 3300 voicemail. The first 2 controlers are using MAS. When calling the new cluster I can't get the voicemail to answer on the embedded. I can call voicemail directly on the new cluster(hunt access code 6000) However when extension is called it will not go to its own embedded voicemail....call times out and cames back via Campon timer. Any help appreciated
 
Sorry it will go extension to extension but transfering an outside call from existing cluster to new cluster with embedded voicemail will not go. I have checked call rerouting.
 
I wonder if you need to put 6000 in the ARS digits dialed.

Always look out for the next tech. because one day it will be you!
 
Be sure to add the new IP scheme, for the new pbx, to the local networks of thw MAS
 
Sorry it will go extension to extension but transfering an outside call from existing cluster to new cluster with embedded voicemail will not go. I have checked call rerouting.

That indicates a problem with the COS of the IP trunk programming on the new system.

**********************************************
What's most important is that you realise ... There is no spoon.
 
Fixed it. When I built the route I made the mistake and added to the Direct IP Route -(PSTN ACCESS VIA DPNSS). Should have left it blank on that parameter. Not very good information on setting up DIRECT IP ROUTING in E-DOCs
 
sooo it was the COS of the IP trunks?

**********************************************
What's most important is that you realise ... There is no spoon.
 
There isn't normally a need to change the cos of direct ip trunks it uses preconfigured cos 100 I think
 
When I built the ARS Route I made the mistake of selecting Route Type of PSTN Access Via DPNSS...there are 4 options of type of route Emergency, Blank, Non-verifed Account, PSTN Via DPNSS...should have been BLANK
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top