Alejandro Guerrieri wrote:
Stipe, Rene,
We work with aggregators from around the world, and we are using many
flavors of the HTTP smsc modules (we even made a couple of modules to
support specific cases).
The scenario is exactly as you described it: The account field is used
to encode the
Please unsubcribe me from this mailing list.
From: Stipe Tolj [EMAIL PROTECTED]
To: Alejandro Guerrieri [EMAIL PROTECTED]
CC: devel@kannel.org devel@kannel.org
Subject: Re: [PATCH] Service routing based on the account field
Date: Fri, 29 Sep 2006 15:27:13 +0200
Alejandro Guerrieri wrote
Alejandro Guerrieri wrote:
I've noticed there were no way for Kannel to do service routing based
on the account field. This is specially handy when you use an HTTP
module to receive messages and the smsc gets encoded on the account
field, so you get a single smsc with different accounts
Guerrieri
Cc: devel@kannel.org
Subject: Re: [PATCH] Service routing based on the account field
Alejandro Guerrieri wrote:
I've noticed there were no way for Kannel to do service routing based
on the account field. This is specially handy when you use an HTTP
module to receive messages and the smsc
Stipe, Rene,
We work with aggregators from around the world, and we are using many
flavors of the HTTP smsc modules (we even made a couple of modules to
support specific cases).
The scenario is exactly as you described it: The account field is used
to encode the real operator's smsc id, since
I've noticed there were no way for Kannel to do service routing based
on the account field. This is specially handy when you use an HTTP
module to receive messages and the smsc gets encoded on the account
field, so you get a single smsc with different accounts depending on
the carrier.
I'm
