<?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>Talk Tech To Me - GFI Blog &#187; Kevin Hodak</title>
	<atom:link href="http://www.gfi.com/blog/author/kevin-hodak/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gfi.com/blog</link>
	<description>Brought to you by GFI Software</description>
	<lastBuildDate>Fri, 13 Sep 2013 16:51:58 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Why Organizations Are Moving Email to Fax (Part 2)</title>
		<link>http://www.gfi.com/blog/why-organizations-are-moving-email-to-fax-part-2/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=why-organizations-are-moving-email-to-fax-part-2</link>
		<comments>http://www.gfi.com/blog/why-organizations-are-moving-email-to-fax-part-2/#comments</comments>
		<pubDate>Thu, 29 Dec 2011 15:00:23 +0000</pubDate>
		<dc:creator>Kevin Hodak</dc:creator>
				<category><![CDATA[Featured]]></category>
		<category><![CDATA[Tech Zone]]></category>
		<category><![CDATA[email]]></category>
		<category><![CDATA[email to fax]]></category>
		<category><![CDATA[fax]]></category>
		<category><![CDATA[outbound communication]]></category>
		<category><![CDATA[SMTP]]></category>

		<guid isPermaLink="false">http://www.gfi.com/blog/?p=7743</guid>
		<description><![CDATA[In addition to the inbound communication that was covered in Part 1 of this two-part blog post, it is important to consider the need to send outbound communication through email to fax functionality.    In a similar fashion to the ability &#8230;]]></description>
				<content:encoded><![CDATA[<p><a href="http://www.gfi.com/blog/wp-content/uploads/2011/12/fax-to-email-communication1.jpg"><img class="alignright size-full wp-image-7744" style="border-width: 0px; border-color: black; border-style: solid; margin: 10px;" title="email-to-fax-communication" alt="" src="http://www.gfi.com/blog/wp-content/uploads/2011/12/fax-to-email-communication1.jpg" width="243" height="221" /></a>In addition to the inbound communication that was covered in <a href="http://www.gfi.com/blog/fax-to-email/">Part 1</a> of this two-part blog post, it is important to consider the need to send outbound communication through email to fax functionality.    In a similar fashion to the ability to receive faxes as email, users can send faxes directly from their standard email client when using an electronic fax solution.  This allows for rapid adoption by the user community as the email to fax process is not a new one for them to learn (they already know how to send email) and significant productivity savings as the user no longer has to print a document and manually send it from a traditional fax machine.<span id="more-7743"></span></p>
<p>With most email to fax solutions, the end user is able to send an email to either faxnumber@domain.com (where domain.com is a custom fax domain) or to an Outlook business fax contact.  From the user perspective, they are creating the email, addressing it, adding notes to the subject and/or body, attaching the desired fax documents, and clicking ‘Send’.   With typical electronic fax solutions, the information on the fax sender and recipient, as well as the subject and body fields from the email, will be included on the cover page.  This allows for the use of cover page templates that can be used in a dynamic fashion rather than requiring the user to create a custom cover page each time they wish to send an email to fax.  The inclusion of the subject and body from the email accommodate the need to add instructions to the cover page so that the user is able to replicate the addition of manual notes with the email to fax process.</p>
<p>Looking at this process from the IT administrator’s point of view, the email is routed using a direct SMTP connector or forwarding rule that is pointed to the fax server.   This option is most common in environments with on-premise email servers that the administrator can easily configure with this custom rule.  Alternatively, as in environments with hosted email solutions, the email is routed by the mail server to the fax server or service using DNS as with any other outbound email.  Regardless of the method used to route the email, the electronic fax solution converts the email to fax for delivery across the phone network to the remote recipient.  Once the fax transmission completes, the fax solution should return an email to the sender to let them know whether their email to fax submission was successfully sent or that it failed to transmit.  Typically, the reason for the failure and an option to retry the fax will also be included.</p>
<p>The ability to send an email to fax also allows for easy integration with third party applications.  Many organizations are sending faxes through a business application such as an Enterprise Resource Planning ERP), invoicing, or accounting system.  With some of these applications, the email to fax workflow can be configured by the IT Administrator while others may require customization by the software vendor.  Whether sending faxes from their email client or through a business application, email to fax allows users to send faxes through an efficient process that bridges the gap between their desire to use email and their recipients desire to receive faxes.</p>
<p>Have a look at what GFI FaxMaker, our leading <a href="http://www.gfi.com/fax-server-software?adv=13558&amp;loc=7">fax server software</a>, can do for you; or just <a href="http://landfax.gfi.com/faxing-manually-sm?adv=13558&amp;loc=21">download a free trial</a> and give it a spin!</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.gfi.com/blog/why-organizations-are-moving-email-to-fax-part-2/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Why Organizations Are Moving Fax to Email (Part 1)</title>
		<link>http://www.gfi.com/blog/fax-to-email/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=fax-to-email</link>
		<comments>http://www.gfi.com/blog/fax-to-email/#comments</comments>
		<pubDate>Mon, 12 Dec 2011 15:00:54 +0000</pubDate>
		<dc:creator>Kevin Hodak</dc:creator>
				<category><![CDATA[Featured]]></category>
		<category><![CDATA[SMB Zone]]></category>
		<category><![CDATA[fax machine]]></category>
		<category><![CDATA[fax server]]></category>
		<category><![CDATA[fax service]]></category>
		<category><![CDATA[fax to email]]></category>
		<category><![CDATA[faxing]]></category>

		<guid isPermaLink="false">http://www.gfi.com/blog/?p=7700</guid>
		<description><![CDATA[As organizations continue to prefer fax transmission for certain scenarios, either because of compliance requirements, or when dealing with legacy systems, it is important for them to allow their users to streamline processes by incorporating fax with email.  In the &#8230;]]></description>
				<content:encoded><![CDATA[<p><a href="http://www.gfi.com/blog/wp-content/uploads/2011/12/fax-to-email-communication.jpg"><img class="alignright size-full wp-image-7701" style="border-width: 0px; border-color: black; border-style: solid; margin: 10px;" title="fax-to-email-communication" alt="" src="http://www.gfi.com/blog/wp-content/uploads/2011/12/fax-to-email-communication.jpg" width="270" height="246" /></a>As organizations continue to prefer fax transmission for certain scenarios, either because of compliance requirements, or when dealing with legacy systems, it is important for them to allow their users to streamline processes by incorporating fax with email.  In the first of this two-part blog post, we will take a look at the ever increasing integration and overlap of fax to email for inbound fax traffic.  This fax to email process allows the sender to use a traditional fax machine, fax service, or fax server to send the document in real-time over the phone network, but provides the recipient with the convenience of email delivery.<span id="more-7700"></span></p>
<p>While most companies have moved to email as their primary means of communication, many still rely heavily on the ability to receive faxes from their customers and business partners.  There are three main reasons why fax is still important for these organizations:</p>
<ol>
<li>To obtain a phone line and a fax machine is still the simplest and least technical way for a small company to begin communicating with the outside world.</li>
<li>Many companies, especially those in the healthcare, legal, and insurance space, are required to transmit data via fax because of compliance concerns.</li>
<li>Companies are maintaining legacy applications, such as purchasing and billing systems, which are only able to transmit a document via fax.</li>
</ol>
<p>With these things in mind, it is obvious that forcing your customers and partners to move completely from fax to email is not practical.</p>
<p>The answer to bridge the gap from fax to email is the implementation of an electronic faxing solution.  Whether implemented as an online service or a network fax server, these systems typically allow multiple options for delivering inbound faxes to the user via email.  The first consideration is the routing of inbound faxes.  While simple electronic fax systems provide the ability to deliver faxes to a single recipient for manual distribution, more advanced solutions provide <a href="http://www.gfi.com/blog/discussing-fax-routing-methods/">dynamic routing options</a> for automatic delivery.   For example, each user or department could be assigned a unique fax number for fax to email delivery directly to their mailbox.  This not only provides for a more efficient user experience, but also allows the organization to control the delivery of sensitive fax traffic and ensure that only the correct recipient views the information.  When compared with a traditional fax machine that would print the received fax where it could be viewed by anybody walking by, the fax to email process represents a significant enhancement to the organizations security practices.</p>
<p>From the end-user’s perspective, the ability to receive the fax as a PDF or TIF file offers two distinct advantages over standard fax machines.  In addition to working more productively with the delivery of fax to email rather than visiting the fax machine, they are also able to easily integrate faxing with their business workflows since the fax is already in an electronic format.</p>
<p>In part two, we will take a look at the fax to email flow in the opposite direction; email to fax.</p>
<p>Have a look at what GFI FaxMaker, our leading <a href="http://www.gfi.com/fax-server-software?adv=13558&amp;loc=7">fax server software</a>, can do for you; or just <a href="http://landfax.gfi.com/faxing-manually-sm?adv=13558&amp;loc=21">download a free trial</a> and give it a spin!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.gfi.com/blog/fax-to-email/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Implementing a Fax Server in a VoIP Environment</title>
		<link>http://www.gfi.com/blog/fax-voip/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=fax-voip</link>
		<comments>http://www.gfi.com/blog/fax-voip/#comments</comments>
		<pubDate>Thu, 15 Sep 2011 16:00:51 +0000</pubDate>
		<dc:creator>Kevin Hodak</dc:creator>
				<category><![CDATA[Featured]]></category>
		<category><![CDATA[SMB Zone]]></category>
		<category><![CDATA[Fax over IP]]></category>
		<category><![CDATA[fax voip]]></category>
		<category><![CDATA[FOIP]]></category>
		<category><![CDATA[Voice over IP]]></category>
		<category><![CDATA[VoIP]]></category>

		<guid isPermaLink="false">http://www.gfi.com/blog/?p=3461</guid>
		<description><![CDATA[Voice over IP (VoIP) is becoming an increasingly popular means to deploy the phone infrastructure within the SMB space.  However, the move to VoIP presents the challenge of interfacing the new VoIP system with the ability to send and receive &#8230;]]></description>
				<content:encoded><![CDATA[<p><img class="alignright size-medium wp-image-3462" style="margin: 10px; border: 0px solid black;" title="Fax VoIP communication" src="http://www.gfi.com/blog/wp-content/uploads/2011/09/Fax-VoIP-communication2-300x215.jpg" alt="" width="300" height="215" />Voice over IP (VoIP) is becoming an increasingly popular means to deploy the phone infrastructure within the SMB space.  However, the move to VoIP presents the challenge of interfacing the new VoIP system with the ability to send and receive faxes.  The advent of Fax over IP (FoIP) technology has allowed organizations to bridge this gap and integrate faxing with the VoIP environment through the use of a network fax server.<span id="more-3461"></span></p>
<p>Traditionally, fax servers have been implemented on a physical server using a modem or internal fax card to connect to analog or digital phone lines.   This is not desirable within organizations using VoIP as it requires the maintenance and cost of separate phone lines outside of the VoIP system.  The development of T.38 as a reliable protocol for converting the traditional fax traffic into Internet Protocol (IP) packets that T.38-capable VoIP systems understand, has allowed organizations to eliminate these extra phone lines.  The fax server is now able to communicate directly with the VoIP system through the Local Area Network (LAN), and the VoIP system is then able to convert the T.38 packets into the traditional analog or digital connections to the telephone provider. This not only allows for the elimination of the costs and maintenance associated with the separate phone lines, but it also allows for the central management of all the phone resources in the organization through the phone system.</p>
<p>The move to faxing through a VoIP environment also allows for several other benefits that are not quite as readily apparent, but can be as important.  Perhaps the most important of these is the ability to run the fax server on a virtual server using applications such as VMware or Microsoft Hyper-V.   Unlike traditional faxing that required a separate physical modem or card to act as the connection point, FoIP-enabled fax servers use a software module to communicate with the server’s Network Interface Card (NIC), which then connects to the VoIP system over the LAN.  This allows organizations to take advantage of the native options of virtualization to easily snapshot, clone, or restore servers in the event of a disaster.  With the physical component out of the picture, the all-software solution allows not only for virtualization, but also for other flexibility that is impossible with a traditional solution.  Chief among these are the ability to easily evaluate the solution through downloadable software and evaluation license keys, and scalability as it is simply a matter of adding licensing to expand.  Gone are the days of ensuring that the fax server has physical room for expansion, waiting for the new fax board to arrive, and bringing down production faxing to install the new board.</p>
<p>It is not unusual for organizations, especially SMBs, to want to take advantage of the benefits of a FoIP fax server, but they have not yet moved to a VoIP infrastructure.  All is not lost for these organizations!  There are inexpensive media gateway appliances that will take traditional analog or digital phone lines and convert them to T.38 for IP delivery to the fax server.  This is a popular transition path for organizations that want to take advantage of the virtualization, scalability, and flexibility options immediately, even if they do not plan to move to VoIP for some time.</p>
<p>Whether an organization is currently managing their phone needs through a VoIP system, is looking to move to VoIP in the near future, or is some way off from implementing VoIP, the benefits of moving to a FoIP-capable fax server are significant and available.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.gfi.com/blog/fax-voip/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
	</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

 Served from: www.gfi.com @ 2013-09-15 05:16:44 by W3 Total Cache --