Avaya Communicator for Web R11 using Chrome

[Mikel82]

I have a new installation of the following. IPO V2 with application server and J169 phones. Communicator for web will only be used on the local network.

Issue is that after I login to the Communicator for Web I never get a SIP registration with the IPO. So I cannot control the desk phone or the softphone. It only displays "connecting" at the top of the Communicator for Web interface after I log in.

I can see the extension as an unregistered "SIP WebRTC" extension type with the IP address of the application server in SSA.

I created a self signed certificate in the application server and installed that in Chrome.

Since the Communicator for Web will only be used on the local network I did not program any Domain name information in the IP office I am just using the LAN IP address.

The WebRTC Gateway and Web Client services are running on the application server.

Each user has a power user license and all boxes are checked.

I am missing something that will not let SIP registration take place for the Communicator for Web.

If your not going to it right don't bother doing it at all!

 

[critchey]

The J169s register? It sounds like SIP registrar is not enabled but if they register it wouldn't be that.

The truth is just an excuse for lack of imagination.

 

[Mikel82]

Yes, the J169 phones register and are working just fine. Both are on the same network.

Thanks for the response.

If your not going to it right don't bother doing it at all!

 

[critchey]

I would suggest running a monitor trace and see what is happening. Hard to tell with the information given.

The truth is just an excuse for lack of imagination.

 

[tecphonelady]

How are you populating the credential fields in the Avaya Communicator for Web login screen?

Try:
Use explicit credentials
User Default
ip address of app server
ip address of app server
Name comes from the Name on the User tab
Password comes from the User tab, just under Name

The name & password are the same credentials you use to log into One-X Portal. Can you log in there successfully? Also, for me personally, I have to be logged into One-X as a user to be able to get Communicator to work. This is with R11 & an App server.

Ann

TelecomEx.com

 

[Bucky101]

You can get logs by opening ACW as its own window and pressing F12 in chrome

If you browse the IPO FQDN or app server FQDN do they have the certificate error message? Have you added root to trusted roots? User has power user? Is one-x portal and WebRTC services up? Have you logged into to one-x and initialized it?

I would suggest as well as phoneladys suggestions
Use explicit credentials
User Default
fqdn of appserver or avayaapp@company.com
fqdn of appserver or avayaapp@company.com
username@sipdomain or bob@company.com
Password comes from the User tab, just under Name

 

[Mikel82]

Issue has been resolved everything is now working. Issue was One-X portal. I had logged in as the administrator to set things up but I had not logged in as a user because the customer was not planning to use One-X. Once I stopped and started the One-X services. I was able to connect to a phone and control it.

I would like to think everyone who helped. I would really like to thank tecphonelady. I had all the settings set correctly but her mention of One-X portal got me thinking. I was not aware that the Communicator for Web used One-X for login. That is when I tried logging to One-X as a user. I was notable to login and that is when I stopped & started the services.

Thanks everyone.

If your not going to it right don't bother doing it at all!

 

[critchey]

If you can leave pink for the helpful post please, sounds like tecphonelady's in this case, that would be appreciated.

The truth is just an excuse for lack of imagination.