<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Jazinga</title>
	<atom:link href="http://jazinga.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://jazinga.com</link>
	<description>Communications Simplified</description>
	<lastBuildDate>Tue, 07 May 2013 18:31:50 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>Jazinga Cloud Updates for May 7, 2013</title>
		<link>http://jazinga.com/jazinga-cloud-updates-for-may-7-2013/</link>
		<comments>http://jazinga.com/jazinga-cloud-updates-for-may-7-2013/#comments</comments>
		<pubDate>Tue, 07 May 2013 17:59:26 +0000</pubDate>
		<dc:creator>alex</dc:creator>
				<category><![CDATA[Changelog]]></category>

		<guid isPermaLink="false">http://jazinga.com/?p=449</guid>
		<description><![CDATA[On May 7, 2013, Jazinga Cloud services will be updated. The following changes are included in this release: People: Combined busy and unavailable greetings into a single message. Added a feature to inform a person when they have not recorded one or more voicemail greetings. Added a feature to allow an admin to remind a [...]]]></description>
				<content:encoded><![CDATA[<p>On May 7, 2013, Jazinga Cloud services will be updated. The following changes are included in this release:</p>
<ul>
<li><strong>People:</strong>
<ul>
<li>Combined busy and unavailable greetings into a single message.</li>
<li>Added a feature to inform a person when they have not recorded one or more voicemail greetings.</li>
<li>Added a feature to allow an admin to remind a user to complete their recordings via email.</li>
<li>Added a feature to allow a person to listen to their recorded greetings from within a web browser.</li>
</ul>
</li>
<li><strong>Phones:</strong>
<ul>
<li>Fixed a bug that caused an error when certain automatically generated softphone devices were deleted.</li>
<li>Softphones now have a status of &#8220;MOBILE&#8221; instead of &#8220;UNKNOWN&#8221;, as mobile device status is not tracked.</li>
<li><em>Remote Phones:</em>
<ul>
<li>Added a check to prevent the <em>Remote Phones</em> test from being run if the appliance is offline.</li>
</ul>
</li>
</ul>
</li>
<li><strong>Phone Services:</strong>
<ul>
<li>Added feature to strip out dashes in the <i>DID </i>or <em>Phone Number</em> fields, to prevent an admin from having to do this manually.</li>
<li>Made error messages for the phone service <em>Test</em> feature look nicer.</li>
</ul>
</li>
<li><strong>Apps:</strong>
<ul>
<li><em>Auto Attendant:</em>
<ul>
<li><strong><span style="color: #ff0000;">New auto attendant upload feature added.</span></strong> Pre-recorded WAV files may now be uploaded for auto attendants, instead of having to record by phone. Recording by phone is still possible.</li>
</ul>
</li>
<li><em>Receptionist:</em>
<ul>
<li><strong><span style="color: #ff0000;">New app added.</span></strong> The <em>Receptionist</em> app allows an admin to direct calls to a particular person. If that person does not answer the call, the app allows the call to be directed to a secondary person, team, or app. Customers may wish to use this if they would normally like a person to handle incoming calls, but would like an auto attendant to answer the call if that person is unable to answer for any reason.</li>
</ul>
</li>
</ul>
</li>
<li><strong>Publish:</strong>
<ul>
<li>Fixed a bug that caused the <em>View Full History</em> link on the <em>Discard</em> page to stop working.</li>
</ul>
</li>
<li><strong>Mobile Applications and Softphones:</strong>
<ul>
<li>Added framework to allow the company directory to be provided to mobile apps in future software versions.</li>
<li><em>iOS:</em>
<ul>
<li>Removed <em>Busy</em> voicemail greeting recording button (as busy and unavailable greetings have now been combined into a single message).</li>
<li>Fixed bug that caused the iOS app to crash in certain circumstances when SIP registrations failed.</li>
</ul>
</li>
<li><em>Mac OS X:</em>
<ul>
<li>Removed <em>Busy</em> voicemail greeting recording button (as busy and unavailable greetings have now been combined into a single message).</li>
<li>Fixed a bug where the softphone attempted to reach the Jazinga appliance over the internet instead of via the local network in cases where there is a gateway between the Mac and the appliance.</li>
</ul>
</li>
</ul>
</li>
<li><strong>Appliance Software:</strong>
<ul>
<li>Fixed a bug that would play a message indicating phone services were not available if phone services were offline and someone attempted an internal (extension to extension) call.</li>
<li>Fixed a bug that would cause the appliance to keep playing greeting recording messages forever if a network issue caused the SIP packet signalling the end of the call to be missed.</li>
<li><strong><span style="color: #ff0000;">New feature added.</span></strong> When a callers reaches voicemail, they may dial 0 to exit voicemail and return to the location from which they entered the system. For example. a caller that enters the system via an auto attendant, dials an extension, and then reaches voicemail may push 0 to return to the auto attendant.</li>
</ul>
</li>
<li><strong>Admin and Reseller Portal:</strong>
<ul>
<li>Fixed a bug that allowed a reseller to be assigned as their own parent.</li>
</ul>
</li>
<li><strong>General:</strong>
<ul>
<li>Various fixes to allow the Jazinga Cloud website to display correctly in multiple browsers.</li>
<li>Removed iOS-style on/off toggles, replaced them with standard checkboxes.</li>
<li>Corrected a few interface issues that caused certain features to be hidden or unusable.</li>
<li>Added a feature to reset UDP and TCP ports to default values if the UPnP feature is disabled for an appliance.</li>
</ul>
</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://jazinga.com/jazinga-cloud-updates-for-may-7-2013/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Jazinga Cloud Updates for April 11, 2013</title>
		<link>http://jazinga.com/jazinga-cloud-updates-for-april-11-2013/</link>
		<comments>http://jazinga.com/jazinga-cloud-updates-for-april-11-2013/#comments</comments>
		<pubDate>Thu, 11 Apr 2013 13:20:05 +0000</pubDate>
		<dc:creator>alex</dc:creator>
				<category><![CDATA[Changelog]]></category>

		<guid isPermaLink="false">http://jazinga.com/?p=441</guid>
		<description><![CDATA[On April 11, 2013, Jazinga Cloud services will be updated. The following changes are included in this release: Overview: Alerts: Added suggested troubleshooting steps for all alerts that could be generated. Call History: Added time zone to all call detail records People: Added validation to Ring Duration field to prevent a person from setting a ring [...]]]></description>
				<content:encoded><![CDATA[<p>On April 11, 2013, Jazinga Cloud services will be updated. The following changes are included in this release:</p>
<ul>
<li><strong>Overview</strong>:
<ul>
<li><em>Alerts:</em>
<ul>
<li>Added suggested troubleshooting steps for all alerts that could be generated.</li>
</ul>
</li>
<li><em>Call History:</em>
<ul>
<li>Added time zone to all call detail records</li>
</ul>
</li>
</ul>
</li>
<li><strong>People:</strong>
<ul>
<li>Added validation to <em>Ring Duration</em> field to prevent a person from setting a ring time out greater than 999 seconds.</li>
<li>Fixed bug where non-standard characters (ex. ♣) in a person&#8217;s name would cause an error.</li>
<li>Fixed bug where the deletion of a person would not delete automatically generated softphone accounts that were created for that person.</li>
<li>Changed <em>Mobile Number</em><em> </em>field to <em>Alternate Number</em>.</li>
<li>Moved <em>Alternate Number</em> field to <em>Advanced Settings</em> section of the <em>People</em> configuration screen.</li>
</ul>
</li>
<li><strong>Teams:</strong>
<ul>
<li>Removed inaccurate text that indicated an admin could select multiple values by holding down <em>ctrl</em> or <em>cmd</em> keys on their keyboard.</li>
</ul>
</li>
<li><strong>Phones:</strong>
<ul>
<li>The IP address of a phone is now shown on the <em>Phones</em> tab when that phone is online.</li>
<li>Reduced Cisco phone registration time out to allow the phones to work better remotely.</li>
<li>Resolved Polycom phone daylight savings time issues, where certain models were showing an incorrect time after daylight savings time engaged or discontinued.</li>
</ul>
</li>
<li><strong>Phone Services:</strong>
<ul>
<li>Added feature to remove spaces before or after the server address for a phone service.</li>
</ul>
</li>
<li><strong>Apps:</strong>
<ul>
<li><em>Auto Attendant:</em>
<ul>
<li>Added validation to <em>Extension</em> field to prevent an admin from entering more than 6 digits.</li>
</ul>
</li>
</ul>
</li>
<li><strong>Billing:</strong>
<ul>
<li>Updated billing screens to allow transactions to take place if the Jazinga invoicing service is offline. In the event of an invoicing service outage, transactions will be deferred until the service is back online, but customers may still purchase licenses and publish changes.</li>
<li>Moved permanent paid user licenses to a separate line item on the <em>Billing</em> page, as well as any generated invoices.</li>
</ul>
</li>
<li><strong>Publish:</strong>
<ul>
<li>Changes that are about to be published are now shown on the <em>Publish </em>tab by default.</li>
<li>Clarified text regarding the free trial period afforded to new customers who are using the monthly licensing model.</li>
<li>Added text to notify administrators that a factory reset will cancel an active billing subscription.</li>
<li>Added a feature to prevent automatic publish if there are currently active calls. If active calls are present, the administrator is notified, and they are presented with an option to disconnect the calls and force the publishing process to complete.</li>
<li>The time zone is now shown on the <em>History</em> page for each change that was made to the system.</li>
<li>Added text to the <i>Factory Reset</i> page to indicate what the limits of the base plan are, in case a customer wishes to reduce their license usage and return to free system limits.</li>
<li>Added text to the <em>Publish</em> page that is shown to customers who are using the one time purchase person licenses. The text explains that a new person will be added as a monthly recurring license, and that one time licenses must be purchased ahead of time, before publishing.</li>
<li>Added feature to allow permanent paid user licenses to survive factory resets.</li>
</ul>
</li>
<li><strong>Mobile Applications and Softphones:</strong>
<ul>
<li><em>iOS:</em>
<ul>
<li>Updated iOS SIP account options to reduce battery drain.</li>
<li>Fixed bug where the keyboard would not reappear after the contact screen had been visited.</li>
<li>Fixed bug where the add/transfer screen would not appear correctly under certain circumstances.</li>
<li>Removed <em>Done</em> button from the contact picker screen (<em>Done</em> button was not used).</li>
<li>Fixed various interface issues to improve app usability.</li>
<li>Added a notification to the user if the Jazinga app cannot use SIP services on the iOS device (typically occurs if there is another softphone already running on the same device).</li>
<li>Added feature to call the last dialed number when the <em>Call</em> button is tapped from the <em>Dial</em> screen.</li>
<li>Updated the way that network changes are handled to better survive a change from 3G/4G to wifi and vice versa.</li>
<li>Added support to vibrate on incoming calls.</li>
</ul>
</li>
<li><em>Mac OS X:</em>
<ul>
<li>OS X app released to beta customers. Beta customers may request the app by emailing <a href="mailto:support@jazinga.com" target="_blank">support@jazinga.com</a>.</li>
</ul>
</li>
</ul>
</li>
<li><strong>Appliance Software:</strong>
<ul>
<li>Updated SIP options to allow the appliance to work more easily behind different routers.</li>
<li>Various stability fixes for appliance software.</li>
<li>Added statistics gathering software to allow for call statistics to be shown to administrators in future software versions.</li>
<li>Added TCP port negotiation to UPnP requests to allow for iOS and Mac softphone apps to function without manual port forwarding.</li>
<li>Significantly improved recovery in the event of bad network situations (such as having no network connectivity when the appliance is booted), reducing the requirement to reboot the appliance to resolve issues.</li>
<li>Added a 1 second delay before inbound calls are answered. For T1/E1/PRI phone services, this ensures that caller ID information will always be received.</li>
<li>Fixed an issue where answered calls directed to an auto attendant sometimes had the first few seconds of audio cut off because the router or firewall was not ready to receive data.</li>
<li>Introduced mechanism to work around routers that fail to clear an invalid state when connectivity drops and then returns. This bad state causes phone service registrations to fail.</li>
<li>Adds an option to allow a person to break out of voicemail by pushing 0 if they do not wish to leave a message.</li>
<li>Added recording that is now played to inform a person that their phone services are offline if phone services are down when they attempt to place an outbound call.</li>
</ul>
</li>
<li><strong>Admin and Reseller Portal:</strong>
<ul>
<li>Fixed several screens (<em>Company Directory, Emergency Call Notification, Auto Attendant</em>) that resellers received errors on when attempting to configure a client system.</li>
<li>Added a new payments screen to allow resellers to view billing history for their clients.</li>
<li>Updated reseller view to use sidebar for navigation.</li>
<li>Added text to explain that the last remaining administrative associate for a reseller cannot be deleted.</li>
<li>Fixed bug where a reseller with 2 or more associates could not be deleted.</li>
</ul>
</li>
<li><strong>General:</strong>
<ul>
<li>The <a href="http://cloud.jazinga.com/start" target="_blank">cloud.jazinga.com/start</a> web page will now show the MAC address of all discovered appliances if more than one appliance is present on the network.</li>
<li>Added favourite icon, to enable visual identification of Jazinga Cloud website in browser favourites.</li>
<li>Fixed email links in welcome and password reset emails (email addresses were not linked previously).</li>
</ul>
</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://jazinga.com/jazinga-cloud-updates-for-april-11-2013/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Jazinga Cloud Updates for January 4, 2013</title>
		<link>http://jazinga.com/changelog-2012-01-04/</link>
		<comments>http://jazinga.com/changelog-2012-01-04/#comments</comments>
		<pubDate>Fri, 04 Jan 2013 19:56:55 +0000</pubDate>
		<dc:creator>alex</dc:creator>
				<category><![CDATA[Changelog]]></category>

		<guid isPermaLink="false">http://jazinga.com/?p=380</guid>
		<description><![CDATA[On Friday, January 4, 2013, Jazinga Cloud services will be updated. The following changes are included in this release: Overview: Call History: Call log times were recorded and displayed in UTC. Call log data is now recorded in GMT and converted to the configured time zone of the appliance when displayed. Calls with a return status of [...]]]></description>
				<content:encoded><![CDATA[<p>On Friday, January 4, 2013, Jazinga Cloud services will be updated. The following changes are included in this release:</p>
<ul class="changelog">
<li><strong>Overview</strong>:
<ul class="changelog">
<li><em>Call History:</em>
<ul class="changelog">
<li>Call log times were recorded and displayed in UTC. Call log data is now recorded in GMT and converted to the configured time zone of the appliance when displayed.</li>
<li>Calls with a return status of &#8220;congested&#8221; were not logged. These calls are now logged, allowing customers to see if their system is over capacity</li>
<li>Calls sent to an extension showed a destination of &#8220;s&#8221; in the CDRs. Calls will now show the extension that was dialed.</li>
<li>CDR data stored on Jazinga appliances was wiped during a software upgrade in some cases (CDR data in the cloud interface was always retained). Local CDR data now survives upgrades.</li>
</ul>
</li>
</ul>
</li>
<li><strong>People:</strong>
<ul class="changelog">
<li>Newly created people would immediately receive an email, and could log in, even though their addition to the system had not yet been published. New people are now stored until a publish operation is performed. On publish, welcome emails are sent out, and the person&#8217;s ability to log into the user portal is activated.</li>
<li>During a password reset, a person would be notified if the email address that they entered was not found in the Jazinga Cloud system. This has been removed due to security concerns.</li>
</ul>
</li>
<li><strong>Phones:</strong>
<ul class="changelog">
<li>Polycom phones were showing incorrect daylight savings time (DST) values after DST engaged for the year. DST values are now correct on Polycom phones to ensure that they show the correct time.</li>
<li>Phone configurations now contain the port negotiated by UPnP, if UPnP is active and negotiated a port.</li>
<li><em>Remote Phones:</em>
<ul class="changelog">
<li>Updated and corrected wording on remote phones page to clarify what the remote phones tester is to be used for.</li>
<li>RTP audio data was sometimes not sent during testing. Increased the amount of data that is sent.</li>
<li>Added echo test at the start of the remote SIP test to force holes in the firewall for RTP data.</li>
<li>SIP test would always test against the default SIP port instead of the port negotiated by UPnP. Test will now send data to the UPnP negotiated port, if one exists.</li>
</ul>
</li>
</ul>
</li>
<li><strong>Phone Services:</strong>
<ul class="changelog">
<li>Phone services form allowed a person to submit only a space in the &#8220;server&#8221; textbox. This is now validated correctly.</li>
<li>Phone services are now monitored for status and will email the primary admin when a phone service has a status of UNREACHABLE or UNKNOWN.</li>
<li>Phone services tester would always use port 5060 instead of the port supplied by the admin. Tester now pulls the entered port and uses it.</li>
<li>Cisco/Linksys phones will now use DNS SRV lookups for registrations.</li>
</ul>
</li>
<li><strong>Apps:</strong>
<ul class="changelog">
<li><em>Auto Attendant:</em>
<ul class="changelog">
<li>Invalid help text has been removed.</li>
</ul>
</li>
<li><em>Conference Bridge:</em>
<ul class="changelog">
<li>Conference room PIN generation would sometimes fail if only a single conference room was present. PINs are now generated successfully.</li>
</ul>
</li>
</ul>
</li>
<li><strong>Billing:</strong>
<ul class="changelog">
<li>Incorrect country code was passed to billing provider in some cases. Correct country code is now sent.</li>
<li>Country field was previously a textbox. Field has been changed to a dropdown.</li>
<li>Customers viewing a system with a cancelled subscription would see &#8220;trial period&#8221; notice. Customers who revoke a subscription will no longer see the trial period notice unless they begin making changes to their blank configuration.</li>
<li>Tax data was not updating in a timely fashion if a subscriber&#8217;s province/state or country changed. Take data is now updated as soon as a subscriber&#8217;s location is changed.</li>
<li>Processing a failed response from billing provider could block a system from publishing. Failed responses are now processed correctly so that systems can continue to publish.</li>
<li>A cancelled subscription would sometimes push a blank config to the appliance without cancelling the subscription successfully. Subscriptions are now confirmed cancelled before configuration is wiped.</li>
<li>Customer information was attached to an account, but not appliance information. Customers with multiple appliances could not determine which appliance was associated with which set of licensing charges. Unique system fingerprint is now sent alongside customer information to assist with identifying the owner of licensing charges.</li>
<li>Performing a factory reset would not cancel an active subscription in some cases. Factory reset procedure will now cancel an active billing subscription, if one exists.</li>
</ul>
</li>
<li><strong>Publish:</strong>
<ul class="changelog">
<li>When discarding changes instead of publishing, systems that had active people but that had not completed the setup wizard would be redirected to the terms of service page. Discard now drops changes and leaves the admin at the publish page.</li>
</ul>
</li>
<li><strong>Mobile Applications:</strong>
<ul class="changelog">
<li>Administrative and reseller users could log into the mobile apps, but registration failed as they were not associated with any Jazinga appliance. Administrative users and reseller users are now blocked from logging into any mobile app.</li>
</ul>
</li>
<li><strong>Appliance Software:</strong>
<ul class="changelog">
<li>Updated version of Asterisk (11.0.1) has been incorporated into the software running on Jazinga appliances.</li>
<li>UPnP is now used to discover and map NAT entry on a router in front of a Jazinga appliance. This avoids having to manually forward ports. If UPnP is not enabled, or no port can be negotiated, the system will fall back to 5060 as was used in the past.</li>
<li>UPnP test is now performed on updated appliance software installation, appliance reboot, or network config changes.</li>
</ul>
</li>
<li><strong>Admin and Reseller Portal:</strong>
<ul class="changelog">
<li>When returning to the list of all managed systems, the system you were last working with is now highlighted.</li>
<li>When returning to the list of all managed systems, the screen automatically scrolls to the location of the last system you were working on.</li>
<li>Resellers sometimes received an exception error when trying to log in with valid credentials. Valid credentials used by resellers will no longer generate an error.</li>
<li>Resellers sometimes received an exception error when trying to reset a password. The password was not reset, but the reseller could no longer log in. Password resets are now processed correctly.</li>
<li>Fixed spelling and wording in reseller welcome email.</li>
<li>Incorrect &#8220;hand&#8221; pointer was shown for the mouse cursor on areas of the installation list that could not be clicked on. A standard arrow pointer is now shown for these locations instead.</li>
</ul>
</li>
<li><strong>General:</strong>
<ul class="changelog">
<li>&#8220;E-mail&#8221; has been changed to &#8220;Email&#8221; throughout the product.</li>
<li>&#8220;Last checked device online&#8221; would sometimes not update until a publish operation. Last check-in data is now recorded correctly.</li>
<li>DNS SRV records are now generated for all appliances in addition to the A records that were generated in the past. This allows more reliable registrations from certain phone models.</li>
<li>General code clean up for improved performance.</li>
</ul>
</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://jazinga.com/changelog-2012-01-04/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New Changelog Page Created</title>
		<link>http://jazinga.com/new-changelog-page-created/</link>
		<comments>http://jazinga.com/new-changelog-page-created/#comments</comments>
		<pubDate>Mon, 24 Dec 2012 16:21:51 +0000</pubDate>
		<dc:creator>alex</dc:creator>
				<category><![CDATA[Changelog]]></category>

		<guid isPermaLink="false">http://jazinga.com/?p=352</guid>
		<description><![CDATA[A new changelog page has been created for the Jazinga Cloud product. Release notes for new Jazinga Cloud software updates will be posted to jazinga.com/changelog. This page will display any new features, changes, or bug fixes for new software versions.]]></description>
				<content:encoded><![CDATA[<p>A new changelog page has been created for the Jazinga Cloud product. Release notes for new Jazinga Cloud software updates will be posted to <a href="http://jazinga.com/changelog" title="jazinga.com/changelog">jazinga.com/changelog</a>. This page will display any new features, changes, or bug fixes for new software versions. </p>
]]></content:encoded>
			<wfw:commentRss>http://jazinga.com/new-changelog-page-created/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
