[quote author=Tambo link=topic=5104.msg22667#msg22667 date=1264756782]
The agents log into GAD. [/quote]
And , if i recognize you post theyr also use soft or hard sip phone soft to connect to sip t-server. right?
Well, since sip t-server version 7.2.001.27 it's incorrectly updates the contact option in the DN configuration if the authentication process for the REGISTER command fails. You can said - and so that?
But since sip t-server version 7.5.000.15 - If an attempt to update the SIP registration information for an endpoint with Configuration Server is unsuccessful, the contact info in the DN object will not be updated until the next SIP registration attempt. Another and o that ?
Resalt of combination this two bug and internal logic of registration proces in asme sip-hone - then sip-phone lost the connection to sip-server, but GAD client still connect = sip server marked this DN as un-monitored, but not generate EventAgentLogout. And you need to delete contact opion in DN anex or use the support phone to clear this issues and sinhronized the actual place status.
The possible solution in this situation - seting up the DN anex to use subcriber presence feature:
set 'use-register-for-service-state'=true - to use sip register state as DN service state
set 'subscribe-presence'=true - to send change of DN state as T-Lib event
And also, i can recomend set 'enable-agentlogin-presence'=true to enable mirror venet logic - remove DN registration if SIP-server got the T-lib event this agent status change.
hope u found this post helpfull
WBR Thaler