[cisco-voip] Jabber contact disappears consistently

[Andrew Grech]

Could be the resource-part of the full JID changing. Use pidgin and look up the
user in say pidgin and you will see username at example.com\resource then move
a user in the subcluster and see if it changes. Then you'll know its how
cisco jabber is storing the contacts.

On Sat, Nov 22, 2014 at 6:48 AM, Josh Warcop <josh at warcop.com> wrote:

> Do to the bugs I've seen I have been pinning all users to a single node in
> the cluster and just having HA failover.
>
> ------------------------------
> Date: Fri, 21 Nov 2014 11:31:39 -0600
> From: pav.ccie at gmail.com
> To: cisco-voip at puck.nether.net
> Subject: [cisco-voip] Jabber contact disappears consistently
>
>
> We have an interesting problem on a new jabber deployment that has us
> stumped. Wonder if anybody else saw this.
>
> Two jabber servers with ha enabled and balanced users. Using 10.5su1 for
> jabber windows and ucm/imp.
>
> Leveraging sip directory uri as the IM scheme due to a multi forest
> environment with duplicate Samaccountnames across domains.
>
> UserA contact list has userB on it. Folks can im each other without any
> problem. If we move userB from his imp server to another server in the same
> subcluster, userB disappears from userA's contact list.
>
> Repeatable across multiple users with different userA and userB and
> happens every time regardless of moving them from server1 to server2 or
> vice versa.
>
> Using router to router communication between nodes and default
> jabber-config.
>
> Any ideas ?
> Have a TAC case open but its going nowhere.
>
>
>
>
> _______________________________________________ cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20141122/069dec89/attachment.html>