Re: Problem receiving MO Meta-Data (TLV) values from sms-service

Hi Michael,

at this point in time it's not possible to receive TLVs that already 
defined in SMPP spec and implemented by kannel.
I will try to expand meta-data patch to allow it...

Thanks,
Alex

Michael Zervakis schrieb:
> Dear All,
> 
> I built the cvs-20081021 that includes meta-data code to test it.
> 
> In bearerbox configuration I included the following to receive MO TLV 
> 0x0204 (defined optional parameter)
> group = smpp-tlv
> name = "user_message_reference"
> tag = 0x0204
> length = 2
> type = integer
> 
> The deliver_sm PDU sent by the SMSC contains at the end the following 
> bytes 0204 0002 00a7
> and and bearerbox logs the TLV:
> DEBUG: Optional parameter tag (0x0204)
> DEBUG: Optional parameter length read as 2
> DEBUG:   user_message_reference: 167 = 0x000000a7
> 
> Smsbox configuration is:
> group = sms-service
> keyword = default
> get-url = 
> "http://myserver/kannel.aspx?sms_source=%p&sms_dest=%P&smsc-id=%i&sms_command=%k&sms_params=%s%r&sms_text=%a&carrier=mts&meta_data=%D 
> <http://myserver/kannel.aspx?sms_source=%p&sms_dest=%P&smsc-id=%i&sms_command=%k&sms_params=%s%r&sms_text=%a&carrier=mts&meta_data=%D>" 
> 
> 
> However the TLV value is lost when submiting the MO to our endpoint
> 
> DEBUG: Parsing URL 
> `http://myserver/kannel.aspx?sms_source=%2B999999999&sms_dest=1111&smsc-id=smsc&sms_command=Test&sms_params=&sms_text=Test&carrier=mts&meta_data=%3Fsmpp%3F 
> <http://myserver/kannel.aspx?sms_source=%2B999999999&sms_dest=1111&smsc-id=smsc&sms_command=Test&sms_params=&sms_text=Test&carrier=mts&meta_data=%3Fsmpp%3F>': 
> 
> DEBUG:   Scheme: http://
> DEBUG:   Host: myserver
> DEBUG:   Port: 80
> DEBUG:   Username: (null)
> DEBUG:   Password: (null)
> DEBUG:   Path: /kannel.aspx
> DEBUG:   Query: sms_source=%2B999999999&sms_
> dest=1111&smsc-id=smsc&sms_command=Test&sms_params=&sms_text=Test&carrier=mts&meta_data=%3Fsmpp%3F 
> 
> DEBUG:   Fragment: (null)
> 
> Any ideas on this?
> 
>