" /> TSERVER to AES DLG Issues - Genesys CTI User Forum

Author Topic: TSERVER to AES DLG Issues  (Read 5670 times)

Offline coachgt1

  • Newbie
  • *
  • Posts: 3
  • Karma: 0
TSERVER to AES DLG Issues
« on: January 24, 2012, 06:48:16 PM »
Advertisement
We are having an issue with our connection between Genesys 8.1 and Avaya AES 4.2.1.  The connection between these two drops and loses CTI and random times during the day.  All of the network connections have been tested and throughput is good with no errors.  The only possible issue I see is the T-Server is set to 1GB Full and the switchport is set to 1GB Full but the AES is set at 100 MB Full with auto off.

The heartbeat timer is set for every 40 seconds with a timeout of 20 seconds.  Below is a snapshot of the Genesys Log when the connection drops.

@17:01:11.1613 [gctmi] AgentLogin [7670,id4496,sNRDY] EvAgentLogin ignored, already logged-in.
@17:01:11.8548 [tsgctm] Link [1,s0] restart timer expired. Opening link.
@17:01:11.8549 [tsgctm] Link [1,s0] start
(link_start) link [1] 'link-tcp' start
(tcp_start) connecting to 30.122.29.101:5678... contacted on socket [70]
@17:01:11.8550 [tsgctm] Link [1,s0] Changing state to 1
(tcp_connect_handler) 30.122.29.101:5678 is connected on socket [70]
@17:01:11.8554 [tsgctm] Link [1,s1] Rx UP_PACKET
@17:01:11.8554 [tsgctm] Link [1,s1] openSession
@17:01:11.8554 [tsgctm] Link [1,s1] Changing state to 2
@17:01:11.8554 [asai] Link [1,s2] (sysReqSessionOpen)
@17:01:11.8554 [asai] No CRVs allocated.
17:01:11.855 Trc 31000 Connection Request: Link[1], link number[1], protocol(1)
@17:01:11.8554 [31000] Connection Request: Link[1], link number[1], protocol(1)
      TP_ConnectionRequest
      Link number: 1
      Protocol: 1
@17:01:11.8555 [>>] 01 00 00 02 01 01
@17:01:13.3322 [BSYNC] Trace: Received [16]:
message RequestSetCallInfo
      AttributeConnID  02e802013b3b2202
      AttributeUpdateRevision 66280
      AttributeOriginalConnID 02e802013b3b2108
      AttributeConsultType    3
@17:01:13.3322 HA: Backup call [02e802013b3b2202] is changed
@17:01:13.3322 [BSYNC] Trace: Received [16]:
message EventCallPartyState
      AttributeConnID  02e802013b3b2202
      AttributePartyID  42e802013b3bc6c4
      AttributePartyUUID      '000CL50HFSFHLD6T3PT1QH5AES002K14'
      AttributeDN '2582'
@17:01:13.3323 HA: Backup party [42e802013b3bc6c4] is created, digits='2582', uuid='000CL50HFSFHLD6T3PT1QH5AES002K14'
@17:01:16.8726 [<<] 00 FF 00 00
      TP_ErrorNotification
      Cause: Server error
17:01:16.872 Std 31014 Error Notification: Link[1], reason [Server error]
@17:01:16.8726 [31014] Error Notification: Link[1], reason [Server error]
@17:01:16.8727 [tsgctm] Link [1,s2] stop
@17:01:16.8727 [tsgctm] LinkReg [1, act=0] clearAll
@17:01:16.8734 [tsgctm] Link [1,s2] Changing state to 0
(link_stop) link [1] 'link-tcp' stop
(tcp_stop) closed on [70]

Offline Fra

  • Hero Member
  • *****
  • Posts: 856
  • Karma: -3
Re: TSERVER to AES DLG Issues
« Reply #1 on: January 25, 2012, 09:35:25 AM »
From the snippet you posted, you can't even say that the connection drops, as it's not even established: there's a connection request which is rejected with cause 'Server Error'.

I suggest you have the same settings on both ends of your LAN segment plus double check the config on AES (ip-services).

Fra

Offline genesysguru

  • Sr. Member
  • ****
  • Posts: 293
  • Karma: 12
    • Genesys Guru Blog
Re: TSERVER to AES DLG Issues
« Reply #2 on: January 25, 2012, 01:52:38 PM »
Have you applied the "magic" settings:

http://genesysguru.com/blog/blog/2010/11/12/magic-avaya-t-server-options/