from:"Davor Spasoski"

Re: Pipe Symbol Issue

2020-08-18 Thread Davor Spasoski




I’m intrigued by Jeff’s interpretation, which is true, but, isn’t alt-charset=utf-8 ensuring transparency of kannel for the encoding and practically leaving the transcoding to the SMSC? I see only this benefit with this setting, offloading the content provider
 from always having to switch coding whenever there is a character outside of gsm 7-bit. Other than that, what’s the use?


Br,
Davor


On Aug 18, 2020, at 9:32 PM, Jeff Thorn  wrote:




The pipe symbol is not a standard GSM 7 character. It needs to be escaped when using the default 7 bit charset (https://www.developershome.com/sms/gsmAlphabet.asp).  Try changing
 your "coding" param to 1 to for 8 bit characters, or 2 if you need extended utf8 characters. https://kannel.org/download/1.5.0/userguide-1.5.0/userguide.html#AEN4623








Jeff Thorn
CEO
Thorn Technologies, LLC
www.thorntech.com
@thorntech | 
LinkedIn | 
Facebook














On Tue, Aug 18, 2020 at 2:53 PM Wan Md Arif Noor Bin. Wan Nizam  wrote:




Hi Anyone?
 

I’ve updated to svn-r5302M and still seeing the same problem.
 
26892:2020-08-19 02:45:42 [9506] [7] DEBUG: SMPP PDU 0x7efcd8006d30 dump:
26893:2020-08-19 02:45:42 [9506] [7] DEBUG:   type_name: submit_sm
26894:2020-08-19 02:45:42 [9506] [7] DEBUG:   command_id: 4 = 0x0004
26895:2020-08-19 02:45:42 [9506] [7] DEBUG:   command_status: 0 = 0x
26896:2020-08-19 02:45:42 [9506] [7] DEBUG:   sequence_number: 8 = 0x0008
26897:2020-08-19 02:45:42 [9506] [7] DEBUG:   service_type: NULL
26898:2020-08-19 02:45:42 [9506] [7] DEBUG:   source_addr_ton: 0 = 0x
26899:2020-08-19 02:45:42 [9506] [7] DEBUG:   source_addr_npi: 1 = 0x0001
26900:2020-08-19 02:45:42 [9506] [7] DEBUG:   source_addr: ""
26901:2020-08-19 02:45:42 [9506] [7] DEBUG:   dest_addr_ton: 1 = 0x0001
26902:2020-08-19 02:45:42 [9506] [7] DEBUG:   dest_addr_npi: 1 = 0x0001
26903:2020-08-19 02:45:42 [9506] [7] DEBUG:   destination_addr: ""
26904:2020-08-19 02:45:42 [9506] [7] DEBUG:   esm_class: 3 = 0x0003
26905:2020-08-19 02:45:42 [9506] [7] DEBUG:   protocol_id: 0 = 0x
26906:2020-08-19 02:45:42 [9506] [7] DEBUG:   priority_flag: 0 = 0x
26907:2020-08-19 02:45:42 [9506] [7] DEBUG:   schedule_delivery_time: NULL
26908:2020-08-19 02:45:42 [9506] [7] DEBUG:   validity_period: NULL
26909:2020-08-19 02:45:42 [9506] [7] DEBUG:   registered_delivery: 0 = 0x
26910:2020-08-19 02:45:42 [9506] [7] DEBUG:   replace_if_present_flag: 0 = 0x
26911:2020-08-19 02:45:42 [9506] [7] DEBUG:   data_coding: 0 = 0x
26912:2020-08-19 02:45:42 [9506] [7] DEBUG:   sm_default_msg_id: 0 = 0x
26913:2020-08-19 02:45:42 [9506] [7] DEBUG:   sm_length: 2 = 0x0002
26914:2020-08-19 02:45:42 [9506] [7] DEBUG:   short_message:
26915:2020-08-19 02:45:42 [9506] [7] DEBUG:    Octet string at 0x7efcd80058f0:
26916:2020-08-19 02:45:42 [9506] [7] DEBUG:  len:  2
26917:2020-08-19 02:45:42 [9506] [7] DEBUG:  size: 1024
26918:2020-08-19 02:45:42 [9506] [7] DEBUG:  immutable: 0
26919:2020-08-19 02:45:42 [9506] [7] DEBUG:  data: 
1b 40 .@
26920:2020-08-19 02:45:42 [9506] [7] DEBUG:    Octet string dump ends.
26921:2020-08-19 02:45:42 [9506] [7] DEBUG: SMPP PDU dump ends.
 
Best Regards

 


From: users 
On Behalf Of Wan Md Arif Noor Bin. Wan Nizam
Sent: Tuesday, August 18, 2020 6:05 PM
To: kannel users@kannel.org 
Subject: Pipe Symbol Issue


 
Hi There,
 
I’ve notice that sending | symbol converted into @ instead regardless alt-charset set to UTF-8 or not. Kindly assist.
 
CGI :
 
curl "localhost:13017/cgi-bin/sendsms?username=smsSMPP2=smsPass=68123=601132495424=%7c"
 
Kannel bearerbox version `svn-r5299M'.
 
Debug Log :
 
291852:2020-08-18 17:44:37 [62170] [7] DEBUG: SMPP PDU 0x7fa23c01c3a0 dump:
291853:2020-08-18 17:44:37 [62170] [7] DEBUG:   type_name: submit_sm
291854:2020-08-18 17:44:37 [62170] [7] DEBUG:   command_id: 4 = 0x0004
291855:2020-08-18 17:44:37 [62170] [7] DEBUG:   command_status: 0 = 0x
291856:2020-08-18 17:44:37 [62170] [7] DEBUG:   sequence_number: 9333 = 0x2475
291857:2020-08-18 17:44:37 [62170] [7] DEBUG:   service_type: NULL
291858:2020-08-18 17:44:37 [62170] [7] DEBUG:   source_addr_ton: 0 = 0x
291859:2020-08-18 17:44:37 [62170] [7] DEBUG:   source_addr_npi: 1 = 0x0001
291860:2020-08-18 17:44:37 [62170] [7] DEBUG:   source_addr: "68123"
291861:2020-08-18 17:44:37 [62170] [7] DEBUG:   dest_addr_ton: 1 = 0x0001
291862:2020-08-18 17:44:37 [62170] [7] DEBUG:   dest_addr_npi: 1 = 0x0001
291863:2020-08-18 17:44:37 [62170] [7] DEBUG:   destination_addr: "601132495424"
291864:2020-08-18 17:44:37 [62170] [7] DEBUG:   esm_class: 3 = 0x0003
291865:2020-08-18 17:44:37 [62170] [7] DEBUG:

Re: Kannel Support - memory leak

2020-08-10 Thread Davor Spasoski

Despite being an open source supporter through and through, I’d have to say if you have 3.5M routes, maybe you are a good candidate for a professional support.
And no, I’m not affiliated to any of the companies offering that kind of kannel support.

Good luck 

On Aug 10, 2020, at 19:33, "ploep...@fibernetics.ca" wrote:

We have a 4 node Kannel cluster, which after bearerbox consumes all the ram on the box, usually about once a day, crashes and we have separate monitoring scripts to shutdown the remaining processes and start them back up.
Every time we reload the number route database, bearerbox uses an extra 1.8GB of ram. Our number routing database containg 3.5M records.
We are looking to get this resolved.

Peter Loeppky | Voice Network System Specialist | Fibernetics
+1-519-489-6700 x675 | www.fibernetics.ca

Disclaimer: A1 Makedonija 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. A1 Makedonija 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!

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

Re: GSM Characters

2020-07-18 Thread Davor Spasoski

Hi,

Do you know your provider’s default encoding (when dcs=0 or 241)?
Alt-charset insteucts kannel to send payload to smsc encoded as utf-8.
I’ve seen lately smscs supporting this but then it’s also a question of 
transcoding on the smsc side. Remember, on the handset you have only two 
options, gsm 7-bit which gives you up to 160 chars per sms and ucs-2 which 
gives you up to 70.
Go back to basics. Detect the default smsc alphabet. Comment the alt-charset 
line, send the @ sign (leave charset and coding empty) and check if you get @ 
or inverted exclamation sign ¡
If first, you have gsm default smsc alphabet, if ¡, you have to set alt-charset 
to Latin-1 or something.
Alt-dcs=1 is used when the default smsc alphabet is not set to gsm 7-bit. If 
you set alt-dcs=1, don’t set alt-charset and you know the set of characters you 
can expect on the handset. Remember, tou always address to smsbox in utf-8, and 
if you have characters beyond gsm 7-bit you must flag coding=2

BR,
Davor

> On Jul 18, 2020, at 04:48, Eichi  wrote:
>
> Hi There,
>
> The test was sent with alt-charset=utf-8 in the configuration and with 
> coding=0 and alt-dcs=1 in the smspush cgi. With alt-dcs=0 the message 
> reveiced on phone is B¤B!CèCΠC_CÆB'B?C¤C6C1C< but by using alt-dcs=1 it 
> becomes $@[\\]^_`{|}~ instead.
>
> While it will work when encoded using ucs2, it will reduce the character 
> count. Could it be that the provider is modifying it as sending 
> @£$¥èéùìòÇØøÅåΔΦΓΛΩΠΨΣΘΞ€ÆæßÉ with the alt-dcs=1 settings works.
>
>
> Best Regards.
>
>
>> On 7/17/2020 4:45 PM, Davor Spasoski wrote:
>> 1. Some of your characters are supported in the default GS 7-bit alphabet: 
>> https://www.developershome.com/sms/gsmAlphabet.asp
>> 2. All of the characters are supported if you use UCS-2 encoding.
>>
>> - These are the only two universally supported alphabets on handsets.
>> - You encode your request towards kannel (smsbox) using UTF-8 encoding. For 
>> 1 nothing to set, for 2, you need to set coding=2 and charset=utf-8
>>
>> For 1, some of your characters will be transcoded to ?
>>
>> Bottom line, check your encoding towards kannel.
>>
>> Davor Spasoski
>>
>>
>> -Original Message-
>> From: users  On Behalf Of Eichi
>> Sent: Friday, July 17, 2020 4:23 AM
>> To: users 
>> Subject: GSM Characters
>>
>> Hi Kannel Users,
>>
>> Please advise if these characters (¤¡ÄÖÑÜ§¿äöñü) are supported in Kannel? 
>> Every time I send it, these characters is converted to $@[\\]^_`{|}~ instead.
>>
>>
>> 1829895:2020-07-17 09:56:19 [4432] [7] DEBUG: SMPP[smppConnection2]:
>> Sending PDU:
>> 1829896:2020-07-17 09:56:19 [4432] [7] DEBUG: SMPP PDU 0x7f6c04003ea0 dump:
>> 1829897:2020-07-17 09:56:19 [4432] [7] DEBUG:   type_name: submit_sm
>> 1829898:2020-07-17 09:56:19 [4432] [7] DEBUG:   command_id: 4 = 0x0004
>> 1829899:2020-07-17 09:56:19 [4432] [7] DEBUG:   command_status: 0 =
>> 0x
>> 1829900:2020-07-17 09:56:19 [4432] [7] DEBUG:   sequence_number: 20013 = 
>> 0x4e2d
>> 1829901:2020-07-17 09:56:19 [4432] [7] DEBUG:   service_type: NULL
>> 1829902:2020-07-17 09:56:19 [4432] [7] DEBUG:   source_addr_ton: 0 =
>> 0x
>> 1829903:2020-07-17 09:56:19 [4432] [7] DEBUG:   source_addr_npi: 1 =
>> 0x0001
>> 1829904:2020-07-17 09:56:19 [4432] [7] DEBUG:   source_addr: "x"
>> 1829905:2020-07-17 09:56:19 [4432] [7] DEBUG:   dest_addr_ton: 1 =
>> 0x0001
>> 1829906:2020-07-17 09:56:19 [4432] [7] DEBUG:   dest_addr_npi: 1 =
>> 0x0001
>> 1829907:2020-07-17 09:56:19 [4432] [7] DEBUG:   destination_addr: "xx"
>> 1829908:2020-07-17 09:56:19 [4432] [7] DEBUG:   esm_class: 3 = 0x0003
>> 1829909:2020-07-17 09:56:19 [4432] [7] DEBUG:   protocol_id: 0 = 0x
>> 1829910:2020-07-17 09:56:19 [4432] [7] DEBUG:   priority_flag: 0 =
>> 0x
>> 1829911:2020-07-17 09:56:19 [4432] [7] DEBUG: schedule_delivery_time: NULL
>> 1829912:2020-07-17 09:56:19 [4432] [7] DEBUG:   validity_period: NULL
>> 1829913:2020-07-17 09:56:19 [4432] [7] DEBUG: registered_delivery: 0 =
>> 0x
>> 1829914:2020-07-17 09:56:19 [4432] [7] DEBUG: replace_if_present_flag: 0 = 
>> 0x
>> 1829915:2020-07-17 09:56:19 [4432] [7] DEBUG:   data_coding: 241 =
>> 0x00f1
>> 1829916:2020-07-17 09:56:19 [4432] [7] DEBUG:   sm_default_msg_id: 0 =
>> 0x
>> 1829917:2020-07-17 09:56:19 [4432] [7] DEBUG:   sm_length: 12 = 0x000c
>> 1829918:2020-07-17 09:56:19 [4432] [7] DEBUG:   short_message:
>> "$@[\\]^_`{|}~"
>> 1829919:2020-07-17 09:56:19 [4432] [7] DEBUG: SMPP PDU

RE: GSM Characters

2020-07-17 Thread Davor Spasoski

1. Some of your characters are supported in the default GS 7-bit alphabet: 
https://www.developershome.com/sms/gsmAlphabet.asp
2. All of the characters are supported if you use UCS-2 encoding.

- These are the only two universally supported alphabets on handsets.
- You encode your request towards kannel (smsbox) using UTF-8 encoding. For 1 
nothing to set, for 2, you need to set coding=2 and charset=utf-8

For 1, some of your characters will be transcoded to ?

Bottom line, check your encoding towards kannel.

Davor Spasoski


-Original Message-
From: users  On Behalf Of Eichi
Sent: Friday, July 17, 2020 4:23 AM
To: users 
Subject: GSM Characters

Hi Kannel Users,

Please advise if these characters (¤¡ÄÖÑÜ§¿äöñü) are supported in Kannel? Every 
time I send it, these characters is converted to $@[\\]^_`{|}~ instead.


1829895:2020-07-17 09:56:19 [4432] [7] DEBUG: SMPP[smppConnection2]:
Sending PDU:
1829896:2020-07-17 09:56:19 [4432] [7] DEBUG: SMPP PDU 0x7f6c04003ea0 dump:
1829897:2020-07-17 09:56:19 [4432] [7] DEBUG:   type_name: submit_sm
1829898:2020-07-17 09:56:19 [4432] [7] DEBUG:   command_id: 4 = 0x0004
1829899:2020-07-17 09:56:19 [4432] [7] DEBUG:   command_status: 0 =
0x
1829900:2020-07-17 09:56:19 [4432] [7] DEBUG:   sequence_number: 20013 = 
0x4e2d
1829901:2020-07-17 09:56:19 [4432] [7] DEBUG:   service_type: NULL
1829902:2020-07-17 09:56:19 [4432] [7] DEBUG:   source_addr_ton: 0 =
0x
1829903:2020-07-17 09:56:19 [4432] [7] DEBUG:   source_addr_npi: 1 =
0x0001
1829904:2020-07-17 09:56:19 [4432] [7] DEBUG:   source_addr: "x"
1829905:2020-07-17 09:56:19 [4432] [7] DEBUG:   dest_addr_ton: 1 =
0x0001
1829906:2020-07-17 09:56:19 [4432] [7] DEBUG:   dest_addr_npi: 1 =
0x0001
1829907:2020-07-17 09:56:19 [4432] [7] DEBUG:   destination_addr: "xx"
1829908:2020-07-17 09:56:19 [4432] [7] DEBUG:   esm_class: 3 = 0x0003
1829909:2020-07-17 09:56:19 [4432] [7] DEBUG:   protocol_id: 0 = 0x
1829910:2020-07-17 09:56:19 [4432] [7] DEBUG:   priority_flag: 0 =
0x
1829911:2020-07-17 09:56:19 [4432] [7] DEBUG: schedule_delivery_time: NULL
1829912:2020-07-17 09:56:19 [4432] [7] DEBUG:   validity_period: NULL
1829913:2020-07-17 09:56:19 [4432] [7] DEBUG: registered_delivery: 0 =
0x
1829914:2020-07-17 09:56:19 [4432] [7] DEBUG: replace_if_present_flag: 0 = 
0x
1829915:2020-07-17 09:56:19 [4432] [7] DEBUG:   data_coding: 241 =
0x00f1
1829916:2020-07-17 09:56:19 [4432] [7] DEBUG:   sm_default_msg_id: 0 =
0x
1829917:2020-07-17 09:56:19 [4432] [7] DEBUG:   sm_length: 12 = 0x000c
1829918:2020-07-17 09:56:19 [4432] [7] DEBUG:   short_message:
"$@[\\]^_`{|}~"
1829919:2020-07-17 09:56:19 [4432] [7] DEBUG: SMPP PDU dump ends.
1829920:2020-07-17 09:56:19 [4432] [7] DEBUG: SMPP[smppConnection2]:
throughput (1.00,15.00)
1829921:2020-07-17 09:56:19 [4432] [7] DEBUG: SMPP[smppConnection2]:
throughput (1.00,15.00)
1829922:2020-07-17 09:56:19 [4432] [7] DEBUG: SMPP[smppConnection2]: Got
PDU:
1829923:2020-07-17 09:56:19 [4432] [7] DEBUG: SMPP PDU 0x7f6c04003ea0 dump:
1829924:2020-07-17 09:56:19 [4432] [7] DEBUG:   type_name: submit_sm_resp
1829925:2020-07-17 09:56:19 [4432] [7] DEBUG:   command_id: 2147483652 =
0x8004
1829926:2020-07-17 09:56:19 [4432] [7] DEBUG:   command_status: 0 =
0x
1829927:2020-07-17 09:56:19 [4432] [7] DEBUG:   sequence_number: 20013 = 
0x4e2d
1829928:2020-07-17 09:56:19 [4432] [7] DEBUG:   message_id: "318BF1"
1829929:2020-07-17 09:56:19 [4432] [7] DEBUG: SMPP PDU dump ends.

Best Regards.





Disclaimer: A1 Makedonija 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. A1 Makedonija 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!

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

Re: SMPP Sender Range Usage

2020-07-15 Thread Davor Spasoski

DID?

> On Jul 15, 2020, at 04:18, Jose Figueroa  
> wrote:
>
> 
> Hi,
>
> I'm trying to achieve a requirement from a vendor from the USA. They provide 
> us with DIDs so we need to push the traffic using those DIDs, but I need to 
> "rotate" them daily, so they provide us a pull of DIDs.
>
> I was reading the documentation and I didn't find anything related to this 
> scenario, like random sender among this pull of DIDs.
>
> Have you implemented something like this? If so, please let me know how you 
> did it.
>
> Thanks
> -Jose

Disclaimer: A1 Makedonija 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. A1 Makedonija 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!

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

RE: ASCI (ANSI X 3.4) IA5 SMPP data coding

2020-06-24 Thread Davor Spasoski

If you mean for the communication between bearerbox and SMSC, sure you can. 
Kannel defaults do GSM 7-bit alphabet, but if you set alt-charset you can 
override. But bear in mind that you will eventually loose some characters not 
existing in GSM 7-bit because the SMSC must transcode those characters from 
ASCII.

From the userguide:
alt-charsetstringDefines which character encoding is used for this specific 
smsc link. Uses iconv() routines to convert from and to that specific character 
set encoding. See your local iconv_open(3) manual page for the supported 
character encodings and the type strings that should be presented for this 
directive.

Davor Spasoski

-Original Message-
From: users  On Behalf Of ahmed qadeer
Sent: Wednesday, June 24, 2020 1:05 PM
To: users@kannel.org
Subject: ASCI (ANSI X 3.4) IA5 SMPP data coding

Dear Team,

Please let me know if we can send use ASCI (ANSI X 3.4) IA5 SMPP data coding in 
kannel 1.5

Operator has asked to use this data coding instead of 8 bit octet stream

Thanks
Ahmed




Disclaimer: A1 Makedonija 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. A1 Makedonija 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!

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

Re: UTF8 characters replaced by question marks

2020-05-06 Thread Davor Spasoski

You have to do that when calling the send-url from the application sending the text.
You don’t need to url encode utf-8 characters (apart from the special url signs) as kannel expects utf-8. Your application should ne set to communicate in utf-8 as well, whic it probably does because you see the text properly in the log files,
only kannel doesn’t know that you want to use ucs-2 and is thus transcoding and replacing anything outside GSM 7-bit with ?

On May 6, 2020, at 21:18, Milos Savic <sav...@gmail.com> wrote:

Hi Davor,

Thank you for you reply.

I tried to add =2 to send-url under smsc http group, but nothing happens. The coding parameter does end up in the dummy service. If you meant to add that to the application sending the request - unfortunately, I am not able to do that.

On Wed, May 6, 2020 at 9:05 PM Davor Spasoski <davor.spaso...@a1.mk> wrote:

Hi,

You also need to set coding=2 and charset to utf-8. Only in that case kannel will know that you are submitting something outside the gsm 7-bit alphabet.

BR,
Davor

On May 6, 2020, at 20:44, Milos Savic <sav...@gmail.com> wrote:

Hi,

I am testing a kannel installation which is supposed to send sms between a python service and a sms aggregator. Regular SMSs work, so I replaced the receiver with a service for testing purposes, which only logs outgoing messages.

I am using kannel from Ubuntu repositories, version 1.4.4-5, with a generic type smsc, directed to my dummy receiving service, with

send-url = "" href="http://proxy:/send?from=%P==%b_id=%I" target="_blank" class="">
http://proxy:/send?from=%P==%b_id=%I

What happens is that I send a test message with utf-8 characters, such as šđčćžшђчћж, and at the end I get a message "? ?", with all characters replaced with question marks.

smsbox log shows a valid message, "sendsms sender: () to: msg:<šđčćž шђчћж>, all charactes valid and shown properly.

the matching bearerbox log entry states:
Parsing URL `http://proxy:/send?from=8088==%3F%3F%3F%3F%3F+%3F%3F%3F%3F%3F_id=

The request at the proxy is, of course, equivalent to the parsed query.

What happens to UTF8 characters? I tried alt-charset on smsc, but that made no changes at all. It seems to me that they get lost somewhere in communication between smsbox and smsc (according to logs).

Any hints on solving this would be highly appreciated. Thank you!

Re: UTF8 characters replaced by question marks

2020-05-06 Thread Davor Spasoski

Hi,

You also need to set coding=2 and charset to utf-8. Only in that case kannel will know that you are submitting something outside the gsm 7-bit alphabet.

BR,
Davor

On May 6, 2020, at 20:44, Milos Savic wrote:

Hi,

I am using kannel from Ubuntu repositories, version 1.4.4-5, with a generic type smsc, directed to my dummy receiving service, with

send-url = "" href="http://proxy:/send?from=%P==%b_id=%I" class="">
http://proxy:/send?from=%P==%b_id=%I

What happens is that I send a test message with utf-8 characters, such as šđčćžшђчћж, and at the end I get a message "? ?", with all characters replaced with question marks.

smsbox log shows a valid message, "sendsms sender: () to: msg:<šđčćž шђчћж>, all charactes valid and shown properly.

the matching bearerbox log entry states:
Parsing URL `http://proxy:/send?from=8088==%3F%3F%3F%3F%3F+%3F%3F%3F%3F%3F_id=

The request at the proxy is, of course, equivalent to the parsed query.

Any hints on solving this would be highly appreciated. Thank you!

RE: Help with Unicode Messages

2020-03-20 Thread Davor Spasoski

BTW, I don’t know why the cgi-bin was slow on you. We’ve sent bilions of SMS so 
far and there was not a single problem with the smsbox

What are you using to address to the smsbox?

Davor Spasoski

From: users  On Behalf Of Davor Spasoski
Sent: Friday, March 20, 2020 12:34 PM
To: Gabriel Augusto Diaz Zapata 
Cc: users@kannel.org
Subject: RE: Help with Unicode Messages

1.Your table must be created with Unicode support

2.select encoding/collation to UTF8mb4

3.If you are using a programming language, set the connection to the table 
must be with the proper (UTF-8) charset.

4.If you use SQL statement from the CLI, make sure the CLI supports UTF8mb4

5.Copy/paste the smiley sign or follow the link here 
https://stackoverflow.com/questions/39463134/how-to-store-emoji-character-in-mysql-database

Davor Spasoski

From: Gabriel Augusto Diaz Zapata 
mailto:gabriel.d...@gmail.com>>
Sent: Friday, March 20, 2020 5:30 AM
To: Davor Spasoski mailto:davor.spaso...@a1.mk>>
Cc: users@kannel.org<mailto:users@kannel.org>
Subject: Re: Help with Unicode Messages

Yes, I did.

So.. change my question
I need to send some millions of unicode messages
I tried with smsbox cgi, but I  didnt get a better performance.. some timeouts 
or very slow..

So.. I think to do a bulk insert to send_sms table, but i need to identify how 
is encoded the HMTL Entities, in example " Hello " to  
%00h%00e%00l%00l%00o%00%A0%D8%3D%DE%00 (bold text is the emoji)
I need to know please how to encode the text  and the UNICODE text

It is possible?

Thanks in advanced

On Thu, Mar 19, 2020 at 3:31 AM Davor Spasoski 
mailto:davor.spaso...@a1.mk>> wrote:
Did you set coding=2

On Mar 19, 2020, at 04:42, Gabriel Augusto Diaz Zapata 
mailto:gabriel.d...@gmail.com>> wrote:

Tks Davor, Antony

URL Encoded doesnt works.. The string after conversion is not the same

On Wed, Mar 18, 2020 at 4:49 AM Davor Spasoski 
mailto:davor.spaso...@a1.mk>> wrote:
Hi,

You need to address to smsbox in UTF-8. So, you then URL encode (percent 
encode) every hex code of the UTF-8 sign.

BR,
Davor

> On Mar 18, 2020, at 02:07, Gabriel Augusto Diaz Zapata 
> mailto:gabriel.d...@gmail.com>> wrote:
>
> Hello
> I need help please
>
> Im sending unicode messages (emojis) using sendsms. IE, xc; is converted in 
> sent_sms table to "%D8%3D%DE%00"
>
> Wich type of conversion is it? I mean UNICODE to? HEX?
>
> Thank you
>
> Gabriel

Disclaimer: A1 Makedonija 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. A1 Makedonija 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!

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

Disclaimer: A1 Makedonija 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. A1 Makedonija 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

RE: Help with Unicode Messages

2020-03-20 Thread Davor Spasoski

1.Your table must be created with Unicode support

2.select encoding/collation to UTF8mb4

3.If you are using a programming language, set the connection to the table 
must be with the proper (UTF-8) charset.

4.If you use SQL statement from the CLI, make sure the CLI supports UTF8mb4

5.Copy/paste the smiley sign or follow the link here 
https://stackoverflow.com/questions/39463134/how-to-store-emoji-character-in-mysql-database

Davor Spasoski

From: Gabriel Augusto Diaz Zapata 
Sent: Friday, March 20, 2020 5:30 AM
To: Davor Spasoski 
Cc: users@kannel.org
Subject: Re: Help with Unicode Messages

Yes, I did.

So.. change my question
I need to send some millions of unicode messages
I tried with smsbox cgi, but I  didnt get a better performance.. some timeouts 
or very slow..

So.. I think to do a bulk insert to send_sms table, but i need to identify how 
is encoded the HMTL Entities, in example " Hello " to  
%00h%00e%00l%00l%00o%00%A0%D8%3D%DE%00 (bold text is the emoji)
I need to know please how to encode the text  and the UNICODE text

It is possible?

Thanks in advanced

On Thu, Mar 19, 2020 at 3:31 AM Davor Spasoski 
mailto:davor.spaso...@a1.mk>> wrote:
Did you set coding=2

On Mar 19, 2020, at 04:42, Gabriel Augusto Diaz Zapata 
mailto:gabriel.d...@gmail.com>> wrote:

Tks Davor, Antony

URL Encoded doesnt works.. The string after conversion is not the same

On Wed, Mar 18, 2020 at 4:49 AM Davor Spasoski 
mailto:davor.spaso...@a1.mk>> wrote:
Hi,

You need to address to smsbox in UTF-8. So, you then URL encode (percent 
encode) every hex code of the UTF-8 sign.

BR,
Davor

> On Mar 18, 2020, at 02:07, Gabriel Augusto Diaz Zapata 
> mailto:gabriel.d...@gmail.com>> wrote:
>
> Hello
> I need help please
>
> Im sending unicode messages (emojis) using sendsms. IE, xc; is converted in 
> sent_sms table to "%D8%3D%DE%00"
>
> Wich type of conversion is it? I mean UNICODE to? HEX?
>
> Thank you
>
> Gabriel

Disclaimer: A1 Makedonija 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. A1 Makedonija 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!

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

Disclaimer: A1 Makedonija 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. A1 Makedonija 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!

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

Re: Help with Unicode Messages

2020-03-19 Thread Davor Spasoski

Did you set coding=2

On Mar 19, 2020, at 04:42, Gabriel Augusto Diaz Zapata  wrote:

Tks Davor, Antony

URL Encoded doesnt works.. The string after conversion is not the same

On Wed, Mar 18, 2020 at 4:49 AM Davor Spasoski <davor.spaso...@a1.mk> wrote:

Hi,

You need to address to smsbox in UTF-8. So, you then URL encode (percent encode) every hex code of the UTF-8 sign.

BR,
Davor

> On Mar 18, 2020, at 02:07, Gabriel Augusto Diaz Zapata <gabriel.d...@gmail.com> wrote:
>
> Hello
> I need help please
>
> Im sending unicode messages (emojis) using sendsms. IE, xc; is converted in sent_sms table to "%D8%3D%DE%00"
>
> Wich type of conversion is it? I mean UNICODE to? HEX?
>
> Thank you
>
> Gabriel

Disclaimer: A1 Makedonija 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. A1 Makedonija 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!

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

Disclaimer: A1 Makedonija 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. A1 Makedonija 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!

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

Re: Help with Unicode Messages

2020-03-18 Thread Davor Spasoski

Hi,

You need to address to smsbox in UTF-8. So, you then URL encode (percent 
encode) every hex code of the UTF-8 sign.

BR,
Davor

> On Mar 18, 2020, at 02:07, Gabriel Augusto Diaz Zapata 
>  wrote:
>
> Hello
> I need help please
>
> Im sending unicode messages (emojis) using sendsms. IE, xc; is converted in 
> sent_sms table to "%D8%3D%DE%00"
>
> Wich type of conversion is it? I mean UNICODE to? HEX?
>
> Thank you
>
> Gabriel

Disclaimer: A1 Makedonija 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. A1 Makedonija 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!

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

Re: Need an Assistance in my Kannel Config

2020-02-23 Thread Davor Spasoski

Another possibility is that the number base of the msg-id does not match with the SMSC. Do you maybe have connecion to more than one SMSC, either explicitelly or behind the virtual IP of the smsc? Check the manual:

msg-id-type
number
Optional, specifies which number base the SMSC is using for the message ID numbers in the corresponding submit_sm_resp and deliver_sm PDUs. This is required to make delivery reports
(DLR) work on SMSC that behave differently. The number is a combined set of bit 1 and bit 2 that indicate as follows: bit 1: type for submit_sm_resp, bit 2: type for deliver_sm. If the bit is set then the value
is in hex otherwise in decimal number base. Which means the following combinations are possible and valid: 0x00 deliver_sm decimal, submit_sm_resp decimal; 0x01 deliver_sm decimal, submit_sm_resp hex;
0x02 deliver_sm hex, submit_sm_resp decimal; 0x03 deliver_sm hex, submit_sm_resp hex. In accordance to the SMPP v3.4 specs the default will be a C string literal
if no of the above values is explicitly indicated using the config directive.

On Feb 18, 2020, at 06:13, Robin C wrote:

Hi,

The same is happening to me also. Sometimes I am not receiving the DLR of delivered messages also. If i sent 1000 messages i might get 900 DLRs. What might be the reason.

On Mon, Feb 17, 2020 at 3:57 PM Tolga Ulas wrote:

Also check your smpp logs (raise it to debug level in your config) and
check if kannel can successfully create outgoing dlr records and can
match them with incoming dlrs during transactions. If all goes well
you will see no warning or error for all messages

> - Maybe you have messages that are pending and they have different status. - Try with a simple mask (3) and then set a short expiration of the messages that you are going to test. Have one test phones on, one that you will turn on before expiration and a
third one that you don’t turn-on before the expiration. Record all the dlrs that the SMSC will send and try to figure out the logic. Increase the dlr-mask and check the other scenarios - check with the SMSC operator if they send back an SLR if the message
is expired or deleted from the SMSC DB for whatever reason. Regards, Davor

Thanks
& Regards,

Disclaimer: This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute
or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted,
corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required
please request a hard-copy version.
7 Switch
off as you go |q Recycle
always | P Print
only if absolutely necessary

RE: Need an Assistance in my Kannel Config

2020-02-17 Thread Davor Spasoski

- Maybe you have messages that are pending and they have different status.
- Try with a simple mask (3) and then set a short expiration of the messages 
that you are going to test. Have one test phones on, one that you will turn on 
before expiration and a third one that you don’t turn-on before the expiration. 
Record all the dlrs that the SMSC will send and try to figure out the logic. 
Increase the dlr-mask and check the other scenarios
- check with the SMSC operator if they send back an SLR if the message is 
expired or deleted from the SMSC DB for whatever reason.

Regards,
Davor

From: Rasika Udayanga 
Sent: Monday, February 17, 2020 3:44 AM
To: Davor Spasoski 
Cc: users@kannel.org
Subject: RE: Need an Assistance in my Kannel Config

Dear Davor,
I’m sending 63 as the dlr mask. Can that be a cause to not to receive some of 
the delivery reports of those were acknowledged? Please assist.

“dlr_mask=63”

Regards,
Rasika.


From: Davor Spasoski [mailto:davor.spaso...@a1.mk]
Sent: Saturday, February 15, 2020 1:38 PM
To: Rasika Udayanga
Cc: users@kannel.org<mailto:users@kannel.org>
Subject: Re: Need an Assistance in my Kannel Config

Dear Rasika,

First suspect is dlr-mask. You have to set it minimally to both delivery 
success and delivery failure (3).
Other condiition is to set smsc-id, which I see you did.

Check this part of kannel userguide:

"When you deliver SMS to Kannel you have to indicate what kind of delivery 
report messages you would like to receive back from the system. The delivery 
report types currently implemented are:
• 1: delivery success
• 2: delivery failure
• 4: message buffered
• 8: smsc submit
• 16: smsc reject
• 32: smsc intermediate notifications
If you want multiple report types, you simply add the values together. “

On Feb 15, 2020, at 05:23, Rasika Udayanga 
mailto:ras...@bellvantage.com>> wrote:

Dear All,
As per the below report, even though 108726 messages were acknowledged I have 
received only 60036  (sum of status 1 and 2) delivery reports. I cannot 
understand as to why there are no delivery reports for the rest of the 
acknowledged messages.

I’m a doing something wrong in my config? Can you please assist me.




group = core
dlr-storage = mysql
admin-port = 8206
admin-password = *
status-password = *
admin-allow-ip = "127.0.0.1"
log-level = 0
sms-resend-retry = 10
sms-combine-concatenated-mo = true
# Smsbox related
smsbox-port = 8205
box-allow-ip = "127.0.0.1"
smsbox-max-pending = 1


group = smsc
smsc = smpp
smsc-id = lankabell
host = **
port = **
smsc-username = ***
smsc-password = **
transceiver-mode = true
msg-id-type = 0x00
reconnect-delay = 2
wait-ack = 60
wait-ack-expire = 0x02
validityperiod = 1440
interface-version = 34
system-type = "VMA"

<https://lk.linkedin.com/in/rasikau>

Rasika Udayanga Kodithuwakku | Senior Manager
Information Technology
Bellvantage (Pvt) Ltd, No - 46, Vauxhall Street, Colombo 02, Sri Lanka.
Mobile :- +94 77 7289868 | Direct :- +94 11 5756256
E-Mail  :- ras...@bellvantage.com<mailto:ras...@bellvantage.com> | Web :- 
www.bellvantage.com<http://www.bellvantage.com/>





Disclaimer: A1 Makedonija 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. A1 Makedonija 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!

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



Disclaimer: A1 Makedonija DOOEL Skopje
This e-mail

Re: Need an Assistance in my Kannel Config

2020-02-15 Thread Davor Spasoski




Dear Rasika,


First suspect is dlr-mask. You have to set it minimally to both delivery success and delivery failure (3).
Other condiition is to set smsc-id, which I see you did.


Check this part of kannel userguide:


"When you deliver SMS to Kannel you have to indicate what kind of delivery report messages you would like to receive back from the system. The delivery report types currently implemented are:


• 1: delivery success


• 2: delivery failure


• 4: message buffered


• 8: smsc submit


• 16: smsc reject


• 32: smsc intermediate notifications


If you want multiple report types, you simply add the values together. “





On Feb 15, 2020, at 05:23, Rasika Udayanga  wrote:




Dear All,

As per the below report, even though 108726 messages were acknowledged I have received only 60036  (sum of status 1 and 2) delivery reports. I cannot understand as to why there are no delivery reports for the rest of the acknowledged messages. 

 

I’m a doing something wrong in my config? Can you please assist me.

 



 

 

group = core

dlr-storage = mysql

admin-port = 8206

admin-password = *

status-password = *

admin-allow-ip = "127.0.0.1"

log-level = 0

sms-resend-retry = 10

sms-combine-concatenated-mo = true

# Smsbox related

smsbox-port = 8205

box-allow-ip = "127.0.0.1"

smsbox-max-pending = 1

 

 

group = smsc

smsc = smpp

smsc-id = lankabell

host = **

port = **

smsc-username = ***

smsc-password = **

transceiver-mode = true

msg-id-type = 0x00 

reconnect-delay = 2

wait-ack = 60

wait-ack-expire = 0x02 

validityperiod = 1440

interface-version = 34

system-type = "VMA"

 









Rasika Udayanga Kodithuwakku | Senior Manager

Information Technology

Bellvantage (Pvt) Ltd, No - 46,
 Vauxhall Street, Colombo 02, Sri Lanka.

Mobile :- +94 77 7289868 | Direct :- +94 11 5756256

E-Mail  :- ras...@bellvantage.com |
 Web :- www.bellvantage.com













Disclaimer: A1 Makedonija 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. A1 Makedonija 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!

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

RE: opensmppbox smsc-route

2020-01-27 Thread Davor Spasoski

You can do that in bearerbox config in the smsc group.
You should use the allow-smsc-id = customerX whee customerX is the esme 
system-id that is propagated as smsc-id due to the directive that you use in 
opensmppbox: use-systemid-as-smsboxid = true

For the reverse direction you should route all smsc-ids towards your mycompany 
opensmppbox. Opensmppbox will know how to route to the proper esme.

BR,

Davor Spasoski


From: users  On Behalf Of Techinnovation
Sent: Monday, January 27, 2020 1:09 PM
To: users@kannel.org
Subject: opensmppbox smsc-route

Hello,

I have installed kannel with opensmmbox, all work fine.

I have connected 3 different ESME customers on opensmppbox,
and I need for each ESME have additional sms routing to separate SMSC on kannel 
server.

With this configuration all sms from all ESME (customer1,customer2, customer3) 
route to smsc1.
But I need to have route like

from customer1 to smsc1
from customer2 to smsc2
from customer3 to smsc3

Please help.

===
smpplogins.txt
customer1 password1 localbox *.*.*.*
customer2 password2 localbox *.*.*.*
customer3 password3 localbox *.*.*.*

opensmmpbox.conf
# sample opensmppbox.conf

group = core
dlr-storage = mysql

group = opensmppbox
opensmppbox-id = mycompany
opensmppbox-port = 2799
bearerbox-host = localhost
bearerbox-port = 13005
log-level = 0
log-file = "/var/log/kannel/opensmppbox.log"
our-system-id = mycompany
route-to-smsc = smsc1
smpp-logins = "/etc/kannel/smpplogins.txt"
use-systemid-as-smsboxid = true

# the following is just standard dlr configuration

group = mysql-connection
id = dlr
host = localhost
username = kannel
password = kannelpass
database = kannel

group = dlr-db
id = dlr
table = dlr
field-smsc = smsc
field-timestamp = ts
field-destination = destination
field-source = source
field-service = service
field-url = url
field-mask = mask
field-status = status
field-boxc-id = boxc


BR,
Alekxandr



Disclaimer: A1 Makedonija 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. A1 Makedonija 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!

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

Re: WARNING: smsbox_list empty!

2019-12-17 Thread Davor Spasoski




You could have messages in store that are waiting to be routed to an smsbox/opensmppbox with id other than your current one.
Davor

On Dec 18, 2019, at 02:00, Александр Недзельский  wrote:






Hi,




I've searched through similar topics, checked https://www.kannel.org/download/1.4.4/gateway-1.4.4/gw/bb_boxc.c, but
 still cannot find a solution:

Upon start and after I see in bearerbox.log multiple messages at moment, repeating periodically:


2019-12-18 03:09:40 [26216] [4] WARNING: smsbox_list empty!
2019-12-18 03:09:40 [26216] [4] WARNING: smsbox_list empty!
2019-12-18 03:09:40 [26216] [4] WARNING: smsbox_list empty!
2019-12-18 03:09:40 [26216] [4] WARNING: smsbox_list empty!
2019-12-18 03:09:40 [26216] [4] WARNING: smsbox_list empty!
2019-12-18 03:09:40 [26216] [4] WARNING: smsbox_list empty!
2019-12-18 03:09:40 [26216] [4] WARNING: smsbox_list empty!
2019-12-18 03:09:40 [26216] [4] WARNING: smsbox_list empty!




At the same time all messages are sending and everything is workin fine.

I've tried changing config in smsbox-route and smsbox part but no success.

My kannel.conf:



group = core
admin-port = 13000
admin-password = [deleted]
status-password = [deleted]
log-file = "/var/log/kannel/bearerbox.log"
log-level = 0
store-type = spool
store-location = "/var/spool/kannel"
box-deny-ip = "*.*.*.*"
box-allow-ip = "[deleted]"
smsbox-port = 13001

 

group = smsbox
smsbox-id = smsbox
bearerbox-host = localhost
bearerbox-port = 13001
sendsms-port = 13007
sendsms-url = "">
log-file = "/var/log/kannel/smsbox.log"
access-log = "/var/log/kannel/smsbox.access.log"
mo-recode = true
log-level = 0

 

group = smsbox-route
smsbox-id = smsbox 

 

group = sendsms-user
username = [deleted]
password = [deleted]
concatenation = true
max-messages = 10 

 

group = smsc
smsc = fake
smsc-id = fake
allowed-smsc-id = fake
port = 1
connect-allow-ip = 127.0.0.1 

 

group = smsc
smsc = smpp
smsc-id = [deleted]
allowed-smsc-id = [deleted]
log-file = "/var/log/kannel/[deleted].log"
smsc-username = "[deleted]"
smsc-password = "[deleted]"
host = [deleted]
port = 4442
transceiver-mode = true
system-type= ""
service-type = ""
address-range = ""
source-addr-ton = 0
source-addr-npi = 1
dest-addr-ton = 1
dest-addr-npi= 1
log-level = 0
alt-charset=ucs-2be
connection-timeout = 300


Thank you for your help!




С уважением,
Недзельский Александр










Disclaimer: A1 Makedonija 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. A1 Makedonija 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!

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

RE: Unicode SMS Length Calculation

2019-11-27 Thread Davor Spasoski

As I wrote earlier, the concatenation mechanism eats some of the payload, which 
is 3x2 bytes for message reference number, total segments and segment number.

That will reduce your payload to 153 septets for GSM-7bit text or 134 8-bit 
data or 67 UCS-2 characters.

I really haven’t checked what shows-up in the access log when someone is using 
message payload TLV instead of usual short_message field. It’s too much effort 
on my side to setup. I can only say that in this case I expect that even 
bearerbox is not going to split the SMS.

BR,

Davor Spasoski

From: Mesbahuddin Malik 
Sent: Wednesday, November 27, 2019 1:23 PM
To: Davor Spasoski 
Cc: rene.klu...@chimit.nl; users@kannel.org
Subject: Unicode SMS Length Calculation

Hello Davor Spasoski,
Thanks for Your reply. My Scenario is  that I can I  send an Unicode Message 
and giving the scenario of  encoded Result:

On access log after  grep "Sent SMS "
2019-11-26 20:42:05 2019-11-27 01:41:58 REJECTED Send SMS [SMSC:smpp1] 
[SVC:mesbah] [ACT:admin] [BINF:][from:giotaas] [to:01833055942] 
[flags:-1:2:-1:-1:  31] [msg:416
"Encoded Text"
===

On PostgreSQL:
The msgdata is encoded

On MySQL
msgdata is encoded
==
 From access log  I can see the message length is 416 and which  seems to be 
correctaccording to Unicode Calculation.
 From Database I can calculate The length easily If  I get  the decoded text.
 So  can any one suggest how to get decoded value on the db  for msgdata field 
? Or Should I have to modify sqlbox.c and sqlbox_mysql.c ?

Regards
Mesbah




On Wed, Nov 27, 2019 at 5:54 PM Davor Spasoski 
mailto:davor.spaso...@a1.mk>> wrote:
Hi,

I’m not using a DB but I know what your problem is. Namely, access log does not 
show the message splits, only message length with one entry and it can be 
tricky to calculate.

In cases when unicode (UCS-2 towards the SMPP) is used, the payload is limited 
to 70 two byte signs. The, if the message is longer than 70, the concatenation 
mechanism uses 7 septets if I’m not mistaken (I need to check the specs, 
really), so you need to take that into the calculation.

I can check later if I find some time.

Davor Spasoski

From: users mailto:users-boun...@kannel.org>> On 
Behalf Of Mesbahuddin Malik
Sent: Wednesday, November 27, 2019 12:22 PM
To: rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>
Cc: users@kannel.org<mailto:users@kannel.org>
Subject:

Hello
I need a help on Unicode SMS Length
I have configured Kannel using mysql and also tested on Postgresql.
All are working fine .But the problem is  on  SMS count issue  from Database 
when sms is
sent through unicode.

From sent_sms table I see the msgdata value is encoded(when sent using unicode) 
and I cannot calculate the Actual character length  as I need it for Billing.

Any suggestions is really appreciable


Regards
Mesbah



Disclaimer: A1 Makedonija 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. A1 Makedonija 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!

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



Disclaimer: A1 Makedonija 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

RE: Send "Sinhala" Letters (Unicode) via Kannel XML Post

2019-08-26 Thread Davor Spasoski

BTW, sorry for misspelling Sinhala. Singha beer is to blame for that ;)

BR,
Davor
From: Davor Spasoski
Sent: Monday, August 26, 2019 3:33 PM
To: 'Rasika Udayanga' ; 'vinayak mv' 

Cc: users@kannel.org
Subject: RE: Send "Sinhala" Letters (Unicode) via Kannel XML Post

Dear Rasika,

Your Singha characters work well on my environent with the following curl 
syntax:

curl -X POST \
  http://10.1.19.5:4004/cgi-bin/sendsms \
  -H 'cache-control: no-cache' \
  -H 'content-type: text/xml' \
  -H 'postman-token: dc4ba5cb-28ca-b9bc-5ab2-9c3369add9db' \
  -d '


+94777289868
Source
රසික
2
1






'

Davor Spasoski

M: +38975400608
e-mail: davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>

one.Vip DOOEL Skopje | Ploshtad Presveta Bogorodica 1 | 1000 Skopje | Macedonia
Member of A1 Telekom Austria Group

From: Rasika Udayanga mailto:ras...@bellvantage.com>>
Sent: Monday, August 26, 2019 2:13 PM
To: Davor Spasoski mailto:davor.spaso...@onevip.mk>>; 
'vinayak mv' mailto:vinayakvasu...@gmail.com>>
Cc: users@kannel.org<mailto:users@kannel.org>
Subject: RE: Send "Sinhala" Letters (Unicode) via Kannel XML Post

Dear Davor, Vinayak,
Thank you and appreciate your responses.

Dear Davor,
Yes I set the content type in the header and below is my C# cording as how I 
does it. but the message is delivered as garbage letters.

string xmlMessage = "\r\n" +

"9477728986894115753753%E0%B6%BB%E0%B7%83%E0%B7%92%E0%B6%9A21";
string url = "http://10.9.8.25:13013/cgi-bin/sendsms;;
HttpWebRequest request = (HttpWebRequest)WebRequest.Create(url);

byte[] requestInFormOfBytes = 
System.Text.Encoding.ASCII.GetBytes(xmlMessage);
request.Method = "POST";
request.ContentType = "text/xml";
request.ContentLength = requestInFormOfBytes.Length;
Stream requestStream = request.GetRequestStream();
requestStream.Write(requestInFormOfBytes, 0, 
requestInFormOfBytes.Length);
requestStream.Close();

HttpWebResponse response = (HttpWebResponse)request.GetResponse();
StreamReader respStream = new 
StreamReader(response.GetResponseStream(), System.Text.Encoding.Default);
string receivedResponse = respStream.ReadToEnd();
Console.WriteLine(receivedResponse);
respStream.Close();
response.Close();

Dear Vinayak,
I tried the same a long time ago and failed. Have you tried doing it with MSSQL.

Regards,
Rasika Udayanga.


From: vinayak mv [mailto:vinayakvasu...@gmail.com]
Sent: Saturday, August 24, 2019 10:34 PM
To: Davor Spasoski
Cc: Rasika Udayanga; users@kannel.org<mailto:users@kannel.org>
Subject: Re: Send "Sinhala" Letters (Unicode) via Kannel XML Post

Better use sqlbox for bulk sending



On Sat, 24 Aug 2019 at 10:04 PM, Davor Spasoski 
mailto:davor.spaso...@onevip.mk>> wrote:
Hi,

I’m rarely using Postman for simple HTTP calls. Try using curl -H

BTW, kannel does state that you need to set the content type in a header not 
the xml payload and you should do so with the enoding as in the xm example, the 
encoding is not set within the xml.

"Note: Don't forget to set POST Content-Type to text/xml!"

On Aug 24, 2019, at 14:34, Rasika Udayanga 
mailto:ras...@bellvantage.com>> wrote:

Dear Davor,
I’m kind of confused. Please correct me if I’m wrong.
As per the Kannal user guide I should send an XML document when I do POST for 
bulk sending. Please refer below screenshot of the Postman that I’m trying to 
send the request through.




When I try to use text/html instead of text/xml smsbox failed with below PANIC 
errors.

2019-08-24 17:17:06 [27859] [3] INFO: smsbox: Got HTTP request 
 from <192.168.51.100>
2019-08-24 17:17:06 [27859] [3] DEBUG: Status: 403 Answer: 
2019-08-24 17:17:06 [27859] [3] PANIC: gwlib/octstr.c:2504: seems_valid_real: 
Assertion `ostr->data != NULL' failed. (Called from 
gwlib/octstr.c:325:octstr_destroy.)
2019-08-24 17:17:06 [27859] [3] PANIC: /usr/local/sbin/smsbox(gw_panic+0x147) 
[0x43c0b7]
2019-08-24 17:17:06 [27859] [3] PANIC: /usr/local/sbin/smsbox() [0x43d2f0]
2019-08-24 17:17:06 [27859] [3] PANIC: 
/usr/local/sbin/smsbox(octstr_destroy+0x1d) [0x43f2dd]
2019-08-24 17:17:06 [27859] [3] PANIC: /usr/local/sbin/smsbox() [0x412784]
2019-08-24 17:17:06 [27859] [3] PANIC: /usr/local/sbin/smsbox() [0x43331e]
2019-08-24 17:17:06 [27859] [3] PANIC: /lib64/libpthread.so.0(+0x7a51) 
[0x7fc246380a51]
2019-08-24 17:17:06 [27859] [3] PANIC: /lib64/libc.so.6(clone+0x6d) 
[0x7fc24590c93d]

Please help me to understand where I go wrong. Appreciate if you can share me a 
working sample of the XML POST that I can test with.

Regards,
Rasika Udayanga


From: Davor Spasoski [mailto:davor.spaso...@onevip.mk]
Sent: Saturday, August 24, 2019 1:47 PM
To: Rasika U

RE: Send "Sinhala" Letters (Unicode) via Kannel XML Post

2019-08-26 Thread Davor Spasoski

Dear Rasika,

Your Singha characters work well on my environent with the following curl 
syntax:

curl -X POST \
  http://10.1.19.5:4004/cgi-bin/sendsms \
  -H 'cache-control: no-cache' \
  -H 'content-type: text/xml' \
  -H 'postman-token: dc4ba5cb-28ca-b9bc-5ab2-9c3369add9db' \
  -d '


+94777289868
Source
රසික
2
1






'

Davor Spasoski

M: +38975400608
e-mail: davor.spaso...@onevip.mk

one.Vip DOOEL Skopje | Ploshtad Presveta Bogorodica 1 | 1000 Skopje | Macedonia
Member of A1 Telekom Austria Group

From: Rasika Udayanga 
Sent: Monday, August 26, 2019 2:13 PM
To: Davor Spasoski ; 'vinayak mv' 

Cc: users@kannel.org
Subject: RE: Send "Sinhala" Letters (Unicode) via Kannel XML Post

Dear Davor, Vinayak,
Thank you and appreciate your responses.

Dear Davor,
Yes I set the content type in the header and below is my C# cording as how I 
does it. but the message is delivered as garbage letters.

string xmlMessage = "\r\n" +

"9477728986894115753753%E0%B6%BB%E0%B7%83%E0%B7%92%E0%B6%9A21";
string url = "http://10.9.8.25:13013/cgi-bin/sendsms;;
HttpWebRequest request = (HttpWebRequest)WebRequest.Create(url);

byte[] requestInFormOfBytes = 
System.Text.Encoding.ASCII.GetBytes(xmlMessage);
request.Method = "POST";
request.ContentType = "text/xml";
request.ContentLength = requestInFormOfBytes.Length;
Stream requestStream = request.GetRequestStream();
requestStream.Write(requestInFormOfBytes, 0, 
requestInFormOfBytes.Length);
requestStream.Close();

HttpWebResponse response = (HttpWebResponse)request.GetResponse();
StreamReader respStream = new 
StreamReader(response.GetResponseStream(), System.Text.Encoding.Default);
string receivedResponse = respStream.ReadToEnd();
Console.WriteLine(receivedResponse);
respStream.Close();
response.Close();

Dear Vinayak,
I tried the same a long time ago and failed. Have you tried doing it with MSSQL.

Regards,
Rasika Udayanga.


From: vinayak mv [mailto:vinayakvasu...@gmail.com]
Sent: Saturday, August 24, 2019 10:34 PM
To: Davor Spasoski
Cc: Rasika Udayanga; users@kannel.org<mailto:users@kannel.org>
Subject: Re: Send "Sinhala" Letters (Unicode) via Kannel XML Post

Better use sqlbox for bulk sending



On Sat, 24 Aug 2019 at 10:04 PM, Davor Spasoski 
mailto:davor.spaso...@onevip.mk>> wrote:
Hi,

I’m rarely using Postman for simple HTTP calls. Try using curl -H

BTW, kannel does state that you need to set the content type in a header not 
the xml payload and you should do so with the enoding as in the xm example, the 
encoding is not set within the xml.

"Note: Don't forget to set POST Content-Type to text/xml!"

On Aug 24, 2019, at 14:34, Rasika Udayanga 
mailto:ras...@bellvantage.com>> wrote:

Dear Davor,
I’m kind of confused. Please correct me if I’m wrong.
As per the Kannal user guide I should send an XML document when I do POST for 
bulk sending. Please refer below screenshot of the Postman that I’m trying to 
send the request through.




When I try to use text/html instead of text/xml smsbox failed with below PANIC 
errors.

2019-08-24 17:17:06 [27859] [3] INFO: smsbox: Got HTTP request 
 from <192.168.51.100>
2019-08-24 17:17:06 [27859] [3] DEBUG: Status: 403 Answer: 
2019-08-24 17:17:06 [27859] [3] PANIC: gwlib/octstr.c:2504: seems_valid_real: 
Assertion `ostr->data != NULL' failed. (Called from 
gwlib/octstr.c:325:octstr_destroy.)
2019-08-24 17:17:06 [27859] [3] PANIC: /usr/local/sbin/smsbox(gw_panic+0x147) 
[0x43c0b7]
2019-08-24 17:17:06 [27859] [3] PANIC: /usr/local/sbin/smsbox() [0x43d2f0]
2019-08-24 17:17:06 [27859] [3] PANIC: 
/usr/local/sbin/smsbox(octstr_destroy+0x1d) [0x43f2dd]
2019-08-24 17:17:06 [27859] [3] PANIC: /usr/local/sbin/smsbox() [0x412784]
2019-08-24 17:17:06 [27859] [3] PANIC: /usr/local/sbin/smsbox() [0x43331e]
2019-08-24 17:17:06 [27859] [3] PANIC: /lib64/libpthread.so.0(+0x7a51) 
[0x7fc246380a51]
2019-08-24 17:17:06 [27859] [3] PANIC: /lib64/libc.so.6(clone+0x6d) 
[0x7fc24590c93d]

