Dont use ME - try with just "SM" and see what happens...
On 22 Μαρ 2013, at 18:14, Ala via SMSLib Discussion Group
<smslib+noreply-apn2wqc48s1aoea5gss3te_zvx3a_xtwgx_81wascj1gkk...@googlegroups.com>
wrote:
> Thanisis, please help. You are right, removing the SR takes care of the
> error. But on a separate note, I am getting no inbound messages (even if SR
> location is included). Oddly enough it did work before (as you see in
> initial log with or without the SR related error I was getting something).
> So now it looks like it is triggering the InboundMessage event, but it does
> not get processed or it is empty. I hope you can shed more light on this or
> give me some clues to troubleshoot.
>
> Now I am getting this:
>
> 85616 2013-03-22 09:02:47,446 [KeepAlive [modem.com1]] DEBUG
> org.smslib.thread
> ng.AServiceThread - Running...
> 85616 2013-03-22 09:02:47,446 [KeepAlive [modem.com1]] DEBUG
> org.smslib.modem.
> ModemDriver - GTW: modem.com1: SEND :AT(cr)
> 85616 2013-03-22 09:02:47,446 [KeepAlive [modem.com1]] DEBUG
> org.smslib.modem.
> ModemDriver - GTW: modem.com1: BUFFER: +CMTI: "ME",0
> 85616 2013-03-22 09:02:47,446 [KeepAlive [modem.com1]] DEBUG
> org.smslib.modem.
> ModemDriver$AsyncNotifier - GTW: modem.com1: Storing AsyncEvent: Event:
> INBOUN
> MESSAGE / Response: +CMTI: "ME",0
> 85616 2013-03-22 09:02:47,446 [SMSLib-AsyncNotifier : modem.com1] DEBUG
> org.sm
> lib.modem.AModemDriver$AsyncNotifier - GTW: modem.com1: Processing
> AsyncEvent:
> Event: INBOUNDMESSAGE / Response: +CMTI: "ME",0
> 85616 2013-03-22 09:02:47,446 [SMSLib-AsyncNotifier : modem.com1] DEBUG
> org.sm
> lib.modem.AModemDriver$AsyncNotifier - GTW: modem.com1: Inbound message
> detect
> d!
> 85694 2013-03-22 09:02:47,524 [KeepAlive [modem.com1]] DEBUG
> org.smslib.modem.
> ModemDriver - GTW: modem.com1: BUFFER: OK
> 85694 2013-03-22 09:02:47,524 [KeepAlive [modem.com1]] DEBUG
> org.smslib.modem.
> ModemDriver - GTW: modem.com1: RECV :OK(cr)
> 85694 2013-03-22 09:02:47,524 [SMSLib-AsyncMessageProcessor : modem.com1]
> DEBU
> org.smslib.modem.AModemDriver - GTW: modem.com1: SEND :AT+CPMS="ME"(cr)
> 85897 2013-03-22 09:02:47,727 [SMSLib-AsyncMessageProcessor : modem.com1]
> DEBU
> org.smslib.modem.AModemDriver - GTW: modem.com1: BUFFER: +CPMS:
> 0,100,0,30,0,
> OK
> 85897 2013-03-22 09:02:47,727 [SMSLib-AsyncMessageProcessor : modem.com1]
> DEBU
> org.smslib.modem.AModemDriver - GTW: modem.com1: RECV :+CPMS:
> 0,100,0,30,0,10
> (cr)OK(cr)
> 85897 2013-03-22 09:02:47,727 [SMSLib-AsyncMessageProcessor : modem.com1]
> DEBU
> org.smslib.modem.AModemDriver - GTW: modem.com1: SEND :AT+CMGL=4(cr)
> 86100 2013-03-22 09:02:47,930 [SMSLib-AsyncMessageProcessor : modem.com1]
> DEBU
> org.smslib.modem.AModemDriver - GTW: modem.com1: BUFFER: OK
> 86100 2013-03-22 09:02:47,930 [SMSLib-AsyncMessageProcessor : modem.com1]
> DEBU
> org.smslib.modem.AModemDriver - GTW: modem.com1: RECV :OK(cr)
> 86100 2013-03-22 09:02:47,930 [SMSLib-AsyncMessageProcessor : modem.com1]
> DEBU
> org.smslib.modem.AModemDriver - GTW: modem.com1: SEND :AT+CPMS="SM"(cr)
> 86303 2013-03-22 09:02:48,133 [SMSLib-AsyncMessageProcessor : modem.com1]
> DEBU
> org.smslib.modem.AModemDriver - GTW: modem.com1: BUFFER: +CPMS:
> 0,30,0,30,0,1
> OK
> 86303 2013-03-22 09:02:48,133 [SMSLib-AsyncMessageProcessor : modem.com1]
> DEBU
> org.smslib.modem.AModemDriver - GTW: modem.com1: RECV :+CPMS:
> 0,30,0,30,0,100
> cr)OK(cr)
> 86303 2013-03-22 09:02:48,133 [SMSLib-AsyncMessageProcessor : modem.com1]
> DEBU
> org.smslib.modem.AModemDriver - GTW: modem.com1: SEND :AT+CMGL=4(cr)
> 86505 2013-03-22 09:02:48,335 [SMSLib-AsyncMessageProcessor : modem.com1]
> DEBU
> org.smslib.modem.AModemDriver - GTW: modem.com1: BUFFER: OK
> 86505 2013-03-22 09:02:48,335 [SMSLib-AsyncMessageProcessor : modem.com1]
> DEBU
> org.smslib.modem.AModemDriver - GTW: modem.com1: RECV :OK(cr)
> 86505 2013-03-22 09:02:48,335 [SMSLib-AsyncMessageProcessor : modem.com1]
> DEBU
> org.smslib.modem.ModemGateway - GTW: modem.com1: CheckMpMsgList(): MAINLIST:
>
> 89735 2013-03-22 09:02:51,565 [QueueManager [modem.com1]] DEBUG
> org.smslib.thr
> ading.AServiceThread - Running...
> 90203 2013-03-22 09:02:52,033 [WatchDog] DEBUG
> org.smslib.threading.AServiceTh
> ead - Running...
> 90593 2013-03-22 09:02:52,423 [CNMIEmulatorProcessor [modem.com1]] DEBUG
> org.s
> slib.threading.AServiceThread - ** disabled **
> 94743 2013-03-22 09:02:56,573 [QueueManager [modem.com1]] DEBUG
> org.smslib.thr
> ading.AServiceThread - Running...
> 99750 2013-03-22 09:03:01,580 [QueueManager [modem.com1]] DEBUG
> org.smslib.thr
> ading.AServiceThread - Running...
>
> Regards,
> Ala
>
> On Thursday, March 21, 2013 11:01:48 AM UTC-7, Ala wrote:
>>
>> I use a ZTE M61 modem and Huawei E560 modem and both having issues with
>> inbound messages (using the .Net SMSLIB 3.5.2 and 3.5.3). I used a Motorola
>> DROIDX phone which works fine (but the phone will split long messages and I
>> don’t want that)
>>
>> Using either Modem, I am unable to receive Inbound messages. I have seen
>> other posts with similar issue but no resolution.
>>
>> If I do not set the memory location (or have SR in it) I get the following
>> error:
>>
>> Exception in thread "SMSLib-AsyncMessageProcessor : modem.com1"
>> java.lang.String IndexOutOfBoundsException: String index out of range: -7
>>
>> At the same token if I set it to ME or MT, will not get an error but will
>> not be get the InboundNotification either.
>>
>> I have used HyperTerminal to query modem storage locations: AT+CPMS=? and
>> the response was:
>>
>> +CPMS: ("ME","MT","SM","SR"),("ME","MT","SM","SR"),("ME","MT","SM","SR")
>>
>> Also HyperTerminal displays +CMTI: "ME",0 every time an Inbound message is
>> received (but nothing on the SMSLib end).
>>
>> Using the modem’s web interfaces messages are received just fine. Is there
>> possibly another Internal memory location specific to these modem for this
>> to work?
>>
>> Please see attached log file
>>
>> Thx
>>
>> Ala
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "SMSLib Discussion Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/smslib?hl=en.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/smslib/-/zpvjoTuP2FMJ.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
--
You received this message because you are subscribed to the Google Groups
"SMSLib Discussion Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/smslib?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
