RE: Meta data parameters in kannel snapshot version (31/08/2010)
Dear Rene Thank you for the advice The following send-sms url works perfect: http://xxx.xxx.xxx.xx:13013/cgi-bin/sendsms?username=usernamepassword=passw ordmeta-data=%3Fsmpp%3Fdestination_port%3D9280text=TESTto=263734625674 So must I then conclude that kannel currently is not using the meta-data option in the config file and ignoring it? Is their a reason for this? Or is this a bug? Kind Regards Jan -Original Message- From: Rene Kluwen [mailto:rene.klu...@chimit.nl] Sent: 02 September 2010 12:25 AM To: j...@in2one.co.za; 'Alejandro Guerrieri' Cc: users@kannel.org Subject: RE: Meta data parameters in kannel snapshot version (31/08/2010) Instead of relying on Kannel's standard reply-text mechanism, you may want your php script to return nothing (empty string) in combination with omit-empty = true. Your script then does it's processing and posts the result via the sendsms-url back to Kannel, including the meta-data. == Rene -Original Message- From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Jan van der Vyver Sent: Wednesday, 01 September, 2010 23:38 To: 'Alejandro Guerrieri' Cc: users@kannel.org Subject: RE: Meta data parameters in kannel snapshot version (31/08/2010) Hi Here is the url we use to test. http://xxx.xxx.xxx.xxx:/cgi-bin/sendsms?username=usernamepassword=passw ordto=0833795999text=testmeta-data=%3Fsmpp%3Fdestination_port%3D9280 This will work to test it. But I need it to work for the following case: Receive message via smpp - kannel makes url call as configured - kannel receives result from php script - kannel send message back via smpp. Do I understand correct that the meta-data option set in my configuration below is set correct? Thank you for the help sofar. Jan From: Alejandro Guerrieri [mailto:alejandro.guerri...@gmail.com] Sent: 01 September 2010 04:53 PM To: j...@in2one.co.za Cc: Jonathan Zylberberg; users@kannel.org Subject: Re: Meta data parameters in kannel snapshot version (31/08/2010) ?smpp?destination_port=9280 must be url-encoded. Please try fixing that and post the complete url if it doesn't work, to rule out any ambiguities. Regards, Alex On Wed, Sep 1, 2010 at 4:24 PM, Jan van der Vyver j...@in2one.co.za wrote: Dear Alex We tried to create the reply by adding the following to our sendsms url meta-data=?smpp?destination_port=9280 And by just echoing the message back on the sms-service http://192.168.1.35/srs/ussd/handle.php?from=%pto=%pmessage=%rbinary=%b; type=%itime=%t Is the meta-data option in the smsc config part ignored? Kind Regards Jan From: Alejandro Guerrieri [mailto:alejandro.guerri...@gmail.com] Sent: 01 September 2010 04:10 PM To: j...@in2one.co.za Cc: Jonathan Zylberberg; users@kannel.org Subject: Re: Meta data parameters in kannel snapshot version (31/08/2010) How are you creating the reply? I guess it's using a sendsms url? Please post it. Regards, Alex On Wed, Sep 1, 2010 at 3:55 PM, Jan van der Vyver j...@in2one.co.za wrote: Dear All We are connecting to an SMSC for USSD purposes. We require to send a destination_port=9280 meta-data in the outgoing smpp pdu. We have updated the kannel to the svn checkout made on 31/08/2010. Our current config is included aswell as debug for incoming and outgoing messages. What are we configuring or doing wrong, why is the meta-data not set in the outgoing pdu. Kind Regards Jan Config: group = smsc smsc-id = USSD23 smsc = smpp host = xxx.xxx.xxx.xxx port = 2775 transceiver-mode = true smsc-username = smsc-password = system-type = service-type = address-range = meta-data = %3Fsmpp%3Fdestination_port%3D9280 my-number = 178 source-addr-autodetect = no source-addr-ton = 6 source-addr-npi = 0 interface-version = 34 group = sms-service keyword = default get-url = http://192.168.1.35/srs/ussd/handle.php?from=%pto=%pmessage=%rbinary=%b; type=%itime=%t accepted-smsc = USSD23 group = smpp-tlv name = destination_port tag = 0x020B type = integer length = 2 smsc-id = USSD23 group = smpp-tlv name = source_port tag = 0x020A type = integer length = 2 smsc-id = USSD23 INCOMING: 2010-09-01 15:48:41 [24667] [6] DEBUG: Optional parameter tag (0x020b) 2010-09-01 15:48:41 [24667] [6] DEBUG: Optional parameter length read as 2 2010-09-01 15:48:41 [24667] [6] DEBUG: Found configured optional parameter `destination_port' 2010-09-01 15:48:41 [24667] [6] DEBUG: Optional parameter tag (0x020a) 2010-09-01 15:48:41 [24667] [6] DEBUG: Optional parameter length read as 2 2010-09-01 15:48:41 [24667] [6] DEBUG: Found configured optional parameter `source_port' 2010-09-01 15:48:41 [24667] [6] DEBUG: SMPP[USSD25]: Got PDU: 2010-09-01 15:48:41 [24667] [6] DEBUG: SMPP PDU 0x12c06d0 dump: 2010-09-01 15:48:41 [24667] [6] DEBUG: type_name: deliver_sm 2010-09-01 15:48:41 [24667] [6] DEBUG: command_id: 5 = 0x0005 2010-09-01 15:48:41 [24667] [6] DEBUG: command_status: 0 = 0x 2010-09-01 15:48:41 [24667] [6] DEBUG
Meta data parameters in kannel snapshot version (31/08/2010)
Dear All We are connecting to an SMSC for USSD purposes. We require to send a destination_port=9280 meta-data in the outgoing smpp pdu. We have updated the kannel to the svn checkout made on 31/08/2010. Our current config is included aswell as debug for incoming and outgoing messages. What are we configuring or doing wrong, why is the meta-data not set in the outgoing pdu. Kind Regards Jan Config: group = smsc smsc-id = USSD23 smsc = smpp host = xxx.xxx.xxx.xxx port = 2775 transceiver-mode = true smsc-username = smsc-password = system-type = service-type = address-range = meta-data = %3Fsmpp%3Fdestination_port%3D9280 my-number = 178 source-addr-autodetect = no source-addr-ton = 6 source-addr-npi = 0 interface-version = 34 group = sms-service keyword = default get-url = http://192.168.1.35/srs/ussd/handle.php?from=%pto=%pmessage=%rbinary=%b; type=%itime=%t accepted-smsc = USSD23 group = smpp-tlv name = destination_port tag = 0x020B type = integer length = 2 smsc-id = USSD23 group = smpp-tlv name = source_port tag = 0x020A type = integer length = 2 smsc-id = USSD23 INCOMING: 2010-09-01 15:48:41 [24667] [6] DEBUG: Optional parameter tag (0x020b) 2010-09-01 15:48:41 [24667] [6] DEBUG: Optional parameter length read as 2 2010-09-01 15:48:41 [24667] [6] DEBUG: Found configured optional parameter `destination_port' 2010-09-01 15:48:41 [24667] [6] DEBUG: Optional parameter tag (0x020a) 2010-09-01 15:48:41 [24667] [6] DEBUG: Optional parameter length read as 2 2010-09-01 15:48:41 [24667] [6] DEBUG: Found configured optional parameter `source_port' 2010-09-01 15:48:41 [24667] [6] DEBUG: SMPP[USSD25]: Got PDU: 2010-09-01 15:48:41 [24667] [6] DEBUG: SMPP PDU 0x12c06d0 dump: 2010-09-01 15:48:41 [24667] [6] DEBUG: type_name: deliver_sm 2010-09-01 15:48:41 [24667] [6] DEBUG: command_id: 5 = 0x0005 2010-09-01 15:48:41 [24667] [6] DEBUG: command_status: 0 = 0x 2010-09-01 15:48:41 [24667] [6] DEBUG: sequence_number: 256475144 = 0x0f498008 2010-09-01 15:48:41 [24667] [6] DEBUG: service_type: NULL 2010-09-01 15:48:41 [24667] [6] DEBUG: source_addr_ton: 1 = 0x0001 2010-09-01 15:48:41 [24667] [6] DEBUG: source_addr_npi: 1 = 0x0001 2010-09-01 15:48:41 [24667] [6] DEBUG: source_addr: 263733529945 2010-09-01 15:48:41 [24667] [6] DEBUG: dest_addr_ton: 2 = 0x0002 2010-09-01 15:48:41 [24667] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2010-09-01 15:48:41 [24667] [6] DEBUG: destination_addr: -263178 2010-09-01 15:48:41 [24667] [6] DEBUG: esm_class: 0 = 0x 2010-09-01 15:48:41 [24667] [6] DEBUG: protocol_id: 255 = 0x00ff 2010-09-01 15:48:41 [24667] [6] DEBUG: priority_flag: 0 = 0x 2010-09-01 15:48:41 [24667] [6] DEBUG: schedule_delivery_time: NULL 2010-09-01 15:48:41 [24667] [6] DEBUG: validity_period: NULL 2010-09-01 15:48:41 [24667] [6] DEBUG: registered_delivery: 0 = 0x 2010-09-01 15:48:41 [24667] [6] DEBUG: replace_if_present_flag: 0 = 0x 2010-09-01 15:48:41 [24667] [6] DEBUG: data_coding: 1 = 0x0001 2010-09-01 15:48:41 [24667] [6] DEBUG: sm_default_msg_id: 0 = 0x 2010-09-01 15:48:41 [24667] [6] DEBUG: sm_length: 13 = 0x000d 2010-09-01 15:48:41 [24667] [6] DEBUG: short_message: 80 33507 178# 2010-09-01 15:48:41 [24667] [6] DEBUG: source_port: 0 = 0x 2010-09-01 15:48:41 [24667] [6] DEBUG: destination_port: 9280 = 0x2440 2010-09-01 15:48:41 [24667] [6] DEBUG: source_port: 0 2010-09-01 15:48:41 [24667] [6] DEBUG: destination_port: 9280 2010-09-01 15:48:41 [24667] [6] DEBUG: SMPP PDU dump ends. OUTGOING REPLY: 2010-09-01 15:48:41 [24667] [6] DEBUG: SMPP[USSD25]: Manually forced source addr ton = 6, source add npi = 0 2010-09-01 15:48:41 [24667] [6] DEBUG: SMPP[USSD25]: Sending PDU: 2010-09-01 15:48:41 [24667] [6] DEBUG: SMPP PDU 0x12c7dd0 dump: 2010-09-01 15:48:41 [24667] [6] DEBUG: type_name: submit_sm 2010-09-01 15:48:41 [24667] [6] DEBUG: command_id: 4 = 0x0004 2010-09-01 15:48:41 [24667] [6] DEBUG: command_status: 0 = 0x 2010-09-01 15:48:41 [24667] [6] DEBUG: sequence_number: 75 = 0x004b 2010-09-01 15:48:41 [24667] [6] DEBUG: service_type: 2010-09-01 15:48:41 [24667] [6] DEBUG: source_addr_ton: 6 = 0x0006 2010-09-01 15:48:41 [24667] [6] DEBUG: source_addr_npi: 0 = 0x 2010-09-01 15:48:41 [24667] [6] DEBUG: source_addr: 178 2010-09-01 15:48:41 [24667] [6] DEBUG: dest_addr_ton: 1 = 0x0001 2010-09-01 15:48:41 [24667] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2010-09-01 15:48:41 [24667] [6] DEBUG: destination_addr: 263733529945 2010-09-01 15:48:41 [24667] [6] DEBUG: esm_class: 3 = 0x0003 2010-09-01 15:48:41 [24667] [6] DEBUG: protocol_id: 0 = 0x 2010-09-01 15:48:41 [24667] [6] DEBUG: priority_flag: 0 = 0x 2010-09-01 15:48:41 [24667] [6] DEBUG: schedule_delivery_time: NULL 2010-09-01 15:48:41 [24667] [6] DEBUG: validity_period: NULL 2010-09-01 15:48:41 [24667] [6] DEBUG:
RE: Meta data parameters in kannel snapshot version (31/08/2010)
Dear Alex We tried to create the reply by adding the following to our sendsms url meta-data=?smpp?destination_port=9280 And by just echoing the message back on the sms-service http://192.168.1.35/srs/ussd/handle.php?from=%pto=%pmessage=%rbinary=%b; type=%itime=%t Is the meta-data option in the smsc config part ignored? Kind Regards Jan From: Alejandro Guerrieri [mailto:alejandro.guerri...@gmail.com] Sent: 01 September 2010 04:10 PM To: j...@in2one.co.za Cc: Jonathan Zylberberg; users@kannel.org Subject: Re: Meta data parameters in kannel snapshot version (31/08/2010) How are you creating the reply? I guess it's using a sendsms url? Please post it. Regards, Alex On Wed, Sep 1, 2010 at 3:55 PM, Jan van der Vyver j...@in2one.co.za wrote: Dear All We are connecting to an SMSC for USSD purposes. We require to send a destination_port=9280 meta-data in the outgoing smpp pdu. We have updated the kannel to the svn checkout made on 31/08/2010. Our current config is included aswell as debug for incoming and outgoing messages. What are we configuring or doing wrong, why is the meta-data not set in the outgoing pdu. Kind Regards Jan Config: group = smsc smsc-id = USSD23 smsc = smpp host = xxx.xxx.xxx.xxx port = 2775 transceiver-mode = true smsc-username = smsc-password = system-type = service-type = address-range = meta-data = %3Fsmpp%3Fdestination_port%3D9280 my-number = 178 source-addr-autodetect = no source-addr-ton = 6 source-addr-npi = 0 interface-version = 34 group = sms-service keyword = default get-url = http://192.168.1.35/srs/ussd/handle.php?from=%pto=%pmessage=%rbinary=%b; type=%itime=%t accepted-smsc = USSD23 group = smpp-tlv name = destination_port tag = 0x020B type = integer length = 2 smsc-id = USSD23 group = smpp-tlv name = source_port tag = 0x020A type = integer length = 2 smsc-id = USSD23 INCOMING: 2010-09-01 15:48:41 [24667] [6] DEBUG: Optional parameter tag (0x020b) 2010-09-01 15:48:41 [24667] [6] DEBUG: Optional parameter length read as 2 2010-09-01 15:48:41 [24667] [6] DEBUG: Found configured optional parameter `destination_port' 2010-09-01 15:48:41 [24667] [6] DEBUG: Optional parameter tag (0x020a) 2010-09-01 15:48:41 [24667] [6] DEBUG: Optional parameter length read as 2 2010-09-01 15:48:41 [24667] [6] DEBUG: Found configured optional parameter `source_port' 2010-09-01 15:48:41 [24667] [6] DEBUG: SMPP[USSD25]: Got PDU: 2010-09-01 15:48:41 [24667] [6] DEBUG: SMPP PDU 0x12c06d0 dump: 2010-09-01 15:48:41 [24667] [6] DEBUG: type_name: deliver_sm 2010-09-01 15:48:41 [24667] [6] DEBUG: command_id: 5 = 0x0005 2010-09-01 15:48:41 [24667] [6] DEBUG: command_status: 0 = 0x 2010-09-01 15:48:41 [24667] [6] DEBUG: sequence_number: 256475144 = 0x0f498008 2010-09-01 15:48:41 [24667] [6] DEBUG: service_type: NULL 2010-09-01 15:48:41 [24667] [6] DEBUG: source_addr_ton: 1 = 0x0001 2010-09-01 15:48:41 [24667] [6] DEBUG: source_addr_npi: 1 = 0x0001 2010-09-01 15:48:41 [24667] [6] DEBUG: source_addr: 263733529945 2010-09-01 15:48:41 [24667] [6] DEBUG: dest_addr_ton: 2 = 0x0002 2010-09-01 15:48:41 [24667] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2010-09-01 15:48:41 [24667] [6] DEBUG: destination_addr: -263178 2010-09-01 15:48:41 [24667] [6] DEBUG: esm_class: 0 = 0x 2010-09-01 15:48:41 [24667] [6] DEBUG: protocol_id: 255 = 0x00ff 2010-09-01 15:48:41 [24667] [6] DEBUG: priority_flag: 0 = 0x 2010-09-01 15:48:41 [24667] [6] DEBUG: schedule_delivery_time: NULL 2010-09-01 15:48:41 [24667] [6] DEBUG: validity_period: NULL 2010-09-01 15:48:41 [24667] [6] DEBUG: registered_delivery: 0 = 0x 2010-09-01 15:48:41 [24667] [6] DEBUG: replace_if_present_flag: 0 = 0x 2010-09-01 15:48:41 [24667] [6] DEBUG: data_coding: 1 = 0x0001 2010-09-01 15:48:41 [24667] [6] DEBUG: sm_default_msg_id: 0 = 0x 2010-09-01 15:48:41 [24667] [6] DEBUG: sm_length: 13 = 0x000d 2010-09-01 15:48:41 [24667] [6] DEBUG: short_message: 80 33507 178# 2010-09-01 15:48:41 [24667] [6] DEBUG: source_port: 0 = 0x 2010-09-01 15:48:41 [24667] [6] DEBUG: destination_port: 9280 = 0x2440 2010-09-01 15:48:41 [24667] [6] DEBUG: source_port: 0 2010-09-01 15:48:41 [24667] [6] DEBUG: destination_port: 9280 2010-09-01 15:48:41 [24667] [6] DEBUG: SMPP PDU dump ends. OUTGOING REPLY: 2010-09-01 15:48:41 [24667] [6] DEBUG: SMPP[USSD25]: Manually forced source addr ton = 6, source add npi = 0 2010-09-01 15:48:41 [24667] [6] DEBUG: SMPP[USSD25]: Sending PDU: 2010-09-01 15:48:41 [24667] [6] DEBUG: SMPP PDU 0x12c7dd0 dump: 2010-09-01 15:48:41 [24667] [6] DEBUG: type_name: submit_sm 2010-09-01 15:48:41 [24667] [6] DEBUG: command_id: 4 = 0x0004 2010-09-01 15:48:41 [24667] [6] DEBUG: command_status: 0 = 0x 2010-09-01 15:48:41 [24667] [6] DEBUG: sequence_number: 75 = 0x004b 2010-09-01 15:48:41 [24667] [6] DEBUG: service_type: 2010-09-01 15:48:41 [24667] [6] DEBUG
RE: Meta data parameters in kannel snapshot version (31/08/2010)
Hi Here is the url we use to test. http://xxx.xxx.xxx.xxx:/cgi-bin/sendsms?username=usernamepassword=passw ordto=0833795999text=testmeta-data=%3Fsmpp%3Fdestination_port%3D9280 This will work to test it. But I need it to work for the following case: Receive message via smpp - kannel makes url call as configured - kannel receives result from php script - kannel send message back via smpp. Do I understand correct that the meta-data option set in my configuration below is set correct? Thank you for the help sofar. Jan From: Alejandro Guerrieri [mailto:alejandro.guerri...@gmail.com] Sent: 01 September 2010 04:53 PM To: j...@in2one.co.za Cc: Jonathan Zylberberg; users@kannel.org Subject: Re: Meta data parameters in kannel snapshot version (31/08/2010) ?smpp?destination_port=9280 must be url-encoded. Please try fixing that and post the complete url if it doesn't work, to rule out any ambiguities. Regards, Alex On Wed, Sep 1, 2010 at 4:24 PM, Jan van der Vyver j...@in2one.co.za wrote: Dear Alex We tried to create the reply by adding the following to our sendsms url meta-data=?smpp?destination_port=9280 And by just echoing the message back on the sms-service http://192.168.1.35/srs/ussd/handle.php?from=%pto=%pmessage=%rbinary=%b; type=%itime=%t Is the meta-data option in the smsc config part ignored? Kind Regards Jan From: Alejandro Guerrieri [mailto:alejandro.guerri...@gmail.com] Sent: 01 September 2010 04:10 PM To: j...@in2one.co.za Cc: Jonathan Zylberberg; users@kannel.org Subject: Re: Meta data parameters in kannel snapshot version (31/08/2010) How are you creating the reply? I guess it's using a sendsms url? Please post it. Regards, Alex On Wed, Sep 1, 2010 at 3:55 PM, Jan van der Vyver j...@in2one.co.za wrote: Dear All We are connecting to an SMSC for USSD purposes. We require to send a destination_port=9280 meta-data in the outgoing smpp pdu. We have updated the kannel to the svn checkout made on 31/08/2010. Our current config is included aswell as debug for incoming and outgoing messages. What are we configuring or doing wrong, why is the meta-data not set in the outgoing pdu. Kind Regards Jan Config: group = smsc smsc-id = USSD23 smsc = smpp host = xxx.xxx.xxx.xxx port = 2775 transceiver-mode = true smsc-username = smsc-password = system-type = service-type = address-range = meta-data = %3Fsmpp%3Fdestination_port%3D9280 my-number = 178 source-addr-autodetect = no source-addr-ton = 6 source-addr-npi = 0 interface-version = 34 group = sms-service keyword = default get-url = http://192.168.1.35/srs/ussd/handle.php?from=%pto=%pmessage=%rbinary=%b; type=%itime=%t accepted-smsc = USSD23 group = smpp-tlv name = destination_port tag = 0x020B type = integer length = 2 smsc-id = USSD23 group = smpp-tlv name = source_port tag = 0x020A type = integer length = 2 smsc-id = USSD23 INCOMING: 2010-09-01 15:48:41 [24667] [6] DEBUG: Optional parameter tag (0x020b) 2010-09-01 15:48:41 [24667] [6] DEBUG: Optional parameter length read as 2 2010-09-01 15:48:41 [24667] [6] DEBUG: Found configured optional parameter `destination_port' 2010-09-01 15:48:41 [24667] [6] DEBUG: Optional parameter tag (0x020a) 2010-09-01 15:48:41 [24667] [6] DEBUG: Optional parameter length read as 2 2010-09-01 15:48:41 [24667] [6] DEBUG: Found configured optional parameter `source_port' 2010-09-01 15:48:41 [24667] [6] DEBUG: SMPP[USSD25]: Got PDU: 2010-09-01 15:48:41 [24667] [6] DEBUG: SMPP PDU 0x12c06d0 dump: 2010-09-01 15:48:41 [24667] [6] DEBUG: type_name: deliver_sm 2010-09-01 15:48:41 [24667] [6] DEBUG: command_id: 5 = 0x0005 2010-09-01 15:48:41 [24667] [6] DEBUG: command_status: 0 = 0x 2010-09-01 15:48:41 [24667] [6] DEBUG: sequence_number: 256475144 = 0x0f498008 2010-09-01 15:48:41 [24667] [6] DEBUG: service_type: NULL 2010-09-01 15:48:41 [24667] [6] DEBUG: source_addr_ton: 1 = 0x0001 2010-09-01 15:48:41 [24667] [6] DEBUG: source_addr_npi: 1 = 0x0001 2010-09-01 15:48:41 [24667] [6] DEBUG: source_addr: 263733529945 2010-09-01 15:48:41 [24667] [6] DEBUG: dest_addr_ton: 2 = 0x0002 2010-09-01 15:48:41 [24667] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2010-09-01 15:48:41 [24667] [6] DEBUG: destination_addr: -263178 2010-09-01 15:48:41 [24667] [6] DEBUG: esm_class: 0 = 0x 2010-09-01 15:48:41 [24667] [6] DEBUG: protocol_id: 255 = 0x00ff 2010-09-01 15:48:41 [24667] [6] DEBUG: priority_flag: 0 = 0x 2010-09-01 15:48:41 [24667] [6] DEBUG: schedule_delivery_time: NULL 2010-09-01 15:48:41 [24667] [6] DEBUG: validity_period: NULL 2010-09-01 15:48:41 [24667] [6] DEBUG: registered_delivery: 0 = 0x 2010-09-01 15:48:41 [24667] [6] DEBUG: replace_if_present_flag: 0 = 0x 2010-09-01 15:48:41 [24667] [6] DEBUG: data_coding: 1 = 0x0001 2010-09-01 15:48:41 [24667] [6] DEBUG: sm_default_msg_id: 0 = 0x 2010-09-01 15:48:41 [24667] [6] DEBUG: sm_length: 13 = 0x000d 2010-09-01 15:48
Routing problem
Hi All I have 2 SMPP smsc connections. 1 with rx and tx (CON1) and 1 with just tx (CON2). I want to be able to receive on the on with rx and tx and reply to each message on that one (CON1). I want to to be able to send via the other one with an http post(CON2). When I post via http the messages is send via CON1 and I want it to be send via CON2. What is wrong with my config? My configuration is as follow: group = smsbox smsbox-id = myout bearerbox-host = localhost sendsms-port = 13013 global-sender = 8605 log-file = /var/log/kannel/smsbox.log log-level = 0 access-log = /var/log/kannel/sms-access.log group = sendsms-user username = test password = blabla group = smsbox-route smsbox-id = myout shortcuts = 8605 smsc-ids = CON2 group = smsc smsc-id = CON1 smsc = smpp host = X.X.X.X port = 6200 receive-port = 6200 smsc-username = XX smsc-password = XX system-type = smpp address-range = interface-version = 34 my-number = 8605 group = smsc smsc-id = CON2 smsc = smpp host = X.X.X.X port = 6200 smsc-username = YY smsc-password = YY system-type = smpp service-type = BLA address-range = interface-version = 34 my-number = 8605 group = sms-service keyword = default accepted-smsc = CON1;CON2 text = thank you for testing. Kind Regards Jan van der Vyver
splitting of messages
Hi all I receive a sms and then get a webpage which i want to return The pages content is the following data qty kannel ignores the spaces and send data qty How can i fix this? Kind regards Jan van der Vyver
using my-number with gsm-modem
Hi I'am trying to change my number of my at modem (So that the messages that return can be routed to the correct person) my current config: group = smsc smsc = at smsc-id = WAVECOM modemtype = auto device = /dev/ttyS0 speed = 9600 pin = 0 my-number = 0831234567 This does not work. Now my question, does someone use this and does it work? Is it maby my network that is ignoring the from number in the message and is setting it to the number of the modem they receive the sms from? Kind Regards Jan van der Vyver
