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

Avaya Communicator, R9.1 and Presence

Status
Not open for further replies.

JayNEC

IS-IT--Management
Jun 5, 2002
942
US
So, what's the trick to getting this running? I've got my FQDN's and XMPP domain set, I can login with Communicator but I always get "Unable to connect to OneX Portal server Presence and IM will be unavailable". I can login to the OneX portal just fine.

What am I missing here? TLS didn't make any difference either.

New England Communications
 
Heard you do not need to input IP address for presence server when connected to IP Office. I take it its not supported.
Don't have the doc with me at the moment.
 
One of the things that changed in 9.1 without much notice is that the IP Office system no longer has a default XMPP group containing all users created by default. XMPP groups are needed to control who can share presence with each other so check that.

Stuck in a never ending cycle of file copying.
 
I am having the same issue, so I'm curious to find out as well...
 
Does your computer trust the certificate used by onex portal?
 
under the One-X portal settings, under Security, there is no certificate, there is an option to import...

So does One-x not come with a self signed certificate?
 
It does. But the self signed cert is usually not trusted by your computer and so it is not trusted by Communicator.
 
how can I get my pc to trust it? I know when I logged in One-X Portal I can add the exception in Firefox and ignore it next time, but nothing like that ever pops up with the Communicator.
 
i tried exporting it from firefox and installing it from my desktop, but when I try to login it still says the certificate has not been installed.
 
You might need to install it into another store other than the default. Try trusted root CA

New England Communications
 
tried installing it in a couple of different stores and it didnt seem to make a difference. As soon as I click on TLS in settings and click ok, a box pops up where you login and it says there is no certificate. Where is the communicator looking for the cert at?
 
You have to create a new certificate for 1XP with a CA. That can be a Server Edition of Application Server or another CA. You have to export the public key of that CA and put it on your computer in the trusted CA store.

You don't have to trust the cert itself but the CA that created it.
 
So I'm not really a IT wizard... I tried googling some of that and getting a lot. Is there any way you could provide steps on how to do it or an article that you might could point me to?
 
I should note, I am not running server edition, just a 500v2 with one-x server on the side
 
Have a look at TechnicalBulletin175. It describes the steps.
 
Certificate is an extra. It does work without too. Just on port 5060 and not 5061.
But I understand, you can logon but there is no presence, right?

There are two differend versions around at the moment as 'AVAYA Communicator' is used with IPO and ACM. They look almost identical, but are not. In addition, don't let you confuse by 'AVAYA One-X Communicator' which is only for ACM...

The one for IP Office is version 2.0 while the one for ACM has 2.1
Now 2.1 is not just newer, it's not 100% IPO compatible. You can call, but there is no One-X integration.
 
Had the same issue.
As said by Tinos, DO NOT enter presence server
 
Any update about this?

Windows Server 2012 R2, 1XP installed with UAC off, Using Communicator 2.0.33. Web Login and Control of a 9608 work fine!. In 1XP Admin all green....

Obviously it is of eminent relevance, that I this, what you celeprate, not optimally effective assume, since the integrate of you in the communicative system as code related terms with me no explosive associations in mental-empirical reproduction process of the mind.
 
@Dirk
Do you have a certificate issue in Communicator or is presence server not available? Look at SIP messages within SysMon during the registration of communicator. IPO sends many information inside of a SIP message to Communicator. One of the is the onex_server address that is used as presence server regardless of what you enter manually. If it contains the wrong IP address or FQDN Communicator will not be able to connect.
 
Pres. Not available.

In the XMPP Domain was the Hostname from the Server. Changed to the ServerIP. Restart Service but is not better. The right IP will be sign. over SIP.

Will be the Server 2012 >R2< the problem? I think not?

Obviously it is of eminent relevance, that I this, what you celeprate, not optimally effective assume, since the integrate of you in the communicative system as code related terms with me no explosive associations in mental-empirical reproduction process of the mind.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top