Avaya Communicator and One-X 9.1.12 question

[MBATech173]

So we've got One-X setup and the XMPP configured and it's working fine with the One-X Mobile app. There's a remote user that wants to use the Communicator. Here's where I'm confused. The setup for Communicator mentions that it requires the One-X services. However, when I try to enter the XMPP info for the Communicator server info, it won't connect. It only connects when I enter the IP Office address info. So why does it need the One-X services if I can't connect to it like the mobile app does ? The end-user needs a VPN setup in order for them to use the Communicator. Could someone shed some light on this ?


BTS Tech

 

[derfloh]

Leave the presence Server info empty but enabled. IPO sends the needed information during SIP registration to Communicator. You can see it if you look into sysmon SIP trace.

 

[MBATech173]

derfloh, I never entered anything in the Presence Server field. My real concern is why I'm not able to enter the XMPP address for the Communicator ? It only works on the local network and when I enter the IPO address. Isn't the Communicator Avaya's replacement for the Soft Phones ? So it should work for remote users. How can I make that happen ?

 

[Pepp77]

Contrary to others I always enter the Presence server address.

We have numerous customers on our hosted offering that use communicator and all use it remotely from the IPO (would be hard not to on a hosted platform

So we enter

Server address - customer.voice.telephony.cloud
Server port - customised non default port
Transport Type - TLS (we have a proper SSL certificate installed)
Domain - voice.telephony.cloud
Presence server address - customer.voice.telephony.cloud

On the firewall that the public IP address that this FQDN translates to is setup we NAT through to the IPO the following ports

5222, 5269, 8444, 9443 (TCP)
7600 - 7601 (TCP) - these are the ports we set as the remote ports on the VoIP tab
60101 - 60201 (UDP)- these are the ports we set as the port number range (NAT) on the VoIP tab.

This is on Server Edition - but then it just works.



| ACSS SME |

 

[MBATech173]

Pepp77, thanks for the info. We're not using a Server Edition, just a standard IP500V2 and a Windows Server 2012 for the VM Pro and One-X. Allow to break down what you sent:

Server address - customer.voice.telephony.cloud <--- This is the address of the IP500V2 or the One-X XMPP info ?
Server port - customized non default port <--- will the standard 5061 port for TLS not work ? What other ports would you suggest ? These are opened/assigned in the firewall ?

Transport Type - TLS (we have a proper SSL certificate installed) <-- Is the certificate created in the firewall or the One-X setup ? I've never used them before so I'm not sure where this is done.

Domain - voice.telephony.cloud <---Again, IP500V2 address of One-X XMPP address ?

Presence server address - customer.voice.telephony.cloud <---IP500V2 address of One-X XMPP address ?

 

[Pepp77]

Server address - customer.voice.telephony.cloud <--- This is the address of the IP500V2 or the One-X XMPP info ? - IP500v2

Server port - customized non default port <--- will the standard 5061 port for TLS not work ? What other ports would you suggest ? These are opened/assigned in the firewall ? - Whatever is set as remote ports on the voip tab - i would just not recommend leaving it default

Transport Type - TLS (we have a proper SSL certificate installed) <-- Is the certificate created in the firewall or the One-X setup ? I've never used them before so I'm not sure where this is done. - It's added to the 7070 page of the server edition in our environment, you would need to add it to the SE and the IP500v2 - ours is a *.voice.telephony.cloud certificate so can be used on all equipment

Domain - voice.telephony.cloud <---Again, IP500V2 address of One-X XMPP address ? - This is the FQDN used on the IPO - minus the first part

Presence server address - customer.voice.telephony.cloud <---IP500V2 address of One-X XMPP address ? - This is the FQDN that translates to the One-x server

In your example you would need

ipo.customer.com or equivalent set in the IPO and onex.customer.com or equivalent set in the one-x server
Both to resolve to the public IP address set in the firewall.

| ACSS SME |