Jabber certificate for webex

[Ben Yosef]

Hi everyone,

Users on my company suddenly getting a popup certificate when they trying to login the jabber.

akamaicdn.webex.com - this is the certificate.

Anyone know something about it? 

Thanks for you help.

[DariuszNowak8349 · Accepted solution]

Hello Ben, 

We faced the same issue... Curiosity: in our case it impacts only PCs / notebooks with one, specific display language. 

Please take a look into: C:\Program Files (x86)\Cisco Systems\Cisco Jabber\jabber-config-defaults.xml 

There is an entry: 

<userConfig name="MeetingUpgradeServerUrl" value="https://akamaicdn.webex.com/jabberUpgrade/upgrade.php"/>

If you don't use Webex Meetings, the easiest way to disactivate above is to edit 'jabber-config.xml' on your CUCM by adding following line under "client" section: 
 <MeetingUpgradeServerUrl></MeetingUpgradeServerUrl>

... then restart TFTP service.

I hope this helps

[slashdots]

out of curiosity: what display language is affected?

[DariuszNowak8349]

German

[Ben Yosef]

Thanks for helping out.

[vinothbalaji.dd]

Hi,

One of our client is getting similar alert to accept to certificate for "akamaicdn.webex.com" on jabber.

Is this getting published from cisco? Do they need to accept it? How can we confirm is it from trusted source?

Any issues if we reject it?

[Ragnar]

Hi,

we are facing the same issue.

I added "<MeetingUpgradeServerUrl></MeetingUpgradeServerUrl>" to the  "jabber-config.xml".

But the entry still appears under "jabber-config-defaults.xml" after a fresh install. Yes we restarted the TFTP for all nodes.

We are using UC Service/Service Profiles in CUCM and there is no Option for "MeetingUpgradeServerUrl" in the UC Service Configuration. I assume that that's the problem?

[slashdots]

Hello Rangnar

It's not a documented parameter.
You need to
1. Click on "Add Custom" on the right hand side
2. Select "Client" in the dropdown
3. Enter "MeetingUpgradeServerUrl" in the Parameter text field
4. leave the value empty
5. save