Fritz!Box WLAN 7390 review

I finally got a AVM Fritz!Box WLAN 7390 modem/router to replace the Belgacom-provided BBOX-2, which gave me a few headaches and quite some frustration over the past year. I am happy to report that the Fritz works with Belgacom VDSL2, despite what Belgacom says about the mandatory use of their own broken modem.  Let’s get to the real meat. Some background first.

AVM, the company

AVM is the premier xDSL modem manufacturer in Germany. Besides the ones they sell under their own brand, they do quite a lot of OEM manufacturing for telcos:  1&1, Deutsche Telekom in Germany, P&T in Luxembourg and XS4ALL in the Netherlands. XS4ALL launched earlier this year a native IPv6 service for their residential customers based on the Fritz 7340 modem, a scaled down version of the 7390.

The Fritz 7390 was first announced at CEBIT 2009. It seems that AVM suffers from the “CEBIT announcement” syndrome. At the time, the 7390 was merely vapourware, in that the actual delivery only started nearly a year later in Germany. It took them also a lot of time to deliver a firmware that actually lived up to the promises. The international version was only delivered in september 2010. It was only last December 2010 that a firmware version was released that included “full support of IPv6″ (announced two years earlier) and compatibility with Belgacom’s VDSL2 network.

Yet, the AVM company is quite serious in implementing standards. For example, they are the only CPE manufacturer I know that attends RIPE meetings. The latest firmware implements DNSSEC in the local resolver, where most other CPE manufacturers could not care less.

The Fritz!Box 7390


As mentioned previously, the modem supports Belgacom’s VDSL2 network. At installation time, a wizard lets you select the right option according to your needs (Belgacom Internet or Belgacom Internet + TV).  Once you have added your PPoE credentials, the box is ready to go.
The real power of the Fritz are the thousands options that allow you to customize it to your needs.

Integrated telephony has been a powerful feature of the AVM boxes over the years. This one does it again, only better. It features a built-in DECT base station. You can also place VoIP phone calls directly from an iPhone or Android phone, and use the built-in phone directory. The PABX inside the Fritz will forward the calls through PSTN or a number of VoIP providers based on the rules you set.

The support for IPv6 was the main reason I bought this modem.  Here again, the Fritz 7390 delivers. It can use native IPv6 (in the unlikely case your ISP supports it) and tunnels (6to4, SixXS, and others).  Screenshot

WLAN can be both on the 2.4 Ghz and the 5 Ghz bands at the same time, with different SSIDs if you like. This may be helpful in an area with a crowded WLAN environment. It can do WIFI-N, up to 300 Mbps.  It makes a real difference. You can also setup a separate WLAN for the guests visiting your home, with a different SSID. Hence, you won’t have to give them the WPA2 password to your home LAN. Further, the guests will get access to the Internet, but not to the local LAN.

The Fritz can also serve as a NAS for the local network. There are two USB ports. You can attach a hard disk or a memory stick and make them available to the LAN and/or the Internet. The BBox-2 also has a USB port, but it was castrated by Belgacom. You could also attach a USB printer to the Fritz, and share it among the users. Some restrictions may apply in this case. Not all USB printers can be used this way.

Real life experience

A small gotcha to begin with: When setting up the modem for the first time, tell the setup wizard that you use an Annex-B line (aka ISDN), even if you are actually using an analog telephone line. It seems Belgacom uses Annex-B signalling for VDSL2, irrespective of the actual type of the line.

After using the Fritz!Box for two weeks, I am happy to see it is much more stable than the BBox-2. The random disconnects I experienced on the WIFI are not happenning with the Fritz.  The random reboots of the BBox-2 too, obviously.

IPv6 works fine. The SixXS tunnel I used in the beginning was stable. I have now switched to native dual stack IPv4/v6 through EDPNet. The Fritz uses router advertisements to allow IPv6 autoconfiguration. This works fine with Macs, Linux and  Windows boxes,  as well as Android phones. It can also announce DNS servers though RA (RFC 5006).

From firmware version  84.05.21 onwards, the Fritz offers a GUI interface to change both IPv4 and IPv6 DNS servers. This is a most welcome change from previous versions. Most ISPs’ DNS servers are broken in one way or another, like those of Belgacom, and many Belgian ISPs are now forced by law to do DNS blocking for sites considered illegal.

All in all, the AVM Fritz!Box WLAN 7390 is a highly recommended CPE, worth every eurocent you paid for.

In the meantime, the newer Fritz!Box 7490 has been released and is certified for use on the Proximus VDSL2 network. You may wish to check my review here.

(Updated 30 October 2014)

Leave a comment ?

