Custom Search
VoIP General
VoIP News
VoIP Provider
VoIP Hardware
VoIP Software
VoIP Technology
Havn't found what you want?? TRY GOOGLE SEARCH:
VoIP News
VoIP Provider
VoIP Hardware
VoIP Software
VoIP Technology
Havn't found what you want?? TRY GOOGLE SEARCH:
Custom Search
Internal telephone calls with 7270 as masters and 7050 as Slave2010-12-08 | |||||||
|
Nextiva is a cloud based VoIP phone system, hosting lots of small and medium sized businesses nationwide. the provides UNLIMITED business calling for only $19.95 a month!! Click here for the detail about this promotion!!
Hello!
After I arose here so far rarely and also only passively, I turn times with a question to the community. First to the constellation: A MT-D hangs and supplies my 7270 via DECT, fax equipment (HP universe in One) at the HAIR DRYER 2 and a ISDN telephone (T-Easy P520) at the internal S0-Bus in the upper floor on the Telekom ISDN/DSL connection in the Telefoniebereich. There the internal S0-Bus leads still into the ground floor and “continues to flow” in the ISDN entrance to 7050. This is used only to the Festnetz Telefonie (at present as it were “luxury a/b transducers”) and supplies similar telephones at all three hair dryer exits. All MSNs knows the 7270 and - the 7050 only the MSN is communicated, to which you also is to react and be supposed with that the outgoing discussions to be led: MSN A: 1234 (use by MT-D and ISDN telephone) MSN B: 2345 (use by similar telephones to the 7050) MSN C: 3456 (use by fax) So far the users of MSN A and MSN B over fixed net call themselves. Now to the problem: In the future the fixed mains connection is to be synchronously replaced by a pure VDSL2-Anschluss with 16 MBit and be realized the Telefonie then over VoIP. With first tests (GMX as VoIP Provider) I noticed however the problem that mutual calling from VoIP to VoIP does not function, if both VoIP numbers over Fritz! Box respectable. over a IP to be completed (is that actually like that? Can't that be done?) As solution I introduced myself to hold in the future internal conversations. From the MT-D and the ISDN telephone folds also great: The choice of ** 5*2345* lets all similar telephones ring to the 7050 - so it is to be! Practical it is also that one can store the number in such a way in the directory of the 7270, which comfortable selecting at the MT-D made possible (simply selects the name and types nothing “Krypti”). Only the other direction - thus of the similar telephones at the 7050 to the MT-D + ISDN telephone to the 7270 becomes difficult. Found out I that with the combination *# ** the MT-D rings to 610 and is attainable with the *#*5*1234* the ISDN telephone. Bld is however that A) both simultaneously rings (as it goes in reverse) and b) the 7050 such an abbreviated dialing in the directory to store does not leave (it is required @, if alphanumeric combinations are entered). Does someone have an idea, how in the future the telephone calls from the similar telephones the 7050 to the MT-D and the ISDN telephone to the 7270 to be led to be able? Would be ideal, if further at the similar telephones simply with choice of the 1234 the MT-D and the ISDN telephone would govern (thus a fixed net call was pretended). (Sorry for the length of the contribution - I think the information am necessary to this extent to consider around all aspects.) Hello JimBeam, perhaps the “internal calling problem” could be better solved, if you announce the 7050 at the SIP Registrar of the 7270. Since the version 54.04.70 has the 7270 a SIP Registrar. Such' times, it gives already some contributions, where a box hangs on the SIP Registrar of the second box. Thus all telephones might ring to the 7050 at the same time… I announced here, however 7270 at the SIP Registrar of the second 7270 without ISDN - folds great. Hello Bibie, thank you for yours tap, which I tried out also directly times. Functions does the Telefonie, but the quality is rather mau (it can be because of it that the WLAN connection of the two boxes is not so good). That could be improved by interwiring surely. However this kind of the binding of the 7050 does not solve the Grundproblem to the 7270. I must select also with this connection again *# ** 610, in order to manufacture an internal discussion of one of the similar telephones to the 7050 to the MT-D to the 7270. I am rather over sowas like a modified selecting rule - in such a way to the slogan “if at a telephone to the 7050 the 1234 am selected, select please *# ** 610”. Are there further suggestions/solutions? In the current constellation 7050 at 7270 announced there is the option of calls without 0 for Internettelefonie around preselection nevertheless supplements. If perhaps you thus 600 select could one thereby ** 600 on the journey send. I assume however that the input field will unfortunately accept no asterisks. Hello JimBeam, You could store this “kryptische” number in the directory, in order to then assign an abbreviated dialing there. If you e.g. ** the appropriate telephone selects, rings 701 at the basis box. I call z. B. of the MT-C2 the Repeaterbox, which hangs on the SIP of the basis box, the MT-C1 the basis with ** 701 on: *** 121#*# ** 610 (for *** the 121# the first VoIP NR stands., which here the SIP NR. the basis is; *# ** 610 is the MT-C1 at the basis box) this number was shown in the MT-C2, when I had selected 620 from the basis **, in order to reach the MT-C2 to the Repeaterbox. You needed to thus only store the number in the directory and to assign an abbreviated dialing which can be noticed easily. Perhaps this constellation could be combined still with the tip of stinking boot… 
@stinkstiefel Also a very creative idea - thanks! I habs tries and as suffix can at the point “Internettelefonie” actually also all possible one be registered - problem is however that everything is also actually sent over the line and *#-Kommandos not of the Fritz! Box to be processed: As selecting rule I specified 1234 for the number that she is to be selected over VoIP - the box reacted and did not use not the fixed net, as usual usually, sent however the command “*# ** to 5*1234” also in such a way to the VoIP Provider and it came the English announcement that it was not possible to develop the international connection. On the way it does not continue. @Bibie On this idea I came also - ** 701 still in the context of the acceptable one would have been. In the first contribution I had written that I had tried it to thus store me the 7050 however a line by the calculation made. The 7270 accepts “*# ** the 610” as call number, the 7050 wants gladly @ in addition to have - I make @, fold however nix more - also, if I write the IP of the 7270 behind @. Oops, which I had probably overlook, sorry! Harm, then I continue to know nix… 
Quotation:
@Bibie Nevertheless thanks for your support! @stinkstiefel Oh you meant also the new SIP Registrar function of the 7270 - I had not tried those out in this connection. I will however directly retrieve! Supplement: I am also here unfortunately also unsuccessful - the suffix “** 5*” does not seem to evaluate the 7270, if it acts as SIP Registrar The connection completely normally over the fixed net manufactured… Hello JimBeam, gladly! Quotation:
If you can somehow still rausbekommen that whether like that it is or not, I think, would be the problem solvable. Quotation:
Suffix in such a way put on before a call number ** one selects. A telephone to the 7050 into the hand take and select the 9. What happens then? In the briegen it is to be described always somewhat helpfully your current Setup as exactly as possible. @Bibie A while ago I have somewhat strange noticed in things VoIP to VoIP Telefonie: If I assign the similar telephones to the 7050 a VoIP number, I can reach the telephones to the 7270 by means of the other VoIP number! It did not go like said, from a telephone the 7270 on the other hand at the same box (also not with different VoIP numbers!). If is confirmed in such a way, then I do not need an internal solution - during 16 a Mbit line (synchronous) I can use then also VoIP to VoIP. Tomorrow test I that again extensively. @stinkstifel Sorry, I was the opinion in the first Posting my Setup to have described very in detail (therefore even the apology for the length of the Posting). If I understood you correctly, you mean it in such a way: 7270 hangs on the fixed net/DSL connection and the 7050 via LAN/WLAN with the 7270 one connects, which serves as SIP Registrar. In the attitudes of the 7050 in the Unterpunkt “Internettelefonie” I work on the connection to 7270 in such a way that as suffix ** one selects? I mean to have caused with ** the 5* however already in such a way into for instance the same (I had not *# ** 5* but really only ** 5* as suffix entered) - I however naturally try it tomorrow again with **. Quotation:
I have to call a similar problem internally here, if I announce the 7150 at the SIP Registrar of the 7270. Here the internal number has the 7150 (and to its announced telephone) ** 622. If I call the 7150 from a hand attachment of the 7270 with ** 622, the call goes perfectly internally. I have however the problem that I cannot select from the hand attachment of the 7150 internally to the telephones of the 7270. Now I have a 1&1-VoIP-Nr. with Stun server indication additionally in the 7150 furnished and the mobile part assigned. With the help of this VoIP number I can “recall” now finally also, by I simply my normal call number (Festnetz/VoIP NR. with 1&1) calls. I stored these also directly in the directory of the 7150 with abbreviated dialing number (** 710). P.S. You could do you please one Signature put on, then everyone sees directly, which for a configuration you have.
That up there is not all snow from yesterday stands there nevertheless Sterbenswrtchen over it like you the 7050 now by SIP to the 7270 announced. I find it briegens quite uncool internal discussions over externally run to let. Even if it is only very with difficulty possible perhaps without this detour. @Bibie Signature follows tomorrow. Your problem is really almost congruent with mine. Doesn't permit the 7150 with the abbreviated dialing *# ** the 610 (as example of the first DECT equipment to the 7270)? It does the 7270, like I in Posting No. 1 described. Straight one during your Internet binding with DSL light (have at present also only 768/12  I can imagine that VoIP to VoIP is not tingling like that.@stinkstifel Configuration is further from Posting the No. 1. The SIP binding was tried only in the context of the suggested solution types and was not however again rejected there (it so far not for solution led and the WLAN connection between the two boxes somewhat is too weak). Whether it uncool is or to let internal discussions external run over I do not dare times not to estimate. It is important that it functions. And the cost argument is not there in the first place - the internal discussions are already led with us for years over externally - and during account in the minutes pulse. Is to have to select me also further rather than *# ** 5*1234*. If there is no decent solution, the ISDN connection remains probably. However is further been to me because of an internal solution. And tomorrow for test I still your suggestion with ** as suffix and make extensive VoIP to VoIP tests. Hello JimBeam, Quotation:
Despite DSL with 384 kBit/s telephoning from VoIP folds here in the best way to VoIP between telephones to the 7270. I have also no WLAN problems. The-half have I the 7270 (basis), which the SIP Registrar gives, directly on the DSL connection in EEC to hang. The 7270 (Repeater), which in EEC on the SIP hang, I in the attic platziert. Now the range for PC, WLAN mobile phone and DECT telephone into the last angle is in the garden (approx. 30-35 m) ensures. You know an example of my connections here see.
@stinkstifel I accomplished the following test now: 7050 to the 7270 via Internettelefonie announced (serves 7270 thus as SIP Registrar). When setting suffix on ** and the choice of the 9 at one of the similar terminals to the 7050 does first nothing - the box/the net waits for further inputs. Successes, there are not these a busy signal. ** I have the suffix thereupon again removes. The choice from ** 9 similar terminals of the 7050 causes then that all other terminals ring to the 7050, but none to the 7270! Also the choice of *# ** 610 does not cause with this kind of the connection of the two boxes the fact that it feels the 7270 addressed and lets the MT-D ring. Also *# ** the 9 emptiness runs in. Thus it is confirmed for me first times that with via LAN/WLAN connected Fritz! Box devices of the masters to the internal Telefonie is not attainable. This becomes by the statement of Bibie in the Posting No. 16 clarifies also again - it must use also the external connection. Thus the binding has a further negative aspect via LAN/WLAN apart from the weak points already with me mentioned. I continue to leave it therefore first with the connection via internal S0-Bus and test there. In things suffix me still which was noticeable: It means that something will angehangen - what I want to actually aim at, is a Prefix… sometimes one is in addition, as nailed @Bibie As already above written, no internal telephone calls from the Slave can apparent be led to the master, if the binding takes place via WLAN/LAN by means of the way of the SIP Registrars with the master. Harm! During your DSL connection I meant the 384 less kbit/s in the Download - those should be enough for two discussions. The needle eye are my judgement rather the 96 kbit/s with the Upload. Probably becomes a codec with max. 40 kbit/s Upload to the employment come, if it works with you well and reliably (speculation meinerseits). I read myself times your remarks in the linked Thread and am surprised that handing over from a WLAN station to the other one when telephoning without problems, designated of you as “Roaming”, functioned - which I would not have in such a way expected. National Roaming times differently…. CO2 schaffts off, Bibie leads it. Perhaps “regionally Roaming” would be there the suitable term
My signature is now also finished… Hello JimBeam, the signature succeeded to you! Quotation:
@JimBeam where you actually register the asterisks? My idea was in the place where one the preselection to supplement can. The “asterisk preselection” would be then the desired prefix. Naturally wrongly the whole time suffix was to be along-tapped, ash on my head by me. @stinkstifel I made for screen SHOT and angehangen. I accordingly removed the Kreuzchen with “0” and the preselection without placed in front 0 (made in the screen SHOT unrecognizable) and used with suffix (which when logical thinking an error was) the two asterisks. As you see in the screen SHOT, however the possibility does not exist other symbols than the “00” as prefix, the “49” of indicating the “0” and the preselection without 0. “**” One cannot let automatic preselect so thus this way. I tried now also times with 7050 a something. I announced the 7050 over LAN A at a Asterisk. At the hair dryer 3 of the 7050 a similar telephone wedges. Without attitudes with AREA or country code functioned *# ** 9 as it is, with the Asterisk arrives it as follows. Code: INVITE sip: ** 9@ 192.168.1.254: 5066 SIP/2.0 via: SIP/2.0/UDP 192.168.1.100: 5060; branch=z9hG4bKD8C9B353213A1A83 From: <sip: egal@ 192.168.1.254>; tag=7633EF4002601E91 ton: <sip: ** 9@ 192.168.1.254: 5066> Call ID: F7AE234CC0C443C3@ 192.168.1.100 CSeq: 15 INVITE Contact: <sip: egal@ 192.168.1.100; uniq=0445E8F770837EABC13B5E28B4177> Max Forwards: 70 Expires: 120 user agent: AVM FRITZ! Box hair dryer WLAN 7050 annex A 14.04.26 (September 6 2006) Supported: 100rel, replaces Allow Events: telephone vent, refer Allow: INVITE, ACK, OPTION, cancel, BYE, UPDATE, PRACK, info., SUBSCRIBE, NOTIFY, REFER, MESSAGE content type: application/sdp Accept: application/sdp, multipart/mixed Accept Encoding: identity content length: 380Next I wanted to see whether one through to change of AREA or country code also only the 9 can select. I registered thus with AREA ** (see appendix) and after to store the attitude on the telephone the 9 selected in hope with the Asterisk ** 9 arrives. Pustekuchen with the Asterisk arrives at all nix. By further try placed I then the 7050, with this attitude, firmly only off select themselves a call number four digit with the Asterisk announces. I do not have as I four asterisks saw badly been astonished although I only on two counted. Code: INVITE sip: **** 1234@ 192.168.1.254: 5066 SIP/2.0 via: SIP/2.0/UDP 192.168.1.100: 5060; branch=z9hG4bK3CC3637F4D8DF0A4 From: <sip: egal@ 192.168.1.254>; tag=9A85A58A0DD524FB ton: <sip: **** 1234@ 192.168.1.254: 5066> Call ID: 90D77003B188DE91@ 192.168.1.100 CSeq: 28 INVITE Contact: <sip: egal@ 192.168.1.100; uniq=0445E8F770837EABC13B5E28B4177> Max Forwards: 70 Expires: 120 user agent: AVM FRITZ! Box hair dryer WLAN 7050 annex A 14.04.26 (September 6 2006) Supported: 100rel, replaces Allow Events: telephone vent, refer Allow: INVITE, ACK, OPTION, cancel, BYE, UPDATE, PRACK, info., SUBSCRIBE, NOTIFY, REFER, MESSAGE content type: application/sdp Accept: application/sdp, multipart/mixed Accept Encoding: identity content length: 382If two stars with AREA the code to four will would have one with a star to two to come and so is it also. Unfortunately whole however stop has the hook only starting from a number four digit anything at all from the 7050 raus goes. For further experiments I had no more desire. Hello, I furnished and could 7150 at 7270 at the incoming goods successfully with SIP Registrar functionality in both directions of discussions construct and telephone - without with it somehow externally to go, the DSL connection was completely cut. The direction of a telephone at the master box 7270 to 7150 is simple and functioned after registering good with ** 62x For the opposite direction I tried all possible and me thereby in the 7150 by telnet the tasks of voipd indicate to let. All the same whether one it with *#… or something similar tried, the result is always a “empty” goal. Now to the functioning Workaround: First: I for safety's sake furnished the 620 and the 621 equal and connected. I believe also that only the 621 finally to the goal led. I developed the internal discussion then over a directory entry. The directory entry contains one sip uri! I fell back to a VoIP account furnished in the master box. That was without DSL not registered, however nevertheless the user account available made. Thus which is to be done: Master 7270: (IP e.g. is. 192.168.178.1) VoIP Provider or VoIP Fake account furnish. Is important of it for internal discussions only the username I say times it is called “master”. IP-Telefoniegerte 620 and 621 furnish. Slave 7150: VoIP accounts 620 and 621 furnish. Directory entry e.g. put on. 701: master@ 192.168.178.1 Internal discussions develop: At telephones of the 7270 master box to 7150: ** 620 or ** 621 At the Dect mobile parts of the 7150 to the master 7270: **701 The same proceeding should with all boxes *# does not support functions means I. Greetings Ralf Hello Ralf, many dear thanks for this mad description. Juhu, folds so in the best way!  
Hello, the proceeding sounds itself well. So I can integrate hopefully also mine 1020ATA. I only come to your guidance to one point into understanding difficulties: As the VOIP Fake account is to be put on… ? Internet call number? all the same? (Property times a 1 registered) Username: master1 Password empty? The next problem is now, as gets I the allocation the terminal on the master box? Leave simply a terminal to the new Internet call number 1 to react? Questions over questions *g*…. My master is by the way 7170 and my Slave a hair dryer 7150 with two DECT terminals. And perhaps soon also a 1020ATA. About an answer I would be pleased…. ~ Idux |
