kannel 1.2.0 and SMPP v3.3
Does anybody know what "SMSC returned error code 0x000a in response to submit_sm" means, using kannel 1.2.0 and connecting to a SMPP SMSC v3.3 in transmitter mode. BR Arnar
Re: kannel 1.2.0 and SMPP v3.3
Thanks, but pls. help me out, I'm using some test utility to connect to the SMSC with basically the same parameters as Kannel and I doesn't get any errors. In Kannel however, does this mean that my global-sender var is faulty or what controls this source address? TIA Arnar On Fös, 2002-07-19 at 02:59, Ignat Vassilev wrote: > Hi Arnar > > 0x000a EMSE_RINVSRCARD and means Invalid source address > > Cheerc > Ignat > > > > Arnar Gestsson wrote: > > >Does anybody know what > > > >"SMSC returned error code 0x000a in response to submit_sm" > > > >means, using kannel 1.2.0 and connecting to a SMPP SMSC v3.3 in > >transmitter mode. > > > >BR Arnar > > > > > > > > > >
Re: kannel 1.2.0 and SMPP v3.3
Thanks Ignat, this was true, at least in a sense, I needed to fiddle with the TON variable. Putting SMPP in debug mode I got 2002-07-22 01:08:01 [5] DEBUG: source_addr_ton: 2 = 0x when pushing SM to the phone, but I knew that the addr_ton should be 0( as put by configureation). What I did to proof the problem was this I changed the smpp_pdu.h such that #define GSM_ADDR_TON_NATIONAL 0x0002 was changed to #define GSM_ADDR_TON_NATIONAL 0x My question is the following, what causes the smsc_smpp to discover the number as national and how can I do this configuration in a right manner. What I was doing was telling the smpp_dpu that TON_NATIONAL was actually TON_UNKNOWN. Any suggestions, TIA Arnar On Fös, 2002-07-19 at 02:59, Ignat Vassilev wrote: > Hi Arnar > > 0x000a EMSE_RINVSRCARD and means Invalid source address > > Cheerc > Ignat > > > > Arnar Gestsson wrote: > > >Does anybody know what > > > >"SMSC returned error code 0x000a in response to submit_sm" > > > >means, using kannel 1.2.0 and connecting to a SMPP SMSC v3.3 in > >transmitter mode. > > > >BR Arnar > > > > > > > > > >
Re: kannel 1.2.0 and SMPP v3.3
Hi Arnar Sorry about my delay getting back to you but I don't work on Saturday and Sanday. You don't need to touch the source at all. Ask your SMSC guys for full config parameters. You need to receive from them someting like this: FROM SMSC In your kannel.conf IP address = host #SMSC IP addres IP Port =port#SMSC IP port number System ID=smsc-username Password =smsc-password System Type=system-type Source TON =source-addr-ton#some number 0-6 Source NPI =source-addr-npi#some number 0-6 Destination TON =dest-addr-ton#some number 0-9 Destination NPI =dest-addr-npi #some number 0-9 MSISDN =global-sender Here you are example for SMPP config group = smsc smsc = smpp interface-version = 33 smsc-id = test host = 203.13.108.18 port = 8011 receive-port = 8011 smsc-username = Futurelab8 smsc-password = testlab8 source-addr-ton = 0 source-addr-npi = 4 dest-addr-ton = 1 dest-addr-npi = 1 priority = 1 system-type = smpp address-range = "" keepalive = 0 group = smsbox bearerbox-host = localhost sendsms-port = 14013 global-sender = "0421268000" If you have some questions don't histate to contact me Arnar Gestsson wrote: >Thanks Ignat, > >this was true, at least in a sense, I needed to fiddle with the TON >variable. Putting SMPP in debug mode I got > >2002-07-22 01:08:01 [5] DEBUG: source_addr_ton: 2 = 0x > >when pushing SM to the phone, but I knew that the addr_ton should be 0( >as put by configureation). What I did to proof the problem was this I >changed the smpp_pdu.h such that > >#define GSM_ADDR_TON_NATIONAL 0x0002 > >was changed to > >#define GSM_ADDR_TON_NATIONAL 0x > >My question is the following, what causes the smsc_smpp to discover the >number as national and how can I do this configuration in a right >manner. What I was doing was telling the smpp_dpu that TON_NATIONAL was >actually TON_UNKNOWN. > >Any suggestions, > >TIA Arnar > >On Fös, 2002-07-19 at 02:59, Ignat Vassilev wrote: > >>Hi Arnar >> >>0x000a EMSE_RINVSRCARD and means Invalid source address >> >>Cheerc >>Ignat >> >> >> >>Arnar Gestsson wrote: >> >>>Does anybody know what >>> >>>"SMSC returned error code 0x000a in response to submit_sm" >>> >>>means, using kannel 1.2.0 and connecting to a SMPP SMSC v3.3 in >>>transmitter mode. >>> >>>BR Arnar >>> >>> >>> >>> >> > >
Re: kannel 1.2.0 and SMPP v3.3
Thanks Ignat, this really did "IT". BR Arnar On Mán, 2002-07-22 at 03:33, Ignat Vassilev wrote: > Hi Arnar > Sorry about my delay getting back to you but I don't work on Saturday > and Sanday. > You don't need to touch the source at all. Ask your SMSC guys for full > config parameters. > You need to receive from them someting like this: > > FROM SMSC In your kannel.conf > IP address = host > #SMSC IP addres > IP Port =port#SMSC IP port > number > System ID=smsc-username > Password =smsc-password > System Type=system-type > Source TON =source-addr-ton#some number 0-6 > Source NPI =source-addr-npi#some number 0-6 > Destination TON =dest-addr-ton#some number 0-9 > Destination NPI =dest-addr-npi #some number 0-9 > MSISDN =global-sender > > > Here you are example for SMPP config > > group = smsc > smsc = smpp > interface-version = 33 > smsc-id = test > host = 203.13.108.18 > port = 8011 > receive-port = 8011 > smsc-username = Futurelab8 > smsc-password = testlab8 > source-addr-ton = 0 > source-addr-npi = 4 > dest-addr-ton = 1 > dest-addr-npi = 1 > priority = 1 > system-type = smpp > address-range = "" > keepalive = 0 > > group = smsbox > bearerbox-host = localhost > sendsms-port = 14013 > global-sender = "0421268000" > > If you have some questions don't histate to contact me > > > Arnar Gestsson wrote: > > >Thanks Ignat, > > > >this was true, at least in a sense, I needed to fiddle with the TON > >variable. Putting SMPP in debug mode I got > > > >2002-07-22 01:08:01 [5] DEBUG: source_addr_ton: 2 = 0x > > > >when pushing SM to the phone, but I knew that the addr_ton should be 0( > >as put by configureation). What I did to proof the problem was this I > >changed the smpp_pdu.h such that > > > >#define GSM_ADDR_TON_NATIONAL 0x0002 > > > >was changed to > > > >#define GSM_ADDR_TON_NATIONAL 0x > > > >My question is the following, what causes the smsc_smpp to discover the > >number as national and how can I do this configuration in a right > >manner. What I was doing was telling the smpp_dpu that TON_NATIONAL was > >actually TON_UNKNOWN. > > > >Any suggestions, > > > >TIA Arnar > > > >On Fös, 2002-07-19 at 02:59, Ignat Vassilev wrote: > > > >>Hi Arnar > >> > >>0x000a EMSE_RINVSRCARD and means Invalid source address > >> > >>Cheerc > >>Ignat > >> > >> > >> > >>Arnar Gestsson wrote: > >> > >>>Does anybody know what > >>> > >>>"SMSC returned error code 0x000a in response to submit_sm" > >>> > >>>means, using kannel 1.2.0 and connecting to a SMPP SMSC v3.3 in > >>>transmitter mode. > >>> > >>>BR Arnar > >>> > >>> > >>> > >>> > >> > > > > > >
Re: kannel 1.2.0 and SMPP v3.3
Arnar If you haven't fixed this the Invalid source address means you need to make sure your from= parameter is correct. If your source TON was wrong you would get a 0x0048 or if your source NPI was wrong you would get a 0x0049 Make sure you get the right +countrycode format of the number or the correct capitalisation of the alphanumerics if you are using them. Alex - Original Message - From: "Ignat Vassilev" <[EMAIL PROTECTED]> To: "Arnar Gestsson" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Friday, July 19, 2002 3:59 AM Subject: Re: kannel 1.2.0 and SMPP v3.3 > Hi Arnar > > 0x000a EMSE_RINVSRCARD and means Invalid source address > > Cheerc > Ignat > > > > Arnar Gestsson wrote: > > >Does anybody know what > > > >"SMSC returned error code 0x000a in response to submit_sm" > > > >means, using kannel 1.2.0 and connecting to a SMPP SMSC v3.3 in > >transmitter mode. > > > >BR Arnar > > > > > > > > > >
RE: kannel 1.2.0 and SMPP v3.3
> If you haven't fixed this the Invalid source address means you > need to make sure your from= parameter is correct. If your source TON was > wrong you would get a 0x0048 or if your source NPI was wrong you would get a > 0x0049 it's not so .. TON and NPI can be 'correct' by itself, but contradict the number format .. if this is a case You get an error about wrong source address .. k
Re: kannel 1.2.0 and SMPP v3.3
Maybe, however lots of SMSCs use TON/NPIs which have no correlation to the source number format you are using (BT Cellnet/O2 being one of them). In this case the TON/NPI is manually overloaded (hence why I added the code to do that) and the source address can be what ever they tell you it should be. In normal operation the TOP/NPI are calculated AUTOMATICALLY based on the source address you set. Therefore unless the automatic code is wrong, or you aren't manually forcing you're TON/NPIs where you need to, then the Source Address is wrong. Alex - Original Message - From: "Kaido Karner" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, July 24, 2002 12:57 PM Subject: RE: kannel 1.2.0 and SMPP v3.3 > > If you haven't fixed this the Invalid source address means you > > need to make sure your from= parameter is correct. If your source TON was > > wrong you would get a 0x0048 or if your source NPI was wrong you would > get a > > 0x0049 > > it's not so .. TON and NPI can be 'correct' by itself, but contradict the > number format .. if this is a case You get an error about wrong source > address .. > > k >
