SMSSYNC web service error

True, without username goes to sandbox, with username goes to users inbox. But still keyword not being detected

Heres the log from the test

11.22.33.44 mydomain.com 2015-11-26 12:19:30 PID5656f8d205048 - L3 auth_validate_login # login attempt u:admin uid:1 p:0c9f9dcb0b347b2a66c39152fcaff314 ip:11.22.33.44
11.22.33.44 mydomain.com 2015-11-26 12:19:30 PID5656f8d205048 - L2 auth_validate_login # valid login u:admin uid:1 ip:11.22.33.44
11.22.33.44 mydomain.com 2015-11-26 12:19:30 PID5656f8d205048 - L2 login # u:admin uid:1 status:2 sid:rt0q8vrr2sg4vb8k5nf4cl8ud4 ip:11.22.33.44
44.33.22.11 mydomain.com 2015-11-26 12:21:29 PID5656f9497376b - L3 infobip__dlr # dlr request:
44.33.22.11 mydomain.com 2015-11-26 12:21:29 PID5656f9497376b - L3 infobip__dlr # apimsgid: 165112612212455188
44.33.22.11 mydomain.com 2015-11-26 12:21:29 PID5656f9497376b - L2 infobip__dlr # addr:44.33.22.11 host:mydomain.com type:DELIVERED smslog_id: uid:
11.22.33.44 mydomain.com 2015-11-26 12:21:34 PID5656f94e597fa - L3 sms_sync__sync # saving uid:1 dt:2015-11-26 12:21:34 ts:1448540485000 message_id:5b778ccf-510d-4452-81a3-2a604dde15c8 s:IBSMS m:@admin shinda be r:IBSMS
11.22.33.44 mydomain.com 2015-11-26 12:21:34 PID5656f94e597fa - L3 sms_sync__sync # forwarded to inbox uid:1 message_id:5b778ccf-510d-4452-81a3-2a604dde15c8
11.22.33.44 mydomain.com 2015-11-26 12:21:34 PID5656f94e597fa - L3 recvsms # isrecvsmsd:1 dt:2015-11-26 12:21:34 sender:IBSMS m:@admin @admin shinda be receiver:IBSMS smsc:
11.22.33.44 mydomain.com 2015-11-26 12:21:34 PID5656f94e597fa - L3 sms_sync__sync # saved uid:1 message_id:5b778ccf-510d-4452-81a3-2a604dde15c8 recvsms_id:223

    • 2015-11-26 12:21:35 PID5656f898959d4 - L3 recvsmsd # id:223 dt:2015-11-26 12:21:34 sender:IBSMS m:@admin @admin shinda be receiver:IBSMS smsc:
    • 2015-11-26 12:21:35 PID5656f898959d4 - L3 incoming__recvsms_intercept # recvsms_intercept dt:2015-11-26 12:21:34 s:IBSMS r:IBSMS m:@admin @admin shinda be
    • 2015-11-26 12:21:35 PID5656f898959d4 - L3 incoming__recvsms_intercept # pv u:admin uid:1 dt:2015-11-26 12:21:34 s:IBSMS r:IBSMS m:[@admin @admin shinda be] reference_id:
    • 2015-11-26 12:21:35 PID5656f898959d4 - L2 recvsms_inbox_add # saving sender:IBSMS receiver:IBSMS target:admin reference_id:
    • 2015-11-26 12:21:35 PID5656f898959d4 - L2 recvsms_inbox_add # saved id:11 sender:IBSMS receiver:IBSMS target:admin
    • 2015-11-26 12:21:35 PID5656f898959d4 - L3 incoming__recvsms_intercept # pv end
    • 2015-11-26 12:21:35 PID5656f898959d4 - L3 recvsms_process # dt:2015-11-26 12:21:34 sender:IBSMS m:@admin @admin shinda be receiver:IBSMS smsc:
    • 2015-11-26 12:21:35 PID5656f898959d4 - L3 recvsms_process # intercepted datetime:2015-11-26 12:21:34 sender:IBSMS receiver:IBSMS message:@admin @admin shinda be
      44.33.22.11 mydomain.com 2015-11-26 12:21:47 PID5656f95b99dd6 - L3 infobip__dlr # dlr request:
      44.33.22.11 mydomain.com 2015-11-26 12:21:47 PID5656f95b99dd6 - L3 infobip__dlr # apimsgid: 165112612214131018
      44.33.22.11 mydomain.com 2015-11-26 12:21:47 PID5656f95b99dd6 - L2 infobip__dlr # addr:44.33.22.11 host:mydomain.com type:DELIVERED smslog_id: uid:
      11.22.33.44 mydomain.com 2015-11-26 12:21:49 PID5656f95d4f0fc - L3 sms_sync__sync # saving uid:1 dt:2015-11-26 12:21:49 ts:1448540502000 message_id:0d9cd248-bba5-4d2f-bf13-18253f8d21c6 s:IBSMS m:shinda be r:IBSMS
      11.22.33.44 mydomain.com 2015-11-26 12:21:49 PID5656f95d4f0fc - L3 recvsms # isrecvsmsd:1 dt:2015-11-26 12:21:49 sender:IBSMS m:shinda be receiver:IBSMS smsc:
      11.22.33.44 mydomain.com 2015-11-26 12:21:49 PID5656f95d4f0fc - L3 sms_sync__sync # saved uid:1 message_id:0d9cd248-bba5-4d2f-bf13-18253f8d21c6 recvsms_id:224
    • 2015-11-26 12:21:49 PID5656f898959d4 - L3 recvsmsd # id:224 dt:2015-11-26 12:21:49 sender:IBSMS m:shinda be receiver:IBSMS smsc:
    • 2015-11-26 12:21:49 PID5656f898959d4 - L3 recvsms_process # dt:2015-11-26 12:21:49 sender:IBSMS m:shinda be receiver:IBSMS smsc:
    • 2015-11-26 12:21:49 PID5656f898959d4 - L3 recvsms_process # unhandled datetime:2015-11-26 12:21:49 sender:IBSMS receiver:IBSMS message:shinda be

told you to test without username, the message should be simple, like TEST 1234, that all

please re-share your log, the test without username, it is irrelevant if you use username in original incoming SMS, so it will just confuse me, the log no good to me

anton

That log is a test is two sms, one WITH @username and another WITHOUT @username

sorry, but I don’t know which one.

please do the test like this:

  1. tail the log

    tail -f /var/log/playsms/playsms.log -n 0 | tee test1.txt
    
  2. do the test, just single test, don’t do multiple test, in your case, send a simple SMS, intended SMS (without username)

  3. ctrl+c the tail log command, and read test1.txt

  4. sanitize test1.txt and paste the content here

thanks,
anton

11.22.33.44 mydomain.com 2015-11-26 12:54:31 PID5657010781808 - L3 sms_sync__sync # saving uid:1 dt:2015-11-26 12:54:31 ts:1448542461000 message_id:ebc1233e-a55d-45cc-911b-0d93fd0a76e1 s:+254723713096 m:Shinda Be r:+254723713096
11.22.33.44 mydomain.com 2015-11-26 12:54:31 PID5657010781808 - L3 recvsms # isrecvsmsd:1 dt:2015-11-26 12:54:31 sender:+254723713096 m:Shinda Be receiver:+254723713096 smsc:
11.22.33.44 mydomain.com 2015-11-26 12:54:31 PID5657010781808 - L3 sms_sync__sync # saved uid:1 message_id:ebc1233e-a55d-45cc-911b-0d93fd0a76e1 recvsms_id:225

    • 2015-11-26 12:54:31 PID5656f898959d4 - L3 recvsmsd # id:225 dt:2015-11-26 12:54:31 sender:+254723713096 m:Shinda Be receiver:+254723713096 smsc:
    • 2015-11-26 12:54:31 PID5656f898959d4 - L3 recvsms_process # dt:2015-11-26 12:54:31 sender:+254723713096 m:Shinda Be receiver:+254723713096 smsc:
    • 2015-11-26 12:54:31 PID5656f898959d4 - L3 recvsms_process # unhandled datetime:2015-11-26 12:54:31 sender:+254723713096 receiver:+254723713096 message:Shinda Be
      11.22.33.44 mydomain.com 2015-11-26 12:55:10 PID5657012e8e040 - L3 sms_sync__sync # saving uid:1 dt:2015-11-26 12:55:10 ts:1448542507000 message_id:915963d3-face-4547-9c99-03a3c1905cdb s:+254790466029 m:SHINDA BA r:+254790466029
      11.22.33.44 mydomain.com 2015-11-26 12:55:10 PID5657012e8e040 - L3 recvsms # isrecvsmsd:1 dt:2015-11-26 12:55:10 sender:+254790466029 m:SHINDA BA receiver:+254790466029 smsc:
      11.22.33.44 mydomain.com 2015-11-26 12:55:10 PID5657012e8e040 - L3 sms_sync__sync # saved uid:1 message_id:915963d3-face-4547-9c99-03a3c1905cdb recvsms_id:226
    • 2015-11-26 12:55:11 PID5656f898959d4 - L3 recvsmsd # id:226 dt:2015-11-26 12:55:10 sender:+254790466029 m:SHINDA BA receiver:+254790466029 smsc:
    • 2015-11-26 12:55:11 PID5656f898959d4 - L3 recvsms_process # dt:2015-11-26 12:55:10 sender:+254790466029 m:SHINDA BA receiver:+254790466029 smsc:
    • 2015-11-26 12:55:11 PID5656f898959d4 - L3 recvsms_process # unhandled datetime:2015-11-26 12:55:10 sender:+254790466029 receiver:+254790466029 message:SHINDA BA

