Thales' cellular IoT products business is now part of Telit Cinterion, find out more.

You are here

Problem with OTAP hanging "OtapMsSmsIncomingIndCb" | Telit Cinterion IoT Developer Community

July 27, 2017 - 12:53pm, 2287 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 mode 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.