In the past I would just busy the PLID and then perform the RTS command and would work. However this does not seem to work in release MCD 4.0 , I used to get prompted after doing the busy <PLID> command and have to enter 'force' command. I am not getting prompted any longer although the output does say it was set to man busy. However when I do a locate on the DN it states still in DND even after the RTS command??? This is causing huge issues as the RAD is the first RAD in one of our main queues? I have changed the rad in the Path for now to another rad but would like to get this corrected and avoid this happening in the future.
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 Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
RAD Vmail port stuck in DND
- Thread starter transfr8
- Start date
dryaquaman
Vendor
A busy/RTS doesn't do anything for DND.
You have to use the remote DND Off FAC to remove the DND.
Dry Aquaman
You have to use the remote DND Off FAC to remove the DND.
Dry Aquaman
Yes you need to use remote DND FAC to remove DND.
Additionally, I would recommend you look at you timers for the RAD, especially the expected offhook timer. The ports will put themselves in DND if the timers are exceeded.
**********************************************
What's most important is that you realise ... There is no spoon.
Additionally, I would recommend you look at you timers for the RAD, especially the expected offhook timer. The ports will put themselves in DND if the timers are exceeded.
**********************************************
What's most important is that you realise ... There is no spoon.
- Thread starter
- #4
OK.. Not sure why it went to DND since the timer was set to default high value? I changed it to 15 secs. Since I am not onsite I assume I need to do the FAC from a local set so will need to do a site visit. Unless there is a way to do this remotely?
dryaquaman
Vendor
Lower is not better in this case.
I almost always set the timer to it's max value.
If it's too short it will go into DND.
Dry Aquaman
I almost always set the timer to it's max value.
If it's too short it will go into DND.
Dry Aquaman
- Thread starter
- #6
Was origianlly at 128, I changed to 15 and now have updated to 255. Is there a way I can take the port out of DND without being onsite? I know I could register a set from my location to the remote pbx but was wondering if there was another way?
dryaquaman
Vendor
I usually call and ask the local contact to dial the Off FAC.
Dry Aquaman
Dry Aquaman
The ability to set and remove DND remotely is based on COS options of both the Activating station and the one being acted upon. If you do not currently use these features then I suspect that the options may not be turned on to allow you to do so. This being the case, it is very likely that you will need to modify the COS of the RAD and any station that you will allow to use the FAC.
If you have a console (SC-1000 or 5550IP or other) then you can clear the DND from the console (more than likely anyway) this might be worth investigating first.
**********************************************
What's most important is that you realise ... There is no spoon.
If you have a console (SC-1000 or 5550IP or other) then you can clear the DND from the console (more than likely anyway) this might be worth investigating first.
**********************************************
What's most important is that you realise ... There is no spoon.
If you can find a spare DDI set up a DISA dial in turn off DND and remove DISA number.
The Port will go in to DND state when it cannot answer, What I have found previously is that someone had programmed the RAD port somewhere else in the system and when the call routing tried to forward the call to this RAD device it put it in to DND, Im sure there was an entry in the maint logs that put me on to this at the time.
The Port will go in to DND state when it cannot answer, What I have found previously is that someone had programmed the RAD port somewhere else in the system and when the call routing tried to forward the call to this RAD device it put it in to DND, Im sure there was an entry in the maint logs that put me on to this at the time.
- Status
Similar threads
- Locked
- Question