I am running CM 3.1 on a S8720 server.
I have received calls from a department on campus that they are experiencing a problem with their Intercom group.
The problem is thus:
Extension 51234 has ringing bridged appearances of 52222, 53333, and 54444.
If anybody calls these three appearances, 51234 answers.
She then puts the caller on hold and Intercoms back to the appropriate extension and they pick up their own line.
So, when a call comes in on 52222, 51234 answers, puts the call on hold, and intercoms 52222.
Recently, what has been happening is when 51234 intercoms 52222 it rings one time back to 52222 on the Intercom ring and then doesn't ring again. When 52222 goes to answer the Intercom, nothing is there. However 51234 still hears ringing.
The only special coverage/forwarding on 52222 is a cover path to voicemail. It is not manually forwarded at all.
Also, this does not happen every time. Most of the time, when 51234 intercoms 52222, it rings normally.
Any ideas? Has anybody ever experienced a similar problem? All "lab" testing hasn't come up with any repeatable problems like this.
Thank you!
I have received calls from a department on campus that they are experiencing a problem with their Intercom group.
The problem is thus:
Extension 51234 has ringing bridged appearances of 52222, 53333, and 54444.
If anybody calls these three appearances, 51234 answers.
She then puts the caller on hold and Intercoms back to the appropriate extension and they pick up their own line.
So, when a call comes in on 52222, 51234 answers, puts the call on hold, and intercoms 52222.
Recently, what has been happening is when 51234 intercoms 52222 it rings one time back to 52222 on the Intercom ring and then doesn't ring again. When 52222 goes to answer the Intercom, nothing is there. However 51234 still hears ringing.
The only special coverage/forwarding on 52222 is a cover path to voicemail. It is not manually forwarded at all.
Also, this does not happen every time. Most of the time, when 51234 intercoms 52222, it rings normally.
Any ideas? Has anybody ever experienced a similar problem? All "lab" testing hasn't come up with any repeatable problems like this.
Thank you!