RE: Scheding light on "http-request-retry "

[Davor Spasoski]

Anyone?
From: Davor Spasoski
Sent: 07 March 2017 09:43
To: 'devel@kannel.org' <devel@kannel.org>
Subject: Scheding light on "http-request-retry "

I thought it would be better to re-post this question in the development forum:

This is potenitally a very nice feature, but the userguide description is very 
thin on details. Can someone explain:
a) how is this scenario trigerred? Is it by TCP timeout occuring while tryin 
got contact the service provider ot it can also be trigerred on HTTP errors 
different from 200 OK?
b) where exactly is the http message queue located in this case?

Thanks

Davor



Disclaimer: one.Vip DOO Skopje
This e-mail (including any attachments) is confidential and may be protected by 
legal privilege. If you are not the intended recipient, you should not copy it, 
re-transmit it, use it or disclose its contents, but should return it to the 
sender immediately and delete your copy from your system. Any unauthorized use 
or dissemination of this message in whole or in part is strictly prohibited. 
Please note that e-mails are susceptible to change. one.Vip DOO Skopje shall 
not be liable for the improper or incomplete transmission of the information 
contained in this communication nor for any delay in its receipt or damage to 
your system.
Please, do not print this e-mail unless it is necessary! Think about saving the 
environment!

: ???.??? ??? ??
 ??? ?? (??? ?? ? ?) ? ? ?  ??  
? ?? ?? ??. ??? ?? ??? ?? ?? ??? ??? ?? ?  
, ?? ? ?? ?? , ? ??? ?? ?? ? ? 
,  ?? ?? ?? ?? ?? ?? ? ?? ?? ? 
 ?? ?  ??? ? ?? ??  ??. ? 
??? ? ??  ?? ?? ?? ??? ?? ?? ?? ? ?? 
?. ?? ?? ?? ??  ? ?? ??  ?? 
???. ???.??? ??? ?? ?? ??? ??? ?? ??? ??? ? 
??? ??   ??  ,  ??? ??  
? ??? ?? ??? ??? ?? ?? ?? ??.
?? ?? ?? ??   ?? ? ??? ?? ? ?! ? ?? 
?!

Encodings

[Davor Spasoski]

Dear kannel users,

Can someone give precise information what happens encoding wise from smsbox to 
SMSC. I understand that as of 1.4.1:

Smsbox i expecting utf-8 by default
Communication smsbox <> bearerbox is only via utf-8
Bearerbox <> SMSC is supposed to be ISO-8859-1

But then we have alt-dcs and alt-addr-charset that are supposed to enable GSM-7 
alphabet between SMSC and bearerbox, but although documented, they both don't 
seem to work from 1.4.2 onwards. There is a slight difference when I add 
alt-charset=GSM, but it certainly is not sending GSM. (I get a lot of question 
marks until I get to 0x28 character)
What if I have specific SMSC that is using GSM-7 or even something more weird 
like Escaped ISO-8859-1 that combines ISO and GSM 7-bit.
Is SMSC - bearerbox in UTF-8 possible?

BR,

Davor Spasoski




Disclaimer: one.Vip DOO Skopje
This e-mail (including any attachments) is confidential and may be protected by 
legal privilege. If you are not the intended recipient, you should not copy it, 
re-transmit it, use it or disclose its contents, but should return it to the 
sender immediately and delete your copy from your system. Any unauthorized use 
or dissemination of this message in whole or in part is strictly prohibited. 
Please note that e-mails are susceptible to change. one.Vip DOO Skopje shall 
not be liable for the improper or incomplete transmission of the information 
contained in this communication nor for any delay in its receipt or damage to 
your system.
Please, do not print this e-mail unless it is necessary! Think about saving the 
environment!

: ???.??? ??? ??
 ??? ?? (??? ?? ? ?) ? ? ?  ??  
? ?? ?? ??. ??? ?? ??? ?? ?? ??? ??? ?? ?  
, ?? ? ?? ?? , ? ??? ?? ?? ? ? 
,  ?? ?? ?? ?? ?? ?? ? ?? ?? ? 
 ?? ?  ??? ? ?? ??  ??. ? 
