Re: Mismatch between received message coding and smsbox forwarded message coding
Hi, access-log-format controls access log format and if it’s changed you may see in access log different flag positions which results in different values für message coding in URL. Regards, Alexander Malysh Am 20. Okt. 2022, 08:58 +0200 schrieb Giulio Giovannini : > Hello Alexander. > > Not sure what you mean. What config parameter controls the access log format > you are referring to? How do you think it is set and how should I set it? > How would the log format have an impact on placeholder substitution? > > Best regards, > Giulio > > > On Wed, 19 Oct 2022 at 17:18, Alexander Malysh wrote: > > > Hi, > > > > > > did you maybe changed access log format and mixed %c / %C there ? > > > > > > Regards, > > > Alexander Malysh > > > Am 3. Okt. 2022, 11:46 +0200 schrieb Giulio Giovannini > > > : > > > > Hi all, > > > > > > > > I receive on kannel (svn-r5188M) an MO message with the below flags: > > > > > > > > 2022-10-03 08:14:15 Receive SMS [SMSC:] [SVC:] [ACT:] [BINF:] > > > > [FID:] [META:?smpp?] [from:] [to:xxx] [flags:-1:2:-1:0:-1] > > > > [msg:278:] [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= > > > > catch-all = true > > > > get-url = > > > > "http://.com/dispatcher?messageCoding=%c=%P=%p=%b=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: request: 'xxx!' url: > > > > 'http:///.com/dispatcher?messageCoding=0===' > > > > 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 > > > > > > > > > > > > > > > > > > > > > > > >
Re: Mismatch between received message coding and smsbox forwarded message coding
Hello Alexander. Not sure what you mean. What config parameter controls the access log format you are referring to? How do you think it is set and how should I set it? How would the log format have an impact on placeholder substitution? Best regards, Giulio On Wed, 19 Oct 2022 at 17:18, Alexander Malysh wrote: > Hi, > > did you maybe changed access log format and mixed %c / %C there ? > > Regards, > Alexander Malysh > Am 3. Okt. 2022, 11:46 +0200 schrieb Giulio Giovannini < > giulio.in...@gmail.com>: > > Hi all, > > I receive on kannel (svn-r5188M) an MO message with the below flags: > > 2022-10-03 08:14:15 Receive SMS [SMSC:] [SVC:] [ACT:] [BINF:] > [FID:] [META:?smpp?] [from:] [to:xxx] [flags:-1:2:-1:0:-1] > [msg:278:] [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= > catch-all = true > get-url = " > http://.com/dispatcher?messageCoding=%c=%P=%p=%b=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: request: 'xxx!' url: > 'http:///.com/dispatcher?messageCoding=0===' > 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 > > > > > > >
Re: Mismatch between received message coding and smsbox forwarded message coding
Hi, did you maybe changed access log format and mixed %c / %C there ? Regards, Alexander Malysh Am 3. Okt. 2022, 11:46 +0200 schrieb Giulio Giovannini : > Hi all, > > I receive on kannel (svn-r5188M) an MO message with the below flags: > > 2022-10-03 08:14:15 Receive SMS [SMSC:] [SVC:] [ACT:] [BINF:] > [FID:] [META:?smpp?] [from:] [to:xxx] [flags:-1:2:-1:0:-1] > [msg:278:] [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= > catch-all = true > get-url = > "http://.com/dispatcher?messageCoding=%c=%P=%p=%b=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: request: 'xxx!' url: > 'http:///.com/dispatcher?messageCoding=0===' > 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 > > > > > >
Re: Mismatch between received message coding and smsbox forwarded message coding
Can have a try on SQLBox ? On Wed, Oct 5, 2022 at 4:55 PM Giulio Giovannini wrote: > Thanks Mesbahuddin. > > If you mean that I might not be actually using the get-url I have reported > in my email then I sure I am using that. All my inbound services are > defined in the same way, specifying messgaCoding=%c in the get-url. > Plus I see in the logs the HTTP GET performed by kannel to my endpoint and > I can see it is coming from that get-url configuration. > > Giulio > > On Wed, 5 Oct 2022 at 12:42, Mesbahuddin Malik > wrote: > >> Double check your config files. >> >> Regards >> Mesbah >> >> On Wed, Oct 5, 2022 at 3:53 PM Giulio Giovannini >> 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 >>> 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:] [SVC:] [ACT:] [BINF:] [FID:] [META:?smpp?] [from:] [to:xxx] [flags:-1:2:-1:0:-1] [msg:278:] [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= catch-all = true get-url = " http://.com/dispatcher?messageCoding=%c=%P=%p=%b=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: request: 'xxx!' url: 'http:/// .com/dispatcher?messageCoding=0===' 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
Re: Mismatch between received message coding and smsbox forwarded message coding
Thanks Mesbahuddin. If you mean that I might not be actually using the get-url I have reported in my email then I sure I am using that. All my inbound services are defined in the same way, specifying messgaCoding=%c in the get-url. Plus I see in the logs the HTTP GET performed by kannel to my endpoint and I can see it is coming from that get-url configuration. Giulio On Wed, 5 Oct 2022 at 12:42, Mesbahuddin Malik wrote: > Double check your config files. > > Regards > Mesbah > > On Wed, Oct 5, 2022 at 3:53 PM Giulio Giovannini > 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 >> 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:] [SVC:] [ACT:] [BINF:] >>> [FID:] [META:?smpp?] [from:] [to:xxx] [flags:-1:2:-1:0:-1] >>> [msg:278:] [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= >>> catch-all = true >>> get-url = " >>> http://.com/dispatcher?messageCoding=%c=%P=%p=%b=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: request: 'xxx!' url: >>> 'http:///.com/dispatcher?messageCoding=0===' >>> 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 >>> >>> >>> >>> >>> >>> >>>
Re: Mismatch between received message coding and smsbox forwarded message coding
Double check your config files. Regards Mesbah On Wed, Oct 5, 2022 at 3:53 PM Giulio Giovannini 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 > 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:] [SVC:] [ACT:] [BINF:] >> [FID:] [META:?smpp?] [from:] [to:xxx] [flags:-1:2:-1:0:-1] >> [msg:278:] [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= >> catch-all = true >> get-url = " >> http://.com/dispatcher?messageCoding=%c=%P=%p=%b=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: request: 'xxx!' url: >> 'http:///.com/dispatcher?messageCoding=0===' >> 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 >> >> >> >> >> >> >>
Re: Mismatch between received message coding and smsbox forwarded message coding
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 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:] [SVC:] [ACT:] [BINF:] > [FID:] [META:?smpp?] [from:] [to:xxx] [flags:-1:2:-1:0:-1] > [msg:278:] [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= > catch-all = true > get-url = " > http://.com/dispatcher?messageCoding=%c=%P=%p=%b=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: request: 'xxx!' url: > 'http:///.com/dispatcher?messageCoding=0===' > 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 > > > > > > >
