I sat Joshua’s CLUS2018 BRKUCC-3347 troubleshooting Jabber breakout session
today. That question came up. We can scale using the service profile but from a
jabber-config.xml perspective, it is all or individual. Jabber 11.9 and up has
not changed this. It was interesting to note that in his
Hey - I had to go buy two new DNS servers and configure a specialty subdomain
to enable MRA.
DNS resolution as the best way to decide who to speak to? Not sure I’m on board
there.
You’re preaching to the converted as they say.
-sent from mobile device-
Lelio Fulgenzi, B.A. | Senior Analyst
It just a silly draconian style application behavior that just doesn’t need to
be there.
Sent from my iPhone
On Jun 14, 2018, at 18:51, Lelio Fulgenzi
mailto:le...@uoguelph.ca>> wrote:
Interesting. Thanks. I’m guessing we’re either not configured for Jabber cloud
or are custom domain is
Interesting - I’ll have to read the rest of the thread to understand the full
the impact of this, however, is it only a problem when you have WebEx messenger
subscription and you don’t want to use it. Or does this impact everyone?
As for your comment on URLs and MSIs, I hear ya. Both good
As I said, I’d even be good with no visual changes. Just let it roll to SRV
checking (the Edge or UDS) if it fails Webexconnect. Why does it have to “fail”
if Webexconnect can’t authenticate?
Sent from my iPhone
On Jun 14, 2018, at 17:42, Anthony Holloway
I guess any solution is going to be good for some, and bad for others. For
example, making a user choose "Cloud Login" is not good in my opinion,
because I believe users will not understand that language.
This reminds me of installing QM and during the setup it asks you to enter
the CTI Server
The spirit of Jabber login‘s as I understand it, is for the client to be able
to login in one shot with out the user having to figure out what side of the
network they’re on, what type of service to use ... etc.
And that mostly works except for when it comes to the Webex connect
authentication
Not at all. I’m saying the control needs to be more simple and friendly to use.
Why can’t there be a control right on the front of the login screen underneath
the advanced settings link, “Cloud Login Yes | No”?
Sent from my iPhone
On Jun 14, 2018, at 17:13, Anthony Holloway
Are you arguing that the Jabber client shouldn't check for cloud services
(webex messaenger) at all?
What is your distinction between a technique which solves a problem, and a
solution?
On Thu, Jun 14, 2018 at 5:04 PM Ryan Huff wrote:
> While I will agree that each “solution” can be made to
While I will agree that each “solution” can be made to work with a little
creativity, my supposition is more basic. Why should I have to?
All of these techniques are not solutions, they are ways to navigate the boat
around an anchor that shouldn’t even be there.
Sent from my iPhone
On Jun 14,
*RE: Re-installing the client*
How did you get the client on their in the first place? How do you handle
upgrades? If either of these methods used the MSI, then using the CLEAR=1
switch shouldn't be a big deal.
*RE: Funky URLs*
End Users are happy to click on URLs. In fact, it happens all the
I realized that in CUCM v9 and Jabber v11, we needed to use custom jabber xml
files if we wanted to turn on a feature for some people but not others. That
gets tricky with multiple features and providing some but not others.
Definitely not scalable.
Has this changed in CUCM v11.5 and Jabber
I think the answer the question is: No, not in CUCM. You will need to
utilize one of your backups. Whether via a DRS restore in a sandbox
network, or with the DRS backup decrypter, or something else.
The other options mentioned, are basically looking for what versions your
phones are currently
13 matches
Mail list logo