??? ? ??  ?? ?? ?? ??? ?? ?? ?? ? ?? 
?. ?? ?? ?? ??  ? ?? ??  ?? 
???. ???.??? ??? ?? ?? ??? ??? ?? ??? ??? ? 
??? ??   ??  ,  ??? ??  
? ??? ?? ??? ??? ?? ?? ?? ??.
?? ?? ?? ??   ?? ? ??? ?? ? ?! ? ?? 
?!

default charset and alt-charset

[Davor Spasoski]

Following-up on our conversation regaring the encodings, I noticed one behviour 
of kannel that in my opinion colides with alt-charset=utf8 directive.

The SMSC supports UTF-8 with DCS=0 and it all works fine as long as I'm using 
characters of the GSM-7 bit (url-encoded in UTF-8). No need to use charset and 
dcs with smsbox.
But when using a character beyond GSM-7 bit, it's no longer automatically 
converted to UTF-8 by bearerbox, but to "?", unless I set coding=2 and 
charset=utf-8

What's the use of utf-8 as smsc alphabet if content provider still needs to 
watch the content of the message and set coding=2 and charset-utf-8 if 
necessary. Shouldn't kannel in this case assume:
- all input is utf-8  unless noted otherwise (dcs, charset)
- forward the text unchanged to SMSC, while preserving DCS=0

Similarly, even with SMSC with default alphabet of GSM 7-bit, isn't it better 
to assume:
- all input is utf-8  unless noted otherwise with charset
- transcode to UCS-2 with DCS=8 if input text (properly encoded in utf-8) 
contains anything outside GSM-7 bit alphabet.

If this is possible, please let me know how. If not, please consider adding 
this "auto-detect" option, I think it's going to be much more user friendly to 
content providers. Otherwise, smart quotes or similar, results in garbage on 
screen, because sender forgot to inspect and set coding=2 and charset=utf-8.

Davor Spasoski
VAS Manager /  Online and VAS Development

-Original Message-
From: Davor Spasoski
Sent: 07 April 2017 16:58
To: 'Stipe Tolj' <st...@kannel.org>
Cc: devel@kannel.org
Subject: RE: Encodings

Hi Stipe,

Thank you for your reply. I apologize for cross-posting. This is really usuful 
information.
I made some tests with few versions ftom 1.4.4 to SVN and it is consistent. 
Kill me if I'm wrong, but I remember that way long ago and with older versions 
and browsers I was able to url-encode the GSM characters with their hex value 
and get them properly on the handset, usually using alt-dcs=1 on our Comverse 
SMSC. My mistake with my tests is that I was doing the same now, but the browser

The enlitement for me is the alt-charset setting which was not clear to me from 
the userguide.

One more question: alt-addr-charset is there to prevent PDU breaking if 0x00 is 
in the address. But how come 0x00 in the short_message does not break it with 
GSM 7-bit?

Thanks a lot again!

Davor Spasoski

-Original Message-
From: devel [mailto:devel-boun...@kannel.org] On Behalf Of Stipe Tolj
Sent: 06 April 2017 11:18
Cc: devel@kannel.org
Subject: Re: Encodings

Am 02.04.17 21:57, schrieb Davor Spasoski:
> Dear kannel users,

Hi Davor,

please don't cross-post into several mailing list, we consider this spaming.

Your questions is more related to internals, so devel@ should be the right 
place to ask.

> Can someone give precise information what happens encoding wise from
> smsbox to SMSC. I understand that as of 1.4.1:
>
> Smsbox i expecting utf-8 by default

correct, the sendsms HTTP interface assumes UTF-8 encoding as input, (if not 
otherwise indicated via the 'coding' and 'charset' HTTP GET variables).

> Communication smsbox ßàbearerbox is only via utf-8

IF the message is considered to be textual (coding=0), yes, UTF-8 is the 
internal encoding.

IF coding=1 is indicated then it's raw byte stream, with no encoding implicated.

IF coding=2 then the internal encoding will leave UCS-2.

> Bearerbox ßàSMSC is supposed to be ISO-8859-1

nop, that's latin1. Depending on the SMSC type there are different upstream 
encodings used as default.

I.e. for SMPP the default encoding (aka data coding scheme, DCS 0x00) is GSM 
03.38.

