Practically, making the sendsms CGI interface wait until a response (either success or fail) from the SMSC is returned would be useful for multithreaded applications, so they can get instant information about whether if the message reliably reached to the SMSC or not.
Ah, reached the SMSC, thats a little different from reaching a phone. You might expect it to reach the SMSC pretty quickly, regardless of phone status.
You can (1.4.1-stable) ask smsbox to wait for a response from bearerbox, which will give you info on submission. If bearerbox is not heavily loaded this is generally submission to the smsc, but can be queued.
The important thing from the app is probably that it will not get lost, so even if bearerbox reports queued, that should be ok for most apps anyway I would have though.
Regards Ben
