" /> Receive EventDNOutOfService for some Extension DN when starting TServer - Genesys CTI User Forum

Author Topic: Receive EventDNOutOfService for some Extension DN when starting TServer  (Read 6762 times)

Offline hong2493

  • Newbie
  • *
  • Posts: 4
  • Karma: 0
Advertisement
When starting TServer, some extension DNs(such as 176) cannot be registered and EventDNOutOfService. However, some extension DNs(such as 173) are ok.

I have no idea why some are ok, some are not ok. b

@03:00:03.7810 [0] 8.0.006.03 distribute_event: message EventDNBackInService
AttributeEventSequenceNumber 0000000000000088
AttributeTimeinuSecs 781000
AttributeTimeinSecs 1271012403 (03:00:03)
AttributeThisDN '173'
@03:00:03.7810 [tsgctm] Registrar [173, l=1f, s=1]  RX OK response, i=0
@03:00:03.7810 [gctmi] request SysRequestRegister ctiRefId 59 removed from reqMgr
@03:00:03.7810 [tsgctm] LinkReg [1f, act=1] processSysRegistered 87 of 87
@03:00:03.7810 [tsapi] TsapiLink [s2] processDnRegistrationComplete
@03:00:03.7810 [tsgctm] TsapiLink [s2] Changing state to 3
@03:00:03.7810 [gctmi] TMsg [EventLinkConnected()] distributing to model
@03:00:03.7810 [gctmi] Switch [sUNK] distributing EventLinkConnected
@03:00:03.7810 [gctmi] Switch [sUNK] processLinkConnected


@03:00:03.6720 [0] 8.0.006.03 distribute_event: message EventDNOutOfService
AttributeEventSequenceNumber 000000000000004f
AttributeTimeinuSecs 672000
AttributeTimeinSecs 1271012403 (03:00:03)
AttributeThisDN '176'
@03:00:03.6720 [tsgctm] LinkReg [1f, act=1] processSysRegisteredError, code=49c, retry=b
@03:00:03.6720 [tsgctm] TsapiLink [s2] processDnRegistrationError
@03:00:03.6720 [tsgctm] LinkReg [1f, act=1] processSysRegistered 4e of 87
@03:00:03.6720 [tsgctm] Registrar [176, l=1f, s=0]  RX error response, i=0, c=49c
@03:00:03.6720 [gctmi] request SysRequestRegister ctiRefId 61 removed from reqMgr
@03:00:03.6720 [tsgctm] Registrar [176, l=1f, s=0] re-sending attempt 1 of 10 in 1157mS
@03:00:03.6720 [tsapi] TsapiLink [s2] [14241200] >> 5:114
@03:00:03.6720 [<<] CSTACONFIRMATION invokeID 6
CSTAMonitorConfEvent
{
  monitorCrossRefID 76
  monitorFilter
  {
    call 32768
    feature 144
    agent 252
    maintenance 192
    privateFilter 0
  }
}
ATTMonitorConfEvent
{
  usedFilter 128
}
@03:00:03.6720 [csta] (processMonitorStartResponse)
@03:00:03.6720 [gctmi] request SysRequestRegister ctiRefId 6 deactivated in reqMgr
@03:00:03.6720 [gctmi] TMsg [SysEventRegistered()] distributing to model

Offline smile

  • Sr. Member
  • ****
  • Posts: 286
  • Karma: 6
what kind of tserver do you use?

In case of CCM if such trouble happens, our  telephony admin do the link/unlink for this dn on ccm side. usually this helps.

Offline hong2493

  • Newbie
  • *
  • Posts: 4
  • Karma: 0
I am using TServer for Avaya TSAPI, Version: 8.0.006.03

Offline Fra

  • Hero Member
  • *****
  • Posts: 856
  • Karma: -3
..and have you checked what the status of those devices is on the Avaya?

Fra

Offline hong2493

  • Newbie
  • *
  • Posts: 4
  • Karma: 0
[quote author=Fra link=topic=5469.msg23818#msg23818 date=1271147264]
..and have you checked what the status of those devices is on the Avaya?

Fra
[/quote]

The status of those devices should be ok. They can be logged in with agent by Avaya hard phone and answer calls.

Offline Fra

  • Hero Member
  • *****
  • Posts: 856
  • Karma: -3
Double check it -  the EventDnOutOfService is generated by T-Server upon an unsuccessful DN registration request.
If their status is ok, restart T-Server and upload its startup log without editing it.

Fra

Offline hong2493

  • Newbie
  • *
  • Posts: 4
  • Karma: 0
[quote author=Fra link=topic=5469.msg23832#msg23832 date=1271203893]
Double check it -  the EventDnOutOfService is generated by T-Server upon an unsuccessful DN registration request.
If their status is ok, restart T-Server and upload its startup log without editing it.

Fra
[/quote]

There is a error when starting TServer for some extension DNs(not all DNs)
@03:00:03.6720 [<<] CSTACONFIRMATION invokeID 62

CSTAUniversalFailureConfEvent

{

error genericSubscribedResourceAvailability

}

@03:00:03.6720 [csta] (processErrorResponse)

@03:00:03.6720 [gctmi] request SysRequestRegister ctiRefId 62 deactivated in reqMgr

@03:00:03.6720 [gctmi] TMsg [EventError()] distributing to model

@03:00:03.6720 [gctmi] Address [177,tDN,sUNK] distributing EventError

@03:00:03.6720 [dmcc] (DmccDevice::dmccProcessError)

@03:00:03.6720 [gctmi] Address [177,tDN,sUNK] processOutOfService

@03:00:03.6720 [gctm] Address [177,tDN,sUNK] Changing state to 80

@03:00:03.6720 [0] 8.0.006.03 distribute_event: message EventDNOutOfService

          AttributeEventSequenceNumber          0000000000000051

          AttributeTimeinuSecs    672000

          AttributeTimeinSecs      1271012403 (03:00:03)

          AttributeThisDN          '177'


Do anyone know what is the error
"error genericSubscribedResourceAvailability"?

Thanks a lot.

Offline noor_372

  • Newbie
  • *
  • Posts: 14
  • Karma: 0
Re: Receive EventDNOutOfService for some Extension DN when starting TServer
« Reply #7 on: October 04, 2010, 05:30:51 PM »
Hi,

Were you able to sort out this problem ; actually i am facing the same error and need urgent help.


Regards

Offline johan_swart

  • Newbie
  • *
  • Posts: 5
  • Karma: 0
Re: Receive EventDNOutOfService for some Extension DN when starting TServer
« Reply #8 on: October 06, 2010, 12:42:56 PM »
Please check that the DN's that failed is loaded on the AES under your Genesys group. If you are experiencing routing issues as well, you may have an incorrect version of the TSAPI client or you may have incorrect AES licenses loaded.

Regards