> But then we have alt-dcs and alt-addr-charset that are supposed to
> enable GSM-7 alphabet between SMSC and bearerbox, but although
> documented, they both don’t seem to work from 1.4.2 onwards. There is
> a slight difference when I add alt-charset=GSM, but it certainly is
> not sending GSM. (I get a lot of question marks until I get to 0x28
> character)

The config 'alt-charset' in the SMPP config groups defines which default 
alphabet the SMSC assumes for it's DCS 0x00 encoding.

Keep in mind that 'alt-charset' relies on the iconv() library, and this does 
NOT include GSM 03.38, so there is no value for GSM 03.38 encoding that can be 
defined via 'alt-charset', which is also not required since it is default. Only 
all other default encodings can be switched to via this config directive.

> What if I have specific SMSC that is using GSM-7 or even something
> more weird like Escaped ISO-8859-1 that combines ISO and GSM 7-bit.
>
> Is SMSC – bearerbox in UTF-8 possible?

yes, 'alt-charset = UTF-8' would simply send the payload as UTF-8 encoded text. 
AFAIR, the HTTP SMSC types do this.

--
Best Regards,
Stipe Tolj

---
Düsseldorf, NRW, Germany

Kannel Foundation   

Scheding light on "http-request-retry "

[Davor Spasoski]

I thought it would be better to re-post this question in the development forum:

This is potenitally a very nice feature, but the userguide description is very 
thin on details. Can someone explain:
a) how is this scenario trigerred? Is it by TCP timeout occuring while tryin 
got contact the service provider ot it can also be trigerred on HTTP errors 
different from 200 OK?
b) where exactly is the http message queue located in this case?

Thanks

Davor Spasoski



Disclaimer: one.Vip DOO Skopje
This e-mail (including any attachments) is confidential and may be protected by 
legal privilege. If you are not the intended recipient, you should not copy it, 
re-transmit it, use it or disclose its contents, but should return it to the 
sender immediately and delete your copy from your system. Any unauthorized use 
or dissemination of this message in whole or in part is strictly prohibited. 
Please note that e-mails are susceptible to change. one.Vip DOO Skopje shall 
not be liable for the improper or incomplete transmission of the information 
contained in this communication nor for any delay in its receipt or damage to 
your system.
Please, do not print this e-mail unless it is necessary! Think about saving the 
environment!

: ???.??? ??? ??
 ??? ?? (??? ?? ? ?) ? ? ?  ??  
? ?? ?? ??. ??? ?? ??? ?? ?? ??? ??? ?? ?  
, ?? ? ?? ?? , ? ??? ?? ?? ? ? 
,  ?? ?? ?? ?? ?? ?? ? ?? ?? ? 
 ?? ?  ??? ? ?? ??  ??. ? 
??? ? ??  ?? ?? ?? ??? ?? ?? ?? ? ?? 
?. ?? ?? ?? ??  ? ?? ??  ?? 
???. ???.??? ??? ?? ?? ??? ??? ?? ??? ??? ? 
??? ??   ??  ,  ??? ??  
? ??? ?? ??? ??? ?? ?? ?? ??.
?? ?? ?? ??   ?? ? ??? ?? ? ?! ? ?? 
?!

RE: Encodings

[Davor Spasoski]

Hi Stipe,

Thank you for your reply. I apologize for cross-posting. This is really usuful 
information.
I made some tests with few versions ftom 1.4.4 to SVN and it is consistent. 
Kill me if I'm wrong, but I remember that way long ago and with older versions 
and browsers I was able to url-encode the GSM characters with their hex value 
and get them properly on the handset, usually using alt-dcs=1 on our Comverse 
SMSC. My mistake with my tests is that I was doing the same now, but the browser

The enlitement for me is the alt-charset setting which was not clear to me from 
the userguide.

One more question: alt-addr-charset is there to prevent PDU breaking if 0x00 is 
in the address. But how come 0x00 in the short_message does not break it with 
GSM 7-bit?

Thanks a lot again!

Davor Spasoski

-Original Message-
From: devel [mailto:devel-boun...@kannel.org] On Behalf Of Stipe Tolj
Sent: 06 April 2017 11:18
Cc: devel@kannel.org
Subject: Re: Encodings

Am 02.04.17 21:57, schrieb Davor Spasoski:
> Dear kannel users,

Hi Davor,

please don't cross-post into several mailing list, we consider this spaming.

Your questions is more related to internals, so devel@ should be the right 
place to ask.

