Re: message split in SUBMIT_SM pdu due to extended GSM characters
Please take a look at the PDU dump below. It seems that these
characters are counted as occupying 2 bytes and yet we are using
ASCII:
2009-10-01 11:18:52 [9435] [7] DEBUG: type_name: submit_sm
2009-10-01 11:18:52 [9435] [7] DEBUG: command_id: 4 = 0x0004
2009-10-01 11:18:52 [9435] [7] DEBUG: command_status: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: sequence_number: 1775 = 0x06ef
2009-10-01 11:18:52 [9435] [7] DEBUG: service_type: 6502
2009-10-01 11:18:52 [9435] [7] DEBUG: source_addr_ton: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: source_addr_npi: 1 = 0x0001
2009-10-01 11:18:52 [9435] [7] DEBUG: source_addr: 6502
2009-10-01 11:18:52 [9435] [7] DEBUG: dest_addr_ton: 1 = 0x0001
2009-10-01 11:18:52 [9435] [7] DEBUG: dest_addr_npi: 1 = 0x0001
2009-10-01 11:18:52 [9435] [7] DEBUG: destination_addr: 250789112112
2009-10-01 11:18:52 [9435] [7] DEBUG: esm_class: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: protocol_id: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: priority_flag: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: schedule_delivery_time: NULL
2009-10-01 11:18:52 [9435] [7] DEBUG: validity_period: NULL
2009-10-01 11:18:52 [9435] [7] DEBUG: registered_delivery: 1 = 0x0001
2009-10-01 11:18:52 [9435] [7] DEBUG: replace_if_present_flag: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: data_coding: 0 = 0x
-- default coding (ASCII)
2009-10-01 11:18:52 [9435] [7] DEBUG: sm_default_msg_id: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: sm_length: 80 = 0x0050
2009-10-01 11:18:52 [9435] [7] DEBUG: short_message:
2009-10-01 11:18:52 [9435] [7] DEBUG:Octet string at 0x9360ed0:
2009-10-01 11:18:52 [9435] [7] DEBUG: len: 80
2009-10-01 11:18:52 [9435] [7] DEBUG: size: 81
2009-10-01 11:18:52 [9435] [7] DEBUG: immutable: 0
2009-10-01 11:18:52 [9435] [7] DEBUG: data: 7b 7d 7b 7d 7b 7d 7b
7d 7b 7d 7b 7d 7b 7d 7b 7d {}{}{}{}{}{}{}{}
2009-10-01 11:18:52 [9435] [7] DEBUG: data: 7b 7d 7b 7d 7b 7d 7b
7d 7b 7d 7b 7d 7b 7d 7b 7d {}{}{}{}{}{}{}{}
2009-10-01 11:18:52 [9435] [7] DEBUG: data: 7b 7d 7b 7d 7b 7d 7b
7d 7b 7d 7b 7d 7c 7c 7c 7c {}{}{}{}{}{}
2009-10-01 11:18:52 [9435] [7] DEBUG: data: 7c 7c 7c 7c 7c 7c 7c
7c 7b 7d 7b 7d 7b 7d 7b 7d {}{}{}{}
2009-10-01 11:18:52 [9435] [7] DEBUG: data: 7b 7d 7b 7d 7b 7d 7b
7d 7b 7d 7b 7d 7b 7d 7b 7d {}{}{}{}{}{}{}{}
2009-10-01 11:18:52 [9435] [7] DEBUG:Octet string dump ends.
2009-10-01 11:18:52 [9435] [7] DEBUG: SMPP PDU dump ends.
...(split occurs here and the second part is sent out)
2009-10-01 11:18:52 [9435] [7] DEBUG: SMPP[MAGPIE1]: Sending PDU:
2009-10-01 11:18:52 [9435] [7] DEBUG: SMPP PDU 0x936a260 dump:
2009-10-01 11:18:52 [9435] [7] DEBUG: type_name: submit_sm
2009-10-01 11:18:52 [9435] [7] DEBUG: command_id: 4 = 0x0004
2009-10-01 11:18:52 [9435] [7] DEBUG: command_status: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: sequence_number: 1776 = 0x06f0
2009-10-01 11:18:52 [9435] [7] DEBUG: service_type: 6502
2009-10-01 11:18:52 [9435] [7] DEBUG: source_addr_ton: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: source_addr_npi: 1 = 0x0001
2009-10-01 11:18:52 [9435] [7] DEBUG: source_addr: 6502
2009-10-01 11:18:52 [9435] [7] DEBUG: dest_addr_ton: 1 = 0x0001
2009-10-01 11:18:52 [9435] [7] DEBUG: dest_addr_npi: 1 = 0x0001
2009-10-01 11:18:52 [9435] [7] DEBUG: destination_addr: 250789112112
2009-10-01 11:18:52 [9435] [7] DEBUG: esm_class: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: protocol_id: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: priority_flag: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: schedule_delivery_time: NULL
2009-10-01 11:18:52 [9435] [7] DEBUG: validity_period: NULL
2009-10-01 11:18:52 [9435] [7] DEBUG: registered_delivery: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: replace_if_present_flag: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: data_coding: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: sm_default_msg_id: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: sm_length: 80 = 0x0050
2009-10-01 11:18:52 [9435] [7] DEBUG: short_message:
2009-10-01 11:18:52 [9435] [7] DEBUG:Octet string at 0x936d0f8:
2009-10-01 11:18:52 [9435] [7] DEBUG: len: 80
2009-10-01 11:18:52 [9435] [7] DEBUG: size: 81
2009-10-01 11:18:52 [9435] [7] DEBUG: immutable: 0
2009-10-01 11:18:52 [9435] [7] DEBUG: data: 7b 7d 7b 7d 7b 7d 7b
7d 7b 7d 7b 7d 7b 7d 7c 7c {}{}{}{}{}{}{}||
2009-10-01 11:18:52 [9435] [7] DEBUG: data: 7c 7c 7c 7c 7c 7c 7c
7c 7c 7c 7c 7c 7c 7c 7c 7c
2009-10-01 11:18:52 [9435] [7] DEBUG: data: 7c 7c 7c 7c 7c 7c 7c
7c 7c 7c 7c 7c 7c 7c 7c 7c
2009-10-01 11:18:52 [9435] [7] DEBUG: data: 7c 7c 7c 7c 7c 7c 7c
7c 7c 7c 7c 7c 7c 7c 7c 7c
2009-10-01 11:18:52 [9435]
map-url
Hi list , i am using mbuni for sending the mms message with help of kannel .i think the connection between kannel adn mbuni is the map-url in the wap-box group .like that given the in the mbuni user guide .according to that i configured and run the both mbuni ,kannel and both are started successfully .but when i run the wapbox it was giving some warning and both are not communicated .can any one pls give me some solution for my problem. here is my config file . group = core admin-port = 13004 admin-password = bar log-file = log/bearer.log log-level = 0 access-log = log/beareraccess.log smsbox-port = 13002 store-file = log/kannelqueue.log wapbox-port=13013 wdp-interface-name=* box-allow-ip = 127.0.0.1,172.22.25.175 # SMSC SMPP group = smsc smsc = smpp smsc-id = SMPPSim host = 172.22.25.175 port = 2775 log-file = log/kannel.log transceiver-mode = 1 alt-dcs = true smsc-username = smppclient smsc-password = password system-type = address-range = source-addr-ton = 1 source-addr-npi = 1 dest-addr-ton = 1 dest-addr-npi = 1 msg-id-type = 0x01 throughput = 50 max-pending-submits = 1 enquire-link-interval= 60 # SMSBOX SETUP group = smsbox bearerbox-host = localhost sendsms-port = 13006 log-file = log/smsbox.log log-level = 0 access-log = log/smsboxaccess.log # SEND-SMS USERS group = sendsms-user username = pyro1 password = pyro1 max-messages = 50 concatenation = true # SMS-Service group = sms-service keyword = www text = Website found!!! # SMS-Service group = sms-service keyword = default text = Reply from ESME #group = wapbox #bearerbox-host = localhost #log-file=log/wapbox.log #log-level=0 #access-log=log/wapboxaccess.log #smart-errors=yes #wml-strict=yes group = wapbox bearerbox-host = localhost log-file = log/wapbox.log syslog-level = none access-log = log/wapaccess.log #timer-freq = 10 map-url = http//mmsc/* http://172.22.25.175:1982/*; timer-freq = 1 #map-url = http://172.22.25.175:10001/* http://localhost:1982/* http-interface-name=172.22.25.175,localhost wml-strict=true an in the terminal i am getting this one . [naren...@localhost this is original]$ ./wapbox -v 1 kannelconf1.conf 2009-10-01 12:02:51 [15896] [0] INFO: Debug_lvl = 1, log_file = none, log_lvl = 0 2009-10-01 12:02:51 [15896] [0] WARNING: 'map-url' config directive and related are deprecated, please use wap-url-map group 2009-10-01 12:02:51 [15896] [0] INFO: Added logfile `log/wapbox.log' with level `-1'. 2009-10-01 12:02:51 [15896] [0] INFO: Starting to log to file log/wapbox.log level -1 2009-10-01 12:02:51 [15896] [0] INFO: Logging accesses to 'log/wapaccess.log'. 2009-10-01 12:02:51 [15896] [0] INFO: Started access logfile `log/wapaccess.log'. 2009-10-01 12:02:51 [15896] [0] INFO: 2009-10-01 12:02:51 [15896] [0] INFO: Kannel wapbox version 1.4.3 starting up. 2009-10-01 12:02:51 [15896] [0] INFO: Connected to bearerbox at localhost port 13013. pls give me some idea regardirding map-url .how can i communicate with from kannel to mbuni . Thanks in Advance . Best Regards, Narendra . -- Best Regards, narendra Reddy.
Re: message split in SUBMIT_SM pdu due to extended GSM characters
Well, I suppose these characters are counted after they would have
been converted to the GSM 03.38 alphabet.
2009/10/1 Jason Mule jason.m...@gmail.com:
Please take a look at the PDU dump below. It seems that these
characters are counted as occupying 2 bytes and yet we are using
ASCII:
2009-10-01 11:18:52 [9435] [7] DEBUG: type_name: submit_sm
2009-10-01 11:18:52 [9435] [7] DEBUG: command_id: 4 = 0x0004
2009-10-01 11:18:52 [9435] [7] DEBUG: command_status: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: sequence_number: 1775 = 0x06ef
2009-10-01 11:18:52 [9435] [7] DEBUG: service_type: 6502
2009-10-01 11:18:52 [9435] [7] DEBUG: source_addr_ton: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: source_addr_npi: 1 = 0x0001
2009-10-01 11:18:52 [9435] [7] DEBUG: source_addr: 6502
2009-10-01 11:18:52 [9435] [7] DEBUG: dest_addr_ton: 1 = 0x0001
2009-10-01 11:18:52 [9435] [7] DEBUG: dest_addr_npi: 1 = 0x0001
2009-10-01 11:18:52 [9435] [7] DEBUG: destination_addr: 250789112112
2009-10-01 11:18:52 [9435] [7] DEBUG: esm_class: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: protocol_id: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: priority_flag: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: schedule_delivery_time: NULL
2009-10-01 11:18:52 [9435] [7] DEBUG: validity_period: NULL
2009-10-01 11:18:52 [9435] [7] DEBUG: registered_delivery: 1 = 0x0001
2009-10-01 11:18:52 [9435] [7] DEBUG: replace_if_present_flag: 0 =
0x
2009-10-01 11:18:52 [9435] [7] DEBUG: data_coding: 0 = 0x
-- default coding (ASCII)
2009-10-01 11:18:52 [9435] [7] DEBUG: sm_default_msg_id: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: sm_length: 80 = 0x0050
2009-10-01 11:18:52 [9435] [7] DEBUG: short_message:
2009-10-01 11:18:52 [9435] [7] DEBUG: Octet string at 0x9360ed0:
2009-10-01 11:18:52 [9435] [7] DEBUG: len: 80
2009-10-01 11:18:52 [9435] [7] DEBUG: size: 81
2009-10-01 11:18:52 [9435] [7] DEBUG: immutable: 0
2009-10-01 11:18:52 [9435] [7] DEBUG: data: 7b 7d 7b 7d 7b 7d 7b
7d 7b 7d 7b 7d 7b 7d 7b 7d {}{}{}{}{}{}{}{}
2009-10-01 11:18:52 [9435] [7] DEBUG: data: 7b 7d 7b 7d 7b 7d 7b
7d 7b 7d 7b 7d 7b 7d 7b 7d {}{}{}{}{}{}{}{}
2009-10-01 11:18:52 [9435] [7] DEBUG: data: 7b 7d 7b 7d 7b 7d 7b
7d 7b 7d 7b 7d 7c 7c 7c 7c {}{}{}{}{}{}
2009-10-01 11:18:52 [9435] [7] DEBUG: data: 7c 7c 7c 7c 7c 7c 7c
7c 7b 7d 7b 7d 7b 7d 7b 7d {}{}{}{}
2009-10-01 11:18:52 [9435] [7] DEBUG: data: 7b 7d 7b 7d 7b 7d 7b
7d 7b 7d 7b 7d 7b 7d 7b 7d {}{}{}{}{}{}{}{}
2009-10-01 11:18:52 [9435] [7] DEBUG: Octet string dump ends.
2009-10-01 11:18:52 [9435] [7] DEBUG: SMPP PDU dump ends.
...(split occurs here and the second part is sent out)
2009-10-01 11:18:52 [9435] [7] DEBUG: SMPP[MAGPIE1]: Sending PDU:
2009-10-01 11:18:52 [9435] [7] DEBUG: SMPP PDU 0x936a260 dump:
2009-10-01 11:18:52 [9435] [7] DEBUG: type_name: submit_sm
2009-10-01 11:18:52 [9435] [7] DEBUG: command_id: 4 = 0x0004
2009-10-01 11:18:52 [9435] [7] DEBUG: command_status: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: sequence_number: 1776 = 0x06f0
2009-10-01 11:18:52 [9435] [7] DEBUG: service_type: 6502
2009-10-01 11:18:52 [9435] [7] DEBUG: source_addr_ton: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: source_addr_npi: 1 = 0x0001
2009-10-01 11:18:52 [9435] [7] DEBUG: source_addr: 6502
2009-10-01 11:18:52 [9435] [7] DEBUG: dest_addr_ton: 1 = 0x0001
2009-10-01 11:18:52 [9435] [7] DEBUG: dest_addr_npi: 1 = 0x0001
2009-10-01 11:18:52 [9435] [7] DEBUG: destination_addr: 250789112112
2009-10-01 11:18:52 [9435] [7] DEBUG: esm_class: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: protocol_id: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: priority_flag: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: schedule_delivery_time: NULL
2009-10-01 11:18:52 [9435] [7] DEBUG: validity_period: NULL
2009-10-01 11:18:52 [9435] [7] DEBUG: registered_delivery: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: replace_if_present_flag: 0 =
0x
2009-10-01 11:18:52 [9435] [7] DEBUG: data_coding: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: sm_default_msg_id: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: sm_length: 80 = 0x0050
2009-10-01 11:18:52 [9435] [7] DEBUG: short_message:
2009-10-01 11:18:52 [9435] [7] DEBUG: Octet string at 0x936d0f8:
2009-10-01 11:18:52 [9435] [7] DEBUG: len: 80
2009-10-01 11:18:52 [9435] [7] DEBUG: size: 81
2009-10-01 11:18:52 [9435] [7] DEBUG: immutable: 0
2009-10-01 11:18:52 [9435] [7] DEBUG: data: 7b 7d 7b 7d 7b 7d 7b
7d 7b 7d 7b 7d 7b 7d 7c 7c {}{}{}{}{}{}{}||
2009-10-01 11:18:52 [9435] [7] DEBUG: data: 7c 7c 7c 7c 7c 7c 7c
7c 7c 7c 7c 7c 7c 7c 7c 7c
2009-10-01 11:18:52 [9435]
how to use procmail to send SMS with kannel ?
Hi kannel user list, I want to use mail2sms. I use sendmail and procmail. I want to use procmail to handle email Subject: Alert* and SMS this Subject to me. My kannel is can send SMS. Have someone can do that ? How I do that ? Help me please. Thank you Watchara Kangkun
Custom PDU's
Title: Custom PDU's Operator has his own PDU commands: BIND_RECEIVER UNBIND UNBIND_RESP LMT_REPORT LMT_REPORT_RESP LMT_GEN_CODE LMT_GEN_CODE_RESP LMT_VERIFY_CODE LMT_VERIFY_CODE_RESP How to use them in kannel ?
Re: Custom PDU's
Hi As i told u earlier, for LMT u have to modify Kannel itself and add those custom PDU's to bearerbox. U cannot add custom PDU's by using SMPP TLV patch, u have to code them directly. Illimar Operator has his own PDU commands: BIND_RECEIVER UNBIND UNBIND_RESP LMT_REPORT LMT_REPORT_RESP LMT_GEN_CODE LMT_GEN_CODE_RESP LMT_VERIFY_CODE LMT_VERIFY_CODE_RESP How to use them in kannel ?
Re[2]: Custom PDU's
Title: Re[2]: Custom PDU's In which file ? Thursday, October 1, 2009, 3:08:45 PM, you wrote: Hi As i told u earlier, for LMT u have to modify Kannel itself and add those custom PDU's to bearerbox. U cannot add custom PDU's by using SMPP TLV patch, u have to code them directly. Illimar Operator has his own PDU commands: BIND_RECEIVER UNBIND UNBIND_RESP LMT_REPORT LMT_REPORT_RESP LMT_GEN_CODE LMT_GEN_CODE_RESP LMT_VERIFY_CODE LMT_VERIFY_CODE_RESP How to use them in kannel ?
Re: Custom PDU's
Hi I would start looking in smsc_smpp.c, smpp_pdu.h and smpp_pdu.def Illimar In which file ? Thursday, October 1, 2009, 3:08:45 PM, you wrote: Hi As i told u earlier, for LMT u have to modify Kannel itself and add those custom PDU's to bearerbox. U cannot add custom PDU's by using SMPP TLV patch, u have to code them directly. Illimar Operator has his own PDU commands: BIND_RECEIVER UNBIND UNBIND_RESP LMT_REPORT LMT_REPORT_RESP LMT_GEN_CODE LMT_GEN_CODE_RESP LMT_VERIFY_CODE LMT_VERIFY_CODE_RESP How to use them in kannel ?
Re: map-url
Hi, I cannot advise you about mbuni. You should address mbuni fora for that. However, I can point you to the right direction for kannel's warning. As detailed in the warning do not use the variable map-url. Pass along the same information with wap-url-map group. It does the same thing for you. You can read in the User's Guide about it. BR, Nikos - Original Message - From: narendra reddy To: users@kannel.org Sent: Thursday, October 01, 2009 11:37 AM Subject: map-url Hi list , i am using mbuni for sending the mms message with help of kannel .i think the connection between kannel adn mbuni is the map-url in the wap-box group .like that given the in the mbuni user guide .according to that i configured and run the both mbuni ,kannel and both are started successfully .but when i run the wapbox it was giving some warning and both are not communicated .can any one pls give me some solution for my problem. here is my config file . group = core admin-port = 13004 admin-password = bar log-file = log/bearer.log log-level = 0 access-log = log/beareraccess.log smsbox-port = 13002 store-file = log/kannelqueue.log wapbox-port=13013 wdp-interface-name=* box-allow-ip = 127.0.0.1,172.22.25.175 # SMSC SMPP group = smsc smsc = smpp smsc-id = SMPPSim host = 172.22.25.175 port = 2775 log-file = log/kannel.log transceiver-mode = 1 alt-dcs = true smsc-username = smppclient smsc-password = password system-type = address-range = source-addr-ton = 1 source-addr-npi = 1 dest-addr-ton = 1 dest-addr-npi = 1 msg-id-type = 0x01 throughput = 50 max-pending-submits = 1 enquire-link-interval= 60 # SMSBOX SETUP group = smsbox bearerbox-host = localhost sendsms-port = 13006 log-file = log/smsbox.log log-level = 0 access-log = log/smsboxaccess.log # SEND-SMS USERS group = sendsms-user username = pyro1 password = pyro1 max-messages = 50 concatenation = true # SMS-Service group = sms-service keyword = www text = Website found!!! # SMS-Service group = sms-service keyword = default text = Reply from ESME #group = wapbox #bearerbox-host = localhost #log-file=log/wapbox.log #log-level=0 #access-log=log/wapboxaccess.log #smart-errors=yes #wml-strict=yes group = wapbox bearerbox-host = localhost log-file = log/wapbox.log syslog-level = none access-log = log/wapaccess.log #timer-freq = 10 map-url = http//mmsc/* http://172.22.25.175:1982/*; timer-freq = 1 #map-url = http://172.22.25.175:10001/* http://localhost:1982/* http-interface-name=172.22.25.175,localhost wml-strict=true an in the terminal i am getting this one . [naren...@localhost this is original]$ ./wapbox -v 1 kannelconf1.conf 2009-10-01 12:02:51 [15896] [0] INFO: Debug_lvl = 1, log_file = none, log_lvl = 0 2009-10-01 12:02:51 [15896] [0] WARNING: 'map-url' config directive and related are deprecated, please use wap-url-map group 2009-10-01 12:02:51 [15896] [0] INFO: Added logfile `log/wapbox.log' with level `-1'. 2009-10-01 12:02:51 [15896] [0] INFO: Starting to log to file log/wapbox.log level -1 2009-10-01 12:02:51 [15896] [0] INFO: Logging accesses to 'log/wapaccess.log'. 2009-10-01 12:02:51 [15896] [0] INFO: Started access logfile `log/wapaccess.log'. 2009-10-01 12:02:51 [15896] [0] INFO: 2009-10-01 12:02:51 [15896] [0] INFO: Kannel wapbox version 1.4.3 starting up. 2009-10-01 12:02:51 [15896] [0] INFO: Connected to bearerbox at localhost port 13013. pls give me some idea regardirding map-url .how can i communicate with from kannel to mbuni . Thanks in Advance . Best Regards, Narendra . -- Best Regards, narendra Reddy.
Re: message split in SUBMIT_SM pdu due to extended GSM characters
No, they are not! As it says in debug log, and can verify from pdu dump,
sm_length = 80. Guess what? oct_length is also 80! Where is your evidence
that any single character is split in more than 1 byte?
You cannot send 160 B of text in a single SMS. You have to leave space for
UDH. Where the SMS will split (middle, end, etc.) is configured with the
split-chars variable in sendsms-user group.
Have you tried sending 160 'a's as a single sms?
BR,
Nikos
- Original Message -
From: Jason Mule jason.m...@gmail.com
To: Nikos Balkanas nbalka...@gmail.com
Cc: users@kannel.org
Sent: Thursday, October 01, 2009 11:36 AM
Subject: Re: message split in SUBMIT_SM pdu due to extended GSM characters
Please take a look at the PDU dump below. It seems that these
characters are counted as occupying 2 bytes and yet we are using
ASCII:
2009-10-01 11:18:52 [9435] [7] DEBUG: type_name: submit_sm
2009-10-01 11:18:52 [9435] [7] DEBUG: command_id: 4 = 0x0004
2009-10-01 11:18:52 [9435] [7] DEBUG: command_status: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: sequence_number: 1775 = 0x06ef
2009-10-01 11:18:52 [9435] [7] DEBUG: service_type: 6502
2009-10-01 11:18:52 [9435] [7] DEBUG: source_addr_ton: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: source_addr_npi: 1 = 0x0001
2009-10-01 11:18:52 [9435] [7] DEBUG: source_addr: 6502
2009-10-01 11:18:52 [9435] [7] DEBUG: dest_addr_ton: 1 = 0x0001
2009-10-01 11:18:52 [9435] [7] DEBUG: dest_addr_npi: 1 = 0x0001
2009-10-01 11:18:52 [9435] [7] DEBUG: destination_addr: 250789112112
2009-10-01 11:18:52 [9435] [7] DEBUG: esm_class: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: protocol_id: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: priority_flag: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: schedule_delivery_time: NULL
2009-10-01 11:18:52 [9435] [7] DEBUG: validity_period: NULL
2009-10-01 11:18:52 [9435] [7] DEBUG: registered_delivery: 1 =
0x0001
2009-10-01 11:18:52 [9435] [7] DEBUG: replace_if_present_flag: 0 =
0x
2009-10-01 11:18:52 [9435] [7] DEBUG: data_coding: 0 = 0x
-- default coding (ASCII)
2009-10-01 11:18:52 [9435] [7] DEBUG: sm_default_msg_id: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: sm_length: 80 = 0x0050
2009-10-01 11:18:52 [9435] [7] DEBUG: short_message:
2009-10-01 11:18:52 [9435] [7] DEBUG:Octet string at 0x9360ed0:
2009-10-01 11:18:52 [9435] [7] DEBUG: len: 80
2009-10-01 11:18:52 [9435] [7] DEBUG: size: 81
2009-10-01 11:18:52 [9435] [7] DEBUG: immutable: 0
2009-10-01 11:18:52 [9435] [7] DEBUG: data: 7b 7d 7b 7d 7b 7d 7b
7d 7b 7d 7b 7d 7b 7d 7b 7d {}{}{}{}{}{}{}{}
2009-10-01 11:18:52 [9435] [7] DEBUG: data: 7b 7d 7b 7d 7b 7d 7b
7d 7b 7d 7b 7d 7b 7d 7b 7d {}{}{}{}{}{}{}{}
2009-10-01 11:18:52 [9435] [7] DEBUG: data: 7b 7d 7b 7d 7b 7d 7b
7d 7b 7d 7b 7d 7c 7c 7c 7c {}{}{}{}{}{}
2009-10-01 11:18:52 [9435] [7] DEBUG: data: 7c 7c 7c 7c 7c 7c 7c
7c 7b 7d 7b 7d 7b 7d 7b 7d {}{}{}{}
2009-10-01 11:18:52 [9435] [7] DEBUG: data: 7b 7d 7b 7d 7b 7d 7b
7d 7b 7d 7b 7d 7b 7d 7b 7d {}{}{}{}{}{}{}{}
2009-10-01 11:18:52 [9435] [7] DEBUG:Octet string dump ends.
2009-10-01 11:18:52 [9435] [7] DEBUG: SMPP PDU dump ends.
...(split occurs here and the second part is sent out)
2009-10-01 11:18:52 [9435] [7] DEBUG: SMPP[MAGPIE1]: Sending PDU:
2009-10-01 11:18:52 [9435] [7] DEBUG: SMPP PDU 0x936a260 dump:
2009-10-01 11:18:52 [9435] [7] DEBUG: type_name: submit_sm
2009-10-01 11:18:52 [9435] [7] DEBUG: command_id: 4 = 0x0004
2009-10-01 11:18:52 [9435] [7] DEBUG: command_status: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: sequence_number: 1776 = 0x06f0
2009-10-01 11:18:52 [9435] [7] DEBUG: service_type: 6502
2009-10-01 11:18:52 [9435] [7] DEBUG: source_addr_ton: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: source_addr_npi: 1 = 0x0001
2009-10-01 11:18:52 [9435] [7] DEBUG: source_addr: 6502
2009-10-01 11:18:52 [9435] [7] DEBUG: dest_addr_ton: 1 = 0x0001
2009-10-01 11:18:52 [9435] [7] DEBUG: dest_addr_npi: 1 = 0x0001
2009-10-01 11:18:52 [9435] [7] DEBUG: destination_addr: 250789112112
2009-10-01 11:18:52 [9435] [7] DEBUG: esm_class: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: protocol_id: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: priority_flag: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: schedule_delivery_time: NULL
2009-10-01 11:18:52 [9435] [7] DEBUG: validity_period: NULL
2009-10-01 11:18:52 [9435] [7] DEBUG: registered_delivery: 0 =
0x
2009-10-01 11:18:52 [9435] [7] DEBUG: replace_if_present_flag: 0 =
0x
2009-10-01 11:18:52 [9435] [7] DEBUG: data_coding: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: sm_default_msg_id: 0 = 0x
2009-10-01 11:18:52 [9435] [7] DEBUG: sm_length: 80 = 0x0050
2009-10-01 11:18:52 [9435] [7] DEBUG: short_message:
Re: how to use procmail to send SMS with kannel ?
Hi, You will have to consult procmail documentation. With sendmail you can define a special recipient that will execute a script when mail is received. That script could post a message to kannel's sendsms interface. BR, Nikos - Original Message - From: Watchara Kangkun To: users@kannel.org Sent: Thursday, October 01, 2009 1:14 PM Subject: how to use procmail to send SMS with kannel ? Hi kannel user list, I want to use mail2sms. I use sendmail and procmail. I want to use procmail to handle email Subject: Alert* and SMS this Subject to me. My kannel is can send SMS. Have someone can do that ? How I do that ? Help me please. Thank you Watchara Kangkun
Re: Custom PDU's
Custom PDU'sYou can't. Kannel supports a zillion SMSc protocols according to spec. But no hacking jobs. How about changing SMSc? PS The top 3 PDUs are standard SMPP and are supported. BR, Nikos - Original Message - From: waza...@inbox.lv To: users@kannel.org Sent: Thursday, October 01, 2009 3:02 PM Subject: Custom PDU's Operator has his own PDU commands: BIND_RECEIVER UNBIND UNBIND_RESP LMT_REPORT LMT_REPORT_RESP LMT_GEN_CODE LMT_GEN_CODE_RESP LMT_VERIFY_CODE LMT_VERIFY_CODE_RESP How to use them in kannel ?
Re: message split in SUBMIT_SM pdu due to extended GSM characters
It is possible to send 160 'a's as a single sms because I suppose these should each fit in 1 septet in the GSM alphabet. Please take a look at the PDU dump below: 2009-10-01 15:37:10 [31609] [7] DEBUG: SMPP PDU 0xab200c30 dump: 2009-10-01 15:37:10 [31609] [7] DEBUG: type_name: submit_sm 2009-10-01 15:37:10 [31609] [7] DEBUG: command_id: 4 = 0x0004 2009-10-01 15:37:10 [31609] [7] DEBUG: command_status: 0 = 0x 2009-10-01 15:37:10 [31609] [7] DEBUG: sequence_number: 418 = 0x01a2 2009-10-01 15:37:10 [31609] [7] DEBUG: service_type: 6502 2009-10-01 15:37:10 [31609] [7] DEBUG: source_addr_ton: 0 = 0x 2009-10-01 15:37:10 [31609] [7] DEBUG: source_addr_npi: 1 = 0x0001 2009-10-01 15:37:10 [31609] [7] DEBUG: source_addr: 6502 2009-10-01 15:37:10 [31609] [7] DEBUG: dest_addr_ton: 1 = 0x0001 2009-10-01 15:37:10 [31609] [7] DEBUG: dest_addr_npi: 1 = 0x0001 2009-10-01 15:37:10 [31609] [7] DEBUG: destination_addr: 254722683186 2009-10-01 15:37:10 [31609] [7] DEBUG: esm_class: 0 = 0x 2009-10-01 15:37:10 [31609] [7] DEBUG: protocol_id: 0 = 0x 2009-10-01 15:37:10 [31609] [7] DEBUG: priority_flag: 0 = 0x 2009-10-01 15:37:10 [31609] [7] DEBUG: schedule_delivery_time: NULL 2009-10-01 15:37:10 [31609] [7] DEBUG: validity_period: NULL 2009-10-01 15:37:10 [31609] [7] DEBUG: registered_delivery: 1 = 0x0001 2009-10-01 15:37:10 [31609] [7] DEBUG: replace_if_present_flag: 0 = 0x 2009-10-01 15:37:10 [31609] [7] DEBUG: data_coding: 0 = 0x 2009-10-01 15:37:10 [31609] [7] DEBUG: sm_default_msg_id: 0 = 0x 2009-10-01 15:37:10 [31609] [7] DEBUG: sm_length: 160 = 0x00a0 2009-10-01 15:37:10 [31609] [7] DEBUG: short_message: 2009-10-01 15:37:10 [31609] [7] DEBUG:Octet string at 0xab2007a8: 2009-10-01 15:37:10 [31609] [7] DEBUG: len: 160 2009-10-01 15:37:10 [31609] [7] DEBUG: size: 161 2009-10-01 15:37:10 [31609] [7] DEBUG: immutable: 0 2009-10-01 15:37:10 [31609] [7] DEBUG: data: 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 2009-10-01 15:37:10 [31609] [7] DEBUG: data: 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 2009-10-01 15:37:10 [31609] [7] DEBUG: data: 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 2009-10-01 15:37:10 [31609] [7] DEBUG: data: 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 2009-10-01 15:37:10 [31609] [7] DEBUG: data: 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 2009-10-01 15:37:10 [31609] [7] DEBUG: data: 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 2009-10-01 15:37:10 [31609] [7] DEBUG: data: 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 2009-10-01 15:37:10 [31609] [7] DEBUG: data: 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 2009-10-01 15:37:10 [31609] [7] DEBUG: data: 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 2009-10-01 15:37:10 [31609] [7] DEBUG: data: 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 2009-10-01 15:37:10 [31609] [7] DEBUG:Octet string dump ends. 2009/10/1 Nikos Balkanas nbalka...@gmail.com: No, they are not! As it says in debug log, and can verify from pdu dump, sm_length = 80. Guess what? oct_length is also 80! Where is your evidence that any single character is split in more than 1 byte? You cannot send 160 B of text in a single SMS. You have to leave space for UDH. Where the SMS will split (middle, end, etc.) is configured with the split-chars variable in sendsms-user group. Have you tried sending 160 'a's as a single sms? BR, Nikos - Original Message - From: Jason Mule jason.m...@gmail.com To: Nikos Balkanas nbalka...@gmail.com Cc: users@kannel.org Sent: Thursday, October 01, 2009 11:36 AM Subject: Re: message split in SUBMIT_SM pdu due to extended GSM characters Please take a look at the PDU dump below. It seems that these characters are counted as occupying 2 bytes and yet we are using ASCII: 2009-10-01 11:18:52 [9435] [7] DEBUG: type_name: submit_sm 2009-10-01 11:18:52 [9435] [7] DEBUG: command_id: 4 = 0x0004 2009-10-01 11:18:52 [9435] [7] DEBUG: command_status: 0 = 0x 2009-10-01 11:18:52 [9435] [7] DEBUG: sequence_number: 1775 = 0x06ef 2009-10-01 11:18:52 [9435] [7] DEBUG: service_type: 6502 2009-10-01 11:18:52 [9435] [7] DEBUG: source_addr_ton: 0 = 0x 2009-10-01 11:18:52 [9435] [7] DEBUG: source_addr_npi: 1 = 0x0001 2009-10-01 11:18:52 [9435] [7] DEBUG: source_addr: 6502 2009-10-01 11:18:52 [9435] [7] DEBUG: dest_addr_ton: 1 = 0x0001 2009-10-01 11:18:52 [9435] [7] DEBUG: dest_addr_npi: 1 = 0x0001 2009-10-01 11:18:52 [9435] [7] DEBUG: destination_addr: 250789112112 2009-10-01 11:18:52 [9435] [7] DEBUG: esm_class: 0 = 0x 2009-10-01 11:18:52 [9435] [7] DEBUG:
Re: message split in SUBMIT_SM pdu due to extended GSM characters
Hi, I am corrected. Indeed septets leave enough space for the UDH headers. And also you seem to have come across a legitimate bug. If you wish you can fill a bug report at http://redmine.kannel.org/. Any developers would like to take a crack at it? BR, Nikos - Original Message - From: Jason Mule jason.m...@gmail.com To: Nikos Balkanas nbalka...@gmail.com Cc: users@kannel.org Sent: Thursday, October 01, 2009 3:43 PM Subject: Re: message split in SUBMIT_SM pdu due to extended GSM characters It is possible to send 160 'a's as a single sms because I suppose these should each fit in 1 septet in the GSM alphabet. Please take a look at the PDU dump below: 2009-10-01 15:37:10 [31609] [7] DEBUG: SMPP PDU 0xab200c30 dump: 2009-10-01 15:37:10 [31609] [7] DEBUG: type_name: submit_sm 2009-10-01 15:37:10 [31609] [7] DEBUG: command_id: 4 = 0x0004 2009-10-01 15:37:10 [31609] [7] DEBUG: command_status: 0 = 0x 2009-10-01 15:37:10 [31609] [7] DEBUG: sequence_number: 418 = 0x01a2 2009-10-01 15:37:10 [31609] [7] DEBUG: service_type: 6502 2009-10-01 15:37:10 [31609] [7] DEBUG: source_addr_ton: 0 = 0x 2009-10-01 15:37:10 [31609] [7] DEBUG: source_addr_npi: 1 = 0x0001 2009-10-01 15:37:10 [31609] [7] DEBUG: source_addr: 6502 2009-10-01 15:37:10 [31609] [7] DEBUG: dest_addr_ton: 1 = 0x0001 2009-10-01 15:37:10 [31609] [7] DEBUG: dest_addr_npi: 1 = 0x0001 2009-10-01 15:37:10 [31609] [7] DEBUG: destination_addr: 254722683186 2009-10-01 15:37:10 [31609] [7] DEBUG: esm_class: 0 = 0x 2009-10-01 15:37:10 [31609] [7] DEBUG: protocol_id: 0 = 0x 2009-10-01 15:37:10 [31609] [7] DEBUG: priority_flag: 0 = 0x 2009-10-01 15:37:10 [31609] [7] DEBUG: schedule_delivery_time: NULL 2009-10-01 15:37:10 [31609] [7] DEBUG: validity_period: NULL 2009-10-01 15:37:10 [31609] [7] DEBUG: registered_delivery: 1 = 0x0001 2009-10-01 15:37:10 [31609] [7] DEBUG: replace_if_present_flag: 0 = 0x 2009-10-01 15:37:10 [31609] [7] DEBUG: data_coding: 0 = 0x 2009-10-01 15:37:10 [31609] [7] DEBUG: sm_default_msg_id: 0 = 0x 2009-10-01 15:37:10 [31609] [7] DEBUG: sm_length: 160 = 0x00a0 2009-10-01 15:37:10 [31609] [7] DEBUG: short_message: 2009-10-01 15:37:10 [31609] [7] DEBUG:Octet string at 0xab2007a8: 2009-10-01 15:37:10 [31609] [7] DEBUG: len: 160 2009-10-01 15:37:10 [31609] [7] DEBUG: size: 161 2009-10-01 15:37:10 [31609] [7] DEBUG: immutable: 0 2009-10-01 15:37:10 [31609] [7] DEBUG: data: 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 2009-10-01 15:37:10 [31609] [7] DEBUG: data: 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 2009-10-01 15:37:10 [31609] [7] DEBUG: data: 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 2009-10-01 15:37:10 [31609] [7] DEBUG: data: 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 2009-10-01 15:37:10 [31609] [7] DEBUG: data: 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 2009-10-01 15:37:10 [31609] [7] DEBUG: data: 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 2009-10-01 15:37:10 [31609] [7] DEBUG: data: 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 2009-10-01 15:37:10 [31609] [7] DEBUG: data: 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 2009-10-01 15:37:10 [31609] [7] DEBUG: data: 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 2009-10-01 15:37:10 [31609] [7] DEBUG: data: 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 2009-10-01 15:37:10 [31609] [7] DEBUG:Octet string dump ends. 2009/10/1 Nikos Balkanas nbalka...@gmail.com: No, they are not! As it says in debug log, and can verify from pdu dump, sm_length = 80. Guess what? oct_length is also 80! Where is your evidence that any single character is split in more than 1 byte? You cannot send 160 B of text in a single SMS. You have to leave space for UDH. Where the SMS will split (middle, end, etc.) is configured with the split-chars variable in sendsms-user group. Have you tried sending 160 'a's as a single sms? BR, Nikos - Original Message - From: Jason Mule jason.m...@gmail.com To: Nikos Balkanas nbalka...@gmail.com Cc: users@kannel.org Sent: Thursday, October 01, 2009 11:36 AM Subject: Re: message split in SUBMIT_SM pdu due to extended GSM characters Please take a look at the PDU dump below. It seems that these characters are counted as occupying 2 bytes and yet we are using ASCII: 2009-10-01 11:18:52 [9435] [7] DEBUG: type_name: submit_sm 2009-10-01 11:18:52 [9435] [7] DEBUG: command_id: 4 = 0x0004 2009-10-01 11:18:52 [9435] [7] DEBUG: command_status: 0 = 0x 2009-10-01 11:18:52 [9435] [7] DEBUG: sequence_number: 1775 = 0x06ef 2009-10-01 11:18:52 [9435] [7] DEBUG: service_type: 6502 2009-10-01 11:18:52 [9435] [7] DEBUG:
Re: map-url
Hi Nikos, first thanks for giving responce to my mail . in the user guide where it was given like this *group = wap-user-map* *group = wap-url--map i *serched whole user guide .but i am not fine it like group=wap-user-map .or i can assume another groups as wap-user-map group .can you tell me where it was in user guide . Thanks Regards , narendra . 2009/10/1 Nikos Balkanas nbalka...@gmail.com Hi, I cannot advise you about mbuni. You should address mbuni fora for that. However, I can point you to the right direction for kannel's warning. As detailed in the warning do not use the variable map-url. Pass along the same information with wap-url-map group. It does the same thing for you. You can read in the User's Guide about it. BR, Nikos - Original Message - *From:* narendra reddy kamaninaren...@gmail.com *To:* users@kannel.org *Sent:* Thursday, October 01, 2009 11:37 AM *Subject:* map-url Hi list , i am using mbuni for sending the mms message with help of kannel .i think the connection between kannel adn mbuni is the map-url in the wap-box group .like that given the in the mbuni user guide .according to that i configured and run the both mbuni ,kannel and both are started successfully .but when i run the wapbox it was giving some warning and both are not communicated .can any one pls give me some solution for my problem. here is my config file . group = core admin-port = 13004 admin-password = bar log-file = log/bearer.log log-level = 0 access-log = log/beareraccess.log smsbox-port = 13002 store-file = log/kannelqueue.log wapbox-port=13013 wdp-interface-name=* box-allow-ip = 127.0.0.1,172.22.25.175 # SMSC SMPP group = smsc smsc = smpp smsc-id = SMPPSim host = 172.22.25.175 port = 2775 log-file = log/kannel.log transceiver-mode = 1 alt-dcs = true smsc-username = smppclient smsc-password = password system-type = address-range = source-addr-ton = 1 source-addr-npi = 1 dest-addr-ton = 1 dest-addr-npi = 1 msg-id-type = 0x01 throughput = 50 max-pending-submits = 1 enquire-link-interval= 60 # SMSBOX SETUP group = smsbox bearerbox-host = localhost sendsms-port = 13006 log-file = log/smsbox.log log-level = 0 access-log = log/smsboxaccess.log # SEND-SMS USERS group = sendsms-user username = pyro1 password = pyro1 max-messages = 50 concatenation = true # SMS-Service group = sms-service keyword = www text = Website found!!! # SMS-Service group = sms-service keyword = default text = Reply from ESME #group = wapbox #bearerbox-host = localhost #log-file=log/wapbox.log #log-level=0 #access-log=log/wapboxaccess.log #smart-errors=yes #wml-strict=yes group = wapbox bearerbox-host = localhost log-file = log/wapbox.log syslog-level = none access-log = log/wapaccess.log #timer-freq = 10 map-url = http//mmsc/* http://172.22.25.175:1982/*; timer-freq = 1 #map-url = http://172.22.25.175:10001/* http://localhost:1982/* http-interface-name=172.22.25.175,localhost wml-strict=true an in the terminal i am getting this one . [naren...@localhost this is original]$ ./wapbox -v 1 kannelconf1.conf 2009-10-01 12:02:51 [15896] [0] INFO: Debug_lvl = 1, log_file = none, log_lvl = 0 2009-10-01 12:02:51 [15896] [0] WARNING: 'map-url' config directive and related are deprecated, please use wap-url-map group 2009-10-01 12:02:51 [15896] [0] INFO: Added logfile `log/wapbox.log' with level `-1'. 2009-10-01 12:02:51 [15896] [0] INFO: Starting to log to file log/wapbox.log level -1 2009-10-01 12:02:51 [15896] [0] INFO: Logging accesses to 'log/wapaccess.log'. 2009-10-01 12:02:51 [15896] [0] INFO: Started access logfile `log/wapaccess.log'. 2009-10-01 12:02:51 [15896] [0] INFO: 2009-10-01 12:02:51 [15896] [0] INFO: Kannel wapbox version 1.4.3 starting up. 2009-10-01 12:02:51 [15896] [0] INFO: Connected to bearerbox at localhost port 13013. pls give me some idea regardirding map-url .how can i communicate with from kannel to mbuni . Thanks in Advance . Best Regards, Narendra . -- Best Regards, narendra Reddy. -- Best Regards, narendra Reddy.
Re: coding
Have you verified what the charset FROM carrier is? Some carriers send messages in different charset depending on content, or just use the charset defined by the sender, therefore, you might need to ask kannel -see the options in userguide- to pass you the incomming charset and pass that info to your application so you can decode charsets correctly in your app. Regards Alvaro |-| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.NET www.smsglobal.com.mx y www.pravcom.com On Thu, Oct 1, 2009 at 3:28 AM, patrick meye patrick_m...@hotmail.fr wrote: Hi all, I come back cause i don't solve my coding problem,is someone can help me please??? So,I've changed coding and charset diferent values (according userguide) no successful,i'm not a develloper so i can juste setting. When i send sms from mobile phone to TV,via sms-service,specials charactères are not correctly apear to TV.I send sms to my service,ex: -CSPI essai2 téléAfrica2,where CSPI is keyword and essai2 téléAfrica2 is body but é charactère apear like this é on TV.So é from mobile é to TV and i want é from mobile é to TV charactère for exemple. Where am i wrong please help me Best regard! add is my traces files(smsbox.log and access.log) Date: Fri, 25 Sep 2009 14:04:28 +0300 Subject: Re: coding From: seik...@gmail.com To: users@kannel.org the ususal character set encoding used by kannel to post to http is ISO-8859-1 when you get extra characters Kannel use UTF-16BE this is why you should convert from the kannel encoing to your native encoding, THEN encode to UTF On Fri, Sep 25, 2009 at 12:27 PM, patrick meye patrick_m...@hotmail.fr wrote: Thanks for reply, perhaps i don't understand what you say but it's my encoding that decode to UTF-8 for sms apear to TV monitor. this is the schema: sms sms Kannel--Application-TV (???) (UTF-8) (UTF-8) My problem is kannel coding and format. Best regard! Date: Fri, 25 Sep 2009 11:32:09 +0300 From: seik...@gmail.com CC: users@kannel.org Subject: Re: coding Decode at the HTTP interface from UTF-8 to your encoding example php: $sms1251=preg_match(/UTF/i,$GLOBALS[_REQUEST][charset]) ? pg_escape_string(iconv($GLOBALS[_REQUEST][charset], Windows-1251,$GLOBALS[_REQUEST][message])) : pg_escape_string($GLOBALS[_REQUEST][message]); patrick meye wrote: Hi all, I successfully setting up kannel like sms gateway and it run perfectly.So i created a service that send sms to TV via another application that format is UTF-8.Service run ok but i have an encoding and format problem,cause some special charactèr are mal formated (i.e ex:é,à,è,ç,...etc).Is some one can help me,what can i do what setting add??? Adding is my kannel.conf please help me. Sorry for my english i'm just learning english. Best regard! Découvrez toutes les possibilités de communication avec vos proches http://www.microsoft.com/windows/windowslive/default.aspx Vous voulez savoir ce que vous pouvez faire avec le nouveau Windows Live ? Lancez-vous ! -- seik Tous vos amis discutent sur Messenger, et vous ? Téléchargez Messenger, c'est gratuit !
Re: message split in SUBMIT_SM pdu due to extended GSM characters
Hi,
Well, GSM extended characters like ^, {, |, } and ~ will need 2
septets because of the escape character so Kannel anticipates this
during the split.
2009/10/1 Nikos Balkanas nbalka...@gmail.com:
Hi,
I am corrected. Indeed septets leave enough space for the UDH headers. And
also you seem to have come across a legitimate bug. If you wish you can fill
a bug report at http://redmine.kannel.org/.
Any developers would like to take a crack at it?
BR,
Nikos
Re: map-url
Hi, In the source code, see: gwlib/cfg.def There are the following groups defined: MULTI_GROUP(wap-url-map, OCTSTR(name) OCTSTR(url) OCTSTR(map-url) OCTSTR(send-msisdn-query) OCTSTR(send-msisdn-header) OCTSTR(send-msisdn-format) OCTSTR(accept-cookies) ) MULTI_GROUP(wap-user-map, OCTSTR(name) OCTSTR(user) OCTSTR(pass) OCTSTR(msisdn) ) I guess wap is not supported any longer in kannel, therefore the User guide is outdated. I will describe the fields for you: wap-url-map: name: Just a refernce name for this map. I.e. map1 url: Target url that you want to replace. Accepts wildcards. map-url: What to replace it with. Accepts wild-cards. msisdn stuff: Radius related stuff. If msisdn is known through radius, it will send the msisdn number in a special header. accept-cookies: Boolean. Yes or No. You know, like a browser. wap-user-map: This is optional, if authentication is needed for the mapped url. I don't think it is implemented, though. Just skip. BR, Nikos - Original Message - From: narendra reddy To: users@kannel.org Sent: Thursday, October 01, 2009 4:20 PM Subject: Re: map-url Hi Nikos, first thanks for giving responce to my mail . in the user guide where it was given like this group = wap-user-map group = wap-url--map i serched whole user guide .but i am not fine it like group=wap-user-map .or i can assume another groups as wap-user-map group .can you tell me where it was in user guide . Thanks Regards , narendra . 2009/10/1 Nikos Balkanas nbalka...@gmail.com Hi, I cannot advise you about mbuni. You should address mbuni fora for that. However, I can point you to the right direction for kannel's warning. As detailed in the warning do not use the variable map-url. Pass along the same information with wap-url-map group. It does the same thing for you. You can read in the User's Guide about it. BR, Nikos - Original Message - From: narendra reddy To: users@kannel.org Sent: Thursday, October 01, 2009 11:37 AM Subject: map-url Hi list , i am using mbuni for sending the mms message with help of kannel .i think the connection between kannel adn mbuni is the map-url in the wap-box group .like that given the in the mbuni user guide .according to that i configured and run the both mbuni ,kannel and both are started successfully .but when i run the wapbox it was giving some warning and both are not communicated .can any one pls give me some solution for my problem. here is my config file . group = core admin-port = 13004 admin-password = bar log-file = log/bearer.log log-level = 0 access-log = log/beareraccess.log smsbox-port = 13002 store-file = log/kannelqueue.log wapbox-port=13013 wdp-interface-name=* box-allow-ip = 127.0.0.1,172.22.25.175 # SMSC SMPP group = smsc smsc = smpp smsc-id = SMPPSim host = 172.22.25.175 port = 2775 log-file = log/kannel.log transceiver-mode = 1 alt-dcs = true smsc-username = smppclient smsc-password = password system-type = address-range = source-addr-ton = 1 source-addr-npi = 1 dest-addr-ton = 1 dest-addr-npi = 1 msg-id-type = 0x01 throughput = 50 max-pending-submits = 1 enquire-link-interval= 60 # SMSBOX SETUP group = smsbox bearerbox-host = localhost sendsms-port = 13006 log-file = log/smsbox.log log-level = 0 access-log = log/smsboxaccess.log # SEND-SMS USERS group = sendsms-user username = pyro1 password = pyro1 max-messages = 50 concatenation = true # SMS-Service group = sms-service keyword = www text = Website found!!! # SMS-Service group = sms-service keyword = default text = Reply from ESME #group = wapbox #bearerbox-host = localhost #log-file=log/wapbox.log #log-level=0 #access-log=log/wapboxaccess.log #smart-errors=yes #wml-strict=yes group = wapbox bearerbox-host = localhost log-file = log/wapbox.log syslog-level = none access-log = log/wapaccess.log #timer-freq = 10 map-url = http//mmsc/* http://172.22.25.175:1982/*; timer-freq = 1 #map-url = http://172.22.25.175:10001/* http://localhost:1982/* http-interface-name=172.22.25.175,localhost wml-strict=true an in the terminal i am getting this one . [naren...@localhost this is original]$ ./wapbox -v 1 kannelconf1.conf 2009-10-01 12:02:51 [15896] [0] INFO: Debug_lvl = 1, log_file = none, log_lvl = 0 2009-10-01 12:02:51 [15896] [0] WARNING: 'map-url'
Re: message split in SUBMIT_SM pdu due to extended GSM characters
Thanks, mate.
I imagine the SMSc inserts these escapes, because kannel's submit_sm PDU
doesn't. So if it is not a bug, it's got to be a feature ;-)
BR,
Nikos
- Original Message -
From: Jason Mule jason.m...@gmail.com
To: Nikos Balkanas nbalka...@gmail.com
Cc: users@kannel.org
Sent: Thursday, October 01, 2009 4:34 PM
Subject: Re: message split in SUBMIT_SM pdu due to extended GSM characters
Hi,
Well, GSM extended characters like ^, {, |, } and ~ will need 2
septets because of the escape character so Kannel anticipates this
during the split.
2009/10/1 Nikos Balkanas nbalka...@gmail.com:
Hi,
I am corrected. Indeed septets leave enough space for the UDH headers. And
also you seem to have come across a legitimate bug. If you wish you can
fill
a bug report at http://redmine.kannel.org/.
Any developers would like to take a crack at it?
BR,
Nikos
Re: kannel over using SMSC API....
Hi Matt, You nailed it exactly on the head. You HAVE to get a first provider, to deliver his SMS. Let's say you take a provider in China. They will give you their subscribers. Then you approach Verizon and you tell them: I can provide you roaming with China's chinatel. Will you provide me roaming in the US? You don't need shortcodes or longcodes. You need to build a clientbase. The more you have, the easier it will be to get them into the bargaining table. Certain providers, like ATT like to have their own services. But there are niche countries, like Rhodesia, that they are not interested in directly investing into. If you have access, you can approach them to discuss possible roaming possibilities. These are fictional names, so please do not take anything for real. I am a technical person, not a business one. I just hope I can point you in the right direction. Basically you have to work with a sales/business person to close these agreements. This person has to find and lookup the contacts you need. BR, Nikos - Original Message - From: Matt Hart To: users@kannel.org Sent: Wednesday, September 30, 2009 6:32 PM Subject: Re: kannel over using SMSC API Thank you Nikos. Ok, this may be a little off-the-normal-topic... but, Is there a compiled list of contacts for carriers (in the US preferably) where one could start this process? It would be instructive to use even one carrier as a starting point to get kannel operating towards several carriers eventually. Also, would one need a short code in hand before approaching these companies, or could they offer up a long code contract one could use on a limited basis that could be assigned for testing? (It would be nice to try to do this without the use of a modem since it seems technically possible.) Thank you, Matt --- On Wed, 9/30/09, Nikos Balkanas nbalka...@gmail.com wrote: From: Nikos Balkanas nbalka...@gmail.com Subject: Re: kannel over using SMSC API To: Kent Walker kent.wal...@jasperwireless.com, Matt Hart covat...@yahoo.com, users@kannel.org Date: Wednesday, September 30, 2009, 5:01 AM Hi Matt, To do carrier routing, you will have to sign roaming agreements with the carriers you are interested. They usually provide an HTTP interface which you can access and for a small charge each time, they will return the status of the subscriber (absent, successful, etc.) BR, Nikos - Original Message - From: Kent Walker To: Matt Hart ; us...@vm1.kannel.org Sent: Wednesday, September 30, 2009 1:02 AM Subject: RE: kannel over using SMSC API Hi Matt, So, you want to send and receive messages to multiple carriers in the US without using an aggregator? I believe you would need to go to www.usshortcodes.com and reserve a short code. This would be reserved on all US based carriers who participate (I believe that is all of the major ones). You would then have to go to TMO, ATT, Verizon, etc. and setup accounts and pricing and the whole deal. I am willing to bet that the pricing they give you as a small user will be far more expensive than what they give an aggregator. Never mind the fact that setting up an SMPP client at a place like TMO (trust me, I know) can take a long time. I still would have no idea how you would keep track of which carrier to send the messages. Kent Walker Senior Wireless Network Engineer From: users-boun...@vm1.kannel.org [mailto:users-boun...@vm1.kannel.org] On Behalf Of Matt Hart Sent: Monday, September 28, 2009 9:50 PM To: us...@vm1..kannel.org Subject: Re: kannel over using SMSC API Thank you Kent , I hope to reach as many carriers as possible. I understand that aggregators and such are a service that is required and need to be paid. I would like to use kannel though, and I was wondering what this buys me over such aggregator's APIs that they offer that allow me to directly connect to their services. Do I need to do my own aggregating foot work if I wish to use kannel and a single short code? What part am I missing? Thanks again, Matt From: Kent Walker kent.wal...@jasperwireless.com To: Matt Hart covat...@yahoo.com; us...@vm1.kannel.org Sent: Wednesday, September 23, 2009 4:12:48 PM Subject: RE: kannel over using SMSC API Hello Matt, Are the destination MSISDNs for these messages all on the same carrier or are they on a variety of carriers? If you are mixing and matching US carriers, you are paying the
Re: how to use procmail to send SMS with kannel ?
Hi, Have sample scripts ? or guideline ? BR Watchara 2009/10/1 Nikos Balkanas nbalka...@gmail.com Hi, You will have to consult procmail documentation. With sendmail you can define a special recipient that will execute a script when mail is received. That script could post a message to kannel's sendsms interface. BR, Nikos - Original Message - *From:* Watchara Kangkun watchara.kang...@gmail.com *To:* users@kannel.org *Sent:* Thursday, October 01, 2009 1:14 PM *Subject:* how to use procmail to send SMS with kannel ? Hi kannel user list, I want to use mail2sms. I use sendmail and procmail. I want to use procmail to handle email Subject: Alert* and SMS this Subject to me. My kannel is can send SMS. Have someone can do that ? How I do that ? Help me please. Thank you Watchara Kangkun
Re: how to use procmail to send SMS with kannel ?
Hi, As I have suggested for that you should contact a procmail or sendmail forum (or documentation). This is off-topic for kannel. If you need to know how to do a sendsms request to kannel, read User's Guide. BR, Nikos - Original Message - From: Watchara Kangkun To: Nikos Balkanas ; users@kannel.org Sent: Thursday, October 01, 2009 7:31 PM Subject: Re: how to use procmail to send SMS with kannel ? Hi, Have sample scripts ? or guideline ? BR Watchara 2009/10/1 Nikos Balkanas nbalka...@gmail.com Hi, You will have to consult procmail documentation. With sendmail you can define a special recipient that will execute a script when mail is received. That script could post a message to kannel's sendsms interface. BR, Nikos - Original Message - From: Watchara Kangkun To: users@kannel.org Sent: Thursday, October 01, 2009 1:14 PM Subject: how to use procmail to send SMS with kannel ? Hi kannel user list, I want to use mail2sms. I use sendmail and procmail. I want to use procmail to handle email Subject: Alert* and SMS this Subject to me. My kannel is can send SMS. Have someone can do that ? How I do that ? Help me please. Thank you Watchara Kangkun
Kannel Encoding Inquiry
Hi, I am using Kannel from CVS and am trying to send an SMS message with an apostrophe. I receive the message with a \ before the apostrophe and I am not sure that is an encoding issue or not. The original message is: Mbele ng'ang'a zkdkdnrnrr And the SMSC Debug logs snippet showing the coding and the message content 2009-10-01 20:06:44 [7948] [6] DEBUG: data_coding: 241 = 0x00f1 2009-10-01 20:06:44 [7948] [6] DEBUG: sm_default_msg_id: 0 = 0x 2009-10-01 20:06:44 [7948] [6] DEBUG: sm_length: 29 = 0x001d 2009-10-01 20:06:44 [7948] [6] DEBUG: short_message: 2009-10-01 20:06:44 [7948] [6] DEBUG:Octet string at 0x81c0348: 2009-10-01 20:06:44 [7948] [6] DEBUG: len: 29 2009-10-01 20:06:44 [7948] [6] DEBUG: size: 1024 2009-10-01 20:06:44 [7948] [6] DEBUG: immutable: 0 2009-10-01 20:06:44 [7948] [6] DEBUG: data: 4d 62 65 6c 65 20 6e 67 1b 2f 27 61 6e 67 1b 2f Mbele ng./'ang./ 2009-10-01 20:06:44 [7948] [6] DEBUG: data: 27 61 20 7a 6b 64 6b 64 6e 72 6e 72 72'a zkdkdnrnrr 2009-10-01 20:06:44 [7948] [6] DEBUG:Octet string dump ends. Can someone shed the light on why this may be? Regards, Engel
Custom PDU's - Need C programmer
Title: Custom PDU's - Need C programmer How to add this custom PDU's to Kannel ? ESME_LMTBADMSG 0x0400 ESME_LMTBADCODE 0x0401 LMT_REPORT 0x0001 LMT_REPORT_RESP 0x8001 LMT_GEN_CODE 0x00010001 LMT_GEN_CODE_RESP 0x80010001 LMT_VERIFY_CODE 0x00010002 LMT_VERIFY_CODE_RESP 0x8001002 Please help, I'm not C/C++ programmer. Big thanks !
Re: Custom PDU's - Need C programmer
Custom PDU's - Need C programmerHi, What you are asking is a major undertaking. It's not worth it. Why don't you change SMSc? BR, Nikos - Original Message - From: waza...@inbox.lv To: users@kannel.org Sent: Thursday, October 01, 2009 8:45 PM Subject: Custom PDU's - Need C programmer How to add this custom PDU's to Kannel ? ESME_LMTBADMSG 0x0400 ESME_LMTBADCODE 0x0401 LMT_REPORT 0x0001 LMT_REPORT_RESP 0x8001 LMT_GEN_CODE 0x00010001 LMT_GEN_CODE_RESP 0x80010001 LMT_VERIFY_CODE 0x00010002 LMT_VERIFY_CODE_RESP 0x8001002 Please help, I'm not C/C++ programmer. Big thanks !
unsubscribe
Scott Page email: scott.p...@me.com mobile: 028 896 797 fax:09 280 3439
