" /> Disconnection between LDS and T-Server - Genesys CTI User Forum

Author Topic: Disconnection between LDS and T-Server  (Read 3291 times)

Toni

  • Guest
Disconnection between LDS and T-Server
« on: November 08, 2007, 09:46:24 AM »
Advertisement
Hi all!!

I've been away some time due to different problems we've been having... :(

The most important, and the one I'll explain you in case you could give me some ideas is the disconnection problems between LDS and T-Server.

Mostly every day we are suffering automatic disconnection problems between those two appliations. LDS (actuating as proxy) is situated 5.000 km away from T-Server in a private network of 1GB capacity. Those disconnections last more or less 0.5 secs, but the problem is that when T-Server sees that LDS is disconnected, it unregisters all the DNs.

Thats causing that all agents are logged out, and call go default routing. Genesys labs told us that those disconnections could be produced by CPU/network problems, but I doubt it.

Has anybody suffered something similar?

There's any way to avoid T-Serevr unregisters all DNs?

When the LDS gets connected automatically after those 0.5 aprox, calls continue default routing, and we have to restart our GIS application in order calls and events arrive correctly to agents.

All comments will be welcome ;)

Thanks a lot friends!

Marked as best answer by on April 23, 2025, 10:13:38 PM

Offline victor

  • Administrator
  • Hero Member
  • *****
  • Posts: 1419
  • Karma: 18
Re: Disconnection between LDS and T-Server
« Reply #1 on: November 09, 2007, 02:22:43 AM »
  • Undo Best Answer
  • Hi, Tony,

    I am not sure if this is going to be of any use, but:

    1. have you played with addp settings? By setting them to different values, you can force a connection to last longer during a timeout. This, of course, would not work if you actually get a real network disconnect, where instead of a dropped packet, your session is forcefully dropped.

    2. LDS backup? If you have it, does it get disconnected as well?

    3. When LDS diconnects from T-Server, do you get any message in LDS that it got disconnected? Is URS informed about it?

    4. When LDS reconnects, why does it not re-register all DNs? This is a default behavior unless it was not aware that it got disconnected. When you say it get's automatically reconnected - how does the log look?

    5. check that no-context-distribution is NOT none.

    6. Can you post the log for LDS and URS and T/S when disconnect and reconnect happen? (+-10 seconds)

    Also, can you please tell me the version of LDS, URS and T/S - did you check for Release Notes?


    Thanks!
    Vic



    Toni

    • Guest
    Re: Disconnection between LDS and T-Server
    « Reply #2 on: November 19, 2007, 02:39:08 PM »
    Hi victor,

    Sorry for the delay.

    It seems it has been a network problem. Thank you anyway!! ;)

    Toni