twitchy087
Vendor
10.1.2 system running on a 500v2
One-X on a Windows Server
Hey Everyone,
I have a couple issues that I am having problems with. I have home users utilizing an SSL VPN back to the office. Full access rules are in place for all of the needed ports. These users are utilizing Communicator through that VPN.
1 - "Status on No-Answer" does not seem to work with Communicator. I have it set to log the extension out upon missing a hunt group call. In testing, Communicator does disconnect for about 5 seconds but ultimately logs itself back in. I have searched and searched but cannot find anything to stop this. I am also using "Force Login" for the users. Has anyone come across this and have a solution to force a logout of a user on Communicator?
2 - Communicator users often cannot log into One-X Portal. Logging in simply presents the users with the "Your phone is logged out" message and does not allow them to log in. Communicator is logged in and I have confirmed operation on other systems when using Communicator as the phone. I am of the impression that this is a valid means of operating but it seems to be hit or miss. Has anyone come across this and have a solution? I really dont want to bring yet another silly item to Avaya...they are just so helpful...
Thanks!
One-X on a Windows Server
Hey Everyone,
I have a couple issues that I am having problems with. I have home users utilizing an SSL VPN back to the office. Full access rules are in place for all of the needed ports. These users are utilizing Communicator through that VPN.
1 - "Status on No-Answer" does not seem to work with Communicator. I have it set to log the extension out upon missing a hunt group call. In testing, Communicator does disconnect for about 5 seconds but ultimately logs itself back in. I have searched and searched but cannot find anything to stop this. I am also using "Force Login" for the users. Has anyone come across this and have a solution to force a logout of a user on Communicator?
2 - Communicator users often cannot log into One-X Portal. Logging in simply presents the users with the "Your phone is logged out" message and does not allow them to log in. Communicator is logged in and I have confirmed operation on other systems when using Communicator as the phone. I am of the impression that this is a valid means of operating but it seems to be hit or miss. Has anyone come across this and have a solution? I really dont want to bring yet another silly item to Avaya...they are just so helpful...
Thanks!
