Voip over WAN?

[terpjj]

I am using Bell Turbo Hub because I live in the country, and I'm trying to get my Thomson TG784 connected so I can use Voip, any ideas on how to do this?

[dibsmft]

From a quick read it looks as if you should be able to connect the TG784 OK. Yo do have the manual I suppose?
http://www.technicolorbroadbandpartner. ... hp?id=6986
There seems to be a good deal of info there.

[bridonca]

I suppose it would be too easy to just plug in the ATA to the TG784 and have it just work? I have no experience with the Bell Turbo Hub, but SIP VOIP over 3G can be hit and miss. If you do try it, let us know. And to increase your chances of success, stay away from Sipura/Cisco/Linksys products, because they are really awful when it comes to wonky configurations. Best bet is to go with Grandstream.

I would go with free first, and see how that goes. Get the freephoneline softphone, and run that on your computer, or Dell voice for the Android or Iphone. If it works, you might want to spens money on an ATA, and get some SIP settings.

[bridonca]

I think I lost what you want to do. I mistakenly thought the TG784 was a Bell Turbo Hub, it is just a ASDL modem. Could I get another explanation on what you actually want to do, and how does the TG784 fit into it? Do you want to try on the VOIP on the TG784 at home, and then use it on the Bell Turbo Hub at the cottage?

[terpjj]

No, no, I'm using a bell turbo hub and trying to use my TG784 modem as a router so I can use the VOIP, but the problem I believe is that I need to get the latest up dates for the TG784 because I don't have a WAN option when I try to configure it, I've contacted FPL and they sent me to a web site thomson-broadband.com, and have been waiting for a reply now for a week on how to get this up date, because there is no update on their site. SOmething for free is not always good

[dibsmft]

I have to admit that I am confused about what your system really is. Doesn't the Thomson TG784 have built in Voip so what is the Thomson7A3146. Does your normal PSTN line work through the TG784? Can you use a standard voip line that gives more assistance with SIP transport such a getonsip.com or sip2sip.com?

[TheHardy]

SOmething for free is not always good

??????

If the problem is the software/firmware on your router, as you described, then how is the service/support from Fongo to blame in anything here? I am really honestly confused now.

You cannot expect a VOIP provider to have upgrades for your router!!

That would be like me getting mad at my local grocer when my refrigerator at home is empty!

Or have I misunderstood not only what you are trying to do, but who you are trying to hold accountable for it not working the way you want it to?

[Jake]

It could be that he bought the TG784 from Fongo. I have 2 accounts signed up for the DSL and they gave me a 784 each time. It could be argued that Fongo should support it a bit if they supplied it.