Please help me to understand where I go wrong. Appreciate if you can share me a 
working sample of the XML POST that I can test with.

Regards,
Rasika Udayanga


From: Davor Spasoski [mailto:davor.spaso...@onevip.mk]
Sent: Saturday, August 24, 2019 1:47 PM
To: Rasika Udayanga
Cc: users@kannel.org<mailto:users@kannel.org>
Subject: Re: Send "Sinhala" Letters (Unicode) via Kannel XML Post

Did you try declaring the encoding in the HTTP POST header like this:

 ?

On Aug 24, 2019, at 08:01, Rasika Udayanga 
mailto:ras...@bellvantage.com>> wrote:

Dear Davor
Thank you and appreciate your prompt response.

Yes, as shown below I tried without url encoding the payload and even removing 
the encoding t

RE: Send "Sinhala" Letters (Unicode) via Kannel XML Post

2019-08-26 Thread Davor Spasoski

1.   Try adding utf-8 in your xml body.

2.   Try first not to double encode. (url encoding of your Singha letters). 
Just make sure that whatever is in your body is indeed UTF-8 encoded 
characters. And set content encoding to utf-8 in the http header, not just the 
ContentType. But try first 1, with or without url encoding

Davor Spasoski
From: Rasika Udayanga 
Sent: Monday, August 26, 2019 2:13 PM
To: Davor Spasoski ; 'vinayak mv' 

Cc: users@kannel.org
Subject: RE: Send "Sinhala" Letters (Unicode) via Kannel XML Post

Dear Davor, Vinayak,
Thank you and appreciate your responses.

Dear Davor,
Yes I set the content type in the header and below is my C# cording as how I 
does it. but the message is delivered as garbage letters.

string xmlMessage = "\r\n" +

"9477728986894115753753%E0%B6%BB%E0%B7%83%E0%B7%92%E0%B6%9A21";
string url = "http://10.9.8.25:13013/cgi-bin/sendsms;;
HttpWebRequest request = (HttpWebRequest)WebRequest.Create(url);

byte[] requestInFormOfBytes = 
System.Text.Encoding.ASCII.GetBytes(xmlMessage);
request.Method = "POST";
request.ContentType = "text/xml";
request.ContentLength = requestInFormOfBytes.Length;
Stream requestStream = request.GetRequestStream();
requestStream.Write(requestInFormOfBytes, 0, 
requestInFormOfBytes.Length);
requestStream.Close();

HttpWebResponse response = (HttpWebResponse)request.GetResponse();
StreamReader respStream = new 
StreamReader(response.GetResponseStream(), System.Text.Encoding.Default);
string receivedResponse = respStream.ReadToEnd();
Console.WriteLine(receivedResponse);
respStream.Close();
response.Close();

Dear Vinayak,
I tried the same a long time ago and failed. Have you tried doing it with MSSQL.

Regards,
Rasika Udayanga.


From: vinayak mv [mailto:vinayakvasu...@gmail.com]
Sent: Saturday, August 24, 2019 10:34 PM
To: Davor Spasoski
Cc: Rasika Udayanga; users@kannel.org<mailto:users@kannel.org>
Subject: Re: Send "Sinhala" Letters (Unicode) via Kannel XML Post

Better use sqlbox for bulk sending



On Sat, 24 Aug 2019 at 10:04 PM, Davor Spasoski 
mailto:davor.spaso...@onevip.mk>> wrote:
Hi,

I’m rarely using Postman for simple HTTP calls. Try using curl -H

BTW, kannel does state that you need to set the content type in a header not 
the xml payload and you should do so with the enoding as in the xm example, the 
encoding is not set within the xml.

"Note: Don't forget to set POST Content-Type to text/xml!"

On Aug 24, 2019, at 14:34, Rasika Udayanga 
mailto:ras...@bellvantage.com>> wrote:

Dear Davor,
I’m kind of confused. Please correct me if I’m wrong.
As per the Kannal user guide I should send an XML document when I do POST for 
bulk sending. Please refer below screenshot of the Postman that I’m trying to 
send the request through.




When I try to use text/html instead of text/xml smsbox failed with below PANIC 
errors.

2019-08-24 17:17:06 [27859] [3] INFO: smsbox: Got HTTP request 
 from <192.168.51.100>
2019-08-24 17:17:06 [27859] [3] DEBUG: Status: 403 Answer: 
2019-08-24 17:17:06 [27859] [3] PANIC: gwlib/octstr.c:2504: seems_valid_real: 
Assertion `ostr->data != NULL' failed. (Called from 
gwlib/octstr.c:325:octstr_destroy.)
2019-08-24 17:17:06 [27859] [3] PANIC: /usr/local/sbin/smsbox(gw_panic+0x147) 
[0x43c0b7]
2019-08-24 17:17:06 [27859] [3] PANIC: /usr/local/sbin/smsbox() [0x43d2f0]
2019-08-24 17:17:06 [27859] [3] PANIC: 
/usr/local/sbin/smsbox(octstr_destroy+0x1d) [0x43f2dd]
2019-08-24 17:17:06 [27859] [3] PANIC: /usr/local/sbin/smsbox() [0x412784]
2019-08-24 17:17:06 [27859] [3] PANIC: /usr/local/sbin/smsbox() [0x43331e]
2019-08-24 17:17:06 [27859] [3] PANIC: /lib64/libpthread.so.0(+0x7a51) 
[0x7fc246380a51]
2019-08-24 17:17:06 [27859] [3] PANIC: /lib64/libc.so.6(clone+0x6d) 
[0x7fc24590c93d]

Please help me to understand where I go wrong. Appreciate if you can share me a 
working sample of the XML POST that I can test with.

Regards,
Rasika Udayanga


From: Davor Spasoski [mailto:davor.spaso...@onevip.mk]
Sent: Saturday, August 24, 2019 1:47 PM
To: Rasika Udayanga
Cc: users@kannel.org<mailto:users@kannel.org>
Subject: Re: Send "Sinhala" Letters (Unicode) via Kannel XML Post

Did you try declaring the encoding in the HTTP POST header like this:

 ?

On Aug 24, 2019, at 08:01, Rasika Udayanga 
mailto:ras...@bellvantage.com>> wrote:

Dear Davor
Thank you and appreciate your prompt response.

Yes, as shown below I tried without url encoding the payload and even removing 
the encoding tag from the XML document. BUT STILL NO LUCK




 94777289868
94115753753
රසික
11

bellvantage
    password@123

Re: Send "Sinhala" Letters (Unicode) via Kannel XML Post

2019-08-24 Thread Davor Spasoski




Hi,


I’m rarely using Postman for simple HTTP calls. Try using curl -H


BTW, kannel does state that you need to set the content type in a header not the xml payload and you should do so with the enoding as in the xm example, the encoding is not set within the xml.


"Note: Don't forget to set POST Content-Type to text/xml!"


On Aug 24, 2019, at 14:34, Rasika Udayanga <ras...@bellvantage.com> wrote:




Dear Davor,

I’m kind of confused. Please correct me if I’m wrong.

As per the Kannal user guide I should send an XML document when I do POST for bulk sending. Please refer below screenshot of the Postman that I’m trying to send
 the request through.

 



 

 

When I try to use text/html instead of text/xml smsbox failed
 with below PANIC errors.

 

2019-08-24 17:17:06 [27859] [3] INFO: smsbox: Got HTTP request  from <192.168.51.100>

2019-08-24 17:17:06 [27859] [3] DEBUG: Status: 403 Answer: 

2019-08-24 17:17:06 [27859] [3] PANIC: gwlib/octstr.c:2504: seems_valid_real: Assertion `ostr->data != NULL' failed. (Called from gwlib/octstr.c:325:octstr_destroy.)

2019-08-24 17:17:06 [27859] [3] PANIC: /usr/local/sbin/smsbox(gw_panic+0x147) [0x43c0b7]

