anas
Cc: Latitude Test ; users
Sent: Monday, October 19, 2009 6:16 PM
Subject: Re: getting delivery report: delivery failure
not relevant !== optional. Where did you read "optional" or "can be removed"?
Again, this is NOT a standard, and it's documented by example, wh
; > > > > > *From:* Latitude Test
> > > > > > *To:* users ; Nikos Balkanas <
> > nbalka...@gmail.com>
> > > > > > *Sent:* Monday, October 19, 2009 4:59 PM
> > > > > > *Subject:* Fwd: getting delivery report: delivery
bject:* Fwd: getting delivery report: delivery failure
> > > > >
> > > > > I will contact my SMSC but I need to know exactly which fields are
> > > really
> > > > > being used by Kannel to return the DLR status?. Seems to me that
> Kannel
> > > is
> > >
;
> Let's stop the spam, until it's needed.
>
> BR,
> Nikos
>
> - Original Message -
> *From:* Alejandro Guerrieri <mailto:alejandro.guerri...@gmail.com>
> *To:* Latitude Test <mailto:latit
> > is
> > > > using *optional fields* like "sub" and "dlvrd". If thats true, then
> > isn't
> > > > is a bug?
> > > >
> > > >
> > > > Quoting Nokos
> > > >
> > > >
> &g
>
> Let's stop the spam, until it's needed.
>
> BR,
> Nikos
>
> ----- Original Message -
> *From:* Alejandro Guerrieri
> *To:* Latitude Test
> *Cc:* Nikos Balkanas ; users
> *Sent:* Monday, October 19, 2009 5:50 PM
> *Subject:* Re: getting de
s needed.
BR,
Nikos
- Original Message -
From: Alejandro Guerrieri
To: Latitude Test
Cc: Nikos Balkanas ; users
Sent: Monday, October 19, 2009 5:50 PM
Subject: Re: getting delivery report: delivery failure
Sorry, what optional fields are you talking about? sub: and dlvrd:
format. According
> to
> > >> SMPP 3.4 specs:
> > >>
> > >>
> > >> “
> > >> *id:II sub:SSS dlvrd:DDD submit date:YYMMDDhhmm done*
> > >>
> > >> *date:YYMMDDhhmm stat:DDD err:E Text: . . . . . . . .
> *id:II sub:SSS dlvrd:DDD submit date:YYMMDDhhmm done*
>>>
>>> *date:YYMMDDhhmm stat:DDD err:E Text: . . . . . . . . .”*
>>>
>>> Several optional fields (sub, dlvrd, err) are missing, but also a
>>> required field: "Text". Withou
; >> “
> >> *id:II sub:SSS dlvrd:DDD submit date:YYMMDDhhmm done*
> >>
> >> *date:YYMMDDhhmm stat:DDD err:E Text: . . . . . . . . .”*
> >>
> >> Several optional fields (sub, dlvrd, err) are missing, but also a required
> >> fiel
;> in the logs I saw the following:
>>
>> dlvrd:001
>> sub:001
>> Text:.
>>
>> The mendatory field Text does not contain any useful info here. How kannel
>> knows the status of the message then? Seems it uses the optional fields
>> which are &quo
l cannot understand the DLR.
>>
>> Contact your SMSc about it. They should comply to the SMPP spec.
>>
>>
>>
>> BR,
>>
>> Nikos
>>
> -- Forwarded message --
> From: Latitude Test
> Date: Mon, Oct 19, 2009 at 3:29 PM
BR,
Nikos
-- Forwarded message --
From: Latitude Test
Date: Mon, Oct 19, 2009 at 3:29 PM
Subject: Re: getting delivery report: delivery failure
To: Nikos Balkanas
Cc: users
Are you saying "dlvrd" and "sub" are mandatory for Kannel?
y field Text does not contain any useful info here. How kannel
> knows the status of the message then? Seems it uses the optional fields
> which are "sub" and "dlvrd".
>
> Please confirm.
>
> Thanks.
> -- Forwarded message --
> From: Latitude
;.
Please confirm.
Thanks.
-- Forwarded message --
From: Latitude Test
Date: Mon, Oct 19, 2009 at 1:31 PM
Subject: Re: getting delivery report: delivery failure
To: users , Nikos Balkanas
Thanks Nikos. But I do get "stat" field which contains some usef
but it is
worth a try.
Let me know how it works. I can not test it.
BR,
Nikos
- Original Message -
From: Latitude Test
To: users ; Nikos Balkanas
Sent: Monday, October 19, 2009 2:31 PM
Subject: Re: getting delivery report: delivery failure
Thanks Nikos. But I do get &q
ong DLR format. According
>>>> to SMPP 3.4 specs:
>>>>
>>>>
>>>> “
>>>> *id:II sub:SSS dlvrd:DDD submit date:YYMMDDhhmm done*
>>>>
>>>> *date:YYMMDDhhmm stat:DDD err:E Text: . . . . . . . . .”*
>>>&g
vrd".
>>
>> Please confirm.
>>
>> Thanks.
>> ------ Forwarded message --
>> From: Latitude Test
>> Date: Mon, Oct 19, 2009 at 1:31 PM
>> Subject: Re: getting delivery report: delivery failure
>> To: users , Nikos Balkanas
t;
> Please confirm.
>
> Thanks.
> -- Forwarded message ------
> From: Latitude Test
> Date: Mon, Oct 19, 2009 at 1:31 PM
> Subject: Re: getting delivery report: delivery failure
> To: users , Nikos Balkanas
>
>
>
> Thanks Nikos. But I do get "stat&
>
> BR,
>
> Nikos
>
> - Original Message -
>
> *From:* Latitude Test
> *To:* users ; Nikos Balkanas
> *Sent:* Monday, October 19, 2009 12:26 PM
> *Subject:* Re: getting delivery report: delivery failure
>
> Apologies for not sending the complete PDU
field: "Text". Without it kannel cannot understand the DLR.
Contact your SMSc about it. They should comply to the SMPP spec.
BR,
Nikos
- Original Message -
From: Latitude Test
To: users ; Nikos Balkanas
Sent: Monday, October 19, 2009 12:26 PM
Subject: Re: gettin
Apologies for not sending the complete PDU before. Kindly review the
complete PDU and guide.
Thanks.
...
[7] DEBUG: SMPP[abc1]: Got PDU:
[7] DEBUG: SMPP PDU 8174bc0 dump:
[7] DEBUG: type_name: enquire_link_resp
[7] DEBUG: command_id: 2147483669 = 0x8015
[7] DEBUG: command_status: 0 = 0x
Hmm. Interesting. I misspelled "DLR" to "DKR" and I think this caused the
problem. When asking for detailed DLR excerpt from bb logs, I didn't have half
a PDU in mind! Are you trying to save lines on copy and paste? Please resubmit
the whole PDU entry from bb logs.
Nikos
- Original Messa
This is what I see in the log:
DEBUG: data: 69 64 3a 32 34 35 31 37 33 33 31 33 34 20 73 75 id:2451733134
su
DEBUG: data: 62 6d 69 74 20 64 61 74 65 3a 30 39 31 30 31 33 bmit
date:091013
DEBUG: data: 30 37 30 34 20 64 6f 6e 65 20 64 61 74 65 3a 30 0704 done
date:0
DEBUG: data: 39 31 30 31 33 30 39
Hi,
Please post detailed bb logs with the respond_sm PDU from your SMSc. I suspect
that your SMSc is sending the wrong DKR.
BR,
Nikos
- Original Message -
From: Latitude Test
To: users
Sent: Tuesday, October 13, 2009 2:15 PM
Subject: getting delivery report: delivery failure
25 matches
Mail list logo
