> Hi Bob, > > Thanks for the inputs. > Single IM account could be registered to two Pidgin clients > by specifying a unique 'resource' value at each client as you > guided on. > I guess the the pasted error message (which I mentioned in my > previous mail )might have dropped while coming on the list > :-( ...Here I am attaching as a screen shot for reference: > screenshot_1.jpg > > However, if I send a message(IM) from the third client,the > Instant message reaches only to one of them and not to both > the clients and so is the same if I send an invitation to the > Conference Chat.Usually the message will reach to the client > which was registered first among the two but not always.
The client that is going to receive the message is the one that is the 'most available' by judging from their XMPP presence. For example, if one client is 'available' and the other is 'away' then the available client will get the message. If the presence that each client advertises is actually representative of your actual presence at that location then you will not miss any IMs but that does require some discipline. If both clients have the same 'availability' then the client that registered the last will get the message. > > I would like to know whether this is the expected behavior or > design intent. > > IMHO, I think the message should be delivered to both the > clients when sent from third client.Moreover a user would > never expect to lose his any Important chat messages :-) It is design intent given the current limitations however, I very much agree with you and I'd like to be able to turn on the 'broadcast' feature on openfire so that every client of equal availability gets the message but I cannot turn this on just yet because of a pidgin bug that I reported. The pidgin design team sent me a private patch that I tested and it should be included in the next release of Pidgin (2.7.0). Once this comes out, I'll turn on the broadcast but until then, that's what we have. If you are curious, here is the pidgin ticket that tracks this: http://developer.pidgin.im/ticket/11489 > > Thanks, > Chitralekha. > _______________________________________________ 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/
