So here is the scoop. I built a call director menu tree on nupoint.
Menu -> option 1 & option 2
Each option gets redirected to their respective RAD built on the 3300. All works well. External callers calling in select option 1 or 2 and are placed in queue w/ message then MOH. Flawless right.
Here's where it gets odd. As I stated, outside callers, it works flawless BUT in the off chance an internal caller calls into the main number through an XNET or PSTN (IE: 9-555-5555) from a IP set within the cluster (say a client or staff member trying to set an appointment) and go into the queue in any placing other than the first caller, the message plays and the MOH starts . . . Then it reroutes to voicemail and prompts them for a mailbox. Again, only the 2nd + caller. If they happen to be first in the queue, no problems.
Granted, the chances of it being a call coming from within is very remote. 99.9 % of the calls come from the public but there has been a rare occation that a staff member has called to book an appoint.
My initial thought is it is in part due to the COS of the sets and the fact that (although we use nupoint for VM) we still need a few embedded vm ports configured on the 3300. 2 set as RAD and 2 set as VM.
Any ideas how to stop it from rerouting on internal calls whilst keeping the RADs functioning as well as the ip sets inhouse?