Re: splitting messages
Jeetendra Singh wrote: Because of billing issues. We do this with the operator NetCom in Norway. The price is set as the originator in the first message, the remaining messages have originator=00. I made a private patch to Kannel that take care of this, and it really does works fine. However, it may be Netcom changes the originator on their side after sorting out the billing - just a thought. Interesting!!! Do you mean NetCom will charge for only a single message if all the messages originated from my gateway contains same originator? -Jeetendra The actual problem lurking under all this is that bearer-based charging doesn't work very well for concatenated SMS. There isn't a really acceptable solution. Consider the case where the first message in a Nokia PM (with the magic charge me flag set in the sender address) arrives, but the follow-on packets don't. There you have the worst of both worlds, as the customer will be charged for content they will likely never even see. One solution I have seen implemented is the following variant of the receipt SMS solution -- where a second charged text message is used to tell the billing system that all parts of the message have been sent. MS ESME -(MO)-; Request for service (MT)--; Part 1 of content -(DLR); Part 1 delivered OK? . . . (MT)--; Part n of content -(DLR); Part n delivered OK? (MT)--; Charged MT, sent if all parts OK. Add the appropriate error handling, and you have a very complex and slow download server that is guaranteed not to cheat the user. As a side note: if the receipt needn't be visible to the end user, then a simple mechanism could use the protocol_id value 64 (decimal) for the charged MT. This is the dreaded PING SM (a/k/a Replace Message Class 0) which is neither displayed nor stored on SIM on most handsets. Another note: the MO request is MANDATORY. Consider a prepaid customer that has fallen below whatever balance the operator considers minimal to use SMS. In that case, the customer will have SMS MO barred, and will not be able to initiate the transaction. David WHITE ONE GmbH
Re: splitting messages
Title: Re: splitting messages thanks to all who got involved in this. I have certainly learnt much more about the issue now. excellent! a quick summary: I needed to have the split use different from numbers for billing reasons. We wanted to bill binary (ringtone and logos) on MT, but because of the splitting issue we were in danger of charging for every message. As charges are stated to the user simply, for example 1 euro per ringtone, it would have been messy to fix this. I also work for the carrier and my comments our billing systems were treated in typical telco style.. we arnt very flexible.. anyway.. the idea was to send the first of the split from a chargeable number and the rest from a non charging number.. simple if it works. Also this would work well with our prepaid customers. As we cant do this now we are faced with 2 more options. 1. send a chargeable ping message to the user. if this gets delivered ok then send the binary from a free short code. 2. implement MO charging. option 2 is the favourite here as it seems to be the established way of doing it. thanks to all mike
Re: MMS and stuff..
What is the current status for MMS and stuff ? Stipe.. you have been working on some stuff ? What does need help etc. ? mmsbox is present. We still need the --add-box switch in Kannel's configure to cleanly seperate cvs modules and the build process. @Alexander: could you preliminary release your new autoconf build tarball snapshot? I could pull that from your cvs machine and drop it to a www.kannel.org place for review of developers? Which one to take? 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 and stuff..
Hi Stipe, On Thursday 21 August 2003 10:12, Stipe Tolj wrote: What is the current status for MMS and stuff ? Stipe.. you have been working on some stuff ? What does need help etc. ? mmsbox is present. We still need the --add-box switch in Kannel's configure to cleanly seperate cvs modules and the build process. @Alexander: could you preliminary release your new autoconf build tarball snapshot? I could pull that from your cvs machine and drop it to a www.kannel.org place for review of developers? Which one to take? heh, it's not so easy because I have moved some of source files to another places (e.g. tried to group wap things)... Please give me some time for looking, what we can do in kannel now without doing too many changes... 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 -- Best regards / Mit besten Grüßen aus Düsseldorf Dipl.-Ing. Alexander Malysh ___ Centrium GmbH Vogelsanger Weg 80 40470 Düsseldorf Fon: +49 (0211) 74 84 51 80 Fax: +49 (0211) 277 49 109 email: a.malysh at centrium.de web: www.centrium.de msn: olek2002 at hotmail.com icq: 98063111 ___ Please avoid sending me Word or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html
RE: splitting messages
hmm.. interesting.. what is this custom billing? what is this billing port? where can i find out more info about this? and will this work with both contract and prepaid customers? thanks mike -Original Message- From: Konstantin Vayner [mailto:[EMAIL PROTECTED] Sent: Thursday, August 21, 2003 1:17 PM To: [EMAIL PROTECTED] Subject: Re: splitting messages Not if you have an option to set custom billing - then you can choose billing port depending on split count DILWORTH MICHAEL wrote: hi yes this option has been mentioned.. but then this means all our binary messages will have to be the same size, or at least have the same number of splits. mike -Original Message- From: Arne K. Haaje [mailto:[EMAIL PROTECTED] Sent: Thursday, August 21, 2003 11:15 AM To: [EMAIL PROTECTED] Subject: Re: splitting messages torsdag 21. august 2003, 09:57, skrev DILWORTH MICHAEL: thanks to all who got involved in this. I have certainly learnt much more about the issue now. excellent! a quick summary: I needed to have the split use different from numbers for billing reasons. We wanted to bill binary (ringtone and logos) on MT, but because of the splitting issue we were in danger of charging for every message. As charges are stated to the user simply, for example 1 euro per ringtone, it would have been messy to fix this. I also work for the carrier and my comments our billing systems were treated in typical telco style.. we arnt very flexible.. anyway.. the idea was to send the first of the split from a chargeable number and the rest from a non charging number.. simple if it works. Also this would work well with our prepaid customers. As we cant do this now we are faced with 2 more options. 1. send a chargeable ping message to the user. if this gets delivered ok then send the binary from a free short code. 2. implement MO charging. option 2 is the favourite here as it seems to be the established way of doing it. Why can't you split the cost between the messages? If the price for a ringtone is 1 euro but it must be split into two messages, can't you bill those two messages 0,5 euro each?
Re: splitting messages
On Donnerstag, August 21, 2003, at 06:46 Uhr, Arne K. Haaje wrote: torsdag 21. august 2003, 06:41, skrev Jeetendra Singh: The reference number should not be confused with message id. A same reference number in UDH of multiple short messages identify them as part of same long message, so in such a case you will have same reference number in all segments of a long message whereas every such segment shall be assigned a unique message id. Also in this case, ETSI GSM Specs 3.40 clearly define that Each concatenated short message contains a reference number which together with the originating address and Service Centre address allows the receiving entity to discriminate between concatenated short messages sent from different originating SMEs and/or SCs. Also I couldnt understand what purpose it would solve to send op logo with different originators? Because of billing issues. We do this with the operator NetCom in Norway. The price is set as the originator in the first message, the remaining messages have originator=00. I made a private patch to Kannel that take care of this, and it really does works fine. However, it may be Netcom changes the originator on their side after sorting out the billing - just a thought. The better way to do this is to send one text message as you have been billed Euro to charge and send the logo separately. This way you can also send the logo over a cheaper path Andreas Fink Global Networks Switzerland AG -- Tel: +41-61-333 Fax: +41-61-334 Mobile: +41-79-2457333 Global Networks, Inc. Clarastrasse 3, 4058 Basel, Switzerland Web: http://www.global-networks.ch/ [EMAIL PROTECTED] --
Re: SMSC Connection using SOAP and FTP
On Donnerstag, August 21, 2003, at 01:05 Uhr, francesco emmi wrote: Hi all, I am using kannel with emi2 smsc protocol. Now I have to connect with a new SMSC which use a strange language to communicate with an SP.Communication language is not at protocol level, but at application level. I can summarize it in four step: 1) Transfer MMS or SMS content through FTP to Mobile Operator Repository 2) Ask a delivery Token through SOAP/HTTPS 3) Ask for content Delivery through SOAP/HTTPS. Is possible to specify different kind of SOAP Methods (one for MMS, SMS, EMS ecc,). And it is mandatory to include the token received in the last step. 4) Receive DLR through HTTP I Know that kannel has an http support, and that Oded Arbel wrote a SOAP module (in addition to MAM protocol which I'm still using!), but I' m wandering if they can be adapted to my task. Can someone help me? The best thing you can do is ask your SP to provide standard protocols using FTP/SOAP/HTTPS for delivery of SMS sounds like a very stupid way of doing business... ...but that doesn't mean you can not write a driver for such a freaky provider but I strongly doubt it would be of use for anyone else than this SP's customers (which probably are not that many). Andreas Fink Global Networks Switzerland AG -- Tel: +41-61-333 Fax: +41-61-334 Mobile: +41-79-2457333 Global Networks, Inc. Clarastrasse 3, 4058 Basel, Switzerland Web: http://www.global-networks.ch/ [EMAIL PROTECTED] --
