Preferred Mobile App will not connect

[Josh.]

I have set up the preferred One X mobile app for the first time and it has not gone to plan.

I used this guide

http://www.ipofficeassistance.com/setting-up-one-x-portal-for-the-preferred-mobility-application/

and followed it down to a T.

The app works over a VPN using local addresses but not through the FQDN's.

I can ping both of the FQDN's and receive a response but the ports are showing as closed using Zenmap and the 'yougetsignal' Openport tool checker. The customers IT company has said all the correct ports are open on the Cisco ASA and all forwarded to the correct location and they have triple checked this.

Please can someone advise what else I can do to prove this is not a configuration error on my side but due to the ports or their firewall?

Also, are there any links I should be receiving a response from that I can test to see if this is their IT departments fault?

I found the two links below but these were from a guide that shows how to set this up using an SBC but should I still receive a response using my set up?

https://fqdn:8444/rest/my/sip-info

https://fqdn.lab:8444/rest/my/im-info

Thanks in advance,

 

[DaIPOTek]

Only way you can prove it is to bring in your own firewall and show them that it works. Have you had them disable Sip ALG on the ASA? I believe it is required on the ASA to get the mobile app working. Also if you're on R10 you will need to fill in the SIP Domain field on the IPO. That field is not present in the guide you're using since its an R10 addition. Those are the two "gotchas" that I've encountered. Knock on wood, haven't encountered a situation yet where I couldn't get the mobile app working, even with uncooperative IT departments.

 

[Pepp77]

Have you completed the following sections on the IPO/App server

Network Topolgy on the LAN tab that is internet facing (to include the public IP address the FQDN translates)
VoIP tab on the LAN tab to include the domain and/or FQDN (depending on version), SIP Remote Extension Enabled is ticked, remote port is set to the ones opened on the firewall (for example we do not leave it at the default 5060/5061 when we do one-x mobile)
App Server has the XMPP domain name set correctly
Split DNS is configured so both FQDNs translate to the correct IP(s)

However to be fair if it works internally it is almost certainly a firewall issue.

| ACSS SME |

 

[Josh.]

I have checked all of the above and can confirm this is all in place.

The IT are still adamant that they have forwarded all the ports correctly.

The only thing that I can think of that could be causing this is the fact that the IPO is on 9.1.9.0 and the UC module is on 9.1.10.0. Could this be the cause??

Also, I did not mention earlier they are using UC module so if there is anything you can think of there please let me know.

TIA,

 

[DaIPOTek]

Release should match, but I doubt that the 1 service pack difference is causing an issue. Almost guaranteed that they aren't forwarding ports correctly, or they have not disabled SIP ALG.

 

[Josh.]

Ok thank you, I am changing releases so that they are the same now. I will then reboot the UC Module. If that still does not work I will begin to configure a new router.

My only option was to get a router from a high street shop so I bought a ASUS AC3100 DSL AC88U. Does anyone know of any gotchas with this router?

TIA,