Thursday, 13 June 2013

Manually Configure Voip.ms on the OBi100 VoIP ATA - Quick Setup


In this article, I will walk you through the basics of how to quickly (relatively speaking) manually configure your shiny new Obihai OBi100 ATA directly with Voip.ms, a well known BYOD VoIP Service Provider (VSP) with proxy servers in both the USA and Canada.

To achieve the goal of a quick and reliable setup, I will recommend that the ATA be initially "factory reset" to it's default values (this way, we're starting on the same page, literally).  Then, I will point out only the essential settings that "must be edited" manually, in order to connect and achieve service registration with the Voip.ms servers.

                                                    ---------------------------------
NOTE:
My procedures outlined here are based on the premise that your OBi100 is NOT, and will not be, linked to the OBiTalk web portal at www.obitalk.com using their "Add Device" feature.  If you "add your device" to the OBiTalk portal, the portal will takeover administration of your OBi device remotely (which is fine, if that is what you want, however my tutorials are not based on that premise).  Thus, any local administration settings you do to your OBi100, via local LAN side administration, could be over-ridden by the OBiTalk remote administration portal periodically, or upon device reboot.  Thus, to proceed with my procedures outlined here, and if your OBi100 is/was previously configured via OBiTalk portal, then I recommend you "unlink" and remove your OBi100 from OBiTalk portal (remove from "Add Device" list) first, followed by a factory reset to ensure you are starting with default configuration values and no remote administration links.

Remember, the premise of all my tutorials are to allow you to locally and manually configure your OBi100 ATA without interaction with the OBiTalk remote administration portal at www.obitalk.com.  (My goal is to show you how to DIY without any 3rd party interaction.)


                                                    ---------------------------------


The good news is that the OBi100 ATA can be configured and making phone calls with your existing Voip.ms account in less than 10 minutes.  (Once you have read and understand all the information outlined below :)

In order to proceed with the quick and easy setup procedure, a few assumptions must be made and prerequisites met:

Assumptions and Prerequisites

  • You need to know how to login to the OBi100 -  I explain how:  HERE.
  • The OBi100 has not been previously locked-down by a VSP (VoIP Service Provider).
  • The OBi100 is not linked to OBiTalk Portal via "Add Device" method on OBiTalk website.
  • Make sure the OBi100 is Ethernet connected to a LAN port on your NAT-Router.
  • Your NAT-Router must be set to issue DHCP IP addresses to LAN connected devices.
  • Your NAT-Router must not be blocking "outbound" ports 5060, 5061, 6800, 5222, 5223, 10000 to 11000, 16600 to 16998, or 19305.  (Most home routers do not usually block outbound traffic.)
  • You have an analog telephone plugged into the OBi100 Phone-1 port.
  • You know how to perform a Factory Reset (Reset Configuration to Defaults) - I explain how:  HERE.
  • Once you know how to perform a Factory Reset, I recommend that you do so, before proceeding.   (This is an important step to be sure that what works for me will work for you, too.)
  • Your OBi100 is running the latest Firmware version.  If not, I explain how to check/update:  HERE.
  • Your OBi100 is powered-up and ready to be configured.
  • If you like, you can test that your OBi100 is working properly by placing an ECHO TEST call to the Obihai Echo Test Server, by dialing **9-222-222-222 from your telephone that is connected to the OBi100.  (The OBi100 can magically do this without any configuration changes from factory defaults.)
  • You have previously setup a Voip.ms account and have your SIP account login username and password handy.

    Note:  
    Voip.ms accounts generally consist of one "Main Account" plus as many Sub-Accounts that you setup for your VoIP device needs.  I personally configure numerous ATA's and IP-Phones using numerous Voip.ms sub-accounts.  I have created a new sub-account specifically for testing my OBi100 ATA with Voip.ms.


Now that we have all the assumptions and prerequisites out of the way, what remains is only to configure the non-default essentials required to successfully login/register the OBi100 with your Voip.ms account.


So, lets get started

  • Login to the OBi100 configuration utility using your PC web browser.
  • Navigate to (click on) the ITSP Profile A menu option, located in the left-hand navigation column.
  • Click on "General" menu option (located under ITSP Profile A).
  • You can set the "Name" of this ITSP profile as "Voip.ms", if you like (optional).
  • Note that the Signaling Protocol, by default, will be:  SIP  (which is correct).

The OBi100 default Digit Map will only partially accommodate Voip.ms dialing needs.

This is the Default Digit Map already set in the OBi100:
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)

  • I'm recommending the following Digit Map for use with Voip.ms:
(*xxx.S2|**275*x.|911|4xxx|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)

