Author Message
Luis Claudio
New member
Username: Agentelu

Post Number: 5
Registered: 11-2018
Posted on Friday, November 29, 2019 - 10:41 pm:   

Hello, we have nowSMS installed and implemented CallBack.

We note that when the callback url service is active, many messages are not sent. Some accounts for some reason cannot send SMS. We would like you to help us understand why this could happen. And we also want to understand what the impact is if the service we provide takes a long time to respond to the nowsms callback, which can happen. When it is too many messages to be sent our service generates small delays. Can this affect the sending of messages? What problems can happen and how can we solve or investigate?

Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 6077
Registered: 08-2008
Posted on Monday, December 02, 2019 - 09:57 pm:   


It depends on what callbacks you have implemented and how long you are taking to respond.

NowSMS may be generating many callbacks simultaneously, especially if they are processing slowly.

Generally speaking, each user connection will get its own thread, and delays processing an SMSSend callback will effect how quickly the next message from that same user will be accepted by NowSMS.

Each SMSC connection will be processing SMSOut callbacks in one thread per connection. Delays will impact the outbound speed of that connection.


We note that when the callback url service is active, many messages are not sent.

The first question is what does this mean?

Is the message making it to NowSMS? Or is the callback rejecting or failing?

The SMSWEB-yyyymmdd.LOG records client submissions to NowSMS.

The SMSOUT-yyyymmdd.LOG records activity from NowSMS to SMSC.

Is the problem that the messages are not submitted (not in SMSWEB log), or not sent out (not in SMSOUT)?

I'm assuming "not submitted" based on your description.

What errors do the clients see?

I'd suggest using Wireshark to see the callback activity and responses. You can also see some of this in SMSDEBUG.LOG, but Wireshark will be a little easier to match requests and responses.

NowSMS Support
Luis Claudio
New member
Username: Agentelu

Post Number: 6
Registered: 11-2018
Posted on Wednesday, December 04, 2019 - 05:30 pm:   

Hello, thanks for the reply.

We'll consider "late" shipping, not "undeliverable". There is a long delay but the messages are sent.
When Call Back URL services are turned on, some users, especially those who send in bulk, are left with pending messages, if services are turned off, messages that have been submitted begin to be sent. I think the problem is that the processing of URL call backs is conditioning the sending of messages!

We cannot understand why services create this delay because our services do not perform any tasks that take time. Our services receive the urls, answer with "OK" and create an internal task to save that record. The only thing the service does is answer the URLs with "OK" to get the message sent.

We are looking for a solution to store the records of sent messages in a database of all sent messages processed by now sms! but that does not condition the performance! Do you suggest any solutions?

Add Your Message Here, or click here to start a new topic.
Bold text Italics Underline Create a hyperlink Insert a clipart image
Options: Automatically activate URLs in message