ok, looks like you don’t have a handler for keyword SHINDA, where do you add it ? can you screenshot the config for that keyword (SHINDA)

anton

Please find image attached…

For now I have no idea why the recvsms didn’t process it. If incoming SMS without sms_sync, does the sms poll with keyword shinda works ?

anton

I have installed playsms in the cloud on a VPS (Digital Ocean) incoming route is only smssync

ok. dont have SMSSync installed right now, will do that later for further tests.

But anyway, I don’t think the issue in sms_sync since its correctly identified the keyword thus it wasn’t add @admin by it self. Fyi, if sms_sync cannot find a known keyword it will automatically add @username in front of incoming SMS before handing it to recvsms() so that the message won’t go to sandbox, but instead routed to username’s Inbox.

anton

Thanks for the effort. will be waiting

Hi, any hope…just wondering why this is not working anymore and it used to

Hi,

I have tested this, here is the result on my server:

127.0.0.1 localhost 2015-11-29 06:02:08 PID565a32703d7ff - L3 sms_sync__sync # saving uid:1 dt:2015-11-29 06:02:08 ts: message_id:test3 s:0987654321 m:shinda ba r:
127.0.0.1 localhost 2015-11-29 06:02:08 PID565a32703d7ff - L3 recvsms # isrecvsmsd:1 dt:2015-11-29 06:02:08 sender:0987654321 m:shinda ba receiver: smsc:
127.0.0.1 localhost 2015-11-29 06:02:08 PID565a32703d7ff - L3 sms_sync__sync # saved uid:1 message_id:test3 recvsms_id:16
- - 2015-11-29 06:02:09 PID565a3142b85d2 admin L3 recvsmsd # id:16 dt:2015-11-29 06:02:08 sender:0987654321 m:shinda ba receiver: smsc:
- - 2015-11-29 06:02:09 PID565a3142b85d2 admin L3 recvsms_process # dt:2015-11-29 06:02:08 sender:0987654321 m:shinda ba receiver: smsc:
- - 2015-11-29 06:02:09 PID565a3142b85d2 admin L2 sms_poll # begin k:SHINDA c:ba
- - 2015-11-29 06:02:09 PID565a3142b85d2 admin L3 gateway_decide_smsc # SMSC supplied:[] configured:[_smsc_supplied_] decided smsc:[]
- - 2015-11-29 06:02:09 PID565a3142b85d2 admin L2 sms_poll # vote s:0987654321 k:SHINDA c:BA vote multiple
- - 2015-11-29 06:02:09 PID565a3142b85d2 admin L2 sms_poll # vote s:0987654321 k:SHINDA c:BA log_id:3 valid vote

I added an SMS poll with keyword SHINDA and choice BA and push through sms_sync. Looks like all good for me.

The difference between your log and mine is after the process after recvsms_process. In my test I entered sms_poll, while yours unhandled.

anton

Does web-server matter? I create a new server (LAMP) Apache Mysql and PHP5 . It works will playsms. When I try with another server (LEMP) Nginx Mysql PHP5-FPM, we get the smssync issues. But both servers are Ubuntu 14.04 64 bit.

are they default config? you didnt touch the php.ini on both or one of them

anton

I used a server template for LEMP, i don’t know if its php.ini is modified, The LAMP is used default Ubuntu (apt-get install lamp-server)

Sharing LAMP server with another application that requires the following

a2enmod rewrite
a2enmod deflate
a2enmod headers

When I enabled them… smssync error appeared again…

try one by one see which one actually affecting

anton

Server crashed. :frowning: had to reinstall everything but it is all working now even with the changes… Confused