> Can someone give precise information what happens encoding wise from
> smsbox to SMSC. I understand that as of 1.4.1:
>
> Smsbox i expecting utf-8 by default

correct, the sendsms HTTP interface assumes UTF-8 encoding as input, (if not 
otherwise indicated via the 'coding' and 'charset' HTTP GET variables).

> Communication smsbox ßàbearerbox is only via utf-8

IF the message is considered to be textual (coding=0), yes, UTF-8 is the 
internal encoding.

IF coding=1 is indicated then it's raw byte stream, with no encoding implicated.

IF coding=2 then the internal encoding will leave UCS-2.

> Bearerbox ßàSMSC is supposed to be ISO-8859-1

nop, that's latin1. Depending on the SMSC type there are different upstream 
encodings used as default.

I.e. for SMPP the default encoding (aka data coding scheme, DCS 0x00) is GSM 
03.38.

> But then we have alt-dcs and alt-addr-charset that are supposed to
> enable GSM-7 alphabet between SMSC and bearerbox, but although
> documented, they both don’t seem to work from 1.4.2 onwards. There is
> a slight difference when I add alt-charset=GSM, but it certainly is
> not sending GSM. (I get a lot of question marks until I get to 0x28
> character)

The config 'alt-charset' in the SMPP config groups defines which default 
alphabet the SMSC assumes for it's DCS 0x00 encoding.

Keep in mind that 'alt-charset' relies on the iconv() library, and this does 
NOT include GSM 03.38, so there is no value for GSM 03.38 encoding that can be 
defined via 'alt-charset', which is also not required since it is default. Only 
all other default encodings can be switched to via this config directive.

> What if I have specific SMSC that is using GSM-7 or even something
> more weird like Escaped ISO-8859-1 that combines ISO and GSM 7-bit.
>
> Is SMSC – bearerbox in UTF-8 possible?

yes, 'alt-charset = UTF-8' would simply send the payload as UTF-8 encoded text. 
AFAIR, the HTTP SMSC types do this.

--
Best Regards,
Stipe Tolj

---
Düsseldorf, NRW, Germany

Kannel Foundation tolj.org system architecture
http://www.kannel.org/http://www.tolj.org/

st...@kannel.org  s...@tolj.org
---





Disclaimer: one.Vip DOO Skopje
This e-mail (including any attachments) is confidential and may be protected by 
legal privilege. If you are not the intended recipient, you should not copy it, 
re-transmit it, use it or disclose its contents, but should return it to the 
sender immediately and delete your copy from your system. Any unauthorized use 
or dissemination of this message in whole or in part is strictly prohibited. 
Please note that e-mails are susceptible to change. one.Vip DOO Skopje shall 
not be liable for the improper or incomplete transmission of the information 
contained in this communication nor for any delay in its receipt or damage to 
your system.
Please, do not print this e-mail unless it is necessary! Think about saving the 
environment!

Напомена: оне.Вип ДОО Скопје
Оваа електронска порака (вклучувајќи ги и прилозите) е доверлива и може да биде 
заштитена со правни привилегии. Доколку не сте лицето на кое таа му е наменета 
пораката, не треба да ја копирате, дистрибуирате или да ја откривате нејзината 
содржина, туку веднаш да ја препратите до испраќачот и да ја избришете 
оригиналната порака и сите нејзини копии од Вашиот компјутерски систем. Секое 
неовластено користење на оваа порака во целост или делови од истата е строго 
забрането. Ве молиме да забележите дека електронските пораки се подложни на 
промени. оне.Вип ДОО Скопје 

RE: Scheding light on "http-request-retry "

[Davor Spasoski]

Six months and no reply? Come on. There must be someone who knows a bit more on 
this.

Davor Spasoski

From: Davor Spasoski
Sent: Tuesday, March 07, 2017 9:13 AM
To: devel@kannel.org
Subject: Scheding light on "http-request-retry "

I thought it would be better to re-post this question in the development forum:

This is potenitally a very nice feature, but the userguide description is very 
thin on details. Can someone explain:
a) how is this scenario trigerred? Is it by TCP timeout occuring while tryin 
got contact the service provider ot it can also be trigerred on HTTP errors 
different from 200 OK?
b) where exactly is the http message queue located in this case?

Thanks

Davor Spasoski