2019-08-24 17:17:06 [27859] [3] PANIC: /usr/local/sbin/smsbox() [0x43d2f0]

2019-08-24 17:17:06 [27859] [3] PANIC: /usr/local/sbin/smsbox(octstr_destroy+0x1d) [0x43f2dd]

2019-08-24 17:17:06 [27859] [3] PANIC: /usr/local/sbin/smsbox() [0x412784]

2019-08-24 17:17:06 [27859] [3] PANIC: /usr/local/sbin/smsbox() [0x43331e]

2019-08-24 17:17:06 [27859] [3] PANIC: /lib64/libpthread.so.0(+0x7a51) [0x7fc246380a51]

2019-08-24 17:17:06 [27859] [3] PANIC: /lib64/libc.so.6(clone+0x6d) [0x7fc24590c93d]

 

Please help me to understand where I go wrong. Appreciate if you can share me a working sample of the XML POST that I can test with.

 

Regards,

Rasika Udayanga

 

 



From: Davor Spasoski [mailto:davor.spaso...@onevip.mk] 
Sent: Saturday, August 24, 2019 1:47 PM
To: Rasika Udayanga
Cc: users@kannel.org
Subject: Re: Send "Sinhala" Letters (Unicode) via Kannel XML Post 



 

Did you try declaring the encoding in the HTTP POST header like this: 








 ?








On Aug 24, 2019, at 08:01, Rasika Udayanga <ras...@bellvantage.com> wrote:


 




Dear Davor 


Thank you and appreciate your prompt response.



 



Yes, as shown below I tried without url encoding the payload and even removing the encoding tag from the XML document. BUT STILL NO LUCK



 








    



    



 94777289868



    94115753753



    රසික



    11



    



    bellvantage



    password@123



    



    



    




 



Please assist.



 



Sent on the move. Please excuse typos.



 



 




On Aug 23, 2019, at 8:11 PM, Davor Spasoski <davor.spaso...@onevip.mk> wrote:




Have you tried not url-encoding the payload? 


Your form may already encode the entire xml.



 



Davor










On Aug 23, 2019, at 14:12, Rasika Udayanga <ras...@bellvantage.com> wrote:


 



Hello,



I’m trying to send Sinhala (Sri Lankan) letters through Kannel and that works perfectly with GET method with coding 2 and charset utf-8



 



http://10.9.8.25:13013/cgi-bin/sendsms?username=**=**=94777289868=94115753753=0=%E0%B6%BB%E0%B7%83%E0%B7%92%E0%B6%9A=2=utf-8



Have you tried not url-encoding the payload? 


Your form may already encode the entire xml.



 



Davor










On Aug 23, 2019, at 14:12, Rasika Udayanga <ras...@bellvantage.com> wrote:


 



Hello,



I’m trying to send Sinhala (Sri Lankan) letters through Kannel and that works perfectly with GET method with coding 2 and charset utf-8



 



http://10.9.8.25:13013/cgi-bin/sendsms?username=**=**=94777289868=94115753753=0=%E0%B6%BB%E0%B7%83%E0%B7%92%E0%B6%9A=2=utf-8



 



When I try to send as a XML Post as shown below (having message text url-encoded and without encoded), the messages are delivered to IPhone BUT NOT DELIVERED TO ANDROID PHONES. 



 



Can someone please assist me as to where I’m doing wrong here. 



 







    



    



 94777289868



    94115753753



    %E0%B6%BB%E0%B7%83%E0%B7%92%E0%B6%9A



    11



    



    bellvantage



    password@123



    



    



    



 



 







    



    



 94777289868



    94115753753



    රසික



    11



    



    bellvantage



    password@123

Re: Send "Sinhala" Letters (Unicode) via Kannel XML Post

2019-08-24 Thread Davor Spasoski




Did you try declaring the encoding in the HTTP POST header like this:


 ?


On Aug 24, 2019, at 08:01, Rasika Udayanga <ras...@bellvantage.com> wrote:




Dear Davor
Thank you and appreciate your prompt response.


Yes, as shown below I tried without url encoding the payload and even removing the encoding tag from the XML document. BUT STILL NO LUCK




    
    
 94777289868
    94115753753
    රසික
    11
    
    bellvantage
    password@123
    
    
    



Please assist.



Sent on the move. Please excuse typos.





On Aug 23, 2019, at 8:11 PM, Davor Spasoski <davor.spaso...@onevip.mk> wrote:



Have you tried not url-encoding the payload?
Your form may already encode the entire xml.


Davor



On Aug 23, 2019, at 14:12, Rasika Udayanga <ras...@bellvantage.com> wrote:




Hello,

I’m trying to send Sinhala (Sri Lankan) letters through Kannel and that works perfectly with GET method with coding 2 and charset utf-8

 

http://10.9.8.25:13013/cgi-bin/sendsms?username=**=**=94777289868=94115753753=0=%E0%B6%BB%E0%B7%83%E0%B7%92%E0%B6%9A=2=utf-8

Have you tried not url-encoding the payload?
Your form may already encode the entire xml.


Davor



On Aug 23, 2019, at 14:12, Rasika Udayanga <ras...@bellvantage.com> wrote:




Hello,

I’m trying to send Sinhala (Sri Lankan) letters through Kannel and that works perfectly with GET method with coding 2 and charset utf-8

 

http://10.9.8.25:13013/cgi-bin/sendsms?username=**=**=94777289868=94115753753=0=%E0%B6%BB%E0%B7%83%E0%B7%92%E0%B6%9A=2=utf-8

 

When I try to send as a XML Post as shown below (having message text url-encoded and without encoded), the messages are delivered to IPhone BUT NOT DELIVERED TO ANDROID PHONES. 

 

Can someone please assist me as to where I’m doing wrong here. 

 



    

    

 94777289868

    94115753753

    %E0%B6%BB%E0%B7%83%E0%B7%92%E0%B6%9A

    11

    

    bellvantage

    password@123

    

    

    

 

 



    

    

 94777289868

    94115753753

    රසික

    11

    

    bellvantage

    password@123

    

    

    

 

Regards,

Rasika Udayanga

0777289868









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!

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



















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: DLRs

2019-08-19 Thread Davor Spasoski

I doubt there is such a granularity in MO->AT direction. I doubt the mobile 
handset can set any of the registered_delivery parameters other than SMSC 
originated. (final state delivered or not delivered issued by the SMSC)
As regards kannel, I can't test right now, but I expect that either kannel 
responds positivelly with a final state delivered once bearerbox accepts the 
message and stores it for further delivery to the smsbox or that happens after 
the service is resolved on the smsbox and delivered.
You will have to test. Just keep the smsbox down and observe when will bearebox 
reply to the SMSC.

Davor
-Original Message-
From: users  On Behalf Of Antony Stone
Sent: Saturday, August 17, 2019 3:54 PM
To: users@kannel.org
Subject: Re: DLRs

On Saturday 17 August 2019 at 15:48:19, Antony Stone wrote:

> Indeed - if I turn off one of my kannel instances, so there is only
> one running to either send or receive message to/from my SMSC
> provider, I get DLR status=8 when the message is sent (with the phone
> turned off), and I then get DLR status=1 once the phone is turned on
> and the message is delivered.

So, this now brings me back to my original question:

How do I tell kannel to send DLR with status=1 once my application has 
delivered an incoming message to the user?

I'll rephrase that to be completely clear:

1. Someone with a mobile phone sends an SMS to a number hosted by my SMPP 
provider

2. The provider sends that message to my kannel instance

3. kannel responds with a DLR status=8 to say it's being processed

4. kannel sends the message on to my application, which delivers it to the user

How does my application then tell kannel to send DLR status=1 so that the 
original sender knows it's been delivered?

Thanks,

Antony.

--
"Remember: the S in IoT stands for Security."

 - Jan-Piet Mens

   Please reply to the list;
 please *don't* CC me.

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: DLRs

2019-08-17 Thread Davor Spasoski

Sorry, points 10-12 were not visible on my phone.
The smsc should send back DLR (deliver_sm pdu) on succesful delivery after you 
turn on the phone.
Try with a different handset and watch for the deliver_sm pdu. Run bearerbox in 
debug level.

Davor

> On Aug 17, 2019, at 2:13 PM, Davor Spasoski  wrote:
>
> And what is wrong with that?
> Kannel will report every change in state as soon as the smsc reports back. 
> The non delivery notification will be received upon expiration of the sms 
> which depends on the validity period on the smsc or the expiration you might 
> have set, whatever comes first.
>
> Davor
>
>> On Aug 17, 2019, at 1:45 PM, Antony Stone 
>>  wrote:
>>
>> Hi.
>>
>> I'm now wondering whether I've misunderstood how DLRs actually work.
>>
>> I just tried the following:
>>
>> 1. Make sure my mobile phone is turned on and has good signal.
>>
>> 2. Send a message via kannel to my mobile phone, with dlr_mask=31, indicating
>> that I want to get all status reports possible.
>>
>> 3. I immediately get back a DLR with status=8, which I interpret to mean that
>> the message has been received by the upstream SMSC and is being processed.
>>
>> 4. I then immediately afterwards get a DLR with status=1, which I interpret 
>> to
>> mean that the message has been delivered to my phone.
>>
>> 5. Sure enough, the message has arrived on my phone.
>>
>>
>> 6. Turn the phone off.
>>
>> 7. Repeat step 2 above.
>>
>> 8. I immediately get back a DLR with status=8, just as in step 3 above.
>>
>> 9. Nothing further happens - no surprise there.
>>
>> 10. I turn my phone back on again and wait until it has signal.
>>
>> 11. The second message arrives on my phone.
>>
>> 12. The bit which surprises me is that I do *not* now get a DLR through 
>> kannel
>> with status=1, so my application has no way of knowing that the message has
>> now been delivered.
>>
>>
>> Am I misunderstanding the meaning of status codes 8 and 1, or maybe
>> misunderstanding how DLRs are supposed to work with SMS?
>>
>> I'd be grateful for any comments helping me to understand why I do not get a
>> DLR status=1 after the second message has arrived on my phone.
>>
>>
>> Thanks,
>>
>> Antony.
>>
>> --
>> "The future is already here.   It's just not evenly distributed yet."
>>
>> - William Gibson
>>
>>  Please reply to the list;
>>please *don't* CC me.
>>
>
> 
>
> 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!
>
> Напомена: оне.Вип ДООЕЛ Скопје
> Оваа електронска порака (вклучувајќи ги и прилозите) е доверлива и може да 
> биде заштитена со правни привилегии. Доколку не сте лицето на кое таа му е 
> наменета пораката, не треба да ја копирате, дистрибуирате или да ја откривате 
> нејзината содржина, туку веднаш да ја препратите до испраќачот и да ја 
> избришете оригиналната порака и сите нејзини копии од Вашиот компјутерски 
> систем. Секое неовластено користење на оваа порака во целост или делови од 
> истата е строго забрането. Ве молиме да забележите дека електронските пораки 
> се подложни на промени. оне.Вип ДООЕЛ Скопје не презема одговорност за 
> несоодветно или нецелосно пренесување на информациите содржани во оваа 
> комуникација, ниту пак за било какво задоцнување на приемот или оштетувања на 
> вашиот систем.
> Ве молиме не ја печатете оваа порака освен ако не е неопходно! Зачувајте ја 
> природата!



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 shoul

Re: DLRs

2019-08-17 Thread Davor Spasoski

And what is wrong with that?
Kannel will report every change in state as soon as the smsc reports back. The 
non delivery notification will be received upon expiration of the sms which 
depends on the validity period on the smsc or the expiration you might have 
set, whatever comes first.

Davor

> On Aug 17, 2019, at 1:45 PM, Antony Stone 
>  wrote:
>
> Hi.
>
> I'm now wondering whether I've misunderstood how DLRs actually work.
>
> I just tried the following:
>
> 1. Make sure my mobile phone is turned on and has good signal.
>
> 2. Send a message via kannel to my mobile phone, with dlr_mask=31, indicating
> that I want to get all status reports possible.
>
> 3. I immediately get back a DLR with status=8, which I interpret to mean that
> the message has been received by the upstream SMSC and is being processed.
>
> 4. I then immediately afterwards get a DLR with status=1, which I interpret to
> mean that the message has been delivered to my phone.
>
> 5. Sure enough, the message has arrived on my phone.
>
>
> 6. Turn the phone off.
>
> 7. Repeat step 2 above.
>
> 8. I immediately get back a DLR with status=8, just as in step 3 above.
>
> 9. Nothing further happens - no surprise there.
>
> 10. I turn my phone back on again and wait until it has signal.
>
> 11. The second message arrives on my phone.
>
> 12. The bit which surprises me is that I do *not* now get a DLR through kannel
> with status=1, so my application has no way of knowing that the message has
> now been delivered.
>
>
> Am I misunderstanding the meaning of status codes 8 and 1, or maybe
> misunderstanding how DLRs are supposed to work with SMS?
>
> I'd be grateful for any comments helping me to understand why I do not get a
> DLR status=1 after the second message has arrived on my phone.
>
>
> Thanks,
>
> Antony.
>
> --
> "The future is already here.   It's just not evenly distributed yet."
>
> - William Gibson
>
>   Please reply to the list;
> please *don't* CC me.
>

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: Three out of four

2019-08-17 Thread Davor Spasoski

I’m not sure I quite understand your question, but if it is about signaling 
back the mobile originator that kannel has received the message, it will 
automatically happen if the sender has requested a delivery report and the SMSC 
is set properly to generate the DLR to the sender once kannel acknowledges the 
deliver_sm PDU. If you are not receiving the DLRs, you should check the smsc 
setup. It’s usually the store and forwaerd engine that is responsible for the 
DLRs.

I hope this is of help.

> On Aug 17, 2019, at 11:31, Antony Stone  
> wrote:
>
> Hi
>
> Can anyone else tell me what magic I'm missing here?
>
> How is everyone else sending delivery notifications for incoming SMS?
>
> I'm happy to post my kannel.conf if that helps.
>
> Thanks,
>
> Antony.
>
> On Friday 16 August 2019 at 13:25:13, Antony Stone wrote:
>
>> On Friday 16 August 2019 at 12:23:57, Alexander Malysh wrote:
>>> Hi,
>>>
>>> define dlr-url in your request to smsbox and you are done.
>>
>> I have defined that - it's how item 2 in my list below is working.
>>
>> kannel sends a GET request to that URL when a delivery report is *received*
>> by kannel in response to a message we have *sent*
>>
>> I am looking for the mechanism to *send* a delivery notification in
>> response to a message we have *received* so that the sender knows we have
>> delivered it to our end user.
>>
 Am 16.08.2019 um 11:59 schrieb Antony Stone
 :

 Hi.

 I've recently installed kannel 1.4.4 on a Debian Stretch machine (from
 the standard Debian repository package).

 I have an account with an SMSC provider and I'm talking to them using
 SMPP 3.4

 So far I've got kannel set up and configured to:

 1. Send SMS to mobiles - works.

 2. Receive delivery notifications for sent messages - works.

 3. Receive SMS from mobiles - works.

 The bit I'm missing is that I can't work out how to send a delivery
 notification for messages I receive.

 For the inbound delivery notifications, I'm getting a status code 8
 from the SMSC when they've received my message and are processing it,
 then I get a status code 1 when the message is delivered to the
 mobile.

 Can I configure kannel to automatically send status code 8 when it gets
 an inbound message, and passes it on to my delivery URL?

 And then, how do I send the appropriate request to kannel to say
 "message has been delivered to user" to get it to send out status code
 1?

 Thanks,

 Antony.
>
> --
> Police have found a cartoonist dead in his house.  They say that details are
> currently sketchy.
>
>   Please reply to the list;
> please *don't* CC me.
>

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: How to Set Data coding scheme to Latin1 (ISO-8859-1)

2019-04-11 Thread Davor Spasoski

Hi Manas,

Per the SMPP and GSM 03.38 standard, you have the following data codings (DCS):
0 – default SMSC alphabet
1 – ASCII
2 – 8 – bit binary
3 – Latin 1
4 – 8 – bit binary
5 – JIS
6 – Cyrillic
7 – Latin/Hebrew
8 – UCS-2
9 – Program Encoding
10 – Music codes
13 -  Extended Kanji
14 – KS C 5601

So, you have two options 3 or 0 if they’ve set the default SMSC alphabet to 
Latin1. But the problem is kannel does not allow you to set dcs specifically 
plus is using gsm alphabet upstream as default (unless otherwise noted in the 
alt-charset parameter)

So, my guess is try changing alt-charset to latin1 which would probably still 
result in dcs=0 but hopefully that’s what the SMSC expects or try coding=2 and 
encode your payload in hex representation of latin1 characters.


Davor Spasoski

From: users  On Behalf Of Manas Mohanty
Sent: Thursday, April 11, 2019 1:42 PM
To: kannel users@kannel.org 
Subject: How to Set Data coding scheme to Latin1 (ISO-8859-1)

Hi,
Our upstream carrier wants us to send message with text encoding in 
Latin1(ISO-8859-1).
Please help me to set DCS set to Latin1 (ISO-8859-1) in kannel.



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: UDH Support on OpenSMPPBox

2019-03-21 Thread Davor Spasoski




Are you trying to reverse engineer iMessage? I don't think it uses MAP for that purpose. iMessage is available only on Wi-Fi/Cellular data, it’s something proprietary to Apple and I’d even be surprised if it’s related to RCS. Can you shed some light if you
 know the insights?


Cheers


On Mar 21, 2019, at 2:27 AM, garz m  wrote:







Dear Users,


Greetings!


Just like to consult if our Opensmppbox service supports Apple type Push Notification such as imessage and facetime? I have seen the correct UDH on the PDU however I found a - maybe an error that I hope you can help check. I'm sharing here the
 PDU captured:
==
DEBUG: SMPP: Got PDU:
DEBUG: SMPP PDU 0x7f1c10001270 dump:
DEBUG:   type_name: submit_sm
DEBUG:   command_id: 4 = 0x0004
DEBUG:   command_status: 0 = 0x
DEBUG:   sequence_number: 128203 = 0x0001f4cb
DEBUG:   service_type: NULL
DEBUG:   source_addr_ton: 1 = 0x0001
DEBUG:   source_addr_npi: 1 = 0x0001
DEBUG:   source_addr: ""
DEBUG:   dest_addr_ton: 1 = 0x0001
DEBUG:   dest_addr_npi: 1 = 0x0001
DEBUG:   destination_addr: ""
DEBUG:   esm_class: 67 = 0x0043
DEBUG:   protocol_id: 0 = 0x
DEBUG:   priority_flag: 0 = 0x
DEBUG:   schedule_delivery_time: NULL
DEBUG:   validity_period: NULL
DEBUG:   registered_delivery: 1 = 0x0001
DEBUG:   replace_if_present_flag: 0 = 0x
DEBUG:   data_coding: 4 = 0x0004
DEBUG:   sm_default_msg_id: 0 = 0x
DEBUG:   sm_length: 90 = 0x005a
DEBUG:   short_message:
DEBUG:    Octet string at 0x7f1c100014d0:
DEBUG:  len:  90
DEBUG:  size: 91
DEBUG:  immutable: 0
DEBUG:  data: 06 05 04 15 79 00 00 42 66 78 20 32 34 20 73 75   y..Bfx 24 su
DEBUG:  data: 20 61 69 64 6c 75 65 2e 20 3f 20 32 50 76 3d 20    aidlue. ? 2Pv=
DEBUG:  data: 35 39 31 20 33 2d 38 20 39 2b 52 53 72 33 45 52   591 3-8 9+RSr3ER
DEBUG:  data: 20 38 3b 30 35 20 3d 33 6e 20 45 3d 33 20 34 31    8;05 =3n E=3 41
DEBUG:  data: 30 32 20 37 30 3d 20 31 31 33 73 20 36 42 3b 20   02 70= 113s 6B;
DEBUG:  data: 47 38 34 3b 20 30 35 43 33 2e G84; 05C3.
DEBUG:    Octet string dump ends.
DEBUG: SMPP PDU dump ends.
DEBUG: SMPP: UDH length read as 7
DEBUG: Found unknown IEI 5 with length 4
DEBUG: UDH was present, but no reference to multipart SMSs
DEBUG: Msg object at 0x7f1c10001a90:
DEBUG:  type: sms
DEBUG:  sms.sender:
DEBUG:  Octet string at 0x7f1c1000:
DEBUG:    len:  13
DEBUG:    size: 1024
DEBUG:    immutable: 0
DEBUG:    data: 2b +
DEBUG:  Octet string dump ends.
DEBUG:  sms.receiver:
DEBUG:  Octet string at 0x7f1c1000:
DEBUG:    len:  13
DEBUG:    size: 1024
DEBUG:    immutable: 0
DEBUG:    data: 2b +
DEBUG:  Octet string dump ends.
DEBUG:  sms.udhdata:
DEBUG:  Octet string at 0x7f1c100022e0:
DEBUG:    len:  7
DEBUG:    size: 8
DEBUG:    immutable: 0
DEBUG:    data: 06 05 04 15 79 00 00  y..
DEBUG:  Octet string dump ends.
DEBUG:  sms.msgdata:
DEBUG:  Octet string at 0x7f1c100014d0:
DEBUG:    len:  83
DEBUG:    size: 91
DEBUG:    immutable: 0
DEBUG:    data: 42 66 78 20 32 34 20 73 75 20 61 69 64 6c 75 65   Bfx 24 su aidlue
DEBUG:    data: 2e 20 3f 20 32 50 76 3d 20 35 39 31 20 33 2d 38   . ? 2Pv= 591 3-8
DEBUG:    data: 20 39 2b 52 53 72 33 45 52 20 38 3b 30 35 20 3d    9+RSr3ER 8;05 =
DEBUG:    data: 33 6e 20 45 3d 33 20 34 31 30 32 20 37 30 3d 20   3n E=3 4102 70=
DEBUG:    data: 31 31 33 73 20 36 42 3b 20 47 38 34 3b 20 30 35   113s 6B; G84; 05
DEBUG:    data: 43 33 2e  C3.
DEBUG:  Octet string dump ends.
DEBUG:  sms.time: 1552605905
DEBUG:  sms.smsc_id:
DEBUG:  sms.smsc_number:
DEBUG:  sms.foreign_id:
DEBUG:  sms.service:
DEBUG:  Octet string at 0x7f1c100022b0:
DEBUG:    len:  4
DEBUG:    size: 5
DEBUG:    immutable: 0
DEBUG:    data:    
DEBUG:  Octet string dump ends.
DEBUG:  sms.account:
DEBUG:  sms.id: e20f497c-cc20-45c2-b989-c9006d828d24
DEBUG:  sms.sms_type: 2
DEBUG:  sms.mclass: -1
DEBUG:  sms.mwi: -1
DEBUG:  sms.coding: 1
DEBUG:  sms.compress: 0
DEBUG:  sms.validity: -1
DEBUG:  sms.deferred: -1
DEBUG:  sms.dlr_mask: 19
DEBUG:  sms.dlr_url:
DEBUG:  sms.pid: 0
DEBUG:  sms.alt_dcs: 0
DEBUG:  sms.rpi: -1
DEBUG:  sms.charset:
DEBUG:  sms.boxc_id:
DEBUG:  Octet string at 0x7f1c10001590:
DEBUG:    len:  4
DEBUG:    size: 5
DEBUG:    immutable: 0
DEBUG:    data:    
DEBUG:  Octet string dump ends.
DEBUG:  sms.binfo:
DEBUG:  sms.msg_left: -1
DEBUG:  sms.split_parts: (nil)
DEBUG:  sms.priority: 0
DEBUG:  sms.resend_try: -1
DEBUG:  sms.resend_time: -1
DEBUG:  sms.meta_data:
DEBUG:  Octet string at 0x7f1c10002310:
DEBUG:    len:  6
DEBUG:    size: 1024
DEBUG:

RE: kannel with sigtran

2019-02-11 Thread Davor Spasoski

I would start the long and winding road with a high level overview book such as 
Mobile Meassaging Technologies by Gwenael le Bodic or something more serious 
and then dig in the docs of the SMS governing bodies, ETSI, 3GPP, IETF having 
all the spcifics of the service.
Yes, you can use kannel as SMPP server (opensmppbox)

Davor Spasoski
From: eyas barhouk 
Sent: Monday, February 11, 2019 10:44 AM
To: Davor Spasoski ; users@kannel.org
Subject: Re: kannel with sigtran

Dear Davor,

thanks for your kind reply.

i am already thinking about the architecture that i will use to build the SMSC.
it could be (kannel for smpp , Queue with database, and SIGTRAN PROTOCOL SUITE 
from shabed or Open SIGTRAN Project) but for now i don't know how to make it 
work or how the whole of system should work.
so i'm looking for any kind of experience with this domain.

B.R
Eyas Barhok

From: Davor Spasoski mailto:davor.spaso...@onevip.mk>>
Sent: Monday, February 11, 2019 8:59 AM
To: eyas barhouk; users@kannel.org<mailto:users@kannel.org>
Subject: RE: kannel with sigtran

Hi Eyas,

I’m not sure if you allready went throught the architecture of and SMSC, but 
implementing one is quite an endevor with a large scope of problems (not only 
technical) that need to be solved.

Regardless of Sigtran or SS7, none of the upper layer protocols (MAP, TCAP and 
SCCP) are supported on kannel. Kannel is naturally SMS gateway helping to 
bridge tha gap betwenn the IT world and the complexities of the protocols 
listed above.

Other than http, radius, smpp, and a bunch of now more or less obsolete 
protocols I’m not aware of anything closer to the tellecommunication protocols.

Kannel is very good at what it does, but it’s not an SMSC.

SMSC typically needs SS7/Sigtran capable element that receives and sends SMS 
from wireless network users a store and forward engine with elaborate retry 
schemes and a way to resolve the routing (SRI_SM towards HLR). If you are after 
an entity that would only send application originated messages and you are 
capable of resolving the technical demands, you would still need a telecom 
operator to give you a whitelisted global title, otherwise, most of the 
operators today will simply block the traffic from your SMSC.

If you decide to pursue the challenge, try the open SS7 protocol stack and 
start from there, but you will need access to a telecom network.

Davor Spasoski

From: users mailto:users-boun...@kannel.org>> On 
Behalf Of eyas barhouk
Sent: Monday, February 11, 2019 8:53 AM
To: users@kannel.org<mailto:users@kannel.org>
Subject: kannel with sigtran

Good evening dears,

i'm trying to build GSM SMSC starting from kannel, so is that's applicable and 
what other components i may need to deal with SIGTRAN signalling?

Thanks in advance

Best regards

Eyas

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!

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

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 mes

RE: kannel with sigtran

2019-02-11 Thread Davor Spasoski

Hi Eyas,

I'm not sure if you allready went throught the architecture of and SMSC, but 
implementing one is quite an endevor with a large scope of problems (not only 
technical) that need to be solved.
Regardless of Sigtran or SS7, none of the upper layer protocols (MAP, TCAP and 
SCCP) are supported on kannel. Kannel is naturally SMS gateway helping to 
bridge tha gap betwenn the IT world and the complexities of the protocols 
listed above.
Other than http, radius, smpp, and a bunch of now more or less obsolete 
protocols I'm not aware of anything closer to the tellecommunication protocols.
Kannel is very good at what it does, but it's not an SMSC.

SMSC typically needs SS7/Sigtran capable element that receives and sends SMS 
from wireless network users a store and forward engine with elaborate retry 
schemes and a way to resolve the routing (SRI_SM towards HLR). If you are after 
an entity that would only send application originated messages and you are 
capable of resolving the technical demands, you would still need a telecom 
operator to give you a whitelisted global title, otherwise, most of the 
operators today will simply block the traffic from your SMSC.

If you decide to pursue the challenge, try the open SS7 protocol stack and 
start from there, but you will need access to a telecom network.

Davor Spasoski

From: users  On Behalf Of eyas barhouk
Sent: Monday, February 11, 2019 8:53 AM
To: users@kannel.org
Subject: kannel with sigtran

Good evening dears,

i'm trying to build GSM SMSC starting from kannel, so is that's applicable and 
what other components i may need to deal with SIGTRAN signalling?

Thanks in advance
Best regards
Eyas




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: Kannel & USSD status

2019-01-20 Thread Davor Spasoski

Your USSD provider should give instructions how to use the api. Smpp is merely 
used to convey the messages to/from the user by using the standard pdus 
(submit_sm and deliver_sm). Probably some TLVs will be used (imsi is a good 
example) and other notable difference is that ussd is session based, so you 
might have session_id as a parameter somewhere.
Anyway, you need to study your provider’s api and ussd as a service a little 
bit.

—Davor

> On Jan 20, 2019, at 5:35 PM, Damian Dimmich  
> wrote:
>
> Hi,
>
> I'm in the process of setting up USSD -> web application integration with a 
> mobile telecoms provider (I have SMPP 3.4 based access to their gateway, and 
> they support USSD messaging).
>
> While looking at options for setting this up, and kannel came up, however 
> looking through the mail archives it's not entirely clear that USSD is 
> supported out of the box with Kannel, potentially requiring 
> patches/recompilation.
>
> I've got  kannel  1.4.4-4 running on a debian 9 machine, and connect to that 
> via a python smpp client library, however I can't seem to figure out how to 
> simulate initiating a USSD session.  Are there some command line 
> tools/clients that can do this or is more a case of write your own?  I've 
> spotted fakesmsc but can't see how to generate ussd traffic from that.
>
> Ideally I'd like to configure kannel/smsbox/sms-service to call into an HTTP 
> api with a session id/phone number/subscriberid - so that I can go back and 
> forth between the user and my server to get answers to a few questions.
>
> Using SMPPSim's inject_mo I can simulate SMS and SMS responses already to my 
> HTTP based application server.
>
> Thank you very much for any pointers in advance,  I attach my current config 
> below.
>
> Damian
>
>
> group = core
> admin-port = 13000
> admin-password = bar
> admin-deny-ip = ""
> admin-allow-ip = "*.*.*.*"
> smsbox-port = 13003
> wdp-interface-name = "*"
> log-file = "/var/log/kannel/bearerbox.log"
> box-deny-ip = "*.*.*.*"
> box-allow-ip = "127.0.0.1"
>
> group = smsbox
> # smsbox-id = mysmsbox
> bearerbox-host = localhost
> sendsms-port = 1025
> global-sender = 1000
> log-level = 0
> log-file = "/var/log/kannel/smsbox.log"
> mo-recode = true
> sendsms-port = 13013
>
> group = smsc
> smsc = smpp
> smsc-id = SMPPSim
> host = 10.10.10.1
> port = 2775
> transceiver-mode = 1
> smsc-username = smppclient1
> smsc-password = password
> system-type = 'VMA'
> #service-type = 'test'
> interface-version = 34
> system-id = smppclient
> preferred-smsc-id = SMPPSim
>
> group = sms-service
> keyword = default
> # get-url = "http://localhost:8000/api/v1/sms/?phone=%p=%a;
> # accept-x-kannel-headers = true
> post-url = "http://localhost:8000/api/v1/sms/;
> catch-all = true
>
> group = smpp-tlv
> name = ussd_service_op
> tag = 0x0501
> type = integer
> length = 1
>
>

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: Incoming messages take too long to show up

2018-12-03 Thread Davor Spasoski

Well, I don’t see anything special in your config. I’ve never used spool store 
type and if anything, I would try with single file storage type prior to your 
next peak and see if that makes a difference. Don't forget the dump and monitor 
your system’s cpu, i/o for anything unusual that might be happening.

You could pre-emtively test your whole chain by using the test smsc and 
injecting desired number of SMS/sec to your application. Check how your app 
behaves under such load.

Good luck!

—Davor

