Monitoring Calls/Auto Callback

[ericwilborn]

Due to various issues with our phone system, I've been having to monitor calls via the IP Office System Status via browser. (Is there a better way to be doing this?)

Let's say ext220 dials ext204, talks for a few, then they both hang up. Occasionally ext220's phone will ring afterwards, showing that it's from ext204. Picking up that call proceeds to call ext204. In the Active Calls section of the System Status monitor, I see that this comes up as a category of "Auto Callback"... why is this happening, and more importantly, how can I stop it? It's fairly intermittent.

 

[Telecomboy]

In Manager, Under System, check the Telephony Tab. There is a spot on the right side of features called "auto hold". Uncheck that feature and save the config. What that does is automatically put a call on hold if you switch from one line appearance to another. This sounds like what is happening. The held call then times out and calls the extension that put it on hold.

 

[intrigrant]

Important to know is the type of phones you are using. The "auto hold" feature only works for multiline extensions with call appearance buttons.


If it ain't dutch it ain't much

 

[ericwilborn]

We have a combination of 9620 and 9640 phones with an IP 500 V2.

 

[Telecomboy]

I stick by taking auto hold off

 

[intrigrant]

I think the users do something wrong.....

If it ain't dutch it ain't much

 

[ericwilborn]

I also think my users do something wrong, especially since it's mainly one or two users that have this happen. The same one or two users that always seem to have issues with many things..

 

[ericwilborn]

I've disabled the "Auto Hold" feature in System > Telephony but I now have three users that experience this on occasion. What else should I be looking for?

Thanks in advance, per usual. This one has me puzzled.

 

[amriddle01]

I have seen this and they are not doing anything wrong I don't think, it happened to me just yesterday on my in house system a couple of times, seems to be an early R8 bug, at least that's what I am using, in my case it's a 9508 calling 1600/1400's but the exact same issue

 

[ericwilborn]

Good to hear that this isn't just an issue for me. I'm on 7.0(31). (If that is indeed the correct version to which you're referring.)