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

One-X Mobile over local WiFi

Status
Not open for further replies.

yankblan

Vendor
Jun 17, 2010
831
CA
Hey,

Haven't been here or working on IPO for a while, I just need confirmation on a couple of things.

I have a customer who wants to use 1X mobile for Android on IPO 8.1. He only wants to use it internally while on his LAN. I seem to recall that the app, no matter what, goes outside on the Internet, and then back in through the FQDN. I'm pretty sure this question has been asked before, and catching up on my doc, it just states what the requirements are, not alluding to local WiFi at all.

Now I have the IT guy forwarding the DNS to the 1X server internally; but it is not solvable through the WAN. I am positive it will not ever work, the app whether on 4G or WIFI will always go outside and back in.

Can someone confirm this?

ACSS-SME

 
Split DNS so "portal.customer.com" on the Windows DNS inside points to 192.x.x.x and on his webhost for his public domain of "customer.com" he points "portal.customer.com" to whatever public IP he has forwarded to the portal server.

Many firewalls prevent packet hairpinning where you go from the trusted LAN out the firewall and back in.
 
Thanks, but I know how to configure it to go out and back in. The problem is the IT guy does not want to have anything come in through WAN, and I'm pretty sure the app is designed to go in first through WAN, either on 4G/public WiFi or by hairpinning if on local WiFi.

ACSS-SME

 
If your server name in the app is the fqdn and you're on internal wifi and internal DNS resolves the FQDN to your internal portal IP, I don't think the WAN would be involved at all.
 
From the doc:

Network requirements
The Avaya one-x Mobile application must be able to connect from the Internet to the one-X
Portal
and to the IP Office system, using either using a 3G network or an external WiFi service.
Your network setup must support this capability.
If the one-X Portal and IP Office will be deployed behind a router or firewall, the following TCP
ports need to be allowed access through the firewall:
• ports 5222 and 8444 must be open in order for the one-X Mobile application to
communicate with the one-X Portal server; port 5222 is for XMPP traffic and port 8444 is
for bootstrap REST API call traffic
• port 5269 needs to be open for the one-X Portal server to be able to federate with another
XMPP server outside the company firewall
In addition, an FQDN that is resolvable over the Internet must be assigned to the public IP
address of the router that is fronting the one-X Portal. That router must be configured to forward
packets destined to ports 5222, 5269 and 8444 to the one-X Portal; you can achieve this by
creating port forwarding rules on the router.
You must ensure that your network meets these requirements before you deploy the one-X
Mobile application.


That is why I'm convinced this app is not supported over local wifi; unless you have a VWLAN that resolves through another router, to simulate an external connection. I mean, you gotta love trouble just to avoid the Big Bad Internet that bad.

ACSS-SME

 
It works well even if only used in internal WLAN. Just enter the 1X server IP address as XMPP domain and enter the same IP address as domain in the app.
 
Yeah, I think when you saw "external wifi service" that means the wifi at starbucks, not the wifi at your customer's site.

Those requirements are for outside access. If fqdn resolves to the private IP inside, you'll be fine.
 
doesn't the system need to be on minimum v9 for this to work?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top