boudinov
Programmer
- Feb 11, 2008
- 1
Hello guys,
I would love to receive opinion from anyone with experience regarding IP Office's CTI software: TAPI and DEVLINK. We have a project requiring agent and group realtime monitoring. Using latest Tapi 2 package in 3rd party mode, we successfuly implemented call and agent activity monitoring, but there are several major issues regarding Tapi:
1. Big problem is that Tapi call-related event data is incomplete. In certain cases, you cant tell by the event data provided, whether call is internal or external, inbound or outbound, whether it is transferred from another extension or no, and whether it is part of a conference.
2. Everytime a new agent or group extension is added in IPO configuration using Configuration Manager, the computer hosting Tapi needs to be restarted, so Tapi can initialize its new Lines. Is there a workaround to this?
3. You can never tell which groups an agent is part of, only their count. This a real limitation and there seems no workaround it?
4. Major problem, Tapi software bug in our opinion. After working several days, Tapi software begins to receive call related events on the wrong Tapi lines. It seems Tapi Lines get shifted one step up or down. For example, there is call event for Tapi line of Group Extension 8000, but the event arrives on Tapi line 7999 or 8001. This happens for all events for all Tapi lines. When Tapi service is restarted, it gets back to normal. Anyone seen this thing?
Because of all this, we are planning on using DEVLINK software for more accurate call information. Would you recommend such approach, and if yes, we need to know if this software is still actively supported and updated for new versions of IP office and firmwares.
Thanks in advance!
I would love to receive opinion from anyone with experience regarding IP Office's CTI software: TAPI and DEVLINK. We have a project requiring agent and group realtime monitoring. Using latest Tapi 2 package in 3rd party mode, we successfuly implemented call and agent activity monitoring, but there are several major issues regarding Tapi:
1. Big problem is that Tapi call-related event data is incomplete. In certain cases, you cant tell by the event data provided, whether call is internal or external, inbound or outbound, whether it is transferred from another extension or no, and whether it is part of a conference.
2. Everytime a new agent or group extension is added in IPO configuration using Configuration Manager, the computer hosting Tapi needs to be restarted, so Tapi can initialize its new Lines. Is there a workaround to this?
3. You can never tell which groups an agent is part of, only their count. This a real limitation and there seems no workaround it?
4. Major problem, Tapi software bug in our opinion. After working several days, Tapi software begins to receive call related events on the wrong Tapi lines. It seems Tapi Lines get shifted one step up or down. For example, there is call event for Tapi line of Group Extension 8000, but the event arrives on Tapi line 7999 or 8001. This happens for all events for all Tapi lines. When Tapi service is restarted, it gets back to normal. Anyone seen this thing?
Because of all this, we are planning on using DEVLINK software for more accurate call information. Would you recommend such approach, and if yes, we need to know if this software is still actively supported and updated for new versions of IP office and firmwares.
Thanks in advance!