Genesys CTI User Forum

Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: eduardosaito on January 28, 2015, 11:42:38 PM

Title: Yealink T20P and Sip Server - Force logout on agents
Post by: eduardosaito on January 28, 2015, 11:42:38 PM
Hi there again  ;D,

Now i am having trouble with agents being logged out from Sip Server. According to log, it seems that the cause is the DN unregistering in sip server.

I already configured the phones keep alive every 30 seconds using sip options type, and in log i can see the OK from sip server.

Thatīs part of the log. Is there any other configuration i should check to avoid this dn unregister with sip server?

14:30:57.080: Sending  [0,UDP] 405 bytes to 10.74.26.58:5062 >>>>>
SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.74.26.58:5062;branch=z9hG4bK836948041;received=10.74.26.58

From: "1105072058" <sip:1105072058@172.19.132.158>;tag=518107016

To: "1105072058" <sip:1105072058@172.19.132.158>;tag=488F32FC-4D23-4F52-9B03-559785AAE3E8-3800522

Call-ID: 1023564669@10.74.26.58

CSeq: 1 REGISTER

Expires: 3600

Contact: <sip:1105072058@10.74.26.58:5062>;expires=3600

Content-Length: 0




14:30:57.080: $-NET:SIP::0:58

14:30:57.080 Trc 04524 Client anonymousTServerClient disconnected on [12052], id=00004c09
14:30:57.080: client disconnected
14:30:57.080: SipTServerDevice::ClientFarewell:SessionID(0x894557):LoggedInSessionID(0x894557)
14:30:57.080: SipTServerDevice::ClientFarewell:SessionID(0x894557): FORCE LOGOUT
14:30:57.080  -- created: CRequest@be119a0 RequestAgentLogout-internal
14:30:57.080: $+TLIB:CTI:Unknown:0:211119
14:30:57.080 +++ CIFace::Request +++
  -- new invoke
  Parsed: RequestAgentLogout
  **internal**
  Numbers: +<1100073217> -<none>
  Status: parsed:1 queued:0 sent:0 acked:0 preevent:0 event:0 context:0 transferred:0
  -----
14:30:57.080: AgentLogut: forced while position is in the call
@14:30:57.0800 [0] 8.1.101.50 distribute_event: message EventAgentLogout
AttributeExtensions [74] 00 02 00 00..
'EmulateLogin' 'true'
'AgentSessionID' 'NCTGUC5Q8H67924GEJKUMR538G09CHIF'
AttributeEventSequenceNumber 0000000002dc815d
AttributeTimeinuSecs 80000
AttributeTimeinSecs 1422462657 (14:30:57)
AttributeAgentID '1100010117'
AttributeThisDN '1100073217'

14:30:57.080: Agent logged off
14:30:57.080: DelImplicitMwiAgentsLoginTables dn:1100073217 mailbox:
14:30:57.080: MWIMNGR:STOP: DN="1100073217", Type=2 - not monitored
  -- AgnDevData: synchronising agent state 0xb00 for 1100073217
  -- AgnDevData: synchronising previous state 0x2
  -- AgnDevData: synchronising previous reason code: NULL
  -- AgnDevData: synchronising not-ready workmode 0

@14:30:57.0800 [BSYNC] Trace: Sent
  -- emulated by AgentEmulator
  FinishRequest CRequest@be119a0 RequestAgentLogout-internal
  IFace stats: q=0 s=0
  -- complete
14:30:57.080 --- CIFace::Request ---
14:30:57.080: IFACE:REQ:AGENTLOGOUT:SESSION_ID(0x0)
14:30:57.080  -- deleted: CRequest@be119a0 RequestAgentLogout-internal
14:30:57.080: $-TLIB:CTI:Unknown:0:756

14:30:57.080 TRegManager::ClientUnregistered 19465  1100073217
14:30:57.080 TRegManager::ClientDisconnected 19465
@14:30:57.0800 [ISCC] CLUSTER_NODE_ROUTE_DESTINATION_STRATEGY: location removed: (anonymousTServerClient:00004c09@)
@14:30:57.0800 [ISCC] Location anonymousTServerClient:00004c09@/0 is removed
@14:30:57.0800 [ISCC] (location-removed-object anonymousTServerClient:00004c09@)


thanks in advance !
Title: Re: Yealink T20P and Sip Server - Force logout on agents
Post by: Grand_Master on January 29, 2015, 12:57:14 AM
What does the endpoint logs show?
Title: Re: Yealink T20P and Sip Server - Force logout on agents
Post by: shiningravi18 on February 02, 2015, 07:10:46 AM
Hello,

Being a Learner would like to share my experience on this issue as i have faced the same situation few days back on my site.

While troubleshooting to this we found Data packet loss (RTO) in network while making ping to SIP server from agent desktop due to which DN's were getting OutOfService and same error message "FORCE LOGOUT" we found in logs as well.

Title: Re: Yealink T20P and Sip Server - Force logout on agents
Post by: jamesmurphyau on February 02, 2015, 07:44:35 AM
That SIP message doesn't look like it matches the EventAgentLogout? They look like two messages for two different DNs (SIP OK = 1105072058, EventAgentLogout = 1100073217)..

Are you logging the agent (1100010117?) into a second DN (1105072058) using a SIP REGISTER which might be automatically logging the agent out of their previous DN (1100073217))..? Not sure if/how that's possible but it's the only thing I can come out with if the two messages relate to different DNs