> On Dec 3, 2018, at 8:40 PM, Manuel García Cabrera 
>  wrote:
>
> Here is my config file, with "x" where I don't think there would be 
> something that could interest you.
>
>
> group = core
> admin-port = x
> smsbox-port = x
> admin-password = x
> status-password = x
> store-type = spool
> store-location = /x/x/x/
> log-file = "x"
> log-level = 2
> box-deny-ip = x
> box-allow-ip = x
> admin-allow-ip = x
> sms-resend-retry = 100
>
> group = smsc
> smsc = smpp
> smsc-id = MY-SMSC-ID
> denied-smsc-id = x
> allowed-smsc-id = MY-SMSC-ID
> host = x
> port = x
> smsc-username = x
> smsc-password = x
> system-type = SMPP
> transceiver-mode = true
> source-addr-autodetect = false
> source-addr-ton = 5
> source-addr-npi = 1
> dest-addr-ton = 1
> dest-addr-npi = 1
> bind-addr-ton = 1
> bind-addr-npi = 1
> reconnect-delay = 90
> enquire-link-interval = 10
>
> group = sendsms-user
> username = x
> password = x
> forced-smsc = MY-SMSC-ID
> user-deny-ip = ""
> user-allow-ip = ""
> concatenation = true
> max-messages = 4
>
> group = sms-service
> accepted-smsc = MY-SMSC-ID
> keyword = default
> get-url = "http://my.app.url;
> concatenation = true
> max-messages = 0
> omit-empty = true
> accept-x-kannel-headers = true
>
>
> To send messages, I insert them in a SQL Box Database. To receive messages, 
> my app listenes to the url configured in "get-url".
>
>
> On 3/12/18 16:31, Davor Spasoski wrote:
>> Well, is it an smsbox service with http get/post/xml call, a shell execute 
>> or you are using opensmppbox maybe?
>>
>> You should include your config file.
>>
>>> On Dec 3, 2018, at 8:25 PM, Manuel García Cabrera 
>>>  wrote:
>>>
>>> Store Type is "spool". What do you mean with how do I call the service?
>>>
>>> Regarding the tcpdump, I'm not having the issue right now because there is 
>>> no high traffic. I could only get it when the problem occurs, but it would 
>>> be already too late by then. I will though if it happens again this weekend.
>>>
>>> On 3/12/18 15:52, Davor Spasoski wrote:
>>>> OK, I get it. I think you should disclose your kannel.config for the 
>>>> community to come up with ideas. (what store methods are you using, how do 
>>>> you call the service, etc…)
>>>> Did you try to tcpdump and check the communication between bearerbox and 
>>>> smsbox? It will look like smpp protocol with improperly used PDUs, but you 
>>>> would still be able to recognize sender and short number. Check how it 
>>>> matches with the deliver_sm time. That way you will isolate the component 
>>>> that introduces the delay.
>>>>
>>>> —Davor
>>>>
>>>>> On Dec 3, 2018, at 4:06 PM, Manuel García Cabrera 
>>>>>  wrote:
>>>>>
>>>>> Hi Davor,
>>>>>
>>>>> 1. I say that kannel is logging the incoming SMS and sending it to my app 
>>>>> minutes after the SMSC sent the message.
>>>>> 2. The reply is the submit_sm that my application sends back. The 
>>>>> deliver_sm "OK" is being sent almost instantly according to the tcpdump. 
>>>>> The submit_sm that the application sends back is taking minutes because 
>>>>> of the delay between the deliver_sm "OK" and Kannel sending the message 
>>>>> to the application. The application takes under a second to reply when it 
>>>>> gets the message.
>>>>>
>>>>> Thank you
>>>>>
>>>>> On 3/12/18 11:57, Davor Spasoski wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I'm just trying to understand this.
>>>>>> - You basically say that kannel is logging the incoming and reply sms 
>>>>>> behind of time on smsc, right?
>>>>>> - What do you consider a "reply", t

Re: Incoming messages take too long to show up

2018-12-03 Thread Davor Spasoski

Well, is it an smsbox service with http get/post/xml call, a shell execute or 
you are using opensmppbox maybe?

You should include your config file.

> On Dec 3, 2018, at 8:25 PM, Manuel García Cabrera 
>  wrote:
>
> Store Type is "spool". What do you mean with how do I call the service?
>
> Regarding the tcpdump, I'm not having the issue right now because there is no 
> high traffic. I could only get it when the problem occurs, but it would be 
> already too late by then. I will though if it happens again this weekend.
>
> On 3/12/18 15:52, Davor Spasoski wrote:
>> OK, I get it. I think you should disclose your kannel.config for the 
>> community to come up with ideas. (what store methods are you using, how do 
>> you call the service, etc…)
>> Did you try to tcpdump and check the communication between bearerbox and 
>> smsbox? It will look like smpp protocol with improperly used PDUs, but you 
>> would still be able to recognize sender and short number. Check how it 
>> matches with the deliver_sm time. That way you will isolate the component 
>> that introduces the delay.
>>
>> —Davor
>>
>>> On Dec 3, 2018, at 4:06 PM, Manuel García Cabrera 
>>>  wrote:
>>>
>>> Hi Davor,
>>>
>>> 1. I say that kannel is logging the incoming SMS and sending it to my app 
>>> minutes after the SMSC sent the message.
>>> 2. The reply is the submit_sm that my application sends back. The 
>>> deliver_sm "OK" is being sent almost instantly according to the tcpdump. 
>>> The submit_sm that the application sends back is taking minutes because of 
>>> the delay between the deliver_sm "OK" and Kannel sending the message to the 
>>> application. The application takes under a second to reply when it gets the 
>>> message.
>>>
>>> Thank you
>>>
>>> On 3/12/18 11:57, Davor Spasoski wrote:
>>>> Hi,
>>>>
>>>> I'm just trying to understand this.
>>>> - You basically say that kannel is logging the incoming and reply sms 
>>>> behind of time on smsc, right?
>>>> - What do you consider a "reply", the deliver_sm "OK" or the submit_sm 
>>>> that the application sends back?
>>>>
>>>> BR,
>>>> --Davor
>>>>
>>>> -Original Message-
>>>> From: users  On Behalf Of Manuel García Cabrera
>>>> Sent: Monday, December 3, 2018 3:09 PM
>>>> To: users@kannel.org
>>>> Subject: Incoming messages take too long to show up
>>>>
>>>> Hi everyone. I'm having problems with incoming messages during high 
>>>> traffic. During a campaign the other day I was receving 85 messages per 
>>>> second, however, clients were complaining that my reply took over five 
>>>> minutes. I checked the logs, and I found out that wasn't the case, I was 
>>>> replying only a few seconds after Kannel was logging the message.
>>>> However, my Carrier sent me a tcpdump were they showed that Kannel was in 
>>>> fact replying to the incoming message with a Deliver_sm "OK" with only a 
>>>> few seconds of delay, but that was minutes before the message was logged 
>>>> in Kannel logs. Where does the message go during that time? What can I 
>>>> improve?
>>>>
>>>>
>>>> 
>>>>
>>>> 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: Incoming messages take too long to show up

2018-12-03 Thread Davor Spasoski

OK, I get it. I think you should disclose your kannel.config for the community 
to come up with ideas. (what store methods are you using, how do you call the 
service, etc…)
Did you try to tcpdump and check the communication between bearerbox and 
smsbox? It will look like smpp protocol with improperly used PDUs, but you 
would still be able to recognize sender and short number. Check how it matches 
with the deliver_sm time. That way you will isolate the component that 
introduces the delay.

—Davor

> On Dec 3, 2018, at 4:06 PM, Manuel García Cabrera 
>  wrote:
>
> Hi Davor,
>
> 1. I say that kannel is logging the incoming SMS and sending it to my app 
> minutes after the SMSC sent the message.
> 2. The reply is the submit_sm that my application sends back. The deliver_sm 
> "OK" is being sent almost instantly according to the tcpdump. The submit_sm 
> that the application sends back is taking minutes because of the delay 
> between the deliver_sm "OK" and Kannel sending the message to the 
> application. The application takes under a second to reply when it gets the 
> message.
>
> Thank you
>
> On 3/12/18 11:57, Davor Spasoski wrote:
>> Hi,
>>
>> I'm just trying to understand this.
>> - You basically say that kannel is logging the incoming and reply sms behind 
>> of time on smsc, right?
>> - What do you consider a "reply", the deliver_sm "OK" or the submit_sm that 
>> the application sends back?
>>
>> BR,
>> --Davor
>>
>> -Original Message-
>> From: users  On Behalf Of Manuel García Cabrera
>> Sent: Monday, December 3, 2018 3:09 PM
>> To: users@kannel.org
>> Subject: Incoming messages take too long to show up
>>
>> Hi everyone. I'm having problems with incoming messages during high traffic. 
>> During a campaign the other day I was receving 85 messages per second, 
>> however, clients were complaining that my reply took over five minutes. I 
>> checked the logs, and I found out that wasn't the case, I was replying only 
>> a few seconds after Kannel was logging the message.
>> However, my Carrier sent me a tcpdump were they showed that Kannel was in 
>> fact replying to the incoming message with a Deliver_sm "OK" with only a few 
>> seconds of delay, but that was minutes before the message was logged in 
>> Kannel logs. Where does the message go during that time? What can I improve?
>>
>>
>> 
>>
>> 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!
>>
>> Напомена: оне.Вип ДООЕЛ Скопје
>> Оваа електронска порака (вклучувајќи ги и прилозите) е доверлива и може да 
>> биде заштитена со правни привилегии. Доколку не сте лицето на кое таа му е 
>> наменета пораката, не треба да ја копирате, дистрибуирате или да ја 
>> откривате нејзината содржина, туку веднаш да ја препратите до испраќачот и 
>> да ја избришете оригиналната порака и сите нејзини копии од Вашиот 
>> компјутерски систем. Секое неовластено користење на оваа порака во целост 
>> или делови од истата е строго забрането. Ве молиме да забележите дека 
>> електронските пораки се подложни на промени. оне.Вип ДООЕЛ Скопје не презема 
>> одговорност за несоодветно или нецелосно пренесување на информациите 
>> содржани во оваа комуникација, ниту пак за било какво задоцнување на приемот 
>> или оштетувања на вашиот систем.
>> Ве молиме не ја печатете оваа порака освен ако не е неопходно! Зачувајте ја 
>> природата!
>




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 messag

RE: Incoming messages take too long to show up

2018-12-03 Thread Davor Spasoski

Hi,

I'm just trying to understand this.
- You basically say that kannel is logging the incoming and reply sms behind of 
time on smsc, right?
- What do you consider a "reply", the deliver_sm "OK" or the submit_sm that the 
application sends back?

BR,
--Davor

-Original Message-
From: users  On Behalf Of Manuel García Cabrera
Sent: Monday, December 3, 2018 3:09 PM
To: users@kannel.org
Subject: Incoming messages take too long to show up

Hi everyone. I'm having problems with incoming messages during high traffic. 
During a campaign the other day I was receving 85 messages per second, however, 
clients were complaining that my reply took over five minutes. I checked the 
logs, and I found out that wasn't the case, I was replying only a few seconds 
after Kannel was logging the message.
However, my Carrier sent me a tcpdump were they showed that Kannel was in fact 
replying to the incoming message with a Deliver_sm "OK" with only a few seconds 
of delay, but that was minutes before the message was logged in Kannel logs. 
Where does the message go during that time? What can I improve?




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: Kannel multiboxing.

2018-11-28 Thread Davor Spasoski

Hm, that could be for a number of reasons. If kannel is firing the submit_sm 
PDUs fast enough, check if you are getting any throttling errors? Also check 
the throughput to your SMSC.
Alternatively, you can always multi-bind to the same SMSC using same smsc-id in 
your kannel config and kannel will load balance for you on the same instance.

--Davor

-Original Message-
From: Gert Tamm 
Sent: Wednesday, November 28, 2018 9:55 AM
To: Davor Spasoski ; users@kannel.org
Subject: Re: Kannel multiboxing.

The reason I wanan try Load Balancing, is that our outgoing sms speed is slow 
when we send it maxes out (8.3x,5.xx,x.xx). How could I make it better?


11/27/2018 14:06 Davor Spasoski kirjutas:
> 1. Yes, just dedicate unique ports to your two instances of the boxes
> 2. This is actually a very good question to which I don't have an answer. It 
> is certainly possible to instruct both instances to use the same DB, 
> typically used as a store and/or DLR repository, but I wonder how will kannel 
> handle the concurrency? Load balancing is usually brought on kannel table in 
> the context of balancing between SMS centers, not instances of kannel. It's 
> best if you try, and you would probably need to set same smsc-ids, etc. I'm 
> interested of the results.
> If you wish to accomplish kannel redundancy another way is to  use 
> active/standby kannel, and I don't see a reason why wouldn't this work.
>
> BR,
> Davor Spasoski
>
> one.Vip DOOEL Skopje | Ploshtad Presveta Bogorodica 1 | 1000 Skopje | 
> Macedonia
> -Original Message-
> From: users  On Behalf Of Gert Tamm
> Sent: Tuesday, November 27, 2018 12:29 PM
> To: users@kannel.org
> Subject: Kannel multiboxing.
>
> Hello,
>
> I have question if you could multibox kannel in one computer?
>
> And how to set up 2 servers with one database to load balance the sending of 
> SMS?
>
> --
> Tervitades/Best Wishes,
> Gert Tamm
> Süsteemiadministraator/System administrator
> E-mail: g...@messenger.ee
> Direct Messenger OÜ
>
>
>
> 
>
> 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!
>
> Напомена: оне.Вип ДООЕЛ Скопје
> Оваа електронска порака (вклучувајќи ги и прилозите) е доверлива и може да 
> биде заштитена со правни привилегии. Доколку не сте лицето на кое таа му е 
> наменета пораката, не треба да ја копирате, дистрибуирате или да ја откривате 
> нејзината содржина, туку веднаш да ја препратите до испраќачот и да ја 
> избришете оригиналната порака и сите нејзини копии од Вашиот компјутерски 
> систем. Секое неовластено користење на оваа порака во целост или делови од 
> истата е строго забрането. Ве молиме да забележите дека електронските пораки 
> се подложни на промени. оне.Вип ДООЕЛ Скопје не презема одговорност за 
> несоодветно или нецелосно пренесување на информациите содржани во оваа 
> комуникација, ниту пак за било какво задоцнување на приемот или оштетувања на 
> вашиот систем.
> Ве молиме не ја печатете оваа порака освен ако не е неопходно! Зачувајте ја 
> природата!

--
Tervitades/Best Wishes,
Gert Tamm
Süsteemiadministraator/System administrator
E-mail: g...@messenger.ee
Direct Messenger OÜ




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: Kannel multiboxing.

2018-11-27 Thread Davor Spasoski

1. Yes, just dedicate unique ports to your two instances of the boxes
2. This is actually a very good question to which I don't have an answer. It is 
certainly possible to instruct both instances to use the same DB, typically 
used as a store and/or DLR repository, but I wonder how will kannel handle the 
concurrency? Load balancing is usually brought on kannel table in the context 
of balancing between SMS centers, not instances of kannel. It's best if you 
try, and you would probably need to set same smsc-ids, etc. I'm interested of 
the results.
If you wish to accomplish kannel redundancy another way is to  use 
active/standby kannel, and I don't see a reason why wouldn't this work.

BR,
Davor Spasoski

one.Vip DOOEL Skopje | Ploshtad Presveta Bogorodica 1 | 1000 Skopje | Macedonia
-Original Message-
From: users  On Behalf Of Gert Tamm
Sent: Tuesday, November 27, 2018 12:29 PM
To: users@kannel.org
Subject: Kannel multiboxing.

Hello,

I have question if you could multibox kannel in one computer?

And how to set up 2 servers with one database to load balance the sending of 
SMS?

--
Tervitades/Best Wishes,
Gert Tamm
Süsteemiadministraator/System administrator
E-mail: g...@messenger.ee
Direct Messenger OÜ





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: using kannel for sms/mms to and from computer to cell phone

2018-04-12 Thread Davor Spasoski

Hi,

I’m not aware of Mighty text. At first glance it looks to me as a product for 
different purpose. Kannel is mainly used as a gateway tied to an SMSC on one 
side and the content provider on the other for processing large volumes of SMS. 
Yes, modem usage is possible for personal SMS based services, but you have 
custom build your complete solution. On the other hand, Migthy text looks like 
an of the shelf, elaborate closed source product

Davor Spasoski
From: Ron T [mailto:rontech...@gmail.com]
Sent: Wednesday, April 11, 2018 8:22 PM
To: Davor Spasoski <davor.spaso...@onevip.mk>
Cc: users@kannel.org
Subject: Re: using kannel for sms/mms to and from computer to cell phone

Thanks for the help Davor.  Mighty Text uses the users cell phone to send and 
receive messages as far as I understand it. Are they also making their phone 
work as a modem on a linux box? Basically the user can't send and receive 
messages without their cell phone on. The user installs the app on their phone 
and a web browser plugin on the their computer. How could I duplicate that 
setup? Are they using something like Kannel or a different setup? Thanks!

On Tue, Apr 10, 2018 at 11:50 PM, Davor Spasoski 
<davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>> wrote:
You can use kannel to send/receive SMS with your phone but first you have to 
make your phone work as a modem on a Linux box, then configure kannel to use 
that device (AT SMSC section).
To send MMS, you will need something else in addition to kannel. Mbuni could be 
used for that, but I see no activity about this project very long time, so you 
might have a problem compiling it on a modern Linux distribution.
The way kannel works with mbuni: when mms is to be received, your device will 
receive MMS formatted WAP push SMS having a URL where to grab the MMS from. 
This SMS is passed to mbuni and mbuni fetches the content. Then it’s up to you 
to process that.

It’s a long way and it will take plenty of time. If you have it, it’s a 
challenge worth, you will deep learn the undelying technologies.

Davor

From: users [mailto:users-boun...@kannel.org<mailto:users-boun...@kannel.org>] 
On Behalf Of Ron T
Sent: Wednesday, April 11, 2018 12:13 AM
To: users@kannel.org<mailto:users@kannel.org>
Subject: using kannel for sms/mms to and from computer to cell phone


Question. I'm trying to send and receive sms and mms messages to and from my 
computer by going through my android phone.

The phone would not be tethered to my computer. I know there are a few apps out 
there like mighty text that will allow a person to do this but I would like to 
create my own. I've read a little about smpp and smsc but am not sure if I need 
a server such as kannel if I'm only going to be sending and receiving from my 
own pc though my cell phone? I would also like to have my phone number be used 
on the send of sms/mms so the receiver will recognize who it is coming from. 
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!

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




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 im

RE: using kannel for sms/mms to and from computer to cell phone

2018-04-11 Thread Davor Spasoski

You can use kannel to send/receive SMS with your phone but first you have to 
make your phone work as a modem on a Linux box, then configure kannel to use 
that device (AT SMSC section).
To send MMS, you will need something else in addition to kannel. Mbuni could be 
used for that, but I see no activity about this project very long time, so you 
might have a problem compiling it on a modern Linux distribution.
The way kannel works with mbuni: when mms is to be received, your device will 
receive MMS formatted WAP push SMS having a URL where to grab the MMS from. 
This SMS is passed to mbuni and mbuni fetches the content. Then it’s up to you 
to process that.

It’s a long way and it will take plenty of time. If you have it, it’s a 
challenge worth, you will deep learn the undelying technologies.

Davor

From: users [mailto:users-boun...@kannel.org] On Behalf Of Ron T
Sent: Wednesday, April 11, 2018 12:13 AM
To: users@kannel.org
Subject: using kannel for sms/mms to and from computer to cell phone


Question. I'm trying to send and receive sms and mms messages to and from my 
computer by going through my android phone.

The phone would not be tethered to my computer. I know there are a few apps out 
there like mighty text that will allow a person to do this but I would like to 
create my own. I've read a little about smpp and smsc but am not sure if I need 
a server such as kannel if I'm only going to be sending and receiving from my 
own pc though my cell phone? I would also like to have my phone number be used 
on the send of sms/mms so the receiver will recognize who it is coming from. 
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: Inverted Exclamation mark and question mark issue.

2018-04-06 Thread Davor Spasoski





Do you mean you get “@“ for any of the "¤¡ÄÖÑÜ§¿äöñüà" or just for “¡” ?


If so, the SMPP part of the SMSC does some strange character conversions. From my experience, the SMSC usually sets some sort of ISO-8859-1 as a default alphabet on SMPP level and than
 converts (with losses) to GSM alphabet. GSM 7-bit is usually supported with DCS above 240 so try setting alt-dcs =1, coding = 0 and charset left blank (utf-8). 
Lately, some SMSCs support UTF-8 as default and even something called "Esaped-Latin-1" or "X-ISO-8859-GSM-escaped" for which I could not find any standardization, but that is basically
 an 8-bit alphabet, having the common GSM/ASCII characters plus the extension with the GSM only characters. In order to support that, you will need a custom charset translation on your side. 
Try the alt-dcs with coding=0 and if not successful, ask to set the default SMSC/SMPP alphabet as GSM. 


BR,
Davor




On Apr 5, 2018, at 4:56 AM, Wan Md Arif Noor Bin. Wan Nizam  wrote:






Hi All,
 
Thanks for the response, I have removed alt-charset from the config but now all I get is @.
 
curl

http://localhost:13017/cgi-bin/sendsms?username=smsSMPP2=smsPass=6=601132495424=%C2%A1=0
curl

http://localhost:13017/cgi-bin/sendsms?username=smsSMPP2=smsPass=6=601132495424=%C2%A1=UTF-8
curl

http://localhost:13017/cgi-bin/sendsms?username=smsSMPP2=smsPass=6=601132495424=%A1=ISO-8859-1
 
2018-04-05 10:21:02 [16025] [7] DEBUG: SMPP PDU 0x7f69dc000a10 dump:
2018-04-05 10:21:02 [16025] [7] DEBUG:   type_name: submit_sm
2018-04-05 10:21:02 [16025] [7] DEBUG:   command_id: 4 = 0x0004
2018-04-05 10:21:02 [16025] [7] DEBUG:   command_status: 0 = 0x
2018-04-05 10:21:02 [16025] [7] DEBUG:   sequence_number: 31 = 0x001f
2018-04-05 10:21:02 [16025] [7] DEBUG:   service_type: NULL
2018-04-05 10:21:02 [16025] [7] DEBUG:   source_addr_ton: 0 = 0x
2018-04-05 10:21:02 [16025] [7] DEBUG:   source_addr_npi: 1 = 0x0001
2018-04-05 10:21:02 [16025] [7] DEBUG:   source_addr: "6"
2018-04-05 10:21:02 [16025] [7] DEBUG:   dest_addr_ton: 1 = 0x0001
2018-04-05 10:21:02 [16025] [7] DEBUG:   dest_addr_npi: 1 = 0x0001
2018-04-05 10:21:02 [16025] [7] DEBUG:   destination_addr: "601132495424"
2018-04-05 10:21:02 [16025] [7] DEBUG:   esm_class: 3 = 0x0003
2018-04-05 10:21:02 [16025] [7] DEBUG:   protocol_id: 0 = 0x
2018-04-05 10:21:02 [16025] [7] DEBUG:   priority_flag: 0 = 0x
2018-04-05 10:21:02 [16025] [7] DEBUG:   schedule_delivery_time: NULL
2018-04-05 10:21:02 [16025] [7] DEBUG:   validity_period: NULL
2018-04-05 10:21:02 [16025] [7] DEBUG:   registered_delivery: 0 = 0x
2018-04-05 10:21:02 [16025] [7] DEBUG:   replace_if_present_flag: 0 = 0x
2018-04-05 10:21:02 [16025] [7] DEBUG:   data_coding: 0 = 0x
2018-04-05 10:21:02 [16025] [7] DEBUG:   sm_default_msg_id: 0 = 0x
2018-04-05 10:21:02 [16025] [7] DEBUG:   sm_length: 1 = 0x0001
2018-04-05 10:21:02 [16025] [7] DEBUG:   short_message: "@"
2018-04-05 10:21:02 [16025] [7] DEBUG: SMPP PDU dump ends.
 
Tested all the character of GSM only @£$¥èéùìòÇØøÅåΔ_ΦΓΛΩΠΨΣΘΞ^{}\[~]|€ÆæßÉ!\"#%&'()*+,-./:;<=>? Is working while the ¤¡ÄÖÑÜ§¿äöñüà is not regardless of charset
 used in the parameter.
 
¤¡ÄÖÑÜ§¿äöñüà
 
curl

http://localhost:13017/cgi-bin/sendsms?username=smsSMPP2=smsPass=6=601132495424=%C2%A4%C2%A1%C3%84%C3%96%C3%91%C3%9C%C2%A7%C2%BF%C3%A4%C3%B6%C3%B1%C3%BC%C3%A0
 
2018-04-05 10:54:07 [16129] [7] DEBUG: SMPP PDU 0x7f09c8000a10 dump:
2018-04-05 10:54:07 [16129] [7] DEBUG:   type_name: submit_sm
2018-04-05 10:54:07 [16129] [7] DEBUG:   command_id: 4 = 0x0004
2018-04-05 10:54:07 [16129] [7] DEBUG:   command_status: 0 = 0x
2018-04-05 10:54:07 [16129] [7] DEBUG:   sequence_number: 56 = 0x0038
2018-04-05 10:54:07 [16129] [7] DEBUG:   service_type: NULL
2018-04-05 10:54:07 [16129] [7] DEBUG:   source_addr_ton: 0 = 0x
2018-04-05 10:54:07 [16129] [7] DEBUG:   source_addr_npi: 1 = 0x0001
2018-04-05 10:54:07 [16129] [7] DEBUG:   source_addr: "6"
2018-04-05 10:54:07 [16129] [7] DEBUG:   dest_addr_ton: 1 = 0x0001
2018-04-05 10:54:07 [16129] [7] DEBUG:   dest_addr_npi: 1 = 0x0001
2018-04-05 10:54:07 [16129] [7] DEBUG:   destination_addr: "601132495424"
2018-04-05 10:54:07 [16129] [7] DEBUG:   esm_class: 3 = 0x0003
2018-04-05 10:54:07 [16129] [7] DEBUG:   protocol_id: 0 = 0x
2018-04-05 10:54:07 [16129] [7] DEBUG:   priority_flag: 0 = 0x
2018-04-05 10:54:07 [16129] [7] DEBUG:   schedule_delivery_time: NULL
2018-04-05 10:54:07 [16129] [7] DEBUG:   validity_period: NULL
2018-04-05 10:54:07 [16129] [7] DEBUG:   registered_delivery: 0 = 0x
2018-04-05 10:54:07 [16129] [7] DEBUG:   replace_if_present_flag: 0 = 0x
2018-04-05 10:54:07 [16129] [7] DEBUG:   data_coding: 0 = 0x
2018-04-05 10:54:07 [16129] [7]

Re: Inverted Exclamation mark and question mark issue.

2018-04-06 Thread Davor Spasoski




Do you mean you get “@“ for any of the "¤¡ÄÖÑÜ§¿äöñüà" or just for “¡” ?


If so, the SMPP part of the SMSC does some strange character conversions. From my experience, the SMSC usually sets some sort of ISO-8859-1 as a default alphabet on SMPP level and than
 converts (with losses) to GSM alphabet. GSM 7-bit is usually supported with DCS above 240 so try setting alt-dcs =1, coding = 0 and charset left blank (utf-8). 
Lately, some SMSCs support UTF-8 as default and even something called "Esaped-Latin-1" or "X-ISO-8859-GSM-escaped" for which I could not find any standardization, but that is basically
 an 8-bit alphabet, having the common GSM/ASCII characters plus the extension with the GSM only characters. In order to support that, you will need a custom charset translation on your side. 
Try the alt-dcs with coding=0 and if not successful, ask to set the default SMSC/SMPP alphabet as GSM. 


BR,
Davor




On Apr 5, 2018, at 4:56 AM, Wan Md Arif Noor Bin. Wan Nizam  wrote:






Hi All,
 
Thanks for the response, I have removed alt-charset from the config but now all I get is @.
 
curl

http://localhost:13017/cgi-bin/sendsms?username=smsSMPP2=smsPass=6=601132495424=%C2%A1=0
curl

http://localhost:13017/cgi-bin/sendsms?username=smsSMPP2=smsPass=6=601132495424=%C2%A1=UTF-8
curl

http://localhost:13017/cgi-bin/sendsms?username=smsSMPP2=smsPass=6=601132495424=%A1=ISO-8859-1
 
2018-04-05 10:21:02 [16025] [7] DEBUG: SMPP PDU 0x7f69dc000a10 dump:
2018-04-05 10:21:02 [16025] [7] DEBUG:   type_name: submit_sm
2018-04-05 10:21:02 [16025] [7] DEBUG:   command_id: 4 = 0x0004
2018-04-05 10:21:02 [16025] [7] DEBUG:   command_status: 0 = 0x
2018-04-05 10:21:02 [16025] [7] DEBUG:   sequence_number: 31 = 0x001f
2018-04-05 10:21:02 [16025] [7] DEBUG:   service_type: NULL
2018-04-05 10:21:02 [16025] [7] DEBUG:   source_addr_ton: 0 = 0x
2018-04-05 10:21:02 [16025] [7] DEBUG:   source_addr_npi: 1 = 0x0001
2018-04-05 10:21:02 [16025] [7] DEBUG:   source_addr: "6"
2018-04-05 10:21:02 [16025] [7] DEBUG:   dest_addr_ton: 1 = 0x0001
2018-04-05 10:21:02 [16025] [7] DEBUG:   dest_addr_npi: 1 = 0x0001
2018-04-05 10:21:02 [16025] [7] DEBUG:   destination_addr: "601132495424"
2018-04-05 10:21:02 [16025] [7] DEBUG:   esm_class: 3 = 0x0003
2018-04-05 10:21:02 [16025] [7] DEBUG:   protocol_id: 0 = 0x
2018-04-05 10:21:02 [16025] [7] DEBUG:   priority_flag: 0 = 0x
2018-04-05 10:21:02 [16025] [7] DEBUG:   schedule_delivery_time: NULL
2018-04-05 10:21:02 [16025] [7] DEBUG:   validity_period: NULL
2018-04-05 10:21:02 [16025] [7] DEBUG:   registered_delivery: 0 = 0x
2018-04-05 10:21:02 [16025] [7] DEBUG:   replace_if_present_flag: 0 = 0x
2018-04-05 10:21:02 [16025] [7] DEBUG:   data_coding: 0 = 0x
2018-04-05 10:21:02 [16025] [7] DEBUG:   sm_default_msg_id: 0 = 0x
2018-04-05 10:21:02 [16025] [7] DEBUG:   sm_length: 1 = 0x0001
2018-04-05 10:21:02 [16025] [7] DEBUG:   short_message: "@"
2018-04-05 10:21:02 [16025] [7] DEBUG: SMPP PDU dump ends.
 
Tested all the character of GSM only @£$¥èéùìòÇØøÅåΔ_ΦΓΛΩΠΨΣΘΞ^{}\[~]|€ÆæßÉ!\"#%&'()*+,-./:;<=>? Is working while the ¤¡ÄÖÑÜ§¿äöñüà is not regardless of charset
 used in the parameter.
 
¤¡ÄÖÑÜ§¿äöñüà
 
curl

http://localhost:13017/cgi-bin/sendsms?username=smsSMPP2=smsPass=6=601132495424=%C2%A4%C2%A1%C3%84%C3%96%C3%91%C3%9C%C2%A7%C2%BF%C3%A4%C3%B6%C3%B1%C3%BC%C3%A0
 
2018-04-05 10:54:07 [16129] [7] DEBUG: SMPP PDU 0x7f09c8000a10 dump:
2018-04-05 10:54:07 [16129] [7] DEBUG:   type_name: submit_sm
2018-04-05 10:54:07 [16129] [7] DEBUG:   command_id: 4 = 0x0004
2018-04-05 10:54:07 [16129] [7] DEBUG:   command_status: 0 = 0x
2018-04-05 10:54:07 [16129] [7] DEBUG:   sequence_number: 56 = 0x0038
2018-04-05 10:54:07 [16129] [7] DEBUG:   service_type: NULL
2018-04-05 10:54:07 [16129] [7] DEBUG:   source_addr_ton: 0 = 0x
2018-04-05 10:54:07 [16129] [7] DEBUG:   source_addr_npi: 1 = 0x0001
2018-04-05 10:54:07 [16129] [7] DEBUG:   source_addr: "6"
2018-04-05 10:54:07 [16129] [7] DEBUG:   dest_addr_ton: 1 = 0x0001
2018-04-05 10:54:07 [16129] [7] DEBUG:   dest_addr_npi: 1 = 0x0001
2018-04-05 10:54:07 [16129] [7] DEBUG:   destination_addr: "601132495424"
2018-04-05 10:54:07 [16129] [7] DEBUG:   esm_class: 3 = 0x0003
2018-04-05 10:54:07 [16129] [7] DEBUG:   protocol_id: 0 = 0x
2018-04-05 10:54:07 [16129] [7] DEBUG:   priority_flag: 0 = 0x
2018-04-05 10:54:07 [16129] [7] DEBUG:   schedule_delivery_time: NULL
2018-04-05 10:54:07 [16129] [7] DEBUG:   validity_period: NULL
2018-04-05 10:54:07 [16129] [7] DEBUG:   registered_delivery: 0 = 0x
2018-04-05 10:54:07 [16129] [7] DEBUG:   replace_if_present_flag: 0 = 0x
2018-04-05 10:54:07 [16129] [7] DEBUG:   data_coding: 0 = 0x
2018-04-05 10:54:07 [16129] [7]

Re: Inverted Exclamation mark and question mark issue.

2018-04-04 Thread Davor Spasoski





What is your smsc’s default alphabet? If not GSM 7 bit, you have to allign that in kannel.

