Hi guys,
I'm on this new stuff (no training) and documentation is just being shared...so...almost blind.
I tried to make this work, created the user, the Imei.xml file configured but can't access it from the WAN or LAN...no matter what I do
I found that the URL is:
https://opentouch/dm_authent_app/Android/<imei>.xml
I register this address on the Android MyIC client
https://opentouch/dm_authent_app/Android/ (the equivalent to http://ics/DM on ICS) but it can't retrieve the configuration file. I'm testing on WiFi only for the moment. Certificate is accepted meaning I reach the server but can't retrieve the XML config file. Do you know which path I must set up on it?
Thanks!
Android client
-
cavagnaro
Re: Android client
Ok...some progress here...
after doing some packet capture I found that this piece of Sh*t actually search for a <imei>_Public.xml file...so renaming it downloads the file (WTF!!?) and now it prompts for user/password...
And got stuck again...
I guess this system is a new headache ahead and many hours to expend with it...I hate ALU
after doing some packet capture I found that this piece of Sh*t actually search for a <imei>_Public.xml file...so renaming it downloads the file (WTF!!?) and now it prompts for user/password...
And got stuck again...
I guess this system is a new headache ahead and many hours to expend with it...I hate ALU
-
corwin
Re: Android client
Hi
There is a price for the security
I assume you aggree that no one will accept a plug and play of end user personnal device as a prooof of security (i mean only allowed physical device should get sip credential or web access to unified communication system and this is done thanks to certificats)
If you are not interested by security
You should locate à file on opentouch : something like ...rewriterule...and rename it then restart ot
It is used for redirection of https flow to à device authentification where certificate are checked
And of course, Anyone looking at your mobile box (where is written your imei) or at the vhe stickers ( where is written your Mac address) will gain access to config file and if smart enough this person can place calll on your behalf and credit
Finally
You have 2 android solution
One for OT user ( icm) and one for oxe user ( same android binary for oxe user using an ics or an opentouch for thé myIC mobile services)
I hope you do not confuse both deployment
Maybe you install my android for icm user which look on a file publicimei, and you declare myIC android for oxe user which does not use the publicimei
There is a price for the security
I assume you aggree that no one will accept a plug and play of end user personnal device as a prooof of security (i mean only allowed physical device should get sip credential or web access to unified communication system and this is done thanks to certificats)
If you are not interested by security
You should locate à file on opentouch : something like ...rewriterule...and rename it then restart ot
It is used for redirection of https flow to à device authentification where certificate are checked
And of course, Anyone looking at your mobile box (where is written your imei) or at the vhe stickers ( where is written your Mac address) will gain access to config file and if smart enough this person can place calll on your behalf and credit
Finally
You have 2 android solution
One for OT user ( icm) and one for oxe user ( same android binary for oxe user using an ics or an opentouch for thé myIC mobile services)
I hope you do not confuse both deployment
Maybe you install my android for icm user which look on a file publicimei, and you declare myIC android for oxe user which does not use the publicimei
-
cavagnaro
Re: Android client
I think you are confusing my posts...
I'm ICS certified and do understand the IMEI idea...what I don't get is the OpenT configuration...it is messy
How does a <imei>_Public.xml file is generated? I have tried all and can't do it in that way.
What do you mean by 2 Android clients? I know and have configured/installed on other installations the ICS only but supposedly for OpenT there is another cliente v4...where does it states that there are 2 clients for same platform? Can't find it on any installation guide.
When trying to create an OpenT user I get an error about configuring ReverseProxy...but I still don't need one for a WiFi network...and where does this is configured?
I'm ICS certified and do understand the IMEI idea...what I don't get is the OpenT configuration...it is messy
How does a <imei>_Public.xml file is generated? I have tried all and can't do it in that way.
What do you mean by 2 Android clients? I know and have configured/installed on other installations the ICS only but supposedly for OpenT there is another cliente v4...where does it states that there are 2 clients for same platform? Can't find it on any installation guide.
When trying to create an OpenT user I get an error about configuring ReverseProxy...but I still don't need one for a WiFi network...and where does this is configured?
-
corwin
Re: Android client
Hi
Thanks for your additional input
You have at your disposal the admin guide and technical communication
Anyway, there is some logic in the mic android setup
The solution is an off site mobility
Meaning working when end user is out of he company
It has also a wifi connectivity for only web service
Wifi can be used at home, .... And finally also in the company
In addition, opentouch is not exposed to Internet, a reverse proxy in the DMZ relay http/ https request from Internet to the company LAN
Hence it has been put as mandatory to give reverse proxy URL in 8770 ot configuration ( topology branch of the config tree)
If no real reverse proxy is setup, example of a lab setup, reverse proxy URL must use ot FQDN
The IMEI file is created once an android device is associated to a user, no rename of file is needed
The mic android solution for opentouch concerns opentouch users ( the one created on icm/ sip server). It is based on mic android 4.1.2.0.29.2 and ot 1.1
Create a user in 8770
Then, create associate an android device to such user ( the IMEI is used for config file name) hence the android loaded with mic mobile is able to get its parameter file from OpenTouch.
We have kept also the solution of myic for oxe user ( oxe device in twin set with remote extension) it is based on myic 3.x client( the same as the one used for ics)
In such case
On oxe create device oxe and remote extension and speed dial number
On ot look at the synchronized oxe device, they must have been synchronized
Create a user ( oxe type) in ot and in contact tab of such user put the oxe device, the remote extension device
and also a myic android device ( created with IMEI)
Of course it is recommended to avoid deploying heterogeneous solution ( android for two kind of ot user: icm and oxe) and to setup only one of the two solution
Hope the quick overview here will help you.
Thanks for your additional input
You have at your disposal the admin guide and technical communication
Anyway, there is some logic in the mic android setup
The solution is an off site mobility
Meaning working when end user is out of he company
It has also a wifi connectivity for only web service
Wifi can be used at home, .... And finally also in the company
In addition, opentouch is not exposed to Internet, a reverse proxy in the DMZ relay http/ https request from Internet to the company LAN
Hence it has been put as mandatory to give reverse proxy URL in 8770 ot configuration ( topology branch of the config tree)
If no real reverse proxy is setup, example of a lab setup, reverse proxy URL must use ot FQDN
The IMEI file is created once an android device is associated to a user, no rename of file is needed
The mic android solution for opentouch concerns opentouch users ( the one created on icm/ sip server). It is based on mic android 4.1.2.0.29.2 and ot 1.1
Create a user in 8770
Then, create associate an android device to such user ( the IMEI is used for config file name) hence the android loaded with mic mobile is able to get its parameter file from OpenTouch.
We have kept also the solution of myic for oxe user ( oxe device in twin set with remote extension) it is based on myic 3.x client( the same as the one used for ics)
In such case
On oxe create device oxe and remote extension and speed dial number
On ot look at the synchronized oxe device, they must have been synchronized
Create a user ( oxe type) in ot and in contact tab of such user put the oxe device, the remote extension device
and also a myic android device ( created with IMEI)
Of course it is recommended to avoid deploying heterogeneous solution ( android for two kind of ot user: icm and oxe) and to setup only one of the two solution
Hope the quick overview here will help you.
-
cavagnaro
Re: Android client
Ok, now got it working, however it is funny what you mention about not mixing configurations as it is one of the point of sales commercial guys refernce...that you can choose or either one platform user or the other...but seems extremely complicated and not very user friendly actually.
Thanks for the input
Thanks for the input
-
baalynt
Re: Android client
Hello!
I tried to make it step-by step.
The remote extension is made on oxe.
When I want to associate to user the android mobile device, the error message is this:
"Could not assiciate device (IMEI number) with the user id=4851, cn=usersenddevices, subnetwork....blabla networknumber=blabla..
due terror from OT: Reverse Proxy must be configured for mobile devices"
In the OT configuration Topology --> Reverse proxy --> Display name: The FQDN is written
Application Server: appServer_otdemo.hulab1.nextiraone.eu
What is wrong with the config?
BR, Balint
I tried to make it step-by step.
The remote extension is made on oxe.
When I want to associate to user the android mobile device, the error message is this:
"Could not assiciate device (IMEI number) with the user id=4851, cn=usersenddevices, subnetwork....blabla networknumber=blabla..
due terror from OT: Reverse Proxy must be configured for mobile devices"
In the OT configuration Topology --> Reverse proxy --> Display name: The FQDN is written
Application Server: appServer_otdemo.hulab1.nextiraone.eu
What is wrong with the config?
BR, Balint
-
corwin
Re: Android client
Please, provide the screenshot of the reverse proxy config (8770 OT config)
May be some field is incorrect
Are you using external RP
Or using direct access to OT from wifi entreprise, in such case RP setup is fil king OT FQDN in the URL of each services access
May be some field is incorrect
Are you using external RP
Or using direct access to OT from wifi entreprise, in such case RP setup is fil king OT FQDN in the URL of each services access
-
corwin
Re: Android client
In addition to the app server name
You need to put public URL of each services
Https://otfqdn. If no real RP
If real RP , you put here the public URL
You need to put public URL of each services
Https://otfqdn. If no real RP
If real RP , you put here the public URL
