OXO and Android 2

[patrick.swinnen]

Ok great. I'm happy you succeeded. But indeed strange that only now in this version the nomadic mode can be activated.

Verstuurd vanaf mijn SM-G920F met Tapatalk

[luca_buratti]

Good morning mr Swinnen

With your help our resellers have found the solution.

Now the mission is use OTC outside my company with public Ip and all the rules to do in the firewall (Nat Stun and so on) that can permit the connection.

I've opened another topic for this

viewtopic.php?f=395&t=25283

For the OTC app there is another spin-off with Bluetooth and the Car ,

I'll open this topic after the connections outside...

If you have any experience on this , your help is very appreciated!

[patrick.swinnen]

via wan you need to put public ip adres of your firewall with indication of a chosen https port in the otcv application And in the oxo not worthy other label "ExthttpsPo" flag you need to set this port in hexcode.
Example: in otcv public field you put https://195.195.195.195:9500
In the oxo not worthy parameter you put hexcode for 9500. And in the firewall you program port forwarding want ip and port to LAN ip address of oxo and port 443.
That should do it

Verstuurd vanaf mijn SM-G920F met Tapatalk

[luca_buratti]

Good Afternoon Mr Swinnen
Thank you very much for Your answer
Now i can make It work with the mobility function outside of my factory
The difficult is to make work SIP (OpenTouch voice over ip) through my Watchguard Firewall...

[cavagnaro]

Sip is not NAT friendly. You need something like a SBC or put oxo directly on Internet, which of course, is not recommended at all

Enviado de meu C6603 usando Tapatalk

[fe80]

Ciao luca_buratti,
Maybe I am wrong, but if I remember correctly OpenTouch VoIP works in your office wifi only and not outside. If you are outside your office, the OCTV app sends an signaling to the public IP:Port of your Watchguard, gets NATted to the OXO and tells the system to do an call to your mobile.

[luca_buratti]

Good Morning Mr. fe80
The OpenTouch App Works with and without SIP
In the second case (without) with the tcp 443 natted when you call someone with the app , the OXO makes the call and call you back (CallBack)
In the first case (with) , when you dial the number, automatically the call go to the destination , for your side is like a skype call
This is what SIP do .
It works with my factory wifi but the hard work is NAT SIP traffic (ALG? or better H323 ALG) .
Cavagnaro talks about SBC ....you talked about something similar here...
viewtopic.php?t=24461

[fe80]

Hi luca_buratti,
If I understood your setup correct, here is no need to NAT the SIP traffic. Within your wifi the OTCV-App can access the OXO directly and without NAT to handle the signaling and RTP.

[luca_buratti]

Yes into the factory with Wifi the SIP connection works but outside no.
Cavaganro talks about SBC for outside connections (how it works?)
Somebody othe use Asterix or 3CX with SIP trunck (how it worsk?) to avoid to handle the SIP with Alcatel
Do you have any idea ?

[fe80]

Hi Luca,
an SBC or ALG is a possible solution, but really not trivial. It may be easier to give the Android phone the possibility to connect to factory lan from outside with some kind of roadwarrior vpn. http://www.watchguard.com/help/docs/wsm ... vpn_c.html