contrib/ast-db-manage: Correct down_revision path for user_eq_phone

When the user_eq_phone patch was backported to 13, it referenced the downward
revision that the PJSIP optimistic encryption option also references. This
creates a multi-path upgrade Exception when generating the SQL files.

This patch corrects this in the 13 branch. Note that trunk, which already
contained both of these features, is unaffected by this problem.

git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/13@430252 65c4cc65-6c06-0410-ace0-fbb531ad65f3

diff --git a/contrib/ast-db-manage/config/versions/371a3bf4143e_add_user_eq_phone_option_to_pjsip.py b/contrib/ast-db-manage/config/versions/371a3bf4143e_add_user_eq_phone_option_to_pjsip.py
index 145d6bea6520d9ffefad571df103c57a3b041a4b..ea2b291de36a76cbf2244850e121cf3a93c189f9 100644 (file)
--- a/contrib/ast-db-manage/config/versions/371a3bf4143e_add_user_eq_phone_option_to_pjsip.py
+++ b/contrib/ast-db-manage/config/versions/371a3bf4143e_add_user_eq_phone_option_to_pjsip.py
@@ -8,7 +8,7 @@ Create Date: 2014-10-13 13:46:24.474675
 
 # revision identifiers, used by Alembic.
 revision = '371a3bf4143e'
-down_revision = '10aedae86a32'
+down_revision = 'eb88a14f2a'
 
 from alembic import op
 import sqlalchemy as sa