| some more information on whats happening. Today i've experienced 2 additional failures, and call volume has been low. I did notice similar elements from the incident on friday.
in all 3 cases (friday, and 2 times today) a call came in via DID to a user who was already on the phone. each time this happens, the protocol trace shows a call coming it to whatever DID the inbound caller dialed, it shows essentially 2 entries with the same crn# (see previous post for example) and then there's no indication of the call being released.
We have our extensions setup to FWD B/NA to voicemail from both CO and from EXT. When this happens, I will notice the corresponding Single-CO button for that line on the call director's phone will be lit up as if the line was in use. When i hit the button, it says "line busy" and gives the option to do a call back. Could this have something to do with call waiting??? I just can't understand why when i go to duplicate the problem and call my DID from my cell while my DID is busy, it transfers to VM as it should, and never results in the error. There must be some other element that remains to be seen.
Maybe this is a bug in the system's firmware? we are currently using Version 004-001 with console Version 1.06h |