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

Auto Attendant on Embedded Voice mail intercept

Status
Not open for further replies.

ExCentigram

IS-IT--Management
Jul 26, 2011
37
US
This is my first foray into embedded VM. Normally I'm a nupoint person. I wanted to route any "intercepted" non-working DID #'s to a recording that says "non working number blah blah"
I created ext 2099 as single line, put it on my phone on a key.
Call reroute always to 2000 which is the pilot # to embedded VM.

Important question:
Changed intercept 1 to go to DN 2099 instead of reorder tone, and when I call a DID taht doesn't have an associated DN I get the generic auto attendant greeting. Why is that? If I change the field in intercept backto reorder, I get fast busy so I know I'm changing the right field.

Side question:
If I call 2099 from my phone it rings 4 times and goes to the recording i put on there for non-working #. Why it rings 4 times instead of re-routing immediately I have no idea, I've checked the reroute form twice and its got the reroute # all the way across....

2099 is a mailbox in embedded. I changed it to every type and it behaves the same way every time.

Please help...
MCD 4.1
 
Segment your voicemail and dedicate a port or ports to this purpose.

Make sure you leave the last port of the voicemail in the original group for MWI.

Create a separate hunt group for the vm ports. I would set them up as RAD ports but you can leave them as standard ports if you like. Either way, make sure they use a separate greeting.

Create speedcalls to match all of your non-active DID's and direct them to the new hunt group

VOILA!

**********************************************
What's most important is that you realise ... There is no spoon.
 
Extending on kwbMitel's post, could you not change the intercept field to go directly to the RAD greeting rather than a single line that is routing to VM. Depending on the amount of non-working DID's there could be a few Speedcalls to program.
 
There are about 1000 non-working DID's
I do not want to add them one at a time to the sys speed call list.

We use embedded VM now, so are you saying if I have 8 vm ports now in the group, then take out, say port 7 and make that a RAD?
so x2001-2006,2008 are in hunt group 1 and 2007 is in hunt group 2, which will be for the intercepted DID's?

Do I have to import a RAD greeting or can I just record it somehow. I don't want to go through all that horror show of converting it.
 
I still don't understand that if 2099 is a valid mailbox why these intercepted calls don't end up on that greeting. Maybe an intercepted DID doesn't carry through the extension info and it's presented to the VM hunt group as just the 10 digits of the original DID call?
 
8 ports is a strange number of ports.

For a CX type that number should be 16

For an MXe Type that number should be at least 20

For 1000 numbers The intercept route would probably be best (next time provide)

Based on your questions, the simplest route would be to separate out a port or ports and assign the greeting to be Primary greeting #2

Then record the greeting via the admin mailbox.

**********************************************
What's most important is that you realise ... There is no spoon.
 
As for your mailbox issue, the VM system is probably trying to use the mailbox for the DID not 2099. Make 2099 a Nametag Hunt Group and forward that to VM. It should also achieve what you want. Obviously make it an information mailbox so that it doesn't take messages.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top