sql_id: 4462
momt: DLR
sender: xxxxxxxx
receiver: 2xxxxxxx
udhdata: NULL
msgdata: NACK%2F0x00000453%2FVendor-specific+error%2C+please+refer+to+your+SMPP+provider
time: 1329228303
smsc_id: SMPP:xxxxxxxx
service: sender
account: NULL
id: NULL
sms_type: 3
mclass: NULL
mwi: NULL
coding: NULL
compress: NULL
validity: NULL
deferred: NULL
dlr_mask: 16
dlr_url: NULL
pid: NULL
alt_dcs: NULL
rpi: NULL
charset: NULL
boxc_id: NULL
binfo: NULL
meta_data: NULL
I need to get TLV fields into this metadata field, but they are not parsed after error message.
Regards Vit.
On Wed, 15 Feb 2012 08:45:16 +0200
>
> Hello,
> TLV options in config are set, example:
> group = smpp-tlv
> name = rut_addr
> tag = 0x1510
> type = octetstring
> length = 20
> About the error - I know what it means, I need to get
>tlv fields for this response. If I get this command
>status I need to write all tlv information into database
>for further logic.
> Kannel supports this function? If so, how can I get the
>metadata for my response into database?
> I have Bearbox , SMSbox , Sqlbox.
> I don’t have metadata for response, with command status
>!= 0.
> Regards Vit.
>
> On Tue, 14 Feb 2012 22:46:29 +0100
> "Milan P. Stanic" wrote:
>> On Tue, 2012-02-14 at 16:04, [email protected] wrote:
>>> Hello,
>>>
>>> I’ve done the changes to Kannel, it is working.
>>>
>>> Got One more problem, when I tester error responses:
>>>
>>> I don’t Get parsed Meta data from Negative
>>>Submit_SM_Resp, it isn’t parsed
>>> by bearbox, dlr gets written to database with error
>>>code from command
>>> status. So if I need to receive TLV metadata from
>>>negative response, maybe
>>> there is a solution?
>>
>> Did you set smpp-tlv options in config file?
>>
>>> Example of Response:
>>>
>>> OUT 2012-02-14 15:37:12
>>> H command_id &nb
> sp; 0x80000004
>>> H command_name SUBMIT_SM_RESP
>>> H sequence_number 41
>>> H command_status 1044
>>> message_id => ''
>>& gt; rut_addr_ton => 5
>>>0x00000003
>>> rut_subscriber_id => '334455253/2'
>>> rut_addr =>
>>>'fserhWJKDwlqwkejf'
>> >
>>> LOG:
>>> 2012-02-14 15:35:32 [720] [6] Got PDU:
>>> 2012-02-14 15:35:32 [720] [6] DEBUG: SMPP PDU
>>>0x9918ae0 dump:
>>> 2012-02-14 15:35:32 [720] [6] DEBUG: type_name:
>>>submit_sm_resp
>>> 2012-02-14 15:35:32 [720] [6] DEBUG: command_id:
>>>2147483652 = 0x80000004
>>> 2012-02-14 15:35:32 [720] [6] DEBUG:
>>>command_status: 1044 = 0x00000403
>>> 2012-02-14 15:35:32 [720] [6] DEBUG:
>>>sequence_number: 42 = 0x0000002a
>>> 2012-02-14 15:35:32 [720] [6] DEBUG: message_id:
>>>NULL
>>> 2012-02-14 15:35:32 [720] [6] DEBUG: SMPP PDU dump
>>>ends.
>>> 2012-02-14 15:35:32 [720] [6] ERROR: SMPP[xxxx]: SMSC
>>>returned error code
>>> 0x00000453 (Vendor-specific error, please refer to
>>>your SMPP provider) in
>>> response to submit _sm.
>>
>> You should ask provider what meand 0x00000453 error
>>code.
>> It is in the range of 'Reserved for SMSC vendor specific
>>errors'.
>>
>>> 2012-02-14 15:35:32 [720] [6] DEBUG: SMSC[xxxxx]:
>>>creating DLR message
>>>
>>> Regards Vit.
>>>
>>> On Fri, 10 Fe b 2012 17:09:42 +0100
>>> "Milan P. Stanic" wrote:
>>> > On Fri, 2012-02-10 at 15:24, [email protected]
>>>wrote:
>>> >> Hello,
>>> >>
>>> >> I’m trying to change File /gw/smsc/smsc_smpp.c
>>> >>
>>> >> Maybe anyone have stept in to such problem, and
>>>has
>>> >>an advice where to
>>> >> change the file will be better?
>>> >>
>>> >> I need to receive Deliver SM with 0 fields, so I’m
>>> >>wondering if I catch
>>&
> gt; >> Delivers With Null source address and change the
>>>data
>>> >>of those fields.
>>> >> Most of time after compilation I get segmentation
>>> >>fault..
>>> >>
>>> >> 1602: dlrmsg = handle_dlr(smpp,
>>> >>pdu->u.deliver_sm.source_addr,
>>> >> pdu->u.deliver_sm.short_message,
>>> >>pdu->u.deliver_sm.message_payload,
>>> >>
>>> >> pdu->u.deliver_sm.receipted_message_id,
>>> >>pdu->u.deliver_sm.message_state ,
>> > >> pdu->u.deliver_sm.network_error_code);
>>> >>
>>> >> Here I can catch if I have an empty source address
>>> >>like that:
>>> >>
>>> >> if ( pdu->u.deliver_sm.source_addr == NULL) {}
>>> >>
>>> >> Any help would be appreciated
> &g
> t;> >
>>> > Could you send a patch with your changes and tell
>>>which
>>> >version of
>>> > Kannel you use as a base for your modifications?
>>> >
>>> > And, questions about code modification/change
>>>should be
>>> >posted to
>>> > the [email protected], IMHO.
>>> >
>>> >> Regards. Vit
>>> >>
>>> >> On Tue, 07 Feb 2012 15:46:04 +0200
>>> >> wrote :
>>> >> >
>>> >> > Hi,
>>> >> > I’ve stept into a problem, Is it possible to
>>>handle
>>> >> >Deliver_SM with empty fields except TLV
>>>fields?how?
>>> >> > I get an Error, that its Null, here is my LOG:
>>> >> > >> > 2012-02-07 15:04:40 [12259] [6] DEBUG:
>>>Optional
>>> > > >parameter tag (0x1506)
>>> >> > 2012-02-07 15:04:40 [12259] [6] DEBUG: Optional
>>> >> >parameter length read as 5
>>> >> > 2012-02-07 15:04:40 [12259] [6] DEBUG: Found
>>> >>configured
>>> >> >optional parameter `rut_message_id'
>>> >> > 2012-02-07 15:04:40 [12259] [6] DEBUG: Optional
>>> >> >parameter tag (0x1508)
>>> >> > 2012 -02-07 15:04:40 [12259] [6] DEBUG: Optional
>>> >> >parameter length read as 1
>>> >> > 2012-02-07 15:04:40 [12259] [6] DEBUG: Found
>>> >>configured
>>> >> >optional parameter `rut _report_type'
>>> >> > 2012-02-07 15:04:40 [12259] [6] DEBUG: Optional
>>> >> >parameter tag (0x1500)
>>> >> > 2012-02-07 15:04:40 [12259] [6] DEBUG: Optional
>>> >> >parameter length r ead as 14
>>> >> > 2012-02-07 15:04:40 [12259] [6] DEBUG: Found
>>> >>configured
>>> >> >optional parameter `rut_created_ts'
>>> >> > 2012-02-07 15:04:40 [12259] [6] DEBUG:
>>>SMPP[xxxx]:
>>> >>Got
>>> >> >PDU:
>>> >> > 2012-02-07 15:04:40 [12259] [6] DEBUG: SMPP PDU
>>> &g t;>0x850eb1
>>> >> > 0 dump:
>>> >> > 2012-02-07 15:04:40 [12259] [6] DEBUG:
>>>type_name:
>>> >> >deliver_sm
>>> >> > 2012-02-07 15:04:40 [12259] [6] DEBUG:
>>>command_id:
>>> >>5 =
>>> >> >0x00000005
>>> >> > 2012-02-07 15:04:40 [12259] [6] DEBUG:
>>> >>command_status:
>>> >> >0 = 0x00000000
>>> >> > 2012-02-07 15:04:40 [12259] [6] DEBUG:
>>> >> > sequence_num ber: 1 = 0x00000001
>>> >> > 2012-02-07 15:04:40 [12259] [6] DEBUG:
>>> >>service_type:
>>> >> >NULL
>>> >> > 2012-02-07 15:04:40 [12259] [6] DEBUG:
>>> >> > source_addr_ton: 0 = 0x00000000
>>> >> > 2012-02-07 15:0 4:40 [12259] [6 ] DEBUG:
>>> >> > source_addr_npi: 0 = 0x00000000
>>> >> > 2012-02-07 15:04:40 [12259] [6] DEBUG:
>>>source_addr:
>>> >> >NULL
>>> >> > 2012-02-07 15:04:40 [12259] [6] DEBUG:
>>> >>dest_addr_ton:
>>> >> >0 = 0x00000000
>>> >> > 2012-02-07 15:04:40 [12259] [6] DEBUG:
>>> >>dest_addr_npi:
>>> >> >0 = 0x00000000
>>> >> > 2012-02-07 15:04:40 [12259] [6] DEBUG:
>>> >> > destination_addr: NULL
>>> >> > 2012-02-07 15:04:40 [12259] [6] DEB UG:
>>>esm_class: 4
>>> >>=
>>> >> >0x00000004
>>> >> > 2012-02- 07 15:04:40 [12259] [6] DEBUG:
>>> >>protocol_id:
>>> >> >0 = 0x00000000
>>> >> & gt; 2012-02-07 15:04:40 [12259] [6] DEBUG:
>>> >>priority_flag:
>>> >> >0 = 0x00000000
>>> >> > 2012-02-07 15:04:40 [12259] [6] DEBUG:
>>> >> > schedule_delivery_time: NULL
>>> >> > 2012-02-07 15:04:40 [12259] [6] DEBUG: >> >
>>>validity_period: NULL
>>> >> > 2012-02-07 15:04:40 [12259] [6] DEBUG:
>>> >> > registered_delivery: 0 = 0x00000000
>>> >> > 2012-02-07 15:04:40 [12259] [6] DEBUG:
>>> >> > replace_if_present_flag: 0 = 0 x00000000
>>> >> > 2012-02-07 15:04:40 [12259] [6] DEBUG:
>>>data_coding:
>>> >>0 >> >> >= 0x00000000
>>> >> > 2012-02-07 15:04:40 [12259] [6] DEBUG:
>>> >> > sm_default_msg_id: 0 = 0x00000000
>>> >> > 201 2-02-07 15:04:40 [12259] [6] DEBUG:
>>>sm_length: 0
>>> >>=
>>> >> >0x00000000
>>> >> > 2012-02-07 15:04:40 [12259] [6] DEBUG:
>>> >>short_message:
>>> >> >""
>>> >> > 2012-02-07 15:04:40 [12259] [6] DEBUG:
>>> >>rut_message_id:
>>> >> >"48024"
>>> >> > 2012-02-07 15:04:40 [12259] [6] DEBUG:
>>> >>rut_created_ts:
>>> >> >"20120207150639"
>>> >> > 2 012-02-07 15:04:40 [12259] [6] DEBUG :
>>> >> > rut_report_type: "0"
>>> >> > 2012-02-07 15:04:40 [12259] [6] DEBUG: SMPP PDU
>>> >>dump
>>> >> >ends.
>>>
> ; >> > 2012-02-07 15:04:40 [12259] [6] DEBUG:
>>>SMPP[xxxx]
>>> >> > ;handle_pdu, got DLR
>>> >> > 2012-02-07 15:04:40 [12259] [6] ERROR:
>>>SMPP[xxx]:
>>> >>got
>>> >> >DLR but could not find message or was not
>>>interested
>>> >>in
>>> >> >it id<> dst<(null)>, type<-1>
>>> >> >
>>> >> >
>>> >> > Regards.
>>> >> WARNING: gnome-keyring:: couldn't connect to:
>>> >>/tmp/keyring-CLI2Mn/pkcs11: No such file or
>>>directory
>>> >
>>> > --
>>> > Kind regards, Milan
>>> > --------------------------------------------------
>>> > Arvanta, IT Security http://www.arvanta.net
>>> > Please do not send me e-mail containing HTML code
>>>or
>>> >documents in
>>> ; > proprietary format (word, excel, pps and so on)
>>> >
>>> WARNING: gnome-keyring:: couldn't connect to:
>>>/tmp/keyring-oldPme/pkcs11: No such file or directory
>>
>> --
>> Kind regards, Milan
>> --------------------------------------------------
>> Arvanta, IT Security http://www.arvanta.net
>> Please do not send me e-mail containing HTML code or
>>documents in
>> proprietary format (word, excel, pps and so on)
>>
>
>