On Apr 4, 2018, at 11:25 AM, Wan Md Arif Noor Bin. Wan Nizam  wrote:







Hi There,
 
Thanks for replying, I already tested using that parameter, but I keep receiving “B?”.
Below are the debug log.
 
curl "http://localhost:13017/cgi-bin/sendsms?username=smsSMPP2=smsPass=6=601132495424=%C2%A1=0=UTF-8"
 
2018-04-04 17:17:39 [10745] [7] DEBUG: SMPP PDU 0x7efe78000a10 dump:
2018-04-04 17:17:39 [10745] [7] DEBUG:   type_name: submit_sm
2018-04-04 17:17:39 [10745] [7] DEBUG:   command_id: 4 = 0x0004
2018-04-04 17:17:39 [10745] [7] DEBUG:   command_status: 0 = 0x
2018-04-04 17:17:39 [10745] [7] DEBUG:   sequence_number: 56414 = 0xdc5e
2018-04-04 17:17:39 [10745] [7] DEBUG:   service_type: NULL
2018-04-04 17:17:39 [10745] [7] DEBUG:   source_addr_ton: 0 = 0x
2018-04-04 17:17:39 [10745] [7] DEBUG:   source_addr_npi: 1 = 0x0001
2018-04-04 17:17:39 [10745] [7] DEBUG:   source_addr: "6"
2018-04-04 17:17:39 [10745] [7] DEBUG:   dest_addr_ton: 1 = 0x0001
2018-04-04 17:17:39 [10745] [7] DEBUG:   dest_addr_npi: 1 = 0x0001
2018-04-04 17:17:39 [10745] [7] DEBUG:   destination_addr: "601132495424"
2018-04-04 17:17:39 [10745] [7] DEBUG:   esm_class: 3 = 0x0003
2018-04-04 17:17:39 [10745] [7] DEBUG:   protocol_id: 0 = 0x
2018-04-04 17:17:39 [10745] [7] DEBUG:   priority_flag: 0 = 0x
2018-04-04 17:17:39 [10745] [7] DEBUG:   schedule_delivery_time: NULL
2018-04-04 17:17:39 [10745] [7] DEBUG:   validity_period: NULL
2018-04-04 17:17:39 [10745] [7] DEBUG:   registered_delivery: 0 = 0x
2018-04-04 17:17:39 [10745] [7] DEBUG:   replace_if_present_flag: 0 = 0x
2018-04-04 17:17:39 [10745] [7] DEBUG:   data_coding: 0 = 0x
2018-04-04 17:17:39 [10745] [7] DEBUG:   sm_default_msg_id: 0 = 0x
2018-04-04 17:17:39 [10745] [7] DEBUG:   sm_length: 2 = 0x0002
2018-04-04 17:17:39 [10745] [7] DEBUG:   short_message:
2018-04-04 17:17:39 [10745] [7] DEBUG:    Octet string at 0x7efe78000c40:
2018-04-04 17:17:39 [10745] [7] DEBUG:  len:  2
2018-04-04 17:17:39 [10745] [7] DEBUG:  size: 3
2018-04-04 17:17:39 [10745] [7] DEBUG:  immutable: 0
2018-04-04 17:17:39 [10745] [7] DEBUG:  data: c2 a1 ..
2018-04-04 17:17:39 [10745] [7] DEBUG:    Octet string dump ends.
2018-04-04 17:17:39 [10745] [7] DEBUG: SMPP PDU dump ends.
 
However it works correctly when sending with coding=2, but by using that it halved the SMS length.  Appreciate your help in this.
 
Cheers,
Arif Noor
 


From: Alexander Malysh 
On Behalf Of amal...@kannel.org
Sent: Wednesday, April 04, 2018 4:40 PM
To: Wan Md Arif Noor Bin. Wan Nizam 
Cc: users@kannel.org
Subject: Re: Inverted Exclamation mark and question mark issue.


 
Hi,

 


you have to send in UTF-8 with coding=0 (for inverted exclamation mark: text=%C2%A1=0).


If it doesn’t work please check your smpp debug logs and check if submit_sm has correct values in message body


and if yes then SMSC doing something wrong.


 


Thanks,


Alex


 






Am 04.04.2018 um 07:27 schrieb Wan Md Arif Noor Bin. Wan Nizam :

 





Hello Users,


 


I’m having an issue with sending both inverted exclamation mark (¡) and
 inverted question mark (¿) , it seems like it was converted to B! and B? instead.


 


Tried with all below parameter but none working except for UCS-2 which I want to avoid.


 


curl "http://localhost:13017/cgi-bin/sendsms?username=smsSMPP2=smsPass=6=60113**=¿"
  Result : B?


curl "http://localhost:13017/cgi-bin/sendsms?username=smsSMPP2=smsPass=6=60113**=%C2%BF" Result
 :B?


curl "http://localhost:13017/cgi-bin/sendsms?username=smsSMPP2=smsPass=6=60113**=¿=0=1" Result
 : ‘


curl "http://localhost:13017/cgi-bin/sendsms?username=smsSMPP2=smsPass=6=60113**=%C2%BF=0=1" Result
 : ‘


curl "http://localhost:13017/cgi-bin/sendsms?username=smsSMPP2=smsPass=6=60113**=¿=0=0" Result
 : B?


curl "http://localhost:13017/cgi-bin/sendsms?username=smsSMPP2=smsPass=6=60113**=%C2%BF=0=0" Result
 : B?


curl "http://localhost:13017/cgi-bin/sendsms?username=smsSMPP2=smsPass=6=60113**=¿=0=ISO-8859-1=1"Result
 : ?’


curl "http://localhost:13017/cgi-bin/sendsms?username=smsSMPP2=smsPass=6=60113**=¿=0=ISO-8859-1=1"Result
 : ?’


 


Tried with charset UTF-8 and ASCII, but same with same result. Please advise what else can be done to get this working?


 


Config:


 


group = core


admin-port = 13005


smsbox-port = 13007


sms-resend-retry = 10


admin-password = admin


box-deny-ip = "*.*.*.*"


box-allow-ip = ""

RE: PHP Code to Send SMS using Kannel without CURL

2018-02-25 Thread Davor Spasoski

Maybe you can get by using the header() function in php.

Davor Spasoski
From: users [mailto:users-boun...@kannel.org] On Behalf Of Web Services
Sent: Friday, February 23, 2018 2:19 PM
To: Sumit Kshatriya <sumitkshatr...@gmail.com>
Cc: kannel users@kannel.org <users@kannel.org>
Subject: Re: PHP Code to Send SMS using Kannel without CURL

Use sqlbox

On Feb 23, 2018 6:07 PM, "Sumit Kshatriya" 
<sumitkshatr...@gmail.com<mailto:sumitkshatr...@gmail.com>> wrote:
Dear Team,

I have successfully installed Kannel and tested sms using SSH which is working 
fine.

Could you please guide me how to send SMS using Kannel without HTTP CURL and 
get_file_contents functions.

Looking forward to your kind reply. Many Thanks
--
[http://www.sybexinfotech.com/images/signature-logo.jpg]

Sumit Kshatriya
Sybex Infotech
P. 9225 122 122
M. 9028 229 229
W. www.sybexinfotech.com<http://www.sybexinfotech.com>,   E. 
su...@sybexinfotech.com<mailto:su...@sybexinfotech.com>

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: Wrong DLR ID.

2017-08-16 Thread Davor Spasoski

Check your ID numbering bases for submit_sm and deliver_sm. Looks like you are 
not using the same base for submit and deliver.

3188534916 = 83101780110

Msg-id-type is the parameter you should be looking at

Davor Spasoski

From: users [mailto:users-boun...@kannel.org] On Behalf Of Wan Md Arif Noor 
Bin. Wan Nizam
Sent: Wednesday, August 16, 2017 11:40 AM
To: users@kannel.org
Subject: Wrong DLR ID.

Hi Users,

I found weird thing with kannel today, where when submit an MT it was tagged 
with different ID but when I checked inside debug log, the ID was correct. This 
causing "got DLR but could not find message or was not interested in it 
id<31943697>" error. I don't know where this  831017801 come from. Appreciate 
your help on this.

Kannel bearerbox version `svn-r5186M'.

Logs :

2017-08-16 17:11:28 [SMSC:6SeriesConn13] [from:*] [to:**] 
[msg:82:RM0: To unsubscribe, send OUT 69111..Tel] [FID:831017801] 
[State:?smpp_resp?]
2017-08-16 17:11:32 [SMSC:6SeriesConn13] [from:+**] [to:*] [msg:0:] 
[FID:31885349] [State:?smpp?Message+State=2&]

1687656:2017-08-16 17:11:28 [3552] [22] DEBUG:   type_name: submit_sm
1687657:2017-08-16 17:11:28 [3552] [22] DEBUG:   command_id: 4 = 0x0004
1687658:2017-08-16 17:11:28 [3552] [22] DEBUG:   command_status: 0 = 0x
1687659:2017-08-16 17:11:28 [3552] [22] DEBUG:   sequence_number: 619 = 
0x026b
1687660:2017-08-16 17:11:28 [3552] [22] DEBUG:   service_type: NULL
1687661:2017-08-16 17:11:28 [3552] [22] DEBUG:   source_addr_ton: 0 = 0x
1687662:2017-08-16 17:11:28 [3552] [22] DEBUG:   source_addr_npi: 1 = 0x0001
1687663:2017-08-16 17:11:28 [3552] [22] DEBUG:   source_addr: "*"
1687664:2017-08-16 17:11:28 [3552] [22] DEBUG:   dest_addr_ton: 1 = 0x0001
1687665:2017-08-16 17:11:28 [3552] [22] DEBUG:   dest_addr_npi: 1 = 0x0001
1687666:2017-08-16 17:11:28 [3552] [22] DEBUG:   destination_addr: "***"
1687667:2017-08-16 17:11:28 [3552] [22] DEBUG:   esm_class: 0 = 0x
1687668:2017-08-16 17:11:28 [3552] [22] DEBUG:   protocol_id: 0 = 0x
1687669:2017-08-16 17:11:28 [3552] [22] DEBUG:   priority_flag: 0 = 0x
1687670:2017-08-16 17:11:28 [3552] [22] DEBUG:   schedule_delivery_time: NULL
1687671:2017-08-16 17:11:28 [3552] [22] DEBUG:   validity_period: NULL
1687672:2017-08-16 17:11:28 [3552] [22] DEBUG:   registered_delivery: 1 = 
0x0001
1687673:2017-08-16 17:11:28 [3552] [22] DEBUG:   replace_if_present_flag: 0 = 
0x
1687674:2017-08-16 17:11:28 [3552] [22] DEBUG:   data_coding: 0 = 0x
1687675:2017-08-16 17:11:28 [3552] [22] DEBUG:   sm_default_msg_id: 0 = 
0x
1687676:2017-08-16 17:11:28 [3552] [22] DEBUG:   sm_length: 82 = 0x0052
1687677:2017-08-16 17:11:28 [3552] [22] DEBUG:   short_message:
1687678:2017-08-16 17:11:28 [3552] [22] DEBUG:Octet string at 
0x7f32c4000b30:
1687679:2017-08-16 17:11:28 [3552] [22] DEBUG:  len:  82
1687680:2017-08-16 17:11:28 [3552] [22] DEBUG:  size: 83
1687681:2017-08-16 17:11:28 [3552] [22] DEBUG:  immutable: 0
1687682:2017-08-16 17:11:28 [3552] [22] DEBUG:  data: 52 4d 30 3a 20 54 6f 
20 75 6e 73 75 62 73 63 72   RM0: To unsubscr
1687683:2017-08-16 17:11:28 [3552] [22] DEBUG:  data: 69 62 65 2c 20 73 65 
6e 64 20 4f 55 54 20 36 39   ibe, send OUT 69
1687684:2017-08-16 17:11:28 [3552] [22] DEBUG:  data: 31 31 31 2e 0a 54 65 
6c 3a 20 36 30 33 38 36 30   111..Tel: 603860
1687685:2017-08-16 17:11:28 [3552] [22] DEBUG:  data: 31 30 31 30 37 2c 49 
6e 6x 6x 6x 6x 7x 2x 4x 7x   10107
1687686:2017-08-16 17:11:28 [3552] [22] DEBUG:  data: 69 61 20 50 61 63 69 
66 69 63 20 53 64 6e 20 42   
1687687:2017-08-16 17:11:28 [3552] [22] DEBUG:  data: 68 64
1687688:2017-08-16 17:11:28 [3552] [22] DEBUG:Octet string dump ends.
1687689:2017-08-16 17:11:28 [3552] [22] DEBUG: SMPP PDU dump ends.
1687692:2017-08-16 17:11:28 [3552] [22] DEBUG: SMPP[6SeriesConn13]: Got PDU:
1687693:2017-08-16 17:11:28 [3552] [22] DEBUG: SMPP PDU 0x7f32c4001e40 dump:
1687694:2017-08-16 17:11:28 [3552] [22] DEBUG:   type_name: submit_sm_resp
1687695:2017-08-16 17:11:28 [3552] [22] DEBUG:   command_id: 2147483652 = 
0x8004
1687696:2017-08-16 17:11:28 [3552] [22] DEBUG:   command_status: 0 = 0x
1687697:2017-08-16 17:11:28 [3552] [22] DEBUG:   sequence_number: 619 = 
0x026b
1687698:2017-08-16 17:11:28 [3552] [22] DEBUG:   message_id: "31885349"
1687699:2017-08-16 17:11:28 [3552] [22] DEBUG: SMPP PDU dump ends.


1687802:2017-08-16 17:11:32 [3552] [22] DEBUG: SMPP PDU 0x7f32c4006850 dump:
1687803:2017-08-16 17:11:32 [3552] [22] DEBUG:   type_name: deliver_sm
1687804:2017-08-16 17:11:32 [3552] [22] DEBUG:   command_id: 5 = 0x0005
1687805:2017-08-16 17:11:32 [3552] [22] DEBUG:   command_status: 0 = 0x
1687806:2017-08-16 17:11:32 [3552] [22] DEBUG:   sequence_number: 31885417 = 
0x01e68869
1687807:2017-08-16 17:11:32 [3552] [22] DEBUG:   service_type:

Re: Routing to multiple SMSCs OPENSMPP

2017-07-29 Thread Davor Spasoski




Hi Gorki,


As they say, there are many ways of skinning a cat. That's the beauty of this craft. Use whatever suits you best or makes a logic.


Thanks,
Davor

Sent from my iPad

On Jul 29, 2017, at 4:33 AM, Gorki Alfaro <gork...@gmail.com> wrote:




Davor


Thanks a lot, it was really helpful. Also I would like to share another solution that I found, and is using to SMSC with the same name, Here you have the config files  ---excerpt




opensmppbox.conf

group = core
dlr-storage = mysql
group = opensmppbox
opensmppbox-id =mysmppbox
log-level = 0
log-file = /var/log/kannel/opensmppbox.log
our-system-id = testsmpp
use-systemid-as-smsboxid = true
route-to-smsc = smppgwgeneric
# see sample smpplogins.txt
smpp-logins = "/etc/kannel/smpplogins.txt"



kannel.conf

#-
# CORE..


#-
# SMSC CONNECTIONS


#SMSC 1
group = smsc
smsc-id = smppgwgeneric
smsc = smpp
host =x.x.x.x
port = 5019
smsc-username = xxx
smsc-password = xx

allowed-prefix = "5019;+5019"
preferred-prefix = "5019;+5019"
allowed-smsc-id = smppgwgeneric
msg-id-type = 0x01


#SMSC 2
group = smsc
smsc-username = xxx
smsc-password = xx
smsc-id = smppgwgeneric
smsc = smpp
host = X.X.X.X
port = 4201

allowed-prefix = "5013;+5013;5018;+5018"
preferred-prefix = "5013;+5013;5018;+5018"
allowed-smsc-id = smppgwgeneric
msg-id-type = 0x01



Hope could be helpful for someone else.


Regards,
Gorki





2017-07-27 9:46 GMT-06:00 Davor Spasoski 
<davor.spaso...@onevip.mk>:



Follow-up configuration:
 
group = smsc
smsc = smpp
smsc-id = "SMSC1"
allowed-smsc-id = "SMSC1;SMSC2"
allowed-receiver-prefix = prefix1,prefix3
 
group = smsc
smsc = smpp
smsc-id = "SMSC2"
allowed-smsc-id = "SMSC1;SMSC2"
allowed-receiver-prefix = prefix2,prefix3
 
………
 
Opensmppbox
group = smsc-route
smsc-id = SMSC1
smsbox-id = SMSC1
 
With the above, kannel will load-share between SMSC12 and SMSC2 for prefix3 and will use SMSC1-only for prefix1 and SMSC2-only for prefix2. If you on top of this
 want to have a preferred SMSC for prefix3 instead of load sharing, just add preferred-smsc-id = SMSC1 in the SMSC1 configuration.
 
Good luck!
 

Davor Spasoski

 


From: users [mailto:users-bounces@kannel.org]
On Behalf Of Davor Spasoski
Sent: Wednesday, July 26, 2017 10:35 PM
To: Gorki Alfaro <gork...@gmail.com>
Cc: users@kannel.org
Subject: Re: Routing to multiple SMSCs OPENSMPP




 

The smscs do not necessarily have to have same-ids. Same smsc-ids are used when you want to load balance the traffic among two or more smscs.


Use two id. It is important that smsc1 should allow smsc2 and vice versa. I can't be much verbose now, as I'm writing from my handy. I'll have access to a computer tomorrow afternoon. Until then, read the userguide and experiment.


 


Davor



On Jul 26, 2017, at 6:24 PM, Gorki Alfaro <gork...@gmail.com> wrote:




Hi Davor, thanks for your help. 


 


I understand that in the opensmppbox config I have to set the variable route-to-smsc to a specific smsc-id and then in the kannel configuration file set two o more  group = smsc with the
 same id  (here use the variables allowed-smsc-id and allowed-prefix)   ? 


Can you provide an example?


 


 


Thanks in advance


Gorki

 


 


 


2017-07-26 1:35 GMT-06:00 Davor Spasoski <davor.spaso...@onevip.mk>:



Hi,
 
Try using the allowed-smsc-id and allowed-prefix of the SMSC group set of variables.
 
Davor Spasoski
From: users [mailto:users-bounces@kannel.org]
On Behalf Of Gorki Alfaro
Sent: Wednesday, July 26, 2017 5:47 AM
To: users@kannel.org
Subject: Routing to multiple SMSCs OPENSMPP


 

Hello my friends

 


Does anyone solve this situation?  I have clients connecting to me through SMPP connections who needs to send messages to more than one SMSC however
 OPENSMPP configuration only allows one SMSC (variable route-to-smsc) .


The question is: How can I redirect messages to different SMSC based on the destination number?


 


Thanks in advance


 


Gorki 


 





 




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: Routing to multiple SMSCs OPENSMPP

2017-07-27 Thread Davor Spasoski

Follow-up configuration:

group = smsc
smsc = smpp
smsc-id = "SMSC1"
allowed-smsc-id = "SMSC1;SMSC2"
allowed-receiver-prefix = prefix1,prefix3

group = smsc
smsc = smpp
smsc-id = "SMSC2"
allowed-smsc-id = "SMSC1;SMSC2"
allowed-receiver-prefix = prefix2,prefix3

………

Opensmppbox
group = smsc-route
smsc-id = SMSC1
smsbox-id = SMSC1

With the above, kannel will load-share between SMSC12 and SMSC2 for prefix3 and 
will use SMSC1-only for prefix1 and SMSC2-only for prefix2. If you on top of 
this want to have a preferred SMSC for prefix3 instead of load sharing, just 
add preferred-smsc-id = SMSC1 in the SMSC1 configuration.

Good luck!

Davor Spasoski

From: users [mailto:users-boun...@kannel.org] On Behalf Of Davor Spasoski
Sent: Wednesday, July 26, 2017 10:35 PM
To: Gorki Alfaro <gork...@gmail.com>
Cc: users@kannel.org
Subject: Re: Routing to multiple SMSCs OPENSMPP

The smscs do not necessarily have to have same-ids. Same smsc-ids are used when 
you want to load balance the traffic among two or more smscs.
Use two id. It is important that smsc1 should allow smsc2 and vice versa. I 
can't be much verbose now, as I'm writing from my handy. I'll have access to a 
computer tomorrow afternoon. Until then, read the userguide and experiment.

Davor

On Jul 26, 2017, at 6:24 PM, Gorki Alfaro 
<gork...@gmail.com<mailto:gork...@gmail.com>> wrote:
Hi Davor, thanks for your help.

I understand that in the opensmppbox config I have to set the variable 
route-to-smsc to a specific smsc-id and then in the kannel configuration file 
set two o more  group = smsc with the same id  (here use the variables 
allowed-smsc-id and allowed-prefix)   ?
Can you provide an example?


Thanks in advance
Gorki



2017-07-26 1:35 GMT-06:00 Davor Spasoski 
<davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>:
Hi,

Try using the allowed-smsc-id and allowed-prefix of the SMSC group set of 
variables.

Davor Spasoski
From: users [mailto:users-boun...@kannel.org<mailto:users-boun...@kannel.org>] 
On Behalf Of Gorki Alfaro
Sent: Wednesday, July 26, 2017 5:47 AM
To: users@kannel.org<mailto:users@kannel.org>
Subject: Routing to multiple SMSCs OPENSMPP

Hello my friends

Does anyone solve this situation?  I have clients connecting to me through SMPP 
connections who needs to send messages to more than one SMSC however OPENSMPP 
configuration only allows one SMSC (variable route-to-smsc) .
The question is: How can I redirect messages to different SMSC based on the 
destination number?

Thanks in advance

Gorki




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!

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




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 dama

Re: Routing to multiple SMSCs OPENSMPP

2017-07-26 Thread Davor Spasoski





The smscs do not necessarily have to have same-ids. Same smsc-ids are used when you want to load balance the traffic among two or more smscs.
Use two id. It is important that smsc1 should allow smsc2 and vice versa. I can't be much verbose now, as I'm writing from my handy. I'll have access to a computer tomorrow afternoon. Until then, read the userguide and experiment.


Davor

On Jul 26, 2017, at 6:24 PM, Gorki Alfaro <gork...@gmail.com> wrote:




Hi Davor, thanks for your help. 


I understand that in the opensmppbox config I have to set the variable
route-to-smsc to a specific smsc-id and then in the kannel configuration file set two o more  group = smsc with the same id  (here use the variables allowed-smsc-id and allowed-prefix)  
 ? 
Can you provide an example?




Thanks in advance
Gorki







2017-07-26 1:35 GMT-06:00 Davor Spasoski 
<davor.spaso...@onevip.mk>:



Hi,
 
Try using the allowed-smsc-id and allowed-prefix of the SMSC group set of variables.
 
Davor Spasoski
From: users [mailto:users-bounces@kannel.org]
On Behalf Of Gorki Alfaro
Sent: Wednesday, July 26, 2017 5:47 AM
To: users@kannel.org
Subject: Routing to multiple SMSCs OPENSMPP


 

Hello my friends

 


Does anyone solve this situation?  I have clients connecting to me through SMPP connections who needs to send messages to more than one SMSC however
 OPENSMPP configuration only allows one SMSC (variable route-to-smsc) .


The question is: How can I redirect messages to different SMSC based on the destination number?


 


Thanks in advance


 


Gorki 


 








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!

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














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: Routing to multiple SMSCs OPENSMPP

2017-07-26 Thread Davor Spasoski

Hi,

Try using the allowed-smsc-id and allowed-prefix of the SMSC group set of 
variables.

Davor Spasoski
From: users [mailto:users-boun...@kannel.org] On Behalf Of Gorki Alfaro
Sent: Wednesday, July 26, 2017 5:47 AM
To: users@kannel.org
Subject: Routing to multiple SMSCs OPENSMPP

Hello my friends

Does anyone solve this situation?  I have clients connecting to me through SMPP 
connections who needs to send messages to more than one SMSC however OPENSMPP 
configuration only allows one SMSC (variable route-to-smsc) .
The question is: How can I redirect messages to different SMSC based on the 
destination number?

Thanks in advance

Gorki

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: Facing issues while configuring Kannel

2017-07-12 Thread Davor Spasoski

P.S.

Send SMS using:

http://ip_of_server_running_kannel:13131/cgi-bin/sendsms?user=user=password=Aplimedia=96170660611=test

You receive SMS via the service URL from the configuration. You need to develop 
a simple http service that parses HTTP-GET parameters and then use that.

Davor

From: Davor Spasoski
Sent: 12 July 2017 16:31
To: 'Mardo Jeghalian' <m.jeghal...@aplimedia.net>
Cc: users@kannel.org
Subject: RE: Facing issues while configuring Kannel

Hi,

I made a simple configuration (attached) with comments for you. It should get 
you going with no surprises. Actual configuration that fully suits your needs 
could depart from this slightly or wildly and can be quite more complex.

BR,
Davor
From: Mardo Jeghalian [mailto:m.jeghal...@aplimedia.net]
Sent: 12 July 2017 13:55
To: Davor Spasoski <davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>
Cc: users@kannel.org<mailto:users@kannel.org>
Subject: Re: Facing issues while configuring Kannel

Hi Davor,

What i have now is direct smpp connection with the GSM operator , i want to 
learn how to install kannel, bind as transceiver to receive and send messages.

Hope you can help me with this task.

Best Regards,

On Wed, Jul 12, 2017 at 1:32 PM, Davor Spasoski 
<davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>> wrote:
Hi Mardo,

It would help if you explain how you want to use kannel, as sms gateway or smpp 
proxy? (Because you mention crating new SMPPs)
I will help you with the configuration, but I advise you to read the manual in 
order to understand what effect the directives in the configuration mean.

Davor

From: users [mailto:users-boun...@kannel.org<mailto:users-boun...@kannel.org>] 
On Behalf Of Mardo Jeghalian
Sent: 12 July 2017 13:04
To: users@kannel.org<mailto:users@kannel.org>
Subject: Facing issues while configuring Kannel

Dear,
I'm new to Linux, trying to install Kannel on Ubuntu, but i'm facing some 
problems in configuring your service. Kindly may I have a configuration done by 
your behalf for kannel.conf? Our SMSC is on the network with IP 172.16.100.10, 
on port 6000, username is 'nour' and password 'nour'. We don't use modem or 
GSM. Please may you help with this issue? Furthermore, can you assist me in how 
to create new SMPPs and how to send and receive SMS? Thank you in advance...



[http://aplimedia.net/images/joomlart/logo/logo1.png]
 Mardiros Jeghalian

Mobile: +961 <tel:+961%2076%20913%20392> 70 660611
Web: www.aplimedia.net<http://www.aplimedia.net/>
Aplimedia S.A.L. (Off-Shore) | P.O. Box 13-5412, Beirut, Lebanon
Tel:  +961 1 785383<tel:+961%201%20785%20383>



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!

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



--
[http://aplimedia.net/images/joomlart/logo/logo1.png]

Mardiros Jeghalian
Mobile: +961 70 660 611<tel:+961%2070%20660%20611>
Web: www.aplimedia.net<http://www.aplimedia.net/>
Aplimedia S.A.L. (Off-Shore) | P.O. Box 13-5412, Beirut, Lebanon
Tel:  +961 1 785 383<tel:+961%201%20785%20383>



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 immed

RE: Facing issues while configuring Kannel

2017-07-12 Thread Davor Spasoski

Hi,

I made a simple configuration (attached) with comments for you. It should get 
you going with no surprises. Actual configuration that fully suits your needs 
could depart from this slightly or wildly and can be quite more complex.

BR,
Davor
From: Mardo Jeghalian [mailto:m.jeghal...@aplimedia.net]
Sent: 12 July 2017 13:55
To: Davor Spasoski <davor.spaso...@onevip.mk>
Cc: users@kannel.org
Subject: Re: Facing issues while configuring Kannel

Hi Davor,

What i have now is direct smpp connection with the GSM operator , i want to 
learn how to install kannel, bind as transceiver to receive and send messages.

Hope you can help me with this task.

Best Regards,

On Wed, Jul 12, 2017 at 1:32 PM, Davor Spasoski 
<davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>> wrote:
Hi Mardo,

It would help if you explain how you want to use kannel, as sms gateway or smpp 
proxy? (Because you mention crating new SMPPs)
I will help you with the configuration, but I advise you to read the manual in 
order to understand what effect the directives in the configuration mean.

Davor

From: users [mailto:users-boun...@kannel.org<mailto:users-boun...@kannel.org>] 
On Behalf Of Mardo Jeghalian
Sent: 12 July 2017 13:04
To: users@kannel.org<mailto:users@kannel.org>
Subject: Facing issues while configuring Kannel

Dear,
I'm new to Linux, trying to install Kannel on Ubuntu, but i'm facing some 
problems in configuring your service. Kindly may I have a configuration done by 
your behalf for kannel.conf? Our SMSC is on the network with IP 172.16.100.10, 
on port 6000, username is 'nour' and password 'nour'. We don't use modem or 
GSM. Please may you help with this issue? Furthermore, can you assist me in how 
to create new SMPPs and how to send and receive SMS? Thank you in advance...



[http://aplimedia.net/images/joomlart/logo/logo1.png]
 Mardiros Jeghalian

Mobile: +961 <tel:+961%2076%20913%20392> 70 660611
Web: www.aplimedia.net<http://www.aplimedia.net/>
Aplimedia S.A.L. (Off-Shore) | P.O. Box 13-5412, Beirut, Lebanon
Tel:  +961 1 785383<tel:+961%201%20785%20383>



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!

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



--
[http://aplimedia.net/images/joomlart/logo/logo1.png]

Mardiros Jeghalian
Mobile: +961 70 660 611<tel:+961%2070%20660%20611>
Web: www.aplimedia.net<http://www.aplimedia.net/>
Aplimedia S.A.L. (Off-Shore) | P.O. Box 13-5412, Beirut, Lebanon
Tel:  +961 1 785 383<tel:+961%201%20785%20383>



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: Facing issues while configuring Kannel

2017-07-12 Thread Davor Spasoski

?

From: Mardo Jeghalian [mailto:m.jeghal...@aplimedia.net]
Sent: 12 July 2017 13:40
To: Davor Spasoski <davor.spaso...@onevip.mk>
Cc: users@kannel.org; Nour Hatoum <n.hat...@aplimedia.net>
Subject: Re: Facing issues while configuring Kannel

On Wed, Jul 12, 2017 at 1:32 PM, Davor Spasoski 
<davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>> wrote:
Hi Mardo,

It would help if you explain how you want to use kannel, as sms gateway or smpp 
proxy? (Because you mention crating new SMPPs)
I will help you with the configuration, but I advise you to read the manual in 
order to understand what effect the directives in the configuration mean.

Davor

From: users [mailto:users-boun...@kannel.org<mailto:users-boun...@kannel.org>] 
On Behalf Of Mardo Jeghalian
Sent: 12 July 2017 13:04
To: users@kannel.org<mailto:users@kannel.org>
Subject: Facing issues while configuring Kannel

Dear,
I'm new to Linux, trying to install Kannel on Ubuntu, but i'm facing some 
problems in configuring your service. Kindly may I have a configuration done by 
your behalf for kannel.conf? Our SMSC is on the network with IP 172.16.100.10, 
on port 6000, username is 'nour' and password 'nour'. We don't use modem or 
GSM. Please may you help with this issue? Furthermore, can you assist me in how 
to create new SMPPs and how to send and receive SMS? Thank you in advance...

[http://aplimedia.net/images/joomlart/logo/logo1.png]
 Mardiros Jeghalian

Mobile: +961 <tel:+961%2076%20913%20392> 70 660611
Web: www.aplimedia.net<http://www.aplimedia.net/>
Aplimedia S.A.L. (Off-Shore) | P.O. Box 13-5412, Beirut, Lebanon
Tel:  +961 1 785383<tel:+961%201%20785%20383>

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!

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

--
[http://aplimedia.net/images/joomlart/logo/logo1.png]

Mardiros Jeghalian
Mobile: +961 70 660 611<tel:+961%2070%20660%20611>
Web: www.aplimedia.net<http://www.aplimedia.net/>
Aplimedia S.A.L. (Off-Shore) | P.O. Box 13-5412, Beirut, Lebanon
Tel:  +961 1 785 383<tel:+961%201%20785%20383>

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

2017-04-02 Thread 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!

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

Scheding light on "http-request-retry "

2017-03-06 Thread Davor Spasoski

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: Help regarding sending pound '£' symbol through kannel

2017-02-23 Thread Davor Spasoski

P.S.

Best way to check the default SMSC encoding is to send %00 with coding=0  and 
check if you get @ or ¡ on your handset. If you get the ¡, then for sure GSM 
03.38 is not the default SMSC alphabet (as far as the SMPP communication is 
concerned).

BR,

Davor Spasoski
From: Davor Spasoski
Sent: 22 February 2017 15:03
To: 'Manas Mohanty' <mohanty.ran...@gmail.com>; users@kannel.org
Subject: RE: Help regarding sending pound '£' symbol through kannel

Hi,

In my understanding, you could send the @ and £ using GSM 7-bit alphabet only 
if the default SMSC encoding is set to GSM or you have set alt-dcs in kannel 
whics sets DCS=241 and should indicate the SMSC to use the 7-bit GSM alphabet.

But you should also consider this document  
http://www.linkas.it/docs/kannel/Characters,%20Kannel%20&%20MT%20SMS.docx which 
explains that after version 1.4.2 kannel has switched to internal use of utf-8. 
So bascially you should use utf-8 to submit to kannel and kannel will translate 
to GSM alphabet if alt-dces i set to true. This might have evolved with the 
vesrions and I would appreciate if someone sched light to this topic.

I think you should do some tests with various parameters and draw your own 
conclusions, but first check the default smsc alphabet. This is the alphabet 
used for SMPP, it’s usually ASCII and is not the same thing as the default GSM 
alphabet.

Davor Spasoski
From: users [mailto:users-boun...@kannel.org] On Behalf Of Manas Mohanty
Sent: 22 February 2017 14:34
To: users@kannel.org<mailto:users@kannel.org>
Subject: Help regarding sending pound '£' symbol through kannel

Hi,
I am trying to send pound '£' symbol through kannel using charset=utf8=0 
but getting '@£' on the handset.
But when I set coding=2, message properly '£' landed on the handset. But doing 
this I am wasting half of the sms capacity as pound symbol is defined in the 
default 7bit GSM 03.38.
Please suggest how to send the message so that I can manage to send it in 
default 7bit GSM 03.38.
Thanks
Manas






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: Help regarding sending pound '£' symbol through kannel

2017-02-22 Thread Davor Spasoski

Hi,

In my understanding, you could send the @ and £ using GSM 7-bit alphabet only 
if the default SMSC encoding is set to GSM or you have set alt-dcs in kannel 
whics sets DCS=241 and should indicate the SMSC to use the 7-bit GSM alphabet.

But you should also consider this document  
http://www.linkas.it/docs/kannel/Characters,%20Kannel%20&%20MT%20SMS.docx which 
explains that after version 1.4.2 kannel has switched to internal use of utf-8. 
So bascially you should use utf-8 to submit to kannel and kannel will translate 
to GSM alphabet if alt-dces i set to true. This might have evolved with the 
vesrions and I would appreciate if someone sched light to this topic.

I think you should do some tests with various parameters and draw your own 
conclusions, but first check the default smsc alphabet. This is the alphabet 
used for SMPP, it’s usually ASCII and is not the same thing as the default GSM 
alphabet.

Davor Spasoski
From: users [mailto:users-boun...@kannel.org] On Behalf Of Manas Mohanty
Sent: 22 February 2017 14:34
To: users@kannel.org
Subject: Help regarding sending pound '£' symbol through kannel

Hi,
I am trying to send pound '£' symbol through kannel using charset=utf8=0 
but getting '@£' on the handset.
But when I set coding=2, message properly '£' landed on the handset. But doing 
this I am wasting half of the sms capacity as pound symbol is defined in the 
default 7bit GSM 03.38.
Please suggest how to send the message so that I can manage to send it in 
default 7bit GSM 03.38.
Thanks
Manas






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: Re[6]: OpenSMPPBox Panic

2017-02-13 Thread Davor Spasoski

Checked and now opensmppbox does not cause panic on startup, nor on sending 
concatenated SMS.

Thanks

Davor Spasoski
VAS Cloud & ICT Development Team Leader / Online and VAS Development

M: +38975400608
e-mail: davor.spaso...@onevip.mk

one.Vip DOO Skopje | Filip Vtori Makedonski 3, DC Soravia 8th floor | 1000 
Skopje | Macedonia
From: Rene Kluwen [mailto:rene.klu...@chimit.nl]
Sent: 09 February 2017 00:47
To: Davor Spasoski <davor.spaso...@onevip.mk>; Davor Spasoski 
<davor.spaso...@onevip.mk>; spameden <spame...@gmail.com>
Cc: users@kannel.org
Subject: Re[6]: OpenSMPPBox Panic

Please be so kind to check out latest svn again.
Probably store-type was not given in your config, but this is not needed with 
internal/mysql storage.

I need to get an better fix for this. But I am curious to know if it works for 
you now.
Apologies for the inconvenience.

== Rene


-- Origineel bericht --
Van: "Davor Spasoski" 
<davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>
Aan: "Davor Spasoski" 
<davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>; "spameden" 
<spame...@gmail.com<mailto:spame...@gmail.com>>
Cc: "users@kannel.org<mailto:users@kannel.org>" 
<users@kannel.org<mailto:users@kannel.org>>
Verzonden: 8-2-2017 14:38:05
Onderwerp: RE: Re[4]: OpenSMPPBox Panic

This is what I get when called with internal or with mysql storage. Can someone 
check please

vas@smpp-proxy:~/sources/gateway-1.5-svn-06-02-2017/addons/opensmppbox/gw$<mailto:vas@smpp-proxy:~/sources/gateway-1.5-svn-06-02-2017/addons/opensmppbox/gw$>
 /vas/bin/opensmppbox -v 1 /vas/config/kannel/opensmppbox_simple.conf
2017-02-08 14:36:14 [1332] [0] INFO: Debug_lvl = 1, log_file = , log_lvl 
= 0
2017-02-08 14:36:14 [1332] [0] INFO: DLR using storage type: internal
2017-02-08 14:36:14 [1332] [0] PANIC: /vas/bin/opensmppbox() [0x442788]
2017-02-08 14:36:14 [1332] [0] PANIC: 
/lib/x86_64-linux-gnu/libpthread.so.0(+0x113d0) [0x7f662ca5a3d0]
2017-02-08 14:36:14 [1332] [0] PANIC: /vas/bin/opensmppbox() [0x4530ba]
2017-02-08 14:36:14 [1332] [0] PANIC: 
/vas/bin/opensmppbox(octstr_str_compare+0x20) [0x454a40]
2017-02-08 14:36:14 [1332] [0] PANIC: /vas/bin/opensmppbox(store_init+0x2a) 
[0x41412a]
2017-02-08 14:36:14 [1332] [0] PANIC: /vas/bin/opensmppbox(main+0x263) 
[0x40a443]
2017-02-08 14:36:14 [1332] [0] PANIC: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f662c397830]
2017-02-08 14:36:14 [1332] [0] PANIC: /vas/bin/opensmppbox(_start+0x29) 
[0x40b349]

2017-02-08 14:34:35 [1330] [0] INFO: Debug_lvl = 1, log_file = , log_lvl 
= 0
2017-02-08 14:34:35 [1330] [0] INFO: MYSQL: Connected to server at localhost.
2017-02-08 14:34:35 [1330] [0] INFO: MYSQL: server version 
5.7.13-0ubuntu0.16.04.2, client version 5.7.17.
2017-02-08 14:34:35 [1330] [0] INFO: DLR using storage type: mysql
2017-02-08 14:34:35 [1330] [0] PANIC: /vas/bin/opensmppbox() [0x442788]
2017-02-08 14:34:35 [1330] [0] PANIC: 
/lib/x86_64-linux-gnu/libpthread.so.0(+0x113d0) [0x7f525dbc83d0]
2017-02-08 14:34:35 [1330] [0] PANIC: /vas/bin/opensmppbox() [0x4530ba]
2017-02-08 14:34:35 [1330] [0] PANIC: 
/vas/bin/opensmppbox(octstr_str_compare+0x20) [0x454a40]
2017-02-08 14:34:35 [1330] [0] PANIC: /vas/bin/opensmppbox(store_init+0x2a) 
[0x41412a]
2017-02-08 14:34:35 [1330] [0] PANIC: /vas/bin/opensmppbox(main+0x263) 
[0x40a443]
2017-02-08 14:34:35 [1330] [0] PANIC: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f525d505830]
2017-02-08 14:34:35 [1330] [0] PANIC: /vas/bin/opensmppbox(_start+0x29) 
[0x40b349]

Davor Spasoski
From: users [mailto:users-boun...@kannel.org<mailto:users-boun...@kannel.org>] 
On Behalf Of Davor Spasoski
Sent: 08 February 2017 13:32
To: spameden <spame...@gmail.com<mailto:spame...@gmail.com>>
Cc: users@kannel.org<mailto:users@kannel.org>
Subject: RE: Re[4]: OpenSMPPBox Panic

This shouldn’t be the case. I tried internal as DLR and it panics, too.

Davor Spasoski
From: spameden [mailto:spame...@gmail.com]
Sent: 06 February 2017 13:46
To: Davor Spasoski <davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>
Cc: Garry Macasieb <garry.macas...@gmail.com<mailto:garry.macas...@gmail.com>>; 
Rene Kluwen <rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>>; 
users@kannel.org<mailto:users@kannel.org>
Subject: Re: Re[4]: OpenSMPPBox Panic

Can only guess it's something to do with store format. Maybe in the new version 
it's different that's why OpenSMPPBox panics.

Try deleting store file / spool and restarting opensmppbox.

2017-02-06 13:53 GMT+03:00 Davor Spasoski 
<davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>:
Hi,

I compiled the latest opensmppbox this morning with the hope for the PANIC 
after concatenated SMS.

Now I can’t even start it. I receive panic on startup. Same config file as ever.

/vas/bin/opensmppbox -v 1 /

RE: Re[4]: OpenSMPPBox Panic

2017-02-08 Thread Davor Spasoski

This is what I get when called with internal or with mysql storage. Can someone 
check please

vas@smpp-proxy:~/sources/gateway-1.5-svn-06-02-2017/addons/opensmppbox/gw$ 
/vas/bin/opensmppbox -v 1 /vas/config/kannel/opensmppbox_simple.conf
2017-02-08 14:36:14 [1332] [0] INFO: Debug_lvl = 1, log_file = , log_lvl 
= 0
2017-02-08 14:36:14 [1332] [0] INFO: DLR using storage type: internal
2017-02-08 14:36:14 [1332] [0] PANIC: /vas/bin/opensmppbox() [0x442788]
2017-02-08 14:36:14 [1332] [0] PANIC: 
/lib/x86_64-linux-gnu/libpthread.so.0(+0x113d0) [0x7f662ca5a3d0]
2017-02-08 14:36:14 [1332] [0] PANIC: /vas/bin/opensmppbox() [0x4530ba]
2017-02-08 14:36:14 [1332] [0] PANIC: 
/vas/bin/opensmppbox(octstr_str_compare+0x20) [0x454a40]
2017-02-08 14:36:14 [1332] [0] PANIC: /vas/bin/opensmppbox(store_init+0x2a) 
[0x41412a]
2017-02-08 14:36:14 [1332] [0] PANIC: /vas/bin/opensmppbox(main+0x263) 
[0x40a443]
2017-02-08 14:36:14 [1332] [0] PANIC: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f662c397830]
2017-02-08 14:36:14 [1332] [0] PANIC: /vas/bin/opensmppbox(_start+0x29) 
[0x40b349]

2017-02-08 14:34:35 [1330] [0] INFO: Debug_lvl = 1, log_file = , log_lvl 
= 0
2017-02-08 14:34:35 [1330] [0] INFO: MYSQL: Connected to server at localhost.
2017-02-08 14:34:35 [1330] [0] INFO: MYSQL: server version 
5.7.13-0ubuntu0.16.04.2, client version 5.7.17.
2017-02-08 14:34:35 [1330] [0] INFO: DLR using storage type: mysql
2017-02-08 14:34:35 [1330] [0] PANIC: /vas/bin/opensmppbox() [0x442788]
2017-02-08 14:34:35 [1330] [0] PANIC: 
/lib/x86_64-linux-gnu/libpthread.so.0(+0x113d0) [0x7f525dbc83d0]
2017-02-08 14:34:35 [1330] [0] PANIC: /vas/bin/opensmppbox() [0x4530ba]
2017-02-08 14:34:35 [1330] [0] PANIC: 
/vas/bin/opensmppbox(octstr_str_compare+0x20) [0x454a40]
2017-02-08 14:34:35 [1330] [0] PANIC: /vas/bin/opensmppbox(store_init+0x2a) 
[0x41412a]
2017-02-08 14:34:35 [1330] [0] PANIC: /vas/bin/opensmppbox(main+0x263) 
[0x40a443]
2017-02-08 14:34:35 [1330] [0] PANIC: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f525d505830]
2017-02-08 14:34:35 [1330] [0] PANIC: /vas/bin/opensmppbox(_start+0x29) 
[0x40b349]

Davor Spasoski
From: users [mailto:users-boun...@kannel.org] On Behalf Of Davor Spasoski
Sent: 08 February 2017 13:32
To: spameden <spame...@gmail.com>
Cc: users@kannel.org
Subject: RE: Re[4]: OpenSMPPBox Panic

This shouldn’t be the case. I tried internal as DLR and it panics, too.

Davor Spasoski
From: spameden [mailto:spame...@gmail.com]
Sent: 06 February 2017 13:46
To: Davor Spasoski <davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>
Cc: Garry Macasieb <garry.macas...@gmail.com<mailto:garry.macas...@gmail.com>>; 
Rene Kluwen <rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>>; 
users@kannel.org<mailto:users@kannel.org>
Subject: Re: Re[4]: OpenSMPPBox Panic

Can only guess it's something to do with store format. Maybe in the new version 
it's different that's why OpenSMPPBox panics.

Try deleting store file / spool and restarting opensmppbox.

2017-02-06 13:53 GMT+03:00 Davor Spasoski 
<davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>:
Hi,

I compiled the latest opensmppbox this morning with the hope for the PANIC 
after concatenated SMS.

Now I can’t even start it. I receive panic on startup. Same config file as ever.

/vas/bin/opensmppbox -v 1 /vas/config/kannel/opensmppbox.conf
2017-02-06 11:35:38 [17516] [0] INFO: Debug_lvl = 1, log_file = , log_lvl 
= 0
2017-02-06 11:35:38 [17516] [0] INFO: MYSQL: Connected to server at localhost.
2017-02-06 11:35:38 [17516] [0] INFO: MYSQL: server version 
5.7.13-0ubuntu0.16.04.2, client version 5.7.17.
2017-02-06 11:35:38 [17516] [0] INFO: DLR using storage type: mysql
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox() [0x442788]
2017-02-06 11:35:38 [17516] [0] PANIC: 
/lib/x86_64-linux-gnu/libpthread.so.0(+0x113d0) [0x7f7a4312e3d0]
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox() [0x4530ba]
2017-02-06 11:35:38 [17516] [0] PANIC: 
/vas/bin/opensmppbox(octstr_str_compare+0x20) [0x454a40]
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox(store_init+0x2a) 
[0x41412a]
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox(main+0x263) 
[0x40a443]
2017-02-06 11:35:38 [17516] [0] PANIC: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f7a42a6b830]
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox(_start+0x29) 
[0x40b349]
Segmentation fault (core dumped)

Davor Spasoski
VAS Cloud & ICT Development Team Leader / Online and VAS Development

M: +38975400608
e-mail: davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>

one.Vip DOO Skopje | Filip Vtori Makedonski 3, DC Soravia 8th floor | 1000 
Skopje | Macedonia
From: Garry Macasieb 
[mailto:garry.macas...@gmail.com<mailto:garry.macas...@gmail.com>]
Sent: 01 February 2017 05:47
To: Rene Kluwen <rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>>

RE: Re[4]: OpenSMPPBox Panic

2017-02-08 Thread Davor Spasoski

This shouldn’t be the case. I tried internal as DLR and it panics, too.

Davor Spasoski
From: spameden [mailto:spame...@gmail.com]
Sent: 06 February 2017 13:46
To: Davor Spasoski <davor.spaso...@onevip.mk>
Cc: Garry Macasieb <garry.macas...@gmail.com>; Rene Kluwen 
<rene.klu...@chimit.nl>; users@kannel.org
Subject: Re: Re[4]: OpenSMPPBox Panic

Can only guess it's something to do with store format. Maybe in the new version 
it's different that's why OpenSMPPBox panics.

Try deleting store file / spool and restarting opensmppbox.

2017-02-06 13:53 GMT+03:00 Davor Spasoski 
<davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>:
Hi,

I compiled the latest opensmppbox this morning with the hope for the PANIC 
after concatenated SMS.

Now I can’t even start it. I receive panic on startup. Same config file as ever.

/vas/bin/opensmppbox -v 1 /vas/config/kannel/opensmppbox.conf
2017-02-06 11:35:38 [17516] [0] INFO: Debug_lvl = 1, log_file = , log_lvl 
= 0
2017-02-06 11:35:38 [17516] [0] INFO: MYSQL: Connected to server at localhost.
2017-02-06 11:35:38 [17516] [0] INFO: MYSQL: server version 
5.7.13-0ubuntu0.16.04.2, client version 5.7.17.
2017-02-06 11:35:38 [17516] [0] INFO: DLR using storage type: mysql
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox() [0x442788]
2017-02-06 11:35:38 [17516] [0] PANIC: 
/lib/x86_64-linux-gnu/libpthread.so.0(+0x113d0) [0x7f7a4312e3d0]
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox() [0x4530ba]
2017-02-06 11:35:38 [17516] [0] PANIC: 
/vas/bin/opensmppbox(octstr_str_compare+0x20) [0x454a40]
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox(store_init+0x2a) 
[0x41412a]
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox(main+0x263) 
[0x40a443]
2017-02-06 11:35:38 [17516] [0] PANIC: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f7a42a6b830]
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox(_start+0x29) 
[0x40b349]
Segmentation fault (core dumped)

Davor Spasoski
VAS Cloud & ICT Development Team Leader / Online and VAS Development

M: +38975400608
e-mail: davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>

one.Vip DOO Skopje | Filip Vtori Makedonski 3, DC Soravia 8th floor | 1000 
Skopje | Macedonia
From: Garry Macasieb 
[mailto:garry.macas...@gmail.com<mailto:garry.macas...@gmail.com>]
Sent: 01 February 2017 05:47
To: Rene Kluwen <rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>>
Cc: Davor Spasoski <davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>; 
users@kannel.org<mailto:users@kannel.org>
Subject: Re: Re[4]: OpenSMPPBox Panic

Hi Rene,

BIG THANKS. As tested, issue has been fixed.

Kind regards,

Garry

2017-01-31 19:57 GMT+08:00 Rene Kluwen 
<rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>>:
I invite you to try again with a fresh svn update.
It should be fixed now.

== Rene

-- Origineel bericht --
Van: "Davor Spasoski" 
<davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>
Aan: "Rene Kluwen" <rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>>
Cc: "Garry Macasieb" 
<garry.macas...@gmail.com<mailto:garry.macas...@gmail.com>>; 
"users@kannel.org<mailto:users@kannel.org>" 
<users@kannel.org<mailto:users@kannel.org>>
Verzonden: 28-1-2017 20:03:48
Onderwerp: Re: Re[2]: OpenSMPPBox Panic

Hi,

Just start opensmppbox normally. Connect a client that takes care how to split 
the SMS in two using UDH. I used kannel and let it split the message that I 
entered on smsbox's http interface.

BR,
Davor
On Jan 28, 2017, at 1:15 PM, Rene Kluwen wrote:
 I promise to look into this one of these days and provide a patch.
 Meanwhile, could somebody send me steps to reproduce?

 == Rene

 -- Origineel bericht --
 Van: "Davor Spasoski" 
<davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>
 Aan: "Garry Macasieb" 
<garry.macas...@gmail.com<mailto:garry.macas...@gmail.com>>
 Cc: "rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>" 
<rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>>; 
"users@kannel.org<mailto:users@kannel.org>" 
<users@kannel.org<mailto:users@kannel.org>>
 Verzonden: 27-1-2017 17:16:39
 Onderwerp: Re: OpenSMPPBox Panic
 I second this. The panic happens on receiving the second part. I used kannel 
as a client and the concatenation mechanism used is udh based.
 On Jan 27, 2017, at 2:13 PM, Garry Macasieb 
<garry.macas...@gmail.com<mailto:garry.macas...@gmail.com>> wrote:

 Hi Rene / Users,

 Greetings!

 Wish to consult you about the PANIC i'm getting from Opensmppbox module 
whenever sending concatenated message:

 PANIC: gwlib/octstr.c:2562: seems_valid_real: Assertion `ostr->len + 1 <= 
ostr->size' failed. (Called from gwlib/octstr.c:325:octstr_destroy.

RE: Re[4]: OpenSMPPBox Panic

2017-02-06 Thread Davor Spasoski

Hi,

I compiled the latest opensmppbox this morning with the hope for the PANIC 
after concatenated SMS.

Now I can’t even start it. I receive panic on startup. Same config file as ever.

/vas/bin/opensmppbox -v 1 /vas/config/kannel/opensmppbox.conf
2017-02-06 11:35:38 [17516] [0] INFO: Debug_lvl = 1, log_file = , log_lvl 
= 0
2017-02-06 11:35:38 [17516] [0] INFO: MYSQL: Connected to server at localhost.
2017-02-06 11:35:38 [17516] [0] INFO: MYSQL: server version 
5.7.13-0ubuntu0.16.04.2, client version 5.7.17.
2017-02-06 11:35:38 [17516] [0] INFO: DLR using storage type: mysql
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox() [0x442788]
2017-02-06 11:35:38 [17516] [0] PANIC: 
/lib/x86_64-linux-gnu/libpthread.so.0(+0x113d0) [0x7f7a4312e3d0]
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox() [0x4530ba]
2017-02-06 11:35:38 [17516] [0] PANIC: 
/vas/bin/opensmppbox(octstr_str_compare+0x20) [0x454a40]
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox(store_init+0x2a) 
[0x41412a]
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox(main+0x263) 
[0x40a443]
2017-02-06 11:35:38 [17516] [0] PANIC: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f7a42a6b830]
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox(_start+0x29) 
[0x40b349]
Segmentation fault (core dumped)

