<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet href="/feed_style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
    <tabi:metadata xmlns:tabi="https://github.com/welpo/tabi">
        <tabi:base_url>&#x2F;</tabi:base_url>
        <tabi:separator>
            •
        </tabi:separator>
        <tabi:about_feeds>This is a web feed, also known as an Atom feed. Subscribe by copying the URL from the address bar into your newsreader. Visit About Feeds to learn more and get started. It&#x27;s free.</tabi:about_feeds>
        <tabi:visit_the_site>Visit website</tabi:visit_the_site>
        <tabi:recent_posts>Recent posts</tabi:recent_posts>
        <tabi:last_updated_on>Updated on $DATE</tabi:last_updated_on>
        <tabi:default_theme></tabi:default_theme>
        <tabi:post_listing_date>date</tabi:post_listing_date>
        <tabi:current_section>VoIP</tabi:current_section>
    </tabi:metadata><link rel="extra-stylesheet" href="/skins/indigo_ingot.css?h=d429472afbb246441b1a" /><title>Andrew Wippler's Sketchpad - VoIP</title>
        <subtitle>Ideas, blog, etc. </subtitle>
    <link href="/tags/voip/atom.xml" rel="self" type="application/atom+xml"/>
    <link href="/tags/voip/" rel="alternate" type="text/html"/>
    <generator uri="https://www.getzola.org/">Zola</generator><updated>2016-01-29T15:00:29+00:00</updated><id>/tags/voip/atom.xml</id><entry xml:lang="en">
        <title>VoIP Troubleshooting Checklist</title>
        <published>2016-01-29T15:00:29+00:00</published>
        <updated>2016-01-29T15:00:29+00:00</updated>
        <author>
            <name>Andrew Wippler</name>
        </author>
        <link rel="alternate" href="/2016-01-29-voip-troubleshooting-checklist/" type="text/html"/>
        <id>/2016-01-29-voip-troubleshooting-checklist/</id>
        
            <content type="html">&lt;p&gt;Voice over IP is very robust and reliable when set up properly. There are only four key areas to set up and check for issues. I have compiled the below list as things to check when an issue occurs. All of the steps are pretty basic and are known by every VoIP professional; however, it is handy to have to show a non-technical person or somebody who has little knowledge on VoIP systems.&lt;&#x2F;p&gt;
&lt;p&gt;Phone&lt;&#x2F;p&gt;
&lt;ul&gt;
&lt;li&gt;Ensure the phone is compatible with the PBX you selected&lt;&#x2F;li&gt;
&lt;li&gt;Ensure voice is on the voice vlan and data is on the data vlan&lt;&#x2F;li&gt;
&lt;li&gt;Ensure the audio codec being used on the phone is supported by the server&lt;&#x2F;li&gt;
&lt;li&gt;Ensure the codec you want to use is listed first in the settings&lt;&#x2F;li&gt;
&lt;li&gt;Switch codecs to see if voice quality improves or declines in quality&lt;&#x2F;li&gt;
&lt;&#x2F;ul&gt;
&lt;p&gt;Phone-to-PBX&lt;&#x2F;p&gt;
&lt;ul&gt;
&lt;li&gt;Ensure voice traffic is on a separate vlan&lt;&#x2F;li&gt;
&lt;li&gt;Ensure the voice vlan has priority on the network (QoS)&lt;&#x2F;li&gt;
&lt;li&gt;Ensure there are no faulty Ethernet lines and that all 8 wires go to a single port (for PoE and best practice)&lt;&#x2F;li&gt;
&lt;li&gt;Ensure switches are voice vlan capable&lt;&#x2F;li&gt;
&lt;li&gt;Ensure the switch has enough voltage to power the amount of phones connected to it (if using PoE)&lt;&#x2F;li&gt;
&lt;&#x2F;ul&gt;
&lt;p&gt;PBX&lt;&#x2F;p&gt;
&lt;ul&gt;
&lt;li&gt;Ensure it is powered on&lt;&#x2F;li&gt;
&lt;li&gt;Ensure services are running&lt;&#x2F;li&gt;
&lt;li&gt;Check call quality between internal-to-internal extension&lt;&#x2F;li&gt;
&lt;li&gt;Check call quality between internal-to-internal extension on separate PBX host (if clustered)&lt;&#x2F;li&gt;
&lt;li&gt;Check inbound call routing rules&lt;&#x2F;li&gt;
&lt;li&gt;Check outbound call routing rules&lt;&#x2F;li&gt;
&lt;&#x2F;ul&gt;
&lt;p&gt;PBX-to-Service Provider&lt;&#x2F;p&gt;
&lt;ul&gt;
&lt;li&gt;Ensure you have phone service and it is turned on&lt;&#x2F;li&gt;
&lt;li&gt;Ensure the service provider allows self-managing of the Caller ID&lt;&#x2F;li&gt;
&lt;li&gt;Ensure voice traffic is not being sent out on the public internet (on-net) if using SIP trunking&lt;&#x2F;li&gt;
&lt;&#x2F;ul&gt;
</content>
        </entry><entry xml:lang="en">
        <title>My Review of Digium</title>
        <published>2016-01-22T15:00:41+00:00</published>
        <updated>2016-01-22T15:00:41+00:00</updated>
        <author>
            <name>Andrew Wippler</name>
        </author>
        <link rel="alternate" href="/2016-01-22-my-review-of-digium/" type="text/html"/>
        <id>/2016-01-22-my-review-of-digium/</id>
        
            <content type="html">&lt;p&gt;In a previous post, I mentioned that we switched to Digium Switchvox. Here are some features I really enjoy.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;an-extension-has-access-to-everything&quot;&gt;An extension has access to everything&lt;&#x2F;h2&gt;
