More from Nexmo, callbacks and sent message status

playSMS Help
1

Hello Anton,

Hope this note finds you well. I have another case involving Nexmo. It has come to our attention that since a couple of week everytime i use Nexmo the messages are sent, however, now the box next to the costs of the message is Yellow. It used to be green when messages were delivered, red when they failed or blue.

Now im getting these weird yellow coded messages. Messages are in fact being delivered but somehow PlaySMS is not acknowledging that. I have not changed anything in my setup however i just upgraded to 1.2.1 just to make sure i was not missing anything. After upgrading the situation is the same. Messages are sent but my playSMS is not aware.

I have checked the callback settings and they are all right. Indeed i see the callbacks in the logs. So im not sure if this is a new bug or Nexmo changed their signaling and you are not aware.

Please find attached a log entry for my last message.

Thanks

73.139.174.29 sms.linkedip.com 2015-08-25 22:35:55 PID55dd260a7f531 admin L2 sendsms # start uid:1 sender_id:[19543723736] smsc:[]
73.139.174.29 sms.linkedip.com 2015-08-25 22:35:55 PID55dd260a7f531 admin L2 sendsms_queue_create # saving queue_code:b99a53209a13c2c3335ff61f68f68feb src:19543723736 scheduled:2015-08-25 22:35:55
73.139.174.29 sms.linkedip.com 2015-08-25 22:35:55 PID55dd260a7f531 admin L2 sendsms_queue_create # saved queue_code:b99a53209a13c2c3335ff61f68f68feb id:369
73.139.174.29 sms.linkedip.com 2015-08-25 22:35:55 PID55dd260a7f531 admin L2 sendsms # dst:1 sms_count:1 total_charges:1
73.139.174.29 sms.linkedip.com 2015-08-25 22:35:55 PID55dd260a7f531 admin L2 sendsms_queue_push # saving queue_code:b99a53209a13c2c3335ff61f68f68feb dst:19546087693
73.139.174.29 sms.linkedip.com 2015-08-25 22:35:55 PID55dd260a7f531 admin L2 sendsms_queue_push # saved queue_code:b99a53209a13c2c3335ff61f68f68feb smslog_id:127476
73.139.174.29 sms.linkedip.com 2015-08-25 22:35:55 PID55dd260a7f531 admin L2 sendsms # end queue_code:b99a53209a13c2c3335ff61f68f68feb queue_count:1 sms_count:1 failed_queue:0 failed_sms:0

    • 2015-08-25 22:35:55 PID55dd233c5743f - L2 clickatell__getsmsstatus # smslog_id:108301 apimsgid:ac3a3659e0711f3b82ecefcb7b98aff8 charge:0 status:001 sms_status:0
    • 2015-08-25 22:35:55 PID55dd260bb09e6 - L2 sendsmsd # start processing queue_code:b99a53209a13c2c3335ff61f68f68feb queue_count:1 sms_count:1 scheduled:2015-08-25 22:35:55 uid:1 gpid:0 sender_id:19543723736
    • 2015-08-25 22:35:56 PID55dd260bb09e6 - L2 sendsmsd # sending queue_code:b99a53209a13c2c3335ff61f68f68feb smslog_id:127476 to:19546087693 sms_count:1 counter:1
    • 2015-08-25 22:35:56 PID55dd260bb09e6 - L2 sendsms_process # start
    • 2015-08-25 22:35:56 PID55dd260bb09e6 - L2 simplerate__cansend # allowed user uid:1 sms_to:19546087693 credit:2959.000 count:1 rate:1.000 charge:1 balance:2958
    • 2015-08-25 22:35:56 PID55dd260bb09e6 - L2 sendsms # saving smslog_id:127476 u:1 g:0 gw:nexmo smsc:linkedipulcnm001 s:19543723736 d:19546087693 type:text unicode:0 status:0
    • 2015-08-25 22:35:56 PID55dd260bb09e6 - L2 sendsms_process # saved smslog_id:127476 id:124178
    • 2015-08-25 22:35:56 PID55dd260bb09e6 - L2 nexmo__outgoing # sent smslog_id:127476 message_id:0200000076359208 status:0 error:
    • 2015-08-25 22:35:56 PID55dd260bb09e6 - L2 simplerate__deduct # enter smslog_id:127476
    • 2015-08-25 22:35:56 PID55dd260bb09e6 - L2 credit_hook_rate_setusercredit # saving uid:1 balance:2958
    • 2015-08-25 22:35:56 PID55dd260bb09e6 - L2 credit_hook_rate_setusercredit # saved uid:1 balance:2958
    • 2015-08-25 22:35:56 PID55dd260bb09e6 - L2 simplerate__deduct # user uid:1 parent_uid: smslog_id:127476 msglen:25 count:1 rate:1.000 charge:1 credit:2959.000 balance:2958
    • 2015-08-25 22:35:56 PID55dd260bb09e6 - L2 simplebilling__post # saving smslog_id:127476 rate:1.000 credit:2959.000 count:1 charge:1
    • 2015-08-25 22:35:56 PID55dd260bb09e6 - L2 simplebilling__post # saved smslog_id:127476 id:94964
    • 2015-08-25 22:35:56 PID55dd260bb09e6 - L2 sendsms_process # end
    • 2015-08-25 22:35:56 PID55dd260bb09e6 - L2 sendsmsd # result queue_code:b99a53209a13c2c3335ff61f68f68feb to:19546087693 flag:1 smslog_id:127476
    • 2015-08-25 22:35:56 PID55dd260bb09e6 - L2 sendsmsd # finish processing queue_code:b99a53209a13c2c3335ff61f68f68feb uid:1 sender_id:19543723736 queue_count:1 sms_count:1
      174.36.197.201 sms.linkedip.com 2015-08-25 22:35:56 PID55dd260c5167d - L2 nexmo__callback # pushed msisdn:19546087693 to:19543723736 network-code:310004 messageId:0200000076359208 price:0.00480000 status:accepted scts:1508260235 err-code:1 client-ref:127476 message-timestamp:2015-08-26 02:35:52
2

the relevant logs are after the last 2 3 lines, please paste more after that

we’re looking for dlr logs after nexmo__callback

anton

3

Hi Anton,

There is no more lines after that. I’ve talked to them and they say their signalling says the message is ‘ACCEPTED’.
Should it be more?

4

Should be more on playSMS side, and it should be reflected in log file. Nexmo has done their part correctly.

Anton