Re: Destination address problem with 1.4.1

I think the issue here is that you _receive_ an SMS (pdu type is  
deliver_sm).
So the destination is whatever your SMSC sends you. The TON/NPI  
settings dont apply there.
in any case you see a +8585 number there which probably should be  
8585 (ton=0, npi=0)

the fixed settings are for submit_sm (messages you SEND using kannel)
As far as the "error" goes, I dont know why we should even check if  
the number is valid or not on incoming SMS as it might be anything.


On 14.11.2006, at 09:23, Rolandow wrote:

> Still, Kannel should "listen" to my config and set dest-addr-ton to  
> 0. Why doesn't this work? According to the PDU dump, it's still set  
> to 1. Am I missing something?
>
> Thanks in advance.
>
> Ehizogie Binitie wrote:
>> I don't think the patch is in CVS yet.
>>
>> Ehi
>>
>> Rancard Solutions Ltd.
>> web: www.rancardsolutions.com
>> email: [email protected]
>> mobile: +233.27.622.1212
>> office: +233.21.782.949
>>
>> -----Original Message-----
>> From: Rolandow [mailto:[email protected]]
>> Sent: Monday, November 13, 2006 4:20 PM
>> To: 'Kannel Development list'
>> Subject: Re: Destination address problem with 1.4.1
>>
>> Hi Stipe,
>>
>> I just updated kannel through CVS, but I am still receiving errors. I
>> don't understand why this is happenig. This is my dump:
>>
>> 2006-11-13 17:12:53 [32590] [6] DEBUG: SMPP PDU 0x81b4a10 dump:
>> 2006-11-13 17:12:53 [32590] [6] DEBUG:   type_name: deliver_sm
>> 2006-11-13 17:12:53 [32590] [6] DEBUG:   command_id: 5 = 0x00000005
>> 2006-11-13 17:12:53 [32590] [6] DEBUG:   command_status: 0 =  
>> 0x00000000
>> 2006-11-13 17:12:53 [32590] [6] DEBUG:   sequence_number: 856949 =
>> 0x000d1375
>> 2006-11-13 17:12:53 [32590] [6] DEBUG:   service_type: NULL
>> 2006-11-13 17:12:53 [32590] [6] DEBUG:   source_addr_ton: 1 =  
>> 0x00000001
>> 2006-11-13 17:12:53 [32590] [6] DEBUG:   source_addr_npi: 1 =  
>> 0x00000001
>> 2006-11-13 17:12:53 [32590] [6] DEBUG:   source_addr: "51198550378"
>> 2006-11-13 17:12:53 [32590] [6] DEBUG:   dest_addr_ton: 1 =  
>> 0x00000001
>> 2006-11-13 17:12:53 [32590] [6] DEBUG:   dest_addr_npi: 1 =  
>> 0x00000001
>> 2006-11-13 17:12:53 [32590] [6] DEBUG:   destination_addr: "8585"
>> 2006-11-13 17:12:53 [32590] [6] DEBUG:   esm_class: 0 = 0x00000000
>> 2006-11-13 17:12:53 [32590] [6] DEBUG:   protocol_id: 0 = 0x00000000
>> 2006-11-13 17:12:53 [32590] [6] DEBUG:   priority_flag: 1 =  
>> 0x00000001
>> 2006-11-13 17:12:53 [32590] [6] DEBUG:   schedule_delivery_time: NULL
>> 2006-11-13 17:12:53 [32590] [6] DEBUG:   validity_period: NULL
>> 2006-11-13 17:12:53 [32590] [6] DEBUG:   registered_delivery: 0 =  
>> 0x00000000
>> 2006-11-13 17:12:53 [32590] [6] DEBUG:   replace_if_present_flag: 0 =
>> 0x00000000
>> 2006-11-13 17:12:53 [32590] [6] DEBUG:   data_coding: 0 = 0x00000000
>> 2006-11-13 17:12:53 [32590] [6] DEBUG:   sm_default_msg_id: 0 =  
>> 0x00000000
>> 2006-11-13 17:12:53 [32590] [6] DEBUG:   sm_length: 39 = 0x00000027
>> 2006-11-13 17:12:53 [32590] [6] DEBUG:   short_message:
>> 2006-11-13 17:12:53 [32590] [6] DEBUG:    Octet string at 0x81b4b58:
>> 2006-11-13 17:12:53 [32590] [6] DEBUG:      len:  39
>> 2006-11-13 17:12:53 [32590] [6] DEBUG:      size: 40
>> 2006-11-13 17:12:53 [32590] [6] DEBUG:      immutable: 0
>> 2006-11-13 17:12:53 [32590] [6] DEBUG:      data: 44 49 4d 45 20  
>> 4b 45
>> 20 44 45 53 45 41 53 20 53   DIME KE DESEAS S
>> 2006-11-13 17:12:53 [32590] [6] DEBUG:      data: 41 42 45 52 20  
>> 44 45
>> 20 4d 49 3f 54 45 20 45 53   ABER DE MI?TE ES
>> 2006-11-13 17:12:53 [32590] [6] DEBUG:      data: 50 45 52 4f 20 4f
>> 4b                              PERO OK
>> 2006-11-13 17:12:53 [32590] [6] DEBUG:    Octet string dump ends.
>> 2006-11-13 17:12:53 [32590] [6] DEBUG: SMPP PDU dump ends.
>> 2006-11-13 17:12:53 [32590] [6] ERROR: SMPP[1]: Mallformed addr  
>> `8585',
>> expected at least 7 digits.
>>
>> As you can see, the dest-addr-ton = 1 .. although I configured it  
>> like this:
>>
>> # SMSC SMPP = SMS CENTER
>> # RX Movistar Peru
>> group = smsc
>> smsc = smpp
>> smsc-id = 1
>> denied-smsc-id = 1
>> host = 200.37.161.238
>> port = 5018
>> transceiver-mode = 1
>> smsc-username = "eMobBr_R"
>> smsc-password = "XXXX"
>> system-type = "ESME"
>> address-range = "9696"
>> my-number = 8585
>> dest-addr-ton = 0
>> dest-addr-npi = 1
>>
>> I hope somebody can help me solving this issue. Also I still  
>> receive an
>> error instead of a warning?
>>
>> Thanks in advance!
>>
>> Kind regards,
>> Roland.
>>
>>
>>
>>
>> Stipe Tolj wrote:
>>
>>> Andreas Fink wrote:
>>>
>>>
>>>>> this is correct... since it's "semantically illegal" to use a
>>>>> combination on TON=1 and addr value <7 digits. This would "mean",
>>>>> that there exist an international destination number with less  
>>>>> then
>>>>> 7 digits, there is no such in real life.
>>>>>
>>>> Stipe, I have to disagree. Some countries might have short numbers
>>>> in  the international format that way.
>>>>
>>>> Think of +49112 as the international format of the emergecny code
>>>> 112  in germany (+49). This would make 5 digits.
>>>> or +88234 as a country code which we own, we could easily make
>>>> +882345 as a pseudo international short ID with 6 digits.
>>>>
>>>> I would make this a warning, not an error.
>>>>
>>> ok, sounds reasonable, even whie I'm not "sure" if a generic PLMN
>>> shortcode (ie. 112 for emergency) can be dial from outside the home
>>> network, hence using the country code prefix plus the shortcode. Can
>>> you dial "+49112" from Switzerland? ;)
>>>
>>> I'm +0 on this... so I'll change to a warning rather then error and
>>> refusing the PDU.
>>>
>>> Stipe
>>>
>>> -------------------------------------------------------------------
>>> Kölner Landstrasse 419
>>> 40589 Düsseldorf, NRW, Germany
>>>
>>> tolj.org system architecture      Kannel Software Foundation (KSF)
>>> http://www.tolj.org/              http://www.kannel.org/
>>>
>>> mailto:st_{at}_tolj.org           mailto:stolj_{at}_kannel.org
>>> -------------------------------------------------------------------
>>>
>>>
>>>
>>
>>
>>
>>
>