Thanasis, I wouldn't dream of re-sending only the missing parts :-).
Anyway, the solution was right in front of my eyes, but ignored it so
far. SmsServer does not set the SMSC number of the modem (or I could
not find how to do it easily). So I added the following code in
SerialModem.java
if (! "".equals(getProperties().getProperty(propName +
"smsc"))){
org.smslib.modem.SerialModemGateway mygate =
(org.smslib.modem.SerialModemGateway) getGateway();
mygate.setSmscNumber(getProperties().getProperty(propName +
"smsc"));
}
And, as it is clearly stated in the previous messages of this thread,
setting the SMSC helps a lot. I do not get CMS error 500 anymore.
I still get timeouts every now and then, but they do not seem to cause
any further implications. I think I will not have to check if
markMessage() has been called again.
On Sep 8, 7:59 am, Thanasis <[email protected]> wrote:
> Hmm... If this happens during a part of a multipart message, it gets
> really complicated... A big message is breaked up in parts on the fly,
> so if one part throws errors it would be extremely difficult to
> identify it and retry just that. SMSLib will retry the transmition of
> the entire message again.
>
> The thing that the markMessage() is not called is what worries me!
> I'll try to reproduce it here and get back to you.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"SMSLib for Java User Group" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/smslib?hl=en
-~----------~----~----~----~------~----~------~--~---
