On Thu, 2010-02-25 at 10:31 +0530, Chitralekha wrote: > Hi All, > > This query is regarding the "Disconnect on idle Time" and "Idle Time > out" for Instant Messaging. > > On Enable the "Instant Messaging" role, A new tab "Instant Messaging" > is made visible on the configUI under the Features menu. > Click on the "Show Advance settings" link. Parameters "Disconnect on > idle Time" and "Idle Time out" will be displayed. > > Configure the server-to-server federation page with the following > details on two different SUT's: > Enabled:YES > Disconnect on idle:YES > Idle timeout:10secs > Allow any user:YES > Click on Apply button. > Restart the prompted "Instant Messaging" services. > > Now I have 2 users where, > User1is added to xxxx.qantom.int---- SUT1 and > User2 is added to yyyy.qantom.int---SUT2. > Both the users are registered to two different Pidgin clients.User1 > and User2 are made buddy to each other through server to server > federation setup. > > > > Query > -------- > I keep both the clients idle for more than 10secs(say 20 secs). > Now if at all I ping User2 from User1(or vice versa) the message > should not reach to User2 as the server-to-server connection will be > closed after the given "Idle time out"(here it is 10secs). > This is what I understand with the help text provided for the > parameter"Disconnect on idle Time" and "Idle Time out" on the > ConfigUI. > Current behavior: > -I could still sent the messages(IM Chat) across each > other without any failour.The connection between two users User1 and > User2 is still established. > -And if there is notification for a user if at all the > server-to-server is really closed. > > Kindly please let me know if this is expected behavior or shall I > raise an Issue for the same. > Could anybody guide me through the functionality of "Disconnect on > idle Time" and "Idle Time out" parameters since the help text provided > is not Self Explanatory
No - even if the servers close the connections after the configured idle time, as soon as you send an IM that needs to go between them, they establish a new one. The only way for you to see if they are actually disconnecting when told to do so is to use Wireshark to look at the TCP directly. If you see FIN messages, the connection is closing. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