Disclaimer: one.Vip DOO Skopje
This e-mail (including any attachments) is confidential and may be protected by 
legal privilege. If you are not the intended recipient, you should not copy it, 
re-transmit it, use it or disclose its contents, but should return it to the 
sender immediately and delete your copy from your system. Any unauthorized use 
or dissemination of this message in whole or in part is strictly prohibited. 
Please note that e-mails are susceptible to change. one.Vip DOO Skopje shall 
not be liable for the improper or incomplete transmission of the information 
contained in this communication nor for any delay in its receipt or damage to 
your system.
Please, do not print this e-mail unless it is necessary! Think about saving the 
environment!

: ???.??? ??? ??
 ??? ?? (??? ?? ? ?) ? ? ?  ??  
? ?? ?? ??. ??? ?? ??? ?? ?? ??? ??? ?? ?  
, ?? ? ?? ?? , ? ??? ?? ?? ? ? 
,  ?? ?? ?? ?? ?? ?? ? ?? ?? ? 
 ?? ?  ??? ? ?? ??  ??. ? 
??? ? ??  ?? ?? ?? ??? ?? ?? ?? ? ?? 
?. ?? ?? ?? ??  ? ?? ??  ?? 
???. ???.??? ??? ?? ?? ??? ??? ?? ??? ??? ? 
??? ??   ??  ,  ??? ??  
? ??? ?? ??? ??? ?? ?? ?? ??.
?? ?? ?? ??   ?? ? ??? ?? ? ?! ? ?? 
?!

RE: Two or more word keyword

[Davor Spasoski]

Hi,

Yes, regex is tricky. Try the following example:
(?i)(stop)(\ )(all)

You can use this resource to build your regex graphically:  https://txt2re.com/
And then the following to check: https://regex101.com/

BR,

Davor

From: devel  On Behalf Of Yahya M.
Sent: Monday, November 12, 2018 10:11 AM
To: amal...@kannel.org
Cc: devel@kannel.org
Subject: Re: Two or more word keyword

Thanks a lot. But, I don't know how to use regex properly. i have been trying 
this for over three weeks now and I need some regex examples for these two 
keywords. "stop all" and "stop B" in different variations like "STOP ALL", 
"Stop All", "Stop all", "STOP B", "Stop B", "Stop b".

thanks.

On Mon, Nov 12, 2018 at 11:46 AM 
mailto:amal...@kannel.org>> wrote:
Hi,

please check userguide:
https://kannel.org/download/kannel-userguide-snapshot/userguide.html#AEN4069

Especially:
keyword-regex

POSIX regular expression

This field may be used to enable service-selection based on a regular 
expression. You can define either keyword or keyword-regex in configuration, 
but not both in the same sms-service. keyword-regex is case sensitive. See 
section on Regular 
Expressions
 for details.


Thanks,
Alex

P.S. This question belongs to users mailing list and not devel.


Am 12.11.2018 um 09:33 schrieb Yahya M. 
mailto:yahiyamohammed...@gmail.com>>:

I want my system to respond to a keywords that made up of two or more words 
like "stop all" or "stop A". I tried to set this up. but it responds with 
unknown keyword reply. default service. Is there anyway I can achieve this? 
Give me some examples please. thanks







Disclaimer: one.Vip DOOEL Skopje
This e-mail (including any attachments) is confidential and may be protected by 
legal privilege. If you are not the intended recipient, you should not copy it, 
re-transmit it, use it or disclose its contents, but should return it to the 
sender immediately and delete your copy from your system. Any unauthorized use 
or dissemination of this message in whole or in part is strictly prohibited. 
Please note that e-mails are susceptible to change. one.Vip DOOEL Skopje shall 
not be liable for the improper or incomplete transmission of the information 
contained in this communication nor for any delay in its receipt or damage to 
your system.
Please, do not print this e-mail unless it is necessary! Think about saving the 
environment!

