No, My question is how to correlate between
message submitted using deliver_sm and delivery notification received for
it.
Sequence Number is only used for correlation
between request and response not between message and its delivery
notification.
I hope now you got my question.
- Orig
Every deliver_sm PDU
contains a sequence number field and every deliver_sm_resp
contains the same sequence number.
Does that answer
your question?
-Original Message-From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]On Behalf Of Amit DangSent:
Tuesday, November 11, 2003 9:4
Don't know why *system* is ignoring BUT
think it makes perfect human sense to ignore.
If sender is same as receiver, receiving the SMS itself is DLR.
Why get another DLR PDU?
regards
Navjot Singh
>-Original Message-
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of
>David Me
>
>If the operator wait for a submit_sm with esm_class=0,
>what can I do ? Maybe I can change the default esm_class ->0
>ESM_CLASS_SUBMIT_DEFAULT_SMSC_MODE
better to change as you said *above*.
>or change value of ESM_CLASS_SUBMIT_STORE_AND_FORWARD_MODE ->0
>Have you any ideas ?
>
>Thank you ve
Jarl,
> I take it as I'm using kannel-cvs (a week or two old) the above still
> applies, however I get the message
> saying use dlr-mask in my smsbox... any ideas why?
There has been a move away from dlrmask to dlr-mask. In future releases
you will need to use the later.
Cheers,
Alan
What all fields are used for correlation of
messages submitted through deliver_sm and its delivery receipt? message_id filed
in deliver_sm response is not allowed.
Thanks in Advance,
Amit
Hi all,
when sending an SMS to a recipient mobile number which is the same as the
sender number, the delivery reports are not properly updated. However, the
response codes from the SMSC are correct. Instead I see the following
entries in the log file:
2003-11-11 16:05:28 [4] INFO: NOTE: sender an
Hello,
If the operator wait for a submit_sm with esm_class=0,
what can I do ? Maybe I can change the default esm_class ->0
ESM_CLASS_SUBMIT_DEFAULT_SMSC_MODE
or change value of ESM_CLASS_SUBMIT_STORE_AND_FORWARD_MODE ->0
Have you any ideas ?
Thank you very much,
Alex
>
> On Tue, Nov 11, 2003 a
default mode in SMPP is Store_Forward mode ;-)
>-Original Message-
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of
>Alexandre BARBEITOS
>Sent: Tuesday, November 11, 2003 5:28 PM
>To: [EMAIL PROTECTED]
>Subject: SMPP submit_sm
>
>
>Hello,
>
>Does someone can explain me why whe
Hello,
Does someone can explain me why when a send a message with SMPP.
I have in the submit_sm:
esm_class = 3 per default, so I saw in the source that corresponds:
ESM_CLASS_SUBMIT_STORE_AND_FORWARD_MODE
But my operator expects to me esm_class = 0 seems to be
ESM_CLASS_SUBMIT_DEFAULT_SMSC_MOD
Last question before I accept I'm stupid and should not be bothering anyone
with more questions
> there could have been my fault or version mismatch but as of 1.3.1, there
> are 2 variables *dlrurl* and *dlrmask*.
I take it as I'm using kannel-cvs (a week or two old) the above still
applies, howe
Hi Jarl,
I'm not sure but probably you mix up what Kannel do and what Kannel doesn't do
(which we must do or create ourselves).
1) If you need to store the outgoing SMS (and its DLR status), you need to
stop pursue using Kannel built-in dlr features (I might miss something, but
the "group = d
On Tue, 2003-11-11 at 00:16, Alex Kinch wrote:
> Hi,
hi.
> Seen a couple of instances in the last few days when messages have got
> "stuck" in the store - at a guess due to the relevent SMPP connection
> being temporarily unavailable at the time they were submitted via
> smsbox.
what version, 1.2
13 matches
Mail list logo
