Re: Inverted Exclamation mark and question mark issue.

Fri, 06 Apr 2018 04:03:01 -0700

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 <md.a...@forest-interactive.com> 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&password=smsPass&from=68888&to=601132495424&text=%C2%A1&coding=0

curl http://localhost:13017/cgi-bin/sendsms?username=smsSMPP2&password=smsPass&from=68888&to=601132495424&text=%C2%A1&charset=UTF-8

curl http://localhost:13017/cgi-bin/sendsms?username=smsSMPP2&password=smsPass&from=68888&to=601132495424&text=%A1&charset=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 = 0x00000004

2018-04-05 10:21:02 [16025] [7] DEBUG:   command_status: 0 = 0x00000000

2018-04-05 10:21:02 [16025] [7] DEBUG:   sequence_number: 31 = 0x0000001f

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 = 0x00000000

2018-04-05 10:21:02 [16025] [7] DEBUG:   source_addr_npi: 1 = 0x00000001

2018-04-05 10:21:02 [16025] [7] DEBUG:   source_addr: "68888"

2018-04-05 10:21:02 [16025] [7] DEBUG:   dest_addr_ton: 1 = 0x00000001

2018-04-05 10:21:02 [16025] [7] DEBUG:   dest_addr_npi: 1 = 0x00000001

2018-04-05 10:21:02 [16025] [7] DEBUG:   destination_addr: "601132495424"

2018-04-05 10:21:02 [16025] [7] DEBUG:   esm_class: 3 = 0x00000003

2018-04-05 10:21:02 [16025] [7] DEBUG:   protocol_id: 0 = 0x00000000

2018-04-05 10:21:02 [16025] [7] DEBUG:   priority_flag: 0 = 0x00000000

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 = 0x00000000

2018-04-05 10:21:02 [16025] [7] DEBUG:   replace_if_present_flag: 0 = 0x00000000

2018-04-05 10:21:02 [16025] [7] DEBUG:   data_coding: 0 = 0x00000000

2018-04-05 10:21:02 [16025] [7] DEBUG:   sm_default_msg_id: 0 = 0x00000000

2018-04-05 10:21:02 [16025] [7] DEBUG:   sm_length: 1 = 0x00000001

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&password=smsPass&from=68888&to=601132495424&text=%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 = 0x00000004

2018-04-05 10:54:07 [16129] [7] DEBUG:   command_status: 0 = 0x00000000

2018-04-05 10:54:07 [16129] [7] DEBUG:   sequence_number: 56 = 0x00000038

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 = 0x00000000

2018-04-05 10:54:07 [16129] [7] DEBUG:   source_addr_npi: 1 = 0x00000001

2018-04-05 10:54:07 [16129] [7] DEBUG:   source_addr: "68888"

2018-04-05 10:54:07 [16129] [7] DEBUG:   dest_addr_ton: 1 = 0x00000001

2018-04-05 10:54:07 [16129] [7] DEBUG:   dest_addr_npi: 1 = 0x00000001

2018-04-05 10:54:07 [16129] [7] DEBUG:   destination_addr: "601132495424"

2018-04-05 10:54:07 [16129] [7] DEBUG:   esm_class: 3 = 0x00000003

2018-04-05 10:54:07 [16129] [7] DEBUG:   protocol_id: 0 = 0x00000000

2018-04-05 10:54:07 [16129] [7] DEBUG:   priority_flag: 0 = 0x00000000

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 = 0x00000000

2018-04-05 10:54:07 [16129] [7] DEBUG:   replace_if_present_flag: 0 = 0x00000000

2018-04-05 10:54:07 [16129] [7] DEBUG:   data_coding: 0 = 0x00000000

2018-04-05 10:54:07 [16129] [7] DEBUG:   sm_default_msg_id: 0 = 0x00000000

2018-04-05 10:54:07 [16129] [7] DEBUG:   sm_length: 13 = 0x0000000d

2018-04-05 10:54:07 [16129] [7] DEBUG:   short_message:

2018-04-05 10:54:07 [16129] [7] DEBUG:    Octet string at 0x7f09c8000c70:

2018-04-05 10:54:07 [16129] [7] DEBUG:      len:  13

2018-04-05 10:54:07 [16129] [7] DEBUG:      size: 27

2018-04-05 10:54:07 [16129] [7] DEBUG:      immutable: 0

