|
I
don't know how different SMSC driver interact, but smsc_emi2.c show (to me - I
may be wrong) that :
- DLR
status code 1, 2 ,4 (Success, Failed, Buffered) are built in response of SMSC in
the receiver thread of a connection.
- DLR
status code 8, 16 (Accepted, Rejected - or ACK / NACK) are built directly in the
sender thread in kannel, just when kannel
tries
to submit_sm to SMSC, not when SMSC tries delivery of
message.
I
cannot garantee this behaviour in other drivers.
Cordialement,
Arnaud Beausoleil
France Telecom
SNCA
1 rue Thomas Edison
33600 PESSAC
Tel: (+33)5 56 55 78
55
[EMAIL PROTECTED]
This error code is defined when SMSC tries delivery of
message. But I doubt that SMSC attempts to deliver a message for which it has
already sent a submit_sm NACK to SMS
gateway.
regards,
Jeetendra
BEAUSOLEIL Arnaud URS Toulouse
wrote:
You can specify dlrmask to ask at least 16 in
order to get a DLR for the event 'NACK'
16
-> SMS rejected (submit_sm fail)..
must be supported by SMSC, of
course.
Cordialement,
Arnaud Beausoleil
France
Telecom SNCA
1 rue Thomas Edison
33600 PESSAC
Tel: (+33)5 56 55
78 55
[EMAIL PROTECTED]
Peter Beckman wrote:
When you use the HTTP portion of the smsbox to send your SMS, you are
getting a response from the smsbox, not the bearerbox.
The smsbox takes your message, checks to see that you have all the minimum
necessary variables set and set correctly, then accepts the message, and
tells you that it as accepted the message by replying with "Sent."
The bearerbox is completely separate. This is when the DLR comes into
usefulness -- to find out if the message was accepted by the SMSC or not.
If a SMSC rejects a message by sending negative ack
in response to a submit_sm, rest assured that you won't be getting any DLR
from it. DLR comes only when SMSC has accepted the submit_sm. So Roberto's
problem remain...
And his observation that the "Sent." only means
it was sent from smsbox to the bearerbox successfully is
*true*.
|
