Mike Lynchfield a écrit :
try not using dst.. maybe its a regex on te fieldname that matches for
reserved keywords..
try pre_dest instead
On 2/28/07, Bayrouni [EMAIL PROTECTED] wrote:
Hello,
I created a new field named pre_dst of type varchar(80) exactly like dst
field in cdr table.
Edgar Luna a écrit :
Hi,
On Wed, 2007-02-28 at 23:43 +0100, Bayrouni wrote:
Hello,
In the dialplan I put:
exten = _7.,1,Set(CDR(pre_dst)=${EXTEN:1})
and when I call, all goes fine except that pre_dst has always NULL value
in cdr.
Do you know why?
Is something wrong I did?
As far
Hello,
I created a new field named pre_dst of type varchar(80) exactly like dst
field in cdr table.
In the dialplan I put:
exten = _7.,1,Set(CDR(pre_dst)=${EXTEN:1})
and when I call, all goes fine except that pre_dst has always NULL value
in cdr.
Do you know why?
Is something wrong I did?
Hi,
On Wed, 2007-02-28 at 23:43 +0100, Bayrouni wrote:
Hello,
In the dialplan I put:
exten = _7.,1,Set(CDR(pre_dst)=${EXTEN:1})
and when I call, all goes fine except that pre_dst has always NULL value
in cdr.
Do you know why?
Is something wrong I did?
As far as I know, custom fields
try not using dst.. maybe its a regex on te fieldname that matches for
reserved keywords..
try pre_dest instead
On 2/28/07, Bayrouni [EMAIL PROTECTED] wrote:
Hello,
I created a new field named pre_dst of type varchar(80) exactly like dst
field in cdr table.
In the dialplan I put:
exten =