We are in the process of programming a TDA200 with TVA200 VM. They are going to have a PRI with about 50 DID numbers.

Here are the two things I need to be able to accomplish.

1. A DID number will ring an ICD group and if unanswered go to a specific user VM box. For example: DID number 555-5555 rings ICD group 2000 and then goes to MB 6000 which is the mailbox for the receptionist. I can not figure out how to do this.

2. They want an ICD group that they can transfer callers to when the caller does not know who they need to speak to. They want buttons programmed at all the phones for this specific ICD group. Some phones will have two buttons programmed and some will have 5 buttons programmed. They want the callers to ring at all the phones but only based upon the number of buttons they have at that phone. So x6000 has three buttons programmed for this ICD group. They want x6000 to ring on all three buttons but if a fourth caller is transfered to the group they do not want it to ring at that phone because they are all out of buttons for that group. Any way to do this? I have it working except when all the button are used up it still rings once at the phone and flashes the intercom key. I would like for the phone to stay silent and not ring at all once all buttons for that specific group are full.

For No.1 the easist way to do this is to setup mailbox 2000 and set over flow no answer to voicemail and put message waiting for mailbox 2000 on reception phone, this will also let the receptionist know the message is from 555-5555.

For No. 2 I don't see how you can stop the calls from ringing on intercom button, you could change the number of calls allowed to queue to max number of buttons i.e 3 group keys but if one phone only has 2 buttions the third will ring on intercom, plus this will cause the group to be busy or go to overflow if limit of calls allowed to queue is reached. May be some one else has the answer to that one.

Thanks for the ideas.

#1: I was hoping to make the DID go to the same mailbox as the extension number. That way they do not have to check two mailboxes. This setup would be done for about 10 different DID numbers. I don't know if they want to check multiple mailboxes for all the DID's. The only way I found to do this was by using the message move feature of the VM. That way they could record a mailbox greeting and then have the VM move the message to the VM Box for that extension. It works except the quickest it will do this is 5 minutes. It won't do it immedietly. I am not sure that will fly. Is there any other ideas?

#2: I think they will have to live with the way that it works. They can ignore the call that shows up on the intercom button. I do not think it will be that big of a problem.

#1- When assigning 5555 under DID tables, give it a unique VM Trunk Group number, for example VM TRK GRP # 2.

Then in the TVA, in PORT/TRUNK Service, assign trunk 2 a unique service group number, for example #2. Still under PORT/TRUNK Service, assign a unique custom service to that service group for DAY/NGHT/LUNCH/BREAK mode, for example custom service # 2.

Then under Service Settings, Custom Service, create custom service #2 as a DAY CONTROL custom service, and assign all days to transfer to MBOX 6000.

This should make all callS to ICD group 2000 overflow to the recept's MBOX 6000.

#2- I don't see a fix to that.

They would not have to keep checking them as a light will be on if there was messages,and all they have to do is press it to get messages.
If the customer has different did numbers they might want different outgoing message i.e. thank you for calling sales / service.

95astro, I think your idea will only work if the did is sent direct to vm200 as auto attendant. any overflow from icd group will go in to voice mail box of 2000, but on the same lines you could do personal AA in the mailbox 2000 with 3 to try again back to group 2000 or "0" to leave a message and option 4 is sent to mailbox 6000.

If Toby follows every step to answer #1 it will work. When someone calls DID 555-5555, it will ring ICD group 2000. Then following all of these programming steps, ICD group 2000 will overflow to MBOX 6000. It's alot of steps but this is how it will work.

Also I don't like the way Panasonic's Message Waiting buttons work. If they are lit red you have to press intercom (or pick up handset/press speakerphone) then press button. And if you only have old messages you cannot check the old messages by pressing that button, you have to log into that mbox thru 998. You can only access that mbox thru the button if there are new messages.

Although it is nice to know you have a message from DID 5555 with a button.

I will let you know what happens. I have programmed the system as 94astro instructed. I can not really test it until the PRI is brought up on Friday. I did have one question. Do I set the overflow no answer in the ICD group to 500 (the VM floating extension number)? Just want to make sure.

hi 94astro, I must try that one myself, I have convinced customers to go with message lamps for groups because getting icd groups into other mailboxs were a pain, but that one doesn't seem to hard to setup.

Toby you do overflow the ICD Group to 500.

Yeah OBT, the day control custom services are nice. It's the best way that I know of to get group calls to go straight to someone's mailbox.

94astro,one question, does the icd group voice mail box have to be deleted for it to work?.

I don't think it has to be deleted, because now you are telling that ICD Group to go directly to the desired user's mailbox so it should never go to the ICD Mailbox. But I don't think it would hurt to delete it.

If you are setting up this scenario from scratch like Toby is, you wouldn't create it in the first place though.

I tested this setup yesterday once the PRI was working. It did not work. I am still going to the auto attendant greeting that is setup for custom service menu #1. I did not have any time to troubleshoot the problem to make sure I did everything correctly. I will do that on Monday. Is there any small details I need to know when setting up the VM trunk's in either the VM or PBX? Anything that could stop this from working correctly?

I'm assuming that custom service #1 is the main greeting for the company.

If you did not change the VM Trunk Group number for your DID (5555) in the TDA 200's DID Tables then by default it is in VM Trunk Group 1, which will most likely end up in custom service 1.

What custom service are you setting up as DAY CONTROL for DID 5555 to end up in?

Also, are you sure the DID's are set up right? Is 5555 ringing your desired ICD group?

Here is the setup:

All DID's ring VM trunk group #1. These will go to specific phones and then to the corrosponding VM box or to the main greeting which is CS Menu #1. CS Menu's 2, 3 and 4 are night, lunch and break.

The DID which rings an ICD group is in VM trunk group #2 and the Day control CS Menu is 5. The Day Control CS Menu is set to transfer to the mailbox we want the ICD Group to go to. The DID does ring the ICD group correctly it just ends up at the CS Menu #1 greeting. The only thing I still have not checked to confirm is the VM setup. I thought I had the VM Trunks setup correctly to go to the Day Control CS #5 but I have to confirm that. Is there any thing special about setting up VM trunks in the VM programming that I could be missing?

Let me know if you need any more details.

So if the DID is in VM Trunk Group 2, you have to make sure you set up trunk 2 in the TVA voicemail.


In Port/Trunk settings in the vmail, you have to point trunk 2 to a unique service group, and point that service group to custom service 5.

By default trunks 1-64 in the VM all go to service group 1 which I'm sure goes to custom service 1.

I got it working today. Thanks for the help. I ad to call tech support and there was one thing that I missed that stopped it from working.

Under Group, VM(DPT) Group, System Settings, you have to make sure Intercept to Mailbox is DISABLED. As soon as I changed this it worked perfectly.

Thanks again for the help.

I don't recall changing that setting, but if you got it working that's great...

So OBT, I guess that's one more step necessary to make this work...