Hi Wilfried and Jan,
>
> Some wavecoms seem to handle cnma not in an apropriate way, if there
> isn't some more vodoo magic. i get an "ERROR" back in that case from
some
> of them. I didn't have the time to look into this closer yet.
> I think the new driver behaves a bit different...
> The first solution is not to enable direct routing to the te by
> initializing the modem by at+cnmi....
as Jan suggested I switched on the access.log. It seems as the modem
receives the SMS several times from the provider and that's why serves
every SMS as a new one (correctly). In my opinion the reason for this is
that the Wavecom does not answer to the mobile network correctly that
the SMS was (already) received - so the provider tries to deliver the
SMS to the mobile device (my Wavecom of course) again after a few
minutes. I think this is going in yours (Wilfrieds) direction, and it
makes sense to me to see this as the reason for the re-sending of the SMS.
I just read a little bit about CNMA (which is obviously responsible for
sending ACK to the network when a message was received successfully, if
I got it right).
> The first solution is not to enable direct routing to the te by
> initializing the modem by at+cnmi....
How can this be done?
Perhaps with something like this:
"init-string = "AT+CNMI=1,2,0,1,1""
which was taken from the Siemens modem in modems.conf.
Perhaps someone can point me to the right syntax here. Are there any
default settings that might work with my Wavecom?
(As a fallback I also own a Siemens TC35, I hope this can cope with the
new driver(s) in kannel 1.4.0. Next week I fly to Arabia and it should
work with one modem (Wavecom or Siemens) reliably...)
greetz from Bonn/Germany,
Lars-Hendrik