Напомена: оне.Вип ДООЕЛ Скопје
Оваа електронска порака (вклучувајќи ги и прилозите) е доверлива и може да биде 
заштитена со правни привилегии. Доколку не сте лицето на кое таа му е наменета 
пораката, не треба да ја копирате, дистрибуирате или да ја откривате нејзината 
содржина, туку веднаш да ја препратите до испраќачот и да ја избришете 
оригиналната порака и сите нејзини копии од Вашиот компјутерски систем. Секое 
неовластено користење на оваа порака во целост или делови од истата е строго 
забрането. Ве молиме да забележите дека електронските пораки се подложни на 
промени. оне.Вип ДООЕЛ Скопје не презема одговорност за несоодветно или 
нецелосно пренесување на информациите содржани во оваа комуникација, ниту пак 
за било какво задоцнување на приемот или оштетувања на вашиот систем.
Ве молиме не ја печатете оваа порака освен ако не е неопходно! Зачувајте ја 
природата!

RE: Two or more word keyword

[Davor Spasoski]

Don’t forget the start and end anchors as kannel wants them

^(?i)(stop)(\ )(all)$

Davor

From: Davor Spasoski
Sent: Monday, November 12, 2018 11:09 AM
To: 'Yahya M.' ; amal...@kannel.org
Cc: devel@kannel.org
Subject: RE: Two or more word keyword

Hi,

Yes, regex is tricky. Try the following example:
(?i)(stop)(\ )(all)

You can use this resource to build your regex graphically:  https://txt2re.com/
And then the following to check: https://regex101.com/

BR,

Davor

From: devel mailto:devel-boun...@kannel.org>> On 
Behalf Of Yahya M.
Sent: Monday, November 12, 2018 10:11 AM
To: amal...@kannel.org<mailto:amal...@kannel.org>
Cc: devel@kannel.org<mailto:devel@kannel.org>
Subject: Re: Two or more word keyword

Thanks a lot. But, I don't know how to use regex properly. i have been trying 
this for over three weeks now and I need some regex examples for these two 
keywords. "stop all" and "stop B" in different variations like "STOP ALL", 
"Stop All", "Stop all", "STOP B", "Stop B", "Stop b".

thanks.

On Mon, Nov 12, 2018 at 11:46 AM 
mailto:amal...@kannel.org>> wrote:
Hi,

please check userguide:
https://kannel.org/download/kannel-userguide-snapshot/userguide.html#AEN4069

Especially:
keyword-regex

POSIX regular expression

This field may be used to enable service-selection based on a regular 
expression. You can define either keyword or keyword-regex in configuration, 
but not both in the same sms-service. keyword-regex is case sensitive. See 
section on Regular 
Expressions<https://kannel.org/download/kannel-userguide-snapshot/userguide.html#regular-expressions>
 for details.


Thanks,
Alex

P.S. This question belongs to users mailing list and not devel.

Am 12.11.2018 um 09:33 schrieb Yahya M. 
mailto:yahiyamohammed...@gmail.com>>:

I want my system to respond to a keywords that made up of two or more words 
like "stop all" or "stop A". I tried to set this up. but it responds with 
unknown keyword reply. default service. Is there anyway I can achieve this? 
Give me some examples please. thanks







Disclaimer: one.Vip DOOEL Skopje
This e-mail (including any attachments) is confidential and may be protected by 
legal privilege. If you are not the intended recipient, you should not copy it, 
re-transmit it, use it or disclose its contents, but should return it to the 
sender immediately and delete your copy from your system. Any unauthorized use 
or dissemination of this message in whole or in part is strictly prohibited. 
Please note that e-mails are susceptible to change. one.Vip DOOEL Skopje shall 
not be liable for the improper or incomplete transmission of the information 
contained in this communication nor for any delay in its receipt or damage to 
your system.
Please, do not print this e-mail unless it is necessary! Think about saving the 
environment!

Напомена: оне.Вип ДООЕЛ Скопје
Оваа електронска порака (вклучувајќи ги и прилозите) е доверлива и може да биде 
заштитена со правни привилегии. Доколку не сте лицето на кое таа му е наменета 
пораката, не треба да ја копирате, дистрибуирате или да ја откривате нејзината 
содржина, туку веднаш да ја препратите до испраќачот и да ја избришете 
оригиналната порака и сите нејзини копии од Вашиот компјутерски систем. Секое 
неовластено користење на оваа порака во целост или делови од истата е строго 
забрането. Ве молиме да забележите дека електронските пораки се подложни на 
промени. оне.Вип ДООЕЛ Скопје не презема одговорност за несоодветно или 
нецелосно пренесување на информациите содржани во оваа комуникација, ниту пак 
за било какво задоцнување на приемот или оштетувања на вашиот систем.
Ве молиме не ја печатете оваа порака освен ако не е неопходно! Зачувајте ја 
природата!