You can copy and paste this complete text string into the "Digit Map" text box in the ITSP Profile A section as a replacement for the default OBi100 digit map. (Don't forget to uncheck the "Default" check-box first.)

Note:
While, you can make regular phone calls using the Default Digit Map, the recommended Voip.ms digit map will enable additional dialing options such as checking Voice Mail, sending *xx vertical service commands, 911, and access to the SIP Broker peering network. 
(911 must be enabled via your Voip.ms user account dashboard, before it will work).


  • Once you have finished the above edits, click the Submit button at the bottom of the ITSP Profile A window.
  • When a pop-up dialog window appears, click the OK button to proceed;  otherwise Cancel to abort.

  • You will then be greeted with the Configuration Update Successful screen.

    Once you have clicked OK above, you could reboot.  However, the previous submission will temporarily be saved until we finish making more changes, and then we will Reboot.

  • Next, click on the SIP menu item, listed under ITSP Profile A.

  • Next, we will be editing two VoIP proxy/registrar server settings, as illustrated  below.

While in ITSP Profile ASIP settings window, edit the following fields with city.voip.ms as the Proxy and Registrar server: 
  • Proxy Server:                toronto.voip.ms      (choose one of 13 server cities)
  • Registrar Server:          toronto.voip.ms      (should match Proxy Server selected)
Note:
I'm using the Seattle server.  Users of Voip.ms will typically be selecting a proxy server nearest their own location, or which ever one provides the lowest ping route latency.  While I'm located in British Columbia, Canada, I could be using the Toronto server.  But, I get much lower latency by connecting via the Seattle servers. (However, I do wish Voip.ms could commission a Vancouver, BC server.)

When finished editing the SIP page, click the SUBMIT Button before proceeding to the next step.




After submitting Submit, you will again be greeted with the Update Successful window.
You do not need to reboot, just yet.  We will do that when finished with all our configuration changes, later.

  • Next, click on Voice Services menu item in the left navigation window pane.
  • Then, click on SP1 Service menu item, located directly under Voice Services menu.

  • Locate the SIP Credentials section located in the middle of the SP1 Service page.
  • In the text box labeled AuthUserName, enter your Voip.ms Account number, or Sub-Account number.  (I have numerous Voip.ms "sub-accounts" under my one main account.  If you have multiple SIP devices, each device, or line, can be configured via a different sub-account under your main account.  This is a great feature I have used extensively for years.
  • In the text box labeled AuthPassword, enter your Voip.ms account/sub-account SIP password.   (Passwords must be a minimum of  6 characters)
  • Scroll down to the bottom portion of  the page.
  • If you have setup and enabled Voice Mail with your Voip.ms account,  Enable Voice Mail Waiting Notification by clicking the following check-boxes:

    MWIEnable               (checked)
    X_VMWIEnable       (checked) 
    MessageWaiting
           (checked)
  • When finished editing, scroll to the bottom of the page and click the Submit button.
  • Click on the OK button to proceed with submitting the changes:

  • Once again, you will be greeted with the Configuration Update Successful window screen.
  • This is the final step to complete our quick and easy OBi100 configuration settings for service with Voip.ms:   Click the REBOOT button located in the window upper-right corner.


Rebooting your OBi100 only takes about 15 seconds.

That's it, we are done!

------------------
While, there is a mind boggling array of potentially editable configuration parameters within the OBi100, we only needed to configure five (5) essential non-default parameters to enable the ATA to make successful VoIP based phone calls via your Voip.ms SIP VoIP account.
------------------

Obviously, there are numerous additional settings for tweaking the configuration and performance of your ATA.  But, configuring and enabling the bare bones basics was the theme of this article.   And, it's working for me.


Start Making Voip.ms Phone Calls
If you started with the OBi100 configuration default values, and only edited the five values and entries described in the above bullet points, you should have a dial tone and now be able to make outbound calls with your ATA using Voip.ms as the default VoIP provider.  Following, I provide some numbers for testing calls via Voip.ms using the OBi100.

All numbers listed below are Free Calls, via Voip.ms and your OBi100 ATA phone:
  • Test your OBiTalk network connection by calling OBi Echo Test server:  **9-222-222-222
  • Voip.ms Echo Test number:   4443
  • Voip.ms DTMF Test:   4747
    Once connected, press any digit on your phone and the service will "talk-back" the digit pressed.
  • Checks your Voip.ms calling credits balance:   *225
    This feature must explicitly be enabled for each sub-account used.  (Disabled, by default on sub-accounts.)
  • Call your Voip.ms Voice Mail box (if you enabled it via your Voip.ms dashboard):   *97
  • iNum network Echo Test:   011-883-5100-0000-0091#
  • iNum network Caller-ID Talk-Back:   011-883-5100-0000-0093#
  • SIP Broker peering network Test Announcement:    **1-**275*-0111-88888#
  • e911 activation validation Test:   1-555-555-0911
    This is not a 911 call.  It only checks the status of your e911 service activation with Voip.ms.

Notes:
  1. 1800 numbers may not be free via Voip.ms. You may need calling credits. (Depends on your Voip.ms account Toll Free Routing preferences settings.  ("Value" vs. "Premium" routing)
  2. Calling to PSTN landlines and mobiles in USA/Canada requires Voip.ms calling credits.
  3. With the procedures outlined in this article, you will still be able to make free OBI-to-OBi in-network    VoIP calls to other OBi ATA's.
  4. Voip.ms also provides for free in-network calling between all their account holders by dialing any other  account DID phone number, or SIP URI (via their Phone Book feature).  Or, directly dial one of your own sub-account extension numbers.
  5. If you populated your Voip.ms online Phone Book with phone numbers and SIP URI's for quick dialing, the OBi100 (as configured in this article) will not correctly interpret a *75xx phone book entry unless you first dial **1, then followed by the *75xx code (and, assuming you used my recommended Digit Map above).   i.e., dial :   **1*75xx
  6. e911 service is available with Voip.ms- but must be activated with a paid account.


I have now covered the bare-bones essentials of "manually" configuring your OBi100 ATA with Voip.ms and placing a few test calls.

Enjoy!


---------------------------------------------------------------------------
UPDATE:
(Dec. 30, 2013)

This update is for the benefit of Obi110 users.

I have received a few emails from Obi110 users who have tried to follow my Obi100 procedures to configure their Obi110 devices.  They tell me they receive a " No Service Configuration Error " when making a call.  One of my insightful readers tells me that he resolved the error issue by making the following configuration changes:

" Go into Physical Devices->PHONE and change the Primary Line from PTSN to SP1 Service.


 Hopefully, this update will help other Obi110 users, too.

P.S.
I do not have or use the Obi110 myself and thus cannot provide any further information on Obi110 configuration issues.