Softphone disconnects from Tserver

please help In our call center sometimes agent get disconnected from Tserver without any reason, only I see in the Tserver log file is something like below…

@12:27:45.3022 [4524] Client TServer65 disconnected on 75, id=0516:002f

g3_dn_unreg_hook(7718)

where 7718 is agent’s DN and we are using Avaya G3 switch.

my question is why this happens… couldn’t figure out.

Also I am thinking.. will this problem will be resolved if I used ADDP between Tserver and Soft phone?

Any help would be appreciated!!

Thanks.

Please check the type of the DN in the CME. Is it the same as other DNs r configured?

silly question what about other DNs?

Are you sure that all DNs ar enot unregistered?

IS there some events in PBX log? ← ask your engineers.

It would help to see the start section of the TServer logs as each DN gets registared + soem more from around the time of the actual event… in particular the messages to and from the switch…

Not all DNs having this problem at the same time. It happens randomly.

PBX log doesn’t have any events.

All DNs are configured to ACD Position.

Tserver log file shows DN registered correctly.

LIke I said before…post some more from the TServer error log…

If you can post a log (not all, pleaaaaaaaaseee, but only the relevant part) it would make it much easier for us to help you!

Hi All,

I’m facing the same issue, can you help?
Find below a sample of SIP Log:

09:43:14.745 Trc 04524 Client Agences 56 disconnected on [10884], id=003f985a
09:43:14.745: client disconnected
09:43:14.745: SipTServerDevice::ClientFarewell:SessionID(0x180db3e):LoggedInSessionID(0x180db3e)
09:43:14.745: SipTServerDevice::ClientFarewell:SessionID(0x180db3e): FORCE LOGOUT
09:43:14.745 – created: CRequest@de31af0 RequestAgentLogout-internal
09:43:14.745: SipTReq: 178,4855274
09:43:14.745: $+TLIB:CTI:Unknown:0:45517
09:43:14.745 +++ CIFace::Request +++
– new invoke
Parsed: RequestAgentLogout
internal
Numbers: +<5607510> -
Status: parsed:1 queued:0 sent:0 acked:0 preevent:0 event:0 context:0 transferred:0

This is given by SIP server configuration, where if the agent/client is disconnected the SIP server forcely logouts the agent to prevent routing of next interactions to this agent.

Thanks for your support.
My main concern is about that disconnection, is there any way to avoid that?

??? ??? : :
Like it is a network issue, so ask the network guys how can they improve that

Laptops?

Sent from my Redmi Note 3 using Tapatalk

Yes.
It was a connection issue; handled by the network team.

Thank you all for your support.

Regards.