Anyway - have you tried plugging a network cable from the turbo hub into one of the 784 network ports, then shutting off the DCHP in case it messes with stuff? (http://192.168.1.254/cgi/b/intfs/_intf_ ... calNetwork)
This should make the 784 act more like a switch rather than a router - which I am not sure you really want anyway. Isn't the turbo hub a router already? Throwing another router into the mix is probably going to confuse things.

[terpjj]

Wow, some of you are confused, now where is it mentioned that there is a Thomson7A3146 router? No where................and also the TG784 was bought from FPL before they changed the name to "Fongo" which is all owned by Fibernetics, Ok? All good now?
And who says I'm "BLAMMING" anyone?

So now, I guess the question is, as it was in my last reply, where would I get the update foe the TG784?

As to Jake.....How is running a net work cable from the Bell hub (which is a router) to the TG784 network port going to work, Network ports are out going not incoming, this is where the WAN port needs to be configured, the WAN port is the only way for the Bell hub to recognize the TG784.

Thanks for all who have replied in trying to help me out.

[FONGO_mike]

If i am not mistaken, you will need to set up the modem in "Voice" mode and then go to telephony to set up the VoIP line through the modem. Once done, and the port selected (green plugs on back of modem) you simply need to plug your phone into the modem.

You shouldn't need to change the firmware on the device in order to do this.

[Jake]

Wow, some of you are confused, now where is it mentioned that there is a Thomson7A3146 router? No where................and also the TG784 was bought from FPL before they changed the name to "Fongo" which is all owned by Fibernetics, Ok? All good now?
And who says I'm "BLAMMING" anyone?

So now, I guess the question is, as it was in my last reply, where would I get the update foe the TG784?

As to Jake.....How is running a net work cable from the Bell hub (which is a router) to the TG784 network port going to work, Network ports are out going not incoming, this is where the WAN port needs to be configured, the WAN port is the only way for the Bell hub to recognize the TG784.

Thanks for all who have replied in trying to help me out.

Did you look at this page? http://www.speedtouch.ca/firmware.php I don't know what version you have, but this has v8.2.7.7 which is later than my version. It has the tool and instructions at the top. The firmware for the 784 is a bit down the page.

Did you try plugging in the TG784 as I suggested? I have done this with routers in the past and it has made them work as a switch. Surely a network port is bidirectional - it has to allow data to travel both ways, no? I will back this up by saying I have had no formal network training what so ever so it might be all rubbish! Turning off the DCHP server as I suggested also would help. Also make sure you set up the IP of the TG784 as something on the IP range of the DCHP server on your turbo hub so you can access it later.

Maybe I am just too used to cobbling things together and this sort of thing is not proper network protocol

[TheHardy]

Terpjj: I count myself as not too confused, just needed to try to sort out what it was you were after.

Jake seems to have nailed it down fairly well in his last post, and like him, I have no formal training either. His "cobbled together" has all the elements of something that should work--- you should never have two things doing DCHP on the same network -- it rather mucks things up (or in Jake's case, tosses a spanner into it! ) Other than that, all I can do is +1 Jake's attempt to assist you until we here back as to other factors, errors or failures with that attempt.

[dibsmft]

The reference to "SIP Device Name: Thomson7A3146" comes from the info under the terpjj user information of the right of the page. According to the manual the TG784 has built in Voip so the question is whether or not it is being used (several small phone line sockets on the back). Built in voip can sometime give problems both when used directly and when ignored and a separate ATA is used. Having several devices doing DHCP does not help but works perfectly well and works OK with voip (I have used it) but it is best avoided it you can. What we lack is enough detail about the service and configuration that terpjj has to help very much.

[TheHardy]

dibsmft: fair that, one reason why I have not waded in heavily.

As for multi DHCP servers, unless things are hardwired in via cables, you will experience all kinds of nasty results for things getting addresses they should not. Wired will always draw from the pool server it is connected to (or closes to in # of hops) unless you force it to look somewhere. But this is all a huge PITA that can easily be avoided by just making sure you have only one machine acting as the Addressing Czar .....

[dibsmft]

dibsmft: fair that, one reason why I have not waded in heavily.

As for multi DHCP servers, unless things are hardwired in via cables, you will experience all kinds of nasty results for things getting addresses they should not. Wired will always draw from the pool server it is connected to (or closes to in # of hops) unless you force it to look somewhere. But this is all a huge PITA that can easily be avoided by just making sure you have only one machine acting as the Addressing Czar .....

True, but it you happen to want/need two separate networks there is really no problem if, as you say, they are hard wired.

[Bloodsong]

Before anything else is said here, I must state what you mean for this topic to say is "VoIP over WWAN" Note the second W (Wireless Wide Area Network) as (generally speaking) ALL internet connections are WAN based.

Next I will mention that I scanned through the previous messages and saw a lot of confusion as to what equipment and what set-up is being attempted. I will attempt to address everything below, though I'm likely to have information that is completely irrelevant. I would like to say however that my first four points always apply.

Now I'll start by saying this:
#1) Yes it is absolutely possible to have (relatively) decent call quality over WWAN, I used to do this with a tethered Palm Treo 700p when I had an unlimited data package as part of the Telus student plan, I never should have gotten rid of that cell (Today I own no cell as my last 3 employers have supplied me with one.)

#2) Wireless networks, whether they are cellular or PTP (Point to Point) have a series of engineering based obstacles to overcome and I have seen everything except a well engineered wireless network so far when it comes to internet connectivity, but I have not done much hands-on research with 3g/4g hubs aside from configuring them for access.

#3) In every scenario I have seen you will almost certainly need to use a STUN server at the very least, if not a more direct way of controlling your external access (VPN or SSH Tunneling ) as VPNs and Tunneling can add additional latency we should try to avoid this.

#4) VoIP is a touchy protocol at best, and modem/router combos tend to be terrible, where-ever possible disable the routing functions of a modem/router combo and place proper routing equipment into the circuit, preferably either something with WRT based firmware, or a small office router (m0n0wall, pfSense, or commercial fortinet) style equipment... though my experiences with fortinet have been tainted by my introduction to them.

#4.a) With the suggested routing equipment it is easy to physically and virtually segregate your network if this is required through the use of VLANs and port assignments.

#5) DHCP can be a tricky mistress AND it is important to remember that DHCP runs a (small) amount of constant over-head to your network. If your network is small enough to run off static IPs do so. If you frequently have guests or wireless devices consider reducing the size of your DHCP pool and making wired systems (Including routing and VoIP equipment) static.

#5.a) Depending upon your routing equipment you can have multiple DHCP pools that run over different mediums (Sorted by VLAN/Ethernet ports, Sorted by WLAN Interface and Sub interface. Each wireless LAN sub-interface can have it's on SSID and DHCP pool)

6) When introducing a modem/router combo to be used for additional ports or functionality you are generally best to statically assign an IP in the same subnet as the primary modem/router combo (in this case the turbo hub), turn OFF the DHCP server on the second routing device (In this case the Thomson) and finally, Connect the secondary router (Thomson) to the Primary (Bell) on the Thomson's LAN ports and treat it as a SWITCHING device, ignore the fact that a WAN port exists on the Thomson altogether, and run one homogenous network on a single Class C private subnet.