On 10/20/05, Stipe Tolj <[EMAIL PROTECTED]> wrote:
Hi Stipe:
I am just working off of the documents from the clickatell web site.
The api_id varies as you register with clickatell to use http or smtp or smpp.
It is not a constant value across all users.
I agree. The value api_id, it seems, varies across users and the type of protocol being used to communicate with the clickatell servers. So on the one hand it is a user specific value. However I still need to read in the value for my code in
smsc_http.c where I use cfg_get_integer. All this stuff works fine and I can
actually talk to the clickatell web server. So for example where does xidris
or brunet specific configuration information go?
Thank you for your help,
regards
west
can you please forward the specification/protocol api?
Hi Stipe:
I am just working off of the documents from the clickatell web site.
Is the api_id a constant value for a dedicated smsc-id within Kannel's
bearerbox? If yes, please consider using 'system-type' config directive within
'smsc' group.
The api_id varies as you register with clickatell to use http or smtp or smpp.
It is not a constant value across all users.
Adding SMSC specific config directives to the smsc group is _not_ the way we
favorize abtraction. Please try to use config directives that _SEMANTICALLY_
reflect the issue api_id stands for.
I agree. The value api_id, it seems, varies across users and the type of protocol being used to communicate with the clickatell servers. So on the one hand it is a user specific value. However I still need to read in the value for my code in
smsc_http.c where I use cfg_get_integer. All this stuff works fine and I can
actually talk to the clickatell web server. So for example where does xidris
or brunet specific configuration information go?
Thank you for your help,
regards
west
