Tuesday, 18 June 2013

Configuring Google Voice and Voip.ms on OBi100 - Manually


Today, I'll be talking about how to manually configure the OBi100 with two great VoIP services:  Google Voice and Voip.ms.

In past articles, I explained how to configure Google Voice or Voip.ms each  as a sole independently configured primary VoIP service on your OBi100.

Today, I'm going to show you how to combine the best of two worlds into one:  Google Voice as your primary default service, and Voip.ms as your number two VoIP provider..... both in one box... and both using just one analog telephone jack on the OBi100 ATA.

This will be another one of my in a "nutshell" series for the OBi100.  And, when I say in a nutshell, I mean the bare bones basics of getting started configuring two VoIP services into the OBi100 instead of just one, as I have presented in the past.  So, let's get started.

Assumptions and Prerequisites
In the past, I have made it a practice to outline a list of assumptions and prerequisites to ensure we are on the same page.  Because I have already covered most of this information previously, I'm going to ask that you review the following previously published articles while paying special attention to the list of assumptions and prerequisites outlined there:

Armed with all this previous knowledge,  I'm assuming your OBi100 is now connected, powered-up, and ready for configuration so that we can proceed with the quick and easy manual configuration of Google Voice and Voip.ms.

The Plan
Because we are configuring two separate VoIP services on the OBi100, we will first configure your default primary provider under ITSP Profile A and correspondingly under Voice Services as SP1.  For the purposes of this article, these first sections will be configured with Google Voice service.

Then, we will configure your secondary VoIP provider under ITSP Profile B and correspondingly under Voice Services SP2 , which will be configured for Voip.ms service.

Let's Begin

     
  • Click on the Service Providers menu option (left-window navigation pane)
  • Navigate to (click on) the ITSP Profile A menu option to expand its sub-menu list.
  • Click on "General" sub-menu option.
  • Set the Signaling Protocol to:  Google Voice  (first, "uncheck" the Default check box next to it)
  • Click the Submit button at the bottom of the ITSP Provile A - General window.
  • When greeted with the "Are you sure..." dialog box, click the OK button to proceed.
  • Next, click on Voice Services menu to expand its sub-menu list.
  • Click on the SP1 Service sub-menu item.
  • While in the SP1 Service window, find the section labeled SIP Credentials
  • Fill in the following VoIP service login authentication text boxes.  In this instance, it will be your Google Gmail login email address, and password (or, application specific password, if applicable).

    AuthUserName:     Your GMail, or Google Apps email address.
    AuthPassword:       Your Gmail, or Google Apps password (or, Application Specific PW).

Note:  If you have enabled 2-Step Verification in your Google account, you will need to generate and provide your Application Specific password  as the AuthPassword (specifically generate one for your OBi100 ATA).  I have done this, and it works for me.  (I'm also using the Google Apps version of Gmail/Google Voice, from within Canada).

  • When finished entering your credentials, click the Submit button at the bottom of the window.

    When the "Are you sure ..." dialog box pop's up, click its OK button to proceed.
  • At this point, we could re-boot the OBi100, but because we clicked the Submit button, all previous changes are now temporarily saved.  We will re-boot later after we finish configuring the Voip.ms settings.


  • Expand the Service Providers menu option (if not already expanded).
  • Click on the ITSP Profile B sub-menu option to expand its sub-menu list.
  • Click on "General" sub-menu option, under ITSP Profile B.
  • Observe that the Signaling Protocol is set to:  SIP  (as it should be, by default).
  • Just for your own reference purposes, you can fill in the "Name" field with "Voip.ms", or whatever you want to label this ITSP configuration profile.  (optional)
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)|[^*#]@@.)

  • Clear the existing default OBi100 Digit Map.  (First, un-check its associated default check box.)
  • Copy and past the above recommended digit map in place of the default digit map. 
  • Click the Submit button at the bottom of the window, before proceeding to the next step.
    When the "Are you sure ..." dialog box pop's up, click its OK button to proceed.
    (You do not need to reboot, just yet, until finished submitting all changes.)
  • Now, click on the SIP sub-menu item, also listed under ITSP Profile B.
    Here, you will be setting the Proxy and Registrar server values for Voip.ms.

While in ITSP Profile BSIP 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 above)

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 server values, scroll down to the bottom of the page and click the
    Submit button.   (However, do not reboot just yet)

    When the "Are you sure ..." dialog box pop's up, click its OK button to proceed.
  • Now, click on the Voice Services menu option, making sure its options list is expanded.
  • Next, click on SP2 Service sub-menu option.
  • Change the following PROFILE settings from A to B:
    X_ServProvProfile:     B
    X_RingProfile:             B
    X_CodecProfile:          
    B

  • Now, in the SIP Credentials section of SP2, set the following login values:

    AuthUserName:     xxxxxx_xxxx   (Your Voip.ms Main Account, or Sub-Account, Number)
    AuthPassword:        xxxxxxxxxx           (Your Voip.ms SIP password - minumum 6 characters)
  • Scroll down to the bottom portion of  SP2 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 (found under the "Calling Features" section)

    MWIEnable               (checked)
    X_VMWIEnable       (checked) 
    MessageWaiting
           (checked)

  • When finished editing, scroll to the bottom of the page and click the Submit button.
  • When the "Are you sure ..." dialog box pop's up, click its OK button to proceed.

Now, to finalize all setting changes, we are ready to Reboot the OBi100.

  • Click on the Reboot button at the top-right corner of the page window:


The OBi100 only takes about 20 seconds to reboot.

If all goes well, your OBi100 will now establish registration with both Google Voice and Voip.ms VoIP services.


