Wednesday, 27 July 2016

Manually Configure Voip.ms In Obihai OBi200

In this article, I will walk you through the basics of how to configure your Obihai OBi200 directly with Voip.ms, a well known BYOD DIY VoIP Service Provider based out of Montreal, Canada with another office in Merida, Mexico.  Voip.ms has dispersed regional VoIP Proxy Servers throughout Canada, the USA, Europe, and even Australia,   I myself had been using Voip.ms for many years.  My only dissatisfaction with their service is that they don't provide DID phone numbers for my area in Kelowna, BC.

The OBi200 is a feature-rich Voice Bridge/VoIP Analog Telephone Adapter (ATA) capable of simultaneously registering with up to 4 VoIP service providers, plus the OBiTalk proprietary network.  So in essence, the OBi200 is capable of making and receiving phone calls via any of 5 VoIP service networks from this one tiny little box (2.9" x 2.9").  

While only equipped with a single FXS RJ-11 analog telephone jack, the OBi200 is capable of directing all inbound calls from any of the 4 configured ITSP VoIP services (and the OBiTalk network) to the one single FXS phone jack.  As well, it can also make outbound calls via the same set of 4 configured VoIP service providers and OBiTalk network via the same FXS phone jack.  The OBi200 has many more talents for which I don't have space to cover at this time.

In this article, I am only focusing on the very fundamental basics of "manually" configuring a single VoIP service  provider (Voip.ms) into the ATA using ITSP-A and SP1 as the voice service pair.  I will start with the factory default settings and then only add, edit, or modify the most essential required setting parameters to successfully achieve reliable SIP registration with Voip.ms.

Once successfully "manually" configured and registered with Voip.ms, you will then be able to make and receive VoIP calls via your Voip.ms account on your OBi200,

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 all 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 reliable service registration with the Voip.ms servers.


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

Please remember, the premise of all my tutorials are to allow you to locally and manually configure your ATA without any interaction with 3rd party control - which is how I configure all my VoIP devices.


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



