All,
If you have hung out here awhile... You know by now that I have a good handle on the TSAPI API's into the Avaya PBX cm3.x.
We have a situation where we init our program to monitor X stations when our app starts. This is how we track telephone behaviors.
In this one case... I have a handful of users (about four) that are constantly losing their device monitors.
From what I have heard from other techs, these are problem users that will try to break stuff on purpose so they don't have to work... But for the life of me, I can't figure out how they are destroying and/or losing their device monitors on their phones.
I have tried placing a monitor on my deskphone and I have left it off hook for an hour, unplugged the whole tdm line from the wall... Everything. In my tests, the monitor is still there.
We have a total of 400+ monitors on various phones throughout the corporation and everyone else is fine. And this is a combination of monitors on TDM and VOIP phones... No issues.
So... My questions for the group are....
1) Once a monitor is placed on a device by calling API cstaMonitorDevice(). What can destroy that monitor besides a cstaMonitorStop() and/or a loss of that stream.
2) Why is this occuring to only the same users? Is there a way that a TDM phone can destroy their own monitor?
3) Is there a way to do anything with a device from CMS that could result in a monitor being destroyed on a phone?
4) Are there any hardware resets with the telephone device that could possibly trigger a monitor loss from the PBX?
In closing...
I hate to bug the group with something that sounds so trivial... But I have tried everything I know and I just can't duplicate this problem.
Any ideas or comments will help.
Thanks,
--Zowwie
If you have hung out here awhile... You know by now that I have a good handle on the TSAPI API's into the Avaya PBX cm3.x.
We have a situation where we init our program to monitor X stations when our app starts. This is how we track telephone behaviors.
In this one case... I have a handful of users (about four) that are constantly losing their device monitors.
From what I have heard from other techs, these are problem users that will try to break stuff on purpose so they don't have to work... But for the life of me, I can't figure out how they are destroying and/or losing their device monitors on their phones.
I have tried placing a monitor on my deskphone and I have left it off hook for an hour, unplugged the whole tdm line from the wall... Everything. In my tests, the monitor is still there.
We have a total of 400+ monitors on various phones throughout the corporation and everyone else is fine. And this is a combination of monitors on TDM and VOIP phones... No issues.
So... My questions for the group are....
1) Once a monitor is placed on a device by calling API cstaMonitorDevice(). What can destroy that monitor besides a cstaMonitorStop() and/or a loss of that stream.
2) Why is this occuring to only the same users? Is there a way that a TDM phone can destroy their own monitor?
3) Is there a way to do anything with a device from CMS that could result in a monitor being destroyed on a phone?
4) Are there any hardware resets with the telephone device that could possibly trigger a monitor loss from the PBX?
In closing...
I hate to bug the group with something that sounds so trivial... But I have tried everything I know and I just can't duplicate this problem.
Any ideas or comments will help.
Thanks,
--Zowwie