Re: [PATCH] SMPP Optional Parameters

That's what Alexandar just said...
You're using:

?smpp-tlv?MBbilling=

and it should be:

?smpp?MBbilling=

regards,

Juan

On Nov 26, 2007 12:33 PM, Kyriacos Sakkas <[email protected]> wrote:
> Call: (Relevant values inserted of courser)
>        $post .= "X-Kannel-Meta-Data:
> ?smpp-tlv?MBbilling=".$bill."&MBoperator=".$operatorid."&MBcontentType=100&MBcommand=START&MBsubDate=".date('U000')."&MBserviceId=XXX\r\n";
>
>
> Definitions: (Had all as octstring, switched to nullterm for those with
> no definite length)
> group = smpp-tlv
> name = MBoperator
> tag = 0x1402
> type = octetstring
> length = 5
>
> group = smpp-tlv
> name = MBbilling
> tag = 0x1403
> type = octetstring
> length = 5
>
> group = smpp-tlv
> name = MBsessionId
> tag = 0x1404
> type = nulterminated
> length = 60
>
> group = smpp-tlv
> name = MBserviceDesc
> tag = 0x1405
> type = nulterminated
> length = 10
>
> group = smpp-tlv
> name = MBcontentType
> tag = 0x1406
> type = nulterminated
> length = 5
> .....
>
>
>
> Alexander Malysh wrote:
> > Hi,
> >
> > I suppose you didn't defined TLVs in the config and group in meta_data named
> > smpp instead of smpp-tlv. Example:
> >         In the config
> > group = smpp-tlv
> > name = MBbilling
> > tag = 0x1601
> > type = integer|nulterminated|octetstring
> > length = 4
> >
> > meta_data=?smpp?MBbilling=XXX&...
> >
> > Kyriacos Sakkas wrote:
> >
> >
> >> If my packet capturing is correct, everything is parsed ok, but the TLVs
> >> do not get added to the PDU.
> >>
> >> Also my log file:
> >>
> >> 2007-11-26 15:58:08 [4930] [6] DEBUG: SMPP PDU 0x667eb0 dump:
> >> 2007-11-26 15:58:08 [4930] [6] DEBUG:   type_name: enquire_link_resp
> >> 2007-11-26 15:58:08 [4930] [6] DEBUG:   command_id: 2147483669 =
> >> 0x80000015
> >> 2007-11-26 15:58:08 [4930] [6] DEBUG:   command_status: 0 = 0x00000000
> >> 2007-11-26 15:58:08 [4930] [6] DEBUG:   sequence_number: 5 = 0x00000005
> >> 2007-11-26 15:58:08 [4930] [6] DEBUG: SMPP PDU dump ends.
> >> 2007-11-26 15:58:13 [4930] [17] DEBUG: boxc_receiver: sms received
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG: SMPP[mblox28444]: Manually forced
> >> source addr ton = 3, source add npi = 9
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG: SMPP[mblox28444]: Manually forced
> >> dest addr ton = 1, dest add npi = 1
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG: new group created `smpp-tlv'
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBbilling'
> >> value=`sub'
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBoperator'
> >> value=`31003'
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv'
> >> key=`MBcontentType' value=`100'
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBcommand'
> >> value=`START'
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBsubDate'
> >> value=`1196085364000'
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBserviceId'
> >> value=`XXXX'
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG: SMPP[mblox28444]: Sending PDU:
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG: SMPP PDU 0x6804c0 dump:
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG:   type_name: submit_sm
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG:   command_id: 4 = 0x00000004
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG:   command_status: 0 = 0x00000000
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG:   sequence_number: 6 = 0x00000006
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG:   service_type: NULL
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG:   source_addr_ton: 3 = 0x00000003
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG:   source_addr_npi: 9 = 0x00000009
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG:   source_addr: "28444"
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG:   dest_addr_ton: 1 = 0x00000001
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG:   dest_addr_npi: 1 = 0x00000001
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG:   destination_addr: "1XXXXXXXXX"
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG:   esm_class: 3 = 0x00000003
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG:   protocol_id: 0 = 0x00000000
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG:   priority_flag: 0 = 0x00000000
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG:   schedule_delivery_time: NULL
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG:   validity_period: NULL
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG:   registered_delivery: 1 =
> >> 0x00000001
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG:   replace_if_present_flag: 0 =
> >> 0x00000000
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG:   data_coding: 0 = 0x00000000
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG:   sm_default_msg_id: 0 = 0x00000000
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG:   sm_length: 8 = 0x00000008
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG:   short_message: "CONTENT0"
> >> 2007-11-26 15:58:13 [4930] [6] DEBUG: SMPP PDU dump ends.
> >> 2007-11-26 15:58:13 [4930] [17] DEBUG: send_msg: sending msg to boxc:
> >> <smsc4>
> >> 2007-11-26 15:58:13 [4930] [17] ERROR: Error reading from fd 46:
> >> 2007-11-26 15:58:13 [4930] [17] ERROR: System error 104: Connection
> >> reset by peer
> >> 2007-11-26 15:58:13 [4930] [17] ERROR: Connection to box <127.0.0.1>
> >> broke. 2007-11-26 15:58:13 [4930] [18] DEBUG: send_msg: sending msg to
> >> boxc: <smsc4>
> >> 2007-11-26 15:58:13 [4930] [18] ERROR: Error writing 16 octets to fd 46:
> >> 2007-11-26 15:58:13 [4930] [18] ERROR: System error 32: Broken pipe
> >> 2007-11-26 15:58:13 [4930] [18] ERROR: Couldn't write Msg to box
> >> <127.0.0.1>, disconnecting
> >> 2007-11-26 15:58:13 [4930] [18] DEBUG: Thread 18
> >> (gw/bb_boxc.c:boxc_sender) terminates.
> >> 2007-11-26 15:58:13 [4930] [17] ERROR: Error writing 16 octets to fd 46:
> >> 2007-11-26 15:58:13 [4930] [17] ERROR: System error 32: Broken pipe
> >> 2007-11-26 15:58:13 [4930] [17] DEBUG: Thread 17 (gw/bb_boxc.c:function)
> >> terminates.
> >> 2007-11-26 15:58:14 [4930] [6] WARNING: SMPP: PDU NULL terminated string
> >> (message_id) has no NULL.
> >> 2007-11-26 15:58:14 [4930] [6] DEBUG: SMPP[mblox28444]: Got PDU:
> >> 2007-11-26 15:58:14 [4930] [6] DEBUG: SMPP PDU 0x6804c0 dump:
> >> 2007-11-26 15:58:14 [4930] [6] DEBUG:   type_name: submit_sm_resp
> >> 2007-11-26 15:58:14 [4930] [6] DEBUG:   command_id: 2147483652 =
> >> 0x80000004
> >> 2007-11-26 15:58:14 [4930] [6] DEBUG:   command_status: 1066 = 0x0000042a
> >> 2007-11-26 15:58:14 [4930] [6] DEBUG:   sequence_number: 6 = 0x00000006
> >> 2007-11-26 15:58:14 [4930] [6] DEBUG:   message_id: NULL
> >> 2007-11-26 15:58:14 [4930] [6] DEBUG: SMPP PDU dump ends.
> >> 2007-11-26 15:58:14 [4930] [6] ERROR: SMPP[mblox28444]: SMSC returned
> >> error code 0x0000042a (Vendor-specific error, please refer to your SMPP
> >> provider) in response to submit_sm.
> >> 2007-11-26 15:58:14 [4930] [6] DEBUG: SMSC[mblox28444]: creating DLR
> >> message 2007-11-26 15:58:14 [4930] [6] DEBUG: SMSC[mblox28444]: DLR =
> >>
> >>
> > http://10.10.3.23:8111/dlrT.php?smsc-id=%i&status=%d&answer=%A&to=%P&from=%p&ts=%t&o=%o&I=%I&ts0=%D&ts1=%v&ts2=%T
> >
> >> 2007-11-26 15:58:14 [4930] [6] WARNING: smsbox_list empty!
> >> 2007-11-26 15:58:14 [4930] [4] WARNING: smsbox_list empty!
> >> 2007-11-26 15:58:14 [4930] [4] WARNING: smsbox_list empty!
> >> 2007-11-26 15:58:17 [4930] [6] DEBUG: SMPP[mblox28444]: Sending enquire
> >> link:
> >> 2007-11-26 15:58:17 [4930] [6] DEBUG: SMPP PDU 0x6804c0 dump:
> >> 2007-11-26 15:58:17 [4930] [6] DEBUG:   type_name: enquire_link
> >> 2007-11-26 15:58:17 [4930] [6] DEBUG:   command_id: 21 = 0x00000015
> >> 2007-11-26 15:58:17 [4930] [6] DEBUG:   command_status: 0 = 0x00000000
> >> 2007-11-26 15:58:17 [4930] [6] DEBUG:   sequence_number: 7 = 0x00000007
> >> 2007-11-26 15:58:17 [4930] [6] DEBUG: SMPP PDU dump ends.
> >> 2007-11-26 15:58:17 [4930] [6] DEBUG: SMPP[mblox28444]: Got PDU:
> >> 2007-11-26 15:58:17 [4930] [6] DEBUG: SMPP PDU 0x6804c0 dump:
> >> 2007-11-26 15:58:17 [4930] [6] DEBUG:   type_name: enquire_link_resp
> >> 2007-11-26 15:58:17 [4930] [6] DEBUG:   command_id: 2147483669 =
> >> 0x80000015
> >> 2007-11-26 15:58:17 [4930] [6] DEBUG:   command_status: 0 = 0x00000000
> >> 2007-11-26 15:58:17 [4930] [6] DEBUG:   sequence_number: 7 = 0x00000007
> >> 2007-11-26 15:58:17 [4930] [6] DEBUG: SMPP PDU dump ends.
> >>
> >> Kyriacos Sakkas wrote:
> >>
> >>> Hi,
> >>>     I just recompiled,  and it looks stable, the difference was that up
> >>> to now I had been using "--with-mysql" on the configure, which to be
> >>> honest I did not need in this instance, just a force of habit. Anyway I
> >>> will now test and if anything comes up I will let you know, but it does
> >>> look like the problem lies there. As soon as I have some time I will try
> >>> and dig a bit more into this.
> >>>
> >>> Kyriacos
> >>>
> >>> Alexander Malysh wrote:
> >>>
> >>>
> >>>> Hi,
> >>>>
> >>>> the warnings while compile are OK.
> >>>> When kannel segfaults? when compile or starting kannel? If when starting
> >>>> kannel please provide backtrace.
> >>>>
> >>>> Kyriacos Sakkas wrote:
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> Minus attachments.
> >>>>>
> >>>>>
> >>>>> Kyriacos Sakkas wrote:
> >>>>>
> >>>>>
> >>>>>
> >>>>>> Hi,
> >>>>>>     Trying to compile against cvs, I segfault. Diring compile the only
> >>>>>> "error" is:
> >>>>>>
> >>>>>> gw/meta_data.c: In function âmeta_data_set_valueâ:
> >>>>>> gw/meta_data.c:338: warning: passing argument 2 of âdict_putâ discards
> >>>>>> qualifiers from pointer target type
> >>>>>> gw/meta_data.c:340: warning: passing argument 2 of âdict_putâ discards
> >>>>>> qualifiers from pointer target type
> >>>>>> gw/meta_data.c:341: warning: passing argument 2 of âdict_getâ discards
> >>>>>> qualifiers from pointer target type
> >>>>>> gw/meta_data.c:343: warning: passing argument 2 of âdict_putâ discards
> >>>>>> qualifiers from pointer target type
> >>>>>> gw/meta_data.c: In function âmeta_data_get_valueâ:
> >>>>>> gw/meta_data.c:368: warning: passing argument 2 of âdict_removeâ
> >>>>>> discards qualifiers from pointer target type
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>
> >
> >
>
>
> --
>
> Kyriacos Sakkas
> Development Team
> Netsmart
> Tel: + 357 22 452565
> Fax: + 357 22 452566
> Email: [email protected]
> http://www.netsmart.com.cy
>
> Taking Business to a New Level!
>
> ** Confidentiality Notice: The information contained in this email
> message may be privileged, confidential and protected from disclosure.
> If you are not the intended recipient, any dissemination, distribution,
> or copying of this  email message is strictly prohibited.
> If you think that you have received this email message in error, please
> email the sender at [email protected] **
>
>
>