2018-04-05 10:54:07 [16129] [7] DEBUG:      data: 24 40 5b 5c 5d 5e 5f 60 7b 7c 7d 7e 7f            $@[\]^_`{|}~.

2018-04-05 10:54:07 [16129] [7] DEBUG:    Octet string dump ends.

2018-04-05 10:54:07 [16129] [7] DEBUG: SMPP PDU dump ends.

 

Kindly do let me know if there’s anything else that I can try, appreciate it.

 

Regards

Arif Noor

 

From: Alexander Malysh <malys...@gmail.com> On Behalf Of amal...@kannel.org
Sent: Wednesday, April 04, 2018 11:46 PM
To: Wan Md Arif Noor Bin. Wan Nizam <md.a...@forest-interactive.com>
Cc: users@kannel.org
Subject: Re: Inverted Exclamation mark and question mark issue.

 

This is in most cases wrong:

 

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.

 

You are sending as UTF-8. Please align your alt-charset with a smsc default charset.

 

dest-addr-ton = 1

dest-addr-npi = 1

interface-version = 52

throughput = 15

alt-charset = "utf-8"

                        ^^^^^^^^^

 

Thanks,

Alex

 

 

 



Am 04.04.2018 um 12:24 schrieb Wan Md Arif Noor Bin. Wan Nizam <md.a...@forest-interactive.com>:

 

Hi There,

 

Thanks for replying, I already tested using that parameter, but I keep receiving “B?”.

Below are the debug log.

 

 

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 = 0x00000004

2018-04-04 17:17:39 [10745] [7] DEBUG:   command_status: 0 = 0x00000000

2018-04-04 17:17:39 [10745] [7] DEBUG:   sequence_number: 56414 = 0x0000dc5e

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 = 0x00000000

2018-04-04 17:17:39 [10745] [7] DEBUG:   source_addr_npi: 1 = 0x00000001

2018-04-04 17:17:39 [10745] [7] DEBUG:   source_addr: "68888"

2018-04-04 17:17:39 [10745] [7] DEBUG:   dest_addr_ton: 1 = 0x00000001

2018-04-04 17:17:39 [10745] [7] DEBUG:   dest_addr_npi: 1 = 0x00000001

2018-04-04 17:17:39 [10745] [7] DEBUG:   destination_addr: "601132495424"

2018-04-04 17:17:39 [10745] [7] DEBUG:   esm_class: 3 = 0x00000003

2018-04-04 17:17:39 [10745] [7] DEBUG:   protocol_id: 0 = 0x00000000

2018-04-04 17:17:39 [10745] [7] DEBUG:   priority_flag: 0 = 0x00000000

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 = 0x00000000

2018-04-04 17:17:39 [10745] [7] DEBUG:   replace_if_present_flag: 0 = 0x00000000

2018-04-04 17:17:39 [10745] [7] DEBUG:   data_coding: 0 = 0x00000000

2018-04-04 17:17:39 [10745] [7] DEBUG:   sm_default_msg_id: 0 = 0x00000000

2018-04-04 17:17:39 [10745] [7] DEBUG:   sm_length: 2 = 0x00000002

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 <malys...@gmail.com> On Behalf Of amal...@kannel.org
Sent: Wednesday, April 04, 2018 4:40 PM
To: Wan Md Arif Noor Bin. Wan Nizam <md.a...@forest-interactive.com>
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&coding=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 <md.a...@forest-interactive.com>:

 

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.

 

 

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 = ""

access-log = /opt/kannel/smpp_access.log

access-log-format = "[SMSC:%i] [from:%p] [to:%P] [msg:%L:%b] [FID:%F]"

store-type = file

store-location = "/opt/kannel/smpp.store"

store-dump-freq = 100

 

group = smsbox

bearerbox-host = 127.0.0.1

sendsms-port = 13017

http-request-retry = 3

http-queue-delay = 5

reply-couldnotfetch = "Please wait"

log-file = "/opt/kannel/smsbox/smsbox.log"

log-level = 0

 

group = smsc

smsc = smpp

smsc-id = smppConnection2

allowed-smsc-id = "smppConnection2"

host =

port =

system-type = ""

address-range = "1234"

smsc-username = ""

smsc-password = ""

source-addr-ton = 0

source-addr-npi = 1

dest-addr-ton = 1

dest-addr-npi = 1

interface-version = 52

throughput = 15

alt-charset = "utf-8"

connection-timeout = 60

max-pending-submits = 10

enquire-link-interval = 20

transceiver-mode = 0

log-file = "/opt/kannel/bearerbox/debug.log"

log-level = 0

reconnect-delay = 2

 

group = sendsms-user

username = smsSMPP2

password = smsPass

max-messages  = 10

concatenation = true

default-smsc = smppConnection2

 

group = sms-service

keyword = default

accepted-smsc = smppConnection2

get-url = "">

max-messages = 0

  concatenation = true

 




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!

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

Reply via email to