&lt;p&gt;There are no receptionist licenses. There are no addons for basic features such as faxing or voicemail. There is no confusion when it comes to determining a cost. Every extension has access to everything for one low yearly subscription fee.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;the-admin-interface-is-accessed-via-web-browser&quot;&gt;The admin interface is accessed via web browser&lt;&#x2F;h2&gt;
&lt;p&gt;I like web browser software. It means I do not have to install an application to configure a setting and I can access the interface from my mobile phone, tablet, or Chromebook.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;it-works-well-with-asterisk&quot;&gt;It works well with Asterisk&lt;&#x2F;h2&gt;
&lt;p&gt;While the extension licenses are cheap ($12&#x2F;year&#x2F;extension for titanium support), I have difficulty buying a license for a phone that will probably be used once in a 5 year time span - such as a lobby phone, dorm room phone, or classroom. These extensions just need dial tone and no advanced functionality (contact listing, switchboard, etc.) - having them as an Asterisk extension works great.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;phones-are-easy-to-add&quot;&gt;Phones are easy to add&lt;&#x2F;h2&gt;
&lt;p&gt;Our installer set us up several templates. Using these templates, I can create an extension in under 10 seconds. Adding it to the phone takes an additional 10-60 seconds depending upon the state of the phone.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;i-can-use-any-phone&quot;&gt;I can use any phone&lt;&#x2F;h2&gt;
&lt;p&gt;There are 3 specific spots in my environment where a cordless phone is vital. With Digium, I can deploy a Grandstream DP715 and call it a day.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;the-servers-are-smart&quot;&gt;The servers are &quot;smart&quot;&lt;&#x2F;h2&gt;
&lt;p&gt;The servers are smart in that they start up after a power outage. Not that power outages happen all the time, but occasionally when the UPS battery is depleted, it is nice to know the default is set to power up when there is a power source.&lt;&#x2F;p&gt;
</content>
        </entry><entry xml:lang="en">
        <title>VoIP implementation and tests</title>
        <published>2016-01-15T15:00:47+00:00</published>
        <updated>2016-01-15T15:00:47+00:00</updated>
        <author>
            <name>Andrew Wippler</name>
        </author>
        <link rel="alternate" href="/2016-01-15-voip-implementation-and-tests/" type="text/html"/>
        <id>/2016-01-15-voip-implementation-and-tests/</id>
        
            <content type="html">&lt;p&gt;In 2014, we decided to transition from a Mitel sx200 to a VoIP solution. We researched Cisco UM, Mitel, Lync, Shoretel, Avaya, Digium, a few hosted solutions, and a few Asterisk clones. I was one of three who sat through several presentations of &lt;strong&gt;the same features of every single phone system&lt;&#x2F;strong&gt;. Two weeks into this process, we narrowed the field down to Avaya and Digium with cost-to-implement for 650 extensions being the main deciding factor. The other deciding factor was these two companies did not give a speech about we should choose them because such-and-so research company rated them #1 in customer satisfaction. In the second round of finding a VoIP solution, we asked if we could do a one week test of a demo system. Both parties agreed to this test and we were sent demo units. With the test units, we selected 6 secretaries, 1 programmer, myself, and 2 receptionists to participate in making internal calls and testing each of the functions. During the week, we deployed several tests:&lt;&#x2F;p&gt;
&lt;ul&gt;
&lt;li&gt;Phone server interruption (I unplugged the server ethernet for 10-30 seconds)&lt;&#x2F;li&gt;
&lt;li&gt;Call audio quality&lt;&#x2F;li&gt;
&lt;li&gt;Phone restart time&lt;&#x2F;li&gt;
&lt;li&gt;The time it took to set up 1 phone&lt;&#x2F;li&gt;
&lt;li&gt;Admin user interface&lt;&#x2F;li&gt;
&lt;&#x2F;ul&gt;
&lt;p&gt;After the week was done, we asked each participant which system they liked better. Everyone liked the Digium handsets. We also received reports that call audio quality was better with Digium (I believe Avaya adds white noise). During the &quot;Phone server interruption&quot; the Digium phones reconnected without rebooting whereas the Avaya phones rebooted as soon as the server went offline.&lt;&#x2F;p&gt;
&lt;p&gt;After looking at a 20 year TCO (with updates and phone upgrades), both phone systems came out to be nearly equal in cost. Ultimately we chose to go with Digium based upon internal experiences and haven&#x27;t regretted it.&lt;&#x2F;p&gt;
</content>
        </entry>
</feed>