RE: Routing problem with bearerbox (kannel svn 5280)

[Davor Spasoski]

And/or use the smsc-id in the push URL. But in that case the forced-smsc might 
contradict, so make a few tests.
davor
From: devel  On Behalf Of Ahmed Shabana
Sent: Monday, August 26, 2019 9:03 AM
To: Edjé DOSSEH ; devel@kannel.org
Subject: RE: Routing problem with bearerbox (kannel svn 5280)

Check allowed-smsc and preferred-smsc parameters



Best regards ,
Ahmed Shabana
+20 1003325373

From: devel mailto:devel-boun...@kannel.org>> On 
Behalf Of Edjé DOSSEH
Sent: Monday, August 26, 2019 6:59 AM
To: devel@kannel.org
Subject: Routing problem with bearerbox (kannel svn 5280)

Dear All,

  I'm facing with a problem on bearerbox. I installed kannel with opensmppbox  
(SVN 5285) on a centos 7 server. I set 2 SMSCs according with Mobile operators 
links (Operators A and B). But we notice for push SMS that, when messages are 
sent to Operator A, it can be routed to Operator B SMSC (who doesn't accept it) 
so transmission is failed. I receive this error:

2019-08-23 16:37:29 [41172] [6] DEBUG: SMPP PDU 0x7f36b4000a00 dump:
2019-08-23 16:37:29 [41172] [6] DEBUG:   type_name: submit_sm_resp
2019-08-23 16:37:29 [41172] [6] DEBUG:   command_id: 2147483652 = 0x8004
2019-08-23 16:37:29 [41172] [6] DEBUG:   command_status: 11 = 0x000b
2019-08-23 16:37:29 [41172] [6] DEBUG:   sequence_number: 27 = 0x001b
2019-08-23 16:37:29 [41172] [6] DEBUG:   message_id: "25D512F6"
2019-08-23 16:37:29 [41172] [6] DEBUG: SMPP PDU dump ends.
2019-08-23 16:37:29 [41172] [6] ERROR: SMPP[OPERATOR B]: SMSC returned error 
code 0x000b (Invalid Destination Address) in response to submit_sm PDU.

In kannel config, i use forced-smsc for sendsms-user configuration.
And the URLs used for sending are set in a script according to the destination 
address.

Please is it a well-known problem or due to a missed compilation/installation 
or missed configuration? I notice that on stable version (installed by rpm), i 
had'nt this problem.

Very thanks for your help in advance.



Disclaimer: one.Vip DOOEL Skopje
This e-mail (including any attachments) is confidential and may be protected by 
legal privilege. If you are not the intended recipient, you should not copy it, 
re-transmit it, use it or disclose its contents, but should return it to the 
sender immediately and delete your copy from your system. Any unauthorized use 
or dissemination of this message in whole or in part is strictly prohibited. 
Please note that e-mails are susceptible to change. one.Vip DOOEL Skopje shall 
not be liable for the improper or incomplete transmission of the information 
contained in this communication nor for any delay in its receipt or damage to 
your system.
Please, do not print this e-mail unless it is necessary! Think about saving the 
environment!

Напомена: оне.Вип ДООЕЛ Скопје
Оваа електронска порака (вклучувајќи ги и прилозите) е доверлива и може да биде 
заштитена со правни привилегии. Доколку не сте лицето на кое таа му е наменета 
пораката, не треба да ја копирате, дистрибуирате или да ја откривате нејзината 
содржина, туку веднаш да ја препратите до испраќачот и да ја избришете 
оригиналната порака и сите нејзини копии од Вашиот компјутерски систем. Секое 
неовластено користење на оваа порака во целост или делови од истата е строго 
забрането. Ве молиме да забележите дека електронските пораки се подложни на 
промени. оне.Вип ДООЕЛ Скопје не презема одговорност за несоодветно или 
нецелосно пренесување на информациите содржани во оваа комуникација, ниту пак 
за било какво задоцнување на приемот или оштетувања на вашиот систем.
Ве молиме не ја печатете оваа порака освен ако не е неопходно! Зачувајте ја 
природата!