I'm not a fan of the Sagemcom 5366 TN. I've had the thing for about a week on a new NBN connection, and have already had to power cycle it 3 times to reconnect to the NBN. I want it as close to gone from my network as possible, but because it must remain to provide VOIP services, the only option was to find a way to relegate it to a supporting role at best.
Unfortunately, because it is not possible to set a default gateway on the LAN interface, it does not appear to be possible to have it on the network behind another router.
However, after some messing around I've managed to get it working as a VOIP only device behind a WAN Router (in this case a Ubiquiti Universal Security Gateway (USG), but it would have also worked behind the ASUS RT68AU I have too).
NOTE: If you are going to to this, it is easier if all other devices are unplugged from the network. You can then gradually add devices back to the network after you have confirmed everything works.
Its only possible if you have a Sagemcom F@ST 3864 and the extraction method is different depending on the which variant you have.
If you have a 3864 you can search whirlpool and yescrowd for further detail.
"May I please know how you get the VoIP working without Sagemcom? I intend to use ASUS RT68U, which does not have phone port."
The VOIP is still on the Sagemcom. I've just moved it behind my WAN Router.
I have the v3 as well (black upright) and extracted the detail from this whirlpool thread I think. Unfortunately its not just a set of instructions but a full blown discussion so it will take a little effort to gleam the info you need.
Its been a few months since I did it so I don't remember the details off hand, but the main thing you need to do are:
* download the " dumpcfgdynamic" config file.
* find the <SIP> section in that config to get the SIP user ID (AuthUserName) and SIP password (AuthPassword) . These are unique to your service.
* find your SIP proxy (RegistrarServer) and SIP outbound proxy (OutboundProxy). These are not unique to you, but you should use these specific ones and not any other ones that may be in the thread.
* decode the SIP password using base64 decoder. I use this one as its off line so encoded/decoded password never leaves your computer.
Hope that helps. Sorry I can't be more specific, and I don't have the time to figure out the exact steps.
I'm having this problem also. Some devices never get an IP address assigned. Some get it once, but can't get it on re-connect. I've started to assign devices static IP addresses, which is a real pain.