Three VoIP Services  -  One Telephone
While we have now configured the OBi100 with two explicitly set VoIP providers (Google Voice and Voip.ms), we actually now have three independent VoIP services at out finger tips, in one box:

  1. SP1   Default Line, or  **1 )
    Google Voice - for free calling to any USA/Canada PSTN landline or mobile telephone numbers.  (Free at least until the end of 2013.... then we will see...)
  2. SP2    (**2)
    Voip.ms VoIP services - for free in-network calling to any other Voip.ms issued DID (phone number),Voip.ms account extension number;  free calling to +883 iNum numbers;  free SIP URI dialing to any VoIP network "peered" with Voip.ms (via Voip.ms online Phone Book feature);  free calling through SIP Broker federation of VoIP Peers;  and, of course calling to any USA/Canada and even world-wide PSTN and mobile phone numbers at a low VoIP termination rate.  Voip.ms can act as your USA/Canada e911 provider, too.
  3. OBiTalk Network   (**9)
    OBiTalk network - for free Obihai in-network calling between any world-wide  OBi devices.  No fees whatsoever.

    Line Selection and Call Routing
    So, with three VoIP services in one box, connected to a single analog telephone line, how do we differentiate between OBi-to-OBi calls, Google Voice calls, and Voip.ms VoIP calls?

    If you want to specify a specific line to place a call on, you will use the **x code to select the line and service provider to route the call to.

    Google Voice Calls  -  (**1) - Default Line - SP1 Line
    By default, SP1 is the default outgoing service line that will be used if you do not specify a **x code at the beginning of dialing a call.  Because we have configured Google Voice under the SP1 service provider, by default all outgoing calls will be routed through your Google Voice account.

    For example, if you explicitly dial a 10-digit number such as "800 466 4411" as a PSTN landline destination, by default this call will automatically be directed through your Google Voice account.  However, you could also get the same results by preceding the number with **1.  i.e.   **1 800 466 4411.


    Voip.ms Calls  -  **2   -   SP2 Line
    Because Voip.ms is currently configured with the SP2 line, you will need to consciously dial **2 at the beginning of all calls that you want routed through your Voip.ms account.

    For example, if I wanted to place and route my call to 800-466-4411 through Voip.ms, I would have to dial as follows:   **2-800-466-4411.

    800 number calls through Voip.ms are free, if not routed via their "Premium Routing" option.  But, if you do route via their Toll Free Premium Routing option, then you do pay a nominal per minute fee.  However, at least now you do have the discretionary option to pick and choose which service provider OBi100 uses to send PSTN calls to, depending on the cost of each route (i.e. Google Voice vs. Voip.ms.

    If you wanted to make free +883 iNum calls, you would then need to route those calls through your Voip.ms account (Google Voice no longer routes iNum numbers for free).  So, to route your iNum call through your Voip.ms line, you would dial as follows:
    For example:   **2-011-883-5100-0000-0091#

    Note:
    Because the Voip.ms recommended Digit Plan isn't fully optimized, it ,may be necessary to place the # key at the end of dialing iNum numbers.  (The same holds true for SIP Broker network dialing, too.)


    OBi-to-OBi In-Network Calls  -  **9   -  OBi Network
    If you want to route specific calls to your family, friends, associates, etc. who also have OBi ATA's connected, you will begin those calls with the **9 code, followed by the OBi ATA device 9-digit number you wish to call.  An example of this is when you dial the OBiTalk Echo Test server at:
    **9-222-222-222


    Making Test VoIP Calls
    The following is a list of numbers for making test calls.  Different numbers are optimized for routing through different VoIP networks.

    Via Google Voice:
    The following numbers can be dialed, as is, without the need to precede the call with the **1 code (default dialing).    All phone numbers listed below are Free Calls via your Google Voice account:
    (At least free through 2013...)

    Canadian Weather Lines:

    • Victoria, BC       wx:        250-363-6717
    • Calgary, AB       wx:        403-299-7878
    • Edmonton, AB    wx:       780-468-4940
    • Regina, SK         wx:       306-780-5744
    • Winnipeg, MB    wx        204-983-2050
    • Montreal, QC     wx:       514-283-4006

    Other Test Numbers:

    • National Research Council, Canada - Talking Clock:    613-745-1576

    NOTE on Google Chat Caller-ID associated with outbound calls:
    Because, here in Canada we cannot get a Google Voice inbound PSTN style DID phone number, you need to know that all your outbound Google Voice initiated calls will show a California Caller-ID as the Caller-ID associated with your outbound phone calls.  Currently, my outbound Google Voice calls are tagged as coming from:  Escondido, Ca - 1-760-705-8888.  
    Here is Google's online-help related confirmation on this Caller-ID number:  Here




    Via Voip.ms:
    All numbers routed below are preceded with **2 code:
    • Voip.ms Echo Test number:   4443
      Dialed as:  **24443
    • Call your Voip.ms Voice Mail box (if you enabled it via your Voip.ms dashboard):   *97
      Dialed as:  **2*97
    • iNum Network Echo Test:   011-883-5100-0000-0091#
      Dialed as:  
      **2011883510000000091#
    • SIP Broker peering network Test Announcement:    **275*-0111-88888#
      **2
      **275*011188888#

    Good luck with your OBi100 configured with Google Voice and Voip.ms VoIP services.


    P.S.
    Remember, everything I have presented here is based on local manual configuration of your OBi100.  For it to function as presented here, it is assumed that your OBi100 is not linked to the OBiTalk configuration and administration portal at www.obitalk.com.  Otherwise, the remote administration aspects of remote administration may overwrite any and all settings presented in this article.