atcomsystems.ca/forum Forums Other TDM Phone Systems Iwatsu Telephones & Systems ~!Transition from call coverage keys to auto attendant

hello adix / iwatsu Gurus
currently we have a (PRI) line ringing to an extension in the suite(s) and the other extensions have the call coverage immediately keys
class 25
DNIS incoming number (the published telephone number)
DNIS conversion number (the extension number)
then we place the call coverage immediate key for that extension on the other extensions in the suite

On the extension that is in the DNIS table we have a medical answering service telephone number in the station speed dial bin. At the end of the business day we do an all call forward at that speed dial tn#. The next morning we take it off call forwarding.

We have been asked to transition to an auto attendant during the day. So if I pointed DNIS to
DNIS incoming number (the published telephone number)
DNIS conversion number *
DNIS mbox/nsc/acd priority 0910 (voicemail menu)

Then the auto attendant will work just fine but I have no way to forward that telephone number to the answering service at nights
adix sw ver 7.31 with an IX 4vml
looking for ideas ....
thanks

Use the access code for the voicemail hunt group as the DNIS conversion number, but don't specify a mailbox. Allow the voicemail system to control the call at point of answer, then create a night menu that will forward the call wherever you want it to go. You may have to use Dynamic trunk routing, and a little external networking, but what you want to do is achievable.

You'll have more options if you have a spare analog trunk port to play with. The ADIX is flexible in ways that defy imagination....

What if you leave the DNIS programmed the original way.... then you could internal forward to the AA during the day and then external forwarding at night? That would also leave you the option of answering calls if you ever wanted to again - just cancel all forwarding.

Another option is to use the day/night DNIS routing. Day mode - have the number ring to the menu. Night Mode - Have the number routed to the answering service by using networking tables.

Third option - wait for JBean to offer an even easier solution!

See? He's so fast, his reply posted before mine!

Thanks for the good ideas. Let me explain the situation a little further. All of the sites we are doing this transition and have multiple suites. This is just the first Suite. Unfortunately each suite has to forward their phone at different times of the day. So the day/night is not an option yet. Also allowing the voicemail system to control probably won't be ideal , unless there is a way to point to a separate voicemail menu dependent on the number dialed. ie:
suite A published telephone number xxx-5758 to menu "A" (0922)
suite B published telephone number xxx-5759 to menu "b" (0923)
suite D published telephone number xxx-5760 to menu "d" (0924)
and so on…

I do have many spare analog trunk ports left over from when we converted to the PRI

Thanks again (while I continue to read the manual).

I assume you have each suites DID number sent to a separate extension. (xxx-5758 to Ext201 xxx-5759 to Ext202 etc) And from there you assigned the CCI keys to the appropriate extensions for answering.

What if you used a DND/Quickforward key on those suite extensions, to send the DID call directly to the correct VM/Menu? You could then use the traditional external forwarding when needed. (Just like you have been doing) When you cancel the external forwarding, just activate the DND/Quickforward again and all calls would ring directly to VM.

Try this perhaps:

Set each incoming number DNIS destination as an unused analog trunk access number. This will make the incoming DNIS call ring as if it was actually an analog trunk. Program that trunk to DIL to the voice mail system during office hours, to a remote forwarded extension when in night mode. You'll have to do some programming in the voice mail for Dynamic Trunk Routing to ensure that calls go to the proper menu. Base your programming on the trunk number of the analog port you are using as a template. Do this for the other suites.

Assign each of your 'analog' trunks a group number in Class 11.38., designate a phone in each suite as an attendant, then put a Group Night button on that phone.Each suite can then forward their calls whenver they want with out bothering the other suites by setting their 'trunk group' to night mode.

Clear as mud?

that does make sense - trunk group idea - I am too busy to get on it until next week but will post if successful

thanks

no - what we have is a single "published" tn that is the only incoming number for the entire suite
dnis xxx-5758 points to ext 3352
then all the other ext in that suite have the cci key for x3352
x 3352 is the one we forward at night