"Arne K. Haaje" schrieb:
> 
> Some operators handle billing outside of the transport with stuff like
> SOAP. These cases should probably not concern Kannel.

that's the question actually. If the result on the SOAP request is
about to be "authenticated" within the scope of Kannel, then it MAY be
on interest in handling this inside Kannel. 

But the negative aspect is that we blow Kannel up with to much
individuality, which is not wanted actually. That's why I suggest an
abstract layer for this with an API. So user's can deside on their own
if they want the billing handled inside Kannel or in their backend
application layers.

> This is the essence of what it does;
> 
> +               /* Likewise, only use the billing info for the first
> part of a concatenated message */
> +               if ((msgno > 1) && part->sms.binfo) {
> +            octstr_destroy(part->sms.binfo);
> +            part->sms.binfo = NULL;
> +        }
> 
> Perhaps it can be enable with some config parameter like
> binfofirst=true

makes sense. Since splitting is done within the scope of smsbox.

> If there is interest for these pathces I will tidy them up a bit and
> submit them.

+1, go ahead. Won't hurt anyone.

Stipe

mailto:[EMAIL PROTECTED]
-------------------------------------------------------------------
Wapme Systems AG

M�nsterstr. 248
40470 D�sseldorf, NRW, Germany

phone: +49.211.74845.0
fax: +49.211.74845.299

mailto:[EMAIL PROTECTED]
http://www.wapme-systems.de/
-------------------------------------------------------------------

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.2.2 (Cygwin)

mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS
OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2
nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT
dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv
bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID
AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl
OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ
K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H
g2HyLAEKQIp30Q==
=aYCI
-----END PGP PUBLIC KEY BLOCK-----

Reply via email to