Enver ALTIN wrote:
It looks like Fred passes additional pairs of key:values without the
need of patching Kannel... that would be great! :)
No, he was adding some comments about another solution Stipe proposed,
so that was a totally different subject.
I just realized that binfo is a
Hey,
On Mon, Nov 14, 2005 at 11:26:28AM -0200, Juan Nin wrote:
Enver ALTIN wrote:
It looks like Fred passes additional pairs of key:values without the
need of patching Kannel... that would be great! :)
No, he was adding some comments about another solution Stipe proposed,
so that was a
Enver ALTIN wrote:
Let me sum it up,
My patch adds another CGI parameter to sendsms called submission_mode,
and SMPP will directly set esm_class to that value.
Fred's solution was to prevent adding SMSC-specific sendsms parameters
by passing a list of name=value pairs via binfo and use that.
Hi!
I need to use esm_class 0 with a Telco.
I could change Kannel's code to use it as default mode (but would mean
running 2 different Kannel instances) or maybe use Enver Altin's
smpp-esmclass-submissionmode patch.
On a thread on the devel list about Enver's patch, I've seen this post:
On Mon, Nov 14, 2005 at 09:53:43AM -0200, Juan Nin wrote:
Hi!
Hey,
I need to use esm_class 0 with a Telco.
I could change Kannel's code to use it as default mode (but would mean
running 2 different Kannel instances) or maybe use Enver Altin's
smpp-esmclass-submissionmode patch.
Enver ALTIN wrote:
On Mon, Nov 14, 2005 at 09:53:43AM -0200, Juan Nin wrote:
Hi!
Hey,
I need to use esm_class 0 with a Telco.
I could change Kannel's code to use it as default mode (but would mean
running 2 different Kannel instances) or maybe use Enver Altin's
