[asterisk-bugs] [JIRA] (ASTERISK-22720) devstate incorrectly cached on trasfer of a DAHDI->SIP call.

[Tzafrir Cohen (JIRA)]

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

Tzafrir Cohen updated ASTERISK-22720:
-------------------------------------

    Description: 
To reproduce:

Setup: A DAHDI extension that can call to a SIP extension and to at least any other exteension (may be anything).

To reproduce:

1. Run 'event dump cache DeviceState' to see DAHDI device is not there.

2. From the DAHDI extension dial to the SIP extension.

3. In the DAHDI extension press flash for an attended transfer.

4. Dial the other extension number and hang up.

5. In the CLI, run 'event dump cache DeviceState'. You'll see the DADHI device listed as 2 (in use).

Expected results: in stage 5, the state of the DAHDI device should not have appeared in the cache, or listed as "unknown".

See also the similar https://issues.asterisk.org/jira/browse/ASTERISK-22718

A workaround patch is attached, to forcefully disable caching of DAHDI devices.

Marked as regression as it has worked OK up until 1.8.19. Broken in 1.8.20.

  was:
To reproduce:

Setup: A DAHDI extension that can call to a SIP extension and to at least any other exteension (may be anything).

To reproduce:

1. Run 'event dump cache DeviceState' to see DAHDI device is not there.

2. From the DAHDI extension dial to the SIP extension.

3. In the DAHDI extension press flash for an attended transfer.

4. Dial the other extension number and hang up.

5. In the CLI, run 'event dump cache DeviceState'. You'll see the DADHI device listed as 2 (in use).

Expected results: in stage 5, the state of the DAHDI device should not have appeared in the cache, or listed as "unknown".

A workaround patch is attached, to forcfully disable caching of DAHDI devices.

Marked as regression as it has worked OK up until 1.8.19. Broken in 1.8.20.

    
> devstate incorrectly cached on trasfer of a DAHDI->SIP call.
> ------------------------------------------------------------
>
>                 Key: ASTERISK-22720
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22720
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_dahdi
>    Affects Versions: 1.8.23.1, 11.5.1
>            Reporter: Tzafrir Cohen
>            Severity: Minor
>         Attachments: dahdi-devstate-cachbility-workaround.patch
>
>
> To reproduce:
> Setup: A DAHDI extension that can call to a SIP extension and to at least any other exteension (may be anything).
> To reproduce:
> 1. Run 'event dump cache DeviceState' to see DAHDI device is not there.
> 2. From the DAHDI extension dial to the SIP extension.
> 3. In the DAHDI extension press flash for an attended transfer.
> 4. Dial the other extension number and hang up.
> 5. In the CLI, run 'event dump cache DeviceState'. You'll see the DADHI device listed as 2 (in use).
> Expected results: in stage 5, the state of the DAHDI device should not have appeared in the cache, or listed as "unknown".
> See also the similar https://issues.asterisk.org/jira/browse/ASTERISK-22718
> A workaround patch is attached, to forcefully disable caching of DAHDI devices.
> Marked as regression as it has worked OK up until 1.8.19. Broken in 1.8.20.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira