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 bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cant login with Avaya Communicator for Web (using SIP user@domain) but OK with extension 1

Status
Not open for further replies.

g18c

Programmer
May 2, 2002
342
AE
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.
 
First - What version are you running?

Second - Use Extension number in the username

Third - You likely have a DNS issue. Does your One-X Portal entries match your LAN1 > VoiP Tab entries? What are your entries for your DNS internally and externally?

ACSS (SME)

 
Thanks for the reply, much appreciated.

It is version 10.0.700 for IP Office and the Avaya server.

How come all the videos (and config guide) showing them logging in with the username (as set on IP Office manager, with the @domain name as per the SIP suffix)? As mentioned it does work when using the extension on the test URL but neither extension nor username@domain work on the Chrome plugin.

The XMMP domain name on One-X portal was set to avaya.mydomain.com, should this be set to the name of the One-X server (apps.avaya.mydomain.com)? You kindly mentioned to make sure One-X XMMP matches IPO500 LAN 1 settings, which ones (as its not a domain name it is a server name, would it then be the FQDN field on the SIP page, i.e. both IPO500 FQDN on LAN page and One-X XMMP should be apps.avaya.mydomain.com)?

On the server i have set DNS entries on the host file, and on the user computers, when pinging by hostname everything is resolving OK (next i will get these added to the DNS server proper by the IT chaps).

Thanks again for the help.
 
Thanks for help @TheSmash, any luck with my clarification on what to set the FQDN to on IPO500 LAN 1 (is it the One-X server hostname, or the IPO500V2 hostname)?

Many thanks in advance.
 
They would all be the same on an SE deployment.
your prsesence server is 1xp server.
Most others are the webrtc gateway/ip office.


A madman with a taste for speed.
 
Thanks for replies, I am running a standalone IPO500V2 with Linux App server, so as i understand and appreciate the replies, that on the IPO LAN 1, i set the FQDN to my Linux application server hostname (and not the IP Office 500V2 host name)?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top