Re: Meta data parameters in kannel snapshot version (31/08/2010)
Hi Alwaro, I am using one of the most recent snapshots as you can see from the log below. This is i believe is 1.5. *2012-05-16 23:48:14 [10478] [0] DEBUG: Kannel bearerbox version `svn-r4974'.* Build `May 12 2012 17:14:19', compiler `4.4.4 20100726 (Red Hat 4.4.4-13)'. System Linux, release 2.6.32-71.el6.i686, version #1 SMP Wed Dec 15 09:50:18 EST 2010, machine i686. Hostname kannelgw, IP 192.168.1.34. Libxml version 2.7.6. Using OpenSSL 1.0.0-fips 29 Mar 2010. Using Oracle OCI 11.2. Using native malloc. On Wed, May 30, 2012 at 4:45 PM, Alvaro Cornejo cornejo.alv...@gmail.comwrote: What kannel version are you using? 1.4.3 does not support it. Regards Alvaro On 5/30/12, Sam nu.e...@gmail.com wrote: Hi Group, When i try to specify 'meta-data' in my config I get the error below. However in the userguide, 'meta-data' was specified as an option. 2012-05-30 15:50:47 [30833] [0] ERROR: Group 'smsc' may not contain field 'meta-data'. -- Sam -- |-| 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
Re: Meta data parameters in kannel snapshot version (31/08/2010)
Hi, meta-data is not supported in smsc group. Userguide was wrong, I just fixed it. Thanks, Alex Am 31.05.2012 um 08:52 schrieb Sam: Hi Alwaro, I am using one of the most recent snapshots as you can see from the log below. This is i believe is 1.5. 2012-05-16 23:48:14 [10478] [0] DEBUG: Kannel bearerbox version `svn-r4974'. Build `May 12 2012 17:14:19', compiler `4.4.4 20100726 (Red Hat 4.4.4-13)'. System Linux, release 2.6.32-71.el6.i686, version #1 SMP Wed Dec 15 09:50:18 EST 2010, machine i686. Hostname kannelgw, IP 192.168.1.34. Libxml version 2.7.6. Using OpenSSL 1.0.0-fips 29 Mar 2010. Using Oracle OCI 11.2. Using native malloc. On Wed, May 30, 2012 at 4:45 PM, Alvaro Cornejo cornejo.alv...@gmail.com wrote: What kannel version are you using? 1.4.3 does not support it. Regards Alvaro On 5/30/12, Sam nu.e...@gmail.com wrote: Hi Group, When i try to specify 'meta-data' in my config I get the error below. However in the userguide, 'meta-data' was specified as an option. 2012-05-30 15:50:47 [30833] [0] ERROR: Group 'smsc' may not contain field 'meta-data'. -- Sam -- |-| 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
Re: Meta data parameters in kannel snapshot version (31/08/2010)
Humm... Tnx Alex M. So where do I specify meta-data directly? I need to pass a custom parameter and value to the USSDC for authentication. N.B. I was also wondering how the initial poster of this thread got away with it in his own config. On Thu, May 31, 2012 at 8:28 AM, Alexander Malysh amal...@kannel.orgwrote: Hi, meta-data is not supported in smsc group. Userguide was wrong, I just fixed it. Thanks, Alex Am 31.05.2012 um 08:52 schrieb Sam: Hi Alwaro, I am using one of the most recent snapshots as you can see from the log below. This is i believe is 1.5. *2012-05-16 23:48:14 [10478] [0] DEBUG: Kannel bearerbox version `svn-r4974'.* Build `May 12 2012 17:14:19', compiler `4.4.4 20100726 (Red Hat 4.4.4-13)'. System Linux, release 2.6.32-71.el6.i686, version #1 SMP Wed Dec 15 09:50:18 EST 2010, machine i686. Hostname kannelgw, IP 192.168.1.34. Libxml version 2.7.6. Using OpenSSL 1.0.0-fips 29 Mar 2010. Using Oracle OCI 11.2. Using native malloc. On Wed, May 30, 2012 at 4:45 PM, Alvaro Cornejo cornejo.alv...@gmail.comwrote: What kannel version are you using? 1.4.3 does not support it. Regards Alvaro On 5/30/12, Sam nu.e...@gmail.com wrote: Hi Group, When i try to specify 'meta-data' in my config I get the error below. However in the userguide, 'meta-data' was specified as an option. 2012-05-30 15:50:47 [30833] [0] ERROR: Group 'smsc' may not contain field 'meta-data'. -- Sam -- |-| 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
Re: Meta data parameters in kannel snapshot version (31/08/2010)
you can pass meta-data as cgi parameter, header or xml tag via smsbox. Please check userguide how to do it. Thanks, Alex Am 31.05.2012 um 09:40 schrieb Sam: Humm... Tnx Alex M. So where do I specify meta-data directly? I need to pass a custom parameter and value to the USSDC for authentication. N.B. I was also wondering how the initial poster of this thread got away with it in his own config. On Thu, May 31, 2012 at 8:28 AM, Alexander Malysh amal...@kannel.org wrote: Hi, meta-data is not supported in smsc group. Userguide was wrong, I just fixed it. Thanks, Alex Am 31.05.2012 um 08:52 schrieb Sam: Hi Alwaro, I am using one of the most recent snapshots as you can see from the log below. This is i believe is 1.5. 2012-05-16 23:48:14 [10478] [0] DEBUG: Kannel bearerbox version `svn-r4974'. Build `May 12 2012 17:14:19', compiler `4.4.4 20100726 (Red Hat 4.4.4-13)'. System Linux, release 2.6.32-71.el6.i686, version #1 SMP Wed Dec 15 09:50:18 EST 2010, machine i686. Hostname kannelgw, IP 192.168.1.34. Libxml version 2.7.6. Using OpenSSL 1.0.0-fips 29 Mar 2010. Using Oracle OCI 11.2. Using native malloc. On Wed, May 30, 2012 at 4:45 PM, Alvaro Cornejo cornejo.alv...@gmail.com wrote: What kannel version are you using? 1.4.3 does not support it. Regards Alvaro On 5/30/12, Sam nu.e...@gmail.com wrote: Hi Group, When i try to specify 'meta-data' in my config I get the error below. However in the userguide, 'meta-data' was specified as an option. 2012-05-30 15:50:47 [30833] [0] ERROR: Group 'smsc' may not contain field 'meta-data'. -- Sam -- |-| 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
Re: Meta data parameters in kannel snapshot version (31/08/2010)
I have tried passing meta-data tru the cgi parameter via smsbox but the truth is the ussdc would not even allow Kannel to connect until a certain parameter and value is set at login. Thus meta-data on cgi parameter would be useless as the connection would not even be up in the first place. On Thu, May 31, 2012 at 8:58 AM, Alexander Malysh amal...@kannel.orgwrote: you can pass meta-data as cgi parameter, header or xml tag via smsbox. Please check userguide how to do it. Thanks, Alex Am 31.05.2012 um 09:40 schrieb Sam: Humm... Tnx Alex M. So where do I specify meta-data directly? I need to pass a custom parameter and value to the USSDC for authentication. N.B. I was also wondering how the initial poster of this thread got away with it in his own config. On Thu, May 31, 2012 at 8:28 AM, Alexander Malysh amal...@kannel.orgwrote: Hi, meta-data is not supported in smsc group. Userguide was wrong, I just fixed it. Thanks, Alex Am 31.05.2012 um 08:52 schrieb Sam: Hi Alwaro, I am using one of the most recent snapshots as you can see from the log below. This is i believe is 1.5. *2012-05-16 23:48:14 [10478] [0] DEBUG: Kannel bearerbox version `svn-r4974'.* Build `May 12 2012 17:14:19', compiler `4.4.4 20100726 (Red Hat 4.4.4-13)'. System Linux, release 2.6.32-71.el6.i686, version #1 SMP Wed Dec 15 09:50:18 EST 2010, machine i686. Hostname kannelgw, IP 192.168.1.34. Libxml version 2.7.6. Using OpenSSL 1.0.0-fips 29 Mar 2010. Using Oracle OCI 11.2. Using native malloc. On Wed, May 30, 2012 at 4:45 PM, Alvaro Cornejo cornejo.alv...@gmail.com wrote: What kannel version are you using? 1.4.3 does not support it. Regards Alvaro On 5/30/12, Sam nu.e...@gmail.com wrote: Hi Group, When i try to specify 'meta-data' in my config I get the error below. However in the userguide, 'meta-data' was specified as an option. 2012-05-30 15:50:47 [30833] [0] ERROR: Group 'smsc' may not contain field 'meta-data'. -- Sam -- |-| 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
Re: Meta data parameters in kannel snapshot version (31/08/2010)
Hi All, I am currently trying to specify *meta-data = *in my SMSC config but Kannel is saying I cannot specify meta-data = in the config. Please can someone advise me how to get this done? On Wed, Sep 1, 2010 at 11:25 PM, Rene Kluwen rene.klu...@chimit.nl wrote: 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: 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
Re: Meta data parameters in kannel snapshot version (31/08/2010)
What kannel version are you using? 1.4.3 does not support it. Regards Alvaro On 5/30/12, Sam nu.e...@gmail.com wrote: Hi Group, When i try to specify 'meta-data' in my config I get the error below. However in the userguide, 'meta-data' was specified as an option. 2012-05-30 15:50:47 [30833] [0] ERROR: Group 'smsc' may not contain field 'meta-data'. -- Sam -- |-| 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
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
Re: Meta data parameters in kannel snapshot version (31/08/2010)
It is the expected behaviour. What you set in config file are the instructions on how kannel should format each meta-data parameter when send it through smpp. As those are optional/special parameters not defined in kannel it need to add or not that parameter on a per message/per connection basis. 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, Sep 2, 2010 at 5:35 AM, Jan van der Vyver j...@in2one.co.za wrote: 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
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)
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: 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]
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)
?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: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
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
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: 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
