Presence 10.0.0.3.0 Build 5 3

[NewNic]

New to Making Presence work:
Using communicator, able to log in for phone function's, however getting error unable to connect to Onex Portal,

I thought this should work outa the box?

Communicator is set
Server address = IPO address
Port = 5060
Domain - IPO address
Presence Server = Blank

What am I missing? Thanks for any input

 

[teletechman]

you kind of answered your own question, no presence server address, this should be the one-x server address.
Mike

 

[bob10752000]

teletechman is wrong as you dont need to populate the PS address in the Communicator client as it gets this information from the 1XP server when you login (look at the sysmon traces). In R10 they changed some settings and I bet if you go into the Administration side of 1XP go to configuration, then go to Host Domain Name and make sure it is set to the internal IP address or FQDN of the 1XP server (as well as making sureIM Presence/XMPP DN is set to this as well) . It took me ages to work out what they had changed but finally got it in the end

ACSS (SME)
APSS (SME)

 

[Okkie26]

check the log file.

C:\Users\ohartman\AppData\Roaming\Avaya\Avaya Communicator\Communicator Logs\AvayaOnexPortalClientLog.log

Search for error containing something like The remote name could not be resolved: 'uc-module'

Then add the DNS 'uc-module' in the host file pointing to the one-x portal IP adress.

C:\Windows\System32\drivers\etc\hosts

Then try again.

 

[NewNic]

Thanks for the response's, should be able to look at this afternoon

 

[bob10752000]

If you use the solution Okkie26 has suggested every PC you install this on will need this fudge in order for it to work as it cant resolve the name in the "Host Domain Name" field via DNS.

ACSS (SME)
APSS (SME)

 

[Okkie26]

of course, when it works you need to change the domain name in de One-X portal configuration settings to the IP Address of the Portal.

 

[NewNic]

Thanks, Bob, okkie

Im staging it in the office so I just modified the host file. Gives me a chance to see what it does.

 

[Okkie26]

Note that uc-module could have a different name in your case..

 

[tomtom9]

Hi guys,

We are having similar issue - and we managed to figure out that there was a problem with DNS not resolving. Our situation is slightly different though:
Current setup where we are unable to see/set presence but we are able to log on:

Server address = AVAYA.DOMAIN.COM
Port = 5060
Domain = DOMAIN.COM
Presence Server = AVAYA.DOMAIN.COM

Where AVAYA.DOMAIN.COM = Internal IP of the server ie 10.110.110.110 that is forwarded internally and externally to the server via Local / External DNS.

Lets say the server name is: AVAYAPhoneServer and it is also on the 10.110.110.110 IP

What we see in the log is: NameResolutionFailureMessage: The remote name could not be resolved: 'AVAYAPhoneServer'

When we add A pointer on internal DNS to point AVAYAPhoneServer to 10.110.110.110, we are not able to log on at all to the Communicator.

Any ideas?