Issues migrating Elastix 2.4 to FreepBX 13


  • Service Provider

    With the demise of Elastix, Sangoma put out a tool to convert systems to FreePBX.

    Problem is that is does not work with Elastix 2.4 as it requires FreePBX 2.9 or higher.

    I upgraded the unembedded FreePBX on a system and no go.

    Someone else posted recently on the FreepBX forums about this issue, but then never responded to a question. I responded this evening. hopefully they will give me an intelligent answer to check things.
    https://community.freepbx.org/t/conversion-tool-error/38846/3

    [[email protected] ~]# curl -s https://convert.freepbx.org | bash
    Checking that 'curl' exists ... OK!
    Validating sha256 integrity ... OK!
    Trying to download converter to /tmp/tmp.XghJhY6651 ... Complete!
    Validating download ... OK!
    Starting FreePBX Converter version release/20151217r1
    Testing connectivity to Conversion server...Success!
    
    FreePBX Conversion Wizard
    -------------------------
    
    The FreePBX Conversion Wizard needs to be run on two machines, the NEW
    machine, which must be an ACTIVATED FreePBX Distro machine, and then it must
    be run on the DONOR machine.
    The DONOR machine is the machine that is currently processing calls, and is
    the machine that will be migrated to the NEW machine. No changes will be made
    to the DONOR machine, and this script will not stop or restart any services
    that may cause an outage.
    If this is the NEW machine, just push 'Enter' to prepare this machine
    
    Enter ID (blank if this is NEW): c...............6
    Testing FreePBX functionality ... Failed. Received '/etc/freepbx.conf doesn't exist.
    This must be run on a FreePBX machine' instead of 'OK'
    Cleaning up...Done!
    [[email protected] ~]# ls /etc/free*
    ls: /etc/free*: No such file or directory
    [[email protected] ~]# 
    

  • Service Provider

    And I solved it.

    I noticed a warning in the FreePBX dashboard about permissions.
    0_1486443445347_upload-ddff86b3-c75d-423b-80ab-5615e37b225b

    So I ran it, and look at that... It moved freepbx.conf.

    [[email protected] ~]# amportal chown
    
    
    moving /etc/asterisk/freepbx.conf to /etc/freepbx.conf
    SETTING FILE PERMISSIONS
    Permissions OK
    

  • Service Provider

    First you run this script on the new machine and get the ID.

    [[email protected] ~]# curl -s https://convert.freepbx.org | bash
    Checking that 'curl' exists ... OK!
    Validating sha256 integrity ... OK!
    Trying to download converter to /tmp/tmp.HTxVQTafPB ... Complete!
    Validating download ... OK!
    Starting FreePBX Converter version release/20151217r1
    Testing connectivity to Conversion server...Success!
    
    FreePBX Conversion Wizard
    -------------------------
    
    The FreePBX Conversion Wizard needs to be run on two machines, the NEW
    machine, which must be an ACTIVATED FreePBX Distro machine, and then it must
    be run on the DONOR machine.
    The DONOR machine is the machine that is currently processing calls, and is
    the machine that will be migrated to the NEW machine. No changes will be made
    to the DONOR machine, and this script will not stop or restart any services
    that may cause an outage.
    If this is the NEW machine, just push 'Enter' to prepare this machine
    
    Enter ID (blank if this is NEW): 
    Testing FreePBX functionality ... Success! (Version 13.0.190.12)
    Getting Deployment ... 19983072
    Getting all Module versions (for conversion) ... OK
    Reserving a conversion slot ... Reserved!
    
    The Conversion process is now ready. Please run the script on the
    DONOR node now, and when asked for a slot identifier, please enter
    the following ID:
    
    	cbdce81b-2ec1-4ed4-bddc-ad557da1f546
    
    [|] Waiting on DONOR to send data
    

  • Service Provider

    Then you run the same thing on the machine you are migrating from.

    You will fill in the ID from the first machine.

    [[email protected] ~]# curl -s https://convert.freepbx.org | bash
    Checking that 'curl' exists ... OK!
    Validating sha256 integrity ... OK!
    Trying to download converter to /tmp/tmp.PftRnI5651 ... Complete!
    Validating download ... OK!
    Starting FreePBX Converter version release/20151217r1
    Testing connectivity to Conversion server...Success!
    
    FreePBX Conversion Wizard
    -------------------------
    
    The FreePBX Conversion Wizard needs to be run on two machines, the NEW
    machine, which must be an ACTIVATED FreePBX Distro machine, and then it must
    be run on the DONOR machine.
    The DONOR machine is the machine that is currently processing calls, and is
    the machine that will be migrated to the NEW machine. No changes will be made
    to the DONOR machine, and this script will not stop or restart any services
    that may cause an outage.
    If this is the NEW machine, just push 'Enter' to prepare this machine
    
    Enter ID (blank if this is NEW): cbdce81b-2ec1-4ed4-bddc-ad557da1f546
    Testing FreePBX functionality ... Success!
    Checking Slot ID ... OK!
    Getting modules to convert ... Complete! 109 modules
    Dumping astdb ... Complete!
    Do you want to copy /tftpboot to the new machine [Ny]? y
    Creating encrypted backup for new machine. This may take some time.
    Backing up the following:
    47M	/var/spool/asterisk
    4.0K	/var/lib/asterisk/moh
    7.9M	/var/lib/asterisk/sounds/custom
    33M	/tftpboot
    Complete!
    Sending backup details to new machine ... Complete!
    	Module announcement (Skipped 1, Completed 0) ... announcement
    	Module callback (Skipped 13, Completed 1) ... callback
    	Module callrecording (Skipped 16, Completed 2) ... callrecording callrecording_module
    	Module cidlookup (Skipped 21, Completed 3) ... cidlookup cidlookup_incoming
    	Module conferences (Skipped 21, Completed 4) ... meetme
    	Module core (Skipped 24, Completed 5) ... sip dahdi featurecodes incoming outbound_routes freepbx_settings trunks users devices dahdichandids globals language_incoming languages outbound_route_patterns outbound_route_sequence outbound_route_trunks outroutemsg trunk_dialpatterns trunks
    	Module customappsreg (Skipped 25, Completed 6) ... custom_destinations custom_extensions
    	Module daynight (Skipped 28, Completed 7) ... daynight
    	Module disa (Skipped 32, Completed 8) ... disa
    	Module fax (Skipped 35, Completed 9) ... fax_details fax_incoming fax_users
    	Module findmefollow (Skipped 37, Completed 10) ... findmefollow
    	Module iaxsettings (Skipped 42, Completed 11) ... iaxsettings
    	Module ivr (Skipped 44, Completed 12) ... ivr_details ivr_entries
    	Module miscapps (Skipped 47, Completed 13) ... miscapps
    	Module miscdests (Skipped 47, Completed 14) ... miscdests
    	Module paging (Skipped 49, Completed 15) ... paging_groups paging_config
    	Module parking (Skipped 50, Completed 16) ... parkplus
    	Module pinsets (Skipped 54, Completed 17) ... pinsets pinset_usage
    	Module queueprio (Skipped 57, Completed 18) ... queueprio
    	Module queues (Skipped 57, Completed 19) ... queues_details queues_config
    	Module recordings (Skipped 58, Completed 20) ... recordings
    	Module ringgroups (Skipped 61, Completed 21) ... ringgroups
    	Module sipsettings (Skipped 63, Completed 22) ... sipsettings
    	Module timeconditions (Skipped 70, Completed 23) ... timeconditions timegroups_groups timegroups_details
    	Module vmblast (Skipped 75, Completed 24) ... vmblast vmblast_groups
    	Module voicemail (Skipped 76, Completed 25) ... voicemail_admin
    Attempting to discover users email addresses ... (37 users, 3 with email) Complete!
    Export complete!
    This backup is currently being processed by the conversion servers, and will
    be automatically downloaded and installed on the NEW machine when completed.
    
    Please Note! All SIP and IAX trunks on the NEW machine will be set to DISABLED,
    and you will need to manually re-enable them. This is to avoid accidental
    outages if the NEW machine registers to a peer unexpectedly.
    Cleaning up...Done!
    

  • Service Provider

    Then you will see the new system getting the data and creating users

    [[email protected] ~]# curl -s https://convert.freepbx.org | bash
    Checking that 'curl' exists ... OK!
    Validating sha256 integrity ... OK!
    Trying to download converter to /tmp/tmp.HTxVQTafPB ... Complete!
    Validating download ... OK!
    Starting FreePBX Converter version release/20151217r1
    Testing connectivity to Conversion server...Success!
    
    FreePBX Conversion Wizard
    -------------------------
    
    The FreePBX Conversion Wizard needs to be run on two machines, the NEW
    machine, which must be an ACTIVATED FreePBX Distro machine, and then it must
    be run on the DONOR machine.
    The DONOR machine is the machine that is currently processing calls, and is
    the machine that will be migrated to the NEW machine. No changes will be made
    to the DONOR machine, and this script will not stop or restart any services
    that may cause an outage.
    If this is the NEW machine, just push 'Enter' to prepare this machine
    
    Enter ID (blank if this is NEW): 
    Testing FreePBX functionality ... Success! (Version 13.0.190.12)
    Getting Deployment ... 19983072
    Getting all Module versions (for conversion) ... OK
    Reserving a conversion slot ... Reserved!
    
    The Conversion process is now ready. Please run the script on the
    DONOR node now, and when asked for a slot identifier, please enter
    the following ID:
    
    	cbdce81b-2ec1-4ed4-bddc-ad557da1f546
    
    [|] Donor now sending module 'voicemail', table 'voicemail_admin' ...
    
    Trying to retrieve the backup from the DONOR machine ...
    [-] Download complete (61163552 bytes)
    	Validating ... Complete!
    Decrypting and extracting ... Complete!
    Queueing conversion ... OK
    Embedded response found, creating raw import file.
    Processing data ... Complete!
    	27 modules to import
    	37 users to import
    Clearing astdb ..Complete!
    [] Importing ASTDB ... Complete!
    [] All modules imported.
    Running module 'customappsreg' command 'fwconsole ma install customappsreg' ... Complete!
    Adding user 6001 (Bundy Test 1) ... User created (Note: No email address!) with password Parrot6crew3sure
    Adding user 6002 (Bundy Test 2) ... User created (Note: No email address!) with password tear*Nearer5Coffee
    Cleaning up...Done!
    [[email protected] ~]# 
    
    

  • Service Provider

    Now log into your new FreePBX system and it will show the Apply Config warning.

    Do so.

    0_1486444059378_upload-fea00064-3888-40ea-af94-ee5a8ca2979c

    At this point you can go through the new system one piece at a time and make sure you are good.
    Change a couple extensions to point to your new PBX and make sure they register and can call each other.
    Once you are sure that the basics are working, disable the trunks on the old system, enable on the new system, and verify outside connectivity works.
    Finally, you can change the rest of the extensions.



Looks like your connection to MangoLassi was lost, please wait while we try to reconnect.