Re: devel Digest, Vol 21, Issue 7

You can use fakesmsc as a smsc  and test_http as a web site. But wrong
sequence number goes beyond of simple stress testing.

Aarno

On 14 Sep 2005, at 17:17, Mario Noboa wrote:

>
> Hi Stipe, few days ago i did a stress test with an operator, kannel  
> worked
> very well with 30 msg/s. But i had problems with more than 40 msg/s  
> in a
> smpp conexion. I set throughput=6 and max-pending-submits=50 but  
> didn't
> work.
>
> This error appears for each messange sent:
>
> 2005-09-02 11:15:51 [11943] [11] WARNING: SMPP[COM]: SMSC sent
> submit_sm_resp with wrong sequence number 0x0001001d
>
> I have a CPU system with 2 Gb and 1200 MHz. How would i configure  
> kannel for
> this stress test?
>
> Thanks for your help.
>
> Mario
>
>
> -----Mensaje original-----
> Date: Fri, 09 Sep 2005 16:19:12 +0200
> From: Stipe Tolj <[email protected]>
> Subject: Re: Limits of kannel
> To: Douglas Jurcovichi <[email protected]>
> Cc: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Douglas Jurcovichi wrote:
>
>
>> Hi folks,
>>
>>
>> What is the maximum traffic per SMPP port have you been worked  
>> (msg/s) ?
>>
>
> on a "normal" hardware machine, meaning single CPU system with  
> 500MB-to-1GB
> RAM
> and a 800-1200 MHz CPU (P4) you should do several thousand msg/sec...
>
> actually our local benchmarks on a more reliable server got up to 4000
> msg/sec.
> over 2-3 SMPP ports.
>
> Actually Kannel is high-performative. The bottle-neck will _ALWAYS_  
> be the
> upstream SMSC links itself.
>
> Stipe
>
> mailto:stolj_{at}_wapme-group.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/
> -------------------------------------------------------------------
>
>
>
> ------------------------------
>
> Message: 3
> Date: Sat, 10 Sep 2005 00:04:00 -0700
> From: Jim Torelli <[email protected]>
> Subject: Receiving and processing MMS messages
> To: Paul Keogh <[email protected]>, [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain
>
> Hey!
>
> Thanks for the info Paul!!  I'm moving this thread over to the devel
> list, as these questions are probably more appropriate here :)
>
> So basically I'm looking at writing a small app that will take in the
> notification from smsbox, pull out the URL of the content, pull it  
> down
> and process it.  Sounds very doable, just a couple questions mostly
> about Kannel, as I'm not familiar with the Kannel source base:
>
>
>> Kannel can capture the MMS notification SMS(es) and route them
>> to an application via the SMS Box sms service interface.
>>
> * Is there any info anywhere about how the message is handed from  
> smsbox
> off to the application?
>
>
>> Fetch the MMS message identified by the Content-Location MMS
>> header (this can be either a native HTTP operation or a WAP  
>> operation. If
>>
> WAP, you need a WAP client stack)
> * Does this mean it's my choice as to whether I want to use normal  
> HTTP
> or WAP as a transport, or are there certain instances where I'll be
> forced to use WAP as a transport?  Also, when I do an HTTP  
> operation to
> pull down the content, can I do it over the public internet or would I
> have to do it through the GPRS connection?
>
>
>
>> So you'll have to write some code. All the functionality is there  
>> in the
>> Kannel and MBuni libraries.
>>
> * If anyone can point me to any useful places in the API where I'll  
> need
> to reassemble and decode the pdus, pull down WAP content, etc, it  
> would
> be much appreciated :)
>
> Thanks!
> Jim
>
>
> On Fri, 2005-09-09 at 08:42 +0100, Paul Keogh wrote:
>
>>> I should probably back up to what we're trying to do.. We
>>> basically just want to be able to use a GSM modem to receive
>>> an MMS message, decode the contents, then either forward it
>>> off to an email address or just save it to disk..
>>>
>>> Is this something that can be done with Kannel and MBuni?
>>>
>>
>> Not out of the box.
>>
>> You don't receive an MMS message in the same way as you receive an
>> SMS. You receive the MMS notification and then you must fetch the
>> referenced MMS message. Check the OMA MMS client transactions spec.
>> for further details.
>>
>> Working through your use case;
>>
>> * Kannel can capture the MMS notification SMS(es) and route them
>> to an application via the SMS Box sms service interface.
>>
>> * Your app. needs to;
>>
>>     * Reassemble MMS notifications if necessary
>>     * Decode the WBXML binary encoding to get at the MMS
>> notification headers
>>     * Fetch the MMS message identified by the Content-Location MMS
>> header (this can
>>     be either a native HTTP operation or a WAP operation. If WAP,
>> you need a WAP client
>>     stack)
>>     * Do something with the message
>>
>> So you'll have to write some code. All the functionality is there  
>> in the
>> Kannel and MBuni libraries.
>>
>
>
>
> ------------------------------
>
> _______________________________________________
> devel mailing list
> [email protected]
> http://www.kannel.org/mailman/listinfo/devel
>
>
> End of devel Digest, Vol 21, Issue 7
> ************************************
>
>
>