(tcp_except_handler) disconnected on socket [12] - LINK DROPPING

[joint_heir]

We are trying to find out in which direction to go on. And trying to build a case to determine who to speak to. So although someone may answer the question - anyone else who can chime in and agree or disagree would be great.
We are loosing our link. Seems like no consistant issue, just randomly drops. Here is the portion of the Tserver which shows it. I will attach as an attachment the entire Tserver but did not want everyone having to read it. (10MB of text) 
@12:53:06.1387 [gctm] Call [00f201ad433e0cc0/4833eeb,s6,t7] processPartyChanged
@12:53:06.1388 [gctm] Call [00f201ad433e0cc0/4833eeb,s6,t7] No consult call/3rdParty found - Ignored.
@12:53:06.2304 [<<] FF 0A 00 1A 05 92 6A 0D 10 00 96 06 04 83 3E EB AA 03 00 4B 07 36 30 36 32 31
Give Ringback Response
Reference ID:126a
Call ID:4833eeb
Call Status:Successful
Controlled DN:60621
@12:53:06.2305 [mlink] (processGiveRingbackResponse)
@12:53:06.2305 [gctm] distributing EventTreatmentApplied to model
@12:53:06.2306 [gctm] request RequestGiveRingBackTreatment deactivated in reqMgr
@12:53:06.2306 [gctm] Call [00f201ad433e0cc0/4833eeb,s6,t7] distributing EventTreatmentApplied
@12:53:06.2307 [gctm] Call [00f201ad433e0cc0/4833eeb,s6,t7] processTreatmentApplied
@12:53:06.2308 [gctm] Party [00f201ad433e0cc0:60621,s800,at4,r2,l1] processTreatmentApplied
@12:53:06.2309 [gctm] Party [00f201ad433e0cc0:60621,s800,at4,r2,l1] Changing state to a00
@12:53:06.2311 [0] 7.2.004.00 distribute_response: message EventTreatmentApplied
.
.
.
12:53:06.231 Int 04544 Interaction message "EventTreatmentApplied" generated
12:53:06.231 Trc 04542 EventTreatmentApplied sent to 17 (0006 crcur)
12:53:06.231 Trc 04542 EventTreatmentApplied sent to 21 (000a crciccssp)
12:53:06.231 Trc 04542 EventTreatmentApplied sent to 20 (0009 crciccssu)
12:53:06.231 Trc 04542 EventTreatmentApplied sent to 18 (0007 crcstatserverpulse)
12:53:06.231 Trc 04542 EventTreatmentApplied sent to 15 (0004 crcstatservercca)
12:53:06.231 Trc 04542 EventTreatmentApplied sent to 14 (0003 crcstatserverur)
@12:53:06.2320 [gctm] request RequestGiveRingBackTreatment deactivated in reqMgr
[b](tcp_except_handler) disconnected on socket [12]
@12:53:06.6593 [tsgctm] Link [1,s4] Rx DOWN_PACKET
@12:53:06.6593 [tsgctm] Link [1,s4] stop[/b]
@12:53:06.6593 [tsgctm] LinkReg [1, act=1] clearAll
--------------------------------------------------------end of log--------------------------
Main point in bold.
Tried searching for this and found some things but nothing that tells us there is the culprit. Any help would be great.

[Genesys Rookie]

That is the same problem as I have and apparently in my case would be a disconnect between Symposium and TServer

The Symposium always has the MLSM service failing when the T-server(CTI) loses connection to Symposium.

"This was causing packet loss to such an extent that tserver would restart as well as cause some of the already mentioned symptoms...."

Your network people sure that no other issues exist with your data network? Given what you have said it would be my first port of call.

[bcyk]

What are versions of Genesys T-server for Symposium and Symposium server?

A number of checklists


1. dedicated LAN segment for CTI-link
    case 1: if other features of Symposium is not used
          [Symposium server]---(LAN-segment-A)---[T-server]----(public, LAN-segment-B)

    case 2: if Symposium features are referred (e.g., routing, reports, ...)
          [Symposium server]---(Router-switch)---[T-server]----(public, LAN-segment-B)
                                                    |
                                                    +--------- LAN-segment for Symposium features

2. debug log files setting
    - All Genesys processes running in the [T-server] machine should be inspected
    - No message level other than 'standard' should be directed to Message server
      (the network option in log section)
    - All debug log files should be pointed to LOCAL drives
      - never specify network drive, even to the same machine!

3. request service packs verification / update in Symposium server
    - personal experience was that some service packs must be applied to make the link stable
    - the latest service patch might not work as experienced
    - issue a trouble-ticket

4. Genesys T-server for Symposium release notes
    - check if there is similar symptom for the dropped link case
    - issue a Service Request


Suggested steps:
  A. Items (1) and (2)
  B. Items (3) and (4)