Dear all, i have a preferred edition IPO500V2 gateway and have added a Linux appliction server but have some issues logging in.
All the servers are showing green under Application Server Web Control (on port :7071).
I then try the demo login on I am able to login with extension (not a username just the extension, i.e. 1502), and password (in the user field)... I can place and receive calls from the dialpad in the browser.
But if i use the name "bill" or "bill@avaya.mydomain.com" it doesn't work and instead shows "SIP registration failed, invalid credentials".
The same applies for the Chrome plugin (only one i have tried) for "Avaya Communicator for Web", throws an error "Connection to the phone device has failed".
I can log in to with the user extension and password, but not user@avaya.mydomain.com, exact same thing (interestingly doesnt show a as a logging failure under System Status, whereas entering the username as extension and deliberate wrong pass will throw "Login failed due to incorrect userId/password").
Something weird:
If i go to the apps server and don't specify a port, it shows an error "URI contains invalid FQDN. DNS resolved address does not match the Interface address" yet the bar is green showing the cert is OK.
Yet if i log into the server Centos as root, and ping apps.avaya.mydomain.com, it resolves and pings 127.0.0.1... it is added to /etc/hosts.
Sanity checking the rest of the settings:
I am able to login to One-X portal as the user with just User and password, this is OK.
Certificates are installed and working OK showing green bars, IP Office application server is reachable on apps.avaya.mydomain.com and the Avaya IP Office 500v2 gateway resolves on media.avaya.mydomain.com. Come to think of it, Avaya IP Office may not be able to resolve apps.avaya.mydomain.com currently (due to the DNS server).
Under IP Office -> LAN 1 I have enabled the SIP registrar and for the SIP Domain Name have put avaya.mydomain.com, and SIP Registrar FQDN is media.avaya.mydomain.com. UDP/TCP all on standard ports.
Then under the Linux Avaya Server, WebManagement (on port :7070) i set the WebRTC SIP Server Settings to match those of the IP Office gateway.
Any help or pointers greatly appreciated, also if i open up a support case with Avaya is this something they will entertain?
Thanks in advance.
All the servers are showing green under Application Server Web Control (on port :7071).
I then try the demo login on I am able to login with extension (not a username just the extension, i.e. 1502), and password (in the user field)... I can place and receive calls from the dialpad in the browser.
But if i use the name "bill" or "bill@avaya.mydomain.com" it doesn't work and instead shows "SIP registration failed, invalid credentials".
The same applies for the Chrome plugin (only one i have tried) for "Avaya Communicator for Web", throws an error "Connection to the phone device has failed".
I can log in to with the user extension and password, but not user@avaya.mydomain.com, exact same thing (interestingly doesnt show a as a logging failure under System Status, whereas entering the username as extension and deliberate wrong pass will throw "Login failed due to incorrect userId/password").
Something weird:
If i go to the apps server and don't specify a port, it shows an error "URI contains invalid FQDN. DNS resolved address does not match the Interface address" yet the bar is green showing the cert is OK.
Yet if i log into the server Centos as root, and ping apps.avaya.mydomain.com, it resolves and pings 127.0.0.1... it is added to /etc/hosts.
Sanity checking the rest of the settings:
I am able to login to One-X portal as the user with just User and password, this is OK.
Certificates are installed and working OK showing green bars, IP Office application server is reachable on apps.avaya.mydomain.com and the Avaya IP Office 500v2 gateway resolves on media.avaya.mydomain.com. Come to think of it, Avaya IP Office may not be able to resolve apps.avaya.mydomain.com currently (due to the DNS server).
Under IP Office -> LAN 1 I have enabled the SIP registrar and for the SIP Domain Name have put avaya.mydomain.com, and SIP Registrar FQDN is media.avaya.mydomain.com. UDP/TCP all on standard ports.
Then under the Linux Avaya Server, WebManagement (on port :7070) i set the WebRTC SIP Server Settings to match those of the IP Office gateway.
Any help or pointers greatly appreciated, also if i open up a support case with Avaya is this something they will entertain?
Thanks in advance.