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.
>>
>> 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?
>>
>>
>> I know that original fields in cdr are only readable, but in this cas
>> pre_dst is one I created myself !!!
>>
>> Thank you.
>>
>>

I tried yet pre_dst un cdr table.
I even change it to foo or coco or whatever, but nothing is written in
this custom field except NULL.


+---------------------+------------------------+------------+------------------+
| clid                | dstchannel             | coco       | dst
       |
+---------------------+------------------------+------------+------------------+
| 2007-02-28 13:31:43 | SIP/xxxxxxxxx-081b1fd8 | NULL       xxxxxxxxx     |

thanks.

_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to