We may be crossing the streams a little. The thread started about the directory 
URI naming scheme being used. This is to have future support for multiple 
domain names and supporting a SIP URI equals JID. In the past we had to do some 
interesting things with Microsoft LDS to get a few pieces to work. Hopefully 
were turning the corner to get away from that intermediary product.


We branched here about directory URI calling on the client. Yes, I also have 
URI dialing working but that isn't directly related to the JID creation 
mechanism.






Sent from Surface





From: Ryan Huff
Sent: ‎Wednesday‎, ‎November‎ ‎26‎, ‎2014 ‎11‎:‎59‎ ‎AM
To: Pavan K, Leslie Meade
Cc: cisco-voip ([email protected])





I call BS! 

I am running a fully AD integrated 9.1.2 CUCM with IM&Presence 9.1.2 and I have 
the Cisco Jabber for Windows 10.5 client deployed and I have URI Dialing 
running in the Jabber client, ALL. DAY. LONG and it works flawlessly.

In the deployment docs, it says to use EnableSIPUriDialing in the 
jabber-config.xml HOWEVER; if you look at the PRT logs generated from one of 
the 10.5 Jabber clients I bet you it is looking for the EnableSIPURIDialing 
node and not the EnableSIPUriDialing node.

Notice the casing difference in URI Vs. Uri ..... I couldn't get URI in the 
client for weeks, got the same junk answer from TAC as well .... then I 
troll'ed the PRT logs and found that to be my issue, a flippin' casing issue.






Date: Wed, 26 Nov 2014 09:09:50 -0600
From: [email protected]
To: [email protected]
CC: [email protected]
Subject: Re: [cisco-voip] Jabber contact disappears consistently


Just to close this out.

Official word from Cisco even though every piece of Jabber doc says its 
supported in J4W 10.5 
==

Currently Directory URI is only supported on the server.  The client has not 
yet been updated to fully support this.  So no, Jabber 10.5 does NOT support 
directory URI
==





On Sat, Nov 22, 2014 at 2:15 PM, Leslie Meade <[email protected]> wrote:




I also have seen the same issue, and put everyone onto the same server

 



Leslie Meade 



.................................................................. 
Mobile:778.228.4339 | Main: 604.676.5239
Email: [email protected]

 



From: cisco-voip [mailto:[email protected]] On Behalf Of Jason 
Aarons (AM)
Sent: Saturday, November 22, 2014 11:33 AM
To: Josh Warcop; Pavan K; [email protected]
Subject: Re: [cisco-voip] Jabber contact disappears consistently

 

I complete agree, put all Jabberusers on single server.  Saw the same bugs in 
10x.

 



From: cisco-voip [mailto:[email protected]] On Behalf Of Josh 
Warcop
Sent: Friday, November 21, 2014 3:48 PM
To: Pavan K; [email protected]
Subject: Re: [cisco-voip] Jabber contact disappears consistently

 

 


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: [email protected]
To: [email protected]
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 
[email protected] https://puck.nether.net/mailman/listinfo/cisco-voip



itevomcid 



-- 

- Pavan

_______________________________________________ cisco-voip mailing list 
[email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip

Reply via email to