[asterisk-bugs] [JIRA] (ASTERISK-27489) Realtime/ODBC voicemail concurrency regression

[Asterisk Team (JIRA)]

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

Asterisk Team updated ASTERISK-27489:
-------------------------------------

    Assignee: Sean Bright  (was: David Moore)
      Status: Triage  (was: Waiting for Feedback)

> Realtime/ODBC voicemail concurrency regression
> ----------------------------------------------
>
>                 Key: ASTERISK-27489
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27489
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_voicemail/ODBC
>    Affects Versions: 13.18.4
>         Environment: Debian, odbc/realtime, mysql
>            Reporter: David Moore
>            Assignee: Sean Bright
>
> I upgraded a test box from 13.4 to 13.18.4 while troubleshooting an unrelated issue. I then ran a self-developed test suite in pursuit of solving that unrelated issue. That test suite generates calls to the asterisk box and leaves voicemails at a configurable rate/frequency.
> With 13.4 I was able to leave upwards of 50 voicemails simultaneously and they would be written to the database. With 13.18.4 this no longer seems possible. Asterisk verbose log shows that all messages have the same filename (e.g. msg0010.txt, repeated 50 times, in the log) and the realtime component is not creating new rows for each voicemail. Rather, as each voicemail concludes, the realtime backend is overwriting a row with the message data. I can observe this by querying the database quickly in succession as the calls are wrapping up. The number of rows does not increase, but the most recently added row is continually updated with new data.
> We need a voicemail system that can handle more than one simultaneous message per user, the current behavior is unpredictable and will result in lost voicemails
> I will assist however possible to address this issue, please let me know if there's anything I can do to aid resolution- is there some odbc debugging we can do?



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