" /> LDS disconnection with client - Genesys CTI User Forum
« previous next »
Pages: [1]   Go Down

Author Topic: LDS disconnection with client  (Read 3160 times)

Offline thmuche

  • Newbie
  • *
  • Posts: 17
  • Karma: 3
LDS disconnection with client
« on: June 03, 2015, 01:29:35 PM »
Advertisement
Hi,

I have an operation that end user application registers DN in TServer trought LDS (TServer Proxy).
In some extensions I see it in the LDS:

[size=8pt]
2015-06-03T09:38:31.450 Exception on 3232 for 512 - (external)
2015-06-03T09:38:31.450 client 3232, sessionId=142607712 will be deleted from Sender(65211) & Receiver(3232)
2015-06-03T09:38:31.450 Trc 04524 Client '[i]<application>[/i]' disconnected
2015-06-03T09:38:31.450 Removed 0 oustanding and 0 queued requests from clnt 3232 (left 10 requests)
2015-06-03T09:38:31.450 Removed 0 oustanding and 0 queued requests from clnt 3232 (left 0 requests)
2015-06-03T09:38:31.450 Removed 0 oustanding and 0 queued requests from clnt 3232 (left 0 requests)
2015-06-03T09:38:31.450 Clnt size for DN ([i]<extension X>[/i]) = 1
2015-06-03T09:38:31.450 [i]<TServerApplication>[/i] : (NewRefRec) added ref 2802->9558(11)
request to 65211([i]<TServerApplication>[/i])
..sent to [i]<HOST and Port>[/i](fd=720) [i]<HOST and Port>[/i](fd=692)
2015-06-03T09:38:31.450 Deleted DN [i]<extension X>[/i]
2015-06-03T09:38:31.450 Client [i]<application>[/i] (3232) unregistered for Call Monitoring
2015-06-03T09:38:31.450 Client [i]<application>[/i] (3232) unregistered for Call Monitoring Startup
2015-06-03T09:38:31.450 Client [i]<application>[/i] (3232) unregistered for Location Monitoring
2015-06-03T09:38:31.450 Client [i]<application>[/i] (3232) unregistered for Transaction Monitoring
2015-06-03T09:38:31.450 Client [i]<application>[/i] (3232) unregistered for Register All
2015-06-03T09:38:31.450 Client [i]<application>[/i] (3232) unregistered for VSP Control
2015-06-03T09:38:31.450 RemoveReceiver 3232 ([i]<application>[/i])
received from 65211([i]<TServerApplication>[/i])[i]<HOST and Port>[/i](fd=720)
2015-06-03T09:38:31.450 Trc 04541 Message EventUnregistered received from 65211 (TServer '[i]<TServerApplication>[/i]')
2015-06-03T09:38:31.450 [i]<TServerApplication>[/i](65211) -> EventUnregistered(425303)-9558
2015-06-03T09:38:31.450 Response on RequestUnregisterAddress (@09:38:31.450) from [i]<TServerApplication>[/i][/size]

I could assume that the exception in first line was generated for something how a packet loss between LDS host and the client? and because this the LDS generated the Unregister to TServer...
Logged

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: LDS disconnection with client
« Reply #1 on: June 03, 2015, 01:51:30 PM »
What say logs before the exception [quote]2015-06-03T09:38:31.450 Exception on 3232 for 512 - (external)[/quote]?
Logged

Offline thmuche

  • Newbie
  • *
  • Posts: 17
  • Karma: 3
Re: LDS disconnection with client
« Reply #2 on: June 03, 2015, 02:08:55 PM »
Nothing...  :-\

Just some minutes before has a RequestUpdateUserData from same application that was responding with successful.
Logged

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: LDS disconnection with client
« Reply #3 on: June 03, 2015, 02:13:01 PM »
If is possible to replicate/simulate the issue, you can catch the network communication and check whether the root-cause is there. The logs of LDS client say anything relevant? What say Genesys guys on that? Did you check RN for LDS?
Logged

Offline thmuche

  • Newbie
  • *
  • Posts: 17
  • Karma: 3
Re: LDS disconnection with client
« Reply #4 on: June 03, 2015, 02:31:40 PM »
I'm trying replicate. The problem is that the network between client and host is with the ICMP blocked and canīt see if I have or not packet loss by normal ways. I'm trying collect some retransmission or another sympton by Wireshark, sniffing the port connection.
The Genesys guys are investing yet and read the RN yesterday but the LDS is in last release (8.1.000.17).
Logged

Offline victor

  • Administrator
  • Hero Member
  • *****
  • Posts: 1419
  • Karma: 18
Re: LDS disconnection with client
« Reply #5 on: June 04, 2015, 06:26:33 AM »
Hi,

what is the application (client) and what are you using to connect to LDS? Are you using an SDK of any sort?
Logged

Offline thmuche

  • Newbie
  • *
  • Posts: 17
  • Karma: 3
Re: LDS disconnection with client
« Reply #6 on: June 09, 2015, 05:25:05 PM »
Hi Victor,

Is an end user application developed using the Genesys SDK.
The problem is really loss of packets between client and LDS, the client sets up the addp in register and a response from client was lost:

(650011): -AP[77]->-3092 @09:30:07.4410
(650036): -Ap[77]-<-3092 @09:30:07.5190
(666094): -AP[78]->-3092 @09:31:07.5320
(685343): -AI[t/o:60000,trace]-<-3092 @09:32:17.9820
(685344): -Ai[3092]->-3092 @09:32:17.9820

When happens it the client or server closes the port communication and the end-user-application don't reconnects.  :-\ :-\ :-\

Thank you all!
Logged

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: LDS disconnection with client
« Reply #7 on: June 09, 2015, 06:06:17 PM »
? You are showing ADDP protocol logs.
Timout is 60, but remote timeout is what?
What happens when ADDP says no connection possible? Well will go to alternative or mark server as unavailable.

AI is the Remote Timeout, so your values are what? 60/60? Try 60/65
Logged
Pages: [1]   Go Up
« previous next »