Problem with OTAP hanging "OtapMsSmsIncomingIndCb" | Telit Cinterion IoT Developer Community
July 27, 2017 - 12:53pm, 1961 views
Hello everyone,
I'm trying to trigger an OTAP update of the midlet of an application for modules that are physically unreachable.
I'm testing the procedure inhouse with a module where I can see the log from a serial connection.
The sms is sent with the correct class and PID, and in the module I see this happening:
^SYSLOADING
^SYSSTART
+PBREADY
AT^SCFG="Trace/Syslog/OTAP","1"
OTAP.OUT STARTED
[OTAP] OtapMsSmsIncomingIndCb, SMS coding=2
And it stops there.
Why isn't the full process starting? What does exactly mean that message, then?
I'm creating the SMS with the tool PDU **** SMS generator, with the content:
OTAP_IMPNG\n
APNORNUM:internet.access.nl\n
JADURL:http://www.myserver.com/MyNewJad.jad\n
APPDIR:a:\n
BEARER:gprs\n
START:install\n
Anyone has a clue of what can be missing here?
Thanks.
Hi Antonio,
to eliminate OTAP SMS influence please please try to exactly follow such steps to do OTAP:
Set one of the COM-ports to OTAP tracing (send at^scfg="trace/syslog/otap","1" )
In the other COM-port:
To clear all OTAP parameters send:
AT^SJOTAP=,,,,,,,,,,,,
To set required parameters send:
AT^SJOTAP=,"http://78.8.146.92/otap/HelloWorld.jad","a:/","","","gprs","internet",,,,"http://78.8.146.92:7500/otap/notify.php","on","off"
To start OTAP procedure send:
AT^SJOTAP
On this address you can check results:
http://78.8.146.92:7500/otap/results.html
Please tell me whether this test is successful for you.
If yes this would mean that your OTAP SMS is wrong.
Best regards
Lukasz
Dear Lukasz,
Thanks for your message.
I could not try fully your method, cause I work with modules that only have a serial port available.
But clearing the otap parameters did help to solve the issue.
It might be a similar problem that the one you pointed out in the post:
https://iot-developer.thalesgroup.com/threads/bgs5-unreachable-after-spow0
Best regards.