Child pages
  • iSymphony 3.2.1 Upgrade Notes

This documentation relates to iSymphony 3.5. You can view older documentation on the Older Documentation page

Skip to end of metadata
Go to start of metadata

This document contains information that is important to note when upgrading to iSymphony 3.2.1. Please be sure to completely read the information before upgrading. 

If you are upgrading from a 3.0.x system, make sure to read the iSymphony 3.1.4 Upgrade Notes as well.

Notes Concerning New Included Dialplan Contexts

In order to support auto answer on PJSIP endpoints when toggling hold state of a call, or barging in on a call, iSymphony 3.2 has introduced two new custom contexts that must be included in the dialplan. The procedure to add these contexts to the dialplan will differ depending on if you are utilizing a FreePBX based system or not.

Adding Contexts To A Vanilla Asterisk (Non-FreePBX) System

If you have already added the /opt/isymphony3/server/dialplan.conf included in your dial plan, simply run the following command, from the server command line, after you have upgrade iSymphony.

asterisk -rx "dialplan reload"

Adding Contexts To A FreePBX Based System

If you are using an iSymphony V3 FreePBX module, with a version of 4.1.8 or higher, you can skip these steps. You can check your module version via Admin->Module Admin in FreePBX.

The current iSymphony FreePBX module will not add the needed contexts to the FreePBX dialplan. To include these contexts, open the following file on the system:

/ect/asterisk/extensions_custom.conf

Next, add the following to the end of the file:

[c-x-3-pjsip-auto-answer-headers]
exten => addheader,1,Set(PJSIP_HEADER(add,Alert-Info)=<http://www.notused.com>\;info=alert-autoanswer\;delay=0)
exten => addheader,n,Set(PJSIP_HEADER(add,Alert-Info)=Ring Answer)
exten => addheader,n,Set(PJSIP_HEADER(add,Alert-Info)=ring-answer)
exten => addheader,n,Set(PJSIP_HEADER(add,Call-Info)=\;answer-after=0)
;--== end of [c-x-3-pjsip-auto-answer-headers] ==--;

[c-x-3-pjsip-auto-answer-redirect]
exten => _X!,1,ExecIf($["${D_OPTIONS}"==""]?Set(D_OPTIONS=TtrI))
exten => _X!,n,Dial(${CX_AUTOANSWER_REDIRECT_PEER},,${D_OPTIONS}b(c-x-3-pjsip-auto-answer-headers^addheader^1))
;--== end of [c-x-3-pjsip-auto-answer-redirect] ==--;

Save the file and run the following command:

asterisk -rx "dialplan reload"

Notes For Users Who Have Made Custom Modifications To The jvm.args File (Including Remote Voicemail/Recording Agent Installations)

This issue only effects RPM upgrades. Upgrades performed via the Administration Interface or via the tarball are not effected.

 

This version of iSymphony contains a modification to the jvm.args file. If you have made modifications to the jvm.args file in the installation (i.e. to set the broker path for a remote voicemail/recording), and you are upgrading with the RPM, you may see a message like the following when running the RPM upgrade:

iSymphonyServerV3 warning: /opt/isymphony3/server/jvm.args saved as /opt/isymphony3/server/jvm.args.rpmsave

This means that your original jvm.args file has been overwritten with the new default version, and your original file has been saved as jvm.args.rpmsave. To retain your custom modifications, simply re-add the modifications in the new jvm.args file, using the jvm.args.rpmsave file as reference. Once the jvm.args file is configured to your liking, restart the iSymphony server for the changes to take effect.

Upgrade Steps

Follow the standard upgrade instructions found in the Upgrading iSymphony document for all upgrades. 

 

  • No labels