Davor Spasoski
VAS Cloud & ICT Development Team Leader / Online and VAS Development

M: +38975400608
e-mail: davor.spaso...@onevip.mk

one.Vip DOO Skopje | Filip Vtori Makedonski 3, DC Soravia 8th floor | 1000 
Skopje | Macedonia
From: Garry Macasieb [mailto:garry.macas...@gmail.com]
Sent: 01 February 2017 05:47
To: Rene Kluwen <rene.klu...@chimit.nl>
Cc: Davor Spasoski <davor.spaso...@onevip.mk>; users@kannel.org
Subject: Re: Re[4]: OpenSMPPBox Panic

Hi Rene,

BIG THANKS. As tested, issue has been fixed.

Kind regards,

Garry

2017-01-31 19:57 GMT+08:00 Rene Kluwen 
<rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>>:
I invite you to try again with a fresh svn update.
It should be fixed now.

== Rene

-- Origineel bericht --
Van: "Davor Spasoski" 
<davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>
Aan: "Rene Kluwen" <rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>>
Cc: "Garry Macasieb" 
<garry.macas...@gmail.com<mailto:garry.macas...@gmail.com>>; 
"users@kannel.org<mailto:users@kannel.org>" 
<users@kannel.org<mailto:users@kannel.org>>
Verzonden: 28-1-2017 20:03:48
Onderwerp: Re: Re[2]: OpenSMPPBox Panic

Hi,

Just start opensmppbox normally. Connect a client that takes care how to split 
the SMS in two using UDH. I used kannel and let it split the message that I 
entered on smsbox's http interface.

BR,
Davor
On Jan 28, 2017, at 1:15 PM, Rene Kluwen wrote:
 I promise to look into this one of these days and provide a patch.
 Meanwhile, could somebody send me steps to reproduce?

 == Rene

 -- Origineel bericht --
 Van: "Davor Spasoski" 
<davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>
 Aan: "Garry Macasieb" 
<garry.macas...@gmail.com<mailto:garry.macas...@gmail.com>>
 Cc: "rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>" 
<rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>>; 
"users@kannel.org<mailto:users@kannel.org>" 
<users@kannel.org<mailto:users@kannel.org>>
 Verzonden: 27-1-2017 17:16:39
 Onderwerp: Re: OpenSMPPBox Panic
 I second this. The panic happens on receiving the second part. I used kannel 
as a client and the concatenation mechanism used is udh based.
 On Jan 27, 2017, at 2:13 PM, Garry Macasieb 
<garry.macas...@gmail.com<mailto:garry.macas...@gmail.com>> wrote:

 Hi Rene / Users,

 Greetings!

 Wish to consult you about the PANIC i'm getting from Opensmppbox module 
whenever sending concatenated message:

 PANIC: gwlib/octstr.c:2562: seems_valid_real: Assertion `ostr->len + 1 <= 
ostr->size' failed. (Called from gwlib/octstr.c:325:octstr_destroy.)

 Do you have a work around for this or a working patch?

 Thanks and looking forward to your response.

 --
 Garry

 
==


 

 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 communicatio

Re: Re[2]: OpenSMPPBox Panic

2017-01-28 Thread Davor Spasoski

Hi,

Just start opensmppbox normally. Connect a client that takes care how to split 
the SMS in two using UDH. I used kannel and let it split the message that I 
entered on smsbox's http interface.

BR,
Davor
On Jan 28, 2017, at 1:15 PM, Rene Kluwen wrote:

> I promise to look into this one of these days and provide a patch.
> Meanwhile, could somebody send me steps to reproduce?
>
> == Rene
>
> -- Origineel bericht ------
> Van: "Davor Spasoski" <davor.spaso...@onevip.mk>
> Aan: "Garry Macasieb" <garry.macas...@gmail.com>
> Cc: "rene.klu...@chimit.nl" <rene.klu...@chimit.nl>; "users@kannel.org" 
> <users@kannel.org>
> Verzonden: 27-1-2017 17:16:39
> Onderwerp: Re: OpenSMPPBox Panic
>
>> I second this. The panic happens on receiving the second part. I used kannel 
>> as a client and the concatenation mechanism used is udh based.
>>
>>> On Jan 27, 2017, at 2:13 PM, Garry Macasieb <garry.macas...@gmail.com> 
>>> wrote:
>>>
>>> Hi Rene / Users,
>>>
>>> Greetings!
>>>
>>> Wish to consult you about the PANIC i'm getting from Opensmppbox module 
>>> whenever sending concatenated message:
>>>
>>> PANIC: gwlib/octstr.c:2562: seems_valid_real: Assertion `ostr->len + 1 <= 
>>> ostr->size' failed. (Called from gwlib/octstr.c:325:octstr_destroy.)
>>>
>>> Do you have a work around for this or a working patch?
>>>
>>> Thanks and looking forward to your response.
>>>
>>> --
>>> Garry
>>>
>>> ==
>>>
>>>
>>
>> 
>>
>> 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!
>>
>> Напомена: оне.Вип ДОО Скопје
>> Оваа електронска порака (вклучувајќи ги и прилозите) е доверлива и може да 
>> биде заштитена со правни привилегии. Доколку не сте лицето на кое таа му е 
>> наменета пораката, не треба да ја копирате, дистрибуирате или да ја 
>> откривате нејзината содржина, туку веднаш да ја препратите до испраќачот и 
>> да ја избришете оригиналната порака и сите нејзини копии од Вашиот 
>> компјутерски систем. Секое неовластено користење на оваа порака во целост 
>> или делови од истата е строго забрането. Ве молиме да забележите дека 
>> електронските пораки се подложни на промени. оне.Вип ДОО Скопје не презема 
>> одговорност за несоодветно или нецелосно пренесување на информациите 
>> содржани во оваа комуникација, ниту пак за било какво задоцнување на приемот 
>> или оштетувања на вашиот систем.
>> Ве молиме не ја печатете оваа порака освен ако не е неопходно! Зачувајте ја 
>> природата!
>>
>
>

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: OpenSMPPBox Panic

2017-01-27 Thread Davor Spasoski

I second this. The panic happens on receiving the second part. I used kannel as 
a client and the concatenation mechanism used is udh based.

