Hi Hammed:
We have developed our own billing application. I think the solution lies in
making kannel send delivery report for even sudmit to SMSC as suggested by
Vahid. This way you would always know from which SMSC your message has
finally gone. I hope this will work for you too.
regards
Shantanu Chauhan
----- Original Message -----
From: "Hammed A. Adeagbo" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, October 17, 2007 8:10 PM
Subject: RE: users Digest, Vol 17, Issue 26
Hi Shantanu,
I would like if you can share with me the type of application you are using
for billing with kannel. I have been working on kannel but not yet
successful with billing aspect.
Best Regards
Hammed Adeagbo
Application Performance Engineer
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 17, 2007 11:00 AM
To: [email protected]
Subject: users Digest, Vol 17, Issue 26
Send users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://www.kannel.org/mailman/listinfo/users
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of users digest..."
Today's Topics:
1. Kannel and Billing Related (Shantanu Chauhan)
2. Re: Kannel and Billing Related (Vahid Ghafarpour)
----------------------------------------------------------------------
Message: 1
Date: Wed, 17 Oct 2007 13:39:46 +0530
From: "Shantanu Chauhan" <[EMAIL PROTECTED]>
Subject: Kannel and Billing Related
To: <[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"
Dear All:
We are currently using kannel with multiple SMSC. In case of a SMSC goes
down Kannel automatically sends the message using alternate SMSC.
My problem is that this causes billing descripency since we are not able to
know which SMSC a specific message was actually sent (unless we get delivery
report where we can use SMSC ID parameter to know).
So if their is no delivery report of a message we cannot know which route
was used for sending that messages. Is there an easy way to know it then
looking up DLR table for checking which SMSC kannel used for sending
messages.
regards
Shantanu Chauhan
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://www.kannel.org/pipermail/users/attachments/20071017/0b1ff8d0/attachment-0001.html
------------------------------
Message: 2
Date: Wed, 17 Oct 2007 11:52:34 +0330
From: "Vahid Ghafarpour" <[EMAIL PROTECTED]>
Subject: Re: Kannel and Billing Related
To: "Shantanu Chauhan" <[EMAIL PROTECTED]>
Cc: [email protected]
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset="utf-8"
you can set dlr-mask=24 so you get dlr 8 and 16 which only described if
message sent to SMSC or not
On 10/17/07, Shantanu Chauhan <[EMAIL PROTECTED]> wrote:
Dear All:
We are currently using kannel with multiple SMSC. In case of a SMSC goes
down Kannel automatically sends the message using alternate SMSC.
My problem is that this causes billing descripency since we are not able
to know which SMSC a specific message was actually sent (unless we get
delivery report where we can use SMSC ID parameter to know).
So if their is no delivery report of a message we cannot know which route
was used for sending that messages. Is there an easy way to know it then
looking up DLR table for checking which SMSC kannel used for sending
messages.
regards
Shantanu Chauhan
--
--Vahid Ghafarpour.
http://vahid.ghafarpour.ir/
vahid at ghafarpour dot ir
ghafarpour at gmail dot com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://www.kannel.org/pipermail/users/attachments/20071017/d40ad491/attachment-0001.html
------------------------------
_______________________________________________
users mailing list
[email protected]
http://www.kannel.org/mailman/listinfo/users
End of users Digest, Vol 17, Issue 26
*************************************
