Avaya R11.0.2 - One X Portal Directory 2

[splittingcodec]

Hello,

I've got a nagging issue that I'm experiencing following a system upgrade of a Primary Server from R 10.1 > 11.0.2.

The trouble that I'm having is that, for two users who use One-X portal through the web page (Https, port 9443), each morning when they try to connect and login, the system will kick them after initializing the portal, giving an error message that "You have been logged out because the phone system became unavailable"

This has been occuring for about 10 days, and here are some steps that I've taken to troubleshoot the matter:

- Ensure that the Directory Service user is enabled and has permission to Read/Write the directory under Security Settings > Rights Groups > HTTP
- Forced re-sync the system directory in the Admin login for OneX Portal and restart the service
- Change from port 8080 login to 9443

The second step above, where i force a re-sync and restart the service, will allow the user to login and use the portal for a day, but, when they come into the office the following the morning, they are again getting repeatedly kicked with the error message explained above.

I wanted to see if this was anything that any of you have experienced before, and if there's another solution short of re-building the One X Portal configuration in full.

Any help is appreciated.

 

[ogTOKYO]

that is a weird issue, the on going problem I have at one site is that onex users like to just "forget" their passwords, because each change requires a reboot for the passwords to propagate over to the app server, we've started changing the passwords into something more standard but still unique.

Anyways, bump for answer.

______________________
|........................................|
|.....i.eat.bunny.children......|
|______________________|
(\__/) ||
(•Y•). ||
/ < )<||

 

[ivjan]

After upgrading IP Office form R9 to R11, and then upgrade One-X Portal to R11,
Avaya One-X mobile client would not able SIP register to IP office.
Also when I try to login same user on One-X portal, the login has been refused after shortly displaying user dashboard, and show this One-X portal message :

"You have been logged out because the phone system became unavailable"

Is there any idea how to resolve this ?

 

[ivjan]

I reinstall One-X Portal version 11.02 on Windows and i have this problem:

DSML-Provider-1-192.168.1.100 Failed Jul 25, 2019 1:55:54 PM Global resynchronization failed for IP Office...

I have IP Office version R11.0.02

Anyone have this or similar issues ?

 

[bahmonkeys]

You login with secure communications https port 9443 and TLS certificate port 5061. You enable secure communications on One-x portal?

What do these 2 users login to, desk phone or soft client? Are they remote users?

 

[ivjan]

If you mean about "Directory IP Office DSML Provider" the login is https on port 9443.
One-X portal secure communication is enabled.

We used one-X Portal for One-X Mobile Clients, so we have soft clients.

 

[JnatureLy]

I've been battling this one as ell. When I ran Apache Chainsaw to troubleshoot, it shows an error regarding the SipX config and specific to the "XMPP accounts parser". I've tracked it down to a recurrence every AM when housekeeping kicks in and in this case, we suspect it pertains to users who log out of their phone at the end of the business day. I looked through Openfire and their accounts do not seem to be affected but I did recreate one of the problematic users in Openfire and also set a custom presence group for all users, but no avail, so I suspect this is an 11.0.2 bug.

Also, fun fact - in IPOSE r10.1+, I have found that the IPTABLES settings automatically block connections to ports 9094 and 9095 via FIREWALLD. I guess I missed the documentation when they changed that....

 

[splittingcodec]

Thanks all for the replies;

JnatureLy - this is EXACTLY what I've found, as well. System housekeeping, users being logged out, the openfire, all of that down to a tee. I suspect 11.0.2 release bug as well and I'm waiting on one of the senior folks to open a ticket with Avaya as I'm not qualified to do so.

The trouble being that, no matter how many times I advise these guys to NOT LOG OUT OF THEIR PHONES AT SHIFT END, they don't seem to get the message. I suppose you can't fix a people problem with technology.

I've been getting into the office before the start of business, logging their phones in remotely, resyncing the directories in One X, then restarting the service. That does the trick for these folks that won't listen to their certified vendor.

If anybody finds anything else on this, input is appreciated.

 

[Ekster]

There was a CP released (One-X Portal V11.0.203.15) to resolve this:

IPOFFICE-146965
Logging out via *36 a hardphone while logged in 1X Call Assistant and Outlook plugin will not allow them to log back in when phone is available until 1X Portal is rebooted.


Upgrade to FP4

“Some humans would do anything to see if it was possible to do it.
If you put a large switch in some cave somewhere, with a sign on it saying 'End-of-the-World Switch. PLEASE DO NOT TOUCH'.
The paint wouldn't even have time to dry.”

Terry Pratchet

 

[splittingcodec]

Thank you Ekster. I appreciate the help!!!