GAD login failed

[Qasna]

Hi there,
I have issue with GAD login into the system. Im receiving following error message: Login Failed: DN 'voice (6051@Alcatel PBX)' is out of service.

The true is that Im able to use same login from my Alcatel IP Touch against PBX without any problem.
Also, IM bale to login to PBX from IPDesktopSogtPhone without any problem too.
I have checked licence file and it seems to me that everything is OK.
GAD log file is empty. TServer log file attached...

Any suggestions?
Thanks a lot
Jan


11:51:45.031 Trc 04541 RequestRegisterAddress received from [460] (00000007 med_gdesktop 192.168.249.115:4359)
message RequestRegisterAddress
AttributeReferenceID 9
AttributeThisDN '6051'
AttributeAddressType 1 (DN)
AttributeRegisterMode 0
AttributeControlMode 0
(tservice_proc) ControlMode set to 1 for 6051
10/23/08@11:51:45.031 +++ RqHandler::RequestRegisterAddress +++
 got message from client <7>
 [6051/-]: check device for 'RequestRegisterAddress'
 *** Transaction Info:
   Type/Oper. : 5 - 71 <Request : MonitorStart>
   hostRef    : 6f
   SubjDev[0] : 6051 (Private)
   LocalDev[0]: 6051 (Unknown)
   userInfo   : 7, 9
 H->S 18 bytes send, invoke id 111 (x6f), 0[1] requests pending
--- RqHandler::RequestRegisterAddress ---
+++ Err::<SubscribedResourceAvailability (ObjectMonitorLimitExceeded)> +++
 *** Transaction Info:
   Type/Oper. : 3 - 1026 <Error : <SubscribedResourceAvailability (ObjectMonitorLimitExceeded)>>
   hostRef    : 6f
 [6051]: event received, for <RequestRegisterAddress:7:9:148:1>
@11:51:45.0310 [0] 7.6.003.03 send_to_client: message EventError
(Object monitor limit exceeded)
AttributeEventSequenceNumber 00000000000000b4
AttributeTimeinuSecs 31000
AttributeTimeinSecs 1224755505 (11:51:45)
AttributeExtensions [64] 00 02 01 00..
'GCTI_SOURCE_ERROR_TYPE' 4
'GCTI_SOURCE_ERROR_CODE' 2
AttributeErrorMessage 'Object monitor limit exceeded'
AttributeErrorCode 1181
AttributeUserEvent RequestRegisterAddress
AttributeClientID 7
AttributeControlMode 1
AttributeReferenceID 9
AttributeThisDN '6051'
AttributeAddressType 1 (DN)
AttributeRegisterMode 0
11:51:45.031 Int 04545 Interaction message "EventError" sent to 460 ("med_gdesktop")
11:51:45.031 Trc 04542 EventError sent to [460] (00000007 med_gdesktop 192.168.249.115:4359)
--- Err::<SubscribedResourceAvailability (ObjectMonitorLimitExceeded)> ---
link (link-tcp) S->H: (0[0 / 0] requests pending)

[Fra]

According to Genesys there are insufficient CSTA licenses available on your switch to register the number of DNs that TServer has been commanded to.

[Qasna]

Hi Fra,
thanks for your tip and comments.
Problem resolved. The funny thing is that I have tried to re-read license file once again, plus I have tried to set parameter Register to switch to FALSE under the my problematic '6051' Extension. Then GAD login starts to work properly 
So thats my story. Thanks for your tips anyway.
Jan

[Fra]

You are welcome, I am glad I have been helpful 

[cavagnaro]

Well of course it will login how ever the DN is not monitored with that FALSE option and you may have later problems with reporting. As Fra mentioned you have a lack of CSTA licences on OXE, ask your provider to sell you more licenses, you are creating more objects than licenses you have.

[Qasna]

Cavagnaro,
I believe that we have 15 licenses for 15 agents, but for some reason more licenses are eaten by my DN Extensions... Is it possible?
What a I need to run according license policy is to use licenses for Agent Login, correct? If so, does it mean that I can set my DN Extensions to NOT Register with OXE? 
Thanks a lot
Jan

[cavagnaro]

Yes, that is "normal". You don't only monitor agents, you monitor ProACD, RSI, GhostZ Dialers if you have OCS, and Processing Groups, however this last one consumes CSTA Monitoring Bypass.
So on TServer you MUST configure: agent-smart-monitor = strict and agent-substitute=true.
Please read the TServer deployment guide for further reference and see which objects consume monitoring licenses.

[Qasna]

Thanks a lot for your tip! Opening TServer dep guide right now...  Jan

[Dionysis]

It's worth noting here that it's not Genesys licenses you are consuming, it is csta licenses on the PABX.

Generally, you need the same number of csta licenses as you have configured extensions, plus 1 extra to handle the licensing as the agents log in.

Setting the register = false option does not fully fix the problem, only delays it.