TServerBridgeDN

[phil]

Hi folks,

in our environment we use a DN of type 'Chat' called 'TServerBridge'. It's used as communication channel between our custom Agent Desktop. I just know of Action Codes which are submitted via this channel to TServer from where Reporting-StatServer can read it and make different NotReady statusses visible in CCPulse.
The question: Is this a usual setup? Is this DN mandotory generally for TServer use? What else might genrally submitted via this channel, if yes?

Cheers


Phil

[rpenney]

> It's used as communication channel between our custom Agent Desktop.

Between your custom agent desktop and what? 

The DN is just used to pass events around. One TServer client subscribes to events and another publishes events. Using User Events you can pass anything that fits in the events structure (up to about 16Mb by default).

Of course both ends need to know what the structure of the events are.

[phil]

Thanks for the feedback, Rpenney,

[quote author=rpenney link=topic=5560.msg24347#msg24347 date=1274423257]

Between your custom agent desktop and what? 

[/quote]

According to the name, between Agent Desktop and TServer Sorry, missed that.
Is it rly 16 MB?

Cheers

Phil

[rpenney]

No it is not 16Mb, it is 16Kb which is only a letter different but a big change otherwise 

I am not sure what else you could use the channel for. It would depend on the TServer capabilities and how the desktop interacts with it.
What TServer are you using?

It is not mandatory to use that DN, it would be configured/programmed in the agent desktop.
If you want to post a TServer log showing an agent desktop sending the code to the TServer, I might have soem better suggestions

[phil]

It's TServer for Avaya Infinity G3 version 7.6.011.00. Here's a snippet of the TServer Log when i change my state from Unpaid to Coaching, not sure if this might help u making better suggestions:


2010-05-25T15:38:47.526 Trc 04541 RequestAgentNotReady received from [792] (00000020 AIL_tomcat 194.xxx.xxx.xxx:1564)
message RequestAgentNotReady
AttributeAgentWorkMode 1 (ManualIn)
AttributeExtensions [2] 00 00..
AttributeReferenceID 63
AttributeReason [16] 00 01 00 00..
'Coaching' '4'
AttributeThisDN '20333'
@15:38:47.5260 [gctmi] Distributing request RequestAgentNotReady
@15:38:47.5260 [asai] AgentLogin [20333,id93333,sNRDY] (reqAgentNotReady)
TP_AsaiData
REGISTER  CRV:16b8
Facility: INVOKE
InvokeId: 3
Operation: FeatureRequest
Feature: ChangeWorkModes
Domain: (ACD_Split),'00'
Domain: (Extension),'20333'
Domain: (PendingWorkMode),1
@15:38:47.5260 [>>] 08 00 00 28 08 02 16 B8 64 96 1C 20 91 A1 1D 02 01 03 02 01 8F 40 15 96 48 01 81 49 03 81 30 B0 49 06 83 32 30 37 35 B3 49 02 9C 81
@15:38:47.5730 [<<] 08 00 00 1A 08 02 96 B8 5A 96 1C 12 91 A2 0F 02 01 03 30 0A 02 01 8F 40 05 96 49 02 9C 81
TP_AsaiData
RELEASE_COMPLETE  CRV:96b8
Facility: RETURN_RESULT
InvokeId: 3
Operation: FeatureRequest
Domain[1]: (PendingWorkMode),1
@15:38:47.5730 [asai] (processRtrnRsltNotReady)
@15:38:47.5730 [gctmi] request RequestAgentNotReady deactivated in reqMgr
@15:38:47.5730 [gctmi] TMsg [EventAgentNotReady()] distributing to model
@15:38:47.5730 [gctmi] AgentLogin [20333,id93333,sNRDY] distributing EventAgentNotReady
@15:38:47.5730 [gctmi] AgentLogin [20333,id93333,sNRDY] processNotReady
@15:38:47.5730 [gctmi] request RequestAgentNotReady removed from reqMgr
@15:38:47.5730 [0] 7.6.011.00 distribute_response: message EventAgentNotReady
AttributeExtensions [53] 00 01 00 00..
'AgentSessionID' '1B4RL5DK0D05HADJL5DOAS22440000EG'
AttributeEventSequenceNumber 000000000000f8bb
AttributeTimeinuSecs 573000
AttributeTimeinSecs 1274794727 (15:38:47)
AttributeThisDN '20333'
AttributeThisQueue '94000'
AttributeAgentWorkMode 4 (AuxWork)
AttributeAgentID '93333'
AttributeReason [16] 00 01 00 00..
'Coaching' '4'
AttributeReferenceID 63
@15:38:47.5730 [ISCC] Translate: '' -> ''; result 1 ()
2010-05-25T15:38:47.573 Trc 04542 EventAgentNotReady sent to [792] (00000020 AIL_tomcat 194.xxx.xxx.xxx:1564)
2010-05-25T15:38:47.573 Trc 04542 EventAgentNotReady sent to [764] (0000001e ICON_Inbound_1 194.xxx.xxx.xxx:1199)
2010-05-25T15:38:47.573 Trc 04542 EventAgentNotReady sent to [748] (0000001d ICON_Inbound_2 194.xxx.xxx.xxx:1761)
2010-05-25T15:38:47.573 Trc 04542 EventAgentNotReady sent to [688] (00000018 StatServer_CCPulse 194.xxx.xxx.xxx:1528)
2010-05-25T15:38:47.573 Trc 04542 EventAgentNotReady sent to [604] (00000011 StatServer_InfoMart_HA 194.xxx.xxx.xxx:1708)
2010-05-25T15:38:47.573 Trc 04542 EventAgentNotReady sent to [592] (00000010 StatServer_URS 194.xxx.xxx.xxx:1190)
2010-05-25T15:38:47.573 Trc 04542 EventAgentNotReady sent to [568] (0000000e StatServer_URS_HA 194.xxx.xxx.xxx:1706)
2010-05-25T15:38:47.573 Trc 04542 EventAgentNotReady sent to [556] (0000000d StatServer_AIL_HA 194.xxx.xxx.xxx:1705)
2010-05-25T15:38:47.573 Trc 04542 EventAgentNotReady sent to [544] (0000000c StatServer_URS_HA 194.xxx.xxx.xxx:1704)
2010-05-25T15:38:47.573 Trc 04542 EventAgentNotReady sent to [532] (0000000b StatServer_InfoMart 194.xxx.xxx.xxx:1187)
2010-05-25T15:38:47.573 Trc 04542 EventAgentNotReady sent to [520] (0000000a StatServer_AIL 194.xxx.xxx.xxx:1186)
2010-05-25T15:38:47.573 Trc 04542 EventAgentNotReady sent to [508] (00000009 StatServer_InfoMart_HA 194.xxx.xxx.xxx:1702)
2010-05-25T15:38:47.573 Trc 04542 EventAgentNotReady sent to [496] (00000008 StatServer_InfoMart 194.xxx.xxx.xxx:1185)
2010-05-25T15:38:47.573 Trc 04542 EventAgentNotReady sent to [484] (00000007 StatServer_CCPulse_HA 194.xxx.xxx.xxx:1701)
2010-05-25T15:38:47.573 Trc 04542 EventAgentNotReady sent to [472] (00000006 StatServer_AIL_HA 194.xxx.xxx.xxx:1700)
2010-05-25T15:38:47.573 Trc 04542 EventAgentNotReady sent to [460] (00000005 StatServer_URS 194.xxx.xxx.xxx:1184)
2010-05-25T15:38:47.573 Trc 04542 EventAgentNotReady sent to [448] (00000004 StatServer_CCPulse_HA 194.xxx.xxx.xxx:1699)
2010-05-25T15:38:47.573 Trc 04542 EventAgentNotReady sent to [440] (00000003 StatServer_AIL 194.xxx.xxx.xxx:1183)