Re: SPCC migration

Rafael 'Dido' Sevilla <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <[email protected]>
Next time, please do not cross-post the devel and user lists.  Post to
one or the other, but not both.

On Thu, Sep 02, 2004 at 03:15:20AM -0000, [email protected] wrote:
>   Does Kannel supports SMS MVAS Pre-Delivery Credit Check (SPCC) for CIMD2 
> implementation because the telco requires us to do so. 
> 

Not directly, and even I don't think it should EVER directly support
this highly telco-specific behavior.  Only one mobile carrier in the
whole world (Smart Communications), as far as I know, does this, and if
it ever becomes standard on Nokia CIMD2 SMSC's (it isn't in the CIMD2
spec, obviously), that's the only time it should ever have direct
support.

> Here's how it goes
> 
> B.	PREPAID WITHOUT SUFFICIENT BALANCE
> 1.)	Single Message
> 	Message with Tariffs – Message is not delivered to subscriber. No 
> deduction of any kind from subscriber’s balance.
> 
> 	Message with 0 Tariff – Message is delivered to subscriber.  No 
> deduction from subscriber’s balance.
> 

Clearly you'll need a way to figure out how to know a priori whether or
not a particular subscriber has any remaining balance.  Naturally, this
is beyond Kannel's scope.  Your own system determines whether particular
messages have any billing information attached, so this should be
entirely up to you.

By the way, if you want a patch to Kannel that will provide CIMD2
billing using TC/SD parameters the way Smart requires it, go here and
download my patch (which was rejected):

http://article.gmane.org/gmane.comp.mobile.kannel.devel/19470/

> 2.)	Concat Message
> 
> 	Message with Tariffs – All concat messages are not delivered to 
> subscriber.  Remaining CDRs of concat message should not be sent anymore to 
> SPCC for pre-credit checking. No deduction of any kind from subscriber 
> balance.
> 
> 	Message with 0 Tariff – Message is delivered to subscriber.  No 
> deduction from subscriber’s balance.

One of my main problems with Kannel is that it puts billing information
on all message fragments in a concatenated message.  Is that standard
practice with mobile carriers in the rest of the world?  Certainly the
mobile carriers here in the Philippines don't like it when you do that,
and recommend that you put billing information only in the first
fragment of a concatenated message, and set it zero in the remaining
pieces.  I had to write a patch that fixed this behavior for our
deployments.  If people think that this should be incorporated into the
Kannel mainline, I'll post it to the list.

-- 
dido
Sans les mathematiques on ne penetre point au fond de la philosophie.  Sans la
philosophie on ne penetre point au fond des mathematiques.  Sans les deux on
ne penetre au fond de rien.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.