Freephoneline VoIP Unlock Key Credentials

The Freephoneline VoIP Unlock Key provides sip credentials that can be used to configure any SIP client to work with the Freephoneline service. Please review the following Freephoneline guidelines to set up your SIP client. Failure to follow the required guidelines will result in account suspension followed by a notification email. Once your configuration adheres to the guidelines, service will be restored.
These guidelines may change over time - if and when they are changed freephoneline users will be notified at the email address used for account login a minimum of 7 days prior to the changes being required. Please ensure your contact information is accurate by visiting your account profile on freephoneline.ca.

Grandstream HT502 Setting for Freephoneline

Before you start configuring the adapter, make sure you have the following settings for your SIP account:

- SIP Server address (sometimes called SIP Proxy)
- SIP User ID (in most cases this is the phone number)
- The password for the SIP account
To obtain these settings, you must contact Freephoneline and ask for your configuration file. There's a one time charge for this, currently $50 CAD + tax. They will send you a Word document with the settings.

Connect all the cables: power cord, an ethernet cable from your router (or modem) to the WAN port of the HT502, an ethernet cable from the LAN port to your PC and a phone to the Phone 1 port. Open a web browser and type in http://192.168.2.1. The login page will come up, enter admin to log in then click Advanced Settings:

Freephoneline.ca Config Info: Obihai OBi-110 ATA

I read the on-line reviews of the Obihai OBi-110 and its smaller sibling, the OBi-100, and decided to test an OBi-110 in conjunction with FPL.

The first challenge: if you purchase the OBi-110 or OBi-100 from Amazon.com (.com not .ca) it won't get shipped to Canada. Don't know why -- and don't really care except it involves one more step. Have the device shipped to a friend / relative in the good ol' US of A and then have it transshipped via UPS. It adds about $28 to the price -- but I believe in the long run it'll be well worth it.

STEP 1:
I presume you can read the instructions which come with the OBi-110 / OBi-100 about what plugs in where.
However, to summarize (I purchased an OBi-110 so I'll use this going forward; the OBi-100 is identical for purposes of these instructions):
#1. Plug in the supplied RJ-45 cable to the OBi-110 and plug the other end of the cable into your router. I have a D-Link DIR-615 with 4 wired ports of which 2 were free. The other two router ports have D-Link Gigabit Ethernet DGS-1008D switches / hubs attached.
#2. Plug the supplied telephone cable into the PHONE jack on the OBi-110 and the other end into your telephone handset
#3. If your router is set up for DHCP as soon as you connect the power (standard 12 V adapter) the device should receive an IP address
#4. Check that the POWER and PHONE LEDs are SOLID GREEN, and that the ACTIVITY LED flickers periodically
#5. Perform an echo test of the Obihai unit (using the OBiTALK network) by dialing **9-222-222-222
Alternatively you can make a test call by dialing **9-333-333-333 followed by the outgoing number

VoIP DMZ - SIP war-dialers - SOHO routers

Regarding SIP war-dialers (and I am getting dinged every frickin' night because I had made the mistake of NATing ports inbound for a single day):

(1) I think we can all agree that the use of a "DMZ" with these SOHO routers (e.g. Linksys or D-Link, and these are not real firewalls) should be limited to testing purposes only, such as to validate whether or not certain ports need to be open, or if they appear to be not open. It's akin to allowing "any port / any source" from the Internet. Best practice is to prohibit ALL inbound traffic from the Internet, except that which is expressly required.

(2) A firewall will generally NOT help you if you are allowing and NATing inbound traffic to your ATA. Forwarding purpose-specific ports inbound, will eliminate most firewalls from usefulness, because even application and protocol-aware firewalls will only deep dive the packets for RFC compliance and specifically-defined attack signatures. If the war-dialer's script is making use of the SIP protocol, a SOHO-class firewall offers little protection. You can impose little tricks by getting your listening service to use non-standard TCP/UDP ports - but this bites you in the ***** if legitimate traffic is trying to communicate with you on standard registered "well-known" ports associated with the listening service. For example, if you change your public-facing web server's listening ports to non-standard ports (e.g. ports other than TCP 80 and TCP 443), your site will likely not get the traffic it expects because the users' browsers are configured to hit web sites using their standard ports. If you somehow communicate to you your users that your web server is listening on non-standard ports (e.g. TCP 81 or TCP 444 for SSL), your users would have to manually suffix his URI with the port number to manually override the use of the standard ports (e.g. http://example.com:81 or https://example.com:444). As far as I can tell, there is no realistic way of communicating something like this to all users and all providers with VoIP.

Google Voice OBi202 | OBi100 | OBi110

Use Google Voice™ on your regular phone and make calls to the USA & Canada for FREE !! *

Make calls to other countries with Google Voice's incredibly low international rates using an OBi202, OBi100 or OBi110 and your broadband connection to the Internet.

Sprint™ Customers: Check Out the Amazing Benefits You'll Get with an OBi