CASSBusinessSystems
Vendor
Occasionally, when answering a call on Avaya Communicator, the IP Office will freeze/lockup. Has anybody else experienced this issue?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Communicator - IP Office R11.0.4.0.0 buld 74
- Thread starter CASSBusinessSystems
- Start date
- Status
- Thread starter
- #3
CASSBusinessSystems
Vendor
The whole PBX. Phones go into discover. Rebooting from the console brings it back. Also worth noting that this is Server Edition.
- Thread starter
- #5
CASSBusinessSystems
Vendor
Communicator 2.1.4.0. All access is lost to the Server except for console.
I'm thinking about backing up all data and installing fresh (We had upgraded this from R11.0.2).
I'm thinking about backing up all data and installing fresh (We had upgraded this from R11.0.2).
- Thread starter
- #6
CASSBusinessSystems
Vendor
Installing fresh this weekend. I will update again after that.
- Thread starter
- #7
CASSBusinessSystems
Vendor
After installing fresh this weekend and restoring all backed up data, all appears to be working but I'm not sure why I can't see or set presence in Communicator (just appears as 'Logged In' - even after reinstalling and windows firewall is turned off). One-X Mobile presence is working without issue. I am going to troubleshooting and reply back with anything I find.
Probably the OneX Portal FQDN is not set. While OneX Mobile connects to OneX Portal first and gets the SIP data from there Avaya Communicator connects to IPO as SIP client first and gets the OneX Portal information within a SIP message (within the 200 OK as response to the registration).
Check the message to see what Communicator gets.
Need some help with IP Office? CLI based cale blocking: SCN fallback over PSTN:
Check the message to see what Communicator gets.
Need some help with IP Office? CLI based cale blocking: SCN fallback over PSTN:
- Thread starter
- #9
CASSBusinessSystems
Vendor
Update here:
We loaded a fresh .ova image on a ESXI host and could also reproduce this problem, so we rolled back to R11.0.2 and all appears to be fine now (we also experience the problem on R11.0.4 for Hyper-V). The Avaya tech said that 11.0.4 SP1 is expected out on July 31st, but I think we're going to stay on 11.0.2 for at least a few more weeks. I'm wondering if anyone else has had this issue in R11.0.4 with Avaya Communicator for Windows?
We loaded a fresh .ova image on a ESXI host and could also reproduce this problem, so we rolled back to R11.0.2 and all appears to be fine now (we also experience the problem on R11.0.4 for Hyper-V). The Avaya tech said that 11.0.4 SP1 is expected out on July 31st, but I think we're going to stay on 11.0.2 for at least a few more weeks. I'm wondering if anyone else has had this issue in R11.0.4 with Avaya Communicator for Windows?
- Status
Similar threads