2b930d7c3b
Allows bridging, parking, and dial messages to be globally ignored for all CDRs such that only a single CDR record is generated per channel. This is useful when CDRs should endure for the lifetime of an entire channel and bridging and dial updates in the dialplan should not result in multiple CDR records being created for the call. With the ignore bridging option, bridging changes have no impact on the channel's CDRs. With the ignore dial state option, multiple Dials and their outcomes have no impact on the channel's CDRs. The last disposition on the channel is preserved in the CDR, so the actual disposition of the call remains available. These two options can reduce the amount of "CDR hacks" that have hitherto been necessary to ensure that CDR was not "spoiled" by these messages if that was undesired, such as putting a dummy optimization-disabled local channel between the caller and the actual call and putting the CDR on the channel in the middle to ensure that CDR would persist for the entire call and properly record start, answer, and end times. Enabling these options is desirable when calls correspond to the entire lifetime of channels and the CDR should reflect that. Current default behavior remains unchanged. ASTERISK-30091 #close Change-Id: I393981af42732ec5ac3ff9266444abb453b7c832 |
||
|---|---|---|
| .. | ||
| CHANGES-staging | ||
| UPGRADE-staging | ||
| lang | ||
| .gitignore | ||
| CODING-GUIDELINES | ||
| Doxyfile.in | ||
| IAX2-security.pdf | ||
| IAX2-security.txt | ||
| Makefile | ||
| README.txt | ||
| aelparse.8 | ||
| appdocsxml.dtd | ||
| appdocsxml.xslt | ||
| astdb2bdb.8 | ||
| astdb2sqlite3.8 | ||
| asterisk.8 | ||
| asterisk.sgml | ||
| smsq.8 | ||
README.txt
The vast majority of the Asterisk project documentation has been moved to the
project wiki:
https://wiki.asterisk.org/
Asterisk release tarballs contain an export of the wiki in PDF and plain text
form, which you can find in:
doc/AST.pdf
doc/AST.txt
Asterisk uses the Doxygen documentation software. Run "make progdocs" and open
the resulting documentation index at doc/api/index.html in a webbrowser or copy
the directory to a directory served by a webserver for remote access.