> On Jan 27, 2017, at 2:13 PM, Garry Macasieb  wrote:
>
> Hi Rene / Users,
>
> Greetings!
>
> Wish to consult you about the PANIC i'm getting from Opensmppbox module 
> whenever sending concatenated message:
>
> PANIC: gwlib/octstr.c:2562: seems_valid_real: Assertion `ostr->len + 1 <= 
> ostr->size' failed. (Called from gwlib/octstr.c:325:octstr_destroy.)
>
> Do you have a work around for this or a working patch?
>
> Thanks and looking forward to your response.
>
> --
> Garry
>
> ==
>
>

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: http sendsms + smsc

2017-01-20 Thread Davor Spasoski

Hi Evgeniy,

You need to use one (but not both) of the directives allowed-smsc-id or 
denied-smsc-id.

For instance in the SMSC1 group add the line:
allowed-smsc-id = SMSC1

And in the SMSC2 group, add the following line:
allowed-smsc-id = SMSC2

As the names imply, allowed-smsc-id allows routing of SMS only with that value 
od smsc-id field as received from smsbox
Denied-smsc-id, will deny every SMS with smsc-id value matching any of the ids 
enumerated in that line. Anything else, even SMS with no smsc-id  will be 
served by that SMSC.

Furthermore, if you have SMSCs that both accept certain smsc-ids, using the 
“preferred-smsc-id” you can give preference towards a certain SMSC (lower cost) 
or use that in case you have geo-redundant SMSCs and want to give one location 
preference over the other, kind of sctive-standby logic.

Bearerbox will always try to route and balance between the SMSCs, so you have 
to be very carefull with the directives in order to give the SMS the propper 
route.

BR,

Davor Spasoski
From: users [mailto:users-boun...@kannel.org] On Behalf Of Eugeniy Khvastunov
Sent: 19 January 2017 16:54
To: users@kannel.org
Subject: http sendsms + smsc

Hello!
I am setup Kannel/1.4.4 under freebsd and trying to select SMSC by smsc 
variable for cgi-bin sendsms, but kannel randomly select SMSC.
In my config I have two SMSC.
Plese help, what I miss?
Some conf:

group = smsc
smsc = smpp
smsc-id = SMSC1
system-type = ""
host = 1.1.1.1
port = 29900
source-addr-autodetect = yes
transceiver-mode = true
#receive-port = 29900
interface-version = 34
smsc-username = yyy
smsc-password = yyy
enquire-link-interval = 270
source-addr-ton = 1
source-addr-npi = 1
dest-addr-ton = 0
dest-addr-npi = 1
msg-id-type = 0x03
log-file = "/var/log/kannel/yyy.log"
log-level = 0

group = smsc
smsc = smpp
smsc-id = SMSC2
system-type = ""
host = 2.2.2.2
port = 20510
source-addr-autodetect = yes
transceiver-mode = true
#receive-port = 29900
interface-version = 34
smsc-username = xxx
smsc-password = xxx
enquire-link-interval = 60
source-addr-ton = 5
source-addr-npi = 0
dest-addr-ton = 1
dest-addr-npi = 1
msg-id-type = 0x03
log-file = "/var/log/kannel/xxx.log"
log-level = 0


--
wbr. Eugeniy Khvastunov,
   System administrator.
   [FMGH-UANIC]
 http://blog.unlimite.net



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: enquire_link

2017-01-16 Thread Davor Spasoski

Anyone?

Davor Spasoski
From: Davor Spasoski
Sent: 11 January 2017 13:58
To: 'users@kannel.org' <users@kannel.org>
Subject: enquire_link

Hi,

Is there any way to instruct opensmmpbox to send enquire_link PDUs in 
configurable time intervals?

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: SMS dropped if url not available.

2017-01-12 Thread Davor Spasoski

Put these lines under the smsbox group:

#Number of rerties if the http service is unavailable
http-request-retry = 10
#Period between two retries in seconds
http-queue-delay = 60

Davor Spasoski

-Original Message-
From: users [mailto:users-boun...@kannel.org] On Behalf Of konrad.przybysz
Sent: 12 January 2017 12:09
To: users@kannel.org
Subject: SMS dropped if url not available.

Dear all,

Im using kannel 1.4.3-2. I have an smpp link in which im receiving sms messages 
from one of local service providers. Those messages are forwarded to web server 
(tomcat) for further processing.

For this forward im using sms-service configuration:

group = sms-service
keyword = default
post-url =
"https://host:port/path?charset=UTF-8=%p=%P=%b;

My problem is that sometimes tomcat is down. And all sms messages from time of 
outage are lost. Is there any way to configure kannel to check error code (or 
similar parameter). If code is not 200 (or page offline) sms should be keeped 
for later delivery?

Could you give my any clues how to create such configuration?

Thanks and best regards, Konrad



--
View this message in context: 
http://kannel.6189.n7.nabble.com/SMS-dropped-if-url-not-available-tp32648.html
Sent from the Kannel - User mailing list archive at Nabble.com.





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!

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

enquire_link

2017-01-11 Thread Davor Spasoski

Hi,

Is there any way to instruct opensmmpbox to send enquire_link PDUs in 
configurable time intervals?

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: smsc-id

2016-09-30 Thread Davor Spasoski

Hey Denis,

I applied your patch which eventually fixed both the crashing and the routing 
of AO->MT.

Thanks!
Davor
From: Денис Давыдов [mailto:dyna...@gmail.com]
Sent: 29 September 2016 15:17
To: Davor Spasoski <davor.spaso...@onevip.mk>
Cc: Rene Kluwen <rene.klu...@chimit.nl>; users@kannel.org
Subject: Re: smsc-id

Davor, use-systemid-as-smsboxid = true (not 0 or 1)

Buy the way, I've got crash too on kannel.svn-r5173. My config:

---8<---

# opensmppbox.conf

group = core
dlr-storage = sqlite3

include = "/etc/kannel/dlr-sqlite3.conf"

group = opensmppbox
opensmppbox-id = opensmppbox2
opensmppbox-port = 1522
bearerbox-host = localhost
bearerbox-port = 13002
our-system-id = opensmppbox2
smpp-logins = "/etc/kannel/smpplogins.txt.bug"
use-systemid-as-smsboxid = true
log-level = 0
log-file = /var/log/kannel/opensmppbox-bug.log

group = smsc-route
smsbox-id = nc-prod
smsc-id = "megafon-starcom"

---8<---

Program received signal SIGABRT, Aborted.
0x00110424 in __kernel_vsyscall ()
Missing separate debuginfos, use: debuginfo-install 
glibc-2.12-1.166.el6_7.3.i68   6 keyutils-libs-1.4-5.el6.i686 
krb5-libs-1.10.3-42.el6.i686 libcom_err-1.41.12-2   2.el6.i686 
libgcc-4.4.7-16.el6.i686 libselinux-2.0.94-5.8.el6.i686 libxml2-2.7.6   
-20.el6.i686 openssl-1.0.1e-42.el6.i686 sqlite-3.6.20-1.el6_7.2.i686 
zlib-1.2.3-   29.el6.i686
(gdb) bt full
#0  0x00110424 in __kernel_vsyscall ()
No symbol table info available.
#1  0x00a2e871 in raise () from /lib/libc.so.6
No symbol table info available.
#2  0x00a3014a in abort () from /lib/libc.so.6
No symbol table info available.
#3  0x00a6e735 in __libc_message () from /lib/libc.so.6
No symbol table info available.
#4  0x00a74c81 in malloc_printerr () from /lib/libc.so.6
No symbol table info available.
#5  0x00a775c2 in _int_free () from /lib/libc.so.6
No symbol table info available.
#6  0x080ae442 in octstr_destroy (ostr=0x8391a90) at gwlib/octstr.c:327
__func__ = "octstr_destroy"
#7  0x08051858 in init_smsc_routes (cfg=)
at opensmppbox.c:2388
grp = 
items = 
smsc_id = 
shortcodes = 0x0
j = 
list = 0x83919a8
boxc_ids = 0x8391a90
---Type  to continue, or q  to quit---
receiver_shortcodes = 
i = 
#8  init_smppbox (cfg=) at opensmppbox.c:2514
grp = 
logfile = 
lvl = 0
__func__ = "init_smppbox"
#9  0x08056da2 in main (argc=2, argv=0xb5e4) at opensmppbox.c:2615
cf_index = 1
filename = 
version = 0x8202700
__func__ = "main"

Try this patch:

--- addons/opensmppbox/gw/opensmppbox.c.orig2016-09-29 10:11:51.031021727 
+
+++ addons/opensmppbox/gw/opensmppbox.c 2016-09-29 13:11:28.409256265 +
@@ -2318,6 +2318,7 @@
   octstr_get_cstr(item));
 }
 gwlist_destroy(items, octstr_destroy_item);
+   octstr_destroy(receiver_shortcodes);
 };

 /* consider now the 3 possibilities: */
@@ -2383,10 +2384,9 @@
 }
 gwlist_destroy(items, octstr_destroy_item);
 octstr_destroy(shortcodes);
+octstr_destroy(boxc_ids);
 }
-octstr_destroy(smsc_id);
-octstr_destroy(boxc_ids);
-octstr_destroy(shortcodes);
+   octstr_destroy(smsc_id);
 }

 gwlist_destroy(list, NULL);


--
С уважением,
Денис Давыдов

2016-09-29 12:16 GMT+03:00 Davor Spasoski 
<davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>:
group = core
dlr-storage = mysql
…
…
…
group = opensmppbox
bearerbox-host = 127.0.0.1
bearerbox-port = 4001
opensmppbox-id = ex_one_smpp_clients
opensmppbox-port = 3339
…
our-system-id = exone
smpp-logins = /vas/config/kannel/clients
use-systemid-as-smsboxid = 1
timeout = 300

group = smsc-route
smsbox-id = "vasgw"
smsc-id = "vasgw;vasgw_OS"

I also tried the last line with a single smsc-id and with 
use-systemid-as-smsboxid = 1 or 0

Davor
From: Rene Kluwen [mailto:rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>]
Sent: 29 September 2016 10:30

To: Davor Spasoski <davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>
Cc: users@kannel.org<mailto:users@kannel.org>
Subject: RE: smsc-id

What’s your config?

Van: Davor Spasoski [mailto:davor.spaso...@onevip.mk]
Verzonden: woensdag 28 september 2016 10:37
Aan: Rene Kluwen <rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>>
CC: users@kannel.org<mailto:users@kannel.org>
Onderwerp: RE: smsc-id

And then setting the smsc-route properly results in opensmppbox crashing like 
this:

*** Error in `/vas/bin/opensmppbox': munmap_chunk(): invalid pointer: 
0x01f6f8a0 ***
/lib/x86_64-linux-gnu/libc.so.6(+0x77725)[0x7fe249b6a725]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x1a8)[0x7fe249b76c18]
….
Davor
From: users [mailto:u

RE: smsc-id

2016-09-29 Thread Davor Spasoski

group = core
dlr-storage = mysql
…
…
…
group = opensmppbox
bearerbox-host = 127.0.0.1
bearerbox-port = 4001
opensmppbox-id = ex_one_smpp_clients
opensmppbox-port = 3339
…
our-system-id = exone
smpp-logins = /vas/config/kannel/clients
use-systemid-as-smsboxid = 1
timeout = 300

group = smsc-route
smsbox-id = "vasgw"
smsc-id = "vasgw;vasgw_OS"

I also tried the last line with a single smsc-id and with 
use-systemid-as-smsboxid = 1 or 0

Davor
From: Rene Kluwen [mailto:rene.klu...@chimit.nl]
Sent: 29 September 2016 10:30
To: Davor Spasoski <davor.spaso...@onevip.mk>
Cc: users@kannel.org
Subject: RE: smsc-id

What’s your config?

Van: Davor Spasoski [mailto:davor.spaso...@onevip.mk]
Verzonden: woensdag 28 september 2016 10:37
Aan: Rene Kluwen <rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>>
CC: users@kannel.org<mailto:users@kannel.org>
Onderwerp: RE: smsc-id

And then setting the smsc-route properly results in opensmppbox crashing like 
this:

*** Error in `/vas/bin/opensmppbox': munmap_chunk(): invalid pointer: 
0x01f6f8a0 ***
/lib/x86_64-linux-gnu/libc.so.6(+0x77725)[0x7fe249b6a725]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x1a8)[0x7fe249b76c18]
….
Davor
From: users [mailto:users-boun...@kannel.org] On Behalf Of Davor Spasoski
Sent: 25 September 2016 21:52
To: Rene Kluwen <rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>>
Cc: users@kannel.org<mailto:users@kannel.org>
Subject: RE: smsc-id

OK, I got-it. Smsbox-id will actually be populated with system-type or 
system-id. Hard to read those xml files :)

Davor
From: Davor Spasoski
Sent: 25 September 2016 21:40
To: 'Rene Kluwen' <rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>>
Cc: users@kannel.org<mailto:users@kannel.org>
Subject: RE: smsc-id

Hi Rene,

Thank you for your reply. The reason I missed the smsc-route is because I 
relied on a pdf version of the manual online and the whole group was missing 
there.
Now I went throught the xml manual but still couldn’t find any system-id or 
system-type syntax under the smsc-route group.
When I added something like:
Group = sms-route
Smsc-id = smsc1
System-id = vasgw or system-type = vasgw

I got:
ERROR: Group 'smsc-route' (or smsc-type) may not contain field 'system-type'

I’ve downloaded the opensmppbox from svn co 
https://svn.kannel.org/opensmppbox/trunk
What is the proper syntax for system-id or system-type directive under 
smsc-route?

BR,
Davor Spasoski

M: + 389 75 400 608
e-mail: davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>

one.Vip DOO Skopje | Filip Vtori Makedonski 3, DC Soravia 8th floor | 1000 
Skopje | Macedonia

From: Rene Kluwen [mailto:rene.klu...@chimit.nl]
Sent: 24 September 2016 15:45
To: Davor Spasoski <davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>
Cc: users@kannel.org<mailto:users@kannel.org>
Subject: RE: smsc-id

Check the opensmppbox user guide for group = smsc-route.
You can either use system-id or system-type for that. This is also covered in 
that same manual.

== Rene


Van: Davor Spasoski [mailto:davor.spaso...@onevip.mk]
Verzonden: donderdag 22 september 2016 10:06
Aan: rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>
Onderwerp: smsc-id

Dear Rene,

My apology for contacting you directly because I’ve previously posted a 
question on the user forum and also on the feature tracker on 
redmine.kannel.org. I don’t see any recent project activy lately, so I took the 
liberty to contact you.

My setup is such that opensmppbox+kannel should act as a sort of transparent 
smpp proxy and pass system-id/password from one side to the other for a bunch 
of ESME. This is so, because our new SMSC host a) doesn’t allow direct access 
and b) has a pair of SMSC. To avoid client disruption, I will preserve the 
single ip and port of the old SMSC and assign-it to opensmppbox, which means I 
will not have the liberty to run multiple opensmppbox instances. On the 
bearerbox side I will connet to the SMSC pair as many times as the number of 
clients. That means that I will have 2 x ESME number smscs and ESME number of 
smsc-ids

As is the current feature set of opensmppbox, I cannot assign smsc-id per 
client (system-id) entry in the clients.conf file and SMS from all ESME will be 
balanced across all smscs which is a big no in my case. I need certain 
system-ids to be routed to exactly the allowed smsc(s) and vice versa.

Unfortunatelly, my programming knowledge is limited to php and touching the C 
code is risky for me. Would you like to at least point in which way to 
intervene in the code and I could find someone who knows C to write the actual 
code?

Thanks for reading, I’m hoping on a response.

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-tran

RE: smsc-id

2016-09-28 Thread Davor Spasoski

And then setting the smsc-route properly results in opensmppbox crashing like 
this:

*** Error in `/vas/bin/opensmppbox': munmap_chunk(): invalid pointer: 
0x01f6f8a0 ***
/lib/x86_64-linux-gnu/libc.so.6(+0x77725)[0x7fe249b6a725]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x1a8)[0x7fe249b76c18]
….
Davor
From: users [mailto:users-boun...@kannel.org] On Behalf Of Davor Spasoski
Sent: 25 September 2016 21:52
To: Rene Kluwen <rene.klu...@chimit.nl>
Cc: users@kannel.org
Subject: RE: smsc-id

OK, I got-it. Smsbox-id will actually be populated with system-type or 
system-id. Hard to read those xml files :)

Davor
From: Davor Spasoski
Sent: 25 September 2016 21:40
To: 'Rene Kluwen' <rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>>
Cc: users@kannel.org<mailto:users@kannel.org>
Subject: RE: smsc-id

Hi Rene,

Thank you for your reply. The reason I missed the smsc-route is because I 
relied on a pdf version of the manual online and the whole group was missing 
there.
Now I went throught the xml manual but still couldn’t find any system-id or 
system-type syntax under the smsc-route group.
When I added something like:
Group = sms-route
Smsc-id = smsc1
System-id = vasgw or system-type = vasgw

I got:
ERROR: Group 'smsc-route' (or smsc-type) may not contain field 'system-type'

I’ve downloaded the opensmppbox from svn co 
https://svn.kannel.org/opensmppbox/trunk
What is the proper syntax for system-id or system-type directive under 
smsc-route?

BR,
Davor Spasoski

M: + 389 75 400 608
e-mail: davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>

one.Vip DOO Skopje | Filip Vtori Makedonski 3, DC Soravia 8th floor | 1000 
Skopje | Macedonia

From: Rene Kluwen [mailto:rene.klu...@chimit.nl]
Sent: 24 September 2016 15:45
To: Davor Spasoski <davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>
Cc: users@kannel.org<mailto:users@kannel.org>
Subject: RE: smsc-id

Check the opensmppbox user guide for group = smsc-route.
You can either use system-id or system-type for that. This is also covered in 
that same manual.

== Rene


Van: Davor Spasoski [mailto:davor.spaso...@onevip.mk]
Verzonden: donderdag 22 september 2016 10:06
Aan: rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>
Onderwerp: smsc-id

Dear Rene,

My apology for contacting you directly because I’ve previously posted a 
question on the user forum and also on the feature tracker on 
redmine.kannel.org. I don’t see any recent project activy lately, so I took the 
liberty to contact you.

My setup is such that opensmppbox+kannel should act as a sort of transparent 
smpp proxy and pass system-id/password from one side to the other for a bunch 
of ESME. This is so, because our new SMSC host a) doesn’t allow direct access 
and b) has a pair of SMSC. To avoid client disruption, I will preserve the 
single ip and port of the old SMSC and assign-it to opensmppbox, which means I 
will not have the liberty to run multiple opensmppbox instances. On the 
bearerbox side I will connet to the SMSC pair as many times as the number of 
clients. That means that I will have 2 x ESME number smscs and ESME number of 
smsc-ids

As is the current feature set of opensmppbox, I cannot assign smsc-id per 
client (system-id) entry in the clients.conf file and SMS from all ESME will be 
balanced across all smscs which is a big no in my case. I need certain 
system-ids to be routed to exactly the allowed smsc(s) and vice versa.

Unfortunatelly, my programming knowledge is limited to php and touching the C 
code is risky for me. Would you like to at least point in which way to 
intervene in the code and I could find someone who knows C to write the actual 
code?

Thanks for reading, I’m hoping on a response.

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!

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

RE: smsc-id

2016-09-25 Thread Davor Spasoski

OK, I got-it. Smsbox-id will actually be populated with system-type or 
system-id. Hard to read those xml files :)

Davor
From: Davor Spasoski
Sent: 25 September 2016 21:40
To: 'Rene Kluwen' <rene.klu...@chimit.nl>
Cc: users@kannel.org
Subject: RE: smsc-id

Hi Rene,

Thank you for your reply. The reason I missed the smsc-route is because I 
relied on a pdf version of the manual online and the whole group was missing 
there.
Now I went throught the xml manual but still couldn’t find any system-id or 
system-type syntax under the smsc-route group.
When I added something like:
Group = sms-route
Smsc-id = smsc1
System-id = vasgw or system-type = vasgw

I got:
ERROR: Group 'smsc-route' (or smsc-type) may not contain field 'system-type'

I’ve downloaded the opensmppbox from svn co 
https://svn.kannel.org/opensmppbox/trunk
What is the proper syntax for system-id or system-type directive under 
smsc-route?

BR,
Davor Spasoski

M: + 389 75 400 608
e-mail: davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>

one.Vip DOO Skopje | Filip Vtori Makedonski 3, DC Soravia 8th floor | 1000 
Skopje | Macedonia

From: Rene Kluwen [mailto:rene.klu...@chimit.nl]
Sent: 24 September 2016 15:45
To: Davor Spasoski <davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>
Cc: users@kannel.org<mailto:users@kannel.org>
Subject: RE: smsc-id

Check the opensmppbox user guide for group = smsc-route.
You can either use system-id or system-type for that. This is also covered in 
that same manual.

== Rene

Van: Davor Spasoski [mailto:davor.spaso...@onevip.mk]
Verzonden: donderdag 22 september 2016 10:06
Aan: rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>
Onderwerp: smsc-id

Dear Rene,

My apology for contacting you directly because I’ve previously posted a 
question on the user forum and also on the feature tracker on 
redmine.kannel.org. I don’t see any recent project activy lately, so I took the 
liberty to contact you.

My setup is such that opensmppbox+kannel should act as a sort of transparent 
smpp proxy and pass system-id/password from one side to the other for a bunch 
of ESME. This is so, because our new SMSC host a) doesn’t allow direct access 
and b) has a pair of SMSC. To avoid client disruption, I will preserve the 
single ip and port of the old SMSC and assign-it to opensmppbox, which means I 
will not have the liberty to run multiple opensmppbox instances. On the 
bearerbox side I will connet to the SMSC pair as many times as the number of 
clients. That means that I will have 2 x ESME number smscs and ESME number of 
smsc-ids

As is the current feature set of opensmppbox, I cannot assign smsc-id per 
client (system-id) entry in the clients.conf file and SMS from all ESME will be 
balanced across all smscs which is a big no in my case. I need certain 
system-ids to be routed to exactly the allowed smsc(s) and vice versa.

Unfortunatelly, my programming knowledge is limited to php and touching the C 
code is risky for me. Would you like to at least point in which way to 
intervene in the code and I could find someone who knows C to write the actual 
code?

Thanks for reading, I’m hoping on a response.

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!

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

Disclaimer: one.Vip DOO Skopje
This e-mail (including any

RE: smsc-id

2016-09-25 Thread Davor Spasoski

Hi Rene,

Thank you for your reply. The reason I missed the smsc-route is because I 
relied on a pdf version of the manual online and the whole group was missing 
there.
Now I went throught the xml manual but still couldn’t find any system-id or 
system-type syntax under the smsc-route group.
When I added something like:
Group = sms-route
Smsc-id = smsc1
System-id = vasgw or system-type = vasgw

I got:
ERROR: Group 'smsc-route' (or smsc-type) may not contain field 'system-type'

I’ve downloaded the opensmppbox from svn co 
https://svn.kannel.org/opensmppbox/trunk
What is the proper syntax for system-id or system-type directive under 
smsc-route?

BR,
Davor Spasoski

M: + 389 75 400 608
e-mail: davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>

one.Vip DOO Skopje | Filip Vtori Makedonski 3, DC Soravia 8th floor | 1000 
Skopje | Macedonia

From: Rene Kluwen [mailto:rene.klu...@chimit.nl]
Sent: 24 September 2016 15:45
To: Davor Spasoski <davor.spaso...@onevip.mk>
Cc: users@kannel.org
Subject: RE: smsc-id

Check the opensmppbox user guide for group = smsc-route.
You can either use system-id or system-type for that. This is also covered in 
that same manual.

== Rene


Van: Davor Spasoski [mailto:davor.spaso...@onevip.mk]
Verzonden: donderdag 22 september 2016 10:06
Aan: rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>
Onderwerp: smsc-id

Dear Rene,

My apology for contacting you directly because I’ve previously posted a 
question on the user forum and also on the feature tracker on 
redmine.kannel.org. I don’t see any recent project activy lately, so I took the 
liberty to contact you.

My setup is such that opensmppbox+kannel should act as a sort of transparent 
smpp proxy and pass system-id/password from one side to the other for a bunch 
of ESME. This is so, because our new SMSC host a) doesn’t allow direct access 
and b) has a pair of SMSC. To avoid client disruption, I will preserve the 
single ip and port of the old SMSC and assign-it to opensmppbox, which means I 
will not have the liberty to run multiple opensmppbox instances. On the 
bearerbox side I will connet to the SMSC pair as many times as the number of 
clients. That means that I will have 2 x ESME number smscs and ESME number of 
smsc-ids

As is the current feature set of opensmppbox, I cannot assign smsc-id per 
client (system-id) entry in the clients.conf file and SMS from all ESME will be 
balanced across all smscs which is a big no in my case. I need certain 
system-ids to be routed to exactly the allowed smsc(s) and vice versa.

Unfortunatelly, my programming knowledge is limited to php and touching the C 
code is risky for me. Would you like to at least point in which way to 
intervene in the code and I could find someone who knows C to write the actual 
code?

Thanks for reading, I’m hoping on a response.

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!

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



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 i

Re: Load balancing MT with preferred SMSC

2016-09-22 Thread Davor Spasoski

Thanks. Is it also kannel based?

Davor

Sent from my iPad

> On 22.9.2016, at 19:39, vinayak mv <vinayakvasu...@gmail.com> wrote:
>
> Dear Davor,
>
> There is also an alternative solution for SMPP Server i.e. vsmppbox ,which 
> has more features compared to other smpp servers.you can find the details of 
> that in http://www.evoxtel.com
>
>> On 22-Sep-2016, at 7:32 PM, Stipe Tolj <st...@kannel.org> wrote:
>>
>> Am 21.09.2016 08:25, schrieb Davor Spasoski:
>>> Hi,
>>>
>>> I realized yesterday that the reason the allowed/preferred trickery
>>> doesn’t work is because opensmppbox doesn’t pass smsc-id dynamically.
>>> It’s either a static value using the route-to-smsc directive or it’s
>>> blank if this is omitted. The whole point of my usecase was to have
>>> different ESMEs routed to different smscs and all that by using a single
>>> opensmpp instance (IP/port) due to specific circumstances of the case I
>>> need to solve.
>>>
>>> AFAICS, for this to work it needs development.
>>
>> Hi Davor,
>>
>> correct, the opensmppbox isn't able to handle such routing internally. For 
>> the purposes you intend to it's more suitable to use the commercial Kannel 
>> SMPP v5.0 server (smppbox), which is a true virtual SMSC solution allowing 
>> the same connection scheme, but with a major benefit in configuration 
>> ability and flexibility.
>>
>> Please let me know if you would like to hear more details and we can arrange 
>> for a test-drive on your own system to get going.
>>
>> --
>> Best Regards,
>> Stipe Tolj
>>
>> ---
>> Düsseldorf, NRW, Germany
>>
>> Kannel Foundation tolj.org system architecture
>> http://www.kannel.org/http://www.tolj.org/
>>
>> stolj at kannel.org   st at 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: Load balancing MT with preferred SMSC

2016-09-22 Thread Davor Spasoski

Hi Stipe,

Thanks for confirming. Yes, I would like to have more details about the 
mentioned product.

Davor

Sent from my iPad

> On 22.9.2016, at 16:03, Stipe Tolj <st...@kannel.org> wrote:
>
> Am 21.09.2016 08:25, schrieb Davor Spasoski:
>> Hi,
>>
>> I realized yesterday that the reason the allowed/preferred trickery
>> doesn’t work is because opensmppbox doesn’t pass smsc-id dynamically.
>> It’s either a static value using the route-to-smsc directive or it’s
>> blank if this is omitted. The whole point of my usecase was to have
>> different ESMEs routed to different smscs and all that by using a single
>> opensmpp instance (IP/port) due to specific circumstances of the case I
>> need to solve.
>>
>> AFAICS, for this to work it needs development.
>
> Hi Davor,
>
> correct, the opensmppbox isn't able to handle such routing internally. For 
> the purposes you intend to it's more suitable to use the commercial Kannel 
> SMPP v5.0 server (smppbox), which is a true virtual SMSC solution allowing 
> the same connection scheme, but with a major benefit in configuration ability 
> and flexibility.
>
> Please let me know if you would like to hear more details and we can arrange 
> for a test-drive on your own system to get going.
>
> --
> Best Regards,
> Stipe Tolj
>
> ---
> Düsseldorf, NRW, Germany
>
> Kannel Foundation tolj.org system architecture
> http://www.kannel.org/http://www.tolj.org/
>
> stolj at kannel.org   st at 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: Load balancing MT with preferred SMSC

2016-09-21 Thread Davor Spasoski

Hi,

I realized yesterday that the reason the allowed/preferred trickery doesn’t 
work is because opensmppbox doesn’t pass smsc-id dynamically. It’s either a 
static value using the route-to-smsc directive or it’s blank if this is 
omitted. The whole point of my usecase was to have different ESMEs routed to 
different smscs and all that by using a single opensmpp instance (IP/port) due 
to specific circumstances of the case I need to solve.

AFAICS, for this to work it needs development.

BR,
Davor
Davor Spasoski
From: DHC Admin [mailto:dhcad...@gmail.com]
Sent: 21 September 2016 04:16
To: Davor Spasoski <davor.spaso...@onevip.mk>
Cc: users@kannel.org
Subject: Re: Load balancing MT with preferred SMSC

Of course you have removed the # form those lines, right? Other than that, I 
cannot tell why it's not working for you.

On Sat, Sep 17, 2016 at 8:48 AM, Davor Spasoski 
<davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>> wrote:
Hi,

I’m trying to  use opensmppbox and kannel to act as SMPP proxy. The SMSC 
operator doesn’t allow direct connections and it has two SMSCs, one of which is 
preferred and the other handles traffic if only the preferred fails. But, both 
are always active, i.e. bearerbox is normally bound to both.
I have a dozen of ESMEs that should connect to opensmppbox with a single bind 
and then bearerbox should make two connections to smsc1 and smsc2 for each and 
every esme. To simplify, the flow with one  ESME would look like this:

    ___   _
ESME1 --> | Opensmppbox   | --> | Bearerbox |---> |SMSC1|
|   ||   |  -
|___||   |---> |SMSC2|
|___|  -

For each new ESME there would be a new set of binds from bearerbox to SMSCs and 
the system-id of the esme should distinguish the rotue in bearerbox.
Hence, use-systemid-as-smsboxid is set to true in opensmppbox.conf

At the moment, I have two fake SMSCs with same SMSC-id and they share the load 
as expected. However, no matter what I try with directives like 
preferred-smsc-id and allowed-smsc-id, I can’t make a confgiration to make 
bearerbox route all MT SMS to SMSC1 only and route to SMSC2 if only SMSC1 is 
down.

This is part of my bearerbox configuration:

group = smsc
smsc = fake
port = 12000
smsc-id = vasgw
#allowed-smsc-id = "vasgw"
#preferred-smsc-id = "vasgw"

group = smsc
smsc = fake
port = 12001
smsc-id = vasgw
#allowed-smsc-id = "vasgw"

Also, bearebox should accept MO SMS from any of the SMSC1 and SMSC2

Any ideas how to achieve this?

BR,
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!

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




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 t

Load balancing MT with preferred SMSC

2016-09-17 Thread Davor Spasoski

Hi,

I’m trying to use opensmppbox and kannel to act as SMPP proxy. The SMSC
operator doesn’t allow direct connections and it has two SMSCs, one of which is
preferred and the other handles traffic if only the preferred fails. But, both
are always active, i.e. bearerbox is normally bound to both.
I have a dozen of ESMEs that should connect to opensmppbox with a single bind
and then bearerbox should make two connections to smsc1 and smsc2 for each and
every esme. To simplify, the flow with one ESME would look like this:

___ _
ESME1 --> | Opensmppbox | --> | Bearerbox |---> |SMSC1|
| || | -
|___|| |---> |SMSC2|
|___| -

For each new ESME there would be a new set of binds from bearerbox to SMSCs and
the system-id of the esme should distinguish the rotue in bearerbox.
Hence, use-systemid-as-smsboxid is set to true in opensmppbox.conf

At the moment, I have two fake SMSCs with same SMSC-id and they share the load
as expected. However, no matter what I try with directives like
preferred-smsc-id and allowed-smsc-id, I can’t make a confgiration to make
bearerbox route all MT SMS to SMSC1 only and route to SMSC2 if only SMSC1 is
down.

This is part of my bearerbox configuration:

group = smsc
smsc = fake
port = 12000
smsc-id = vasgw
#allowed-smsc-id = "vasgw"
#preferred-smsc-id = "vasgw"

group = smsc
smsc = fake
port = 12001
smsc-id = vasgw
#allowed-smsc-id = "vasgw"

Also, bearebox should accept MO SMS from any of the SMSC1 and SMSC2

Any ideas how to achieve this?

BR,
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!

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

RE: alt-charset // coding pages

2008-10-30 Thread Davor Spasoski

Hi,

What do you mean by special characters? If you don't specify the 
charset/encoding, kannel defaults to ISO8859-1 and translates all that can fit 
into the GSM 7-bit alphabet. Maybe you are trying to send something outside the 
GSM alphabet. (Handsets basically support GSM and UCS-2 for SMS) For special 
characters you will need to use UTF-8 and kannel will in turn translate this 
into telecom standard UCS-2 charset. This is as far as I understand and 
confirmed with testing on versions up to 1.4

BR,

Davor


