What’s the new deal for ip calling?

Thursday, October 22nd, 2009

http://www.telbo.com
http://www.nonoh.net
http://www.voipraider.com
http://www.jumblo.com
http://www.voipzoom.com
http://www.12voip.com
http://www.smartvoip.com

All includes to China. includes a $1/m plan for North America.

Note:
**xxx reserves the right after a certain amount of calls to start charging the default rate. are available for users with .

If you want to a home that can make and receive calls, follow these steps.

1.you can get a or . For , is recommended. If you are using an , you need a regular to connect to the .

Note: phones and adapters are connected to / using directly, not connected to computer using USB cable or line.

2. Get a nonoh.net account for 10EUR/4mon.

3. Set up the nonoh account on the ip or .

4.Get a US number () at .com. New York is not available at . Choose one you like. number is your nonoh user name. Proxy is .nonoh.net.

Basically, now you have a home with that you can receive calls and make calls, even to China.

5. (optional) Get a local number from .com/voice. Forward the number to your number.

If you just need a home that can receive calls, in step 2 above, get an account from Gizmo5.com. Then get a voice account that can be forwarded to your account. With , you can make toll-.

Sphere: Related Content

Inbound Calls Directly to your LinkSys or Sipura

Tuesday, January 20th, 2009

OP

How to accept direct calls to your / , bypassing all providers.
  • Does your registered provider not allow URI calls?
  • Do you want to cut down on latency/echo, by bypassing your provider on calls?
  • Do you simply like the idea of allowing calls directly into your ?

If you said yes to any of the above, then this FAQ page may be for you. Here is a description of how to let your / model accept calls directly from a URI ( address), bypassing all providers in the process. Here’s how to do it:

  • Setup your for use behind a NAT
    • Setup STUN on your (NOTE: STUN settings are on the tab)
      • Handle VIA received: no
      • Handle VIA rport: no
      • Insert VIA received: no
      • Insert VIA rport: no
      • Substitute VIA Addr: yes
      • Send Resp To Src Port: yes
      • STUN Enable: yes
      • STUN Test Enable: no
      • STUN Server: stun.voxalot.com.au:3478
        • NOTE: You can replace the above STUN server with any STUN server you like…
      • EXT IP:
        • NOTE: Leave this setting blank, STUN will figure this out for you…
      • EXT RTP Port Min:
        • NOTE: Normally you can leave this blank, but you can set this if you have a specific need
      • NAT Keep Alive Intvl: 45
        • NOTE: Use an value SHORTER than the “timeout” value in your .
    • set “NAT Mapping Enable: yes
  • Set “Ans Without Reg: yes” on your settings
  • Make sure your is on the default port
    • i.e. “ Port: 5060
  • Make sure that SOMETHING is set for “User ID:”
    • NOTE: If your is “registered” with a provider, this will be your real “User ID”
  • Make sure NOTHING is in “Outbound Proxy:” field on your
    • NOTE: This field is not normally needed if/when you have STUN setup (as above)
  • Forward UDP port 5060 to your
    • NOTE: This may be easier if you use a static LAN address for your
  • Set up a “dynamic DNS” service for your LAN
    • NOTE: The service from “no-ip.com” works fine for this

If all of the above is setup correctly, then anyone on the can directly your / by :userid@dyamic_dns_address”. For example, if your userid is “12345″, and your dynamic DNS entry is “myaddress.no-ip.com”, then your URI is “:12345@myaddress.no-ip.com”.

NOTE: One useful purpose of this, is to point a http://ipkall.com number to your . You do this by logging into your IPKall account, and filling in your “UserID” info (12345 in this example) for “ Number:” and your dynamic DNS entry (myaddress.no-ip.com in this example) for the “ Proxy:” field. After saving these changes (and waiting the necessary hour for them to take effect), then your number will directly ring your (bypassing any service provider, including “ World Dialup”).

NOTE (added 2/7/2006):
Another poster mentioned that he needed to set “NAT Keep Alive Enable: yes“, or he got 1-way audio with his . So if you are having problems with this trick (and you are not already telling your to send “keep alive” packets), try turning the “NAT Keep Alive” setting on…

NOTE (added 2/7/2006):
After using this “trick” for some time, I have discovered that (while this often works very well), a minority of providers just don’t like this setup.

The problem (when you run into a provider that just won’t forward directly to your , even though they do support URI forwarding) appears to be with the details of the “dynamic DNS” service. The problem is, there are actually two DIFFERENT types of DNS records often used by proxies (which is what you are having your pretend to be, by this trick). DNS “A” records are the “normal type” of DNS entries (the type we use all the time, for example when visiting web sites), and also the type most dynamic DNS services (including the http://www.no-ip.com service I use) offer. However, apparently there is also a special DNS “SRV” type record that some proxies use just for . And if your provider is using a picky enough proxy, they will be unable to forward directly to your , because they won’t find a “SRV” record for your “proxy address” (even though your dynamic DNS service will have a “A” record for your IP). While most proxies either don’t use SRV records or will happily use an “A” record if an SRV record isn’t present, some proxies are just “too picky” about this little detail (and will therefore fail to forward directly to your UNLESS you have DNS “SRV” record for your IP address).

Happily there is an easy “work around”, if you already have your ’s registered slots “full”, and you want to add a service that has this “issue” (i.e. is picky about the SRV records). What I found works well (when you run into this problem), was to register for a SIP Broker alias that points directly to my (via my dynamic DNS address). I then tell any service that has a problem with forwarding directly to my , to instead forward to *0111xxxxxxx@sipbroker.com (where xxxxxxx is my SIP Broker alias ). This seems to work well as a “work around”, because “sipbroker.com” appears to have the DNS “SRV” record that some proxies “need” and Broker can forward to a location identified just by a DNS “A” record. So the essentially gets forwarded to Broker, which forwards the onto my in that case. While this isn’t quite as nice as going directly to your , it is still an effective “work around” for when the proxy just refuses to forward directly to your /.

Of course, you might as well try the “forward directly to your ” address first, and only resort to the SIP Broker alias if/when the “direct” path doesn’t work (as your path will be slightly more reliable if the direct address works with your provider). And many places (including http://ipkall.com ) will happpily forward directly to your / without any problems. But for those places that just don’t like the DNS “A” records provided by dynamic DNS services, forwarding to Broker (and then letting Broker forward directly to your ) can be an effective “work around”.

Sphere: Related Content