[OpenSIPS-Users] MSILO Module can't work

[Bogdan-Andrei Iancu]

Hi Tin,

Once again, can you post the full REGISTER request here ? are you sure 
that REGISTER do advertise "MESSAGE" in the Allow header

Also , you could enable full debug for the m_dump() function:
     set_debug(4);
     m_dump();
     set_debug();

In this case, you may get a clue why the function does not send out the 
stored messages.

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 03.02.2015 03:05, tin wrote:
> Dear Bogdan,
>          Thanks for all your reply and kindly help. I definitely saw 
> the record in DB. here are the records on my DB:
>> mysql> select * from silo where ctype = 'text/plain';
>> +------+-------------------------+-------------------------+----------+-----------------+------------+------------+----------+------------+-------+
>> | id   | src_addr                | dst_addr            | username | 
>> domain          | inc_time   | exp_time   | snd_time | ctype      | 
>> body  |
>> +------+-------------------------+-------------------------+----------+-----------------+------------+------------+----------+------------+-------+
>> | 3659 | sip:008 at 118.193.154.214 | sip:010 at 118.193.154.214 | 010     
>>  | 118.193.154.214 | 1422859611 | 1422895611 |        0 | text/plain 
>> | coi   |
>> | 3667 | sip:008 at 118.193.154.214 | sip:010 at 118.193.154.214 | 010     
>>  | 118.193.154.214 | 1422860496 | 1423119696 |        0 | text/plain 
>> | ggg   |
>> | 3669 | sip:008 at 118.193.154.214 | sip:010 at 118.193.154.214 | 010     
>>  | 118.193.154.214 | 1422860514 | 1423119714 |        0 | text/plain 
>> | qqq   |
>> | 3671 | sip:008 at 118.193.154.214 | sip:010 at 118.193.154.214 | 010     
>>  | 118.193.154.214 | 1422860599 | 1423119799 |        0 | text/plain 
>> | bbbbb |
>> | 3719 | sip:003 at 118.193.154.214 | sip:010 at 118.193.154.214 | 010     
>>  | 118.193.154.214 | 1422868318 | 1423127518 |        0 | text/plain 
>> | 456   |
>> | 3718 | sip:003 at 118.193.154.214 | sip:010 at 118.193.154.214 | 010     
>>  | 118.193.154.214 | 1422868210 | 1423127410 |        0 | text/plain 
>> | 123   |
>> | 3717 | sip:003 at 118.193.154.214 | sip:010 at 118.193.154.214 | 010     
>>  | 118.193.154.214 | 1422867734 | 1423126934 |        0 | text/plain 
>> | 999   |
>>
>>
>> The username is : 010
>> Domain is :  118.193.154.214
>> They match the AOR of the user that register later.
>>
>> *Here is how i test offline message:*
>> The user of sip:008 at 118.193.154.214 is online, And another user of 
>> sip:010 at 118.193.154.214 is offline, When the user of 
>> sip:008 at 118.193.154.214 is sending message to another user of 
>> sip:010 at 118.193.154.214, the message is saved to DB and not reached 
>> to destination since another user of sip:010 at 118.193.154.214 is 
>> offline. The records for offline messages are saved to DB  as above.
>>  I could not found anything wrong with records, could you please help 
>> me to double check ? appreciate!!!
>>
>> *The problem that i am facing now:*
>> The problem i am facing is that record is saved successfully to DB 
>> but not offline message shown up on linphone android app when offline 
>> user goes back to online. this issue has already cost us a lot of 
>> time but not good news, i appreciate all your help so much,your help 
>> gives us hope.
>> The function m_dump() has already be added on my opensips.cfg script, 
>> and the following log for success is received. *
>> **log("MSILO: offline messages dumped - if they were\n"); ***
>>
>> *my opensips.cfg script
>> *The following is my full opensips.cfg scrip, i hope it might help. 
>> could you please help me to double check the script if anything 
>> wrong? I really could not find out the reason why offline message is 
>> not sending from DB to android app when user go back to online. By 
>> the way, this script can be run successfully  on my opensips v1.11 
>> and has no error.
>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20150203/80ac140d/attachment-0001.htm>