Genesys CTI User Forum
Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: Ghost on July 08, 2011, 03:24:45 PM
-
Hi,
I'm a CC Pulse newbie, I'm looking to create a template with a column where we can monitor if an agent is releasing calls, can anyone advise on how to do this? Cheers
-
What version of TServer and what kind of switch you have ? Only selected switches and TServer 8.0+ can provide necessary information to create that kind of statistics.
-
We are on Avaya switch and have Ver 7.5 T server
-
As said by borkokrz you need TServer 8 and create some stats to do this
-
You need at least TServer Release Number 8.0.101.05
New in This Release
* T-Server now supports the call release tracking feature, which provides information about which party initiated the release of a call. This feature can be valuable for different applications to provide historical and real-time call reporting. The following restrictions/limitations apply to this feature:
Call release tracking can be configured using the configuration option releasing-party-report option. This configuration option enables/disables the reporting in the AttributeExtensions of the extension key ReleasingParty in EventReleased and EventAbandoned events, and also enables/disables AttributeCtrlParty reporting in EventCallPartyDeleted and EventCallDeleted events.
Note: A client must subscribe for call-monitoring events by issuing RequestStartCallMonitoring in order to receive EventCallPartyDeleted and EventCallDeleted messages.
releasing-party-report
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately
This configuration option specifies whether T-Server reports the ReleasingParty key in the AttributeExtensions of EventReleased and EventAbandoned events to indicate which party initiated the call release. Additionally, this option specifies whether T-Server reports AttributeCtrlParty in the EventCallPartyDeleted and EventCallDeleted events to indicate which party initiated the call release (when call monitoring is enabled in T-Server). This option can be configured only in the TServer section of the T-Server Application object. If this configuration option is set to true, the value assigned to AttributeCtrlParty will contain the DN of the party that initiated the release, and the ReleasingParty key will contain one of the following values:
* 1 Local-the call is released because AttributeThisDN in EventReleased requested a release operation.
* 2 Remote-the call is released because the other party (which is remote to AttributeThisDN) in EventReleased or EventAbandoned requested a release operation.
* 3 Unknown-the call is released, but T-Server cannot determine the release initiator.
-
Thanks for you help with this borkokrz, we won't be upgrading to Ver 8.+ just yet but good to know for the future.
-
Hello guys, don't wont to start a new thread, so asking here. Is there any way to add additional releasing party. In our case we have call charger, which third party application (tomcat web app) connected to SIP server via (Tlib) java libs. So is it possible to identify when is call released by charger request ? Except tracking SIP BYE in logs ?
-
If you read the whole post will see it is possible but need to grab your TServer Event.
StatServer RN has more details on it
Enviado de meu E6633 usando o Tapatalk
-
[quote author=deadmeat link=topic=6525.msg49933#msg49933 date=1527071650]
Hello guys, don't wont to start a new thread, so asking here. Is there any way to add additional releasing party. In our case we have call charger, which third party application (tomcat web app) connected to SIP server via (Tlib) java libs. So is it possible to identify when is call released by charger request ? Except tracking SIP BYE in logs ?
[/quote]
I don't think so. The only thing SIP Server reports on its TLib events would be "Remote" (in your case, could be the Charger or the Customer) or "Local" (the agent, strategy, or IVR).