| Summary: | ASTERISK-21698: Bridge API Enhancements - handle Attended Transfers in CDRs | ||||
| Reporter: | Matt Jordan (mjordan) | Labels: | Asterisk12 | ||
| Date Opened: | 2013-04-26 07:17:34 | Date Closed: | 2013-07-08 08:23:07 | ||
| Priority: | Major | Regression? | No | ||
| Status: | Closed/Complete | Components: | CDR/General Core/Bridging | ||
| Versions: | Frequency of Occurrence | ||||
| Related Issues: |
| ||||
| Environment: | Attachments: | ||||
| Description: | An attended transfer can be a little complex. This is due to:
* Local channel optimization that occurs during the transfer * The attended transfer can involve nested bridging (a channel is in more than one bridge at a time) * The attended transfer can be into an application Each of the above scenarios requires specific logic to handle in the CDR engine. | ||||
| Comments: | By: Matt Jordan (mjordan) 2013-07-08 08:23:08.013-0500 Since these are all using appropriate BridgeEnter/BridgeLeave events, these should just "work". Documentation needs to be reflected with the actual scenarios and their results and tests updated as well, but those will be taken care of in other tasks. | ||||