Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
The key is using the sipuri to resolve contacts... Here is the jabber-config file I am using <?xml version="1.0" encoding="utf-8"?><config version="1.0"> <Options> <Start_Client_On_Start_OS>true</Start_Client_On_Start_OS> <AllowUserCustomTab...
yes, I am currently doing this with four businesses that are in the same scenario. You will need to setup LDAP directories on both UC clusters, one with home cluster and presence enabled, the other without. Then in the Service Profile check the box...
I am having to force UDS for both on site and mobile access. Also in this scenario I had to sync all four AD forests to All four UC clusters... 1 of the forest on each cluster sets the User for home cluster, the other 3 I just apply a feature group...
You are correct, it is supposed to be in Beta still on the producion release of jabber 10.6, however this configuration does work when using only UDS for both on premise and off premise deployments. The issue was still in place on the 10.5 train of ...
I have this working in a multi-cluster/multi-forest environment.. jabber-config file is below, one thing to note as I just recently discovered, the sip: that prefixes the msRTCSIP-primaryuseraddress in ad is case sensitive, in this environment, two ...
