Unable to set UserAgent (EHS6) - urgent | Telit Cinterion IoT Developer Community
September 29, 2017 - 4:05pm, 3508 views
Hello,
I use a EHS6 modem to "get" data from our http servers.
Our devices are recognized by the User Agent, so, I set in the EHS6 memory, as URI, method, APN and so.
We had a very similary application with BGS2 (working fine).
After nearly one day searching, we are stucked with the ESH6 :
Our Apache server always see the "User Agent" as "EHS6/357042068469734 Profile/IMP-NG Configuration/CLDC-1.1"
Nevertheless, the AT^SISS? command tells that the configuration is OK (see below).
URL is opened correctly, as data read.
Do I miss something ?
Is there any reasons why the UserAgent may not be set or transmitted ?
The problem occurs on our device using a EHS6, and the Gemalto development kit fitted with a EHS8.
Thanks a lot !!
Pascal
AT^SISS?
^SISS?
^SISS: 0,"srvType",""
^SISS: 1,"srvType",""
^SISS: 2,"srvType",""
^SISS: 3,"srvType",""
^SISS: 4,"srvType","Http"
^SISS: 4,"conId","0"
^SISS: 4,"address","http://my.url.com/data"
^SISS: 4,"tcpMR","10"
^SISS: 4,"tcpOT","6000"
^SISS: 4,"cmd","get"
^SISS: 4,"hcUserAgent","DeviceV10/12345678"
^SISS: 5,"srvType",""
^SISS: 6,"srvType",""
^SISS: 7,"srvType",""
^SISS: 8,"srvType",""
^SISS: 9,"srvType",""
OK
AT^SISO=4
^SISO=4
OK
^SIS: 4,0,2200,"Http my.url.com:80"
^SISR: 4,1
ATI1
I1
Cinterion
EHS8
REVISION 03.001
A-REVISION 00.000.14
OK
PS : Accessing the URI with Firefox and the Firefox UserAgent modified works perfectly.
Hello,
I've done the same test with the latest EHS6 REVISION 03.001 A-REVISION 00.000.51 and http://httpbin.org/get.
It's working.
Please update the firmware and try.
Best regards,
Bartłomiej
Hello,
Thanks for the httpbin tip, this will help.
Unfortunately, our EHS6 firmware upgrade possibility was not taken in account when desgning the board.
For the EHS8 developement, I'll try to update it.
Additionnaly, if confirmed, such bug was not documented. And if newly discovered, a really sad story for our projet.
Pascal
PS : With EHS8, not updated, and httpbin, confirmation that the user agent is "User-Agent": "EHS8/357044060137020 Profile/IMP-NG Configuration/CLDC-1.1"
Hello,
Currently I can't see any workaround for this besides firmware update or using some other field if possible - adding User-Agent to hcProp didn't work.
Do you already have devices in a field or assembled or modules bought? Maybe there's still some way to update the modules or use current firmware for productinon.
I've just seen that this was aslo reported to our support line. Maybe they will provide some way for update.
Regards,
Bartłomiej
Hello,
Our 20 mockups have EHS6 with this reply : ATI1 Cinterion EHS6 REVISION 03.001 A-REVISION 00.000.31
Our 200 preseries have the same.
So we have ~220 units to reprogramme with modem soldered on our board.
Our EMS shall have in stock 3000 EHS6 with unknow version, not soldered. Purshase order is from spring or summer 2017. As you proposed, we have to find a way for this stock.
I understood with Christophe, our local support, that the version shall be 0.51.
Just for information, I really need confirmation that :
- User Agent bug described above is confirmed on your side with the firmware we have. Else, I may made a mistake in my command sequence, and I will correct it
- Is this bug known to be resolved with version 0.51 ?
I may confirm this if I can upgrade my EHS8 development kit. Where can I find the appropriate firmware and software tools ?
Best regards,
Pascal
Hello,
I have checked the EHS6 REVISION 03.001 A-REVISION 00.000.31 and the result is the same as for A-REVISION 00.000.14.
I have previosly tested with A-REVISION 00.000.51 and it was working correctly.
T hink that from the forum perspective everything is clear now and you need to further talk with your local Gemalto technical person or distributor about updating the modules that you already have.
I will send you the software so you could try with your EHS8 module. The update procedure is very easy - you only need a PC and USB or serial interface.
As for the workaround - there is some way - you'd need to use bare socket instead of http and send the http header manually.
Best regards,
Bartłomiej
Thanks.
Just for update : I agree, upgrade of the EHS8 resolve the issue (no change to AT commands sequence).
I guess that it will be the same on EHS6. Now, we have to manage manufacturing stock issue.
Pascal