sundance-communications.com/forum Forums TDM Business Telephone Systems Mitel Telephones & Systems Express Messenger

Have a 4 port Express Messenger with port 4 as a RAD for overflow. When I call the port ext number or huntgrp number it says "busy". The bay PSU is not getting the red ringing LED so I switched PSU no change, I then switched the BCC III and no change. All the other ports work fine on the Express Messenger. I made port 3 a RAD and it works fine from the huntgrp and ext. I tried to delete the ext on port 4 but it says it is in use so I took the EM card out and then deleted it. When I put the card back in and it came up then now port 3 is forwarding to the VM and not answering with the RAD greeting. I don't know what is going on. Any help would be appreciated.

Thanks

Look at the RAD port thru maintenance, and see if it's in DND. The red 'ringing' LED only flashes if a single line phone is being called, and/or there's a MW activated in that bay. In a normal condition, the light SHOULD NOT be flashing. If ANY ports are working in the bay, the BCC is more than likely OK.

I went to the console and called the new RAD port and it says it is in DND. I tried to remove the DND and it will not allow me to. If I go and try to deleter the RAD ext. it says it is in use and cannot be deleted. So I took port 4 which I recently deleted made it a RAD, set it up and it works fine, It was the port that was nor working previously. It seems that if you remove the card or remove power from the shelf it automatically puts the RAD port in DND. It did it twice today!!I'm missing something.

Thanks for the help!

A couple of things to remember when programming rad ports on the sx200. Ensure that form 17 is programmed as a rad hunt group, under the sub menu options ensure the message length timer is programmed 2-3 seconds longer then the message length. In the cos of the rad port I recommend programming the recording failure hangup timer cos option 403 to 10 seconds longer then the actual message length. This will put the rad port on hook should it get into a state where it remains off hook.

Once you get it squared away you might want to take DND out of the VM COS. It's putting those ports in DND so people will not get RNA.

Not a 100% sure but I don't think they include cos option 220 (dnd) in the vmail default cos in the sx200icp. Vmail ports are easy to emulate for trouble shooting, put the port (ons or dnic) in a separate rad hunt group then call the port and when it rings come off hook for the prescribed time and then go on hook, if you keep it off hook it should go in dnd status regardless.

Thanks I will try all of these things. The VM and RAD COS has no DND allowed. That is why I can't understand why the card is putting the RAD port in DND when you remove the card. I have tried everything and the only thig to do is delete the port and reprogram it. This EM has ben workig great for about six months.

I'll keep you posted.

Thanks again

If the system tries to access a rad, and it's not available, it will automatically be put into DND, whether or not the COS is enabled. In the COS of your Rad port, make sure option #404 is a little longer than the actual greeting. T remove the DND on a RAD, log into Maintenance, Diagnostics, 'clear feature, 'DND', etc.

I've made all the changes you guys have recommended the only one I am confused on is making the Hungrp a RAD group. I see an option under type named RABTOS is this it?
Thanks fifty5footer for the tip on taking the DND off.

Thanks

When I changed my additional RAD port back to a regular VM port it RNA and then fowards to the first ext number in the huntgrp. What am I doing wrong? Do I need to reset the EM?