Hello Iain,
please keep in mind that in case you expect traffic peaks or a
sustained high level of service requests, the overhead disk i/o and
processor time from doing grep/sed in every webserver process may
grind your server to a halt. If you really need to parse the logfile,
pipe it through a s
my-number = "12345"
to smsc configuration. it must be change your number to 12345
ah, that's unfortunate!! because i'm going to be using the same
installation for multiple inbound numbers, and because i don't have a
'service based' inbound sms but rather using a catchall (and also cos i
ha
add
my-number = "12345"
to smsc configuration. it must be change your number to 12345
On Mon, Mar 17, 2008 at 5:37 AM, Iain Dooley
<[EMAIL PROTECTED]> wrote:
> hi tulga,
>
>
> > I think it is not destination number. it is my-number in your smsc
> > group. could you send your configuration file
hi tulga,
I think it is not destination number. it is my-number in your smsc
group. could you send your configuration file?
so, file below. whether i use %P or %Q it still produces the send sms port
number. i have gotten around this problem by ading the %I placeholder to
the log file, then d
I think it is not destination number. it is my-number in your smsc
group. could you send your configuration file?
On Sat, Mar 15, 2008 at 11:02 PM, Iain Dooley
<[EMAIL PROTECTED]> wrote:
> has anyone else seen the problem where %P in your get-url of an
> sms-service configuration sends the port n
has anyone else seen the problem where %P in your get-url of an
sms-service configuration sends the port number rather than the
destination number?
cheers
iain
