-
-
-
-
- THIS IS NO LONGER TRUE REWRITE *****
-
-
-
The CEL function parallels the CDR function, for fetching values from the channel or event. It has some notable notable differences, though! For instance, CEL data is not stored on the channel. Well, not much of it, anyway! You can use the CEL function to set the amaflags, accountcode, and userfield, which are stored on the channel.
Channel variables are not available for reading from the CEL function, nor can any variable name other than what's in the list, be set. CDRs have a structure attached to the channel, where the CDR function could access the values stored there, or set the values there. CDRs could store their own variable lists, but CEL has no such storage. There is no reason to store any event information, as they are immediately output to the various backends at the time they are generated.
See the description for the CEL function from the CLI: core show function CEL
Here is a list of all the available channel field names:
- cidname
- userfield
- cidnum
- amaflags
- cidani
- cidrdnis
- ciddnid
- appdata
- exten
- accountcode
- context
- uniqueid
- channame
- appname
- peer
- eventtime
- eventtype