177 Comments.

  1. Hi everyone,

    I contacted the AVM to know whether any firmware ” Belgacom” is published, and there is the answer: “As far as the AVM Support is informed no specicial Belgacom firmware for the FRITZ Box 7390 will! be released – at least not in the near future. “

    I find it absurd to have to change modem just because a company decides arbitrarily. I said that when the 7390 is connected to the Bbox 2 VoIP calls are sometimes interrupted.

    I plan to try a direct connection with the 7390, we’ll see …?

    Texte orginal :

    Bonsoir à tous,

    J’ai pris contact avec le support technique d’AVM afin de connaître si un éventuel firmware “compatible Belgacom” serait publié, voici la réponse : “As far as the AVM Support is informed no specicial Belgacom firmware for the FRITZ!Box 7390 will be released – at least not in the near future.” :sad:

    Je trouve aberrant de devoir changer de modem uniquement parce qu’une société en décide arbitrairement :twisted: . Je précise que lorsque la 7390 est branchée sur la Bbox 2, les communications VoIP sont parfois interrompues. :sad:

    J’envisage d’essayer une connexion directe avec la 7390, on verra … !? :?:

    • Hello,

      I have lots of problems with Belgacom BBOX and voip.
      We have VOIP phones both at the office, and at home.
      At the office, it stopped working reliably 6 months ago. All problems have to do with routing.
      To resolve issues, we have to reset modem and firewall several times a week.
      In order to solve this, I replaced the BBOX2 with a Zyxel modem, and it fixes the problems. However, now the DSL is squeezed … Ordered the 7360, will see if it then improves.

  2. Jonas Lonnroth

    FB 7390 now works with Telia Sonera adsl in Sweden. Since bridged encapsulation is used and the IP address is obtained with DHCP, no user name or password should be inserted. DSL ATM settings. VCI/VPI 8/35.

    Tick PPPoA/LCC. The router will then show that DHCP is used.

    Telia uses protocol RBC1483, LLC based VP8/VC35.

    The options shown by the FB are confusing since bridged encapsulation is not shown initially.

  3. Jonas Lonnroth

    PS Telia support pages say that I should not use PPPoE or PPPoA but Enet/Encap, routing, LLC based.
    However, this option is not present in the AVM manual account settings. The router that works with 05.51 uses automatic settings and I can’t find a way to see what is actually used.

  4. Jonas Lonnroth

    I am using one 7390 in Belgium on Belgacom VDSL and two in Sweden on 8 mbit/s adsl with ISP Teliasonera. 7390 works in Sweden with fw 05.51 but they won’t work when upgraded with fw 06.03 or 06.06. I reset to factory default and fill in adsl settings (same as in 05.51) manually. DSL sync works but I won’t get an IP address. The log says “PPPoE error. Timeout”

    I use the plan A setting which works with 05.51. I don’t have any TV on the adsl line. Telia VPI/VCI is 8/35. PPPoE. No VLAN as far as I know.

    IS there any known problem? Any tips for a work around?

    Jonas

  5. Hi everyone,

    Just a quick note to say that for me the passage to the multiplexer Broadcom is well. My connection from 50 Mbit/s to about 43 Mbits/s, nothing catastrophic so (-15%), which is not the catastrophe!
    —————————————————
    Bonsoir à tous,

    Juste un petit mot pour dire que pour moi le passage au multiplexeur Broadcom c’est bien déroulé. Ma connexion est passée de 50 Mbit/s à environ 43 Mbits/s, rien de catastrophique donc (-15%) ; ce n’est pas la catastrophe annoncée !
    http://www.hiboox.fr/go/images/informatique/vdsl1,008e95f8fd1132da080c59a6a9b480cc.jpg.html
    http://www.hiboox.fr/go/images/informatique/vdsl2,0ff7cececa4250e3d829a936395a7d90.png.html

    • Patrick Vande Walle

      Merci J-Marc pour cette info.
      D’après ce document (page 30), l’activation du vectoring se fait en 3 phases, à 15 jours d’intervalle.

      • 1. remplacement des cartes dans le ROP (vous l’avez eu).
      • 2. reconfiguration des ports en mode “vectoring friendly”: The lines equipped with modem with non-vector friendly firmware will get a fall-back line profile or a fall-back mode
      • 3. activation du vectoring.

      Dans 2 semaines, vous devriez donc voir votre vitesse chuter :-(

      • Dear Patrick,

        So far I am still connecting at 70Mb/6Mb. I did not upgrade to the newest vectoring firmware. What would your recommend?

        If I upgrade and then Belgacom sees my device as not on the white-list my connection will get worst, if I don’t upgrade will Belgacom reduce my connection also?

        Just a thought :).

        I would like to hear your opinion on this matter.

        Thanks,

        Johev

        • Patrick Vande Walle

          The upgrade of the Fritz Box is irrelevant.
          In any case, Belgacom will detect that you do not have a BBox-2, BBox-3 or Sagem. They will apply the repair profile.
          Your best bet for now is to buy a secondhand BBox-2, and configure it in bridge mode. They can be found for less than 30€

          • Thanks Patrick, even though I don’t like it, I will consider the option. I hope that harassing AVM and Belgacom on their Facebook pages will help us get our chip on the whitelist (call me optimist) :).

            Time will tell. By the way do you already have the new 7490? Can we expect a review of it?

            Thanks.

            Johev

            • Patrick Vande Walle

              I do not plan to buy a 7490 any time soon. I do not see any features that would justify the cost right now. If and when the 7490 gets allowed on the Belgacom network, I might change my mind.

          • I have a 7490 :smile:

            Main differences are:
            1) ROM flash is 512MB (in stead of 16MB for the 7390). The 16MB ROM is to small to allow new features in future Firmwares (reason why SMB support has been dropped in the latest 7390 Firmware).
            2) 2 * USB 3.0
            3) Wireless AC (1300 MBit/s)
            see: http://www.router-faq.de/index.php?id=routervg&hwf1=fbfonwlan7390&hwf2=fb7490

  6. Dear Patrick,

    It’s me again :). First of all I want to wish you and everyone coming here a Happy New Year.

    As for the question regarding our Fritzbox, I have seen that the latest Firmware was released, version 84.06.01. With many improvements, amongst them full vectoring support.

    Do you think it’s worth updating? Has anyone had any issues with it?

    I always get a bit couscous when updating firmware of a stable router, however if the new features justify it I normally go ahead.

    Would like to hear back from you on this topic.

    I wish you a good day.

    Regards,

    Johev

    • If you would like to update, just because of full vectoring support, then DON’T DO IT. The FritzBox 7390 – even with Full vectoring – will NOT be on the belgacom approved list.

      Another reason for not updating, is the support of SMB (Samba) that has been removed. Hence you have no access anymore to the NAS via Windows Network Sharing.
      Altough you still can use the Web GUI to access NAS, and FTP.
      There is a strong pressure on AVM from international FritzBox users to get SMB back in.

      Note: I just set-up my new FritzBox 7490 yesterday, and gess what: SMB is back :)

      There are some improvements in the Smart Home area, also in the WLAN Guest Access.
      Also a much better VPN managment (trough the Web GUI in stead of a separate Tool)

  7. Fritzbox 3790 with Belgacom IPTV

    At home I recently upgraded my ADSL-line now to VDSL with Belgacom IPTV.

    By choosing “Belgacom with TV” in the provider options, everything will work fine, besides the fact that the Ports 1 and 2 on the inbedded 4 port switch are put into Bridiging mode.
    That sucks as only one port would be needed for the IPTV.
    I tried manually to configure my line and also by using telnet connection to the box trying to edit config files for bringing back Port 2 into normal swictching mode, but had no success. Anybody having an advice for me?

    • By choosing “Belgacom with TV” in the provider options, you should have Internet on LAN1 + LAN2, and Belagcom TV on LAN3 + LAN4 (bridging VLAN30 for Belgacom TV.
      Unfortunately no way to change this (trough the Web GUI).

      I am discussing with AVM the possibility to add support for a “fully routed” mode, so that you can connect the TV decoder to the LAN (as this is now the default process in the B-box3), however AVM needs more deatils on how this actually works …

  8. Problem with Fritzbox 3790 using Belgacom-Skynet on ADSL and latest 6.0xx firmware:

    Having used 84.05.51 so far, I can tell that there seems to be a DNS bug usin 6.0xx under the follwing condition: You use an (rather old) Belgaom-Office-ADSl contract with a fixed IP adress.
    Once you update to 6.0xx all typed URls will bring you to the Web-if of the Fritzbox. Going back to 84.05.51 is the only working solution.
    Cheers

    Thomas

  9. Not sure if already posted here, but there is a new “Beta” Firmware for the 7390, now supporting full vectoring for the international version.

    ftp://service.avm.de/Beta/FRITZ!Box_7390_int./

    This Beta is version 84.05.61-27090, and is a preview of the upcoming FRITZ!OS Release (OS 06.00).

    Please note that – altough this version is supporting “Full vectoring” – you will not be able to use this on a Belgacom vectorised line (because not “white-listed” :sad: ).

  10. Dear Patrick,

    I would like to check with you if anything is wrong with my box, or if the problems I have been having are ISP related.

    I have always had some problems, mainly instability issues that my friend with the same ISP (Scarlet) and router, but living in Tremelo doesn’t have. His connection is rock solid for years.

    With ADSL2 I had a very slow and unstable connection, with only 4Mbts down and 0.4Mbts up. When changing to VDSL2 I now have a strong 70Mbts down and 6Mbts up, at least that is what my fritzbox shows. However not everything is perfect.

    First, from the 70/6 I can never get over 48Mbts down and 3.8Mbts up. The upload bothers me more as I like to connect remotely and streaming from my server would be so much better if I could get to a stable 5Mbts upload.

    Second and most annoying is when every 36h my ISP clears my internet connection it takes my box sometimes 40 minutes to get a connection again (last time it took only 8 min). My log repeats these errors for about 30 minutes before it gets a connection:
    “PPPoE error: Timeout. pads: hostuniq mismatch”
    “PPPoE error: Timeout”
    “PPPoE error: Timeout. pado: wrong state”
    The funny thing is that it detects the line, and the synchronisation of 70/6 is still there, however it just doesn’t connect me to the internet. In the fritzbox graphical UI in the Overview/Interfaces/DSL is green however in the Overview/Connections/Internet is colour gray.
    I have contacted my ISP and they just told me that nothing was wrong and that they could send someone to check my line, however if that person did not find anything wrong with it I would be charged for their work.

    You are basically my last hope to see if I should get a new frtizbox or continue screaming at my ISP :).

    Have a good day and thanks in advance for all your help.

    • Johev,

      Your connection speed is alright. There is a difference between the synchronisation speed and the delivered speed on the Internet connection. Scarlet delivers a maximum of 50/4 Mbit per their terms.The extra 20 Mbit is reserved for TV.

      Regarding the PPPoE errors, I do not think there is anything wrong with your FritzBox. I have not encountered these errors either with Belgacom or EDPNet. For that part, you could complain to Scarlet. Of course, they won’t help you if you are using anything else than their crappy Sagem or a BBox-2, even of the issue is on their side.

    • As Patrick already confirmed: your speed (48/3.8) is exactly in line with your Scarlet subscription: promised speed (50/4) minus overhead …

      Regarding PPPoE error
      I have seen in my logfiles the same kind of errors, when I manually reconnect the PPPoE session (hostuniq mismatch, pado state).

      This reflects a mismatch during the PPPoE handshake.
      Normally, the FritzBox is sending a PPPoE PADI with a unique host id.
      The router is then listening only on a PADO (answer) with that unique id from the BRAS.
      If the BRAS changes the id or does not using unique id), it could be an answer for another client and the Box is ignoring the answer.
      see: http://www.rfc-editor.org/rfc/rfc2516.txt

      If AVM and the ISP are BOTH following the standard, you should not have such errors.
      However the only way to find out would be to trace the traffic during handshake

      If the Box sends following unique id:
      9c:c7:a6:a8:98:1f:aa:aa:aa:aa:00:00:00:08:aa:aa:aa:aa:46:21:42:6f:78:20:20:20:aa:aa:aa:aa
      But the BRAS answers with:
      9c:c7:a6:a8:98:1f:aa:aa:aa:aa:00:00:00:08:aa:aa:aa:aa:46:21:42:6f:78:20:40:01:01:00:40:02
      Then you have mismatch (different unique ID) and is not allowed.

      The solution in your case would be to enable the option in the FritzBox for a DAILY disconnect, for example during the night (between 3am and 4am).
      This will avoid the 36u forced disconnect, and the handshake will happen during the night, when you are not using the intenet (unless you are a night person :))

      • Thank you Patrick for your fast reply. When talking to the Scarlet support person, he insisted that I had a 70/6 speed. Even after I have asked him if they are not only sending me the 50/4 which I contracted. So I started questioning if my box was having some issues.

        Now that you explained to me that they reserve some bandwidth for the TV, it all makes sense and keeps my mind at piece as I don’t have a failing device :).

        Have a good day.

        • @Philippe

          I want to thank you also for the technical explanation. I have observed these handshakes in real time, and I think that you are spot on with your assumption.

          So there is nothing that can be done from my side but wait for them to get the message right? Does fritzbox try different messages until it guesses the one from Scarlet?

          In the meantime I will implement your workaround suggestion to put disconnect at 3AM, however if having my server 24/7 to other people was an issue, this would not work either solve the problem completely.

          Many thanks again to both of you and I wish you all a good weekend.

          • Hi there, ask Scarlet to monitor your CRC errors. (Scarlet will ask this to BGC.) I sure that in your line has some parasites signals from ISDN or from BGC TV because these two disturb the VDSL2 frequencies. How many CRC errors do you get on you line? You can check this on DSL page of your Fritz.

          • @Wolf

            Thank you also for your input. I just checked my line and the values are like this:
            – I have 2 CRC errors in the last 24h.
            – FEC errors 228 per 15 min (5 per minute).
            – Errors (ES):
            – fritzbox 4
            – DSL Telephone switch 14

            Hope this information is useful.

            Have a nice weekend.

            Johev

            • I find the number of errors on your line unusually high.
              One thing you could try is to tweak the “Line Settings”. This is under “Internet/DSL Information”. By default, it is set to maximum performance. Try setting this to maximum stability and see if it helps.

          • Don’t play too much with the “performace versus stability” settings (unless you really have an unstable line (unstable in the sense of many disconnects).
            Otherwise you riks that Belgacom’s DLM intervenes, resulting (in the worst case) a fallback to the 30/6 “provisioning” profile :sad:

            Note also that the setting towards “higher stability” may reduce your speed (currently 70 mbps).

            I do not believe those errors are linked to the PPPoE problem you talked about above.

            Can you post your line DSL results (actual speed, max speed, attenuation, margin)?

          • I understand your concern about your server running 24/7.
            However you have a residential subscription, not supposing to host servers :wink: .
            I still believe you better have a 24h controlled disconnnect (at the time most concveniant for you), than a uncontrolled 36h disconnect (at any random time which might fall in the daytime).

            I believe that the forced disconnect (36h) is on purpose to avoid customers to run servers – or force them to go for a fixed-IP subscription). There is absolutely no technical reason for this!

          • Thank you all for your help in debugging some issues with my line. As a picture is worth more than a 1000 words here is a link with the today values of my line.

            https://picasaweb.google.com/101806676411896587814/BESTHTPC100PassiveCooledI58GBBlueRay500GB?authkey=Gv1sRgCOnJzYCdvt667AE#5949553060899367362

            If you are ever in Brussels let me know and the 1st beer is on me :).

            Have a nice rest of the weekend.

  11. Found a good one: Run a LAMP server on a 7360 but I belive could work on a 7390 too:

    http://blog.videgro.net/2013/11/fritzbox-lamp-server/

  12. Last week I got a call from Belgacom, on the fact that they could not update my router and were wondering if I was using a third party router. So I explained that I was using the FB 7390. I was told that this router would not be compatible with the VDSL2 vectoring that is rolled out. They advised me to exchange my old BBOX2 which I shelved for the BBOX3 and start using that one. Will the FB 7390 be getting a VDLS2 vectoring firmware? or do I have to switch to BBOX3 or beter wait and buy the new FB 7490 which was announced by AVM and seems prepared for vectoring: http://www.avm.de/en/press/announcements/2013/2013_03_05_cebit1.php3

    • AVM is already testing firmware with VDSL-Vectoring support:

      http://www.avm.de/de/Service/Service-Portale/Labor/7390_frisch_aus_der_entwicklung/labor_feedback_versionen.php

      Neue Funktionen in diesem Labor:

      DSL:
      NEU: Support für VDSL-Vectoring (G.Vector, Full Support)

      • Indeed, AVM has just published a beta version of the 5.51 international firmware with vectoring support added:
        ftp://service.avm.de/Beta/FRITZ!Box_7390_int./

        new with version FRITZ!OS 5.60-26961:
        DSL: support for VDSL Vectoring (full vectoring)

        • Dear Patrick,

          Thank you very much for keeping this support alive. I come here time to time to see what new developments are happening on our box, and the vectoring whitelist/blacklist is something that worries me a little bit (I’m using scarlet and they have not been very friendly lately).

          On another note, the link for the beta firmware does not work for me. Could you please check it?

          Many thanks,

          Johev

      • Don’t get too excited about the FritzBox 7390 which is full vectoring.
        There is no reason to believe that this modem will ever be on the Belgacom whitelist.

        Only OLO’s (other licenced operators) can start the process to approve alternative CPE’s.

        AVM, as the CPE manufacturere, cannot get their CPE’s on Belgacom’s whitelist. And even if they would, why should they put any effort in the 7390 – as their new flagship (7490) is now beeing released.

        The good news however is that the approval of the 7360 (by EDPNet)is in the final stage, and this modem is expected to be on Belgacom’s whitelist very soon.

        And I hope that they will also have the 7490 approved at the same time, because both are using the same (lantiq) chipset.

        • Dear Philippe,

          Thank you very much for that information, even if I did not particularly like the prospect of going from my current 70Mbs/6Mbs connection to a blacklist and having my connection crippled by my ISP.

          I still have hope that things will work out eventually as the new 7490 is first quite expensive and second there still has not been released an international version of it.

          If our box full gets vectoring support I don’t see a need to change anything for some time.

          Have a good day.

          Johev

          • Johev

            I understand your position, however that’s not how Belgacom is working. Hence my post above to avoid any dissapointment. The 7390 is not – and will not be – whitelisted. You will have to just accept it.

            In Dutch we say “Hoop doet leven”, but in this case there is no hope, unfortunately :sad:

            • There is hope. I do not see any legally or contractually binding document from Belgacom or ISPs which prohibit the use of alternative modems. It would be hard for them to put it down in writing, because the free choice of the terminal equipement by the customer is part of both the 1991 belgian law on public enterprises and two EU directives. These texts say that equipement can only be disconnected if it has generated nuisances. This is an after-the-fact approach, based on individual devices (what KPN does). Not before-the-fact based on general exclusions, as Belgacom would like to do.

              The fact that neither IBPT nor Belgacom bothered to reply up to now in writing to my request for confirmation of this white list demonstrates how confused they are. If they ever start using this white list, I would expect lawsuits to follow.

  13. The rollout of the hardware in preparation of the Vectoring technology has started. In a first phase the line cards with an Ikanos chipset are being replaced with line cards with a Broadcom chipset. Exotic hardware, like Fritz!Box modems connected on these ports will probably loose sync or at least become unstable. Once Vectoring is activated, all modems that not at least have a Vector Friendly Firmware (including B-Box2 with VLAN20 closed) will go in Fallback Mode (reduced spectrum profile), meaning best case 7 Mb/s down, 512kb/s up.

    • I trust AVM to come up with a vectoring-friendly firmware. Actually, AVM is in the process of getting the Fritz!Box 7360 approved to work on the Belgacom VDSL2 infrastructure. They are interested in the Belgian market.
      The 7360 is fully vectoring-compatible, and is nearly identical in functionality to the 7390, absent the ISDN part and 5Ghz WIFI.

      Regarding chipset compatibility, I think there is not much to be afraid of. A study from BIPT/IBPT last year pointed out that the issue had been exagerated by Belgacom. Countries where environments are more heterogenous (Netherlands, Switzerland and Luxembourg) show no signs of hardware incompatibilities. VDSL2 is now a mature technology.

      I do not think Belgacom wishes to see its helpdesk flooded with angry phone to calls either. They will proceed with care with the upgrade, in their own interest. In short, do not pay much attention to the FUD.

    • >>> Exotic hardware, like Fritz!Box modems connected on these ports will probably loose sync or at least become unstable

      Why should that be? Source?
      There are thousands of FritzBoxes in Germany and around the world conected to Broadcom VDSL DSLAM’s
      I believe this is a stupid rumour without grounds …

    • In addition to previous comments, I got the news that P&T Luxembourg has deployed some Alcatel line cards with Broadcom BCM65300 chips. The main CPE over there is the AVM Fritz!Box 7390 (Ikanos chipset). ISPs are free to use any CPE they want, as long as it passes the tests. However, most settle for AVM boxes of different models. Note that the Fritz 3370 and 7360 use a Lantiq chipset. It seems that real field experience invalidates the rumours.

    • Unfortunately, I must confirm Danny’s statement (apologise for my previous reply).
      Belgacom will work with a white list. As soon as vectoring is activated, all modems not on the whitelist will go in Fall back Mode.
      Wether or not your modem supports full vectoring (FB 7360) or is vectoring-friendly does not matter.
      Only BBox2 (with latest Firmware) and BBox3 will be allowed.

      It is unclear how quick 3rd Party CPE’s will get on the whitelist, but it does not look promising.
      Note that the FritzBox 7390 (Ikanos) is not yet vectoring friendly, and it is unknwown whenn it will be.
      It seems that 7360 (Lantiq) will be full vectoring sooon.

      I’m very dissapointed with this process, and I hope that many users will protest to the regulator (BIPT), or that alternative ISP’s (EDPNet, Dommel, KPN) will coordinate action to get other CPE’s on the whitelist.

      Users should have full freedom of hardware choice – as long as the hardware is proven to be vectoring capabable or not disturbing the network (black list), as in the Netherlands (where vectoring gets activated in November 2013)

    • This looks ugly :( after 3 years of happily using the FritzBox 7390 I’ll have to put the crappy BBox in front of it … hmmmm
      Does anyone know if other VDSL providers will follow the Belgacom path ? Scarlet, EDP, Billi, Toledo ?

      • Dommel and EDPNet are in the Fritz league. The latter wishes to have a FritzBox approved, but it did not happen yet. Most other ISPs compete on price, so they would rather sell a cheap 99€ modem than a Fritz. The bottom line of the IBPT/BIPT policy is that the modem you is rented or sold by the ISP. You are not supposed to buy it elsewhere.

  14. bob gsrbuty

    I’ve got a 7390 this is the third Fritzbox I’ve had, overal pleased with them but I’m sure the firmware on international version of the Fritzbox, latest update as problems, I used to ne able to receive faxes via sipgate but now can’t, also I get a lot of dropouts both ways in a telephone conversation, they day everythings ok, but if I reboot the device it works for a couple of days then start up suffer drop out, but if I reboot then its gonr again, they blame everything except the Fritzbox, surely if it was sipgate or the isp the problem would ne there all of the time and resolve with a reboot!

    • this is a reply to my earlier post, in the end I put an earlier image of the firmware onto the device AVM where as much help as a chocolate teapot! all works fine now, I doubt if I’ll very bother to update the firmware again!

  15. Hello,
    do anyone know how to configure the Fritzbox 7390 in order to see Belgacom TV with an ADSL2+ line? I currently have internet and VOIP working but I do not get any signal for the TV.
    I only find comments that it is working fine with VSDL, but what about ADSL2+? I will really appreciate your help since VDSL is not available where I live?
    Thanks in advance,
    Arnaud

    • ADSL2+ use Annex A and put BGC TV on VLAN 20.

      • Ik heb dit gevonden hoe je het moeten doen.
        http://userbase.be/forum/viewtopic.php?f=53&t=36132

      • is it possible to do it with the GUI of the fritzbox or do I have to manipulate the config file?

        • Go to “internet” on the left pane then “Account Infomation” then “Internet Service Provider” on the drop down menu you will see Belgacom with TV. Enter your acoount and password. Try to installed with the wizzard. Good luck.

          • it seems that the configuration “Belgacom with TV” expects that I’m having a VSDL line. Since I have an ADSL2+ line, I get the error message “Erreur PPPoE : dépassement du délai”.
            I’ve tried several configurations with “other provider” but I do not get the TV. Any other idea?

    • Why go through all this trouble if you have a working B-Box?

      • Indeed.

        Belgacom TV over ADSL2+ will not work with the FritzBox.
        Contrary to VDSL2, where Belgacom is using VLAN30 (not VLAN20 as per Wolfair’s comment) for IPTV, on ADSL2+ they use different ATM settings (VPI/VCI).

        If you really want to use the FritzBox as your router, and for VOIP, I would recommend to:
        1) keep the BBox2 for IPTV (ports 3+4).
        2) use the FritzBox behind the BBox2 (conncet Bbox port 1 with FritzBox LAN1).
        3) let the FritzBox establish a own PPPoE connection (using your Belgacom credentials).

        This will solve your IPTV problem, while you can still use all the nice features of the FritzBox (The Fritz will receive a separate public IP).

        • It seems indeed that I have to use the solution proposed by Philippe. I hope I won’t get any conflict between both boxes. I will try it soon.
          Thanks everyone for your help.

          • You will not get any conflicts. This is the way many people are running FrritzBoxes behind the modem.
            Just set-up the FritzBox to use “Internet over LAN1″, and enter your Belgacom (@skynet) user-id + pwd.
            If you need any support, you can post a message in the VoIP Forum on http://www.userbase.be

  16. The reviews are usually good for the FRITZ!Box 7390, because they don’t test it for long.

    Advice : **** DON’T BUY A FRITZ!BOX DEVICE! ****

    They stop working after a few weeks’ time, and AVM technical support will make you pay for any repair (when they care to answer, see other posts about that here).

    Don’t buy their DECT phone either, the sound quality is just terrible.

    It’s sad, because the digital part of the system is good, and offers just the desired options. But alas, the analogue part is badly conceived and breaks down after a while. I had to observe that with 3 units: the CLIP wouldn’t be recognized anymore, DECT would start to fail, or WIFI would start disconnect… not mature.

    • I am sorry to hear you had such issues with a Fritz!Box. Mine has been running for two years without a single hitch. The last time I restarted it was in April 2012, after a firmware upgrade. I had absolutely no issues with either the WLAN or DECT part. The signals could be a bit stronger, yes. Despite that, it passes through 3 concrete floors. I cannot comment on CLIP for the analog part, because I do not use it. CLIP works well on the VoIP part, however.
      No issue with the Fritz!Fon either. I actually bought a second one to replace a Siemens DECT phone.

      The international support has always been slow to react, and is often unhelpful. In the past however, they have replaced one of my previous 7170’s without discussion under warranty, with a proof of purchase. Things that do not fall under warranty are typically German boxes which are flashed with an international firmware.

      • FritzBox not working that will be the first. Mine still working bought it in Feb 2012, same as Patrick I need to reboot just ones after firmware upgrade.It connected on Belgacom VDSL2 line.

  17. Hi guys, apologies if this isn’t the right place, but collectively there seems to be a massive gathering of intelligence on the Fritz 7390 here so it’s worth asking. I’ve just taken delivery of a Raspberry Pi that I’ve run up the Domotiga home automation software on. One of the options is to detail information about call stats, voicemails etc. I was wondering if anyone had done any integration between the 7390 and any home automation products? Presumably there would be a way to read the info from the AVM (e.g. using PHP) to get the number of new calls (it’s displayed on the DECT handsets after all), and possibly export or map to the answerphone/voicemail directory in the AVM? My conversational German is “ok” but technical German is a stretch and much of the clever information regarding the AVM is buried away in German forums unfortunately. However, if someone has a useful link I’ll persevere to read it, as this is something I’m really interested in. Thanks for all your help.

  18. When Alcatel-Lucent moves from Ikanos to Broadcom chipsets next year, I doubt if the Fritzbox will still be working.

    • I would not worry too much. there are several reasons.

      For one, there are currently more than a million Ikanos-based CPEs deployed, Belgacom’s B-Box-2 and the OLOs Sagem F@st 3464. Neither Belgacom nor Alcatel can afford to make these devices obsolete.

      Also, there are currently several CPEs that work on the Belgacom VDSL2 network that are not Ikanos-based. The Fritz!Box 7570 uses a Lantiq chipset. Zyxel uses a mix lof Lantiq and Ikanos. The Cisco 88X devices use a Broadcom chipset. (The Broadcom chip even has an Ikanos-compatible mode). The situation in neighbouring countries is also one of heterogenous devices. Even the IBPT considered that Belgacom’s cautiousness about which devices to allow on its network was over-exagerrated.

      The Broadband Forum testfests have similarly allowed chipset manufacturers to adapt their products to different contexts.

      I would say my main concern about the Fritz!Box 7390 is that the current chipset is its inability to fully use the vectoring (aka ITU-T G.993.5) that Belgacom plans to deploy next year. But this will also be the case for the existing B-Box2 and Sagem 3464.

  19. Hi Patrick,

    Yes, 7360 and 7390 work on VDSL2. You can even change the speed on the DSL option. I don’t know by heart on which tab. But sinces I work at BGC I can change my own sepectrum for better stability. IPv6 at the moment is only use by EDPNet in dual stack IPv4 and IPv6. And with EDPNet you can choos 50M-6M or 16.5M-10M If you whant to lower the power cumsumtion on the Sagem or BBOX2 you can kill the cron job.

  20. Dear Patrick,

    Thank you very much for your post. I also have a fritzbox 7390 but so far I was only using it with an ADSL2+ provider.

    In my area the speeds were quite low (out of the 12Mb I would only sync at 3.6Mb) and thus after some time I have decided to upgrade my Scarlet connection to VDSL2.

    Today the person came to my home and their configured the Modem/Router accordingly and now it is working. I was not sure what was the problem, but my fritzbox just could not detect the internet signal.

    After reading your article I now think that the problem might lie in the Annex. After I come back home I will try to change it to Annex B and see if things improve.

    I nevertheless have 2 questions. I understand that you are a Belgacom client but as Scarlet is using the same network your configuration might get me get mine working properly.

    1) Should I enable the IPv6 in the connection settings?

    2) Under the Account Information Settings, in DSL ATM settings, should I use the “Detect all ATM settings automatically” or should I “Define ATM settings manually”?
    In the case I should use the manual option:
    Should it look like this:
    VPI: 8
    VCI: 35
    Encapsulation: PPPoE
    Or should it be something else?

    Thank you in advance for all your help. After I come back from work I will try to configure it on the basis of your guide and I will report back.

    Have a nice long weekend.

    Regards,

    Johev

    • Dear Johev,

      Are you sure you are using VDSL2 ? I am asking because
      1. ISPs insist on using a Sagem/BBox2 modem. The technician is not authorized to configure anything else. If he did, you are a lucky guy.

      2. VDLS2 modems in Belgium will not work at all with Annex A. Annex B is a prerequisite. I guess the technician already took care of that.

      To check if you are on VDSL2, got to “Internet/DSL information” in the Fritz GUI. You should see “VDSL2″ in the “Overview” tab.

      If you are now on VDLS2, the ATM settings are no more relevant. They only apply to ADSL.

      Scarlet does not offer a native IPv6 connection at this time. If you enable the automatic IPv6 tunneling, you might be disappointed with the performance. SixXS tunnelling is much better, but it takes some time to set it up. If you do not have a good reason to enable IPv6, I would advise to wait, or at least postpone it to a rainy Sunday. There are plenty ahead :-(

      • Dear Patrick,

        First of all thank you for your reply. It took me some time but I finally got everything working with my fritzbox 7390.

        In my previous question I might have given you the idea that the technician came and he actually configured my fritzbox. He did not, we have tried it for a minute or two and when the 7390 did not detect the signal, he said that it did not have a VDSL modem and used the standard one that he brought with him.

        After he left I went back to work and I started searching for the answer on how to make things work with our excellent router. I finally got it working by selecting 2 very simple options:
        1) The most important one was to change to Annex B (something that took me some time to find)

        2) In ISP I have selected instead of other, Belgacom. Incredibly after I introduced my username with @SCARLET and my password it synced immediately and I finally had the internet working.

        Just as a curiosity. With the modem router combo from Scarlet I was getting 15Mb download and 2Mb upload speed, and with my fritzbox I am getting over the same line 28,5Mb download and 3,9Mb upload.

        So when they try to convince you as they did with me that their router is top quality and that you do not need yours any more, don’t believe them :).

        Thanks once again and keep this information as it was extremely useful to me.

        Best regards,

        Johev

  21. The 7390’s firmware has been updated over the last couple of days. They’ve finally added a GUI option to manually override the ISP’s DNS servers.

  22. Hi all,

    I use the application for the Android system controlling the 7390: awesome, we have a complete phone in hand (in addition to GSM), access to the phonebook, to settings … Note that it is better to use the BETA firmware, 84.05.07-21362, optimized for a display of pages from the Android device.

    J-Marc
    __________________________________________________
    Texte original :
    ================
    Bonjour à tous,

    J’utilise l’application pour le système Android pilotant la 7390 : génial, on a un téléphone complet dans la main (en plus du GSM), l’accés au répertoire téléphonique, aux réglages … A noter qu’il est préférable d’utiliser la version BETA 84.05.07-21362 du firware, pour un affichage optimalisé des pages de l’appareil sur Android.

    J-Marc

  23. I wonder if we could expect an update to use the FON FritzBox 7390 for Belgacom FON

  24. I’m a bit disappointed with AVM now, This is the third Fritz!Box I’ve had. I now have a 7390 but no matter what I did it did not like taking to my cable modem, the help I got from AVM was next to useless! They used to be very good but recently they just keep repeating themselves as if they are just reading from a script. I also telephoned and spent over 30 minutes on an International call not even getting an answer from them I also sent some Faxes but never even received a reply!!

    In the end the only way I could get the 7390 to work was to piggy back it off the 7270, where it found the internet without any problems, I would like to give the 7390 a different IP address to the 7270 but whatever I give it its does not seems reachable!

    • I also have had problems getting the 7390 talking to a cable modem; I had set the DSL in/out rates too high and this seemed to make the modem choke repeatedly – on setting it right down to 512/1024 I got better throughput so it seemed a little sensitive to the ‘connection settings’ and this is a cable, not DSL line! I brought it up slowly to the actual 5140/53000 Kbps and it worked better.
      Then recently it started halting again. After a lot of debugging I finally made it a client on the network instead of establishing a connection itself. This means that the DNS and gateway is via the cable modem which is now dishing out the DHCP addresses and everything seems to be working better. But all I have now is an expensive wifi router and DECT base station rather than the great functions and firewall of the 7390. Still not satisfied.

      • @Doug What seemes to be the issue is that both your cable modem and the Fritz!Box seemed to do more or less the same thing, but in a conflicted. For example, both were acting as DHCP servers on you LAN, etc.

        The best way to use a Fritz!Box with a cable modem is to configure it router mode only, i.e. disable the DSL part altogether. This is under Internet/Account Information” In the Settings tab, under “Connection”, this should be “Internet vie LAN1″. After a reboot, Those In/out rates fields should be greyed out, or at least ineffective.

        If possible, I also suggest you place your cable modem in bridge mode (call your friendly support desk) , and leave the Fritz!Box to do all the DHCP, DNS and firewalling. That would require the Fritz!Box to initiate the PPoE session, too. For this you need to fill in the User Name and Password fields under Connection Settings with your ISP subscription credentials.

        • Hi there Doug, who supplies your cable service, I use Virgin media, they have recenly released a combined cable modem and router based on a Netgear model, I use it as a router and plug my Fritzbox into one of the LAN sockets the |Superhub then assigns it a Ip addrees like 192.168.*.*I then fixed that IP address in the superhub and also put that address in the DMZ so that two firewalls where not working, the 7390 seems to work fine now, Cheers, Bob

          • I also have the Virgin Media cable service and the Superhub. When I selected ‘Establish own Internet connection’ on the 7390 there seemed to be a conflict and the Fritz!box ran slowly. I think I’ll try your idea of basically getting the Superhub to run as a modem and router with nothing on it’s subnet, then the 7390 in the modem DMZ acting as a NAT router and doing the firewall. thanks for the info.

          • The Virgian Meia Super Hub is a Docsis 3.0 modem + wireless N router. You do not need to establish any PPPoE session, just Ethernet.
            Because this is alrady a router, it is not a good idea to use the FritzBox as a router, becasue this will gave you a set-up withh double NAT.
            Even with the FritzBox in DMZ, you will not avoid double NATting, this is detremental for VOIP.

            The correct set-up indeed is using the Fritz as IP Client.
            Account Information:
            * Internet connection via LAN 1
            * Share existing Internet connection in the network (IP client)
            * Obtain adress automatically (or if you know the IP range of the Virgin Media Super Hub, select a static IP adress)
            * enter your Internet speed
            * Apply

            This will disable both the modem AND the router of the FritzBox, but you will be able to use all other functionality (VOIP, PABX, Media server, answering machine, etc …

            You connect your Super Hub to any LAN port of the FritzBox, the other LAN ports remain available (acting as a switch). You can setup the wireless as a roaming partner of the Super Hub (same SSID, same encryption, same password, different channel)

            Ideally, you should insist to your ISP NOT to receive the Super Hub, but the classic modem (without router). If you insist that you like to continue to use your own router, and that your VOIP application does not work well behind the Super Hub, they might consider giving you the modem-only ??

            That’s how we do it in Belgium: FritzBox users just REFUSE to receive the Combined Telenet modem/router !

          • That would require the Fritz!Box to initiate the PPoE session, too. For this you need to fill in the User Name and Password fields under Connection Settings with your ISP subscription credentials.

            Cant do that withy Virgin Cable modem its not a DSL device? Am I missing something?

            Cheers, Bob.

  25. Hello everyone,

    I have a lot of questions because AVM can’t answer me.
    I don’t have Belgacom TV or a Classic Line.
    I only have internet with an old ADSL line around 3km far from the DSLAM.
    I bought this Fritzbox because i wanted to have a better Wifi, a better modem/router, and the support of multiple voip accounts (3) than the BBox 2.
    With the prioritization of the voip on the internet …
    Except the WiFi, the rest doesn’t work very well.

    First the line :

    I had a profile 4640/512 with the BBox 2 and it was very stable.
    With the Fritzbox i had to answer Belgacom to decrease my profile to 3360/512 and they still say that the relative capacity of the line with this modem is quite bad. I have a lot of disconnections every day 2-10.
    With the BBox 2 for example the S/N margin is about 16dB only 9 dB with the Fritzbox. I can’t understand why i loose near 7 dB …

    Voip problem :

    The VOIP lines work very well but if i download a file or surf on a website, the speech quality becomes bad. So it’s quite complicate to ask everyone to stop surfing when i want to phone … But AVM claims to have a prioritization of the traffic.

    I have asked AVM to help me but they have said that they can’t help me. They think it’s not the Fritzbox but for me i think it’s the Fritzbox that’s defective.
    What do you think ?

    Thank you.

    • The FritzBox 7390 DSL driver is optimised for VDSL2, hence I am not surprised to hear about your problems. It is known that those modmes do not perform well on bad (long) ADSL lines.

      I believe there was no reason for you to request a lower profile from your provider. In case of low SNR, you can set-up your FritzBox for lower sync speeds (and there more stable connections).
      Go to Internet > DSL Information > Line settings and try to set the sliders to the left (towards increased stability).

      Regarding VoIP
      Set your Internet speed manually to a lower value (use the real speeds you have in stead of thhe sync. speed). The QoS will only work if the FritzBox knows your (realistic) intenet speed.

      In your case, I would kee the BBox2 as modem, and connect the FritzBox behind the BBox2.
      Setup the FrtzBox to use “Internet via LAN1″, and allow the FritzBox to make the PPPoE conncetion.

      • Thank you for answering so fast.
        First i tried to set all the sliders to the left but there was a lot of cuts-off.
        So i asked Belgacom to decrease the profile and the line was stabilized.
        But time to time there is still cuts-off.
        Belgacom said me that the relative capacity occupation was much better with the Bbox 2 than with the Fritzbox.

        And today for example, i was on the phone and the Fritzbox restarted but not only the line all the Fritzbox.

        For the speed of the line. There is also a bug in the Fritzbox.
        My profile is 3360/512 ATM speed so the IP speed is around 2850/420.
        So i entered 2850/420 but the fritzbox doesn’t enter the value correctly. You have to try you’ll see on the log and in the overview in the internet menu that the speed isn’t entered correctly.
        The other problem is that all my internet speed is marked as IPTV and not Internet. So if this is true, maybe the Fritzbox considers IPTV traffic as important as Internet Telephony and that’s why i haven’t a good speech quality when i surf on the Apple website for example.

        I changed to the Fritzbox because of it’s power consumption and the fact that it was a all-i-one device. If i had to have a separate IP phone, a separate modem .. then the fritzbox is very expensive …

      • Thank you for answering so fast.
        First i tried to set all the sliders to the left but there was a lot of cuts-off.
        So i asked Belgacom to decrease the profile and the line was stabilized.
        But time to time there is still cuts-off.
        Belgacom said me that the relative capacity occupation was much better with the Bbox 2 than with the Fritzbox.

        And today for example, i was on the phone and the Fritzbox restarted but not only the line all the fritzbox.

        For the speed of the line. There is also a bug in the Fritzbox.
        My profile is 3360/512 ATM speed so the IP speed is around 2850/420.
        So i entered 2850/420 but the fritzbox doesn’t enter the value correctly. You have to try you’ll see on the log and in the overview in the internet menu that the speed isn’t entered correctly.
        The other problem is that all my internet speed is marked as IPTV and not Internet. So if this is true, maybe the Fritzbox consider IPTV traffic as important as Internet Telephony and that’s why i haven’t a good speech quality when i surf on the Apple website for example.
        I changed to the Fritzbox because of it’s power consumption and the fact that it was a all-i-one device. If i have to have a separate IP phone, a separate modem .. then the fritzbox is very expensive …

  26. Good evening everyone,

    A trick and a question.

    * Tip: To configure the VDSL connection of Fritz! Box 7390, it is better to use the wizard! I drove around for a long time trying all the settings as each other on the forums suggested, but nothing worked. “The internet connection is disrupted,” invariably replied the system. There are still a small snag in the config: the choice Annex A / B (analogue / ISDN), and for those who, like me, no longer operates a phone line WITHOUT “classic” … ? Fortunately, the assistant answered the question.

    * Question: what is this “Vlan 20″ mentioned in the B-box? Vlan 10 is clearly the Internet (PPP), but if one understands the Vlan 20 is designed for VoIP? As suggested by the information given by the device:

    Vlan id 10 Vlan id 20
    Protocol Wan eth1.10 PPP Protocol Wan eth1.20 VoIP
    ………………………….
    PPP login fc######@SKYNET NTP ntp.belbone.be

    Is this the “Use an additional connection for Internet telephony via DSL (PVC)
    _______________________________________________________________

    Bonsoir à tous,

    Une astuce et une question.

    * Astuce : pour configurer la connexion VDSL de la Fritz!Box 7390, il vaut mieux utiliser l’assistant !! J’ai tourné en rond pendant longtemps en essayant tous les réglages que les uns et les autres suggéraient sur les forums, mais rien ne fonctionnait. “La connexion internet est perturbée”, répondait invariablement le système. Il y a quand même un petit hic dans la config : le choix Annex A/B (ligne analogique/ISDN) ; et pour ceux qui, comme moi, n’exploite plus qu’une ligne SANS téléphone “classique” … ? Heureusement, l’assistant à répondu à la question !

    * Question : qu’est-ce que ce “Vlan 20″ dont parle la B-box ? Vlan 10 est clairement le réseau internet (PPP), mais si on comprend bien le Vlan 20 serait destiné à la VoIP ? Comme le suggére les infos donnée par l’appareil :

    Vlan id 10 Vlan id 20
    Protocol Wan eth1.10 PPP Protocol Wan eth1.20 VoIP
    ………………………….
    PPP login fc######@SKYNET NTP ntp.belbone.be

    Est-ce la “connexion supplémentaire pour la téléphonie Internet via DSL (PVC)” dont parle la Fritz!Box ? Dans l’affirmative, peut-on l’exploiter, et comment ?

    J-Marc

    • VLAN20 in the BBox2 is used for 2 purposes:
      1) Firmware updates pushed by Belgacom (TR-069)
      2) Belgacom VoIP service called “i-Talk”

      “Use an additional connection for Internet telephony via DSL (PVC)” is only for ADSL (not VDSL2), where you can use a different VPI/VCI for VoIP.

      In the latest Firmware for the 7390, you can manually set a different VLAN for VoIP (but this is not needed, unless you have Belgacom i-Talk.)

  27. Hi,
    One quick question, does the Fritz!Box WLAN 7390 allow NAT Loopback ? Because this doesn’t work with the BBOX 2 :(

  28. I’ve recently got a 7390 I’ve been using a 7270 for some time, I cant even get as far as getting it to talk to my cable modem, the 7270 works fine, I’ve used the same settings as the 720 and as suggested in the manual, but the fritz 7390 just sits there forever and in the end comes up with a error saying it cannot connect to the internet and does not give a error code!!

    • @Bob

      Is you cable modem configured as a RFC 1483 bridge, or does it initiate the PPoE connection ?

      There are several ways to configure the Fritz in such a context. Take a look at this video, which explains the different possibilities.

      Please note also that the latest firmware for the 7390 allows you to selectively import the settings from your 7270. Maybe there is no need to start recreating your configuration from scratch. The latest version is numbered 84.05.04, and you can download it here.

      • Hi there, I’ve had no luck I imported the settings telephone numbers etc. from the old Fritz and then tried once again to get the 7390 to talk to my cable modem I still get the error “‘ The Internet connection as failed, the reason for the error could not be determined, very useful! I’ve been in touch with Fritz tech support but they seem to be reading from a script and just repeat what’s in the manual! This is the third Fritzbox I’ve had and it might be the last. Also tried ringing them direct but gave up after being on the line with music playing for 20 minutes.

  29. I was thinking of getting the 7390 when FTTC arrives here, but I was astonished to see line lengths from Telnet given in feet!! Why? This is Europe, not the USA. My Thomson Speedtouch modem shows data in metric, so why not the Fritz box? Can’t it be change?

    • Can you be more specific on where the 7390 reports line lengths ? I have not seen any indication of line length in the GUI. Anyway, line length is only one of the parameters. Copper quality and insulation are as important. Which is why the telco always performs a line test before assigning a specific bandwidth to your DSL connection.

      • These figures are in the CLI using Telnet. I first saw this here: http://forums.thinkbroadband.com/fibre/t/3994697-how-to-get-a-fritzbox-7390-working-as-a-vdsl-modem.html?view=collapsed&o=1 I saw the figures on this site, but now realise that these are for a Sagem. So maybe it’s common to all Telnet stats – I’ll see what I can find about the Speedtouch.

        Yes, I fully understand that the figures are not accurate. It’s just that I am annoyed that the stats use a measurement that only the USA now uses.

        • I suspect that the figures displayed in the telnet session come from the rough output of the DSL chipset. They closely match the ones displayed by Sagem boxes, which also uses Ikanos DLS chipsets.

          To be fair to AVM, I would say that those values are not meant to be seen by the average end user. Indeed, by default, telnet is deactivated on the Fritz!Box. Activating it gives you a message in the GUI that this configuration is unsupported.

        • Please note that the latest Firmware allows you to set the correct VLAN trough the web interface.
          Therefore there is no need to use telnet or manipulating the config file as decsribed in the above link.
          You can simply choose VLAN = 101 to get the FB work on the UK FTTC.

          • The chipset might explain it. I was beginning to wonder if it was something to do with the Telnet stack. I know that AVM don’t like people using Telnet, but Thomson provide a 710-page guide to using CLI on their boxes!

            I’ve had an acknowledgement of my enquiry to AVM. It will be interesting to see what they say.

  30. Since this Saturday my Fritzbox 7390 no longer connects on VDSL. It shows “nicht verbunden”, and does not even seem to make an atempt to connect. Initially I thought it was a Belgacom issue, and would just require some time, but found that the Sagem is able to establish a stable 30/6 connection. I did not make any changes. In fact, I was not even at home when the router got disconnected. Anyone else experiencing problem with the 7390 on the Belgacom VDSL network? Is it just my box, or has Belgacom implemented a change against usage of Fritzboxes?

    • I have no problem connecting.
      I see your error message is in German. Are you using a German box and if so which firmware do you use ?
      If all else fails, I would suggest to try to flash the recovery image. Source and documentation are here.

      • Hi, thanks for the quick response. Useful to know this does not appear to be a Belgacom triggered change. Yes, I’m using a German box, running sw version 84.04.91freetz-devel-6653 (I use some extras like dnsmasq to provide tftp options to the DHCP clients). It has been running stable for months. I will try reflashing it.

    • What do you mean with “no longer connects” on VDSL.
      – no VDSL synchronisation or
      – no PPPoE connection ?
      If you have VDSL2 sync (Annex B), but no PPPoE there might be 2 reasons:
      – you exceeded the number of simulteneous PPPoE conncetions (for example using a Belgacom Hotspot)
      – wrong VLAN setting

      • I have no sync. It doesn’t even get to the stage of negotiating PPPOE. I just did a recovery back to version 84.04.91, after trying a labor version. Still no solution. The vdsl command menu option 11 shows “Port 1 is not in showtime”. But, the strange thing is that the problem started on Saturday, while I was away for the weekend. So I expect either a HW error in the router (but can’t find other indications for this), or a change at the Belgacom (Edpnet) side.

        • Hi, I’ve continued my troubleshooting, but not found a solution. Could other 7390 users maybe post some stats (output from vdsl CLI command) to use as a reference to compare too? I’m afraid I did not capture enough before the weekend, to know how a good working solution should look like.

          cpe>10

          b1p1 iposPortGetStatusBrief cmdtag 0 status: IN PROGRESS
          cpe>
          b1p1 iposPortStatusBrief cmdtag 0 status: COMPLETE
          cpe>
          Brief Port Status
          =================
          Bme: 1 Port: 1 Status: Port Enabled(Provisioned)
          cpe>
          cpe>11

          Port 1 is not in showtime.
          cpe>15

          Host Software Event Logs
          ===================================
          01:00:23:day 1: Bme 1 System Provisioned
          01:00:24:day 1: Bme 1 Port 1 Provisioned
          01:00:26:day 1: Bme 1 Port 1 Attempting Activation

          cpe>
          cpe>90

          b1p0 iposDeviceVersion cmdtag 0 status: IN PROGRESS
          cpe>
          b1p0 iposDeviceVersion cmdtag 0 status: COMPLETE
          cpe>
          BME Firmware Versions
          =====================
          Firmware-VTU-R:1.68.16.17 AVM4 Time Feb 10 2011, 14:37:08
          RTOS 1.13.1
          BME R:96 AFE
          IFE
          cpe>

          The working Sagem shows the following output:

          # vdsl pstatex

          Extended Port Status
          =================
          Bme: 1 Port: 1
          Downstream line rate: 37428 kbps
          Upstream line rate: 7968 kbps
          Bearer0 Downstream payload rate: 0 kbps
          Bearer1 Downstream payload rate: 29992 kbps
          Bearer0 Upstream payload rate: 0 kbps
          Bearer1 Upstream payload rate: 6048 kbps
          Downstream attainable payload rate: 88892 kbps
          Downstream attainable line rate: 110192 kbps
          Downstream Training Margin: 23.8 dB
          Downstream Line Protection (Bearer1 Path): 1.0 DMT Symbols
          Upstream Line Protection (Bearer1 Path): 1.0 DMT Symbols
          Near-end ITU Vendor Id: 0xb500494b4e530200
          Far-end ITU Vendor Id: 0xb500494b4e530200
          Downstream delay: 7.6 ms
          Upstream delay: 5.4 ms
          Tx total power -15.5 dbm
          FE Tx total power 12.9 dbm
          VDSL Estimated Loop Length : 777 ft
          G.Hs Estimated Near End Loop Length : 841 ft
          G.Hs Estimated Far End Loop Length :715 ft
          Current framing mode: 0x10
          Bandplan Type...........: 0
          No. of Upstream Bands...: 2
          No. of Downstream Bands.: 3
          Line Type: 0x04000000
          #
          # vdsl logp

          Host Software Event Logs
          ===================================
          01:00:36:day 1: Bme 1 System Provisioned
          01:00:38:day 1: Bme 1 Port 1 Provisioned
          01:00:39:day 1: Bme 1 Port 1 Attempting Activation
          01:01:12:day 1: Bme 1 Port 1 Activate Successfully
          #

          What is you Downstream attainable line rate? Is 110192 kbps maybe too high for the 7390?

          Edpnet can not provide assistance, given this is an unsupported setup, using the 7390.

          • I tested my Fritzbox on a German ADSL connection, and could not get a sync either. Firmware upgrade to the newly released 05.05 version did not help either. I’m afraid the box just got damaged. For the time being I’ll use it behind the Sagem, and run PPPOE over LAN0. :-(
            btw. 05.05 include a nice improvement allowing to set the VLAN from the GUI. No need any longer to tweak the ar7 config file

  31. Anyone had this type of 7390 failure ? After a power cycle the box keeps on rebooting. Any ideas?

    When the box is powered up, the power/DSL light flashes, followed by the WLAN light. After a while the wlan light stays on, a few seconds later, the DSL ALSO. After maybe 20 secs, all the lights flash and it reboots.

  32. hi again
    forgot to tell I was at Firmware-Version 84.04.88 level in my Fritzbox 7390

  33. Hello Patrick, Hello All,

    I have the Fritz!Box 7390 for 2 months, it was working fine on my ADSL2+ line in Brussels
    I just requested a migration from ADSL2+ to VDSL2
    changed the 7390 from Annex A to Annex B …
    Synchronisation is OK between Fritz!Box (DSL version 1.68.16.14) and DSL Exchange
    ” Ready down 16528 kBits/s up 2048 kBit/s”

    But Internet status is : “not connected” Additionnal Information : “PPPoE error: Timeout”

    I tried many of the suggested VPI and VCI with PPPoE (and even tried the PPPoA/LLC and PPPoA/V-Mux)
    Especially the VPI 8 and VCI 35 suggested on your page …

    When trying a setting I always receive a “The internet connection failed. The Internet Service Provider is not responding to PPPoE packets. Repeat the test at a later point in time”

    If I connect the BBox it works !!

    and I feel a bit lost and dissappointed.

    What do you think it can be?
    1) is it always VPI 8 and VCI 35 everywhere in Belgium for the VDSL VDSL2?
    2) does belgacom now do a check that the modem-routeur is well their BBOX2?

    Thanks
    Fred

    • 8 and 35 did the trick for me. VDSL with Belgacom – no issues so far, so I doubt they do a linecheck.

    • philippe_d

      For VDSL2, the distinction between services (internet, voip, TV) is done with VLANs, and not with VPI/VCI (as for ADS2). Hence VPI/VCI are completely irrelvant.

      Make sure you selected “Belgacom VDSL” as your Internet provider, and reboot the FritzBox: this setting will automatically create the correct VLAN(s).

      If it still does not work, I would do a factory reset, and re-run the wizzard. Select Belgium, Annex B and “Belgacom VDSL”. You will of course need to re-enter all other settings.

      I found a international beta Firmware on the FritzBox Australia website: http://fritzbox.com.au/firmware/annex_b/FRITZ.Box_Fon_WLAN_7390.AnnexB.en-de-es-it-fr.84.05.04-19709.image (as this is a Beta: test at your own risk).
      This Firmware has a few new features (e.g. DECT repeater, new child protection, …) and also contains a complete new DSL datapump (DSL driver 1.16.18.08)

      • They might be irrelevant, but without that setting, it did not work on Belgacom VDSL for me :-)

        • Thanks to all for your quick reactions…
          Now it works fine, it was just a password issue in the end (it had been resetted to a default value yesterday evening) but strangely the error was not very clear… maybe a mix of 2 problems yesterday evening
          This AVM FB 7390 is a really wonderful DSL modem-routeur !

          Same for me Michael, it is the second time (connection of a friend and now my connection) that it only works when VPI/VCI is set to 8/35. It is strange but true :-)

          Thanks for your help anyway to both of you Philippe and Michael

          Fred

  34. I’m currently looking for a wireless router i could travel with… the purpose is to configure my devices (notebook, pad, smartphone, SIP phone,…) to use this router, so when i’m somewhere (customer, hotel,…) i just need to configure the internet connexion on the router, and all of my devices can use it…

    I’m currently looking at the FB 7390, and i see some great opportunities :

    - I could configure the router to directly connect to my Office VPN
    – I could configure the FB to a SIP server and directly use my DECT phone with it (my phone line follow me everywhere)

    Now i have a few questions :

    - I’ve read that i could use the FB7390 with a UMTS stick, does it works correctly with the Belgacom stick ? (i would like to be able to use it even where there isn’t any other internet connexion available)

    - Is it possible to use it as a client with a WLAN USB stick in place of the UMTS stick ? I’m not talking about using a wlan stick on my computer, but connect a wlan stick on the USB port of the FB to connect to a wifi internet hostpot (in an hotel,…).

    It’s really a need i have for a few years now : a router configured for my devices able to connect to any internet connexion : DSL, Ethernet, Modem Cable, UMTS but also WiFi Hotspot… is it possible with this FB model ?

    • philippe_d

      your question re. Belgacom USB Modem:
      find below the list with supported modems: http://service.avm.de/support/de/SKB/FRITZ-Box-7390/238:Unterstuetzte-Mobilfunk-Modems

      your question whether the 7390 supports: DSL, Ethernet, Modem Cable, UMTS but also WiFi Hotspot…
      DSL: yes (ADSL2+ and VDSL2)
      Ethernet: yes (bus please note VoIP may not always work if you have an Ethernet connection behind a router (e.g. at the customer, in a hotel room)
      Cable modem: yes (but VoiP issues behind the Telenet cable modem/router)
      UMTS: yes (even 4G) – see above list
      WiFi Hotspot: No (the FritzBox WLAN cannot be set-up as a WLAN Client), except WDS (but for WDS you need to enter the FritzBox MAC in the other router (master/slave).
      Only solution: a wireless access point that can be configured as a WLAN client.

  35. I assume that the Fritz!Box WLAN 7390 is also compatible with edpnet then? Edpnet uses the Belgacom lines just like dommel does so…
    But I’m just checking before I purchase this pricey Fritz!Box.

    • @Mike
      Indeed, the Belgacom VDSL2 network is also used by EDPNet and Dommel. Additionnally, you might even be able to use native IPv6 on EDPNet.

      If you are using the EDPNet telephony service, this might be a little trickier. AFAIK, the Fritz does not create by default the VLAN for VoIP.
      [Edit] The VoIP settings for EDPNet are on their wiki. It seems they do not use a private LAN for this, unlike Belgacom. Hence, it should work OK with the Fritz.

      • As far as I know, EDPNet VoIP service does NOT use VLAN20 (contrary to Scarlet/Belgacom), but VOIP goes via the normal Internet conncetion (VLAN10), hence there should not be any problem.

        PS. Mike, you did not mention wether you have ADSL2+ or VDSL2 with EDPNet.

        • I’m not an EDPNet customer just yet. I’m about to move and that’s why I started looking around for a better provider (and my modem/router could use an upgrade too). Dommel looked great but then I bumped into the EDPNet website and I like them even more. The search for internet providers and the problems with Belgacom’s hideous BBOX-2 brought me here. Really glad I found this :)
          Anyway, I’m probably going to get the newer & faster internet package (VDSL).

  36. I just found on an Australian website a new international Firmware (beta) for the 7390:
    http://fritzbox.com.au/firmware/annex_b/FRITZ.Box_Fon_WLAN_7390.AnnexB.en-de-es-it-fr.84.05.04-19647.image

    Not sure what the new features are, but as far as I can see:
    * updated DSL driver (solving sync probems on some Australian ADSL DSLAM’s)
    * Support for Annex M
    * support for Australian time zone (GMT + 9.5)

    The German Firmware was already 84.05.xx (upgrade for Cebit), this beta FW is also the first international 84.05.xx version.

    I believe VDSL2 users should not upgrade (and take the risk) … but ADSL2+ users may have some benefits of the improved DSL driver + Annex M ??

    As usual: make sure you have dowloaded the latest Recovery Firmware BEFORE you update (in case of) … and backup your configuration !!!

    • Interesting Philippe glad to see further development in the pipeling. I do wish some of the other utilities offered by AVM were made available in English.

      Does anyone know if you can toute multiple IP addresses through the AVM 7390 i.e:
      212.67.8.3 (Internet) > 192.168.10.5 (Internal)
      212.67.8.4 (Internet) > 192.168.10.6 (internal)

      Paul

  37. I received my 7390 international version and want to use it to replace my B Box 2, so that I can use DynDNS. I have the Belgacon Intense subscription with TV over the Internet. Where would I connect the TV box, just any of the ethernet ports?

    • If you have the international version …
      and if you have a recent Firmware (.88) …
      and if you have selected “Belgacom VDSL with TV” as your Internet provider ….
      … then the FritzBox has been setup with the VLAN30 needed for Belgacom TV, and LAN ports 3 and 4 have been converted to TV ports.

      • I have tried both LAN3 and 4, but the TV box keeps saying that there is no connection to Belgacom and the display shows 0 IP.
        When I connect the TV box to LAN 1 or 2 it shows up in the LAN list as a PC, and the box shows a loading page for a loooong time, after which it just goes into the normal menu on the screen, but I can’t use any of the services.
        The internet connection works just fine.
        I have the “Internet Favorite sans ligne fixe Pack Internet + TV” package and connect through VDSL 2.

        • Any suggestions as what I am doing wrong?

          • * which Firmware are you using ?
            * Have you selected “Belgacom VDSL + TV” in the provider list ?

          • It’s updated to the latest version (.88). I did a factory reset, chose Belgium as country and Belgacom VDSL + TV from the list. Very strange indeed, but I am at my wit’s end and hope not to have to choose between using the Fritz or going back to the b-box2 to be able to watch TV.

          • I have no idea … everything you are doing looks OK to me (you sure you have VDSL2 and not ADSL2+ ?).

            I do not have Belgacom TV, hence I cannot test it, but some users have reported on Userbase that it works fine: http://userbase.be/forum/viewtopic.php?f=83&t=27372&start=300#p377140

            A temporary solution is to use the BBox2 for TV, and have your FB7390 connected to the BBox2, and use as router (Internet via LAN1 with own PPPoE session).

  38. One further issue I had with the 7390 – I live at the end of a very long telephone line so my ADSL experience is somewhat limited. On the 7270 I can get 2.7-2.8Mbps. On the 7390 I’ve never had more than 2.3Mbps. It’s only a small thing, but many people only get an ADSL link equivalent to the bandwidth I’ve lost by using the supposedly better model. I’m rather disappointed that the ADSL performance should be bad in comparison to the 7270.

    • re. your bandwith loss using a “supposedly better” model. I am not surprised.
      The chipset used in the 7390 is optimised for VDSL2 (contrary to the 7270 which is a pure ADSL2+ model)
      The fact that you can use the 7390 on your slow ADSL line is just a (coincidental) nice-to-have backwards compatibity of the VDSL2 protocol ….
      I guess that all efforts made by AVM to write the code has been focused around VDSL2, and not around the obsolete ADSL2+ standard.
      Hence … just be happy that it syncronises in the first place :)

      • Just to leave an update for this, I never did get any joy from AVM in adapting/configuring my 7390 for (yes, my very backwards) ADSL connection here in the UK. After reading many posts, I took the initiative to buy (for the bank account-empty sum of £10) an older “2-wire” modem that seems to be pasrticularly good on line lines, and reconfigured my router to be a PPPoE client through it, with it acting as a modem. I now get more than 1Mbps INCREASE in speed AND of course I retain all the router feature, just don’t use the built-in modem part of the router. So I’m happy, although it kind of defeats the object of the AVM as a single box and energy efficient solution. So if anyone else does have the same problem of poor ADSL performance, there is a solution: front-end it with a better ADSL modem.

  39. Having been a “long time” user of the 7270, and a huge supporter of the AVM range, I was really excited to get my hands on a 7390. However, this experience has left me bitter and unlikely ever to use their products again. Problems first started on the 7270 to be fair, when I got the latest firmware update (.81). It broke the built-in SIP server, which had worked previously. After months of emailing AVM support, I finally got to the issue myself: in my case, for VPN purposes I need to have my local LAN as 16.1.1.0 – therefore my router is 16.1.1.1. However, on the latest firmware releases, the SIP server doesn’t recognise clients on this LAN as internal and therefore fails their authorisation. I was able to get round it by using a voip.cfg option to allow external clients, but now I have only one-way audio. To add insult to injury, despite researching this and telling AVM exactly what the issue is, they responded as said as I’d modified the unit (by using Telnet) they couldn’t/wouldn’t support me. I’m really damned angry at that.

    Anyway, having bought the 7390 because primarily of the Gigabit facilities, I have exactly the same issue: they’d put the same ‘problem’ in that release too. However, the main issue I have with the 7390 is poor voice quality – in fact, it’s so bad it’s unusable so if anyone else on the forum can advise, I’d be really grateful. I have several VOIP connections (e.g. via sipgate) and these are perfect. It’s only when calls are made over the POTS that they’re rubbish. People can hear me (and I’ve left answerphone messages to test this myself) – no problem at their end. However, in my ear piece all I have is a lot of “noise” and echo, it’s also very quiet. So I ask people to repeat things several times. It’s completely unworkable. Unfortunately being a homeworker, I am forced to dial using the POTS line and an accounting prefix to charge things to my company, so the majority of my calls, and all those to mobiles, MUST use the POTS. I’ve asked my supplier (broadbandstuff.co.uk) to look into it but they aren’t being helpful either. All I want to know is a) does anyone else have this issue or is it likely to be my box, and b) if someone had it, can it be resolved somehow? AVM keep suggesting it’s my line, which is a rubbish explanation: the 7270 works just fine on it, and the line is as clear as a bell. The problem is only there using the 7390. It’s really annoying, because I bought the AVM MT handset, which is BRILLIANT when coupled with the 7390. The dynamic phone book, pictures, and so on – talk about fantastic integration. if the 7390 issue can be sorted out, I’m replacing all my handsets with the MTs but I’m really loathe to give AVM a single penny more of my money while they’re treating with such disrepect and frankly, like an idiot. Anyone got any similar experiences or am I on my own here?

    • Echo on PSTN is a known issue with the 7390 (I see reports of this on Dutch Sites, also on a Australian Forum.
      Hope this will be taken care of in a next Firmware release.
      A work around seems to be to insert a ADSL filter between your phone wall socket and the FritzBox PSTN line.
      Even is there is already one, just put a second one on top of it … and try.

      re. your 16.1.1.0 LAN range.
      This IPv4 range is normally not known as a private range. Hence you can’t blame the FritzBox that it seems this as public IP adresses. Private IP (v4) adress ranges are:
      10.0.0.0/8
      172.16.0.0/12
      192.168.0.0/16
      Unfortunately, the voip.cfg option to allow external clients is not working anymore :(

      • I’ll try the double filter idea – thanks. I have a filtered BT wall plate but might have one of those rather flimsy plug-in things lying around somewhere to try. Glad it’s acknowledged by others though, pity AVM won’t own up to it.

        Reg. the LAN range, yes I appreciate it’s not a usual LAN range, but I don’t why a LAN range should ONLY be an RFC1918 range. What if I had a public subnet for my own use and didn’t want to NAT anything for example? In my case, my company owns the 15.0.0.0 and 16.0.0.0 class A (I won’t bother saying who I work for, you can easily work it out by that) and internally we use 16.x.x.x addresses. There’s the facility for split tunnelling on the 16.1.1.x range only, which is useful for access my internal servers, NAS and network printers while I’m connected to the VPN, which is why I had to change my range from an RFC1918 to begin with. As it is, to get the Fritz back to its default config I’ve had to insert a virtual LAN interface on one of my server instances just to route between the 16.1.1.x and the 192.168.178.x range just so I can get the Fritz back to its normal config. I did it through last night (I’m exhausted now) so I haven’t even had the chance to check whether my Cisco 7960 will connect again, I really do miss it.

        Thanks for your help and your instant response Philippe.

      • I can confirm the double-filter approach works! Who’d have thought? OK, it’s not ideal and it makes the sound a little quieter but by removing the background noise at least I can hear people, which means I’ll at least stay with the 7390. Sounds like it’s not just a fault with my unit then, so what would be your recommendations for returning it, guess there’s no point – I’ll probably just hold out for a firmware release and hope they’ve fixed it. It’s a pity AVM technical support hadn’t acknowledged this issue though – I’m one of those people who’d rather be told bad news honestly than be told dishonest comments badly. Thanks for your help in this.

        • I guess that’s exactly what the double filter approach is doing: making the sound a little quieter (as a too loud sound on the PSTN was the reason for the noice/echo issue in the first place).
          Happy to hear that this worked out for you.

          I’m also sorry to hear that you have such a bad ADSL line … 2.3 mbps is not from this century anymore ;) and certainly not for a HP home worker :(
          Is VDSL2 not available at your place ? My FritBox syncs at 30 mbps down / 6 mbps up !!

          • Just to let you know I had this little gem today, with AVM seeming to indicate it’s a problem with my line, which is inconsistent with the fact that their OTHER product works. They’ve either not understood the issue, or are failing to acknowledge it. Either way, all these people who have the issue must just be a coincidence ;-)

            I have now adopted your case from my colleague.

            No, we cannot confirm that there is a general issue concerning voice quality and the FRITZ!Box. More likely the problem lies with the existing telephone extension or the used components.

            Nevertheless, I will internally forward your comments for further investigation. If we should find the cause on side of the FRITZ!Box or any way that the FRITZ!Box can improve the speech quality of telephone calls, we will implement this in a forthcoming firmware update.

            Best regards,

            Neil O’Hara (AVM Support)

    • I have just set up a 7390 a few weeks ago and run into the same problem. VOIP works fine ! The POTS line is another thing ! Background hiss (or white noise) makes it difficult to use at all. I have connected the POTS handset to another connection point in the house and when a call comes in it works perfectly. Its not a line issue.I believe its a design fault due to the fact the 7390 uses a single plug for the DSL and for the POTS connection hence the 2 into 1 cable ! It seems to me likely that there is crossover inside the box hence it is possibly an hardware issue ! I see lots of folk with the same issue and no feedback from AVM that is helpful, just a lot of suggestions like “check your filter; check your connections” etc Given it could be a hardware issue I don’t see how it will be resolved. I am utilizing a second handset for POTS not connected to the 7390 as a workaround and its fine – but a big disappointment given the hype I have heard around this unit (which in general is very good) !

      • @Graham

        It works for me.

        I suspect the background noise you are hearing might be the DSL signal itself. Please re-read the instructions regarding the wiring (Page 21). There needs to be a DSL splitter between the phone line and the FritzBox connections. The phone connection part of the Y cable needs be be connected after the DSL filter/splitter.

        Your IP address tells me you are living in Australia. I cannot comment on the specifics of phone plug wiring in your country. However, the rules are roughly the same everywhere.

  40. The A/CH version and the International version are identical, and even the Firmwares are the same (it is a separtae download area, because the language, nevertheless identical).

  41. OK, verything is working fine. A comment further up in this thread gave the answer: under ATM settings, VPI needs to be set to 8 and VCI to 35 – then everything works smooth.

    I did not know there is a Swiss/Austria AND a different international one. But I can confirm the Swiss/Austrian version works just fine on Belgacom VDSL.

    I will send you a few screenshots to your email address, which you can use for a new post (if you like).

    As a sidenote: I used my old (now obsolete) Fritz!box 7270 to span a WDS network, so we can overcome poor transfer rates due to double steel-reinforced concrete floors. Worked quite nice.

    • philippe_d

      Michael …
      I see that you are using your “old” 7270 to span your WDS network.
      Please note that with the new Firmware (version xx.05.xx) on both the 7390 and 7270 you can now also span your DECT range, by setting your 7270 as a DECT repeater.

      • Has it been released by now? I tried the Beta, but my 7270 was too old (revision 1) for this. Actually right now I don’t use the 7270 at all, since I connected the machine under the roof via cable. WDS proved to be unstable and with lots of issues.

  42. Are you sure you have set the FritzBox DSL system to Annex B? By default boxes used in Austria/Switserland have Annex A on the PSTN lines.
    In Belgium we have:
    ADSL over POTS = Annex A
    ADSL over ISDN = Annex B
    VDSL2 = Annex B (both PSTN as ISDN)
    Philippe.

  43. I got the 7390 and try to get it working on a Belgian VDSL line. Unfortunately no suitable adapters came with it (only adpaters for Austria/Switzerland) but finally I got the DSL connection working.

    However the actual INTERNET connection does not work, repeatedly saying “PPPoE timeout”. Experimenting with the various internet settings did not help. Also changing from the presets “Belgacom”, “Belgacom VDSL” and “Belgacom VDSL with TV” did not help either.

    I’m back now to the B-Box writing this – any idea/help/clue what migt be wrong? Firmware is the 84.04.88 of February 2.

    Any suggestions will be appreciated.

    P.S. I noticed the B-Box has the DSL up and running almost a minute before the actual net connection comes online. But waiting on the 7390 did not help either.

    Thanks!

    • Unfortunately no suitable adapters came with it (only adapters for Austria/Switzerland)

      You apparently bought the Swiss/Austrian version (ref 20002486), rather than the international one (ref 20002484). I am not sure how different they are, apart from the connectors. Anyway, I notice at http://download.avm.de/fritz.box/fritzbox.fon_wlan_7390/firmware/ that the Swiss/Austrian version has a separate download area from the international box.

      If you have Belgacom VDSL2, one thing to check is that is that the “interference resistance” (under Internet/DSL information) is set to annex B. I overlooked this at the beginning, and the modem would not connect initiate the PPoE session. Once set to annex B, it went through.

  44. Chaining two repeaters is technically feasible. As for the overall performance, it is difficult to guess. I would suggest trying different positions where to install the repeaters. It is really a question of experimenting. No two buildings are identical.

  45. Many thanks Patrick.

    I presume that as you did not comment on my suggestion of using a string of 2 Repeaters, that it is perfectly possible, without any anticipated ‘set up’ complications?

    Best regards

  46. @Roger Repeaters are all working their best if they can “see” each other. A staircase is generally a good place, because this is where radio waves move from one floor to another.

    By “router only”, I only meant the Internet connection part (ie ADSL/VDSL). The telephony part remains working. The modem is delivered with a Y cable. You would only connect the one leg marked telephone/PSTN” and leave the other (DSL) unconnected, and connecgt your cable modem to LAN1.

  47. Many thanks for your very prompt response.

    Unfortunately, the house is already built, so a little late now to lay in a wired network!

    Could I incorporate one, or even two, FRITZ!WLAN Repeaters – say one partway down the staircase with the other on the ground floor, almost within line of sight of each other (the Router would be in my 1st floor study) – without significant loss of transmission speed, as I have an Internet enabled Samsung TV on the ground floor?

    You say that……The Fritz can be used as a router only……but is the Fritz!Box WLAN 7390 not also usable as a DECT base station and also to handle VOIP telephony, both of which would be desirable?

    Best regards

  48. Hi,

    I live on the Greek island of Crete, and due to poor telephony links have resorted to installing a Homenet satellite system from Tooway, together with their model 1101 cable modem which I am about to bring into service.

    The house is constructed of concrete and has a large amount of steel reinforcing embedded within the floors / ceilings and also the supports for upper floors, due to being in an earthquake zone.

    I now need a suitable wireless router, with an excellent range, to enable me to connect to one computer running under Windows 7, and another using Windows XP, together with Internet Telephony.

    I have been looking at the spec for the Fritz!Box WLAN 7390 and would like to enquire as to its suitability for my situation?

    I am not hugely technical, and so would appreciate a suitably worded response.

    Looking forward to receiving your comments a.s.a.p. as I am currently in the UK, flying back to Crete on 15 February, and would like to source appropriate hardware prior to then if possible.

    Many thanks and best regards,

    Roger E. Cooper

    • @Roger

      The Fritz can be used as a router only. It can be connected to whatever device interfacing to the network, like your cable modem, through the LAN1 socket.

      The Fritz has a good WIFI range BUT concrete with steel bars is always detrimental to WIFI. It builds a sort of Faraday cage. This is not only for the Fritz, but for all WIFI access points. You should look at the possibility of installing network cabling. This being said, my Fritz is in the basement, and I still get a useable signal on the second floor. The quality of the WIFI cards in your computers also play a role. Cards with external antennas are usually better.

  49. re. DynDNS
    I have no problems with my dyndns.org account on the FritzVox 7390.
    Not sure if this is related to Belgacom blocking some ports (those are only closed for inbound)
    Anyway you can open these ports in your e-services screen

  50. re. new Firmware. Don’t bother to update to 84.04.88, as this Firmware is only impacting Annex A settings. Hence Belgian VDSL2 users (Annex B) do not need this update.

    re. the warning message on the Main Menu.
    This message appears as soon as you have activated Telnet, and does not disappear neither by updating the Firmware, nor by restoring to factory default.
    It will only disappear by a Firmware Recovery.
    Alternatively, with the “RuKernelTool” (written by Rainer Ulrich) you can remove this warning.
    http://www.rainerullrich.de/ruKernelTool.html
    http://userbase.be/forum/viewtopic.php?p=361395

    However to avoid the warning in the first place, you can use the special FritzBox text Editor to update the configuration. With this tool you can READ the configuration out of the Fritz, SAFELY change, SAVE to your disk and WRITE configuration back into the Fritz.
    http://patrick.vande-walle.eu/uploads/2011/01/FBEditor-0.5.2.zip

    More help on the FritzBox 7390 (in Dutch) is also available on the Userbase VOiP Forum: http://userbase.be/forum/viewtopic.php?f=83&t=27372

    Philippe.

  51. Update : Day 3 with the AVM 7390

    Had my DNS_1 changed to he.net and DNS_2 to OARC. While he.net gives very fast response the OARC it’s a bit slower.

    The ipv6 tunnel with sixxs is stable.

    VoIP: I changed the “reg_from_outside = yes;” and the IP phones (Fring and X-lite) can connect to the SIP server. I can call internal and external numbers but the connection does not work. No sound and the phone and when I call the destination phone keeps on ringing even after I answer.
    SIP signaling seams to fail. Probably I’ll have to play with the SIP ports used by the external phones. I think they conflict with the 5060 used by the SIP server to register with the internet VoIp providers.

    VPN: Configuration of the 7390 using the config tool is very easy, but having a Windows 7/64 client configured it’s not that easy. The AVM VPN client is not supported on W7 (does not have network drivers).
    AVM recommends using another client from Shrew:

    http://www.avm.de/de/Service/Service-Portale/Service-Portal/VPN_Interoperabilitaet/15729.php?portal=VPN

    http://www.shrew.net/home

    Anyone having some experience with this one ?

    DynDNS Errors: It seams that the DynDNS does not work very well. It keeps on reporting an error after login. I suspected a firewall problems on port 80 ? Belgacom is blocking ports 23/80 and 443 by default I think.
    But than I used a different device in my network with a DynDNS client and that one is OK (DS210j).
    Conflicts with the DNS settings ? I have no clue yet!

    One last thing, I noticed that the Fritzbox reported on the overview page an unsupported version of the system and recommended to restore the original setup :) that must be the result of the manual changes I did on DNS and VoIp.

    Have a good day / weekend !

    Calin

  52. Belgacom finally upgraded my line from ADSL to VDSL. Getting 30 down and 6 up. Just had to update my firmware and ensure the correct VPI, VCI was set. Perhaps worthy noting that the encapulation changes from PPPoA/VC-Mux and Appendix A on ADSL to PPPoE and Appendix B on VDSL.

  53. @Calin Glad you could solve it by yourself.

    To enable telnet, I created an entry in the Fritz address book that with the number #96*7*, and double clicked on it. That worked from the LAN. It does not from the WAN, and luckily so.

    Re DNS servers, I prefer OARC and HE.NET (74.82.42.42), because they do not censor results, like OpenDNS does and honor DNSSEC requests. HE.NET is whitelisted by Google, so you will get AAAA responses for Google domains. Additionally, HE.NET resolvers are anycasted and close network-wise. SixXS also provides that, but their DNS servers are v6 only, and that is not supported by the Fritz.

    RE VPI and VCI, mine are set at 1 and 32, based on this post. The same discussion says VDSL2 is ethernet-based, and thus these ATM settings are not used anyway. I’ll need to dig into that a bit further.

  54. Got it ! … after a bit of digging :)
    Account Settings:

    VPI = 8;
    VCI = 35;
    and not on “auto” mode. and everything works!
    Got sync with DSl exchange at 29984 kbps uplink and 6048 kpbs downlink.
    I did a few speedtest.net and I got ping 40ms, between 115 Mbps to 260 Mbps downlink and about 4.16 Mbps uplink, depending on the server (BE / NL / DE). That’s a lot faster than my “old” VOO connection.
    The setup of IPV6 with sixxs was an easy task after requesting a heartbeat tunnel and a subnet.

    AVM released a new firmware: 84.04.88
    Release Notes: http://www.avm.de/en/Download/Info/index.php?url=http%3A%2F%2Fdownload.avm.de%2Ffritz.box%2Ffritzbox.fon_wlan_7390%2Ffirmware%2Fenglish%2Finfo.txt&title=FRITZ%21Box+Fon+WLAN+7390+Firmware

    Today will carry on more testing with VoIP / DNS and VPN.
    I tried to enable the telenet access with #96*7* but it did not work. I’ll have to check the DTMF settings. (I use one analog phone (Philips Voip841), 2 IP softphones and I still have to get my Nokia SIP client to connect)
    I’ll try to change the DNS settings fron BGC to OpenDNS or OARC.!?

    Thank you Patrick and Phillipe for your messages.

    All the best to The Next Net !

    Calin

  55. Hi there,
    got my VDSL2 line today with Belgacom.
    I can sync with their exchange dsl but I can’t get my PPOE connection. I have the credentials and I tried them with the bbox2 and they’re ok.
    Any idea? I called B support but not much help. the guy just reseted and resent the activation codes.
    BBox connection ok.

  56. @calin
    >> I tried to connect on SIP from outside using the DynDNS and IP address but without success so far.

    - first create a new IP Phone account (e.g. ext 621)
    – then go into voip.cfg and search for “extension_number = 621;”
    – change the next line to: “reg_from_outside = yes;”

    Settings of your VOIP device from outside:
    registrar = fritz.box (not the external IP)
    proxy = your dyndns external ip
    username, auth. username etc = 621
    password = the password you use to create the 621 account

    * all above assumes your Box has a direct public IP.
    * Without guarantee.
    * No responsability for broken boxes (if you alter manually some configuration settings).

    trust this helps.

  57. Ok, here comes my 1st experience with the AVM 7390:

    I’ve got the AVM 7390 international with last firmware. Bought it in Germany from sipgate.de (I also have an account with sipgate)
    In 2 hours was fully configured on WAN / LAN / WiFi / VoIP / NAS.
    I’m still using the old VOO connection and I’m ready to move to Belgacom intense.
    I’ve got their installation package (ipod from the promotion was missing and they forgot to send a technician to install the distribution box in the basement … it is a new line) I’ll have to sort that out myself.
    I’ll get back to you when I’ll have the line activated and the 7390 connected to VDSL2.

    So far the 1st impression is very good. I’m moving to AVN from a Linksys 4400N and and SPA9000 SIP / PBX.
    On the WiFi using the 5Gz mode I get up to 9Mbps at 3m and about 6Mbps 1 floor away ( this is almost 5 times more than on the overcrowded 2.4Ghz i used before)
    On LAN using the internal NAS I get very low transfer rates 1.4 Mbps I think it is the QoS that kicks in)
    I have a gigabit switch connected to 1 port, but I noticed on the 7390 it is connected on 100 Mb and not 1GB.
    Is there a way to change the “auto” negotiation mode on the 4 switched ports ?
    Using a gigabit connection over my switch (HP ProCurve) to my other NAS (Synology 210j) I get 24 Mbps (no jumbo frames)
    I did not manage to get my Nokia SIP client to connect via wifi.
    All other fixed and IP phones worked without any problems. I plan to get one of the AVM phones MT-F.
    I tried to connect on SIP from outside using the DynDNS and IP address but without success so far.
    Did anyone tried this already ?

    I did a bit of a stress test (large file transfers, DECT and VoIP on, WiFI 2.4 and 5 Ghz + guest WiFi, audio streaming on, nmap port scan) and it kept a steady performance and power consumption most of the time around 50% and lower.

    One feature I miss is SNMP pooling and syslog. Would be nice to have this enabled. I use PRTG for network monitoring and I miss the snmp monitoring.

    Tonight I’ll try to sort out the cabling and hopefuly tomorrow I’ll have the VDSL line up to do some bandwith testing.
    I’m very courious to see how much better is Belgacom VDSL over the cable connection I have now (2 max 3 Mbps downstream and 0.23Mbps upstream)

    PS. I see now that VOO is ofering 50Mbps with 2.5 Mpps upstream for 50 Euro, but you need to get a new cable modem using the Eurodocsis 3.0

    All the best,

    • @calin Thanks a lot for your review. A few comments:

      Is there a way to change the “auto” negotiation mode on the 4 switched ports ?

      Yes. Go to the System/Energy Monitor and click on the “settings” tab. From there, select “Power Mode” for each port.

      I tried to connect on SIP from outside using the DynDNS and IP address but without success so far.

      I have not tried that. What you could try is to forward the TCP and UDP ports 5060 from outside to the IP address of your box.

      Internal NAS I get very low transfer rates

      I noticed that, too. My first idea was that it could be linked to the fact that USB itself is not a Formula 1 in the first place.

  58. @Patrick

    Do you think the 7390 would also work on the lines of other Belgian providers (I suppose they are using Belgacom VDSL lines)? I’m with Edpnet (ADSL) and I’m thinking of switching to VDSL. I don’t feel like missing my Fritzbox (now a 7270) with it’s wonderful options, also for telephony.

    What’s your opinion?

    • @Jan All Belgian ISPs that offer VDSL2 use the Belgacom network. That includes EDPnet, Belgacom, Scarlet, Dommel and maybe others. If you intend to switch to VDSL2 with EDPNet, they will give you a free Sagem F@st modem, which is a Belgacom BBox2 with another design. The 7270 will not work. It is ADSL only.

      You have three options.
      – You use the delivered Sagem as a replacement for your current Fritz!Box.
      – You use the Sagem as a simple modem, in bridge mode and connect your 7270 behind it. You would keep all the functionalities of the Fritz.
      – You replace the Sagem with the Fritz!Box 7390

      The cheapest options are one and two. I chose the third option, because I did not want to have two devices for one connection. The choice is really up to you.

  59. Excelent! this is teh kind of info you want to read about a product !
    Thank you Patrick!
    I made my mind abot the product I only need to find a matching VDSL2 with IPV6 support. I live in Ixelles / Brussels and I have few choices: Belgacom, Toledo, Scarlet, Telenet, Anyone having some experience and did some performance testing with these providers please share! Thank you!
    Calin

    • @Calin

      You have actually a larger choice of ISPs. There is also Dommel and EDPNet, both of which are using the Belgacom’s VDSL2 network.

      No ISP offers native IPv6 at this time. EDPNet has announced v6 for this year. The rumour has it that Belgacom will some time in 2012. Right now, you need a tunnel to get Ipv6 at home.

      As far as I am concerned, the “least worst” ISP I had up to now is Belgacom. I have not tried EDPNet, though. Telenet is cable, not VDSL2. If you want the Fritz!Box, you would use it as a router only. I have no experience with them, so I cannot comment.

  60. The NTP TF 2007 wall socket is the missing piece! Ty! Belgacom informed me that, regardless of whether I get my own router or not, I will be provided with a free bbox 2. Would be interesting to see whether that includes that wall socket. German Telekom distributes the Speedport 721 modems and better with the new wall sockets. Cheers again, will report back once I got it all set up — or not :D

  61. Thanks for the pointer! Yup, got an int’l version. What about the dsl splitter? I recall not being able to hook my German 7390 up because the Belgian splitter simply has a telephone wire coming out while the German Telekom splitters have ethernet plugs. Assuming the int’l Fritzbox has the same I/O as the German version, how do you hook it up? Cheers for all the input, it’s very appreciated!

    • For the VDSL2 connections, Belgacom requires the use of their new NTP TF 2007 wall socket. Picture here. AFAIK, it is available for free in Belgacom shops. On the Fritz side, the Y cable is delivered with indeed with RJ45 connectors, but RJ11 adapters are included. Hope this helps.

  62. Hi Patrick,

    I read your post on the vdsl bbox and was happy to not have upgraded my patents (who living in Belgium). This post finally confirms that the 7390 works with Belgacom’s vdsl2 offering. I got the German version running in Germany and it works great. Although, VPN-through was a nightmare, ended up using the built-in VPN server for lack of alternatives. Cheers again!

  63. Thanks for the write up, I have found it quite difficult getting information in English on the Fritzbox 7390. I’ve only had mine since the beginning of December and so far I am pretty pleased with it. Certainly the voice capabilities are excellent, the same can’t be said for the firewall settings via the GUI. I’ve come from a Draytek device that had very good firewall configuration for denying access to certain sites based on external rating i.e. alcohol, gambling, pornography,etc.

    I’m looking forward to more articles on this subject. For those that don’t know to enable telnet you use an attached phone and dial #96*7*

Leave a Comment


NOTE - You can use these HTML tags and attributes:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>