Re: protocol for java box application development
Hello all ! The answer is Yes! The thing is, that it might be by summer, and don't know very well yet the licensing, because it is a thesis project. But it is for sure that eventually will be open source completely :). The status is, almost complete, I'm testing the SMSbox functionality but don't have plans to enable the WAPbox functionality in short term, but in such a case is not that big deal. I'm sending here the javadoc so you could start planning your applications in the while. Cheers! == Oscar On Wed, 2005-04-06 at 15:36, Hillel Bilman wrote: Dear Oscar, Are you going to release the Kannel's native protocol for the java box application development to the Kannel group? as I program in Java and would like to test it. Maybe you can start a project at Source Forge where you release your code and have many people that way contribute to it. Best Regards Hillel kjProtocol.tgz Description: application/compressed-tar
One doubt about box's protocol
Hi all ! I'm almost done with the first usable/lab version of Kannel's native protocol for java box application development, I just have some doubts: What do the time field is exactly ? What do the time field is for ? and how is it handled over the protocol?
Re: Kannel concatenation bug Q
Hi!
Here is the example:
I sent:
0123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789morethan160bytes
like:
http://localhost:64235/cgi-bin/sendsms?user=foo\password=bar\from=12345\to=54321\text=0123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789morethan160bytes
and by sniffing I got:
00 00 00 00 00 00 00 00 00 00 00 00 08 00 45 00 ..E.
0010 01 03 65 ee 40 00 40 06 d6 04 7f 00 00 01 7f 00 [EMAIL
PROTECTED]@.
0020 00 01 80 2c 27 11 6b cb 19 15 6c 60 58 c0 80 18 ...,'.k...l`X...
0030 7f ff b7 49 00 00 01 01 08 0a 00 03 11 1c 00 02 ...I
0040 ff 06 00 00 00 cf 00 00 00 04 00 00 00 00 00 00
0050 00 0a 00 00 01 31 32 33 34 35 00 02 01 35 34 33 .12345...543
0060 32 31 00 43 00 00 00 00 00 00 00 00 9f 05 00 03 21.C
0070 02 02 01 30 31 32 33 34 35 36 37 38 39 30 31 32 ...0123456789012
0080 33 34 35 36 37 38 39 30 31 32 33 34 35 36 37 38 3456789012345678
0090 39 30 31 32 33 34 35 36 37 38 39 30 31 32 33 34 9012345678901234
00a0 35 36 37 38 39 30 31 32 33 34 35 36 37 38 39 30 5678901234567890
00b0 31 32 33 34 35 36 37 38 39 30 31 32 33 34 35 36 1234567890123456
00c0 37 38 39 30 31 32 33 34 35 36 37 38 39 30 31 32 7890123456789012
00d0 33 34 35 36 37 38 39 30 31 32 33 34 35 36 37 38 3456789012345678
00e0 39 30 31 32 33 34 35 36 37 38 39 30 31 32 33 34 9012345678901234
00f0 35 36 37 38 39 30 31 32 33 34 35 36 37 38 39 30 5678901234567890
0100 31 32 33 34 35 36 37 38 39 30 31 32 04 26 00 01 123456789012...
0110 01 (Checkout the last 5 bytes)
for the first message , and
00 00 00 00 00 00 00 00 00 00 00 00 08 00 45 00 ..E.
0010 00 7c 65 ef 40 00 40 06 d6 8a 7f 00 00 01 7f 00 .|[EMAIL
PROTECTED]@.
0020 00 01 80 2c 27 11 6b cb 19 e4 6c 60 58 d9 80 18 ...,'.k...l`X...
0030 7f ff 5a 25 00 00 01 01 08 0a 00 03 11 1e 00 03 ..Z%
0040 11 1e 00 00 00 48 00 00 00 04 00 00 00 00 00 00 .H..
0050 00 0b 00 00 01 31 32 33 34 35 00 02 01 35 34 33 .12345...543
0060 32 31 00 43 00 00 00 00 00 00 00 00 1d 05 00 03 21.C
0070 02 02 02 33 34 35 36 37 38 39 6d 6f 72 65 74 68 ...3456789moreth
0080 61 6e 31 36 30 62 79 74 65 73an160bytes
For the second message.
As you can see, the UDH is where it sould, but there are some 5 bytes at
the end of the first message that I just cant recognize.
Thanx!
==Oscar
On Thu, 2005-01-27 at 02:27, Aarno Syvänen wrote:
Can you send an example segment ? UDH is at the beginning.
Aarno
On 26.1.2005, at 23:27, Oscar Medina Duarte wrote:
Hi
On Wed, 2005-01-26 at 04:08, Aarno Syvänen wrote:
Hi,
On 26.1.2005, at 03:04, Oscar Medina Duarte wrote:
Hi list !
I'm doing some tests with Kannel's concatenation, and there are two
things I found relevant (4 me al least).
First, messages part of a concatenated message have a 159 chars long
message body (Including headers), while IMO (cause I dont remember
that
being an issue in concatenation specs {ETSI TS 03.40 v7.5.0 @
9.2.3.24})
should/could be 160, in this case, for me it seems like we are not
using
one char per message.
Second, in all of the not last messages of a concatenated long
message, there are 5 bytes at the end that look like a IE for me,
those
are : 0x04 0x26 0x00 0x01 0x01. I dont have a clue on what that IE
looking might be, could some one please tell me?
This cannot be IE. First byte would be information element identifier,
second
information element length. So (8 byte) concatenation IE should start
with
0x00 0x03.
mhmh... OK, then, any ideas, what would those 5 bytes might be?
Kannel would not split an escaped character, so sometimes segments can
be
shorter.
I'm not escaping any chars, Im just sending plain ascii text numbers.
thanx !
==Oscar
Kannel concatenation bug Q
Hi list !
I'm doing some tests with Kannel's concatenation, and there are two
things I found relevant (4 me al least).
First, messages part of a concatenated message have a 159 chars long
message body (Including headers), while IMO (cause I dont remember that
being an issue in concatenation specs {ETSI TS 03.40 v7.5.0 @ 9.2.3.24})
should/could be 160, in this case, for me it seems like we are not using
one char per message.
Second, in all of the not last messages of a concatenated long
message, there are 5 bytes at the end that look like a IE for me, those
are : 0x04 0x26 0x00 0x01 0x01. I dont have a clue on what that IE
looking might be, could some one please tell me?
Cheers !
== Oscar
OM MANI PEME HUM
Re: UDH Headers for different manufacturers?
Hi, Here is a ethereal hex dump of a vCard created by a comercial Gateway: No. TimeSourceDestination Protocol Info 12311 369004.224536 10.0.1.5 10.0.1.204 SMPP WSP Unknown PDU type (0x45) (0x45) Frame 12311 (174 bytes on wire, 174 bytes captured) Arrival Time: Jan 11, 2005 17:38:20.619615000 Time delta from previous packet: 110.280007000 seconds Time since reference or first frame: 369004.224536000 seconds Frame Number: 12311 Packet Length: 174 bytes Capture Length: 174 bytes Ethernet II, Src: 00:0b:cd:31:a1:2b, Dst: 00:40:f4:61:36:52 Destination: 00:40:f4:61:36:52 (CameoCom_61:36:52) Source: 00:0b:cd:31:a1:2b (CompaqHp_31:a1:2b) Type: IP (0x0800) Internet Protocol, Src Addr: 10.0.1.5 (10.0.1.5), Dst Addr: 10.0.1.204 (10.0.1.204) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00) 00.. = Differentiated Services Codepoint: Default (0x00) ..0. = ECN-Capable Transport (ECT): 0 ...0 = ECN-CE: 0 Total Length: 160 Identification: 0x1008 (4104) Flags: 0x04 (Don't Fragment) 0... = Reserved bit: Not set .1.. = Don't fragment: Set ..0. = More fragments: Not set Fragment offset: 0 Time to live: 128 Protocol: TCP (0x06) Header checksum: 0xd37f (correct) Source: 10.0.1.5 (10.0.1.5) Destination: 10.0.1.204 (10.0.1.204) Transmission Control Protocol, Src Port: 1069 (1069), Dst Port: 10001 (10001), Seq: 3778, Ack: 1142, Len: 120 Source port: 1069 (1069) Destination port: 10001 (10001) Sequence number: 3778(relative sequence number) Next sequence number: 3898(relative sequence number) Acknowledgement number: 1142(relative ack number) Header length: 20 bytes Flags: 0x0018 (PSH, ACK) 0... = Congestion Window Reduced (CWR): Not set .0.. = ECN-Echo: Not set ..0. = Urgent: Not set ...1 = Acknowledgment: Set 1... = Push: Set .0.. = Reset: Not set ..0. = Syn: Not set ...0 = Fin: Not set Window size: 63019 Checksum: 0xe44b (correct) Short Message Peer to Peer, Command: Submit_sm, Seq: 112, Len: 120 Length: 120 Operation : Submit_sm (0x0004) Sequence #: 112 Service type: (Default) Type of number (originator): Unknown (0x00) Numbering plan indicator (originator): ISDN (E163/E164) (0x01) Type of number (recipient): National (0x02) Numbering plan indicator (recipient): ISDN (E163/E164) (0x01) Recipient address: 1234567890 ..00 = Messaging mode: Default SMSC mode (0x00) ..00 00.. = Message type : Default message type (0x00) 01.. = GSM features : UDHI indicator (0x01) Protocol id.: 0x00 Priority level: GSM: None ANSI-136: Bulk IS-95: Normal (0x00) Scheduled delivery time: Immediate delivery Validity period: SMSC default validity period ..00 = Delivery receipt : No SMSC delivery receipt requested (0x00) 00.. = Message type : No recipient SME acknowledgement requested (0x00) ...0 = Intermediate notif: No intermediate notification requested (0x00) ...0 = Replace : Don't replace (0x00) Data coding: 0xf5 SMPP Data Coding Scheme: Unknown (0xf5) GSM SMS Data Coding = DCS Coding Group for SMS: SMS DCS: Data coding / message class (0x0f) 01.. = DCS Character set: 8-bit data (0x01) ..01 = DCS Message class: Class 1 - ME specific (0x01) GSM CBS Data Coding = DCS Coding Group for CBS: SMS DCS: Data coding / message class (0x0f) 01.. = DCS Character set: 8-bit data (0x01) ..01 = DCS CBS Message class: Class 1 - User defined (0x01) Predefined message: 0 Message length: 77 Message GSM Short Message Service User Data UDH Length: 6 IE Id: SMS - Application port addressing scheme, 16 bit address (0x05): source port 9204, destination port 9204 Destination port: 9204 Source port: 9204 Wireless Session Protocol, Method: Unknown (0x45) (0x45) Transaction ID: 0x42 PDU Type: Unknown (0x45) 00 40 f4 61 36 52 00 0b cd 31 a1 2b 08 00 45 00 [EMAIL PROTECTED] 0010 00 a0 10 08 40 00 80 06 d3 7f 0a 00 01 05 0a 00 [EMAIL PROTECTED] 0020 01 cc 04 2d 27 11 4b 04 25 1e 8a 78 a5 88 50 18 ...-'.K.%..x..P. 0030 f6 2b e4 4b 00 00 00 00 00 78 00 00 00 04 00 00 .+.K.x.. 0040 00 00 00 00 00 70 00 00 01 00 02 01 31 32 33 34 .p..1234 0050 35 36 37 38 39 30 00 40 00 00 00 00 00 00 f5 00 [EMAIL PROTECTED] 0060 4d 06 05 04 23 f4 23 f4 42 45 47 49 4e 3a 56 43 M...#.#.BEGIN:VC 0070 41 52 44 0d 0a 56 45 52 53 49 4f 4e 3a 32 2e 31 ARD..VERSION:2.1 0080 0d 0a 4e 3a 45 6c 20 4f 73 63 61 72 0d 0a 54 45 ..N:El
Re: Something is wrong on kannel
On Wed, 2004-12-29 at 20:28, Stipe Tolj wrote: Oscar Medina Duarte wrote: Hi list ! I think something is wrong, see, I need to run smsbox and bearerbox in different computers, but happens that when ever I run smsbox -d -P configfile it just terminates ! I dont achieve a connection with my bearer with that option, unless it is in the same computer ! What can it be done to have them running in different computers? Hmm. How about debug output? I forgot to say, I got no debug info. I have debug level set, and indicated to write to a file, but I get no output. Although I can start it with no problem if I only include the -P or no switch at all. == Oscar Tashi Delek
Some things I dont like/know on Kannel
Hi folks! I've been doing some benchmarking on kannel on late days, and I'v found some thinks I feel are wrong or that I dont like in it or I dont knew of it. This tests use 3 smpp simulators to send 10, 50 bytes long messages each to kannel, and then kannel get's a url but sending no response back. I've tried several configs having the bearerbox, smsbox and apache to run on the same computer, all in diferent computers etc... The HW I use is P4 3Ghz 1mb cache with 1Gb Ram. Runing all on debian 3.1 kernel 2.4. And here are my complains: If I run smsbox in a separate computer from bearer: The -d option doesnt work (see other messages by me) The smsbox doesnt reconnect's successfully to the bearer whe reset command is issued, it only has a small delay and dies if no connection is available, different behavior should be programmed. Taking a look on the protocol used between boxes I think that a performance boost may be achieved by specifying it correctly, because although it works it has a LOT of overhead, I'm working on it right now, any way as part of my thesis work, I will have a formal paper on this in a couple of months to show you all. If I run all on the same computer, too many file descriptors are opened and smsbox doesn't handle this in a proper manner, so that many messages are just lost, instead of waiting for the system to release descriptors or something like that. Also, the gw_gethostbyname fails although It may be caused by the lack of file descriptors. Log piece: 2004-12-30 18:25:47 [18761] [9] ERROR: Error while gw_gethostbyname occurs. 2004-12-30 18:25:47 [18761] [9] ERROR: System error 1076104129: Unknown error 1076104129 2004-12-30 18:25:47 [18761] [9] ERROR: gethostbyname failed 2004-12-30 18:25:47 [18761] [9] ERROR: System error 24: Too many open files 2004-12-30 18:25:47 [18761] [9] ERROR: error connecting to server `xxx.com' at port `80' 2004-12-30 18:25:47 [18761] [9] ERROR: Couldn't send request to http://xxx/xxx.html 2004-12-30 18:25:47 [18761] [9] ERROR: Error while gw_gethostbyname occurs. 2004-12-30 18:25:47 [18761] [9] ERROR: System error 1076104129: Unknown error 1076104129 2004-12-30 18:25:47 [18761] [9] ERROR: gethostbyname failed 2004-12-30 18:25:47 [18761] [9] ERROR: System error 24: Too many open files 2004-12-30 18:25:47 [18761] [9] ERROR: error connecting to server `xxx.com' at port `80' 2004-12-30 18:25:47 [18761] [9] ERROR: Couldn't send request to http://xxx/xxx.html And this repeats for almost every message. I hate to write very long e mails like this one, I just want to know is someone is working (or will be working) on some of the issues I think I've found and what are you're opinions. I'll release the results of my testing when it is completed as well as the current protocol description (as I promised before) and a protocol recomendation in a couple of moths from now. I hope this is useful for more people than me! Cheers ! == Oscar Tashi Delek!
Something is wrong on kannel
Hi list ! I think something is wrong, see, I need to run smsbox and bearerbox in different computers, but happens that when ever I run smsbox -d -P configfile it just terminates ! I dont achieve a connection with my bearer with that option, unless it is in the same computer ! What can it be done to have them running in different computers? thanks a lot ! == Oscar
On the kannel protocol description
Hi all !
Here is the first draft of the kannel protocol, any help/comments will
be highly appreciated !
== Oscar
Tashi Delek
Kannel Protocol Description
Packet description, draft v0.1
Description by:
Oscar Medina Duarte
{moscar}[at]gmail.com
Protocol Description
This protocol has been designed with the purpose of mantaining a connection
between kannel bearerbox and another box, tipically an smsbox and/or a wapbox.
Kannel protocol session:
A session is initated when a kannel box client requests to connect to a bearer
box and sends an administration command requesting to be identified.
And finishes when the bearer box request's the client box to shutdown or reset.
During the session, both parts can request heartbeats to each other to ensure
that the link is up and to measure the round trip of packages, wich is not yet
hanled by the current implementation of the protocol.
Kannel session to a smsbox
When a smsbox has established a session, it will send and receive sms packets
wich contain a short message, a destination (MT) address, a source (MO) address
and an identification number, among other fields.
Kannel session to a wapbox
When a wap box has established a session, it will send and receive wdp datagrams
though the connection containing, the source and destination's ports and
addresses, and user data.
Protocol's Operations
Heartbeating
Sms boxing
Wap boxing
Packet BNF:
message := lenghttypepacket
packet := heartbeat_packet | admin_packet | sms_packet |
ack_packet | wdp_datagram_packet
heartbeat_packet := load
admin_packet := adm_comandboxc_id
sms_packet := senderreceiverudhdatamsgdatatime\
smsc_idserviceaccountuuidsms_type\
mclassmwicodingcompressvalidity\
deferreddlr_maskdlr_urlpidalt_dcs\
rpicharsetboxc_idbinfomsg_leftpriority
ack_packet := nacktimeuuid
wdp_datagram_packet := source_addresssource_port\
destination_addressdestination_port\
user_data
lenght := INT
type := INT
load := INT
adm_comand := INT
boxc_id := STRING
sender := STRING
receiver := STRING
udhdata := STRING
msgdata := STRING
time := INT
smsc_id := STRING
service := STRING
account := STRING
sms_type := INT
mclass := INT
mwi := INT
coding := INT
compress := INT
validity := INT
deferred := INT
dlr_mask := INT
dlr_url := STRING
pid := INT
alt_dcs := INT
rpi := INT
charset := STRING
binfo := STRING
msg_left := INT
priority := INT
nack := INT
source_address := STRING
source_port := INT
destination_address := STRING
destination_port := INT
user_data := STRING
uuid := lenghtUUID
STRING := lenghtOctetString
UUID := BYTE{16}
INT := BYTE{4}
OctetString := BYTE*
Protocol's Glossary
message .- Is the unit of data trasmited over a link in a box to box session.
packet .- Is the biggest meaningful part transmited by a box.
heartbeat_packet .- Is the kind of packet used for the heartbeating operation.
admin_packet .- Is the kind of packet used to send commands among boxes.
sms_packet .- Is the kind of packet used to transfer SMS messages.
ack_packet .- Is the packet used to send acknowledges.
wdp_datagram_packet .- Is the packet to carry wdp datagrams.
lenght .- It is the number of bytes left plus one.
type .- Is the type of packet contained in a message.
Package types:
0 = heartbeat
1 = admin
2 = sms
3 = ack
4 = wdp_datagram
5 = msg_type_count
load .-
adm_comand .- Is the command contained by an admin command.
Admin commands:
cmd_shutdown = 0
cmd_suspend = 1
cmd_resume = 2
cmd_identify = 3
cmd_restart = 4
boxc_id .- It is the client box ID
sender .- Is the address of the originating entity of an sms message.
receiver .- Is the address of the destination for an sms message
udhdata .- User Data Header.
msgdata .- Is the data contained in a sms message, generally text.
time .-
smsc_id .- Is the internal name of the smsc link that received the sms message
or the smsc link that should send the message.
service .-
account .-
sms_type .- It indicates the type of sms message.
SMS types:
mo = 0,
mt_reply = 1,
mt_push = 2,
report_mo = 3,
report_mt = 4
mclass .-
mwi .-
coding .-
compres .-
validity .-
deferred .-
dlr_mask .-
dlr_url .-
pid .-
alt_dcs .-
rpi .-
charset .- It indicates the Charset used to encode the SMS message's data
binfo .-
msg_left .-
priority .-
nack .- It indicates the ack status in a ack packet.
Ack status:
ack_success = 0,
ack_failed = 1,
ack_failed_tmp = 2,
ack_buffered = 3
source_address .- It is the originating IP address of the datagram.
source_port .- Is is the originating port of the datagram.
destination_address
Some where is the implementation ?
Hello, Just with a simple fast question for the proper guy to answer: Where is the implementation of : encode_network_long(char *, long int) thank's to all ! PS Just to let you know, I'm writing a spec of the current Kannel box protocol to allow programmers in other langs (like java) to connect to kannel as a box. == Oscar
Re: Some where is the implementation ?
Hi Stipe ! Thanx! I was searching in the wrong place jeje :). PS Just to let you know, I'm writing a spec of the current Kannel box protocol to allow programmers in other langs (like java) to connect to kannel as a box. ok, interesting. What kind of spec will it be? Will be an explanation of how the packages between boxes are coded (BNF), their meaning, how to use them, creation of a java API to read/write this kind of packages, a small testing jsmsbox, and some other work that I may not be allowed to release until some time. The API will definitely be OpenSource any way. This whole work should be finished until next Summer, it is part of my thesis work. In it, I will probably release some recommendations to make current protocol more correct, efficient, and feature enabled.
Some feature requests
Hello ! I've been fighting a lot lately with smsc routing and several production services, and i think it would be very nice - to have an option to enable or disable an smsc in a config like: smsc-enable = true | false Resulting that some connections may not be active unless specified with out the need to change files. - Another nice thing would be to have a way to start and stop smsc connections with out the need to restart the whole kannel, having that would allow us to have a live production system and safely start and stop other connections. Ok, those two are things that would be very useful for me, but there's another that before making a suggestion I would like to know what you think or if some one if already working on it. - When using http admin to restart kannel, happens sometimes that smsbox doesn't make it to reconnect successfully to the bearerbox, it currently works by waiting a few seconds to give time to the bearer to start, but is that really correct? it doesn't always works well as it happens on my system, my system would require more time, that is, by hand. I've thought of possible solutions, but they doesn't seem so correct either. I'll show them 2 u as a brainstorm: + Make smsbox try to connect several times until it makes a connection or a time out or something similar occurs. + Make smsbox do a sort of port scan to the bearer port until its open and connect to it. + Have a concertation box, that is, a box that receives all commands to bearer and/or smsbox and administers order of things and monitors how things are going to prevent errors from happening. + Let bearerbox to start explicitly the smsbox by executing it only when it is ready. Ok there's my participation as brainstorm, some ideas ?? == Oscar OM MANI PEME HUM
Re: sms service behavior
Hi again ! On Thu, 2004-10-21 at 09:57, Alexander Malysh wrote: Hi, Oscar Medina Duarte wrote: Hi all ! I still haven't got any reply about this, please help !! because such questions belongs rather to user ML... mhmh... sorry list ! It wont happen again :) == Oscar On Sat, 2004-10-16 at 11:22, Oscar Medina Duarte wrote: Hello ! I want to know what is the behavior of the smsbox in an sms service configured to do a post, I mean, when the http service is down, what would the smsbox do? Would it re-attempt until the service is up again? yes, smsbox will retry... How many times ? that is up to you, see userguide (something with `retry' in smsbox group) Is this configurable somewhere? see above... Thanx ! == Oscar
Re: sms service behavior
Hi all ! I still haven't got any reply about this, please help !! == Oscar On Sat, 2004-10-16 at 11:22, Oscar Medina Duarte wrote: Hello ! I want to know what is the behavior of the smsbox in an sms service configured to do a post, I mean, when the http service is down, what would the smsbox do? Would it re-attempt until the service is up again? How many times ? Is this configurable somewhere? thanx for you're help ! == Oscar
Problem with routing
Hi, I'm using Kannel cvs 20041006 and I have this problem: I send a message from a phone, to 2665, it gets routed correctly and a post to attend the service is called correctly, and all logs reflect it. But If I send a message to 24024, it gets routed, but the value in the %P part of the post-url in the sms-service gets wrong, is set as the other short number, that is reflected in the smsbox log, but in the access log's to field is set as it should. Kannel is configured like this: ... group = smsc smsc = smpp smsc-id = mi_te_24024 denied-smsc-id = mi_te_2665 ... group = smsc smsc = smpp smsc-id = mi_te_2665 denied-smsc-id = mi_te_24024 ... group = smsbox smsbox-id = smsbox_01 ... group = sms-service post-url = http://localhost:8080/gwin/?fromNumber=%ptoNumber=%PrawInMessage=%aoperatorGatewayId=%i; ... group = smsbox-route smsbox-id = smsbox_01 shortcuts = 2665;4378;24024 Log sample: access log: 2004-10-08 11:57:41 Receive SMS [SMSC:mi_te_24024] [SVC:] [ACT:] [BINF:] [from:2351501572] [to:24024] [flags:-1:0:-1:0:-1] [msg:5:Agmpt] [udh:0:] smsbox log: 2004-10-08 11:57:41 [4167] [9] DEBUG: Parsing URL `http://localhost:8080/gwin/?fromNumber=2351501572toNumber=2665rawInMessage=AgmptoperatorGatewayId=mi_te_24024': 2004-10-08 11:57:41 [4167] [9] DEBUG: Scheme: http:// 2004-10-08 11:57:41 [4167] [9] DEBUG: Host: daisy.micel.com 2004-10-08 11:57:41 [4167] [9] DEBUG: Port: 8080 2004-10-08 11:57:41 [4167] [9] DEBUG: Username: (null) 2004-10-08 11:57:41 [4167] [9] DEBUG: Password: (null) 2004-10-08 11:57:41 [4167] [9] DEBUG: Path: /gwin/ 2004-10-08 11:57:41 [4167] [9] DEBUG: Query: fromNumber=2351501572toNumber=2665rawInMessage=AgmptoperatorGatewayId=mi_te_24024 What is wrong here!? Can someone help me please !? Thanx in advance! == Oscar OM MANI PEME HUM
Possible bug on restart command from http
Hi! The restart command is not working here, I send the command, and it only makes it to the bearer but the smsbox doesn't, I guess is some kind of problem with the synchronization of them, perhaps smsbox should try a couple of more times to connect to the bearer, or have a delay of something else. This what I get on smsbox when I try to reset using the restart command from http admin: 2004-10-08 12:20:28 [4167] [0] INFO: Bearerbox told us to restart 2004-10-08 12:20:28 [4167] [0] INFO: Received (and handled?) 1 requests in 1367 seconds (0.00 per second) 2004-10-08 12:20:28 [4167] [0] INFO: Kannel smsbox terminating. 2004-10-08 12:20:28 [4167] [7] DEBUG: Thread 7 (gw/heartbeat.c:heartbeat_thread) terminates. 2004-10-08 12:20:28 [4167] [3] DEBUG: HTTP: No clients with requests, quitting. 2004-10-08 12:20:28 [4167] [3] DEBUG: Thread 3 (gw/smsbox.c:sendsms_thread) terminates. 2004-10-08 12:20:28 [4167] [0] DEBUG: Waiting for 2 (gwlib/http.c:server_thread) to terminate 2004-10-08 12:20:28 [4167] [2] DEBUG: Thread 2 (gwlib/http.c:server_thread) terminates. 2004-10-08 12:20:28 [4167] [1] DEBUG: Thread 1 (gwlib/fdset.c:poller) terminates. 2004-10-08 12:20:28 [4167] [0] DEBUG: Waiting for 4 (gw/smsbox.c:obey_request_thread) to terminate 2004-10-08 12:20:28 [4167] [4] DEBUG: Thread 4 (gw/smsbox.c:obey_request_thread) terminates. 2004-10-08 12:20:28 [4167] [6] DEBUG: Thread 6 (gw/smsbox.c:http_queue_thread) terminates. 2004-10-08 12:20:28 [4167] [0] DEBUG: Waiting for 5 (gw/smsbox.c:url_result_thread) to terminate 2004-10-08 12:20:28 [4167] [5] DEBUG: Thread 5 (gw/smsbox.c:url_result_thread) terminates. 2004-10-08 12:20:33 [4167] [0] DEBUG: Waiting for 9 (gwlib/http.c:write_request_thread) to terminate 2004-10-08 12:20:33 [4167] [9] DEBUG: Thread 9 (gwlib/http.c:write_request_thread) terminates. 2004-10-08 12:20:33 [4167] [8] DEBUG: Thread 8 (gwlib/fdset.c:poller) terminates. 2004-10-08 12:20:33 [4167] [0] DEBUG: Immutable octet strings: 317. 2004-10-08 12:20:33 [4456] [0] INFO: Added logfile `/opt/Kannel/concurso/logs/smsbox.log' with level `0'. 2004-10-08 12:20:33 [4456] [0] INFO: Service global sender set as '2665' 2004-10-08 12:20:33 [4456] [0] INFO: Logging accesses to '/opt/Kannel/concurso/logs/smsbox.access'. 2004-10-08 12:20:33 [4456] [0] INFO: Started access logfile `/opt/Kannel/concurso/logs/smsbox.access'. 2004-10-08 12:20:33 [4456] [0] INFO: HTTP: Opening server at port 2665. 2004-10-08 12:20:33 [4456] [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller) 2004-10-08 12:20:33 [4456] [0] DEBUG: Started thread 2 (gwlib/http.c:server_thread) 2004-10-08 12:20:33 [4456] [0] INFO: Set up send sms service at port 2665 2004-10-08 12:20:33 [4456] [0] DEBUG: Started thread 3 (gw/smsbox.c:sendsms_thread) 2004-10-08 12:20:33 [4456] [0] DEBUG: -- 2004-10-08 12:20:33 [4456] [0] DEBUG: Kannel smsbox version cvs-20041006 starting 2004-10-08 12:20:33 [4456] [1] DEBUG: Thread 1 (gwlib/fdset.c:poller) maps to pid 4456. 2004-10-08 12:20:33 [4456] [2] DEBUG: Thread 2 (gwlib/http.c:server_thread) maps to pid 4456. 2004-10-08 12:20:33 [4456] [3] DEBUG: Thread 3 (gw/smsbox.c:sendsms_thread) maps to pid 4456. 2004-10-08 12:20:33 [4456] [0] DEBUG: Started thread 4 (gw/smsbox.c:obey_request_thread) 2004-10-08 12:20:33 [4456] [0] DEBUG: Started thread 5 (gw/smsbox.c:url_result_thread) 2004-10-08 12:20:33 [4456] [0] DEBUG: Started thread 6 (gw/smsbox.c:http_queue_thread) 2004-10-08 12:20:33 [4456] [0] ERROR: connect failed 2004-10-08 12:20:33 [4456] [0] ERROR: System error 111: Connection refused 2004-10-08 12:20:33 [4456] [0] ERROR: error connecting to server `localhost' at port `26657' 2004-10-08 12:20:33 [4456] [0] PANIC: Couldn't connect to the bearerbox. 2004-10-08 12:20:33 [4456] [0] PANIC: ../../gateway/gw/smsbox(gw_panic+0x19a) [0x807f24b] 2004-10-08 12:20:33 [4456] [0] PANIC: ../../gateway/gw/smsbox(connect_to_bearerbox+0x48) [0x8060d16] 2004-10-08 12:20:33 [4456] [0] PANIC: ../../gateway/gw/smsbox(main+0x2dc) [0x805bc44] 2004-10-08 12:20:33 [4456] [0] PANIC: /lib/tls/libc.so.6(__libc_start_main+0x108) [0x402d17f8] Cheers ! == Oscar
I have a troubleshooting question
Hello My eyes can't see where the error is, I'm pretty sure is something trivial, this is what is going on : I have two smsc's configured using smpp, and I have problems with routing, here are fragments of my config: ... group = smsc smsc = smpp smsc-id = mi_te_24024 denied-smsc-id = mi_te_2665 allowed-smsc-id = mi_te_24024 preferred-smsc-id = mi_te_24024 ... group = smsc smsc = smpp smsc-id = mi_te_2665 denied-smsc-id = mi_te_24024 allowed-smsc-id = mi_te_2665 preferred-smsc-id = mi_te_2665 ... group = smsbox smsbox-id = smsbox_01 bearerbox-host = localhost sendsms-port = 2665 global-sender = 2665 ... group = smsbox-route smsbox-id = smsbox_01 shortcuts = 2665;4378;24024 ... The messages are apparently making it to the smsbox with no problem, but, when I send a message in response, I get this at the bearer: 2004-10-07 00:26:35 [31138] [14] DEBUG: boxc_receiver: got ack 2004-10-07 00:26:36 [31138] [14] DEBUG: boxc_receiver: sms received 2004-10-07 00:26:36 [31138] [14] WARNING: Cannot find SMSCConn for message to 2331451531, rejected. 2004-10-07 00:26:36 [31138] [14] WARNING: Message rejected by bearerbox, no router! 2004-10-07 00:26:36 [31138] [14] DEBUG: send_msg: sending msg to boxc: smsbox_01 Any suggestions? thanx 2 all ! == Oscar OM MANI PEME HUM
RE: Problem on bearer box
Hey hehe !! It worked ! The weird thing is that sometimes had worked in uppercase, and also, I changed the line in which admin-allow-ip field was, and that gave me a completly different error saying something like there was no core group... weird... :) Thanks ! On Tue, 2004-09-21 at 17:27, Rene Kluwen wrote: Try writing admin-allow-ip completely in lowercase. Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Oscar Medina Duarte Sent: woensdag 22 september 2004 0:21 To: Kannel Development list Subject: Problem on bearer box Heelp !! Im having this error on bearer box: 2004-09-22 00:13:33 [30405] [0] INFO: Debug_lvl = -1, log_file = none, log_lvl = 0 2004-09-22 00:13:33 [30405] [0] ERROR: Group 'core' may not contain field 'Admin-allow-ip'. 2004-09-22 00:13:33 [30405] [0] ERROR: Error found on line 23 of file `../conf/telcel_cool.conf'. 2004-09-22 00:13:33 [30405] [0] PANIC: Couldn't read configuration from `../conf/telcel_cool.conf'. 2004-09-22 00:13:33 [30405] [0] PANIC: ../../deploy/bin/bearerbox(gw_panic+0x19a) [0x80d2cc3] 2004-09-22 00:13:33 [30405] [0] PANIC: ../../deploy/bin/bearerbox(main+0x163) [0x80526a3] 2004-09-22 00:13:33 [30405] [0] PANIC: /lib/tls/libc.so.6(__libc_start_main+0x108) [0x402cb7f8] But the real problem is that my config file looks like this: group = core admin-port = 26659 admin-password = status-password = admin-deny-ip = *.*.*.* Admin-allow-ip = 127.0.0.1;200.88.23.188 smsbox-port = 26657 box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1;200.88.23.188 wdp-interface-name = * log-file = /opt/Kannel/logs/bearer.log log-level = 0 access-log = /opt/Kannel/logs/kannel.access What can be wrong ? what can I do ? is this a bug ? Thanx to all! == Oscar
Quesion about Charset usage
Hi all ! I'm experimenting problems to send and receive info in ISO-8859-1 format, now, I haven't done anything yet to properly correct it because I don't know much to start with because I'm confused ! From java, I'm posting to sendsms a phrase like : keyword_not_found, but, at my handset (Nokia3650) I get a text like keyword¿not¿found, so obviously I doing something wrong, in kannel confs I'm not specifying anything related to charsets at any place. The thing is, that I want to send and receive messages in with spanish using characters like áÁéÉíÍóÓúÚüÜñÑçÇ and other symbols like _ (underscore). I've tried some things but nothing yet seems to work fine. If some one (a latin chic@ perhaps?) would have an advice on this topic, would be highly appreciated ! Thanks a lot ! == Oscar OM MANI PEME HUM
Thesis project
Hi all, I'm looking for an interesting topic for my bachelor degree thesis, my first shot is to do something related to my work, that is, sms and protocol related... Any suggestions !?? Here is my topic candidate list so far: Kannel security Design of guidelines to deploy Kannel in a secure high risk environment, as kannel systems often have something to do with making money, these have to be run in a way to reduce risk of being successfully attacked. Hot points: Secure/proper implementation (This may include change of code or architecture to have correct practices) Configuration and preparation of a secure environment, OS selection and configuration. Kannel SMPPv5 implementation Upgrade Kannel smsc SMPP module to comply with SMPP v5. Kannel JMS gateway Make a smsjmsbox for kannel, this is to create a kannel box to allow a JMS compliant software to comunicate with kannel using an object oriented protocol. Hot points: Implementation of Kannel's internal protocol using java SMS filtering rules MO and MT billing support and accounting Contibution to a OpenSource project Kannel Web Service Gateway Make a smsWSbox for kannel, this is to create a kannel box that comunicates with other applications using a Web Service as a communication standard. Hot points: Using Web Services with native software Thanks for any reply !!! == Oscar OM MANI PEME HUM
Re: HTTP implementation/usage problems (sendsms)
Hi !
Now I know what is going on with this, was veeery simple, I was not URL
encoding the URL I was requesting from my app.
So now is working fine!
==Oscar
OM MANI PEME HUM
On Thu, 2004-08-12 at 19:50, Oscar Medina Duarte wrote:
Hi all !
I'm not sure yet if I'm doing something wrong, but I think we may have a
bug on http implementation, but is hard to explain, so please be
patient.
What am I doing?
I'm sending a sms request (MO) to a servlet, the servlet should reply
using the sendsms http interface, that is requesting a url like:
http://localhost:8080/kannel_test/KannelTest?from=222140576to=4378keyWord=ll9fscndWord=segundatheRest=todo%20lo%20demas
The related confs:
group = smsbox
bearerbox-host = localhost
sendsms-port = 64235
global-sender = 4378
reply-couldnotfetch = Contacta a soporte code 1
reply-couldnotrepresent = Contacta a soporte code 2
reply-requestfailed = Contacta a soporte code 3
reply-emptymessage = Contacta a soporte code 4
group = sms-service
keyword = default
post-url =
http://localhost:8080/kannel_test/KannelTest?from=%pto=%PkeyWord=%kscndWord=%stheRest=%r;
#accept-x-kannel-headers = true
max-messages = 0
What is the problem?
The problem is that when my java app tries to get the URL, I get an
exception like:
java.net.SocketException: Unexpected end of file from server
in the JVM, and the debug on smsbox looks like:
2004-08-12 18:30:49 [13488] [2] DEBUG: HTTP: Creating HTTPClient for
`127.0.0.1'.
2004-08-12 18:30:49 [13488] [1] DEBUG: HTTP: Destroying HTTPClient area
0x941f2c8.
2004-08-12 18:30:49 [13488] [1] DEBUG: HTTP: Destroying HTTPClient for
`127.0.0.1'.
2004-08-12 18:30:49 [13488] [2] DEBUG: HTTP: Creating HTTPClient for
`127.0.0.1'.
2004-08-12 18:30:49 [13488] [1] DEBUG: HTTP: Destroying HTTPClient area
0x941f2c8.
2004-08-12 18:30:49 [13488] [1] DEBUG: HTTP: Destroying HTTPClient for
`127.0.0.1'.
Ok, that looks like a problem at my java app, so I tried connecting to
another url with my app with no problem, thats why I partially discarded
that possibility.
The next thing that may had gone wrong was the URL creation, so I tried
with Mozilla using the url generated by my app, and it worked fine.
So, I decided to sniff and compare 3 tests:
1.- My App connecting to www.google.com :
My app sent this:
GET / HTTP/1.1
User-Agent: Java/1.4.2_03
Host: www.google.com
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: keep-alive
and received this from google:
HTTP/1.1 302 Found
Location:
http://www.google.com.mx/cxfer?c=PREF%3D:TM%3D1092355048:S%3DKFxs1Ocs1_d6SPlR
Set-Cookie:
PREF=ID=7296c503648eed6e:CR=1:TM=1092355048:LM=1092355048:S=_Z4iNjWgx73z9Dz1;
expires=Sun, 17-Jan-2038 19:14:07 GMT; path=/; domain=.google.com
Content-Type: text/html
Server: GWS/2.1
Content-Length: 207
Date: Thu, 12 Aug 2004 23:57:28 GMT
HTMLHEADTITLE302 Moved/TITLE/HEADBODY
H1302 Moved/H1
The document has moved
A
HREF=http://www.google.com.mx/cxfer?c=PREF%3D:TM%3D1092355048:S%3DKFxs1Ocs1_d6SPlR;here/A.
/BODY/HTML
No exceptions thrown, and sniffing seems quite ok to me.
2.- Mozilla connecting to the URL created by my app:
Mozila said:
GET
/cgi-bin/sendsms?username=xxxpassword=xxxto=2221401576from=4378text=mensaje
HTTP/1.1
Host: localhost:64235
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Gecko/20031030
Accept:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,*/*;q=0.1
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Kannel responded:
HTTP/1.1 202 Accepted
Server: Kannel/cvs-20040812
Content-Length: 5
Content-type: text/html
Pragma: no-cache
Cache-Control: no-cache
Sent.
And everything worked smoothly.
3.- My App sending via Kannel :
My app said:
GET
/cgi-bin/sendsms?username=xxxpassword=xxxto=2221401576from=4378text=mensaje via
http request HTTP/1.1
User-Agent: Java/1.4.2_03
Host: localhost:64235
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: keep-alive
And Kannel had nothing to say... Exception was thrown and the problem I
explained before.
Flags at TCP level :
myApp [SYN]
Kannel [SYN, ACK]
myApp [ACK]
myApp [PSH, ACK] Here goes the HTTP request
{
Kannel [ACK]
Kannel [FIN, ACK]
instead of:
Kannel [ACK]
Kannel [PSH, ACK] HTTP response from kannel
}
...
I'm not very http literate, but I see no reason for kannel to reject my
connection from my java app, there are some obvious differences from the
Mozilla version of the request to java's request, but, should that be an
issue for Kannel?
BTW: the piece of code I'm connecting with at my java app is :
... some code ...
// At this point sb.toString returns the full URL to connect to
url
Re: Using regex
On Mon, 2004-08-09 at 07:42, Stipe Tolj wrote: Oscar Medina Duarte wrote: Hello my kannel e-friends ! I'm doing some testing on kannel 1.3.2 in order to put it to deploy services in the real world, but, I have a doubt, I want to use keyword-regex to differentiate two (and more) services, because, the messages arrive from my Operator with a prefix, lets say pm4s, so if I have 2 services, one named puebla and the other cholula, the request to those would be something like : pm4s puebla and pm4s cholula I tried this on kannel: 8--- group = sms-service keyword = pm4s keyword-regex = ^(pm4s)[ ]+(puebla) text = de bolas catch-all = true group = sms-service keyword = pm4s keyword-regex = ^(pm4s)[ ]+(cholula) get-url = http://%S; 8- But only puebla service is recognized, even if I send a pm4s message the puebla service is triggered. I tought that was because both have keyword = pm4s, so I tried without the keyword config, but smsbox wouldnt start. Could be a good idea to base a service in a keyword-regex or a keyword and not necessarily both, that would be a nice feature! Cheers ! == Oscar OM MANI PEME HUM now, obiously you are mis-using the 'keyword' directive here, IMO. Because you have in both(!) groups the 'keyword = pm4s', this will cause smsbox to catch always the first group, which is exactly the behaviour that you are experiencing. I guess you have to leavce away(/comment out) the 'keyword = pm4s' from both(!) blocks. I've tried with out the keyword directive in both cases, but smsbox doesnt like it that way: 2004-08-12 17:10:24 [12956] [0] DEBUG: Kannel smsbox version cvs-20040812 starting 2004-08-12 17:10:24 [12956] [0] ERROR: Group 'sms-service' must include 'keyword'. 2004-08-12 17:10:24 [12956] [0] ERROR: Couldn't create a URLTranslation. 2004-08-12 17:10:24 [12956] [0] PANIC: urltrans_add_cfg failed 2004-08-12 17:10:24 [12956] [0] PANIC: gw/smsbox(gw_panic+0x175) [0x807ccd2] 2004-08-12 17:10:24 [12956] [0] PANIC: gw/smsbox(main+0x1eb) [0x805ab89] 2004-08-12 17:10:24 [12956] [0] PANIC: /lib/tls/libc.so.6(__libc_start_main+0xf0) [0x5ef750] 2004-08-12 17:10:24 [12956] [0] PANIC: gw/smsbox(SSL_write+0x41) [0x8050b29] Any other suggestion someone ? I think kannel should accept an sms-service group with only keyword-regex to work, is this correct? thanks! == Oscar
Is this a bug or mis usage?
Hi again all... (Damn, I'm starting to feel attached to all of you guys !! My girlfriend left, and workaholicsm and a mail list makes good partner... ) Ok, back to the real message, I have a service like this: group = sms-service keyword = test post-url = http://localhost:8080/kannel_test/KannelTest?from=%pto=%PkeyWord=%kscndWord=%stheRest=%r; accept-x-kannel-headers = true max-messages = 3 and Im trying to read the X-Kannel-From header thing, but kannel is not sending it !! I first thought it was something in my code, but then I sniffed it and the was no X-Kannel-From header at all. Is something wrong with my config or we need to patch again? Thanks to all ! == Oscar OM MANI PEME HUM
Re: Is this a bug or mis usage?
and Im trying to read the X-Kannel-From header thing, but kannel is not sending it !! Er, it should be in the from parameter delivered by POST Yes, it actually is, but I think that the header should have it also. According to what I understood from the manual... I first thought it was something in my code, but then I sniffed it and the was no X-Kannel-From header at all. Is something wrong with my config or we need to patch again? I have to ask the obvious question, which version are you using? Have to tried the latest CVS snapshot? That is usually considered the most stable. Yeah of course, I forgot it, I'm using today's snapshot.
XML-post, X-Kannel headers...
Hi all !! I'm not completely sure how to use HTTP Posts with Kannel, I'm working specially with Java Servlets for that purpose if someone had any examples on how to do this (specially is they are in Java) it would be really great to give them a look !!! Thanks to all ! == Oscar
RE: SMPP implementation bug?
Oups !! Sorry I think I didn't explain myself correctly I should practice my english a bit more, those modifications where to make Logica's Simulator more use full for me, not to b able connect to it. Although there still a bug in Kannel's smpp impl when handling NULL srcaddr in DeliverSM al least... Cheers !! == Oscar On Mon, 2004-07-19 at 15:52, Hillel Bilman wrote: Hi, What modifications did you need to get Kannel to connect to the Logica's SMSC Simulator v 1.1? I'd like to test. Thanks -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Oscar Medina Duarte Sent: Friday, July 16, 2004 4:51 PM To: [EMAIL PROTECTED] Subject: SMPP implementation bug? Hi all ! I think a have a small bug here, when an smsc sends a DeliverSM pdu to the gateway, with the fields, source_adde and destination_addr set to NULL, the bearerbox crashes with the following logs: 2004-07-16 18:39:20 [15969] [6] PANIC: gwlib/octstr.c:2326: seems_valid_real: Assertion `ostr != NULL' failed. (Called from gwlib/octstr.c:807:octstr_check_range.) 2004-07-16 18:39:20 [15969] [6] PANIC: ./bearerbox(gw_panic+0x175) [0x80c8501] 2004-07-16 18:39:20 [15969] [6] PANIC: ./bearerbox [0x80ce67f] 2004-07-16 18:39:20 [15969] [6] PANIC: ./bearerbox(octstr_check_range+0x26) [0x80caaa3] 2004-07-16 18:39:20 [15969] [6] PANIC: ./bearerbox [0x807fecb] 2004-07-16 18:39:20 [15969] [6] PANIC: ./bearerbox [0x8081e9f] 2004-07-16 18:39:20 [15969] [6] PANIC: ./bearerbox [0x8082da9] 2004-07-16 18:39:20 [15969] [6] PANIC: ./bearerbox [0x80be000] 2004-07-16 18:39:20 [15969] [6] PANIC: /lib/tls/libpthread.so.0 [0x86879c] 2004-07-16 18:39:20 [15969] [6] PANIC: /lib/tls/libc.so.6(__clone+0x5a) [0x6b527a] Instead of PANIC there should be proper handling of this king of messages according to SMPP v 0x34. Or perhaps I'm misunderstanding some config file spot, so here I'm also sending the config file: group = core admin-port = 6669 admin-password = f00bar status-password = f00bar admin-deny-ip = *.*.*.* admin-allow-ip = 127.0.0.1 smsbox-port = 6667 # wapbox-port = 6668 box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 wdp-interface-name = * log-file = kannel.log log-level = 1 access-log = kannel.access group = smsbox bearerbox-host = localhost sendsms-port = 64235 global-sender = 64235 group = smsc smsc = smpp host = 127.0.0.1 port = transceiver-mode = true smsc-username = pavel smsc-password = wpsd system-type = VMA interface-version = 0x34 enquire-link-interval = 60 max-pending-submits = 10 reconnect-delay = 30 source-addr-ton = 0 source-addr-npi = 1 source-addr-autodetect = true dest-addr-ton = 0 dest-addr-npi = 2 group = sms-service keyword = de text = de bolas catch-all = true group = sms-service keyword = default text = No se que quieres ! group = sms-service keyword = www get-url = http://%S; group = sendsms-user username = foo password = bar What should I do to correct this !?? Note: The log was generated by Kannel 1.3.2 When I use stable Kannel 1.2.1, it doesnt generate any log file info, but it just dont completes the service transaction. I performed those tests using Logica's Open SMPP API v 1.3 and Logica's SMSC Simulator v 1.1, with few modifications. Thank to all for you're valuable info and help !!! == Oscar OM MANI PEME HUM
SMPP implementation bug?
Hi all ! I think a have a small bug here, when an smsc sends a DeliverSM pdu to the gateway, with the fields, source_adde and destination_addr set to NULL, the bearerbox crashes with the following logs: 2004-07-16 18:39:20 [15969] [6] PANIC: gwlib/octstr.c:2326: seems_valid_real: Assertion `ostr != NULL' failed. (Called from gwlib/octstr.c:807:octstr_check_range.) 2004-07-16 18:39:20 [15969] [6] PANIC: ./bearerbox(gw_panic+0x175) [0x80c8501] 2004-07-16 18:39:20 [15969] [6] PANIC: ./bearerbox [0x80ce67f] 2004-07-16 18:39:20 [15969] [6] PANIC: ./bearerbox(octstr_check_range+0x26) [0x80caaa3] 2004-07-16 18:39:20 [15969] [6] PANIC: ./bearerbox [0x807fecb] 2004-07-16 18:39:20 [15969] [6] PANIC: ./bearerbox [0x8081e9f] 2004-07-16 18:39:20 [15969] [6] PANIC: ./bearerbox [0x8082da9] 2004-07-16 18:39:20 [15969] [6] PANIC: ./bearerbox [0x80be000] 2004-07-16 18:39:20 [15969] [6] PANIC: /lib/tls/libpthread.so.0 [0x86879c] 2004-07-16 18:39:20 [15969] [6] PANIC: /lib/tls/libc.so.6(__clone+0x5a) [0x6b527a] Instead of PANIC there should be proper handling of this king of messages according to SMPP v 0x34. Or perhaps I'm misunderstanding some config file spot, so here I'm also sending the config file: group = core admin-port = 6669 admin-password = f00bar status-password = f00bar admin-deny-ip = *.*.*.* admin-allow-ip = 127.0.0.1 smsbox-port = 6667 # wapbox-port = 6668 box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 wdp-interface-name = * log-file = kannel.log log-level = 1 access-log = kannel.access group = smsbox bearerbox-host = localhost sendsms-port = 64235 global-sender = 64235 group = smsc smsc = smpp host = 127.0.0.1 port = transceiver-mode = true smsc-username = pavel smsc-password = wpsd system-type = VMA interface-version = 0x34 enquire-link-interval = 60 max-pending-submits = 10 reconnect-delay = 30 source-addr-ton = 0 source-addr-npi = 1 source-addr-autodetect = true dest-addr-ton = 0 dest-addr-npi = 2 group = sms-service keyword = de text = de bolas catch-all = true group = sms-service keyword = default text = No se que quieres ! group = sms-service keyword = www get-url = http://%S; group = sendsms-user username = foo password = bar What should I do to correct this !?? Note: The log was generated by Kannel 1.3.2 When I use stable Kannel 1.2.1, it doesnt generate any log file info, but it just dont completes the service transaction. I performed those tests using Logica's Open SMPP API v 1.3 and Logica's SMSC Simulator v 1.1, with few modifications. Thank to all for you're valuable info and help !!! == Oscar OM MANI PEME HUM