-Original Message-
From: Alexander Eckert [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 30, 2008 10:43 AM
To: users@kannel.org
Subject: alt-charset // coding pages

Hi,

maybe someone is able to bring a light into my darkness.

I use a cvs version of kannel to test - and for sure the the stable
1.4.1 version in productive enviroment.

On 1.4.1 i do not need to set any charset option to send SMS via
http request to kannel. If i try that on the cvs version this won`t
work at all. No special character is being sent to the mobile correctly.
I tried to find some hints inside the maillist archive but there
is nothing which helps me.

2008-10-30 10:23:03 [27125] [6] DEBUG: SMPP PDU 0x81bdca8 dump:
2008-10-30 10:23:03 [27125] [6] DEBUG:   type_name: submit_sm
2008-10-30 10:23:03 [27125] [6] DEBUG:   command_id: 4 = 0x0004
2008-10-30 10:23:03 [27125] [6] DEBUG:   command_status: 0 = 0x
2008-10-30 10:23:03 [27125] [6] DEBUG:   sequence_number: 4 = 0x0004
2008-10-30 10:23:03 [27125] [6] DEBUG:   service_type: 900015
2008-10-30 10:23:03 [27125] [6] DEBUG:   source_addr_ton: 5 = 0x0005
2008-10-30 10:23:03 [27125] [6] DEBUG:   source_addr_npi: 0 = 0x
2008-10-30 10:23:03 [27125] [6] DEBUG:   source_addr: mobilcom
2008-10-30 10:23:03 [27125] [6] DEBUG:   dest_addr_ton: 2 = 0x0002
2008-10-30 10:23:03 [27125] [6] DEBUG:   dest_addr_npi: 1 = 0x0001
2008-10-30 10:23:03 [27125] [6] DEBUG:   destination_addr:
00491704001858
2008-10-30 10:23:03 [27125] [6] DEBUG:   esm_class: 3 = 0x0003
2008-10-30 10:23:03 [27125] [6] DEBUG:   protocol_id: 0 = 0x
2008-10-30 10:23:03 [27125] [6] DEBUG:   priority_flag: 0 = 0x
2008-10-30 10:23:03 [27125] [6] DEBUG:   schedule_delivery_time: NULL
2008-10-30 10:23:03 [27125] [6] DEBUG:   validity_period: NULL
2008-10-30 10:23:03 [27125] [6] DEBUG:   registered_delivery: 0 =
0x
2008-10-30 10:23:03 [27125] [6] DEBUG:   replace_if_present_flag: 0 =
0x
2008-10-30 10:23:03 [27125] [6] DEBUG:   data_coding: 0 = 0x
2008-10-30 10:23:03 [27125] [6] DEBUG:   sm_default_msg_id: 0 =
0x
2008-10-30 10:23:03 [27125] [6] DEBUG:   sm_length: 6 = 0x0006
2008-10-30 10:23:03 [27125] [6] DEBUG:   short_message: test ?
2008-10-30 10:23:03 [27125] [6] DEBUG: SMPP PDU dump ends.

If i set the charset variable inside the http request to:
charset=WINDOWS-125
i get all the special characters being sent fine.

2008-10-30 10:37:41 [21393] [6] DEBUG: SMPP PDU 0x81a1260 dump:
2008-10-30 10:37:41 [21393] [6] DEBUG:   type_name: submit_sm
2008-10-30 10:37:41 [21393] [6] DEBUG:   command_id: 4 = 0x0004
2008-10-30 10:37:41 [21393] [6] DEBUG:   command_status: 0 = 0x
2008-10-30 10:37:41 [21462] [0] DEBUG: Got ACK (0) of
808b1a8e-b086-4db7-b81a-a0e79b0a9ad6
2008-10-30 10:37:41 [21393] [6] DEBUG:   sequence_number: 2 = 0x0002
2008-10-30 10:37:41 [21393] [6] DEBUG:   service_type: 900015
2008-10-30 10:37:41 [21393] [6] DEBUG:   source_addr_ton: 5 = 0x0005
2008-10-30 10:37:41 [21393] [6] DEBUG:   source_addr_npi: 0 = 0x
2008-10-30 10:37:41 [21393] [6] DEBUG:   source_addr: mobilcom
2008-10-30 10:37:41 [21462] [0] DEBUG: HTTP: Resetting HTTPClient for
`62.104.242.109'.
2008-10-30 10:37:41 [21393] [6] DEBUG:   dest_addr_ton: 2 = 0x0002
2008-10-30 10:37:41 [21393] [6] DEBUG:   dest_addr_npi: 1 = 0x0001
2008-10-30 10:37:41 [21393] [6] DEBUG:   destination_addr:
00491704001858
2008-10-30 10:37:41 [21393] [6] DEBUG:   esm_class: 3 = 0x0003
2008-10-30 10:37:41 [21393] [6] DEBUG:   protocol_id: 0 = 0x
2008-10-30 10:37:41 [21393] [6] DEBUG:   priority_flag: 0 = 0x
2008-10-30 10:37:41 [21393] [6] DEBUG:   schedule_delivery_time: NULL
2008-10-30 10:37:41 [21393] [6] DEBUG:   validity_period: NULL
2008-10-30 10:37:41 [21393] [6] DEBUG:   registered_delivery: 0 =
0x
2008-10-30 10:37:41 [21393] [6] DEBUG:   replace_if_present_flag: 0 =
0x
2008-10-30 10:37:41 [21393] [6] DEBUG:   data_coding: 0 = 0x
2008-10-30 10:37:41 [21393] [6] DEBUG:   sm_default_msg_id: 0 =
0x
2008-10-30 10:37:41 [21393] [6] DEBUG:   sm_length: 8 = 0x0008
2008-10-30 10:37:41 [21393] [6] DEBUG:   short_message: test {|~
2008-10-30 10:37:41 [21393] [6] DEBUG: SMPP PDU dump ends.

Does that means i do need now change all my http request to include the
charset
variable ? I tried to set alt-charset inside the SMPP config group but
this
won`t work at all.


COSMOFON - Mobile

RE: Kannel startup script does not stop bearerbox completely

2008-10-28 Thread Davor Spasoski

Can you please be more precise with your method?
Tried mv access.log acess.rotated
cp blank acess.log
but kannel continues to write in the acess.rotated

Davor


-Original Message-
From: Mihai Zsigmond [mailto:[EMAIL PROTECTED]
Sent: Monday, October 27, 2008 7:02 PM
To: users@kannel.org
Subject: RE: Kannel startup script does not stop bearerbox completely




--- On Mon, 10/27/08, Mihai Zsigmond [EMAIL PROTECTED] wrote:

 From: Mihai Zsigmond [EMAIL PROTECTED]
 Subject: RE: Kannel startup script does not stop bearerbox completely
 To: [EMAIL PROTECTED]
 Date: Monday, October 27, 2008, 7:55 PM
 Hi guys,

 I'm adding my 5 cents' worth at this discussion.

 The bearerbox waits for all SMSC connections to be properly
 closed, before it can close itself. This can take some time,
 mostly when connections are UCP/EMI type. You can skip this
 wait issuing a second kill command, which closes immediately
 the bearerbox and puts Can not die at its own
 will message in the log.

 However, there is a more elegant approach to log rotation,
 which does NOT stop the bearerbox.
 Instead, my log script renames the log file to some other
 name and then copies a blank file with the name of the log.
 This method has been working for the past four years on
 different Kannel versions on Fedora and CentOS systems.

 Yet, I have never tested this method in high volume traffic
 environment, we are limited by our SMS providers to 1
 SMS/sec rate.

 Hope it helps.

 Best regards,
 Mihai Zsigmond

 --- On Mon, 10/27/08, Mathieu Bruneau
 [EMAIL PROTECTED] wrote:

  From: Mathieu Bruneau
 [EMAIL PROTECTED]
  Subject: RE: Kannel startup script does not stop
 bearerbox completely
  To: Jason Mule
 [EMAIL PROTECTED], users@kannel.org
  Date: Monday, October 27, 2008, 6:36 PM
  We have seen a similar thing, however ours _usually_
  shutdown within
  30s... The SMS server is still on Debian Sarge
 however.
 
  I usually do an strace on the process and see it's
  actually does a futex
  (Don't have the exact line atm) operation. I
 always
  tought it was
  actually waiting for all connection to be cleanly
 closed
  (?). I'm
  usually able to use the status command
 till
  it's almost closed and see
  which connections are still active.
 
  However for log rotation, in sarge at least it's
 doing
  an HUP and we
  never had issue I can recall...
 
  /var/log/kannel/*.log {
  daily
  missingok
  rotate 100
  olddir /var/log/kannel/backup
  compress
  create 640 kannel adm
  sharedscripts
  postrotate
  killall -HUP bearerbox smsbox wapbox
 
  /dev/null 2
  /dev/null || true
  endscript
  }
 
  Regards,
  Mathieu Bruneau
 
  -Original Message-
  From: Jason Mule [mailto:[EMAIL PROTECTED]
  Sent: Monday, October 27, 2008 11:02 AM
  To: users@kannel.org
  Subject: Kannel startup script does not stop bearerbox
  completely
 
  Hi,
  Can anyone else on this list confirm this? I have
 noticed
  that the
  Kannel init script (Debian Etch, Kannel 1.4.1) does
 not
  stop bearerbox
  completely when called. After calling
  'start-stop-daemon --stop --retry
  5 --pidfile $PIDFILES/kannel_bearerbox.pid --exec
  $BOXPATH/run_kannel_box' , a bearerbox process
 remains
  which must be
  killed manually or by adding a line similar to the one
  below to the init
  script:
 
  # Wait for bearerbox to finish
  start-stop-daemon --stop --quiet --oknodo
  --retry=0/30/KILL/5 --exec
  $BOXPATH/bearerbox
 
  --
  Kind regards
  Jason Mule





COSMOFON - Mobile Telecommunications Services - A.D. 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. COSMOFON A.D. 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.

RE: Kannel startup script does not stop bearerbox completely

2008-10-27 Thread Davor Spasoski

Hi

Yes, I can confimr this happens to me too, and it seems that this is related to 
the traffic the bearerbox was dealing with at the moment the it's called to 
stop.
Bearerbox behaves the same on HUP and it is really impossible to rotate its 
logs at the required time.

Davor

-Original Message-
From: Jason Mule [mailto:[EMAIL PROTECTED]
Sent: Monday, October 27, 2008 4:02 PM
To: users@kannel.org
Subject: Kannel startup script does not stop bearerbox completely

Hi,
Can anyone else on this list confirm this? I have noticed that the
Kannel init script (Debian Etch, Kannel 1.4.1) does not stop bearerbox
completely when called. After calling 'start-stop-daemon --stop
--retry 5 --pidfile $PIDFILES/kannel_bearerbox.pid --exec
$BOXPATH/run_kannel_box' , a bearerbox process remains which must be
killed manually or by adding a line similar to the one below to the
init script:

# Wait for bearerbox to finish
start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec
$BOXPATH/bearerbox

--
Kind regards
Jason Mule


COSMOFON - Mobile Telecommunications Services - A.D. 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. COSMOFON A.D. 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.

RE: GUI

2008-03-12 Thread Davor Spasoski

GUI would be nice thing but what it's good for when kannel needs a restart once 
a new service is defined in the config file? It would be much more useful to 
build a reload (without restart) function. Another thing I would like to see is 
queueing and throttling mechanism per sender.


Davor Spasoski



From: preeteesh kakkar [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 12, 2008 1:34 PM
To: [EMAIL PROTECTED]
Cc: mms test; users@kannel.org
Subject: Re: GUI

I totally agree if somone is doing the best language for it would be PHP...!
On Wed, Mar 12, 2008 at 6:00 PM, Michael Sole [EMAIL PROTECTED]mailto:[EMAIL 
PROTECTED] wrote:

For the love of God do not do this in JSP!



PHP is the only way to go in my opinion.



From: Atul Chaudhari [mailto:[EMAIL PROTECTED]mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 12, 2008 8:29 AM
To: Remon Magdy
Cc: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED]; mms test; 
users@kannel.orgmailto:users@kannel.org
Subject: Re: GUI



we could use GTK so that it becomes OS independant and we can also have a 
desktop utility.


On Wed, Mar 12, 2008 at 5:44 PM, Remon Magdy [EMAIL PROTECTED]mailto:[EMAIL 
PROTECTED] wrote:

Hello All,

We can all start building a web GUI interface for Kannel administration,
I've been interested in the issue since a while and can help initiating
the development phase, I use JAVA/JSP for such projects and I can learn
PHP if needed.

I've been managing and administrating Kannel for a while and know the
basics to develop such project.

My hope is to build a web based GUI for managing both Kannel (Including
SMPP server by Stipe) and Mbuni.

If anybody is interested to join me please contact me.

Regards,
Remon

I'

Michael Sole wrote:
 A web based configuration and administration tool would be quite useful as
 setting up and configuring Kannel is quite the task.

 -Original Message-
 From: mms test [mailto:[EMAIL PROTECTED]mailto:[EMAIL PROTECTED]]
 Sent: Wednesday, March 12, 2008 7:27 AM
 To: users@kannel.orgmailto:users@kannel.org
 Subject: GUI

 Dear All,

 I need to know that is any open source GUI application available
 through which all configurations of Kannel can be done or any one has
 developed it for its own use.

 I need this type of application.What development tools  techniques
 you guys would suggest for development.

 Thanks in advance.








--
Thanks and Best regards
Atul Chaudhari


COSMOFON - Mobile Telecommunications Services - A.D. 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. COSMOFON A.D. 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.

RE: Need Help, Sending 7bit default alphabet specified by GSM 03.38

2008-02-21 Thread Davor Spasoski

Just set coding=0 and alt-dcs=1 and url encode the characters according to the 
GSM 03.38 charset. Try the url encoding manually at first, then build a script 
that will do the job for you.

Davor Spasoski



Tel: +389 76 411 056; +389 2 2441 056
Mob: + 389 75 400 608
www.cosmofon.com.mk

-Original Message-
From: Michael Bochkaryov [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 21, 2008 9:44 AM
To: [EMAIL PROTECTED]
Cc: users@kannel.org
Subject: Re: Need Help, Sending 7bit default alphabet specified by GSM 03.38

[EMAIL PROTECTED] wrote:
 Hi,

   I would like to know how to send a full set of 7bit aphabet in kannel
 without the need of sending it in unicode character.

[table skipped]

 The above table is a complete set of  7bit default alphabet specified by
 GSM 03.38 . Was this mean i would be able to send this alphabet by just
 setting coding=1?

No. It's for binaries.

 Cost i been failed to do so in some of the aphabet above
 was is because of my encoding problem? i been using php urlencode function
 in encoding the text message b4 being send to kannel.

Try to specify also charset of string you send to kannel.
For example you can send coding=0charset=ISO-8859-1 parameters.

AFAIK kannel uses windows-1252 charset as default for 7-bit.

 Regards,
 SoNG


--
Michael Bochkaryov


COSMOFON - Mobile Telecommunications Services - A.D. 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. COSMOFON A.D. 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.

RE: Special Characters and Kannel 1.4.1

2008-02-21 Thread Davor Spasoski

From my experience I can tell you than the SMSCs supports only a small number 
of alphabets, usually GSM and UCS-2. Even if your phone supports the 
ISO-8859-1 the SMSC will try to convert the characters to the supported 
alphabets and you will have a mismatch. Some SMSCs installed in countries not 
using Latin may even use other default encodings.
My advice is to stick to GSM alphabet or UCS-2

Davor Spasoski



-Original Message-
From: Songhh [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 21, 2008 11:43 AM
To: users@kannel.org
Subject: Re: Special Characters and Kannel 1.4.1


Hi,

Can i know how u encode ur text ABCDäöüÄÖÜß to become ISO-8859-1 encoded
ABCD%e4%f6%fc%c4%d6%dc%df ?


Markus R. wrote:

 Hi,

 I have a problem sending special characters in mobile terminated
 messages through Kannel.

 The Setup: Debian (Sarge), Kannel 1.4.1 (from .deb packages), libxml
 2.6.16-7

 SMSC: Vodafone Germany, EMI


 The Problem: I want to send the following test message: ABCDäöüÄÖÜß

 Each time I send this message I receive ABCDäößÄÖ§ñ on the mobile phone.

 Here are my requests to kannel:

 ISO-8859-1 encoded:
 http://SERVER:PORT/cgi-bin/sendsms?user=USERpassword=PASSto=RECIPIENTtext=ABCD%e4%f6%fc%c4%d6%dc%dfcharset=ISO-8859-1from=SHORTNUMBER

 smsbox.log says:
 2007-04-03 11:23:49 [762] [3] INFO: sendsms
 sender:smsSender:SHORTNUMBER (IPADDRESS) to:RECIPIENT
 msg:ABCDäöüÄÖÜß

 This at least tells me that the characters are transmitted to kannel
 correctly but on the mobile I receive ABCDäößÄÖ§ñ

 If I send the following UTF-8 encoded request:
 http://SERVER:PORT/cgi-bin/sendsms?user=USERpassword=PASSto=RECIPIENTtext=ABCD%c3%a4%c3%b6%c3%bc%c3%84%c3%96%c3%9c%c3%9fcharset=UTF-8from=SHORTNUMBER

 smsbox.log says:
 2007-04-03 11:29:12 [762] [3] INFO: sendsms
 sender:smsSender:SHORTNUMBER (IPADDRESS) to:RECIPIENT
 msg:ABCDÃ¤Ã¶Ã¼Ã84Ã96Ã9CÃ9F

 The Mobile still receives ABCDäößÄÖ§ñ

 It is interesting that at least ö, ä, Ö and Ä pass through correctly.

 How can I find out, why ü, Ü and ß get garbled?

 Regards,

 Markus




--
View this message in context: 
http://www.nabble.com/Special-Characters-and-Kannel-1.4.1-tp9807411p15607269.html
Sent from the Kannel - User mailing list archive at Nabble.com.



COSMOFON - Mobile Telecommunications Services - A.D. 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. COSMOFON A.D. 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.

RE: Kannel 1.4.1-2 Greek Character Set

2008-01-15 Thread Davor Spasoski

Aha, then it might be the SMSC or the the handset. Have you tried another
handset? What SMSC are you connecting to?
I'm using kannel 1.3.1. Last thing I could suggest is to explicitly set
coding=1  in the URL and try another handset.

BR,

Davor Spasoski 

-Original Message-
From: Joe Perry [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, January 15, 2008 11:50 AM
To: Davor Spasoski; users@kannel.org
Subject: Re: Kannel 1.4.1-2 Greek Character Set

Hi,

Tried this and the phone is just returning question marks (??) for each 
of the greek characters. I have just installed the latest CVS (Kannel 
bearerbox version `cvs-20080109'). My URL is the same as what you posted 
also.

Could there be anything else that is effecting this?

Thanks,


Davor Spasoski wrote:
 Hi Joe,

 Your encoding is wrong. Please use the link I gave you for the encoding
 table. Your ΗΕΛΛΟ phrase should be encoded as %48%45%14%14%4F and the
entire
 URL should look something like:


http://localhost:4004/cgi-bin/sendms?user=foopassword=barfrom=Joeto=x
 xalt-dcs=1text=%48%45%14%14%4F

 Try posting this from your browser and it should work.My advice for you is
 to stick to GSM alphabet and use Greek capital letters because all
handsets
 support the GSM alphabet, whereas the complete UTF is much more rarely
 supported.

 Davor Spasoski 

 Value Added Services Engineering Group Leader
 Core Network  Services Department
 Technical Division



 Tel: +389 76 411 056; +389 2 2441 056 
 Mob: + 389 75 400 608 
 www.cosmofon.com.mk 


 -Original Message-
 From: Joe Perry [mailto:[EMAIL PROTECTED] 
 Sent: Monday, January 14, 2008 5:18 PM
 To: Davor Spasoski; users@kannel.org
 Subject: Re: Kannel 1.4.1-2 Greek Character Set

 Hi Davor and thanks for the response,

 I have tried what you have explained but have so far failed to have much 
 luck.

 I am attempting to send the phrase ΗΕΛΛΟ. Through my hex conversions, 
 the actual body of the message being sent through HTTP to the smsbox is 
 %CE%97%CE%95%CE%9B%CE%9B%CE%9F.

 The phone however is only displaying what appears to be |?|?|?|?|?.

 Any idea what might be occuring here?

 Thanks,

 Davor Spasoski wrote:
   
 Basically, you have two ways of sending Greek alphabet, either using the
 UTF-8 or by using Greek capital which are part of the default GSM
 
 encoding.
   
 If you use the second method, which have the 160 characters per SMS
 advantage over UTF-8, try setting alt-dcs=1 that will guarantee using the
 default GSM encoding. Also make sure you actually encode those characters
 properly by using its appropriate hex code
 (http://www.visualtron.com/bit_default_alphabet.htm ), not by just typing
 those characters in Windows (UTF-8)

 BTW, this works for sure, I tried this.

 Davor Spasoski 


 -Original Message-
 From: Joe Perry [mailto:[EMAIL PROTECTED] 
 Sent: Monday, January 14, 2008 1:51 PM
 To: users@kannel.org
 Subject: Kannel 1.4.1-2 Greek Character Set

 Hi there,

 Been reading up on this but still yet to find any fixes that has 
 successfully worked for me.

 I am posting my message (UTF-8) to the smsbox using HTTP, but once the 
 message reaches the phone certain characters are converted to strange 
 combinations of characters.

 For example, I can send a plain english message perfectly and the phone 
 will receive it as it should. However, once I start using greek 
 characters which are inside the default GSM alphabet the message which 
 is delivered to the phone becomes corrupt and appears not as it 
 perhaps should.

 Is there a fix that any of you know to help me with this problem, or can 
 explain where I am going wrong?

 Thanks



 COSMOFON - Mobile Telecommunications Services - A.D. 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. COSMOFON A.D. 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.
   

   
 



 COSMOFON - Mobile Telecommunications Services - A.D. 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

RE: Message Queue Full causes sms to be sent to smsc repeatedly manytimes a second

2008-01-14 Thread Davor Spasoski

Hi Tomer,



Long time ago I had this problem. You should disable resending of the SMS in
case of message queue full because it makes no sense. The SMSC will not let
you and mobile originated SMS to be queued to the B-party until B-party is
attached again and pulls all the messages. And god knows when and if it will
happen. You have to do the following changes:



smsc_smpp.c


...

static long smpp_status_to_smscconn_failure_reason(long status)
{
switch(status) {
/* case SMPP_ESME_RMSGQFUL:
return SMSCCONN_FAILED_TEMPORARILY;
break;

case SMPP_ESME_RTHROTTLED:
return SMSCCONN_FAILED_TEMPORARILY;
break; */

default:
return SMSCCONN_FAILED_REJECTED;
}
}


.



Cheers!


COSMOFON - Mobile Telecommunications Services - A.D. 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. COSMOFON A.D. 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.

RE: Kannel 1.4.1-2 Greek Character Set

2008-01-14 Thread Davor Spasoski

Basically, you have two ways of sending Greek alphabet, either using the
UTF-8 or by using Greek capital which are part of the default GSM encoding.
If you use the second method, which have the 160 characters per SMS
advantage over UTF-8, try setting alt-dcs=1 that will guarantee using the
default GSM encoding. Also make sure you actually encode those characters
properly by using its appropriate hex code
(http://www.visualtron.com/bit_default_alphabet.htm ), not by just typing
those characters in Windows (UTF-8)

BTW, this works for sure, I tried this.

Davor Spasoski 


-Original Message-
From: Joe Perry [mailto:[EMAIL PROTECTED] 
Sent: Monday, January 14, 2008 1:51 PM
To: users@kannel.org
Subject: Kannel 1.4.1-2 Greek Character Set

Hi there,

Been reading up on this but still yet to find any fixes that has 
successfully worked for me.

I am posting my message (UTF-8) to the smsbox using HTTP, but once the 
message reaches the phone certain characters are converted to strange 
combinations of characters.

For example, I can send a plain english message perfectly and the phone 
will receive it as it should. However, once I start using greek 
characters which are inside the default GSM alphabet the message which 
is delivered to the phone becomes corrupt and appears not as it 
perhaps should.

Is there a fix that any of you know to help me with this problem, or can 
explain where I am going wrong?

Thanks



COSMOFON - Mobile Telecommunications Services - A.D. 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. COSMOFON A.D. 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.

Kannel and SIM toolkit

2007-08-13 Thread Davor Spasoski

Hi,

 

Has anybody managed to successfully send SMS to Sim Toolkit WIB
(microbrowser)? I'm trying as explained in the 1.3.1 manual

and sending a Hello World like this:

 

http://localhost:4004/cgi-bin/sendsms?user=XXXpassword=XXXfrom=XXXto=
XXtext=%80%C2%00%00%47%D1%45%82%02%83%81%86%07%91%91%71%09%57%22%F0%8B%36%4
4%03%81%11%F2%7F%F6%00%00%00%00%00%00%00%27%02%70%00%00%22%0D%00%04%00%00%00
%00%01%00%00%00%00%00%00%00%12%02%0C%48%65%6C%6C%6F%2C%20%77%6F%72%6C%64%06%
00%06%00mclass=3coding=2pid=127alt-dcs=1 

 

but the handset does not receive anything. SMSC asserts Error in mobile
station.

 

Davor

 


COSMOFON - Mobile Telecommunications Services - A.D. 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. COSMOFON A.D. 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.

RE: Working configuration for wap push

2007-05-30 Thread Davor Spasoski

Correction: Trying to send to localhost:8080/cgi-bin/wap-push gives:

 

Unable to connect to remote host.

 

Davor Spasoski

VAS Engineering Group Leader

Cosmofon

 

  _  

From: Davor Spasoski 
Sent: Monday, May 28, 2007 11:26 AM
To: 'users@kannel.org'
Subject: Working configuration for wap push

 

Hi,

 

I'm trying to make kannel 1.3.1 work as PPG using the configuration below. I
used this version for long as sms gateway and it worked fine with the config
below.

Adding the PPG core group and WAP push user does not seem to work. 

netstat -an | grep 8080 gives:

tcp1  0 172.20.106.100:40860172.20.1.30:8080
CLOSE_WAIT

 

and sending wap-push message to localhost:8080/cgi-bin/wap-push.cgi

gives

 Unknown request

 

Am I missing something?

 

#===
===

# 1. Bearerbox configuration

#===
===

group = core

admin-port = 4000

smsbox-port = 4001

admin-password = gwyadmin

status-password = gwyadmin

box-allow-ip = *.*.*.*

unified-prefix = 

log-file = bearerbox.log

log-level = 1

access-log = access.log

store-file = kannel.store

dlr-storage = internal

#===
===

 

#===
===

# 2. SMS centre connection

#===
===

group = smsc

smsc = smpp

host = 172.20.207.107

smsc-id = smsc1a

port = 3705

receive-port = 3705

transceiver-mode = 0

smsc-username = iq

smsc-password = iq

system-type =VMA

address-range = 

source-addr-ton = 0

source-addr-npi = 1

dest-addr-ton = 0

dest-addr-npi = 1

interface-version = 34

enquire-link-interval = 15

reconnect-delay = 30

msg-id-type = 1

#===
===

 

#===
===

# 3. Definition of the SMS box

#===
===

group = smsbox

smsbox-id = smsbox1

bearerbox-host = localhost

sendsms-port = 4004

sendsms-chars = 0123456789 +-

access-log = smsboxaccess.log

mo-recode = 1

#===
===

 

#===
===

# 3. SMS box routing

#===
===

group = smsbox-route

smsbox-id = smsbox1

smsc-ids = smsc1a

#===
===

 

#===
===

# 4. Definition of PPG core group for Push Initiator (PI)

#===
===

group = ppg

ppg-url = /cgi-bin/wap-push.cgi

ppg-port = 8080

concurrent-pushes = 100

trusted-pi = false

users = 1024

ppg-allow-ip = *.*.*.*

#===
===

 

#===
===

# 4.1 WAP Push user

#===
===

group = wap-push-user

wap-push-user = test

ppg-username = test

ppg-password = test

#===
===

 

#===
===

# 5. SEND-SMS USERS

#===
===

group = sendsms-user

username = bulk

password = bulk

user-allow-ip = *.*.*.*

forced-smsc = smsc1a

max-messages = 10

concatenation = 1

 

Davor Spasoski

VAS Engineering Group Leader

Cosmofon

 


COSMOFON - Mobile Telecommunications Services - A.D. 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. COSMOFON A.D. 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.

Working configuration for wap push

2007-05-30 Thread Davor Spasoski

Hi,

 

I'm trying to make kannel 1.3.1 work as PPG using the configuration below. I
used this version for long as sms gateway and it worked fine with the config
below.

Adding the PPG core group and WAP push user does not seem to work. 

netstat -an | grep 8080 gives:

tcp1  0 172.20.106.100:40860172.20.1.30:8080
CLOSE_WAIT

 

and sending wap-push message to localhost:8080/cgi-bin/wap-push.cgi

gives

 Unknown request

 

Am I missing something?

 

#===
===

# 1. Bearerbox configuration

#===
===

group = core

admin-port = 4000

smsbox-port = 4001

admin-password = gwyadmin

status-password = gwyadmin

box-allow-ip = *.*.*.*

unified-prefix = 

log-file = bearerbox.log

log-level = 1

access-log = access.log

store-file = kannel.store

dlr-storage = internal

#===
===

 

#===
===

# 2. SMS centre connection

#===
===

group = smsc

smsc = smpp

host = 172.20.207.107

smsc-id = smsc1a

port = 3705

receive-port = 3705

transceiver-mode = 0

smsc-username = iq

smsc-password = iq

system-type =VMA

address-range = 

source-addr-ton = 0

source-addr-npi = 1

dest-addr-ton = 0

dest-addr-npi = 1

interface-version = 34

enquire-link-interval = 15

reconnect-delay = 30

msg-id-type = 1

#===
===

 

#===
===

# 3. Definition of the SMS box

#===
===

group = smsbox

smsbox-id = smsbox1

bearerbox-host = localhost

sendsms-port = 4004

sendsms-chars = 0123456789 +-

access-log = smsboxaccess.log

mo-recode = 1

#===
===

 

#===
===

# 3. SMS box routing

#===
===

group = smsbox-route

smsbox-id = smsbox1

smsc-ids = smsc1a

#===
===

 

#===
===

# 4. Definition of PPG core group for Push Initiator (PI)

#===
===

group = ppg

ppg-url = /cgi-bin/wap-push.cgi

ppg-port = 8080

concurrent-pushes = 100

trusted-pi = false

users = 1024

ppg-allow-ip = *.*.*.*

#===
===

 

#===
===

# 4.1 WAP Push user

#===
===

group = wap-push-user

wap-push-user = test

ppg-username = test

ppg-password = test

#===
===

 

#===
===

# 5. SEND-SMS USERS

#===
===

group = sendsms-user

username = bulk

password = bulk

user-allow-ip = *.*.*.*

forced-smsc = smsc1a

max-messages = 10

concatenation = 1

 

Davor Spasoski

VAS Engineering Group Leader

Cosmofon

 


COSMOFON - Mobile Telecommunications Services - A.D. 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. COSMOFON A.D. 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.

working wap push configuration

2007-05-30 Thread Davor Spasoski

Can somebody please send a working configuration of WAP Push gateway and
explain the environment a bit more. I'm trying to work this out, but no
listener starts on port 8080 when I run the bearerbox and smsbox.



dspasoski




COSMOFON - Mobile Telecommunications Services - A.D. 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. COSMOFON A.D. 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.

RE: Getting real IP address of the handset

2007-04-20 Thread Davor Spasoski

Thank you Stipe,

Yes, that's the header, however it only gives the IP address of the
firewall, as it is masquerading the private IP addresses of the handset.
I was told by the operator that they include the IP address in the cookie
headers appended by Ericsson MIEP (some proxy) to any cookie of the HTTP
server. Don't know what this means, but here's an example they gave me:

 cookie:

$Version=0;User-Identity-Forward-msisdn=333036393734333533353634;

User-Identity-Forward-userid=3734333533353634;

User-Identity-Authentication=Bearer;

ip-address=10.10.10.132;

Bearer-Type=w-TCP;

wtls-security-level=none;

network-access-type=CSD;

nas-ip-address=192.168.254.1;

Called-station-id=35303030303030;

accounting-session-id=00514BFB


Davor Spasoski


-Original Message-
From: Stipe Tolj [mailto:[EMAIL PROTECTED] 
Sent: Thursday, April 19, 2007 2:09 PM
To: Davor Spasoski
Cc: users@kannel.org
Subject: Re: Getting real IP address of the handset

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi Davor,

Davor Spasoski wrote:

 I started testing the WAP gateway. My problem is that I cannot get the IP
 address of the mobile handset by invoking any of the following http
headers:
 
 $_SERVER[HTTP_CLIENT_IP]
 
 $_SERVER[REMOTE_ADDR];

ok, these are obviously PHP code segments you use here ;)

 I always get back the IP address of the machine where the Kannel is
running.
 Is there any setting on kannel to solve this problem?

as you try to get the client IP of the mobile that is accessing your HTTP
server, you will see for REMOTE_ADDR of course the IP of the machine running
Kannel.

What you need is to look for a specific HTTP header that is used by Kannel
to
proxy the mobile client IP to the application layer.

This is HTTP header: X-WAP-Network-Client-IP

I don't recall it now, otherwise I would tell, but you simply need to figure
out
in PHP how to obtain the HTTP header with the above name while the requests
is
processed, then you get the client IP.

Stipe

- ---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany

tolj.org system architecture  Kannel Software Foundation (KSF)
http://www.tolj.org/  http://www.kannel.org/

mailto:st_{at}_tolj.org   mailto:stolj_{at}_kannel.org
- ---
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGJ1vy9ez0oeKvYs0RAgelAJ0UGdb/+wHegrejlEaxKYHl1D3oEACfW13a
jDeSNRUVTXAG3dhhvVzH6Es=
=1sNq
-END PGP SIGNATURE-


COSMOFON - Mobile Telecommunications Services - A.D. 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. COSMOFON A.D. 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.

RE: Getting real IP address of the handset

2007-04-20 Thread Davor Spasoski

Hi Juan,

Thank you for your proposal. I tried it, but the firewall is doing
masquerading and I can't get the real IP address.
I was told that a proxy server called MIAP is appending some cookie headers
to any cookie of the HTTP server. The ip address is contained there. I don't
really know what they exactly mean by this and what mechanism to build to
acquire the cookie headers.

Thanks for helping

Davor Spasoski
VAS Engineering Group Leader
Cosmofon


-Original Message-
From: Juan Nin [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 19, 2007 4:09 PM
To: Stipe Tolj
Cc: Davor Spasoski; users@kannel.org
Subject: Re: Getting real IP address of the handset

Stipe Tolj wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Hi Davor,

 Davor Spasoski wrote:


 I started testing the WAP gateway. My problem is that I cannot get the IP
 address of the mobile handset by invoking any of the following http
headers:

 $_SERVER[HTTP_CLIENT_IP]

 $_SERVER[REMOTE_ADDR];


 ok, these are obviously PHP code segments you use here ;)


 I always get back the IP address of the machine where the Kannel is
running.
 Is there any setting on kannel to solve this problem?


 as you try to get the client IP of the mobile that is accessing your HTTP
 server, you will see for REMOTE_ADDR of course the IP of the machine
running
 Kannel.

 What you need is to look for a specific HTTP header that is used by Kannel
to
 proxy the mobile client IP to the application layer.

 This is HTTP header: X-WAP-Network-Client-IP

 I don't recall it now, otherwise I would tell, but you simply need to
figure out
 in PHP how to obtain the HTTP header with the above name while the
requests is
 processed, then you get the client IP.

 Stipe

 -
then it should appear in $_SERVER['X-WAP-NETWORK-CLIENT-IP']

if not you can use print_r($_SERVER) to see all headers  :)

Regards,

Juan


COSMOFON - Mobile Telecommunications Services - A.D. 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. COSMOFON A.D. 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.

Getting real IP address of the handset

2007-04-18 Thread Davor Spasoski

Hi,



I started testing the WAP gateway. My problem is that I cannot get the IP
address of the mobile handset by invoking any of the following http headers:



$_SERVER[HTTP_CLIENT_IP]

$_SERVER[REMOTE_ADDR];



I always get back the IP address of the machine where the Kannel is running.
Is there any setting on kannel to solve this problem?



BR,



Davor Spasoski




COSMOFON - Mobile Telecommunications Services - A.D. 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. COSMOFON A.D. 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.

91 matches

Mail list logo