ISDN over FB, breaks off again and again - VoIP General, VoIP News, VoIP Providers, VoIP hardware, VoIP software, VoIP Technology

Hello,

I have the problem that the Fritz box makes igendwie that with telephone calls (ISDN internally and externally), with some called participants and with certain telephones (2 different have), the connection breaks outgoing ISDN off immediately, if the other one takes off. (or also after n seconds of bells)

There does someone have an idea?

I have ideas somehow already, but are missing a few information:

1. Which Fritz box?
2. Which telephones?
3. Which offerer?
4. Are there telephones, which function perfectly at the box?
5. Do the telephones function directly at the NTBA?

Ok one gladly;

Fritz box 7170 (in addition, now with newest firmware, does not go)
Telephones Ascom/Swissvoice ISDN Eurit 133 or 557 cordless
Ascom/Eurit ISDN 30 cable-bind (with it no problem!)
Connection Telekom T-Home Entertain with VDSL 25 ISDN
Call over Telekom 01033
Directly at the NTBA also everything goes marvelously
Telephone system Telekom xi721, between FB and telephones
LCR Quicktel (does not go without in addition,)

For the moment I went around the Fritz box and everything at the NTBA attached, but that is not satisfying. The telephone system is not also the reason. It happened even if I the telephone directly to the FB attach.

Sometimes as said, after n bells or, if someone takes off, the connection is also separated. If the other one goes before the n times bells, then I can if necessary even telephone. It kahm also forwards that it rang with me and I have taken off and the connection became separately. I do not know however whether that has the same cause.

newest firmware is always so a statement, because which of the many new and with some is due newest partly already xx months old - Mach it you in the future more simply and write equal the version - thanks.

Mach asks more recover as per. Guidance here: http://www.router-faq.de/index.php?id=fb&fb=recover
register importantly after it MANUAL the data again. (not the Konfig. back-store)

Are not unfortunately locally. The FB updated 2 days ago.

With the Recover a quite hard and complex interference seems to be. Since the FB functioned and was again geflasht the firmware, did I ask myself, how which can change at the situation? There does a concrete assumption lie behind it or is only a “club”?

you write that the box makes “which her wants”.

This could on an incorrect Konfig. its, therefore it is to be made meaningfully a work RESET of the firmware, what goes only over more recover.
you need approx. And however then security would have 10 min that you a clean firmware + manually Konfig. have.

With a firmware update not all data are again written, therefore is not it with one another (<> more recover) comparably.

Ok one,

at the earliest on weekend am I again locally, in order to test.

Perhaps someone knows the problem even concretely and knows that it lies.

It is really amusing, because it arises only in combination of certain Aparaten and participants.

Legends wirs times so, you should always have problems with the same equipment, all the same whether it hangs separately attached or behind a TK-plant, I as the first on the equipment would tap. The TK-plant actually develops its own ISDN bus and separates thus the telephone from the Fritz box. Why it functions directly at the NTBA, I can not explain myself in addition.

I could solve such compatibility problems between a Fritz box and an attached telephone by interposing a TK-plant. Perhaps the T-Com-connections are only simply more tolerant opposite such devices. The fact that ringing is broken off after certain time is normal. One while should ring it however. Did not measure I the time however yet.

Are there also the problems, if the equipment hangs as only on the box? I do not believe also that a Downgrade of the firmware will solve your problem. You have thereby only a defined starting situation without configuration corpses.

Greeting telephone male

That it is the telephone, I thought also only and then a new cordless bought. But Eurit, only generations further.

It happens with and without TK-plant between FB and telephone. The Tel had already directly to the FB.

The abort happens already after 10-20 seconds, before the STARTING FROM of someone goes. And with some persons even if it takes off.

Property exactly the same problem for months with my 7170 and the XI 721. A ISDN trace had been able to supply no reason for the separation. Already did someone find a solution?
The firmware version in the Fritz box is 29.04.70. Repeated reseten on factory settings, as well as again configuration had brought so far nothing. Use my box however not as if rout, but only as modem and the ISDN Telefoniefunktionen.
Me it seems to be a software problem, because the connection is separated cleanly, and is not only interrupted. In the case of a minutes error my Siemens says plant to the XI 721 “minutes errors” in the display and during the interruption by the Fritz box “connection was separated”. On the opposite side usually “opposite side presented”.

Mfg Igi

I do not know unfortunately today yet more. Can it be that it is because of the TK plant?

It can also be that it is because of the TK-plant, or that this comes with certain signaling/Displaymessages of the Fritz box not by right. If it were however a biased error, one would have to actually read more here. Test way can switch you times the Displaymessages off at the internal S0 with the choice of #960*0* at a telephone attached to the Fritz box (to restart you know the full mode with #960*1* and the minimum mode with #960*2*). To represent Displaymessages after the structure of call and also during ringing transferred around information for used line or other features. Perhaps your TK does not get along with such information.

I assume times the TK is attached to the Fritz box ordungsgemss and the bus is also accordingly scheduled. Strangenesses in the ISDN Telefonie can be due also to not completely the standard corresponding remarks of the wiring. Straight sporadic errors are a reference to it. ISDN is digital, but “goes” between and “go not” lies also “go sometimes”.

Greeting telephone male

Yes, I had already tried that with the Displaymessages. Those are for well two months cut out. I used the Fritz box the last mark as VoIP before well two years with ISDN. There still the firmware 29.04.15, thus 2.4er Linux Kernel drauf, was here never gave it to interruptions. Since then I VoIP no more do not have, but purely ISDN did not have I 7170 the no more in enterprise. It has however again in enterprise taken as I the arriving call barriers used. That was like that in December rum. DS-MOD from at that time down and the current official firmware drauf. Everything folded from the outset marvelously, up to the interruptions, and/or. presenting by the Fritz box. As said, also ISDN D-Kanaltrace did not bring realizations, the several-day-long along-logged, until the text file became large several 100MB, without success.
I wanted to use the 7170 only more weger the more comfortable call list and the arriving call barriers.
Today I have times of the 29.04.70 on the 29.04.15 down geflasht, times see like it behave if not as much Schnickschnack there in the box packed am.

Mfg Igi

HP. As do not rout use I those, only as modem, rout makes my Linux server in the back to.

Thus, after I runtergeflasht the box on 29.04.15 (2.4er Kernel), the Telefonie without Unterbrechnungen functions also with the Displaymessages. My problem took care of itself thereby. The box will probably not more update.

Mfg Igi