Double check your config files. Regards Mesbah
On Wed, Oct 5, 2022 at 3:53 PM Giulio Giovannini <giulio.in...@gmail.com> wrote: > Hi all, > > nobody has ever encountered this issue or knows how to solve it? > > Best ragards, > Giulio > > On Mon, 3 Oct 2022 at 11:46, Giulio Giovannini <giulio.in...@gmail.com> > wrote: > >> Hi all, >> >> I receive on kannel (svn-r5188M) an MO message with the below flags: >> >> 2022-10-03 08:14:15 Receive SMS [SMSC:xxxx] [SVC:] [ACT:xxxx] [BINF:] >> [FID:xxxx] [META:?smpp?] [from:xxxx] [to:xxxxxxx] [flags:-1:2:-1:0:-1] >> [msg:278:xxxx] [udh:0:] >> >> As you can see the second flag, the message coding %c, is set to 2 and >> the body of the MO is UCS2 encoded. >> >> I forward this message out using smsbox HTTP client capabilities >> configuring the below get-url: >> >> group = sms-service >> keyword-regex = ".*" >> name= xxxx >> catch-all = true >> get-url = " >> http://xxxx.com/dispatcher?messageCoding=%c&To=%P&Orig=%p&Body=%b&SmsCode=1 >> " >> accept-x-kannel-headers = true >> max-messages = 0 >> >> As you can see I am asking kannel to fill parameter messageCoding with >> content of placeholder %c >> >> If I check the smsbox access log I see that the messageCoding has been >> set to 0 when the message is forwarded to the HTTP endpoint defined in the >> get-url. >> >> 2022-10-03 08:14:15 SMS HTTP-request sender:xxxx request: 'xxx!' url: >> 'http:///xxxx.com/dispatcher?messageCoding=0&To=xxxx&Orig=xxxx&Body=xxxx' >> reply: 200 '<< successful >>' >> >> Is this a known bug? Have I misconfigured anything? >> >> Using %C placeholder instead of %c would solve the issue I think. The 4th >> flag in the log trace above printed when the message is received is the %C >> placeholder and it is already at 0 (flags:-1:2:-1:*0*:-1). >> >> Thanks for your help, >> >> Giulio >> >> >> >> >> >> >>
