Re: alpha patch CIMD2?
Hi Angel, I'll try this today with two of my CIMD2 providers, and comment on it. great. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [PATCH] Re: [FYI] contrib/kannel-monitor: a php application
Alexander Malysh wrote: Hi Stipe, patch adds names to kannel instanses and fix date calculation... thanks Alex, commited to cvs. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [Fwd: [Kannel 0000005]: sms-service HTTP Basic Authentication no longer working [1.3.1]]
Bruno David Rodrigues wrote: I think Bas Schulte is right - second parse_url is not needed. Can you please remove it and test if it works ok ? right, I already worked this out. And will commit the change in a couple of minutes. Another alternative is to create an Octstr *logurl and have it with * and replace every error|debug|info with it. I've even started doing that here but I think first we need to solve the double parse_url. At lest, to prevent memory leaking, if it exists. I moved another value to the trans struct itself, the path (URI). See the cvsdiff when checked in. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
[Fwd: Extensive DLR testing with SMPP found lots of bugs]
forwarded to the list. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are---BeginMessage--- Hello! I' ve found your e-mail on mailing list about Kannel. I need some help very much. I have some problems with MySql and kannel. Firts it did not want to store information in MySql database. But I fixed it somehow. But I got another problem. And I really don't know what I need to do, how to fix that? So Kannel store the DLR in MySql and suddenly removes it. So when Kannel get delivery report he cannot find DLR in MySql, because Kannel removed it ealier. Please tell me what I can do! 2003-03-06 09:30:56 [6] DEBUG: Found entry, row[0]=31, row[1]=simple, row[2]=http://66.xxx.x.xxx/php/submitform.php?status=, row[3]=447781482005, row[4]=(null)2003-03-06 09:30:56 [6] DEBUG: created DLR message for URL http://66.xxx.xxx.xx/php/submitform.php?status=2003-03-06 09:30:56 [6] DEBUG: removing DLR from database2003-03-06 09:30:56 [6] ERROR: Could not route message to smsbox id (null), smsbox is gone! regards, Bartosz JozwiakResearch Development DepartmentCq-Link, GreenTonee-mail: [EMAIL PROTECTED]Office tel no.: +597 433932/492065/464954private tel. no.: +597 8500569 www.greentone.com Bartosz JozwiakResearch Development DepartmentCq-Link, GreenTonee-mail: [EMAIL PROTECTED]Office tel no.: +597 433932/492065/464954private tel. no.: +597 8500569 http://www.cq-link.srhttp://www.greentone.com ---End Message---
[REQ] any fix for the AT2 module fails to open serial ports after system startup. issue
Hi Oded, any update from your side concerning this entry in the STATUS file: * AT2 module fails to open serial ports after system startup. The reason is that the default serial port parameters are not proper set for connecting to modems. To work around the problem you can open the modem port with a terminal program, make sure it works, close the terminal program and use the stty program (available on linux and other unixes. check your system's documentation for an equivilent program) to record the port parameters: $ stty -g -F /dev/serial device and then write a startup script to setup the port with those parameters: $ stty -F /dev/serial device output of stty -g The following line works for me(tm) on a Linux Mandrake 8.2 with wavecom modem connected to a USB port extender: $ stty -F /dev/usb/tts/0 1:0:88bd:0:3:1c:7f:15:4:5:1:0:11:13:1a:0:12:f:17:16:0:0:2f:0:0:0:0:0:0:0:0:0:0:0:0:0 Posted by: Oded Arbel [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Status: Oded: AT2 module should be fixed to do that internally Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: wap gateway - wtls
[EMAIL PROTECTED] wrote: Is there any wtls workaround in Kannel 1.3.1 ? a possible workaround is the kwtls package, see http://www.kannel.org/download/wtls/kwtls-1.0.3.tar.gz but this is *not* supported in any way by the group. Or is there a working patch that enables wtls in 1.3.1 ? Kannel itself contains pre-alpha stage WTLS code, which is currently not operatable. If you are willing to contribute and have SSL/TLC experience, grap the kwtls package and try to addopt things to Kannel's existing WTLS stack. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Siemens SEO Specification
Hi Dominik, If all tests are done, I want to make a tutorial :-) great. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
[FYI] gwlib/dbpool.[ch] commited
Hi list, I have now commited a first implementation of database connection pools. (Currenly MySQL mainly). They are intended to reduce/eliminate database communication bottle-necks by providing a set of functions that pool single connections into an more abstract data type, the pool itself. To try out, you have to configure with mysql support, i.e. $ ./configure --with-mysql=some location --enable-mysql $ make $ ./test/test_dbpool -v 1 -h host -u userid -p passwd \ -d mysql -s 10 -q 1000 -t 10 -S SHOW STATUS will create a pool of 10 connections to the mysql engine, create 10 client query threads that do 1000 sql queries SHOW STATUS in each thread. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Reconciliation of DLR with original message?
Bas A. Schulte wrote: Jason, On Wednesday, March 12, 2003, at 12:44 AM, [EMAIL PROTECTED] wrote: On 12/03/2003 10:26:29 AM devel-admin wrote: http://kannel.machine:13013/cgi-bin/sendsms?.dlr- url=http://your.machine/de livered.php?msisdn=msisdn I understood that part of it, but what I want to know, is what does the DLR callback URL include, to identify it as a delivery report for a specific message. My take is that you generate some unique id yourself in the code where you execute the sendsms http call and feed that in the dlr-url. yep. smsbox does call exactly the GET method URL you specify. It's up to the caller to make it's semantical logic work. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: SMS Replies
Does sms-service have any way to reconciliate an outgoing message, with a reply. Does Kannel have anyway to recognise a reply from a message it sent out to start with. I know that you have support for sms-services which are identified by the first word in the sms message, and I really like that functionality, but I was wondering how much more was possible. you can also route the MO message using the 'allowed|denied-receiver-prefix' if the MO messages are send to shortcut numbers (i.e. 71212) to specific sms-service groups. But I'm not aware if this was the question?! Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [PATCH] trivial fix smpp-pdu
attached you can find patch that should fix (my mistake:() parsing of optional parameters in smpp stack ... yep, +1, commited to cvs. Thanks a lot. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: When will Kannel 1.3.x be 1.4.0 stable?
[EMAIL PROTECTED] wrote: Hi, Any idea generally how long it might be before 1.3.x goes into feature-freeze phase? now, as I asked for comments, I suggest to have a couple of issues included into 1.3.2 development and let that be then in feature-freeze, which means only bug fixing, and populate it to 1.4.0 stable. Its considered important by some in my company, that we have an idea which version of Kannel will be ready for production use for our clients, when we ship our software, with Kannel support in August/September 2003. The list consideres currently the CVS tree to be of (almost) production quality. A lot of Kannel users (mainly companies that to extensive MT and MO traffic) use the CVS tree in production environments. I realise that this is something you cannot answer with any certainty, but an indication of what is required to reach a feature-freeze phase, would be just as helpful. How close do you feel Kannel is to a feature freeze? Since you have only release 1.3.1 and looking at 1.3.2, perhaps 1.4.0 is a bit of a way off. nop, 1.3.2 is pretty close I guess and a feature-freeze is usually 2-3 weeks, depending how many people do/do not report bugs. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: When will Kannel 1.3.x be 1.4.0 stable?
Aarno Syvänen wrote: What features should 1.4.0 contain. Mms support is enough for a stable release, imho. see my last mail with suject [RFC] new development release 1.3.2. I'd like to roll that one first in near time and let a feature-freeze postulate it to 1.4.0 stable. What do the others think about this?! Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
[FYI] SMSC re-connecting behaviour changed!
Hi list, this is informative and also a COMPATIBILITY BREAKER! We have moved the smsc group config directive 'reconnect-delay' which was used mainly for SMPP and SM/ASI to the higher abstraction SMSCConn layer, so all SMSC modules can benefit from this. Which means within AT2 and EMI2 there is *no longer* a 'retry' smsc group directive and there is *no longer* an exponential back-off behaviour for reconnecting to the SMSC links. They are now using also the 'reconnect-delay' that you give within the smsc group. Which also means they will *alway* try to reconnect, unless you don't set the link to 'dead' state or choose a very high 'reconnect-delay'. Can anyone please try the current cvs tree on their SMSC links and check if the reconnecting behaviour acts as expected. It should. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [PATCH]ppg push - crashing bug trusted-pi/no user
In theory, only the patch to wap_push_ppg_pushuser.c is needed to prevent the crash. However, why bother to have pap_request_thread call wap_push_ppg_pushuser_smsc_id_get when you already know there is no username to make wap_push_ppg_pushuser_smsc_id_get do something usefull? Also, it allows to differentiate between the 2 situations if needed (e.g. logging). yep, the fix inside wap_push_ppg_pushuser_smsc_id_get() is *definetly* needed. Ok, with performance in mind we'll also add the if clause. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
anyone tested the new 'reconnect-delay' with EMI2 links?!
Hi list, I just tried to restart our production server with a bunch of EMI/UCP links and the new reconnect harmonized config, but *all* EMI2 links failed to connect ;(( Anyone had the chance to test this? Seems something is wrong in here. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: ppg test tool
It does require the latest CVS kannel as there were some issues that have recently been fixed in kannel. If nothing else, it can be used as an additional test tool for ppg (besides test/test_ppg.c). and will be available in the upcoming 1.3.2 development release. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: accept-x-kannel-headers
everything seems to work fine. but what about the userguide? can you provide a patch in unified format?! Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
[RFC] new 'sms-service' transport type 'store'
Hi list, we came accross a demand that can be implemented in Kannel for various other functional uses. Assume you want to receive MOs via bearerbox and pass to smsbox, but you don't want to handle them on-the-fly. So what you can do is push them via 'get-url' to an HTTP server and store them application internally. If you want to avoid this, we may provide a simple 'store' transport, that stores the MO into a file of kannel.store file structure. Hence If you want to re-queue those stored messages you simply stop bearerbox, copy the contents of the store to kannel.store and they will be re-routed to smsbox. A config would look like this: group = sms-service accepted-smsc = smsc_a;smsc_b ... store = /var/kannel/store/%i to store all MOs from smsc links 'smsc_a' and 'smsc_b' to /var/kannel/store/smsc_a and /var/kannel/store/smsc_b. I think this shouldn't be too hard to implement and would be very usefull to have a re-queuing alternative. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [PATCH] CIMD2 driver upgraded to smsconn api
Angel Fradejas wrote: So, finally here it is. A first working version of the Nokia CIMD2 driver upgraded to the more convenient api SMSCConn*. I took Kalle Majorla's work on this issue as a starting point, then further improved it. I have tested this with two providers, with every type of message I could think of (binary, ems, class 0, concatenated and so on) and works fine. patch applied cleanly. compiled and build cleanly. +1 for commiting this. Can you please provide us also a patch for the doc/userguide/userguide.xml for the CIMD section?! Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [PATCH] complete restart functionality
Alexander Malysh wrote: attached patch adds missing restart functionality to smsbox and wapbox. So you can now really use this functionality over http-admin interface :) Comments and votes please ... thanks Alex. are the smsbox and wapbox restarts gracefull?! which means do they harm the HTTP request/response handling? or is it a brute-force restart? Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Markefile.in - distclean deletes config.sub and config.guess
Been building a few debian packages - found a minor bug in process (I think). The Makefile.in file currently builds a Makefile which when you distclean removes config.guess and config.sub. I believe this is incorrect - ie: try running a ./configure after a make distclean (trivial patch attached). As a result shouldn't need the cp config.sub, config.guess in debian/rules - no harm in leaving as is... but attached patch for completeness. Makefile.in has been fixed in cvs. Bruno, can you please check on the debian packaging rules?! Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [PATCH] CIMD2 driver upgraded to smsconn api
commited to cvs. Thanks a lot Angel! Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: GPRS / MMS configuration SMS
Jason Brian Friedrich wrote: Hello list, are there any examples of gprs-config-sms out there? I need one for a Nokia 7650 and/or SonyEricsson T68i. I tried to send one to a wavecom modem but the config-sms did not arrive. check out the Nokia/Ericsson OTA specs, there are examples of GPRS configs. Basically it's pretty much the same as CSD. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [PATCH] CIMD2 driver upgraded to smsconn api
Dziugas Baltrunas schrieb: I currently was writing a question to the mailing list about plans to rewrite CIMD2 to smsconn :)) now... that should go to recycle I guess ;) great job, Angel. yep, he did ;) Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [Kannel 0000010]: HTTP requests get urlencoded twice (orevenmore) if HTTP 302 (redirect) responses are received
Rene Kluwen wrote: I think you answered your question yourself :). Yes, the querystring should be included in subsequent requests. By intuition I'd disagree. But maybe we should check if other common HTTP clients do this. Should be easy to check. Can someone do this? I'm busy with applying patches and doing the updates for the 1.3.2 development release ;) Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [PATCH] CIMD2 driver upgraded to smsconn api
and if yes, maybe we could add one more directive in the configuration file, like use-dlr? Concerning additional directives, I'm pretty much for it if they avoid real life problems, to be able to use Kannel our-of-the-box (with the proper config) without hacking with the code. And most of us like only more directives that can be addopted to more then one smsc module type ;) So you should always take care when thinking of adding more config directives. It will be easier as soon as we split of the config directive things by smsc specific configuration cfg.def etc. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [PATCH] complete restart functionality
commited to cvs. Thanks. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [PATCH] log.c reopen bug fix
attached patch will fix segfault in log.c. Segfault arise while reopening of shared files. The solusion for this is: while reopening of log files walk logfiles reverse and seek for allready reopened one, if found then point FILE pointer to already reopened and try the same with next log file... Comments and votes please ... yep, +1, commited in a slightly changed form. Alexander, please keep the otehr patch chunks also updated against current cvs. Which means if we commit patches, we may change then slightly, ie. concerning source code formating etc., so this parts come up again in a later patch from you which shouldn't. This is only to make it easier for us all. Anyway, thanks for the above ;) Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [PATCH] CIMD2 fix and userguide (overrides last one)
Angel Fradejas wrote: This patch fixes some problems with the SMSCConn CIMD2 driver, for example high CPU load in a connection with no traffic at all (thanks to Dziugas Baltrunas for pointing it out), and some other things. Also included an update for the user guide. This patch overrides last one I sent yesterday. Stipe please, commit. done. Thanks. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: SIMToolkit Implementation (www.smartrust.com)
Anyone interested in developing SIMToolKit module (especially SIMToolkit platform provide by www.smarttrust.com called Delivery Platform) in Kannel? The mechanism is like WAP over SMS mechanism, but they use proprietary wml compiling mechanism to provide proprietary wml bytecode. what I see is that they simply use a PPG to push a WML deck via SMS to a mobile device. Right now, I can manage to deliver the bytecode successfully using Kannel with some modification (without smarttrust Delivery Platform). which modifications?! Can you send us a diff/patch of that?! You can produce bytecode by compiling WML page with SmartTrust program called Transformer Pro. which should be the same as if we use our PPG to push a WML deck to a device. If anybody interest, I will share. ( I need to translate my documentation into English first). yep, please provide it to the list in English. My next aim is to find out how they compile bytecode itself. I try to find out mapping table for every wml tag used. The progress is slow since I am not good enough to code it into C/C++. I try to modify wml_compiler.c in Kannel, but it's too complicated for me. :( I think I need help. :) are you sure it differs from the official WML bytecode?! Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [PATCH] SMPP sender-prefix ala unified-prefix
Benjamin Lee wrote: Those of you connected to a large multinational SMSC who does not support NATIONAL TON... ;-) ... may find this patch useful where you want users to be able to set their originator / source address in national format. It is based on the unified prefix code. hmm, so you want your user's to inject into sendsms HTTP interface national source addresses in the to=value field and re-code that using the normalization routine to an international format?! hmmm... I think this is not very hard to do, even in the SMSCConn abstraction layer. But the question is: should it be done? and how do we name the configuration directive. Basically 'unified-prefix' acts as follows now: MO: msg.sender gets normalized MT: msg.receiver gets normalized so 'unified-prefix' only deals with the MSISDNs of the remove entity. Now we'd need a directive to deal with the local entity. Maybe renaming 'unfied-prefix' to 'unified-remove-prefix' and adding 'unified-local-prefix' for MO: msg.receiver gets normalized MT: msg.sender gets normalized ?? Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [PATCH] SMPP
Nisan, sorry to be nastly, but could you please resend the whole patch in *one* diff file and at email attachement rather then enbedding in the email body. Thanks. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
[Fwd: [PATCH] SMPP]
forwarding this to the list.
Stipe
[EMAIL PROTECTED]
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf
Tel: +49-211-74845-0
Fax: +49-211-74845-299
E-Mail: [EMAIL PROTECTED]
Internet: http://www.wapme-systems.de
---
wapme.net - wherever you are---BeginMessage---
Hi
here you go
nisan
At 07:46 PM 3/27/03 +0100, you wrote:
Nisan,
sorry to be nastly, but could you please resend the whole patch in
*one* diff file and at email attachement rather then enbedding in the
email body.
Thanks.
Stipe
[EMAIL PROTECTED]
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf
Tel: +49-211-74845-0
Fax: +49-211-74845-299
E-Mail: [EMAIL PROTECTED]
Internet: http://www.wapme-systems.de
---
wapme.net - wherever you are
--- ../../cvs/gateway/gw/smsc/smsc_smpp.c Thu Mar 20 10:23:57 2003
+++ ../../gateway-clickcvs/gw/smsc/smsc_smpp.c Wed Mar 26 21:59:32 2003
@@ -12,6 +12,10 @@
either) */
/* XXX numbering plans and type of number: check spec */
+#if defined(HAVE_LIBSSL) || defined(HAVE_WTLS_OPENSSL)
+#include openssl/opensslv.h
+#endif
+
#include gwlib/gwlib.h
#include msg.h
#include smsc_p.h
@@ -31,16 +35,20 @@
#ifndef DEBUG
/* This version doesn't dump. */
-static void dump_pdu(const char *msg, Octstr *id, SMPP_PDU *pdu)
+static void dump_pdu(const char *msg, Octstr *id, SMPP_PDU *pdu, int do_dump)
{
}
#else
/* This version does dump. */
-static void dump_pdu(const char *msg, Octstr *id, SMPP_PDU *pdu)
+static void dump_pdu(const char *msg, Octstr *id, SMPP_PDU *pdu, int do_dump)
{
debug(bb.sms.smpp, 0, SMPP[%s]: %s,
octstr_get_cstr(id), msg);
+if (do_dump)
smpp_pdu_dump(pdu);
+else
+debug(bb.sms.smpp, 0, SMPP[%s]: type_name: %s,
+octstr_get_cstr(id), pdu-type_name);
}
#endif
@@ -51,6 +59,7 @@
#define SMPP_ENQUIRE_LINK_INTERVAL 30.0
#define SMPP_MAX_PENDING_SUBMITS10
+#define SMPP_RECONNECT_DELAY10.0
#define SMPP_DEFAULT_VERSION0x34
#define SMPP_DEFAULT_PRIORITY 0
#define SMPP_THROTTLING_SLEEP_TIME 15
@@ -84,17 +93,22 @@
List *received_msgs;
Counter *message_id_counter;
Octstr *host;
+int is_ssl;
+int dump_pdu;
Octstr *system_type;
Octstr *username;
Octstr *password;
Octstr *address_range;
Octstr *my_number;
Octstr *service_type;
+ Octstr *forced_sender;
int source_addr_ton;
int source_addr_npi;
int dest_addr_ton;
int dest_addr_npi;
int alt_dcs;
+int pack_7bit;
+int reg_dlr_mask;
int transmit_port;
int receive_port;
int quitting;
@@ -102,6 +116,8 @@
long max_pending_submits;
int version;
int priority; /* set default priority for messages */
+long throttle_sleep;
+int throughput;
time_t throttling_err_time;
int smpp_msg_id_type; /* msg id in C string, hex or decimal */
int autodetect_addr;
@@ -117,16 +133,21 @@
int source_addr_ton, int source_addr_npi,
int dest_addr_ton, int dest_addr_npi,
int alt_dcs, int enquire_link_interval,
- int max_pending_submits, int version, int priority,
- Octstr *my_number, int smpp_msg_id_type,
- int autodetect_addr, Octstr *alt_charset,
- Octstr *service_type)
+ int max_pending_submits,
+int version, int priority, Octstr
*my_number,
+int smpp_msg_id_type, int
autodetect_addr,
+Octstr *alt_charset, Octstr
*service_type,
+ int is_ssl, int dump_pdu, Octstr *forced_sender,
+ long throttle_sleep, int throughput, int reg_dlr_mask,
+ int pack_7bit)
{
SMPP *smpp;
smpp = gw_malloc(sizeof(*smpp));
smpp-transmitter = -1;
smpp-receiver = -1;
+smpp-is_ssl = is_ssl;
+smpp-dump_pdu = dump_pdu;
smpp-msgs_to_send = list_create();
smpp-sent_msgs = dict_create(16, NULL);
list_add_producer(smpp-msgs_to_send);
@@ -143,7 +164,9 @@
smpp-dest_addr_ton = dest_addr_ton;
smpp-dest_addr_npi = dest_addr_npi;
smpp-alt_dcs = alt_dcs;
+ smpp-pack_7bit = pack_7bit;
smpp-my_number = octstr_duplicate(my_number);
+ smpp-forced_sender = octstr_duplicate(forced_sender);
smpp-service_type = octstr_duplicate(service_type);
smpp-transmit_port = transmit_port;
smpp-receive_port = receive_port;
@@ -154,6 +177,9 @@
smpp-priority = priority;
smpp-conn = conn;
smpp-throttling_err_time = 0;
+
Re: TON error on SMSpush
Rory Campbell-Lange wrote: Hi Alex. Thanks very much for your mail. I am using 1.3.1. The problem I reported seems to be solveable by also setting the dest-addr-npi = 1. the config directives *should not* depend on eachother. Alex, if you test this and can reproduce, could you make a bug report to http://bugs.kanne.org please. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Multiple smsc groups
Is it ok to have multiple smsc groups? of course. We have up to 140 smsc groups in one Kannel instance ;)) If I try and set both of these to run concurrently, I get a failure on one of the SMSC connections. 2003-03-27 21:34:59 [7] DEBUG: SMPP[orangeshort]: Sending enquire link: 2003-03-27 21:34:59 [7] DEBUG: SMPP PDU 0x8126760 dump: 2003-03-27 21:34:59 [7] DEBUG: type_name: enquire_link 2003-03-27 21:34:59 [7] DEBUG: command_id: 21 = 0x0015 2003-03-27 21:34:59 [7] DEBUG: command_status: 0 = 0x 2003-03-27 21:34:59 [7] DEBUG: sequence_number: 7 = 0x0007 2003-03-27 21:34:59 [7] DEBUG: SMPP PDU dump ends. 2003-03-27 21:34:59 [7] ERROR: Unknown SMPP_PDU type, internal error. 2003-03-27 21:34:59 [7] ERROR: SMPP[orangeshort]: PDU unpacking failed. 2003-03-27 21:34:59 [7] DEBUG: SMPP[orangeshort]: Failed PDU follows. 2003-03-27 21:34:59 [7] DEBUG: Octet string at 0x8125a90: 2003-03-27 21:34:59 [7] DEBUG: len: 12 2003-03-27 21:34:59 [7] DEBUG: size: 13 2003-03-27 21:34:59 [7] DEBUG: immutable: 0 2003-03-27 21:34:59 [7] DEBUG: data: 80 00 00 00 00 00 00 03 2003-03-27 21:34:59 [7] DEBUG: data: 00 00 00 07 2003-03-27 21:34:59 [7] DEBUG: Octet string dump ends. 2003-03-27 21:34:59 [7] ERROR: SMPP[orangeshort]: I/O error or other error. Re-connecting. while this is the same thread, you see this in the brackets (here [7], which means thread-id 7), it seems that the smsc responds with an upknown PDU response on the enquire_link request. Does this happen each time Kannel sends the enquire_link PDU to the SMSC? Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
[RFC] adding new foobox modules to cvs
Hi list, I'm wondering how (which means in which source directory organization) we should add new foobox'es (ie. smppbox, emibox, sqlbox, etc.)?! Those are 'server-side' implementations and use Kannel's internal message communication to act as an smsbox attached to bearerbox. I'd like to keep them in seperated cvs modules. This makes Kannel the core system and if you need server implementations you can plug-in the smppbox or other. How should this be organized conferning source tree layout and build process? Any ideas? A nice approach would be something like $ ./configure --with-server smppbox and the corresponsing files from cvs module smppbox would go into a directory gateway/servers/smppbox. Or maybe --with-addon?! Comments please. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Wappush not sending response back in the proper format
Ok, I checked this: When I use your PAP document ?xml version=1.0? !DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP 1.0//EN http://www.wapforum.org/DTD/pap_1.0.dtd; pap push-message push-id=235http://127.0.0.1:8080/wappush104871366918042893839821184112102 4 source-reference= address address-value=WAPPUSH=+123456789/[EMAIL PROTECTED]/ quality-of-service priority=medium delivery-method=unconfirmed bearer=sms/ /push-message /pap and run it via test/test_pap I get an error that states that the address parsing failed, because it could not find TYPE. In fact the PI seems to write this in lower-case in the address entitiy. When you switch this manually to upper-case test_pap works, and even a test/test_ppg call against Kannel's PPG works without a complain. See attached log of that. Now the question is who acts wrong: - Jatayuu PI, because of writing the TYPE in lower-case - Kannel, because of not accepting lower-case Anyone checked the specs?! Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are ppg.log Description: application/unknown-content-type-txtfile
Re: Wappush not sending response back in the proper format
to answer this on my own. The PAP spec does not quote any must or should be in upper-case. Even the example in section 12.1. is using this: pap push-message push-id=[EMAIL PROTECTED] address address-value=wappush=12345/[EMAIL PROTECTED]/address /push-message /pap so obviously in lower-case. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Wappush not sending response back in the proper format
I will make a bug report of this to mantis, resolve, fix and close in a bunch ;) Fix will be in cvs in a couple of minutes. Could you please try then the cvs head tree. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [PATCH] [BUG] http.c does not follow redirections at all
Angel Fradejas wrote: Current http.c does not follow 302 Location redirections at all. I tracked down the problem down to the handle_transaction() function. If we leave trans-host and trans-port set there, there will be no parse_url() for the redirection, and the original url is fetched again and again :-( Attached is a patch that fixes it. yep, seems get_redirection_location() does not what it should do. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [PATCH] [BUG] http.c does not follow redirections at all
Andreas Fink wrote: Did everyone test this with and without Proxy? While using a proxy is exactly the locatio where the host would stay the same. I have to addmit, no, I didn't test proxy mode. Andreas, can you do this please. The code is already commited. If there are problems please report. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Help with Windows
The problem now is when I tried the next step: ./configure. There'sa problem with gcc and cc compilers, which seems to not come with the CygWin environment. Or maybe they come but i don't know how to install them. These are the messages from CygWin: loading cache ./config.cache Configuring for Kannel gateway version 1.2.1 ... Running system checks ... checking host system type... i686-pc-cygwin checking for gcc... no checking for cc... no configure: error: no acceptable cc found in $PATH Please, if someone knows how to solve this problem in order to keep going with Kannel, I would be grateful if he/she helped me. Thanks for your time, Sincerely, Javier Giménez I guess you haven't included the adequate items while running Cygwin's setup.exe. Please simply re-run setup.exe and check that you include the 'Develop' section to. gcc et al are included there. And by the way, yes, it's off-topic ;) Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [PATCH] [BUG] EMI2 wait-ack-expire fix
Angel Fradejas wrote: Attached an simple patch to fix a typo in the EMI2 driver, related to wait-ack-expire behaviour. Stipe, please, don't close your wincvs and keep on commiting ;-) how do you know about that? ;))) Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [PATCH] [BUG] EMI2 wait-ack-expire fix
Angel Fradejas wrote: Attached an simple patch to fix a typo in the EMI2 driver, related to wait-ack-expire behaviour. Angel, thanks for the patch. Can you please comment why this is a typo or any other please vote if this is a fix?! Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Problem in WAPPUSH
forget about this. The HTTP header in the PAP control entity gets handled. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Problem in WAPPUSH
Hi, can you please send us a log of the HTTP request that the PI sends to PPG. You can capture that like this: $ ./gateway/test/test_http_server /tmp/pi.log which starts a HTTP server at port 8080 and simply let the PI trigger the same way as it would to the PPG. Please provide us then the pi.log file as attachement. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Possible race condition with HTTP.c
Hi Michael, can this be reproduced with setting up an apache that has a max client limit set also? Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [FYI] a new smsc (Minick Ltd LAPI)
Aarno Syvänen wrote: Hi List, I wrote last week a smsc drive (that's I were not answering push question ?) This could, in principle, be added to cvs, if there is interest. Some stabilation is required, however. I guess if it's in SMSConn API style, it's always welcome. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [PATCH] smsc_cimd2.c sleep times
Stipe, could you revert smsc_cimd2.c to version 1.7 and then apply the second patch? done, please check. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Possible race condition with HTTP.c
Michael Mulcahy wrote: I have attached a simple perl script that reproduces the problem (for me anyway:). It listens on port 8080 and disconnects the listener socket when a connection attempt is made. My test case consists of fakesmsc - bearerbox - smsbox - perl script with smsbox sending http requests to the machine that this script is running on at port 8080. Fakesmsc sends in 10 MO requests and while the smsbox is invoking the script it crashes. yep, I can reproduce this even on Cygwin. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Possible race condition with HTTP.c
yep, +1, commited the fix to cvs. Thanks Michael! Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [PATCH] [BUG] EMI2 wait-ack-expire fix
has been commited, thanks. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [PATCH] smsc_cimd2.c sleep times
so the question is - why mine cvs update didin't fetch version 1.9? I guess it has still it's sticky bit on it for the revision you updated previously. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: MMS trials, getting insane trying to decode pdu's!
Bas A. Schulte wrote: Hmm. How on earth would I have known that? :) I figured with about 3 documents in front of me I'd have enough but no! I also need the WSP spec (WAP-203-WSP-2504-a.pdf in WAP 1.2.1 which is WAP-230-WSP-20010705-a.pdf in WAP 2.0)... Luckily that one has some examples on decoding. Those specs are really hard to work with! as I said: the entry border is high, but after that *everything* starts to make sense ;) reading the WSP code in Kannel :) both! When you see how the WSP header code is parsing the headers you'll start to understand the specs too. Maybe we should have commited Kannel's sources as reference to the WAP Forum specs ;)) Thanks a bunch, gonna do some more decoding today BTW, can anyone recommend a good resource on this (besides the specs themselves)? A book maybe or a web page? Better examples sure would help out here! I have google'd for those too. No luck. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: sms message format to access URLs
Steven Sabado wrote: may i ask if what is the specific format on how to access the http using a simple sms message? do i need a specific format in order to a url site? and if there are key words, does kannel have it's own keywords or does the developer need to specify it's own key words? thanks in advance :) I guess most answers are within the user's guide: http://www.kannel.org/download/kannel-userguide-snapshot/userguide.html Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: UCP protocol with GSM modem
Tronet Sarah wrote: As far as I know, it is possible to connect Kannel to the mobile network via a GSM modem (e.g. Siemens M20). In that case, I would like to connect my terminal application to Kannel via UCP-EMI protocol as if Kannel was my SMSC in order to receive SMS from the mobile network? Kannel does yet not include server-side implementations of SMSC protocolls, excepts it's HTTP interface provided via smsbox. But this is to come. We have smppbox and emibox which implement the server-sides that will be added as seperate CVS modules to the Kannel reposority in some near future. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: CDR output
Has anyone implemented a CDR interface on to Kannel. I'm not talking a billing engine, just something that outputs simple CD records that can be processed elsewhere ? yes. Bearerbox provides it's own access-log, hence that are your CDR records. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Hello LIST
Hi Vijay, Vijay Patwari wrote: Hello All, i hve an smil file cats.smil( which contains text cat image audio) , i wnt it to be represented it into mms (.mms), hw this possible.., can u say me. hw to create mms message. say me. first I'd like to ask you an counter-question: Have you read *all* MMS specific specification papers from the WAP Forum? If no, then please do before asking such complex things on the lists here. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [PATCH] small fix to previous patch
ok, this has been commited to cvs now. But we *SHOULD* abstract this to the upper SMSCConn layer, so that the new config directive is available for all SMSC module types. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: SMPP Service Type --wap
Guanghua Hou wrote: When push message is sent through SMSC. SMPP v3.4 'submit_sm' is used by kannel. Kannel sets 'service_type'as NULL and 'protocol-id' as zero.The short message is WDP/WSP encoded PDU. When this message is sent to Terminal, how does the terminal distinguish application type of short message? How does the terminal know this message is WAP push message? Maybe the terminal treates it as normal short message of ascii. by the UDH header. Within the UDH header you specify the receiver port (like a socket port on regular machines). Check our the UDH headers sequence when pushing a SL or SI document via Kannel's PPG. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Wap Push SI compliant PDU (for Openwave wap browsers as Sharp GX10)
Enzo dell'Aquila wrote: Hi Aarno, Sharp GX10 works well if you don't send AF, so Kannel PPG should have no problem with Sharp. Other Openwave browsers should work too. so there is no problem here? is this right? Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Strange error message
Jarrod Hermer wrote: While running Kannel 1.3.1 in Cygwin the following error message was printed to screen by the bearerbox: 7 [unknown (0x74C)] bearerbox 1960 pthread_cond::Signal: Released too many threads - 1 now 1 originally Any ideas what might have caused this and what the implications are? no ideas. Please beware that Cygwin's pthread stack is *not* as reliable as on real unix-flavored machines. To make it simple: it's Cygwin's fault! ;) (but don't ask me why) Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
[FYI] HTTP smsc modified/fixed
Hi list, I have patched gw/smsc/smsc_http.c to fix a couple of issues, including: * bearerbox crash if smsc is shutdown and /status is called * don't 'fail' messages if the connection could not be established to HTTP SMSC, instead re-queue and respect 'reconnect-delay' for a sleeping period. Should work now more smoothly. BTW, a new system-type 'brunet' was also added. This is the client side implementation of Brunet's interface. (It's mostly properietary, but that are all HTTP inerfaces for SMS transmissions ;) Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: SMPP Service Type --wap
Guanghua Hou wrote: How phone to know the application type? So SMSC should transfer some smpp headers to phone and the header value is written by Kannel. Now I think the header is service_type and its value is WAP. But kannel sets this value as NULL. According to what you mean, phone will know the message is binary message and know the message is WDP PDU if received message is binary. yes. the SMPP service_type is a thing to say the SMSC what kind of application data you carry out to the user. The phone itself will recognize this via the UDH header. So you *should* be able to push WDP PDUs as binary SMS without setting explicitly the service_type in the SMPP protocol. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: SMPP Service Type --wap
According to what you said, 'service_type' setting is optional.If it's null, phone shall also recogonize WAP application. yes, it will recognize either via the UDH header port or the token that has been encoded within the UDH header while using PPG's push capabilities and setthing the X-Wap-Application-Id. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
[RFC] Telit GSM862 GSM modem?
Hi list, anyone ever tried to use the industry GSM862 modems from Telit (IT)? They are pretty cheap, compared to Siemens or Falcom. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [RFC] Telit GSM862 GSM modem?
anyone ever tried to use the industry GSM862 modems from Telit (IT)? They are pretty cheap, compared to Siemens or Falcom. hmmm, no one? Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Access limitation on wap gateway side.
Vjacheslav Chekushin wrote: Hi, Angus and Andreas. Ok. After discussion I must agree with you that forcing HTTP request to go from specific interface is good way to solve my problem. So go to solution: http.c function get_connection has hardcoded our_host = NULL, binding not forced now. I propose add configuration variable (http-interface-name?) and use it as value for our_host. Do you agree with it? I can write patch for this. so you want a configurable our-interface is xy only for the HTTP client calls? Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Kannel SMPP interface !
yes there is. We at Wapme have those beasts arround here still in cages ;) Reason: We need a modularized configure/make process to have them hooked in cleanly and keep them seperated in own cvs modules. So could some people *please* think of how to handle configure/make of external cvs modules with the gateway cvs module as base core. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Kannel SMPP interface !
Himalay Gopu schrieb: I went wrong in explaining the problem But the link is for a SMPP simulator but i would like to have a open source SMPP/EMI server which will inturn connect to Kannels bearerbox which has different SMSC connections configured yep, our smppbox and emibox are SMPP servers and EMI server that connect via smsbox interface to bearerbox and provide full transparent proxying. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: It's possible to send Push SI message through Virtual SMSC?
Mauricio Ramos wrote: Hi Folks, I would like to use a GSM phone as a Virtual SMSC (AT2) to send WAP Push SI/SL messages to another GSM phone. Is it possible? How? yes, should be possible. Some GSM modems require to have alt-dcs set when sending binary SMS. I guess this can't be handled currently by Kannel's PPG, because it sets the normal DCS value. Aarno, any idea from your side here? Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Strange smsbox/bearerbox problem : SMS messages not being sent
Rory Campbell-Lange wrote: My smsbox/bearerbox setup has been working flawlessly for about a month. However recently I have had to restart the system after a number of messages are shown as queued but not sent. On restarting bearerbox the messages flood through. The problems start with a message I sent myself at 7.30am in the morning (a sys_chk message). Although this gets recorded in bearerbox it wasn't in fact sent. See *a*. Then, as about 100 scheduled messages are rapidly fired off at 8am, the first through are sent through (see *b*), then the next lot (about 54) are _not_ sent, but show up as queued. See *c*. I'd be most grateful to know the reasons for this problem, if it can be identified, and ways of troubleshooting. So I need to put in a loop on the perl message sending program (its for a medical trial for diabetic kids). hmm, I don't see any submit_sm_resp PDUs that ACK the submit_sm from the SMSC side? Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [PATCH] smsc_cimd2.c sleep times
Dziugas Baltrunas wrote: something mysterious has happend after commiting cimd2_smsc2.c patches written by Angel Fradejas. there were problems with sleep times and Angel wrote the final patch (file was called cimd2_fix2.diff) and it was commited by Stipe. recently I did cvs update and seems like most recent fix wasn't applied or was applied incorrectly? attached patch fixes these sleep times (it's made with older smsc_cimd2.c). if I'm wrong, Stipe and Angel, please correct me. Angel send 2 patches. One stating the fix and then updating that patch itself. I commited the later one. Angel, is current cvs ok from your perstecpitve? Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: wml in wap push
Hi Amit, amits schrieb: Hiii We are trying to push a multipart wap push to the phone..we done SI and SL successfully..but in this case we are facing problemsnothing is delivered on the phone we try same in two ways First we create a multipart message through nokia internet mobile toolkit 3.1...in this file we add one .sic file and one wmlc file according to nokia docs.and it working fine on simulator.we tried to send this file using test_ppg with a working pap. but nothing comes on the phone. Second we created a file having a pap and wml code in a single filebut test_mime sows error while parsing if u need the files code pls inform us...we shall send you pls guide us to do same in right way... first of all, the PAP document has to be seperate from the content itself. Can you send us the files you pass to test_ppg and the exact command line you use while calling it?! Can you also describe what you are trying to do? Pushing a pre-compiled wml deck? Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Kannel w. TETRA Packet Data
R. Dam wrote: Good news guys, I've just performed some life tests with Kannel with TETRA Packet Data on the Nokia THR850 through our TetraNode software. Browsing the net with WAP works perfect on this TETRA terminal. (The WAP software in this mobile is the same as the software used in the Nokia 8310/1.0). So here's your confirmation that Kannel works with TETRA Packet Data. thanks a lot Robbert! I'll forward this to the Open Group for the reference parts. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [REQ] UAProf suppport
Hi Paul, Paul Keogh schrieb: our REFPOOL tests are doing well. Handset manufacturers claim the lack of UAProf support within Kannel. Is there any more details about these claims - ie. what exactly are they claiming is missing ? now basically they complain that Kannel does not check the UAProf profile of a device and hence does not recognize that certain mime-types can or can't be accepted by the device. Can someone please check if UAProf is a mandatory feature for WAP 1.2.1 (jun)? Is there anyone interested to pick this issue up and work on it? The Profile, Profile-Diff and Profile-Warning HTTP headers are all defined, as is the uaprof content type in WSP 1.2.1. Is the question what the gateway should do with this information, other than pass it on to the HTTP server ? yes, I guess UAProf is not only about passing the information. It is also about dealing with it in terms of allowing to modify mime-types to fit the needs of the device. Or am I wrong here? Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Kannel SMPP interface !
Aarno Syvänen wrote: You mean making cvs modules located in different machines ? no, I'd like to have the current gateway cvs module as the base component and add-ons (ie. smppbox, emibox, mmsbox) to be extendable to the gateway source. Basically something similiar as the Apache guys did with their APR (apache portable runtime). Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Kannel SMPP interface !
Alex Judd wrote: No, I think Stipe's on about the discussions to build a more module based build with bearerbox forming the core - ie. - smsbox - wapbox bearerbox - smppbox - etc. if we split the modules out a little cleaner like this, then you can checkout just the base and the module you want. It shouldn't be a big job, just need to freeze a cvs branch while someone starts it would be my thoughts. It would be a good incentive to get Wapme to let loose the smppbox they've got chained there :) yep, it's waiting to be freed! ;)) same with mmsbox (our MMSC implementation). Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
[RFC] changing defaults of SMPP TON and NPI for MT?
Hi list, I'd like to have a quick voting for chaning the current defaults settings for the SMPP module for the TON and NPI values. Currently we have: /* setup default values */ pdu-u.submit_sm.source_addr_ton = GSM_ADDR_TON_NATIONAL; /* national */ pdu-u.submit_sm.source_addr_npi = GSM_ADDR_NPI_E164; /* ISDN number plan */ pdu-u.submit_sm.dest_addr_ton = GSM_ADDR_TON_NATIONAL; /* national */ pdu-u.submit_sm.dest_addr_npi = GSM_ADDR_NPI_E164; /* ISDN number plan */ I'd like to change to: pdu-u.submit_sm.source_addr_ton = GSM_ADDR_TON_INTERNATIONAL; pdu-u.submit_sm.dest_addr_ton = GSM_ADDR_TON_INTERNATIONAL; please votes and comments. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Fw: Incorrect Validity Time
Hi Patrick, my GSM provider has requested to to put the Validity flag to 8 hours. we did it but aftter about 10 hours the SMSC started to have these errors PROVIDER ERROR MESSAGE 06/06 18:52:32 AMP:uac_amppdu001 trace AMP PDU Trace, SMPP: Incorrect Validity Time: 030607030006076+ 06/06 18:52:32 AMP:uac_amppdu001 trace AMP PDU Trace, SMPP: Incorrect Validity Time: 030607030006076+ 06/06 18:52:32 AMP:uac_amppdu001 trace AMP PDU Trace, SMPP: Incorrect Validity Time: 030607030006076+ 06/06 18:52:32 AMP:uac_amppdu001 trace AMP PDU Trace, SMPP: Incorrect Validity Time: 030607030006076+ 06/06 18:52:32 AMP:uac_amppdu001 trace AMP PDU Trace, SMPP: Incorrect Validity Time: 030607030006076+ 06/06 18:52:32 AMP:uac_amppdu001 trace AMP PDU Trace, SMPP: Incorrect Validity Time: 030607030006076+ in the sms box log file we get a error response_sm 0X012 which i belive is a reserved message.. what could it be? why do the times on bith servers need to be in sync? the error you quote can't be inside smsbox log. You may meen bearerbox's log? Can you provide us a log extract of it?! Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Strange smsbox/bearerbox problem : SMS messages not being sent
Rory Campbell-Lange schrieb: Thanks very much for your message, Stipe. Upon enquirey it appears that the target SMPP host only allows 6 messages a second to pass through on our service. I was trying to send 150 messages in less than a second! yeah, Kannel performs very well ;)) I've slowed down the sending system. However, is there a way of throttling the number of messages sent in a second or automatically retrying requeued messages when sending clients try to send too many messages in a few moments? not directly in the SMPP module. There is an implementation inside the EMI/UCP module. This is definetly a issue for the SMSCConn abstraction layer. Bruno and Angel, are you guys agree'ing? Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: FW: Updated Charset.c with greek Alphabet 7-bit encoding
Andreas Fink wrote: will probably mean it works in greece but breaks compatibility in other countries. I vote -1 for this patch as is. Proper implementation of greek has to be made different. ISO-8859-1 is also not appropriate so there's more to this. ok, these are serious concerns from Andreas. Is there a chance that we can use iconv for the mapping?! Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [RFC] changing defaults of SMPP TON and NPI for MT?
Alexander Malysh schrieb: Hi Stipe, -1 from me. How do you want recognize national numbers? International numbers can be simple detected. They have '+' in front and then we set ton to international and remove the plus. hmm, so you *require* users to send to=%2b49xxx at sendsms HTTP interface. If someone sends to=49xxx then it will be send with national TON. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Strange smsbox/bearerbox problem : SMS messages not being sent
Alexander Malysh wrote: hmm, sleep is very bad (imho). In this sleep time you can maybe handle 100 delivery receipts instead just sleeping. It would be great to add abstracted bandwidth calculation code to kannel and then send only if bandwidth allow this. so sleeping makes only sense if the MT sending thread can be send to sleep and the MO thread yields for the CPU and the connection. If the modules use *one* thread for MT and MO, then sleeping is sort of a problem, that's right. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
[FYI] recent CIMD2 patch commited, please check
Hi list, I have commited now: 2003-06-19 Stipe Tolj [EMAIL PROTECTED] * gw/smsc/smsc_cimd2.c: fixed a bug inside CIMD2 module. Thanks to Per Skaglund [EMAIL PROTECTED] for the patch. [Msg-ID: [EMAIL PROTECTED]] if you run CIMD2 connections, please update your local CVS tree and try this. If there are problems please shout. Angel, any chance you can give this a quick try? Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Bug in log.c
a) change gwthread code to use the freed slot ID number instead of incrementing. So we will never have a thread id above 1024 (which is the hard thread limit). b) thing how we can map the thread to the exlusive log file to be honest I'd like to pick a), because b) should be pretty fast because the logging functions are called a lot on high-load systems, so this has to be very fast and array lookups are pretty fast. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Strange smsbox/bearerbox problem : SMS messages not being sent
Rory Campbell-Lange wrote: The only error codes I'm getting are: 2003-06-06 20:42:53 [8] ERROR: SMPP[orangelong]: SMSC returned error code 0x0045 in response to submit_sm. according to SMPP specs this is considered to be a *general* error for a submit_sm PDU. (seee SMPP v3.4, p. 113). Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Bug in log.c
ok, I just commited this: 2003-06-19 Stipe Tolj [EMAIL PROTECTED] * gwlib/gwthread.h, gwlib/gwthread-pthread.c: added function gwthread_table_slot() to provide the slot integer of threadtable the thread is using. * gwlib/log.c: fixed Michael's reported bug for the logging functions. please update your trees and check. It implements the module access to the thread[] mapping table inside the logging module to ensure we don't access over the array limit. Because gwthread_self() is unique and assigned to a free slot when the thread is registered, also (gwthread_self() % THREADTABLE_SIZE) is unique and provides us with the correct slot the thread belongs to. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [PATCH] rewrite/cleanup of dlr handling (new)
Nisan Bloch wrote: Hi what happened to this? I'm just reading it. Unfortunatly it's huge and even in unified diff almost unreadable to understand what happens. Maybe you Nisan can explain a bit?! Have you tested Alexander's code again SMSCs? Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Strange smsbox/bearerbox problem : SMS messages not being sent
Andreas Fink wrote: AT2 module sleeps anyway and waits for ACK from modem before proceeding. So adding sleeps there is not making any sense unless you wana limit it to have only 1 message every minute or such. ok, I wasn't aware of it right now. That's fine with me then. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [PATCH] rewrite/cleanup of dlr handling (new)
Alexander Malysh wrote: sorry first mail has wrong diff :( attached big patch does following: 1) adds more abstraction to dlr handling 2) makes it easier to add new dlr storage types to kannel without touching a dlr-core code 3) makes dlr-core ready for coming (hopefully soon) modules API 4) makes handling/creating of dlr messages uniformly over all storage types Please look in it. Comments are very welcome... ok, looks good to me. +1. will commit this. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [PATCH] rewrite/cleanup of dlr handling (new)
Alexander Malysh wrote: i found a small memleak after it ... Attached you can find corrected version of this patch. I can say, mysql and internal where tested and works on our production systems without any problems. libsdb is not tested yet, but should work, because i have not changed any calls to the library itself. So please people, who use libsdb, test it! What happens is pretty simple ;) 1. if dlr_init calls then here storage will be initilialized return pointer to operations struct. pls consult dlr_p.h for possible operations on the storage. 2. If dlr_find calls then core dlr do following: call storage get function create new dlr message check if this end status of message (e.g. delivered or undelivered) and then delete the message by calling of remove storage funct. if end state not reached then call storage update status entry funct. (its optional, that means, if storage define this funct. it will be called otherwise not) 3. dlr_status just call storage status funct. and so on ... +1, commited to cvs. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
[RFC] cookie support per detault in wapbox?!
Hi list, I'd like to throw the --enable-cookie directive from configure and make cookie support for wapbox now a permanent default feature. Any objections for doing this? Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Bug in log.c
Andreas Fink schrieb: so what if I have a thread 10 which is a EMI/UCP process and suddendly a new process gets added with 1034? we have a new conflict... ahhh, Andreas *is* right here. We don't take into account that the threadtable handling does a linear scan in the threadtable to find a free slot. So the gwthread_self() id can't be used to determine a unique thread id with the module operator, right?! Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Bug in log.c
Michael Mulcahy schrieb:
so what if I have a thread 10 which is a EMI/UCP process and
suddendly a new process gets added with 1034? we have a new conflict...
No, that what I thought as well, but the gwthread-pthread.c takes
care of that problem.
see gwthread-pthread.c
/* Find a free table entry and claim it. */
first_try = next_threadnumber;
do {
ti-number = next_threadnumber++;
/* Check if we looped all the way around the thread table. */
if (ti-number == first_try + THREADTABLE_SIZE) {
panic(0, Cannot have more than %d active threads,
THREADTABLE_SIZE);
}
} while (THREAD(ti-number) != NULL);
THREAD(ti-number) = ti;
active_threads++;
where THREAD(t) is:
#define THREAD(t) (threadtable[(t) % THREADTABLE_SIZE])
The thread number is incremented and the mod 1024 position in
array is checked to see if an entry exists. If an entry exists then
the thread number is incremented again.
ok, once again I'll chance my opinion ;))
Andreas, do you agree that a (gwthread_self() % THREADTABLE_SIZE)
gives us a runtime unque ID of the thread?
Stipe
[EMAIL PROTECTED]
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf
Tel: +49-211-74845-0
Fax: +49-211-74845-299
E-Mail: [EMAIL PROTECTED]
Internet: http://www.wapme-systems.de
---
wapme.net - wherever you are
GNU autoconf experts arround?!
Hi list, I'm fidling arround with a modified configure/make process to allow adding new add-on boxes (ie. smppbox) to the build. I come up with --with-box[=NAME] inside configure.in and this works, even while this is really an un-nice hack ;) Unfortunatly I can't give more then one --with-box statement to configure. Can anyone give me a good hint or example code on how to implement --with-foobar=1 --with-foobar=2 ... inside M4 macro code for confifure.in??? Any help is appritiated, since release date for smppbox and mmsbox depends on it ;) Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
[FYI] RADIOUS accounting proxy commited
Hi list, I just commited this to cvs: 2003-06-20 Stipe Tolj [EMAIL PROTECTED] * Makefile.in: added compilation of RADIUS related files inside radius/. * doc/userguide/userguide.xml: new MSISDN provisioning section describing the use of the RADIUS accounting proxy thread. * gwlib/cfg.def: removed properietary groups that are *not* used inside Kannel's tree and added 'radius-acct' group configuration directives. * gw/wap-appl.c, gw/wapbox.c: added RADIUS accounting proxy related calls. * radius/*: added RADIUS accounting proxy implemenation. * test/test_radius_*.c: added some testing applications for the RADIUS routines. which means we have now a real MSISDN provisioning boarded inside Kannel using a RADIUS accounting proxy thread inside wapbox. See user's guide for guidance. It works here at Wapme for some time inside our MMSC implementation, because we pick the 'From' MMS header using the MSISDN provsioning value provided by the WAP gateway (wapbox) directly. The only thing that needs work on is the MD5 shared secret re-computation to ensure NAS and we are having the same shared secret. Usually I'm aware on how this is done, but it seems I can get this right with our Ascend MAX2000 we have here arround. BTW, we used GNU-radius as the RADIUS server back-end for authentication and account packet forwarding. Any help in getting the damn shared secret re-computation done right is highly welcome. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [FYI] RADIOUS accounting proxy commited
huangcy wrote: hi,list: when will kannel support wap2.0? now that's a good question ;) I guess this depends on how many people there are outside using Kannel and want to contribute as module maintainer. Which means people that pick up a certain issue (like Aarno does for PPG) and provide their code to the group. Currently we are to few people in having the WAP 2.0 stack implemented in a short time frame. Please don't forget that we have a more huge architecture to maintain (with the SMS gateway part, and now even MMSC), so it's not only the WAP gw we have to deal with. And again: contributors are *highly* welcome! This is an open source project, which means *anyone* can contribute as long as their contributions show up the required quality. Ok, quality is somethign subjective, but now, that's like. There is always someone who has to pick the thumb up or down ;)) (mainly we do with votes) Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: EMS Support
Xavier RODRIGUEZ wrote: Hi, Is it possible to send an EMS with kannel ? The response seems to be yes but is there any ems generator or something to turn an ems discriptor file into a binary sms Anybody has tried to send an EMS with kannel ? yes, there have been a lot of people sending EMS with Kannel. Note that Kannel is *only* responsible for the physical sending to the SMSC, not for the compilation of the binary format of an EMS and the segmentation (if required). That generator you talk of is out of scope of Kannel and can be provided as external module. Maybe someone who has an adequate EMS generator solution could write an emsbox (connecting to bearerbox) and basically generating the required Kannel msgs to pass to bearerbox?! Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
