Hi Falko,

This is strange, because I bind the same client from another gateway and it
works perfectly. SMSC behaves normally

On Tue, Mar 3, 2009 at 4:12 PM, Falko Ziemann <fal...@gmail.com> wrote:

> LOOK at this:
>
> 2009-03-02 21:16:45 [11971] [6] DEBUG: SMPP PDU 0x86ed8b0 dump:
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   type_name: deliver_sm
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   command_id: 5 = 0x00000005
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   command_status: 0 = 0x00000000
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   sequence_number: 771 = 0x00000303
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   service_type: NULL
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   source_addr_ton: 100 = 0x00000064
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   source_addr_npi: 101 = 0x00000065
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   source_addr: "mirbim"
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   dest_addr_ton: 1 = 0x00000001
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   dest_addr_npi: 1 = 0x00000001
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   destination_addr: "355672509006"
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   esm_class: 0 = 0x00000000
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   protocol_id: 1 = 0x00000001
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   priority_flag: 57 = 0x00000039
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   schedule_delivery_time: "99998"
>
> ...
>
> This is the message the SMSC passes to kannel! See: Source_addr is
> mirbim!!! There is the fault! Additionally the source_ton and npi are far
> away from anything valid, AND the source_addr is in the dest_addr field AND
> the source_addr is in the scheduled_derlivery_time field!
>
> So your SMSC-logs tell you something else: do a tcpdump (or snoop or
> wireshark or whatever) capture the package and find out what is wrong...
> It bet that your SMSC is totally messed up and kannel is right...
>
> Regards
> Falko
>
>
> Am 03.03.2009 um 15:58 schrieb Elton Hoxha:
>
> Hi Rodrigo
>
> I changed it as you said and restarted the services. After trying sending
> an MO
>
> Here is the output from SMSBOX logs
>
> 2009-03-02 21:16:45 [11979] [9] DEBUG: Parsing URL `
> http://localhost:13004/logger/logMessage?mobile_number=mirbim&short_code=%2B355672509006&text=%40&binary_text=
> ':
> 2009-03-02 21:16:45 [11979] [9] DEBUG:   Scheme: http://
> 2009-03-02 21:16:45 [11979] [9] DEBUG:   Host: localhost
> 2009-03-02 21:16:45 [11979] [9] DEBUG:   Port: 13004
> 2009-03-02 21:16:45 [11979] [9] DEBUG:   Username: (null)
> 2009-03-02 21:16:45 [11979] [9] DEBUG:   Password: (null)
> 2009-03-02 21:16:45 [11979] [9] DEBUG:   Path: /logger/logMessage
> 2009-03-02 21:16:45 [11979] [9] DEBUG:   Query:
> mobile_number=mirbim&short_code=%2B355672509006&text=%40&binary_text=
> 2009-03-02 21:16:45 [11979] [9] DEBUG:   Fragment: (null)
> 2009-03-02 21:16:45 [11979] [9] DEBUG: HTTP: Opening connection to
> `localhost:13004' (fd=26).
> 2009-03-02 21:16:45 [11979] [9] DEBUG: Socket connecting
> 2009-03-02 21:16:45 [11979] [8] DEBUG: Get info about connecting socket
> 2009-03-02 21:16:45 [11979] [8] DEBUG: Socket not connected
> 2009-03-02 21:16:45 [11979] [8] ERROR: Couldn't fetch <
> http://localhost:13004/logger/logMessage?mobile_number=mirbim&short_code=%2B355672509006&text=%40&binary_text=
> >
> 2009-03-02 21:16:45 [11979] [5] DEBUG: message length 31, sending 1
> messages
> 2009-03-02 21:16:45 [11979] [0] DEBUG: Got ACK (0) of
> ec7d8817-68a2-483b-a268-1739464cf7d5
> 2009-03-02 21:16:45 [11979] [0] DEBUG: No client - multi-send or ACK to
> pull-reply
>
>
> And from bearerbox:
>
> 2009-03-02 21:16:35 [11971] [0] INFO: MAIN: Start-up done, entering
> mainloop
> 2009-03-02 21:16:35 [11971] [6] DEBUG: Thread 6
> (gw/smsc/smsc_smpp.c:io_thread) maps to pid 11971.
> 2009-03-02 21:16:35 [11971] [7] DEBUG: Thread 7
> (gw/bb_smscconn.c:sms_router) maps to pid 11971.
> 2009-03-02 21:16:35 [11971] [6] DEBUG: SMPP[internal]: Sending PDU:
> 2009-03-02 21:16:35 [11971] [6] DEBUG: SMPP PDU 0x86ecd08 dump:
> 2009-03-02 21:16:35 [11971] [6] DEBUG:   type_name: bind_transceiver
> 2009-03-02 21:16:35 [11971] [6] DEBUG:   command_id: 9 = 0x00000009
> 2009-03-02 21:16:35 [11971] [6] DEBUG:   command_status: 0 = 0x00000000
> 2009-03-02 21:16:35 [11971] [6] DEBUG:   sequence_number: 1 = 0x00000001
> 2009-03-02 21:16:35 [11971] [6] DEBUG:   system_id: "demirbim"
> 2009-03-02 21:16:35 [11971] [6] DEBUG:   password: "demirbim"
> 2009-03-02 21:16:35 [11971] [6] DEBUG:   system_type: "demirbim"
> 2009-03-02 21:16:35 [11971] [6] DEBUG:   interface_version: 52 = 0x00000034
> 2009-03-02 21:16:35 [11971] [6] DEBUG:   addr_ton: 0 = 0x00000000
> 2009-03-02 21:16:35 [11971] [6] DEBUG:   addr_npi: 0 = 0x00000000
> 2009-03-02 21:16:35 [11971] [6] DEBUG:   address_range: "999998"
> 2009-03-02 21:16:35 [11971] [6] DEBUG: SMPP PDU dump ends.
> 2009-03-02 21:16:35 [11971] [6] DEBUG: Optional parameter tag (0x0210)
> 2009-03-02 21:16:35 [11971] [6] DEBUG: Optional parameter length read as 1
> 2009-03-02 21:16:35 [11971] [6] DEBUG: SMPP[internal]: Got PDU:
> 2009-03-02 21:16:35 [11971] [6] DEBUG: SMPP PDU 0x86ed110 dump:
> 2009-03-02 21:16:35 [11971] [6] DEBUG:   type_name: bind_transceiver_resp
> 2009-03-02 21:16:35 [11971] [6] DEBUG:   command_id: 2147483657 =
> 0x80000009
> 2009-03-02 21:16:35 [11971] [6] DEBUG:   command_status: 0 = 0x00000000
> 2009-03-02 21:16:35 [11971] [6] DEBUG:   sequence_number: 1 = 0x00000001
> 2009-03-02 21:16:35 [11971] [6] DEBUG:   system_id: "demirbim"
> 2009-03-02 21:16:35 [11971] [6] DEBUG:   sc_interface_version: 52 =
> 0x00000034
> 2009-03-02 21:16:35 [11971] [6] DEBUG: SMPP PDU dump ends.
> 2009-03-02 21:16:39 [11971] [5] INFO: Client connected from <127.0.0.1>
> 2009-03-02 21:16:39 [11971] [5] DEBUG: Started thread 8
> (gw/bb_boxc.c:function)
> 2009-03-02 21:16:39 [11971] [8] DEBUG: Thread 8 (gw/bb_boxc.c:function)
> maps to pid 11971.
> 2009-03-02 21:16:39 [11971] [8] DEBUG: Started thread 9
> (gw/bb_boxc.c:boxc_sender)
> 2009-03-02 21:16:39 [11971] [9] DEBUG: Thread 9 (gw/bb_boxc.c:boxc_sender)
> maps to pid 11971.
> 2009-03-02 21:16:45 [11971] [6] ERROR: SMPP: PDU NULL terminated string
> (service_type) longer than allowed.
> 2009-03-02 21:16:45 [11971] [6] DEBUG: SMPP[internal]: Got PDU:
> 2009-03-02 21:16:45 [11971] [6] DEBUG: SMPP PDU 0x86ed8b0 dump:
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   type_name: deliver_sm
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   command_id: 5 = 0x00000005
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   command_status: 0 = 0x00000000
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   sequence_number: 771 = 0x00000303
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   service_type: NULL
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   source_addr_ton: 100 = 0x00000064
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   source_addr_npi: 101 = 0x00000065
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   source_addr: "mirbim"
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   dest_addr_ton: 1 = 0x00000001
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   dest_addr_npi: 1 = 0x00000001
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   destination_addr: "355672509006"
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   esm_class: 0 = 0x00000000
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   protocol_id: 1 = 0x00000001
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   priority_flag: 57 = 0x00000039
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   schedule_delivery_time: "99998"
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   validity_period: NULL
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   registered_delivery: 0 =
> 0x00000000
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   replace_if_present_flag: 0 =
> 0x00000000
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   data_coding: 0 = 0x00000000
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   sm_default_msg_id: 0 = 0x00000000
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   sm_length: 1 = 0x00000001
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   short_message:
> 2009-03-02 21:16:45 [11971] [6] DEBUG:    Octet string at 0x86ee530:
> 2009-03-02 21:16:45 [11971] [6] DEBUG:      len:  1
> 2009-03-02 21:16:45 [11971] [6] DEBUG:      size: 2
> 2009-03-02 21:16:45 [11971] [6] DEBUG:      immutable: 0
> 2009-03-02 21:16:45 [11971] [6] DEBUG:      data:
> 00                                                .
> 2009-03-02 21:16:45 [11971] [6] DEBUG:    Octet string dump ends.
> 2009-03-02 21:16:45 [11971] [6] DEBUG: SMPP PDU dump ends.
> 2009-03-02 21:16:45 [11971] [6] DEBUG: SMPP[internal]: Sending PDU:
> 2009-03-02 21:16:45 [11971] [6] DEBUG: SMPP PDU 0x86ee558 dump:
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   type_name: deliver_sm_resp
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   command_id: 2147483653 =
> 0x80000005
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   command_status: 0 = 0x00000000
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   sequence_number: 771 = 0x00000303
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   message_id: NULL
> 2009-03-02 21:16:45 [11971] [6] DEBUG: SMPP PDU dump ends.
> 2009-03-02 21:16:45 [11971] [9] DEBUG: send_msg: sending msg to box:
> <127.0.0.1>
> 2009-03-02 21:16:45 [11971] [9] DEBUG: boxc_sender: sent message to
> <127.0.0.1>
> 2009-03-02 21:16:45 [11971] [8] DEBUG: boxc_receiver: got ack
> 2009-03-02 21:16:45 [11971] [8] DEBUG: boxc_receiver: sms received
> 2009-03-02 21:16:45 [11971] [8] DEBUG: send_msg: sending msg to box:
> <127.0.0.1>
> 2009-03-02 21:16:45 [11971] [6] DEBUG: SMPP[internal]: Sending PDU:
> 2009-03-02 21:16:45 [11971] [6] DEBUG: SMPP PDU 0x86ee530 dump:
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   type_name: submit_sm
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   command_id: 4 = 0x00000004
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   command_status: 0 = 0x00000000
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   sequence_number: 2 = 0x00000002
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   service_type: NULL
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   source_addr_ton: 1 = 0x00000001
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   source_addr_npi: 1 = 0x00000001
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   source_addr: "355672509006"
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   dest_addr_ton: 2 = 0x00000002
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   dest_addr_npi: 1 = 0x00000001
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   destination_addr: "mirbim"
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   esm_class: 3 = 0x00000003
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   protocol_id: 0 = 0x00000000
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   priority_flag: 0 = 0x00000000
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   schedule_delivery_time: NULL
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   validity_period: NULL
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   registered_delivery: 0 =
> 0x00000000
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   replace_if_present_flag: 0 =
> 0x00000000
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   data_coding: 0 = 0x00000000
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   sm_default_msg_id: 0 = 0x00000000
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   sm_length: 31 = 0x0000001f
> 2009-03-02 21:16:45 [11971] [6] DEBUG:   short_message:
> 2009-03-02 21:16:45 [11971] [6] DEBUG:    Octet string at 0x86eed60:
> 2009-03-02 21:16:45 [11971] [6] DEBUG:      len:  31
> 2009-03-02 21:16:45 [11971] [6] DEBUG:      size: 32
> 2009-03-02 21:16:45 [11971] [6] DEBUG:      immutable: 0
> 2009-03-02 21:16:45 [11971] [6] DEBUG:      data: 43 6f 75 6c 64 20 6e 6f
> 74 20 66 65 74 63 68 20   Could not fetch
> 2009-03-02 21:16:45 [11971] [6] DEBUG:      data: 63 6f 6e 74 65 6e 74 2c
> 20 73 6f 72 72 79 2e      content, sorry.
> 2009-03-02 21:16:45 [11971] [6] DEBUG:    Octet string dump ends.
> 2009-03-02 21:16:45 [11971] [6] DEBUG: SMPP PDU dump ends.
>
>
>
>
> On Tue, Mar 3, 2009 at 3:46 PM, Remon <re...@interact.mobi> wrote:
>
>>  Hello there,
>>
>>
>> I’m gonna guide you on sms services
>>
>>
>> First to test your setup please configure only one sms service group as
>> follows
>>
>>
>> group = sms-service
>>
>> keyword = default
>>
>> get-url = “
>> http://localhost/logger/logMessage?mobile_number=%p&short_code=%P&text=%b&binary_text=%s
>> "
>>
>>
>>
>> Please make sure the URL will log all received parameters.
>>
>>
>> Now if kannel receives SMS message from SMSC (MO Message) sent from mobile
>> then kannel will send these parameters to the URL configured above.
>>
>>
>> Please check this and send me back.
>>
>>
>> Regards,
>>
>> Remon
>>
>>
>>
>>
>>
>> *From:* users-boun...@kannel.org [mailto:users-boun...@kannel.org] *On
>> Behalf Of *Elton Hoxha
>> *Sent:* Tuesday, March 03, 2009 4:27 PM
>> *To:* Rodrigo Cremaschi
>>
>> *Cc:* users@kannel.org
>> *Subject:* Re: SMS-SERVICE
>>
>>
>>
>> Hi Rodrigo,
>>
>>
>> I`m reading the guide several times, and what I want now its the basic
>> service, just to send and receive MO-MT SMS using Kannel. I have set the
>> SMPP connections already and there is no problem with binding issues between
>> kannel and SMPP Server.
>> I`m able to send from tha application to mobile, but I cannot vice versa,
>> from mobile to application.
>>
>> In the guide at the SMS-SERVICE configuration section, it writes:
>>
>> *Now that you have an SMS center connection to send and receive SMS
>> messages you need to define services for incoming message*s
>>
>> But after many many many tries, im not able to receive
>>
>> Here is the conf file. All the blocks are understandable except
>> SMS-SERVICE one that looks a bit ambigous.
>>
>> group = core
>> admin-port = 13000
>> smsbox-port = 13002
>> admin-password = bar
>> log-file = "/tmp/kannel.log"
>> log-level = 0
>> box-deny-ip = "*.*.*.*"
>> box-allow-ip = "127.0.0.1"
>> access-log = "/tmp/access.log"
>>
>> group=smsc
>> smsc=smpp
>> smsc-id=internal
>> interface-version=34
>> host=10.234.252.80
>> port=3700
>> system-id=demirbim
>> smsc-password=demirbim
>> system-type=demirbim
>> transceiver-mode=1
>> address-range=999998
>>
>>
>> group = smsbox
>> bearerbox-host = 127.0.0.1
>> sendsms-port = 13014
>> log-level = 0
>>
>> group = sendsms-user
>> username = b
>> password = b
>>
>> group = sms-service
>> keyword = default
>> text = "test"
>> faked-sender = 999998
>> catch-all = true
>>
>>
>> Thanks
>>
>> On Tue, Mar 3, 2009 at 3:18 PM, Rodrigo Cremaschi <
>> rodrigo.cremas...@gmail.com> wrote:
>>
>> HEllo Elton,
>>
>> The userguide is not perfect, it's not complete, and it's not foolproof.
>> You are right.
>> But take some more time reading it, explore the web, use Google, write
>> and test some configurations for yourself, read the mail archives and
>> you will be rewarded with a working Kannel.
>> If, in spite of all this, you find yourself in trouble to make Kannel
>> work, come back with your config files, log excerpts and the list will
>> try to help you.
>>
>> Best regards,
>> Rodrigo.
>>
>>
>> On Tue, Mar 3, 2009 at 12:03 PM, Elton Hoxha <elt...@gmail.com> wrote:
>> > I have it but its confusing a bit
>> >
>> > On Tue, Mar 3, 2009 at 2:59 PM, Davor Spasoski
>> > <davor.spaso...@cosmofon.com.mk> wrote:
>> >>
>> >> Do you have a manual?
>> >>
>> >> ________________________________
>> >>
>> >> From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On
>> Behalf
>> >> Of Elton Hoxha
>> >> Sent: Tuesday, March 03, 2009 2:44 PM
>> >> To: users@kannel.org
>> >> Subject: SMS-SERVICE
>> >>
>> >>
>> >>
>> >> Hi,
>> >>
>> >> Can anyone please explain me the functionality of this group? I read
>> the
>> >> guide already but again I have some ambiguities.
>> >> What the keyword parameter is used for?
>> >> The text parameter, is it used for predefined reply when the sender
>> sends
>> >> a SMS to a voting service for example.
>> >>
>> >> Please anyone explain with few words these parameters?
>> >> send-url, get-url, dlr-url
>> >>
>> >> Thanks
>> >>
>> >> COSMOFON - Mobile Telecommunications Services - A.D. Skopje
>> >> _______________________________________________________________
>> >> This e-mail (including any attachments) is confidential and may be
>> >> protected by legal privilege. If you are not the intended recipient,
>> you
>> >> should not copy it, re-transmit it, use it or disclose its contents,
>> but
>> >> should return it to the sender immediately and delete your copy from
>> your
>> >> system. Any unauthorized use or dissemination of this message in whole
>> or in
>> >> part is strictly prohibited. Please note that e-mails are susceptible
>> to
>> >> change. COSMOFON A.D. Skopje shall not be liable for the improper or
>> >> incomplete transmission of the information contained in this
>> communication
>> >> nor for any delay in its receipt or damage to your system.
>> >
>>
>>
>
>
>

Reply via email to