Hello

I have the CH version, analogue. When I last tried it at the beginning of the year, there were massive failures on the TV…

Has anything changed on the Swisscom side since then? The firmware is still the same.

Greetings

Andrew

Sure, a lot has changed. Look under “Fritz Labor”, there are various updates. I’m currently running the lab from July 22, 2011 (Annex A, Analogue, 20′000). By the way, perfect.

@Empowered: I have a 7390 CH version, bought at the bridge

---

@Empowered wrote:

Does anyone here in the forum already have the 3370 running?

---

I would be interested in that too. But apparently it doesn’t exist with Annex A

Where did you get your Fritz box from?

Originally it is packaged quite well in a cardboard box with appropriate holders.

Without massive damage to this box, it is almost impossible to scratch it.

If so, the seller gave you a complaint and sent you a used/returned or exhibition model.

What do you mean it reboots? Completely or is the connection just disconnected? It is normal for the connection to be briefly disconnected once a day (lasts about 45 seconds).

Take a screenshot of the event log (>> System >> Events >> Internet Connection).

This week I bought a FRITZ!Box 7390 DE and got it running on my analogue Swisscom VDSL Anschluss (Annex A) with the latest official DE firmware 84.05.05. Swisscom TV also still works perfectly, I even have the feeling that switching channels in Swisscom TV works a bit faster than with the included Motorola VDSL router.

To run the German Fritz!Box 7390 on Annex A Anschluss, all you need is the ruKernelTool software. The “Read/Change Annex” function must be carried out via the “Tools” tab. There you then have the opportunity to change the Annex Anschluss from “B” to “A”. If you do this, the Fritz!Box 7390 DE works, as already mentioned, with the official DE firmware on an analog Swisscom VDSL Anschluss. However, it is important to point out that this setting is not officially offered by AVM and that this could potentially violate the device’s warranty, so please approach this matter with caution.

Additional information 1: To execute the “Read/Change Annex” function in the ruKernelTool you need the Windows software “Telnet Client”. You can install these later at any time via “Control Panel - Software - Add Windows Components”. This is also pointed out again in the ruKernelTool. You also have to activate the expert mode in the ruKernelTool.

Additional information 2: I connected the cable supplied with the Fritzbox directly to the telephone socket without a Swisscom splitter or filter; the purple Swisscom cable did not work for me.

Hello

Today I tried to update the firmware 84.05.05, the update went without any problems, but I can no longer get an internet connection to Swisscom.

@Empowered. What have you posted on your FB?

Have you changed VPI to 8 and VCI 35 and changed DHCP hostname to myhost to Encapsulation Bridged IP Automatically? (see also the PDF, which is explained several times in the forum)?

Yes, that’s how it’s set up, the internet was still working before the FW update. 🙂

But I have now found the solution, changing Annex A to Annex B after the update to 84.05.05 is logical, right!?!?! FritzBox sends greetings with the firmware adjustments.

Greetings Steve

With VDSL you don’t need to enter VPI VCI, right?

---

@Dani CH wrote:

Have you changed VPI to 8 and VCI 35 and changed DHCP hostname to myhost to Encapsulation Bridged IP Automatically? (see also the PDF, which is explained several times in the forum)?

---

greetings elchoer

SteveB wrote:

But I have now found the solution, changing Annex A to Annex B after the update to 84.05.05 is logical, right!?!?!

Would be logical with VDSL. Whether analog or ISDN. But AVM somehow has a different understanding of Annex.

Do you have an ISDN Anschluss?

If so, it may be that the FW update automatically sets to Annex A.

I have a silent Infinity Anschluss, so VDSL and still on Annex A to connect.

I loaded the FW on Saturday. Without any problems, without having to adjust other settings or settings.

elchoer wrote:

With VDSL you don’t need to enter VPI VCI right?

Yes, that’s what it takes.

---

@Herby wrote:

@SteveB wrote:

But I have now found the solution, changing Annex A to Annex B after the update to 84.05.05 is logical, right!?!?!

Would be logical with VDSL. Whether analog or ISDN. But AVM somehow has a different understanding of Annex.

Do you have an ISDN Anschluss?

If so, it may be that the FW update automatically sets to Annex A.

I have a silent Infinity Anschluss, so VDSL and still on Annex A to connect.

I loaded the FW on Saturday. Without any problems, without having to adjust other settings or settings.

@elchoer wrote:

With VDSL you don’t need to enter VPI VCI right?

Yes, that’s what it takes.

SteveB:

I have an analog connection.

---

I’ve now experimented a bit with myself.

FB7390(CH) FW 84.05.05 Anschluss: DSL and Natel Pro.

In the FB web guide:

Whether Annex A or B, both work.

Annex read with ruKenrelTool shows Annex A. Even if the FB web guide is set to Annex B.

If ruKernelTool is set to Annex B, no connection is possible.

Set to Annex – the FB connects again. When you read the annex again, the FB was set to Annex A.

The confusion is now complete.

The FB simply wants, at least with me, Annex A in order to be able to connect.

The FB also wants or requires values ​​for VPI / VCI.

Otherwise she won’t. Which values ​​don’t matter.

I have now entered VPI 0 and VCI 32. FB Connects.

So much for AVM’s understanding of Swiss DSL

But I assume that you are running the FritzBox in expert mode…

Why does the FritzBox ask that? You don’t have to set things up automatically, just cancel everything when you log in and enter the things manually…