Re: [asterisk-users] Set CDR userfield in a realtime dialplan

2008-01-09 Thread Benchev
On Wednesday 09 January 2008 09:54:59 Yves Räber wrote:
 Hello,

 I'm using Asterisk with Realtime extensions and ODBC CDR. And I'm have
 some trouble with the CDR userfield that is not changed when using the
 SET command in the realtime dialplan.
 In my dialplan (extensions.conf, the file) I'm setting the userfield
 like this :

 exten = s,n,Set(CDR(userfield)=X)

 Later, my dialplan switches to the realtime part and this is an extract
 for what is inside :
 ===
 id | context | exten |  priority | app | appdata
 ===
 12 |  script | s |  n| SET | CDR(userfield)=Y
 ===

 I can show that the command is executed :
 -- Executing Set(SIP/siemens1-081ca290, CDR(userfield) = Y)

 But in my CDR, the old value is saved (X in this case).
Into a database the line exten = s,n,Set(CDR(userfield)=X)
should be enterd as:
context | exten |  priority | app | appdata
means in your case:
your_context| s|n|Set(CDR(userfield)|X

Boyko

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

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


Re: [asterisk-users] Set CDR userfield in a realtime dialplan

2008-01-09 Thread Andrea Cristofanini
Hello
I'm running the same with no-problem.

CDR(userfield)=INCOMING

We use also a quite nice patch from Matt Riddell
http://bugs.digium.com/view.php?id=9424
that allow to have extra userfield.

CDR(userfield2)=${CODEC-IN}
CDR(userfield3)=${CODEC-OUT}


and so on...

This is quite good for custom report.
/a

Benchev ha scritto:
 On Wednesday 09 January 2008 09:54:59 Yves Räber wrote:
   
 Hello,

 I'm using Asterisk with Realtime extensions and ODBC CDR. And I'm have
 some trouble with the CDR userfield that is not changed when using the
 SET command in the realtime dialplan.
 In my dialplan (extensions.conf, the file) I'm setting the userfield
 like this :

 exten = s,n,Set(CDR(userfield)=X)

 Later, my dialplan switches to the realtime part and this is an extract
 for what is inside :
 ===
 id | context | exten |  priority | app | appdata
 ===
 12 |  script | s |  n| SET | CDR(userfield)=Y
 ===

 I can show that the command is executed :
 -- Executing Set(SIP/siemens1-081ca290, CDR(userfield) = Y)

 But in my CDR, the old value is saved (X in this case).
 
 Into a database the line exten = s,n,Set(CDR(userfield)=X)
 should be enterd as:
 context | exten |  priority | app | appdata
 means in your case:
 your_context| s|n|Set(CDR(userfield)|X

 Boyko

 ___
 -- Bandwidth and Colocation Provided by http://www.api-digital.com --

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

   


___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

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


Re: [asterisk-users] Set CDR userfield in a realtime dialplan

2008-01-09 Thread Yves Räber
I answered my own question ... it was a stupid syntax mistake.

CDR(userfield) = Y   --- No spaces allowed at all here

Mea culpa.


On Wed, 2008-01-09 at 08:54 +0100, Yves Räber wrote:
 Hello, 
 
 I'm using Asterisk with Realtime extensions and ODBC CDR. And I'm have
 some trouble with the CDR userfield that is not changed when using the
 SET command in the realtime dialplan.
 
 In my dialplan (extensions.conf, the file) I'm setting the userfield
 like this :
 
 exten = s,n,Set(CDR(userfield)=X)
 
 Later, my dialplan switches to the realtime part and this is an extract
 for what is inside :
 ===
 id | context | exten |  priority | app | appdata 
 ===
 12 |  script | s |  n| SET | CDR(userfield)=Y
 ===
 
 I can show that the command is executed :
 -- Executing Set(SIP/siemens1-081ca290, CDR(userfield) = Y)
 
 But in my CDR, the old value is saved (X in this case).
 
 Does anyone have an idea what's going on here ? Of course I'll send my
 complete config details if needed.
 
 Thanks
 
 Yves.
 
 
 
 
 
 
 
 
 
 ___
 -- Bandwidth and Colocation Provided by http://www.api-digital.com --
 
 asterisk-users mailing list
 To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users


___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

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

[asterisk-users] Set CDR userfield in a realtime dialplan

2008-01-08 Thread Yves Räber
Hello, 

I'm using Asterisk with Realtime extensions and ODBC CDR. And I'm have
some trouble with the CDR userfield that is not changed when using the
SET command in the realtime dialplan.

In my dialplan (extensions.conf, the file) I'm setting the userfield
like this :

exten = s,n,Set(CDR(userfield)=X)

Later, my dialplan switches to the realtime part and this is an extract
for what is inside :
===
id | context | exten |  priority | app | appdata 
===
12 |  script | s |  n| SET | CDR(userfield)=Y
===

I can show that the command is executed :
-- Executing Set(SIP/siemens1-081ca290, CDR(userfield) = Y)

But in my CDR, the old value is saved (X in this case).

Does anyone have an idea what's going on here ? Of course I'll send my
complete config details if needed.

Thanks

Yves.









___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

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