[asterisk-bugs] [JIRA] (ASTERISK-24308) Call IDs in Asterisk 12: Planning

[Jonathan Rose (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-24308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Rose updated ASTERISK-24308:
-------------------------------------

    Status: Open  (was: Triage)

> Call IDs in Asterisk 12: Planning
> ---------------------------------
>
>                 Key: ASTERISK-24308
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24308
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Bridging, Core/Channels, Core/Logging
>    Affects Versions: SVN, 12.6.0, 13.0.0-beta1
>            Reporter: Jonathan Rose
>
> Call IDs have decayed somewhat since their initial release in Asterisk 11, largely on account of the new bridging architecture. This task is to plot out expected behavior for Call IDs in Asterisk 12+, to define the concept of a call for this purpose so that we can more readily identify if/when this feature goes off the rails in the future, and to plan a series of tests for ideal call ID behavior.
> Note: I filed this as a regression bug on account of the following use case:
> 1. SIP/A calls SIP/B -- they each start with C-00000000
> 2. SIP/A starts attended transfer of SIP/B to SIP/C -- SIP/A (separate channel) is in a call with SIP/C with C-00000001
> 3. SIP/A completes transfer, SIP/B and SIP/C are now in a call but each have the same call IDs from before (SIP/B is C-00000000 and SIP/C is C-00000001)
> In Asterisk 11, the call ID for SIP/B and SIP/C would be unified as C-00000001. Taking C-00000001 may or may not be the ideal behavior, but the fact that they should have the same call ID once they are bridged together is more or less certain.



--
This message was sent by Atlassian JIRA
(v6.2#6252)