Orgasmatron 5.1/5.2 Fixes

[wardmundy]

A couple of bugs have reared their ugly heads. Here is a thread with the fixes.

[wardmundy]

For those that installed Orgasmatron 5.1 before mid-afternoon on Friday, 2/27/2010, please execute the following commands after logging into your server as root:

# patches for reminders and ARI security
echo "#Password protect ARI interface" > /etc/pbx/httpdconf/ari.conf
echo "<Directory /var/www/html/recordings>" >> /etc/pbx/httpdconf/ari.conf
echo "AuthType Basic" >> /etc/pbx/httpdconf/ari.conf
echo 'AuthName "Restricted Area"' >> /etc/pbx/httpdconf/ari.conf
echo "AuthUserFile /usr/local/apache/passwd/wwwpasswd" >> /etc/pbx/httpdconf/ari.conf
echo "Require valid-user" >> /etc/pbx/httpdconf/ari.conf
echo "</Directory>" >> /etc/pbx/httpdconf/ari.conf

echo "#Password protect web reminders" > /etc/pbx/httpdconf/reminders.conf
echo "<Directory /var/www/html/reminders>" >> /etc/pbx/httpdconf/reminders.conf
echo "AuthType Basic" >> /etc/pbx/httpdconf/reminders.conf
echo 'AuthName "Restricted Area"' >> /etc/pbx/httpdconf/reminders.conf
echo "AuthUserFile /usr/local/apache/passwd/wwwpasswd" >> /etc/pbx/httpdconf/reminders.conf
echo "Require valid-user" >> /etc/pbx/httpdconf/reminders.conf
echo "</Directory>" >> /etc/pbx/httpdconf/reminders.conf

apachectl restart

Syntax for adding additional user with ARI webaccess only:

htpasswd /usr/local/apache/passwd/wwwpasswd ari password

[wardmundy]

For those that installed Orgasmatron 5.1 before 2:30 p.m. EST on Saturday, 2/28/2010, you also will need to apply this patch or all sorts of apps won't work since the extensions_custom.conf dialplan was broken by an earlier "improvement." Log into your server as root and execute the following commands:

sed -i 's|412,9|s,9|' /etc/asterisk/extensions_custom.conf
sed -i '1,/s,9/s/s,9/412,9/' /etc/asterisk/extensions_custom.conf
sed -i '1,/s,9/s/s,9/412,9/' /etc/asterisk/extensions_custom.conf
asterisk -rx "dialplan reload"

And, yes, we know the second command is being executed twice. That is required!

[wardmundy]

If you receive an error that CID Superfecta cannot access the AsteriDex database, simply log into your server as root and run the following commands:

mysql -uroot -ppassw0rd asterisk <<EOF
use asterisk;
UPDATE superfectaconfig SET value='passw0rd' WHERE source='Default_AsteriDex' AND field='DB_Password' LIMIT 1 ;
EOF

You also may need to change the maint password in CID Superfecta to match the password you set with passwd-master!

[wardmundy]

Be aware that with some IPkall numbers, an incorrect CallerID Number is passed with incoming calls from Google Voice. Rather than displaying your Google Voice number, IPkall sends 2062040232. This will cause the phone you are using to place outbound calls to ring as if you're receiving a second call, i.e. Call Waiting-like behavior. The fix is two steps.

#1 Log into your server as root, edit /etc/asterisk/extensions_custom.conf, and scroll to the bottom of the file. In the [custom-park] context, the entry for s,2 sets GVNUM to your Google Voice number. Carefully remove your Google Voice number and replace it with 2062040232. Save your changes: Ctrl-X, Y, then Enter. Then asterisk -rx "dialplan reload"

#2 With a web browser, log into FreePBX. You'll need to make one additional change. Edit the gv-ringback Inbound Route and remove your Google Voice number from the Caller ID Number field. Save your change and reload.

[wardmundy]

Starting to look like Google Voice may actually be spoofing the CallerID on calls to IPkall numbers as a cost-saving measure. Correct CallerID is passed if you call your IPkall number from a non-GV number. Because IPkall is an ILEC, it would receive less of a revenue share on calls from within its own network. In this case the spoofed CallerID appears to be on the IPkall network. Stay tuned!

[wardmundy]

There is a very serious security vulnerability that needs to be patched by loading the very latest version of FreePBX Framework as soon as it becomes available for your version of FreePBX. Just displaying a call report in the FreePBX browser could compromise your system.

The 2.5 and 2.6 patches (which are what you need with Orgasmatron builds) already have been released. Load this patch IMMEDIATELY by opening FreePBX with a browser and...

Setup, Module Admin, Check for Updates on Line, Upgrade All

2.5.2.3: #4223 Security Vulnerability
2.6.0.2: #3805, #3707, #4188, #4223 Security Vulnerability

[wardmundy]

Orgasmatron Reminders: A bug was discovered that caused scheduling of some reminders to fail because of 2 missing directories. The fix is here: http://nerd.bz/dwO0fd

Our apologies.