[asterisk-bugs] [JIRA] (ASTERISK-23986) Voicemail msg_id is changed when a voicemail is played or moved.

[Michael L. Young (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-23986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=220270#comment-220270 ] 

Michael L. Young commented on ASTERISK-23986:
---------------------------------------------

One thing that comes to mind would be that msgnum could change but msg_id stays the same.  The msg_id only changes when a new record is made in the database.  The new record is created when moving a message to another folder or when listening to a message.  When listening, the record is automatically created in order to put the message in the Old folder.  Otherwise, as long as you are not copying the message around, the msg_id stays the same, even if you delete or add other messages to the same folder.

> Voicemail msg_id is changed when a voicemail is played or moved.
> ----------------------------------------------------------------
>
>                 Key: ASTERISK-23986
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23986
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_voicemail/ODBC
>    Affects Versions: 11.6.0
>         Environment: CentOS 6.5 x86_64
> unixODBC 2.2.14-12
> MySQL Connector/ODBC 5.3.2
> MySQL 5.1.73
>            Reporter: Steven T. Wheeler
>            Severity: Minor
>         Attachments: vm_queries.sql
>
>
> We are getting ready to make the jump from v1.8 to v11.6-cert4. One of the new features (as listed in https://wiki.asterisk.org/wiki/display/AST/Upgrading+to+Asterisk+11) we were most excited for was the new unique msg_id column in the voicemessages table. The hope was that this would allow us to store additional information related to a message.
> However, it appears that the msg_id value changes whenever the message is moved to a different mailbox (i.e. moved from INBOX to Old).  Is this expected behavior or is it a bug?



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