Trying to manually configure the OBi200 may at first appear to be a daunting task (which it can be for someone not familiar with it's configuration settings and layout).  After all, there are over 1,000 configurable settings inside the OBi200...


The good news is that the OBi200 ATA can be manually 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, a few assumptions must be made and prerequisites met:

Assumptions and Prerequisites
  • You need to know how to login to the OBi200 -  I explain how:  HERE.
  • The OBi200 has not previously been "locked-down" by a VSP (VoIP Service Provider).
  • The OBi200 is not linked to OBiTalk Dashboard portal via "Add Device" method on OBiTalk website.
  • Make sure the OBi200 is Ethernet connected to a LAN port on your NAT-Router/switch.
  • Your NAT-Router must be set to issue DHCP IP addresses to LAN connected devices.
  • You should have an analog telephone plugged into the OBi200 Phone 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 with my configuration directions.   (This is an important step to be sure that what works for me will also work for you, too.)
  • Your OBi200 is running the latest Firmware version.  Don't know?   I explain how to check/update:  HERE.
  • Your OBi200 is powered-up and ready to be configured.
  • If you like, you can test that your OBi200 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 OBi200 Phone port.  (The OBi200 can magically make this call over the OBiTalk network without any configuration changes from the factory defaults.  :)
  • You have previously setup a Voip.ms account and have your SIP account login username and password credentials handy.
    (You can use your Voip.ms "Main Account" credentials, or any of your Voip.ms "extension" sub-account credentials setup for specific use with your OBi200 connections).

Now that all the assumptions and prerequisites out of the way, we are all set.



So, lets get started

  • Login to the OBi200 configuration utility using your PC web browser.
  • Navigate to (click on) the "Service Providers" menu option.
  • Click on ITSP Profile A menu option.
  • Click on "General" menu option (located just below ITSP Profile A).
  • You can set the "Name" of this ITSP A profile as "Voip.ms", if you like (optional).
    (Uncheck the Default checkbox to make changes)

I'm recommending the following Digit Map for most people using Voip.ms:


(*xx|*xxx|*75xx|4xxx|[34589]11|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 OBi200 digit map.  (Delete/erase the entire default digit map before pasting the new digit map.)  
(You must uncheck the "Default" check-box first before editing.)

Note:
While you can make regular phone calls using the Default Digit Map, my recommended Voip.ms digit map will enable additional dialing options such as checking your Voip.ms Voice Mail (*97); 311,411,511,811, or 911; and the Voip.ms *75xx based quick dial phone book. (911 service must be purchased and enabled via your Voip.ms user account dashboard in order to have 911 access).




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

  • 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 be temporarily saved until we finish making more changes, and then we will Reboot.
    In the meantime, you will see the gold colored "Reboot Required" icon in the upper-right corner of config windows, reminding you that changes won't take full effect until you eventually do reboot.
  • Next, on the left side of the window,  click on the SIP menu item, listed under ITSP Profile A.


  • Now, we will be editing the VoIP proxy server settings in the SIP section of ITSP Profile A:




While in ITSP Profile ASIP settings window, edit the following fields:
  • Proxy Server:                 city.voip.ms  (see list of servers below)
  • Registrar Server:           city.voip.ms  (Must be same name as Proxy Server Name.)
  • Set Registration Period to:               360 (seconds) (i.e. every 6 minutes) 
  • Set Registration Expires value to:    360 (seconds)

Below is a list of available Voip.ms proxy servers at the time of this article:


I use Vancouver server because of its super low latency of 17ms from my location in the Okanagan Valley, BC, Canada.


When finished editing the SIP page, scroll to the bottom and then click the SUBMIT Button before proceeding to the next page.






After clicking 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.



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

  • For reference purposes, note that the parameter:  X_ServProvProfile is defaulted to value = AWe will not be changing this setting.  At this time, we want SP1 to be paired with ITSP-A;  so no change is currently required.


  • Enable:  X_KeepAliveEnable  by un-checking its  Default box and then checking its Value box to Enable it.
    This setting should help ensure that your NAT-Router SIP ports don't time-out in between the periodic server registrations, and thus allows the SIP ports to remain open for incoming calls through Voip.ms servers at all times.

  • For reference purposes, note that the parameter:  X_UserAgentPort is defaulted to Value =  5060.   This is the default and standard VoIP SIP port used by most VoIP User Agents (i.e. your ATA or IP-Phone).  If you have conflicts with other VoIP devices on your network, SIP ALG conflicts, or prefer to use a non-standard port, this is an option you that can alter as required, or desired.  You can change this value, but is not usually required (depending on circumstances).

  • 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 (Main Account), or the Sub-Account Number_Name that you created in your Voip.ms dashboard for the OBi200 to use.


  • In the text box labeled AuthPassword, enter your Voip.ms Main Account SIP password, or the SIP Password you created in your Voip.ms dashboard for the Sub-Account you created in your Voip.ms dashboard for the OBi200 to use.

  • Enable:  X_EnforceRequestUserID  by check-marking its Value check box.

  • In the Calling Features section, you can Enable and insert your personal Caller ID Name.  This is an optional setting.


And finally, you can enable Mail Waiting Notifications for your Voip.ms account (assuming you have enabled Voice Mail within your Voip.ms VoIP service account).
  • Enable:  MWIEnable
  • Enable:  X_VMWIEnable
    • When finished editing this page, scroll to the bottom of the page and click the Submit button.


    • Then, 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 OBi200 configuration settings for service with Voip.ms:   Click the REBOOT button located in the window upper-right corner:




    Rebooting your OBi200 only takes about 15-20 seconds.

    If you made all the above required edit changes correctly, your OBi200 Phone port LED should now be On and GREEN.  (Actually, all three LED's should be GREEN.)   When the Phone port LED is green, this means you have successful service registration with Voip.ms.

    If the Phone port is not GREEN (not lit), then take this opportunity to review all settings that we changed earlier for correct values.



    Start Making Voip.ms Telephone Calls

    If you started with the OBi200 configuration default values, and only changed the values and entries described in the above bullet points, you should now have SIP registration and be able to make and receive phone calls with your OBi200 using Voip.ms as your default VoIP service provider.  Following, I provide some numbers for testing calls via Voip.ms using the OBi200.


    All numbers listed below are Free Calls, via Voip.ms and your OBi200 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 you 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.)
    • Voip.ms Voice Mail box   *97     (if you enabled it via your Voip.ms dashboard)
    • iNum network Echo Test:   011-883-5100-0000-0091#
    • iNum network Caller-ID Talk-Back:   011-883-5100-0000-0093#       (If you acquired a Voip.ms iNum number (free), this test may talk back only the iNum you have - even if you have another DID enabled)
    • 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.) (It will talk-back the caller-id of your Voip.ms enabled e911 DID phone number)

    Notes:
    1. Calling to 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 phone numbers 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 your Voip.ms Phone Book feature).  Or, directly dial one of your own sub-account extension numbers for free. (e.g.:  dial 101# )
    5. If you populated your Voip.ms online Phone Book with phone numbers and SIP URI's for quick dialing, the OBi200 (as configured in this article) may 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.

    That's it, we are done!


    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.   It's working for me.  I hope it works as well for you, too!

    Enjoy!

    Jeff - VoipDIY