Thanks Alex, Actually, for MT cases, Im calling the HTTP using the example in the guide; &meta-data=%3Fsmpp%3Fmy-data%3DHello%2BWorld but I receive some SMSC returned errors like invalid destinations, which of course has not to do with kannel.
I have two ambigous cases in my head; -How can I terminate the session initialized by MO request? When I throw a request, lets say by dialing *200#, I`m able to call my application sending there %D values, but it lasts many seconds until HLR terminates it by itself. Also If multiple requests in paralel are initialised, how Kannel can keep records of each session, so when I will reply back from cgi-bin, kannel will understand the respective session and drop it? - How can I find the related specifications for Tag parameter? I see many combinations in hexadecimal but withput understanding their meaning. Is there any explanations for each hexa code? Thank You, Elton On Wed, Dec 2, 2009 at 11:23 AM, Alejandro Guerrieri < alejandro.guerri...@gmail.com> wrote: > You need to pass the value on the meta-data field. For example: > > ....&meta-data=?smpp?my-custom-var=1 > > (urlencoded of course) > > Regards, > > Alex > > On Wed, Dec 2, 2009 at 9:01 AM, Elton Hoxha <elt...@gmail.com> wrote: > >> Hi guys, >> >> I`m trying to use kannel for sending ussd request and receiving back using >> SMPP. >> >> my conf for TLV is: >> >> group = smpp-tlv >> name = my-custom-var >> tag = 0x0501 >> type = integer >> length = 2 >> smsc-id = test >> >> Using this I`m able to call my application by dialing ussd shortcodes, but >> I`m not able to terminate the session immediately. >> >> Also the values of ussd parameters take place under the VALUE parameter of >> TLV itself which is not present in the above conf. How can I manipulate this >> parameter if its not configurable in kannel? >> >> P.S this is an example I found googling around; >> >> Field Size Octets Type Description Parameter Tag 2 Integer 0x0501 >> Length 2 Integer Length of value part in octets Value 1 Integer This >> value can be one of the following values: >> >> 0 = PSSD Indication >> 1 = PSSR Indication >> 2 = USSR Request >> 3 = USSN Request >> >> 4 to 15 = Reserved >> >> 16 = PSSD Response >> 17 = PSSR Response >> 18 = USSR Confirm >> 19 = USSN Confirm >> >> 20 to 31 = Reserved >> 32 to 255 = Vendor specific operations >> > >
