Re: Setting DCS field
Very strange. Your operator see DCS = 0x15 [0001 0101].
DCS = 0x15
7654 3210 -- Bit column
0001 0101
||++--- Message Class 1 (to ME)
||
++- 8-bit data
|||+ Message Class stored in DCS
|||
||+- Uncompressed Text
||
++-- Only bits 0 to 5 are relevant
To me, this implies that it's just an 8-bit binary SMS. Had the
6th bit been set, it would have indicated that the SMS should be
deleted after reading (which would fit the behavior you exhibited).
Now, looking into the code of v1.3.1 for two of the SMSC client
implementations (AT2 and SMPP) indicates that the DCS field should
be set properly:
AT2 SMSC:
gateway/gw/smsc/smsc_at2.c:at2_pdu_encode()
:
octstr_append_char(buffer, fields_to_dcs(msg, /* data coding scheme */
(msg->sms.alt_dcs ? 2 - msg->sms.alt_dcs : privdata->alt_dcs)));
SMPP SMSC:
gateway/gw/smsc/smsc_smpp.c:msg_to_pdu()
:
pdu->u.submit_sm.data_coding = fields_to_dcs(msg, (msg->sms.alt_dcs ?
2 - msg->sms.alt_dcs : smpp->alt_dcs));
Setting DCS field function:
gateway/gw/sms.c:fields_to_dcs()
:
/* Non-MWI */
else {
/* mode 0 */
if (mode == 0 || msg->sms.coding == DC_UCS2 || msg->sms.compress) {
/* bits 7,6 are 0 */
if (msg->sms.compress)
dcs |= 0x20; /* sets bit 5 */
if (msg->sms.mclass)
dcs |= 0x10 | (msg->sms.mclass - 1); /* sets bit 4,1,0 */
if (msg->sms.coding)
dcs |= ((msg->sms.coding - 1) << 2); /* sets bit 3,2 */
}
/* mode 1 */
else {
dcs |= 0xF0; /* sets bits 7-3 */
dcs |= (msg->sms.coding - 1) << 2; /* only DC_7BIT or DC_8BIT, sets
bit 2*/
if (msg->sms.mclass == 0)
dcs |= 1; /* sets bit 1,0 */
else
dcs |= (msg->sms.mclass - 1); /* sets bit 1,0 */
}
}
return dcs;
Now, based on this code, in the fields_to_dcs(), the only way to set
the 4th bit is if:
1) alt-dcs = 2
or
2) coding = 3 (DCS_UCS2)
or
3) compress = 1
If "compress = 1" turned on the 4th bit, then the 5th bit would be on
as well. Since this is not the case, we can rule out that possibility.
If "coding = 3" turned on the 4th bit, then bit 3 and 2 would be 10,
which it is not, currently.
This leads me to believe either:
1) "alt-dcs = 2" occured in the sendsms procedure or
2) alt-dcs was not passed AND the either no "alt-dcs" is delcared
in your "group = smsc" definition or "alt-dcs = 2" is in your
"group = smsc" declaration
Can you check your Kannel v1.3.1 smsbox logs to verify that the
MT SMS you sent had a "alt-dcs=1" as a CGI parameter or
"X-Kannel-Alt-DCS: 1" in the HTTP optional headers (with
"accept-x-kannel-headers = true" in your sms-services group declaration
if the SMS is a response to an MO SMS from the user).
See ya...
d.c.
**>From: "J. Kizito" <[EMAIL PROTECTED]>
**>To: users@kannel.org
**>Subject: Re: Setting DCS field
**>Date: Wed, 16 Feb 2005 14:56:54 +0100
**>
**>I have tried alt-dcs=1, coding=2 and mclass=2 but when we run a trace at the
**>SMS-C, we realize that this results in DCS=0x15 (00010101) instead of 0xF5
**>(0101) implying that the left most three bits have not been set. Is
there
**>a way I can ensure they are also set to '1'? Looks like they are not used
**>anyway however with 0x15, the message (logo) can be displayed on the phone
**>but can not be saved.
**>J.
**>
**>On Tuesday 15 February 2005 06:06, Davy Chan wrote:
**>> **>From: "J. Kizito" <[EMAIL PROTECTED]>
**>> **>To: users@kannel.org
**>> **>Subject: Setting DCS field
**>> **>Date: Mon, 14 Feb 2005 14:25:33 +0100
**>> **>User-Agent: KMail/1.7.92
**>> **>
**>> **>Hi list,
**>> **>I am using kannel 1.3.1 and having problems setting the DCS (Data Coding
**>> **>Scheme) field when sending the message from kannel to the SMS-C. My
**>> provider **>requires me to use DCS=0xF5. I see a number of parameters like
**>> mclass, coding **>and mwi that all set certain bits of the DCS field but I
**>> have no idea on what **>values they should take on (if I am supposed to use
**>> them) in order for me to **>achieve my goal. Does anyone have an idea on
**>> this?
**>>
**>> Hope I remember this right...
**>> DCS = 0xF5 means the following:
**>> 0101
**>>
**>>
**>> ||++--- Message Class 1
**>> |
**>> |+- 8-bit data
**>>
**>> +-- Reserved
**>>
**>> Contains only data coding and message class info
**>>
**>> Therefore, I think you need to set the following when sending an SMS to
**>> your v1.3.1 Kannel:
**>> alt-dcs=1
**>> coding=2
**>> mclass=2
**>>
**>> For Kannel versions after 1.3.1:
**>> alt-dcs=1
**>> coding=1
**>> mclass=1
Re: Sending WAP Push to phone simulators over a network.
Hi Evgeny, Yes. IP is just an address like a phone number. Aarno On 17.2.2005, at 00:14, Evgeny Stukalov wrote: Hi Everyone, Is it possible to setup Kannel so that we can send WAP Push to Nokia or Openwave phone emulators over the internet or a LAN? Kannel Users Guide talks about sending WAP push to an emulator running under VMWare on the same machine where Kannel is running, using addressing like Would it be possible to do the same but send to a remote machine that's running a phone emulator listening on a specific port if we know the machine's IP address? And if yes, how do we set this up? Any pointers appreciated! Best regards, Eugene
Problem with Kannel
Hello, It is my first time using Kannel and I do not achieve that it me works. Trying very much I have achieved that it receives the sms but it does not spend them to the servlet that I have realized. Neither I manage to send sms with http://155.54.210.229:13013/cgi-bin/sendsms?username=prueba&password=prueba&to=609066632&text=HOLAAA5 Can someone help me to that it works? A greeting and thank you very much. The file kannel.conf that I use is: ## THIS IS A SAMPLE CONFIGURATION FOR SMS KANNEL## It is run like this:## 1% gw/bearerbox gw/smskannel.conf# 2% gw/smsbox gw/smskannel.conf# 3% test/fakesmsc -p 1 -H localhost -i 1 -m 100 "123 345 text nop"## ..all 3 commands in separate shells (or screen sessions)## For any modifications to this file, see Kannel User Guide # If that does not help, send email to users@kannel.org## Kalle Marjola May 2000# Changed for new fakesmsc version by Uoti Urpala Jan 2001# Added service and sendsms for HTTP SMSC by Kalle Marjola Mar 2001# group = coreadmin-port = 13000smsbox-port = 13001admin-password = bar#status-password = foo#admin-deny-ip = ""#admin-allow-ip = ""log-file = "/tmp/kannel.log"log-level = 0box-deny-ip = "*.*.*.*"box-allow-ip = "127.0.0.1"access-log = "/tmp/access.log"store-file = "/tmp/kannel.store" # SMSC GSMgroup = smscsmsc = atsmsc-id = SERPAspeed = 9600modemtype = wavecomdevice = /dev/ttyS1pin = # In the line of up I put the PIN sms-center = +34656000311my-number = +34658969135 group = modemsid = wavecomname = wavecomno-smsc = falsedetect-string = "WAVECOM" # SMSBOX SETUP group = smsboxbearerbox-host = localhostsendsms-port = 13013global-sender = +34658969135log-file = "/tmp/smsbox.log"sendsms-chars = "0123456789+" # SEND-SMS USERS group = sendsms-userusername = pruebapassword = prueba # SERVICES group = sms-servicekeyword = serpaget-url = """>http://155.54.210.107:8080/prueba/index.jsp?movil=%p&op=%k&sms=%r"accept-x-kannel-headers = true # there should be default always group = sms-servicekeyword = defaultget-url = """>http://155.54.210.107:8080/prueba/index.jsp?movil=%a" -Javier de Andrés RiveroDept. Ingeniería de la Información y las ComunicacionesFacultad de InformáticaUniversidad de MurciaTelf. 968 36793830001 Murcia
RE: Using Siemens MC35i as smsc AT2
Hi Davy!
Your explanation was very hopeful! Now, the creation of AT smsc instances is
good.
Thx a lot,
Pedro
-Original Message-
From: Davy Chan [mailto:[EMAIL PROTECTED]
Sent: quarta-feira, 16 de Fevereiro de 2005 11:28
To: Pedro Braz?o Ferreira
Cc: [EMAIL PROTECTED]; users@kannel.org
Subject: Re: Using Siemens MC35i as smsc AT2
Did your mail agent put those blank lines between "group = smsc"
and "smsc = at"? Or, are they actually in the configuration file?
If you do have blank lines in there, then remove them.
Support for the GSM Modem as a virtual SMSC is found in
gateway/gw/smsc/smsc_at.c and gateway/gw/smsc/smsc_at.h.
The error you were getting "Unknown SMSC type 'at'" only happens
after the checks for all the smscs.
That usually happens if the smsc is mispelled, has extra characters
(e.g. double-byte characters instead of ASCII) in the name, or
incorrect parsing of the configuration file.
The bearerbox execution sequence is:
- gateway/gw/bearerbox.c:main() calls
gateway/gw/bearerbox.c:init_bearerbox().
- init_bearerbox() calls gateway/gw/bearerbox.c:start_smsc().
- start_smsc() calls gateway/gw/bb_smscconn.c:smsc2_start().
- smsc2_start() calls gateway/gw/smscconn.c:smscconn_create() for
every "group = smsc" encountered.
- smscconn_create() processes the configuration group and then
creates the smsc client instances based on the configuration.
It is here that checks the "smsc = xxx" entry in the following
sequence:
"fake" --> smsc_fake_create()
"cimd2" --> smsc_cimd2_create()
"emi" --> smsc_emi2_create()
"http" --> smsc_http_create()
"smpp" --> smsc_smpp_create()
"at"--> smsc_at2_create()
"cgw" --> smsc_cgw_create()
"smasi" --> smsc_smasi_create()
"oisd" --> smsc_oisd_create()
The name comparison is byte-for-byte. Therefore, if the name does not
exactly match the byte sequence 0x61 0x74 ("at"), 0x41 0x54 ("AT"),
0x41 0x74 ("At"), or 0x61 0x54 ("aT"), then the match will fail to
find a declaration for the GSM modem smsc configuration.
Should the smsc not be one of the above, it punts the evaluation over
to gateway/gw/smsc/smsc_wrapper.c:smsc_wrapper_create() for the older,
less support smsc client implementation.
- Inside smsc_wrapper_create() it calls
gateway/gw/smsc/smsc.c:smsc_open().
- smsc_open() compares the smsc type to the following older
implementations:
"cimd"
"emi_x25"
"sema"
"ois"
If the smsc type is none of the above, then it will issue the:
Unknown SMSC type '...'
message and abort the attempt to create and instance of the smsc client.
See ya...
d.c.
**>From: Pedro Braz?o Ferreira <[EMAIL PROTECTED]>
**>To: <[EMAIL PROTECTED]>
**>Subject: RE: Using Siemens MC35i as smsc AT2
**>Date: Wed, 16 Feb 2005 10:02:19 -
**>Cc: users@kannel.org
**>
**>Hi,
**>
**>As Pieter ask me, my modems.conf has only two groups like this:
**>
**>group = modems
**>id = generic
**>name = "Generic Modem"
**>
**>group = modems
**>id = siemens-mc35
**>name = "Siemens MC35"
**>detect-string = "SIEMENS"
**>detect-string2 = "MC35"
**>init-string = "AT+CNMI=1,2,0,1,1"
**>speed = 19200
**>enable-hwhs = "AT\\Q3"
**>need-sleep = true
**>
**>The second one was copied from Siemens TC35 group, included on default
**>modems.conf distribution.
**>
**>But I feel the problem is on the compilation time. I had a look by
sources
**>and I didn't found AT (or AT2) support within any original script,
**>particularly on smsc.c file functions.
**>
**>Because I'm not a C specialist I have some difficulty add that option and
**>recompile the Kannel. Perhaps some of you know the problem and have a
**>solution...
**>
**>Thx again,
**>Pedro
**>
**>-Original Message-
**>From: Pieter Natte [mailto:[EMAIL PROTECTED]
**>Sent: quarta-feira, 16 de Fevereiro de 2005 0:42
**>To: Pedro Braz ? o Ferreira
**>Subject: Re: Using Siemens MC35i as smsc AT2
**>
**>
**>Pedro,
**>
**>Please let us know what is in modems.conf?
**>
**>Pieter
**>
**>
**>-- Original Message --
**>From: Pedro Braz?o Ferreira <[EMAIL PROTECTED]>
**>Date: Tue, 15 Feb 2005 17:26:37 -
**>
**>>Dear fellows,
**>>
**>>
**>>
**>>I?m trying using Kannel 1.4.0 as sms gateway. Setting up boxes, users
and
**>>services was a really piece of cake but I?m feeling some troubles
putting a
**>>Siemens MC35i GSM modem acting as a smsc, through the AT smsc type.
**>>
**>>
**>>
**>>I?m working on a Red Hat 9 Linux distribution and the modem is
responding
**>as
**>>needed, testing it with at commands via Minicom.
**>>
**>>
**>>
**>>My smsbox.conf has a smsc group like this.
**>>
**>>group = smsc
**>>
**>>smsc = at
**>>
**>>smsc-id = MODEM
**>>
**>>device = /dev/ttyS0
**>>
**>>modemtype = siemens-mc35
**>>
**>>#pin = 1212
**>>
**>>
**>>
**>># MODEM TYPES
**>>
**>>include = "/usr/local/kannel/etc/modems.conf"
**>>
**>>
**>>
**>>But every time the bearbox is started (./bearbox ?v 1 et
Re: need help on wap push/ota/mms on cdma network
Alex, Hi, Jonathan, I'm from Moldova, ex-USSR. Reading kannel's lists I found that you are work with MMS on CDMA. Yes indeed. GSM and CDMA both actually. We are using CDMA, but I can't find any info about parameters of SMS used in WDP over SMS. Can you give some hint's on sending wap push messages over SMPP gateway ? If you can, please, tell me which values of esm_class, data_coding must be used ? Can you give dump of real MMS notification which can be accepted by CDMA handset's ? I can't give you a dump as we are a commercial company and that info's not mine to share. However I can point you to the same specs I was pointed to regarding this. The spec you want is WAP-259-WDP-20010614-a.pdf and you'll want to look at section 6.5 where it describes the CDMA message. Then you'll have to look in the SMPP 3.4 spec to see how to specify a WAP push message and find the appropriate headers for SMPP. Note that the SMSC you use has to be able to handle a binary CDMA WAP push SMS and to encode it properly. Depending on your SMSC, this may be asking a lot (as it's rather complex in and of itself). Note that without my patch to Kannel, this will not be possible with Kannel. I had to add the bits to make this all possible for CDMA. Jon
SMPP to HTTP
I would like to be able to accept SMPP protocol and then redirect the requests to my kannel. Can anyone help ? J
Re: Kannel Assertions
Jonathan Houser wrote:
It's been a while since I've looked at this code, but if I build
Kannel with assertions turned off, will it stop shutting down with
panics or will it instead crash violently? I ask because I have always
had issues with wapbox hitting asserts and shutting down, thus disabling
WAP 1 browsing and PPG and whatever else that entails. That'd be fine
in a test environment as then I'd know something went wrong, but this is
production with live customers. The asserts generally look like things
that shouldn't be fatal for wapbox -- the latest a few minutes ago was:
2005-02-15 12:04:30 [27939] [8] PANIC: gwlib/octstr.c:2340:
seems_valid_real: Assertion `ostr->len + 1 <= ostr->size' failed.
(Called from gwlib/octstr.c:317:octstr_dest
roy.)
2005-02-15 12:04:30 [27939] [8] PANIC:
/usr/local/sbin/wapbox(gw_panic+0x19a) [0x80d03f7]
2005-02-15 12:04:30 [27939] [8] PANIC: /usr/local/sbin/wapbox [0x80d816d]
2005-02-15 12:04:30 [27939] [8] PANIC:
/usr/local/sbin/wapbox(octstr_destroy+0x2f) [0x80d28d1]
2005-02-15 12:04:30 [27939] [8] PANIC:
/usr/local/sbin/wapbox(octstr_destroy_item+0x11) [0x80d2905]
2005-02-15 12:04:30 [27939] [8] PANIC:
/usr/local/sbin/wapbox(list_destroy+0x35) [0x80ce555]
2005-02-15 12:04:30 [27939] [8] PANIC:
/usr/local/sbin/wapbox(http_destroy_headers+0x1e) [0x80cc567]
2005-02-15 12:04:30 [27939] [8] PANIC: /usr/local/sbin/wapbox [0x80c80f2]
2005-02-15 12:04:30 [27939] [8] PANIC:
/usr/local/sbin/wapbox(http_receive_result+0xb4) [0x80ca691]
2005-02-15 12:04:30 [27939] [8] PANIC: /usr/local/sbin/wapbox [0x805c21d]
2005-02-15 12:04:30 [27939] [8] PANIC: /usr/local/sbin/wapbox [0x80c648a]
2005-02-15 12:04:30 [27939] [8] PANIC: /lib/libpthread.so.0 [0x400a4dd6]
2005-02-15 12:04:30 [27939] [8] PANIC: /lib/libc.so.6(__clone+0x5a)
[0x4037a9aa]
I mean sure it's horrible that the lengths were off, but it's not
so horrible that we should kill all WAP/PPG traffic until a monitoring
script recovers the system. I'm guessing ./configure
--disable-assertions would fix this, but I want to check as this *is*
production. TIA. :)
ok, this assertions means, ocstr_destroy() seems to destroy something that is
not an Octstr nor a NULL pointer. Obviously we have a defined Octstr pointer
here that is not initialized, but tried to be destroyed.
Can you provide us some more lines before the first PANIC?!
And also please use 'addr2line' to resolve the source code lines of the
backtrace addresses, see 'man addr2line' for details on how to use.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: Using Kernel with WTLS
Christian Zorn wrote:
Hi List,
I want to set up a kernel WAP Gateway with WTLS.
Does anybody have experience how to set up the mobile phone so i can
have secure traffic with my Web-server via Mobile Phone? Can I use the
usual Mobile Service Provider APNs (e.g. wap.vodafone.de) with Port 9203 and
and the IP of my Kernel WAP-WTLS-Gateway?
I may guess "no". Since generally the core WAP profiles (GPRS and CSD) of
operators do firewall external IPs and let you only access the operator's WAP gw.
If it is only a "request" to use WTLS from phone to gw, you may also use
Vodafone's own WAP GW.
I'm not quite sure if they do HTTPS on the WAP GW to HTTP server side, but they
may. Kannel would support it.
Unfortunatly there is no full WTLS support for Kannel, but there is an
"external" box that can "dock" to kannel's bearerbox for the WTLS layer, it's
kwtls, see Kannel's web site for download.
In order to have Kannel doing your WTLS to HTTP server traffic you (may) move to
the general IP-APN from Vodafone.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: SMPP to HTTP
Julien Buratto wrote:
I would like to be able to accept SMPP protocol and then redirect the
requests to my kannel.
Can anyone help ?
now, this question is more then "un-detailed".
Kannel is accepting SMPP messages from bearerbox side (towards smscs) and
delivers them via HTTP to the application layer.
But I guess this is not what you are looking for. Please describe your needed
scenario in more details.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: Problem with Kannel
Javier de Andres wrote:
Hello,
It is my first time using Kannel and I do not achieve that it me works.
Trying very much I have achieved that it receives the sms but it does not spend
them to the servlet that I have realized.
Neither I manage to send sms with
http://155.54.210.229:13013/cgi-bin/sendsms?username=prueba&password=prueba&to=609066632&text=HOLAAA5
Can someone help me to that it works?
A greeting and thank you very much.
ok, config looks at least ok (even while untested of course ;)
How about providing us pieces of the bearerbox.log and smsbox.log to see what
actually happends internally?
Please attach them to the mail, in an acceptable size.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: SMPP API
Tech mark wrote:
hi ,
can some body tell me , what is the SMPP library ( API ) which is used in Kannel ?
Can we seperately i dentifiy in the source code ?
adding something to this of Davy:
be warned, the pre-processor magic contained and defined inside the .def files
is _non_ trivial. ;)
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: Installation pbs
[EMAIL PROTECTED] wrote:
Hello,
I'm quite news with Kannel and need some help to make it running. Here is the
description of the issue :
I install all lib and package on a Debian Sarge Linux machine. This machine have
apache2 daemon launch on standard port (eg 80). My configuration for kannel is
as following, but when I tried to have acces to Kannel http admin or sendsms,
the connection is refused. Is there is something to do with the apache
configuration ? or is Kannel is a standalone http server ? My local network is
192.168.1.*.
Thanks for your help.
# THIS IS A SAMPLE CONFIGURATION FOR KANNEL
#
# For any modifications to this file, see Kannel User Guide
# If that does not help, send email to users@kannel.org
# Modification : 15/02/05
# Auteur: CHN
group = core
admin-port = 13000
admin-password = bar
#status-password = foo
#admin-deny-ip = ""
#admin-allow-ip = "*.*.*.*"
log-file = "/tmp/kannel.log"
log-level = 0
access-log = "/tmp/access.log"
#http-proxy-host = "127.0.0.1"
#http-proxy-port = 8080
#http-proxy-exceptions = "127.0.0.1"
#http-proxy-username = "user"
#http-proxy-password = "password"
#ssl-certkey-file = "mycertandprivkeyfile.pem"
you did not limit via admin-*-ip here, so you obviously should be able to
connect to port 13000 for the HTTP admin/status commands.
# Smsbox related
smsbox-port = 13001
#box-deny-ip = "*.*.*.*"
#box-allow-ip = "127.0.0.1;192.168.1.*"
unified-prefix = "00336,0"
#white-list = "http://127.0.0.1/white-list.txt";
#black-list = "http://127.0.0.1/black-list.txt";
store-file = "kannel.store"
same here, where no sendsms-port is given, hence default 13013 is assumed?
BTW, didn't you read the user's guide first??? ;)
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: kwtls
Kothary, Raj wrote:
Hi,
I've been asked whether kwtls needs updating in kannel 1.4.0. I'm not sure
what that means...would that be referring to memory leaks or is there
another known problem I should know about?
Basically, I want to know if any updates need to be made to the code for
1.4.0 befor einstallation.
nop. ktwls is actually behaving as a WTLS proxy in front of bearerbox. There are
no changed in kwtls needed.
But, be warned, kwtls has memory leaks and is considered "not stable".
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: help with the models working perpectly with kanne!
walid HAOUARI wrote:
please ,could anyone tell me about the model working
perpectly with kannel ,there is some model mentionned
like the nokia ,premicell, but I can't find it in the
tunisian market ...I'll be grateful!
now, first of all you may also order it from an other country ;)
To see which models work as GSM modems, have a look into
doc/examples/modems.conf for the modem configuration definition.
Personally I'd relly on Falcom or Siemens.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: plz help ............for wap
Tech mark wrote:
hi ,
I want to know , in kannel , is there any accessing limitation of wap gateway with regards simultaniously accessing load of users ?
no! Not at all.
This is an open source project. We don't limit anything, if it has no technical
reasons. And there is no reason for that.
Kannel is running as productive WAP GW in several real-operator networks.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: Read kannel configuration from MySQL?
postboot.de (Information) wrote:
Hi there,
has anybody experiences with reading parts or even the whole kannel
configuration from MySQL?
nop. I'd guess what you "mean" is, on how to make things more dynamical without
the need to restart? That is not-trivial.
IMO, there is no need only to put "static" things into DB, you may use the
normal config text files and put them under version control, like cvs or svn.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: plz help ............for wap
I want to know , in kannel , is there any accessing limitation of wap gateway with regards simultaniously accessing load of users ? no! Not at all. This is an open source project. We don't limit anything, if it has no technical reasons. And there is no reason for that. Kannel is running as productive WAP GW in several real-operator networks. During busy hours, we see anything from around 6-10 WAP requests per second being fulfilled. Jon
Re: Kannel Assertions
Stipe, Can you provide us some more lines before the first PANIC?! Unfortunately the logs have since rotated away into oblivion. Here is a more recent panic from a couple of days ago as well. Note that this log file will also rotate into oblivion in another 12 hours or so. 2005-02-15 19:29:49 [31332] [0] WARNING: WTP: got a truncated datagram, ignoring 2005-02-15 19:29:49 [31332] [0] PANIC: wap/wap_events.c:218: wap_event_assert: Assertion `event != NULL' failed. 2005-02-15 19:29:49 [31332] [0] PANIC: /usr/local/sbin/wapbox(gw_panic+0x19a) [0x80d03f7] 2005-02-15 19:29:49 [31332] [0] PANIC: /usr/local/sbin/wapbox(wap_event_assert+0x40) [0x808c19c] 2005-02-15 19:29:49 [31332] [0] PANIC: /usr/local/sbin/wapbox(wtp_unpack_wdp_datagram+0x1f0) [0x80a4674] 2005-02-15 19:29:49 [31332] [0] PANIC: /usr/local/sbin/wapbox(wap_dispatch_datagram+0xa4) [0x8081fb8] 2005-02-15 19:29:49 [31332] [0] PANIC: /usr/local/sbin/wapbox(main+0x481) [0x8056480] 2005-02-15 19:29:49 [31332] [0] PANIC: /lib/libc.so.6(__libc_start_main+0xc0) [0x402de460] 2005-02-15 19:29:49 [31332] [0] PANIC: /usr/local/sbin/wapbox [0x8054611] The above is all I really have for this one. The log-level is turned down quite a bit due to all of the traffic we get. I can't run it at debug or anything like that. And also please use 'addr2line' to resolve the source code lines of the backtrace addresses, see 'man addr2line' for details on how to use. What am I doing wrong here? # addr2line -e /usr/local/sbin/wapbox 80d03f7 ??:0 # addr2line -e /usr/local/sbin/wapbox 0x80d03f7 ??:0 Jon
Re: Wap question !
Sewa AGBODJAN delalom wrote:
Hi,
I have a Kannel box hosted on a MNO network running smpp. Everything is
running fine so far.
The MNO has created a short number linked to the my gateway which was
created only on their smsc not on their switch.
Now I want to run the wap gateway on Kannel box.
For that purpose I have create a ppg group a wap-push-user.
When I send OTA settings to the phone, it gets it with all the parameters.
When I want to get the URL on the phone it doesn’t work.
The cell phone displays a call message, plays a network non available
sound and then display the message “Data bearer not available”.
I’m sure I’m missing something to get it work. Any help will very
appreciate.
you obviously miss the generic concepts of how WAP works. Please read the user's
guide and other generic documents of the WAP architecture.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: kannel on cdma network
Alex Antropoff wrote:
Anyone have expirience and/or modified kannel which can sent
wap push over SMPP into cdma networks ?
now, sending WAP push via SMPP is the "same" for GSM or CDMA networks. Basically
from the perspective of Kannel, there is no "difference" for the SMPP protocol.
There are some slight things different in parameters in SMPP for CDMA, but I
don't think they are relevant for pushing binary concat messages out of the door.
Actually it's the job of the SMSC itself to deal with the CDMA network and make
the messages go correctly to the devices.
@aarno: Am I right here? Or do I write absolute nonsense? ;)
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 DÃsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: plz help ............for wap
Jonathan Houser wrote:
I want to know , in kannel , is there any accessing limitation of wap
gateway with regards simultaniously accessing load of users ?
no! Not at all.
This is an open source project. We don't limit anything, if it has no
technical reasons. And there is no reason for that.
Kannel is running as productive WAP GW in several real-operator networks.
During busy hours, we see anything from around 6-10 WAP requests
per second being fulfilled.
ok, at least some benchmarks here ;)
But this will not cause any kind of resource harm to the machine, right? You are
not balancing the load accross machines, right?
BTW, what is the subscriber base (in figures) of your network, and where is it
running? (provide off-list if desired).
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: Developer with Kannel experience wanted
James Carlyle wrote:
Hi
We are looking for a developer already familiar with Kannel, vCard
formulation and smsbox for a short term contract to build platform for
pilot service, with possibility of longer term extension.
Let me know if this is of interest.
we (The Kannel Group) should take a head-hunter fee here I guess ;)
Any luck for now? Did someone addequate offer it's know-how?
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: wap gateway via GPRS
Tech mark wrote:
hi ,
Can v implement this wap gateway for GPRS network ? i meant can it possible to access wap contents via GPRS using kannel wap gateway ?
If it is possible , how many clients allowable to access via wap gateway ? Is there any load balancing mathod to use ?
yes. Kannel as a WAP gateway sits "on top" of the physical transmission layer
which is either CSD or GPRS. Kannel needs IP connectivity to work. GPRS is the
layer providing the IP connectivity.
There is not limitation in Kannel from software perspective.
Real-life operators (and setups I did too) use load-balanced machines via LVS to
spread the load accross several machines. But you will need several hundred
concurrent users per second to reach this demand and have a single machine
running at it's physicall networking limits.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: kannel on cdma network
Stipe, Anyone have expirience and/or modified kannel which can sent wap push over SMPP into cdma networks ? now, sending WAP push via SMPP is the "same" for GSM or CDMA networks. Basically from the perspective of Kannel, there is no "difference" for the SMPP protocol. There are some slight things different in parameters in SMPP for CDMA, but I don't think they are relevant for pushing binary concat messages out of the door. Actually it's the job of the SMSC itself to deal with the CDMA network and make the messages go correctly to the devices. Not 100% true. Kannel tacks in a GSM-style UDH and sets the DCS' UDHI when sending a large WAP push (ie. a URL-carrying MMS notification). Also, the specs for CDMA WDP require certain fields to be set in the SMS, and these fields are set according to fields in the SMPP message (that are not accessible via Kannel currently). That's why I made that whole un-committed, un-committable (as of now anyway) CDMA patch to allow for a data_sm. For the most part they are the same, but not enough the same that you can get it to work as is (or at least we couldn't). :P Jon
Re: Problem with Kannel
Hello The file smsbox.log is not created, is one of the problems. When I try to send a sms from web (/cgi-bin/sendsms ...) it takes produced the mistake of Internet Explorer of that it is not possible to show the page. I have done many tests and i have changed version of the kannel but I do not achieve that it works Kannel's version that i use is 1.3.1 in a Linux Debian. Very very thanks. Javi. The content of the file of bearerbox.log (in my case kannel.log) is this: 2005-02-17 19:36:02 [0] DEBUG: Read from modem: 'OK' 2005-02-17 19:36:02 [0] DEBUG: AT: Command: ATI 2005-02-17 19:36:02 [0] DEBUG: Read from modem: 'WAVECOM MODEM MULTIBAND 900E 1800 OK' 2005-02-17 19:36:03 [0] DEBUG: AT: Command: ATI1 2005-02-17 19:36:03 [0] DEBUG: Read from modem: 'OK' 2005-02-17 19:36:04 [0] DEBUG: AT: Command: ATI2 2005-02-17 19:36:04 [0] DEBUG: Read from modem: 'OK' 2005-02-17 19:36:05 [0] DEBUG: AT: Command: ATI3 2005-02-17 19:36:06 [0] DEBUG: Read from modem: '421_09gm.2C 1172952 071901 18:17OK' 2005-02-17 19:36:07 [0] DEBUG: AT: Command: ATI4 2005-02-17 19:36:07 [0] DEBUG: Read from modem: 'Q:0 V:1 S0:000 S2:043 S3:013 S4:010 S5:008 +CR:0 +CRC:0 +CMEE:0 +CBST:0,0,1 +SPEAKER:0 +ECHO:0,1 &C:1 &D:2 %C:0 +IPR:9600 +ICF:3,4 +IFC:2,2OK' 2005-02-17 19:36:08 [0] DEBUG: AT: Command: AT+CPIN? 2005-02-17 19:36:08 [0] DEBUG: Read from modem: '+CPIN: READY' 2005-02-17 19:36:08 [0] DEBUG: AT: Command: AT+CMGF=0 2005-02-17 19:36:08 [0] DEBUG: Read from modem: 'OK' 2005-02-17 19:36:09 [0] DEBUG: AT: Command: AT+CNMI=1,2,0,0,0 2005-02-17 19:36:09 [0] DEBUG: Read from modem: 'OK' 2005-02-17 19:36:09 [0] INFO: AT SMSC successfully opened. 2005-02-17 19:36:09 [0] DEBUG: Started thread 6 (gw/smsc/smsc_wrapper.c:wrapper_receiver) 2005-02-17 19:36:09 [0] DEBUG: Started thread 7 (gw/smsc/smsc_wrapper.c:wrapper_sender) 2005-02-17 19:36:09 [0] DEBUG: Started thread 8 (gw/bb_smscconn.c:sms_router) 2005-02-17 19:36:09 [0] INFO: 2005-02-17 19:36:09 [0] INFO: Kannel bearerbox II version 1.3.1 starting 2005-02-17 19:36:09 [0] ERROR: fopen failed: couldn't open `/tmp/kannel.store' 2005-02-17 19:36:09 [0] ERROR: System error 2: No such file or directory 2005-02-17 19:36:09 [0] ERROR: fopen failed: couldn't open `/tmp/kannel.store.new' 2005-02-17 19:36:09 [0] ERROR: System error 2: No such file or directory 2005-02-17 19:36:09 [0] ERROR: fopen failed: couldn't open `/tmp/kannel.store.bak' 2005-02-17 19:36:09 [0] ERROR: System error 2: No such file or directory 2005-02-17 19:36:09 [0] INFO: Cannot open any store file, starting new one 2005-02-17 19:36:09 [0] INFO: MAIN: Start-up done, entering mainloop 2005-02-17 19:36:09 [0] DEBUG: Starting wrapper 2005-02-17 19:36:09 [8] DEBUG: sms_router: time to sleep 2005-02-17 19:36:09 [8] DEBUG: sms_router: list_len = 0 2005-02-17 19:37:15 [3] DEBUG: HTTP: Creating HTTPClient for `155.54.210.107'. 2005-02-17 19:37:15 [4] DEBUG: HTTP: Resetting HTTPClient for `155.54.210.107'. 2005-02-17 19:37:20 [4] DEBUG: HTTP: Resetting HTTPClient for `155.54.210.107'. 2005-02-17 19:38:23 [2] ERROR: Error reading from fd 29: 2005-02-17 19:38:23 [2] ERROR: System error 104: Connection reset by peer 2005-02-17 19:38:23 [2] DEBUG: HTTP: Destroying HTTPClient area 0x80f6b00. 2005-02-17 19:38:23 [2] DEBUG: HTTP: Destroying HTTPClient for `155.54.210.107'. 2005-02-17 19:47:21 [3] DEBUG: HTTP: Creating HTTPClient for `155.54.210.107'. 2005-02-17 19:47:21 [4] DEBUG: HTTP: Resetting HTTPClient for `155.54.210.107'. 2005-02-17 19:47:30 [4] DEBUG: HTTP: Resetting HTTPClient for `155.54.210.107'. 2005-02-17 19:47:39 [4] DEBUG: HTTP: Resetting HTTPClient for `155.54.210.107'. 2005-02-17 19:47:45 [4] DEBUG: HTTP: Resetting HTTPClient for `155.54.210.107'. 2005-02-17 19:47:50 [4] DEBUG: HTTP: Resetting HTTPClient for `155.54.210.107'. 2005-02-17 19:47:52 [4] DEBUG: HTTP: Resetting HTTPClient for `155.54.210.107'. 2005-02-17 19:48:01 [4] DEBUG: HTTP: Resetting HTTPClient for `155.54.210.107'. 2005-02-17 19:48:04 [4] DEBUG: HTTP: Resetting HTTPClient for `155.54.210.107'. 2005-02-17 19:48:08 [4] DEBUG: HTTP: Resetting HTTPClient for `155.54.210.107'. 2005-02-17 19:49:09 [2] ERROR: Error reading from fd 29: 2005-02-17 19:49:09 [2] ERROR: System error 104: Connection reset by peer 2005-02-17 19:49:09 [2] DEBUG: HTTP: Destroying HTTPClient area 0x80f6dc0. 2005-02-17 19:49:09 [2] DEBUG: HTTP: Destroying HTTPClient for `155.54.210.107'. 2005-02-17 21:26:47 [3] DEBUG: HTTP: Creating HTTPClient for `84.121.148.254'. 2005-02-17 21:26:47 [4] DEBUG: HTTP: Resetting HTTPClient for `84.121.148.254'. 2005-02-17 21:26:51 [4] DEBUG: HTTP: Resetting HTTPClient for `84.121.148.254'. 2005-02-17 21:27:57 [2] ERROR: Error reading from fd 29: 2005-02-17 21:27:57 [2] ERROR: System error 104: Connection reset by peer 2005-02-17 21:27:57 [2] DEBUG: HTTP: Destroying HTTPClient area 0x80f6b00. 2005-02-17 21:27:57 [2] DEBUG: HTTP: Destroying HTTPClient for `84.121.148.25
Re: Problem with Kannel
Javier de Andrés wrote:
Hello
The file smsbox.log is not created, is one of the problems.
When I try to send a sms from web (/cgi-bin/sendsms ...) it takes produced
the mistake of Internet Explorer of that it is not possible to show the page.
I have done many tests and i have changed version of the kannel but I do not
achieve that it works
Kannel's version that i use is 1.3.1 in a Linux Debian.
Very very thanks.
Javi.
The content of the file of bearerbox.log (in my case kannel.log) is this:
now the content of kannel.log does not show any obvious errors. Reading your
config from the previous mail, I see that you _have_ a smbox group in there. Do
you start a smsbox instance on the machine? If yes, the log-file should be written?!
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: kannel on cdma network
Jonathan Houser wrote:
Not 100% true. Kannel tacks in a GSM-style UDH and sets the DCS'
UDHI when sending a large WAP push (ie. a URL-carrying MMS
notification). Also, the specs for CDMA WDP require certain fields to
be set in the SMS, and these fields are set according to fields in the
SMPP message (that are not accessible via Kannel currently). That's why
I made that whole un-committed, un-committable (as of now anyway) CDMA
patch to allow for a data_sm. For the most part they are the same, but
not enough the same that you can get it to work as is (or at least we
couldn't). :P
yep, Jon is right here. There are some things to tweak.
But we'd definetly like to have a view on the changes, even while not clean
commitable. As we are currently discussing about how to implement SMPP specific
parameter support, this may go into there too.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: how to set up kannel gateway for WAP 2.0 Gateway
Jaegil Kim wrote:
Is there anyone who know how to set up Kannel Gateway for WAP 2.0 Gateway?
now, Kannels officially supported stack is WAP 1.2.1 June. Since 2.0 is
basically "only" HTTP proxy'ing in it's simplest form, there is either no proxy
required, or you pick an HTTP proxy of your choice, like apache2.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 DÃsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: need help on wap push/ota/mms on cdma network
Hi Jon,
Jonathan Houser wrote:
I can't give you a dump as we are a commercial company and that
info's not mine to share. However I can point you to the same specs I
was pointed to regarding this. The spec you want is
WAP-259-WDP-20010614-a.pdf and you'll want to look at section 6.5 where
it describes the CDMA message. Then you'll have to look in the SMPP 3.4
spec to see how to specify a WAP push message and find the appropriate
headers for SMPP. Note that the SMSC you use has to be able to handle a
binary CDMA WAP push SMS and to encode it properly. Depending on your
SMSC, this may be asking a lot (as it's rather complex in and of
itself). Note that without my patch to Kannel, this will not be
possible with Kannel. I had to add the bits to make this all possible
for CDMA.
is there a chance to get this changes/patch made available?
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: Kannel Assertions
Jonathan Houser wrote:
What am I doing wrong here?
# addr2line -e /usr/local/sbin/wapbox 80d03f7
??:0
# addr2line -e /usr/local/sbin/wapbox 0x80d03f7
??:0
obviously there are no debugging symbols inside the binaries. Please
re-build using
$ ./configure --with-cflags="-O2 -g -rdynamic" [...]
as option to make the debugging symbols added to the bins. Then retry with
addr2line. But beware that you can't use the addresses from this log, only from
logs with backtraces produced by the new binaries.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: SMPP to HTTP
On Thu, Feb 17, 2005 at 07:37:07PM +0100, Stipe Tolj wrote: > Julien Buratto wrote: > > >I would like to be able to accept SMPP protocol and then redirect the > >requests to my kannel. > >Can anyone help ? > > now, this question is more then "un-detailed". > > Kannel is accepting SMPP messages from bearerbox side (towards smscs) and > delivers them via HTTP to the application layer. > > But I guess this is not what you are looking for. Please describe your > needed scenario in more details. > > Stipe Like, Value Added Services Provider to offer SMPP connectivity to other Value Added Services Providers Company A has SMPP connection via Kannel to SMSC X Company B wants to use SMPP connectivity to SMSC X, but SMSC X allows only Company A to use such connectivity. So, company B asks for SMMP connectivity to Company A .. I hope the above description will match the original question. BR seik
Re: Kannel Assertions
Jonathan Houser wrote:
2005-02-15 19:29:49 [31332] [0] WARNING: WTP: got a truncated datagram,
ignoring
2005-02-15 19:29:49 [31332] [0] PANIC: wap/wap_events.c:218:
wap_event_assert: Assertion `event != NULL' failed.
2005-02-15 19:29:49 [31332] [0] PANIC:
/usr/local/sbin/wapbox(gw_panic+0x19a) [0x80d03f7]
2005-02-15 19:29:49 [31332] [0] PANIC:
/usr/local/sbin/wapbox(wap_event_assert+0x40) [0x808c19c]
2005-02-15 19:29:49 [31332] [0] PANIC:
/usr/local/sbin/wapbox(wtp_unpack_wdp_datagram+0x1f0) [0x80a4674]
2005-02-15 19:29:49 [31332] [0] PANIC:
/usr/local/sbin/wapbox(wap_dispatch_datagram+0xa4) [0x8081fb8]
2005-02-15 19:29:49 [31332] [0] PANIC:
/usr/local/sbin/wapbox(main+0x481) [0x8056480]
2005-02-15 19:29:49 [31332] [0] PANIC:
/lib/libc.so.6(__libc_start_main+0xc0) [0x402de460]
2005-02-15 19:29:49 [31332] [0] PANIC: /usr/local/sbin/wapbox [0x8054611]
ok, the first WARNING would also have more information in debug log-level mode,
since the wap_event_dump() is called and we get more information on what is
actually inside the datagram. This information is not available in the log,
because of the higher log-level.
ok, this is obviously a bug! since we return NULL for unpack_wdp_datagram_real()
and directly afterwards do wap_event_assert() and the first gw_assert(event !=
NULL) brings us to PANIC.
I will file this to Mantis and check for a fix.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: SMPP to HTTP
[EMAIL PROTECTED] wrote:
Like, Value Added Services Provider to offer SMPP connectivity to other Value
Added Services Providers
Company A has SMPP connection via Kannel to SMSC X
Company B wants to use SMPP connectivity to SMSC X, but SMSC X allows only
Company A to use such connectivity.
So, company B asks for SMMP connectivity to Company A ..
I hope the above description will match the original question.
yes, in some sense. Actually the demand is a SMPP relay/proxy between real-smsc
feeding bearerbox and "customers" bearerbox. Ie.
<-> <-> <->
So the beast you are looking for is smppbox. It exists and lives in cages at
Wapme. Unfortunatly it's not free and is (at least still/currently) not part of
the Kannel project. Which means it's not generally available.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: Kannel Assertions
Jonathan Houser wrote:
2005-02-15 19:29:49 [31332] [0] WARNING: WTP: got a truncated datagram,
ignoring
2005-02-15 19:29:49 [31332] [0] PANIC: wap/wap_events.c:218:
wap_event_assert: Assertion `event != NULL' failed.
2005-02-15 19:29:49 [31332] [0] PANIC:
/usr/local/sbin/wapbox(gw_panic+0x19a) [0x80d03f7]
2005-02-15 19:29:49 [31332] [0] PANIC:
/usr/local/sbin/wapbox(wap_event_assert+0x40) [0x808c19c]
2005-02-15 19:29:49 [31332] [0] PANIC:
/usr/local/sbin/wapbox(wtp_unpack_wdp_datagram+0x1f0) [0x80a4674]
2005-02-15 19:29:49 [31332] [0] PANIC:
/usr/local/sbin/wapbox(wap_dispatch_datagram+0xa4) [0x8081fb8]
2005-02-15 19:29:49 [31332] [0] PANIC:
/usr/local/sbin/wapbox(main+0x481) [0x8056480]
2005-02-15 19:29:49 [31332] [0] PANIC:
/lib/libc.so.6(__libc_start_main+0xc0) [0x402de460]
2005-02-15 19:29:49 [31332] [0] PANIC: /usr/local/sbin/wapbox [0x8054611]
just fixed this bug #197 in cvs HEAD branch. Please see
http://www.kannel.org/cgi-bin/viewcvs.cgi/gateway/wap/wtp.c.diff?r1=1.8&r2=1.9&sortby=date
for the change.
@Aarno: I guess this is obvious. But I'd like to have a post-mortem +1 from your
here for saving my poor soul. ;)
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: Using Siemens MC35i as smsc AT2
**>From: Pedro Braz?o Ferreira <[EMAIL PROTECTED]> **>To: "'Davy Chan'" <[EMAIL PROTECTED]> **>Subject: RE: Using Siemens MC35i as smsc AT2 **>Date: Thu, 17 Feb 2005 15:54:20 - **> **>Your explanation was very hopeful! Now, the creation of AT smsc instances is **>good. Glad to hear it. So what was the problem? 1) smsc is mispelled 2) extra characters (e.g. double-byte characters instead of ASCII) 3) incorrect parsing due to the extra blank line between "group = smsc" and "smsc = at"? 4) Something else. See ya... d.c.
