IP Office 11.1.1 SE, Sending chat message gives unexpected error. 2

[G van Hamburg]

Hi all,

So in my Lab i have an IP Office SE, release 11.1.1. I use this system primarily to study the Avaya SBCE (my expertise) in combination with remote workers and IP office. (little knowledge of IPO)

Yesterday, I forgot to make a snapshot before I changed the Onex-X Portal XMPP domain name and renewed the IPO identity certificate. (I did that action before) I am not sure what I did wrong but now chat is not working anymore. On the IX client I can see the other user’s chat bubble, I can click on it and type a message, but when I press sent, I get an unexpected error.

I deleted the users from IPO and added them again and the sync between the IPO and One-X portal part seems ok. (When I delete the users, the disappear from the dorectory in One-X Portal) Any ideas what I could do?

Freelance Certified Avaya Aura Engineer

 

[G van Hamburg]

Ok, I need to add one more important thing. I only have 2 users on the IPO. The 1st is named ‘Extension 1000’ and the 2nd ‘Extension 1001’. When, on my iPhone, I open the IX WP client, there are no recent chat messages loaded. (Since I deleted the users an added them again that seems fair)

I click on the > to go to chat messages and search for 1001. I find 1001 in the company directory, still good. when I click on 1001 I can see his presence (also good) but.....

The chat bubble of 1001 shows the user is available at 'Extension_1001@mydomain.com’. Now to be honest, I think that is (at least part of) the issue. I remember I saw this before before I went to 11.1.1. but as far as I can remember that happened sometimes when switching between Wifi and 4G.

As said, I am not able to sent a chat message at that point but when I go back to ‘Top of mind’ I can see that recent chat with the correct name.

Freelance Certified Avaya Aura Engineer

 

[G van Hamburg]

Ok, I found this in the One-X Portal logs.

2021-05-19 17:22:43,941 ERROR OpenApiRestServlet - Open Api Exception occured while procesing REST request -OpenApiRestException [422][INVALID_INPUT_DATA][EXT_1001@mydomain.com][ 'To' user does not exists.]

Any advice is welcome

Freelance Certified Avaya Aura Engineer

 

[G van Hamburg]

Is there a way to uninstall one-x portal on SE and after that reinstall?

Freelance Certified Avaya Aura Engineer

 

[TomMills]

It's been a long time since i played with this, so take this with a pinch of salt, but I think you can do this if you log in on port 7071 and go to the updates page.

You can uninstall and reinstall services there. I remember having to use it to apply a few fixes on app servers many years ago.

If you're not doing this on a live system maybe have a play around in there. If you uninstall a service, you can reinstall from the same place.

APSS/ACIS/ACSS-SME
not arrogant, just succinct.

 

[G van Hamburg]

Hi Tom,

I did try that but it did not uninstall because there where dependencies and I did not feel like uninstalling everything. So I digged a little further and found this:

Enabling the XMPP Admin Console

For security, the XMPP admin console is not enabled by default. If enabled for maintenance or troubleshooting, you must disable the admin console again afterwards.
To enable the Admin console:
1. Login locally as the root user.
2. Enter cd /opt/Avaya/oneXportal/openfire/bin
3. At the prompt, enter: sh AdminConsoleManager.sh enable
4. To restart the service, enter: service onexportal restart

I logged in to that console and found my problem. As stated in my initial post, it all started after changing the IPO certificate. I did that before but this time I skipped the dns name onex.mydomain.com. This because in one-x portal I changed the hostname and xmpp domain a while ago from onex.mydomain.com to ipo.mydomain.com. (This because on an SE all can be the same)

But, and here’s the thing, changing onex xmpp domain and hostname did not change the (openfire) xmpp server name! So first thing I saw was a lot of certificate errors! I changed the server name to ipo.mydomain.com, removed some old users, cleared the cache and rebooted onex-portal. After that: Back In Business! Case closed!

Freelance Certified Avaya Aura Engineer