UPDATE:
The problem has been fixed.
There issue was twofold.
No. 1: My apologies to every who insisted that the password must be the user password and not the extension password. Notwithstanding Avaya's guidance (which I think they have since removed), the login for Communicator is the...
Thanks snowman. Tried it (the change of the presence server) and it still failed.
There either has to be some corruption that I can't find, or some setting blocking the service, but no-one has been able to identify what can be blocking the service.
Hello Snowman -
Can't do a full screen shot as I don't give out internal (or external) ip addresses.
But the Server address points to the IP Office Lan 1
Server port is 5060 (using TCP)
Domain is set to the IP Office
and the Presence Server is set to the One-X UC ip address.
User login is the...
critchey - sorry, I didn't mean to overlook that.
Yessoftphone, one-X portal, one-X Telecommuter, Remote Worker, Desktop/Tablet VoIP and Mobile VoIP are all enabled
teletechman - yes, my apologies for the first post where I listed Essentials, I then corrected it in a later post indicating Essentials + Preferred Edition (R8+Preferred Edition (VM Pro)
Communicator has worked well in the past, but since we've moved the location of the server (and the original...
Okkie26 and teletechman
Yes, the preferred edition system is legit, unless it somehow was corrupted with the change of the UC module. But the Voicemail Pro still works, so it appears that the license is still in effect.
snowman50 - not a silly question, often the obvious is overlooked, but yes, softphone is enabled.
IPOLackey - I can work on getting the trace but I know the Communicator is communicating without issue (already disabled the SIP-ALG just in case it was interfering) VoIP tab has the trunks...
NYSTech
It does not work onsite or remote
No-one is able to use communicator
Yes, One-x Portal for users is working
No, I did not try removing the extension password as that would leave the physical extension vulnerable.
deffloh - I have R8+ Preferred Edition
IPOLackey - it was a good suggestion, but it didn't help.
I checked the UC Module - everything is green. The database checksum is still corrupt even though service pack 4 was supposed to correct that issue, but in the past that hasn't stopped Communicator (and does not affect the phone login...
I've tried:
[ol 1]
The extension as the username and the extension password;
The user name and the user name password;
The extension as the username and the user password;
The user name and the extension password;
[/ol]
All the above still result in the same error - incorrect extension or...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.