You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@openmeetings.apache.org by "Maxim Solodovnik (JIRA)" <ji...@apache.org> on 2013/02/08 07:57:15 UTC

[jira] [Closed] (OPENMEETINGS-469) Deleted meeting data remains in SIP db tables

     [ https://issues.apache.org/jira/browse/OPENMEETINGS-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maxim Solodovnik closed OPENMEETINGS-469.
-----------------------------------------

    
> Deleted meeting data remains in SIP db tables
> ---------------------------------------------
>
>                 Key: OPENMEETINGS-469
>                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-469
>             Project: Openmeetings
>          Issue Type: Bug
>          Components: VoIP/SIP
>    Affects Versions: 2.1 Apache Release
>         Environment: CentOS 6.3 using MySQL db backend
>            Reporter: Jeff Clay
>            Assignee: Maxim Solodovnik
>            Priority: Minor
>             Fix For: 2.1 Apache Release
>
>
> When a meeting is created and the SIP settings are enabled, it creates the appropriate rows within the extensions and meetme tables of the database. However, when the meeting is manually deleted, or expires, the settings remain in the tables instead of being deleted.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira