KX-T: KX-TD7890
Anyone know where a used/new 7890 (long range model) might be lurking. I just had someone call who had their handset and charging cradle stolen (but not the base station) and is looking for a replacement. Assuming there are none left anywhere, how does the Engenius EP-436 or SN-920 compare in the long range category? Thanks! Dick M. Snow ([EMAIL PROTECTED]) Datalytics, Incorporated Efland, NC _ KX-T Mailing list --- http://kxthelp.com/ Subscription changes: http://kxthelp.com/mailman/listinfo/kxt
KX-T: RE: kxt digest, Vol 10 #219 - 12 msgs
I keep reading that TD500 Maint. software doesn't work on Win2K, but I use it on Win2K pro all the time. Getting ready to upgrade that box to Win2K server so I can use Windows Terminal server into the box. I also use this box to connect to TVS200 (via QVTTerm) and another add-on serial port for SMDR via TSCOLL (thanks Carl!). I know that a box capable to run Win2K Server is way overkill for these functions. I also have custom network monitoring software running here... -Original Message- From: [EMAIL PROTECTED] [mailto:kxt-admin@;kxthelp.com]On Behalf Of Nils Finnsson Sent: Wednesday, October 30, 2002 2:29 PM To: [EMAIL PROTECTED] Subject: Re: KX-T: Continued Quest for Terminal Server Solution... Just my $0.02 on this whole remote administration stuff. ...stuff deleted... As for the TD500, it still needed to be configured through the TD500 Maint. Console which needed to be run under either Win3.x or Win9x. It does not work under 2K, XP or NT. To solve this I just happened to have another machine that was sitting under my desk doing nothing, so I threw Win98 OSR2 on it, and installed the TD500 Maint. software and a copy of Vnc Server. I just vnc into the machine, which sits under the desk with no keyboard, mouse or monitor and use it to dial into the ERMT card in the TD500. All configuration changes can easily be done through there. ...more stuff deleted... _ KX-T Mailing list --- http://kxthelp.com/ Subscription changes: http://kxthelp.com/mailman/listinfo/kxt
KX-T: pointers for VOIP implementation
I've been thrust into a situation where I'm required to provide a VOIP solution for a customer of ours. My normal job is systems/network administrator and I take care of the phone system for our business (a KX-T123211D with TVS-50). The customer's phone gent has a bad case of blinders and appears to be reluctant to look at new technology. Between the sales guy and me we came up with using Multitech's MVP810 on each end of a point to point T1 (using Cisco routers). The mvp810's will be connecting two phone switches (Norstar's is my understanding). What I'm hoping to glean from this list and it's members is any info in implementing such a setup. Gotcha's, "Next time we'll do it like this", problems, etc.. would be appreciated as well as links to web sites. Thanks. _ KX-T Mailing list --- http://kxthelp.com/ Subscription changes: http://kxthelp.com/mailman/listinfo/kxt
Re: KX-T: RE: kxt digest, Vol 10 #219 - 12 msgs
Good morning, Thats pretty weird. I had a laptop here with 2kpro installed on it and attempted to connect to the TD500 with the Maint. Software with no success. The same laptop and HyperTerminal was able to connect to the TVP200 system. So I know the serial port works, but the TD500 software wouldn't talk to the unit. But it's cool to hear that it is working for you :) -nils On Tue, Nov 05, 2002 at 09:28:51AM -0600 or thereabouts, Mike Frederick wrote: > I keep reading that TD500 Maint. software doesn't work on Win2K, but I use > it on Win2K pro all the time. Getting ready to upgrade that box to Win2K > server so I can use Windows Terminal server into the box. I also use this > box to connect to TVS200 (via QVTTerm) and another add-on serial port for > SMDR via TSCOLL (thanks Carl!). > > I know that a box capable to run Win2K Server is way overkill for these > functions. I also have custom network monitoring software running here... _ KX-T Mailing list --- http://kxthelp.com/ Subscription changes: http://kxthelp.com/mailman/listinfo/kxt
KX-T: Re: KX-TD7890
SN920 is the new long-range champ and is a fine phone. First production of EP436 had lots of trouble and we returned all we bought. Michael N. Marcus AbleComm, Inc. www.ablecomm.com etc. 1977 - 2002: Still Alive at 25 - Original Message - From: "Dick M. Snow" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Tuesday, November 05, 2002 9:55 AM Subject: KX-T: KX-TD7890 > Anyone know where a used/new 7890 (long range model) might be lurking. I > just had someone call who had their handset and charging cradle stolen (but > not the base station) and is looking for a replacement. > > Assuming there are none left anywhere, how does the Engenius EP-436 or > SN-920 compare in the long range category? > > Thanks! > > Dick M. Snow ([EMAIL PROTECTED]) > Datalytics, Incorporated > Efland, NC > > > _ > KX-T Mailing list --- http://kxthelp.com/ > Subscription changes: http://kxthelp.com/mailman/listinfo/kxt > _ KX-T Mailing list --- http://kxthelp.com/ Subscription changes: http://kxthelp.com/mailman/listinfo/kxt
Re: KX-T: pointers for VOIP implementation
You may want to look at the Norstar BCM, there is a mailing list ( much like this one ) devoted to BCM ... [EMAIL PROTECTED] "another thing", Although fine equipment ( NEVER PUT ANYTHING DOWN ) Cisco routers will cost at least 30% more BECAUSE of the name. Keith Morse wrote: > > I've been thrust into a situation where I'm required to provide a VOIP > solution for a customer of ours. My normal job is systems/network > administrator and I take care of the phone system for our business (a > KX-T123211D with TVS-50). The customer's phone gent has a bad case of > blinders and appears to be reluctant to look at new technology. > > Between the sales guy and me we came up with using Multitech's MVP810 on > each end of a point to point T1 (using Cisco routers). The mvp810's will > be connecting two phone switches (Norstar's is my understanding). > > What I'm hoping to glean from this list and it's members is any info in > implementing such a setup. Gotcha's, "Next time we'll do it like this", > problems, etc.. would be appreciated as well as links to web sites. > > Thanks. > > _ > KX-T Mailing list --- http://kxthelp.com/ > Subscription changes: http://kxthelp.com/mailman/listinfo/kxt -- Would a fly without wings be called a walk? _ KX-T Mailing list --- http://kxthelp.com/ Subscription changes: http://kxthelp.com/mailman/listinfo/kxt
RE: KX-T: pointers for VOIP implementation
Keith, I set up a VOIP link using the single port Multitech gateways. All worked fine, the proprietary mode was used as the VOIP gateways were behind firewalls which were not H.323 compliant. The only gotcha was detecting call termination. One kind soul off this list helped me out. The solution was to define the port that the Multitech was sitting on as a voice mail integration port; then to define the DTMF sequence that should be sent to the VOIP gateway when the PBX saw a call terminate. Match that with the Gateway's setting and all worked perfectly. Chris. Keith Morse wrote: > > I've been thrust into a situation where I'm required to provide a VOIP > solution for a customer of ours. My normal job is systems/network > administrator and I take care of the phone system for our business (a > KX-T123211D with TVS-50). The customer's phone gent has a bad case of > blinders and appears to be reluctant to look at new technology. > > Between the sales guy and me we came up with using Multitech's MVP810 on > each end of a point to point T1 (using Cisco routers). The mvp810's will > be connecting two phone switches (Norstar's is my understanding). > > What I'm hoping to glean from this list and it's members is any info in > implementing such a setup. Gotcha's, "Next time we'll do it like this", > problems, etc.. would be appreciated as well as links to web sites. > > Thanks. > > _ > KX-T Mailing list --- http://kxthelp.com/ > Subscription changes: http://kxthelp.com/mailman/listinfo/kxt -- Would a fly without wings be called a walk? _ KX-T Mailing list --- http://kxthelp.com/ Subscription changes: http://kxthelp.com/mailman/listinfo/kxt _ KX-T Mailing list --- http://kxthelp.com/ Subscription changes: http://kxthelp.com/mailman/listinfo/kxt
KX-T: Re: pointers for VOIP implementation
Ok. So you're going to link 2 switches. I haven't used the Multitech units, so I won't comment specifically on those. I have used Cisco's VoIP hardware, which I've had good luck with, so my perspective is based on how *I* would do this using Cisco hardware, but I would imagine you can substitute the Multitech equipment w/o much trouble. Since the KXT doesn't support E&M, your only real choices are FXO or FXS. >From the perspective of the KXT side... If we use FXS, then we will connect to a trunk port. For outbound calls, that means users will have to press a line button, or you can set up a separate trunk group, to place tie trunk calls. That's convenient enough. For inbound calls, if there is no DISA service available, all incoming calls will have to ring at a designated extension or extensions. Inbound callers will not be able to choose the destination extension by intercom number. As a workaround, you could have the AA answer the calls and prompt the caller, but that is a kludge that wastes a bit of call setup time, and uses your voicemail ports. IIRC, there is a DISA module you can add which should be able to bypass using the AA. If we use FXO, then we will connect to a station port. For outbound calls, users will have to dial the extension number, but you could program it as a DSS button and label it as a line so the users almost wouldn't know the difference. Program the FXO port to go offhook when ring is detected, take the dialed digits and route the call as desired. On inbound calls the FXO port will simply go offhook (drawing DT) and spit digits which will correspond to the dialed extension. As far as the Norstar side, if they have a Modular ICS, E&M is definitely the way to go. If they have a Compact ICS, or balk at the price of E&M (E&M on Norstar requires several extra pieces of hardware that they may or may not already have), then FXS to loop start trunk ports is the way to go. Connecting to trunk ports lets you take advantage of the routing tables in the Norstar. That let's you do a coordinated numbering plan, where the Norstar users will only have to dial an extension number, and the call will be routed appropriately. No extra digits, and no trunk group (pools in Norstar parlance) selection required. If they have a MICS and decide on loop start and FXS, they will at least need a services cartridge to provide DTMF receivers for DISA service. If they have the CICS, there are a couple of DTMF receivers built in. Be warned that Nortel calls DISA service "auto answer", and "answer with DISA" is optional. You will want the auto answer feature on the tie trunks, but if you enable "answer with DISA" then the system requires a 6 digit COS code before it will provide a dialtone. Rather inconvenient for the controlled access configuration you will be using. The primary reason you don't want to use FXO ports on the Norstar (and I'm pretty sure the KXT has this same limitation) is because Norstar single line ports (either ATAs or ASM ports) do *not* provide a CPC signal. This means that if you have an active call using a Norstar analog port connected to an FXO connected to a far end FXO connected to a Pana station port, no call will ever end. The VoIP equipment will never receive a disconnect signal, and so will never drop the now inactive call. Another reason not to use FXO on the Norstar is because you won't be able to use the routing tables, and users will have to dial the extension # and wait for DT to place a call, just like the KXT. Got to run, but I can answer additional questions. In summary, depending on the Cisco equipment already in place, I would be inclined to use the Cisco stuff directly rather than the Multitech stuff. - Original Message - From: "Keith Morse" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, November 05, 2002 1:09 PM Subject: KX-T: pointers for VOIP implementation | | I've been thrust into a situation where I'm required to provide a VOIP | solution for a customer of ours. My normal job is systems/network | administrator and I take care of the phone system for our business (a | KX-T123211D with TVS-50). The customer's phone gent has a bad case of | blinders and appears to be reluctant to look at new technology. | | Between the sales guy and me we came up with using Multitech's MVP810 on | each end of a point to point T1 (using Cisco routers). The mvp810's will | be connecting two phone switches (Norstar's is my understanding). | | | What I'm hoping to glean from this list and it's members is any info in | implementing such a setup. Gotcha's, "Next time we'll do it like this", | problems, etc.. would be appreciated as well as links to web sites. | | Thanks. | | | _ | KX-T Mailing list --- http://kxthelp.com/ | Subscription changes: http://kxthelp.com/mailman/listinfo/kxt | _ KX-T Mailing list --- http://kxthelp
RE: KX-T: RE: kxt digest, Vol 10 #219 - 12 msgs
I run Win 2K Pro on my Winbook Z1 also for the 500 but it is not always stable. I have about a 75% success rate on connecting and downloading the first time. If the connection is lost or the program decides to hang up at 87% complete, a control alt delete is necessary to do an End Task on the 500.exe program to reset it. One thing that you have to do is right click on the 500 icon that is on your desk top, select properties, Compatibility - set for Win 98. This should get your prog running. Hyperterm runs fine since it is designed for W2K. Michael Karaman President The Phone Network, Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:kxt-admin@;kxthelp.com]On Behalf Of Nils Finnsson Sent: Tuesday, November 05, 2002 2:15 PM To: [EMAIL PROTECTED] Subject: Re: KX-T: RE: kxt digest, Vol 10 #219 - 12 msgs Good morning, Thats pretty weird. I had a laptop here with 2kpro installed on it and attempted to connect to the TD500 with the Maint. Software with no success. The same laptop and HyperTerminal was able to connect to the TVP200 system. So I know the serial port works, but the TD500 software wouldn't talk to the unit. But it's cool to hear that it is working for you :) -nils On Tue, Nov 05, 2002 at 09:28:51AM -0600 or thereabouts, Mike Frederick wrote: > I keep reading that TD500 Maint. software doesn't work on Win2K, but I use > it on Win2K pro all the time. Getting ready to upgrade that box to Win2K > server so I can use Windows Terminal server into the box. I also use this > box to connect to TVS200 (via QVTTerm) and another add-on serial port for > SMDR via TSCOLL (thanks Carl!). > > I know that a box capable to run Win2K Server is way overkill for these > functions. I also have custom network monitoring software running here... _ KX-T Mailing list --- http://kxthelp.com/ Subscription changes: http://kxthelp.com/mailman/listinfo/kxt _ KX-T Mailing list --- http://kxthelp.com/ Subscription changes: http://kxthelp.com/mailman/listinfo/kxt
Re: KX-T: pointers for VOIP implementation
On Tue, 5 Nov 2002, Don Ritchie wrote: > You may want to look at the Norstar BCM, there is a mailing list > ( much like this one ) devoted to BCM ... [EMAIL PROTECTED] Thanks for the reference. I'll check this out. > "another thing", Although fine equipment ( NEVER PUT ANYTHING DOWN ) > Cisco routers will cost at least 30% more BECAUSE of the name. Indeed, but in this case the customer specified the brand name to us so the decision was easy (one of the few). _ KX-T Mailing list --- http://kxthelp.com/ Subscription changes: http://kxthelp.com/mailman/listinfo/kxt
RE: KX-T: pointers for VOIP implementation
On Tue, 5 Nov 2002, Chris Fowler wrote: > Keith, > > I set up a VOIP link using the single port Multitech gateways. All worked > fine, the proprietary mode was used as the VOIP gateways were behind > firewalls which were not H.323 compliant. > > The only gotcha was detecting call termination. One kind soul off this list > helped me out. The solution was to define the port that the Multitech was > sitting on as a voice mail integration port; then to define the DTMF > sequence that should be sent to the VOIP gateway when the PBX saw a call > terminate. Match that with the Gateway's setting and all worked perfectly. > Thanks, I'll keep this in mind when setting this up. I'm prototyping as much as possible prior to implementing. Sadly I don't have a spare PBX. _ KX-T Mailing list --- http://kxthelp.com/ Subscription changes: http://kxthelp.com/mailman/listinfo/kxt
Re: KX-T: Re: pointers for VOIP implementation
On Tue, 5 Nov 2002, Dave Phelps wrote: > Ok. So you're going to link 2 switches. I haven't used the Multitech units, > so I won't comment specifically on those. I have used Cisco's VoIP hardware, > which I've had good luck with, so my perspective is based on how *I* would > do this using Cisco hardware, but I would imagine you can substitute the > Multitech equipment w/o much trouble. If I had seen any VOIP implementation prior, this experience would be less painfull. > Since the KXT doesn't support E&M, your only real choices are FXO or FXS. > > >From the perspective of the KXT side... > > If we use FXS, then we will connect to a trunk port. > For outbound calls, that means users will have to press a line button, or > you can set up a separate trunk group, to place tie trunk calls. That's > convenient enough. For inbound calls, if there is no DISA service available, > all incoming calls will have to ring at a designated extension or > extensions. > Inbound callers will not be able to choose the destination extension by > intercom number. As a workaround, you could have the AA answer the calls and > prompt the caller, but that is a kludge that wastes a bit of call setup > time, and uses your voicemail ports. IIRC, there is a DISA module you can > add which should be able to bypass using the AA. > > If we use FXO, then we will connect to a station port. > For outbound calls, users will have to dial the extension number, but you > could program it as a DSS button and label it as a line so the users almost > wouldn't know the difference. Program the FXO port to go offhook when ring > is detected, take the dialed digits and route the call as desired. > On inbound calls the FXO port will simply go offhook (drawing DT) and spit > digits which will correspond to the dialed extension. > > As far as the Norstar side, if they have a Modular ICS, E&M is definitely > the way to go. If they have a Compact ICS, or balk at the price of E&M (E&M > on Norstar requires several extra pieces of hardware that they may or may > not already have), then FXS to loop start trunk ports is the way to go. > Connecting to trunk ports lets you take advantage of the routing tables in > the Norstar. That let's you do a coordinated numbering plan, where the > Norstar users will only have to dial an extension number, and the call will > be routed appropriately. No extra digits, and no trunk group (pools in > Norstar parlance) selection required. If they have a MICS and decide on loop > start and FXS, they will at least need a services cartridge to provide DTMF > receivers for DISA service. If they have the CICS, there are a couple of > DTMF receivers built in. Be warned that Nortel calls DISA service "auto > answer", and "answer with DISA" is optional. You will want the auto answer > feature on the tie trunks, but if you enable "answer with DISA" then the > system requires a 6 digit COS code before it will provide a dialtone. Rather > inconvenient for the controlled access configuration you will be using. I think the Norstar is a Modular ICS. And supposedly, there will be another one in the new office with the VOIP solution providing the trunking between them ( is trunking the right word?). The Multitech MVP810 has 8 sets of ports with each set containing a jack for E&M, FX0, and FXS. Hopefully this is enough flexibility for the phone gent to work with. > The primary reason you don't want to use FXO ports on the Norstar (and I'm > pretty sure the KXT has this same limitation) is because Norstar single line > ports (either ATAs or ASM ports) do *not* provide a CPC signal. This means > that if you have an active call using a Norstar analog port connected to an > FXO connected to a far end FXO connected to a Pana station port, no call > will ever end. The VoIP equipment will never receive a disconnect signal, > and so will never drop the now inactive call. > Noted, and heck, the phone guy may even know this already. I hope so. > Another reason not to use FXO on the Norstar is because you won't be able to > use the routing tables, and users will have to dial the extension # and wait > for DT to place a call, just like the KXT. > > Got to run, but I can answer additional questions. > > In summary, depending on the Cisco equipment already in place, I would be > inclined to use the Cisco stuff directly rather than the Multitech stuff. In retrospect, I probably would too. Maybe not Cisco, but at least the same vendor. Thanks for the voluminous post. _ KX-T Mailing list --- http://kxthelp.com/ Subscription changes: http://kxthelp.com/mailman/listinfo/kxt
Re: KX-T: Caller ID Table
Paul, years ago, when we first tested the CID boards on kxtd, i think we determined that the lookup table will not work when there is anything sent in the name field. the original kxtd implementation only supported number delivery, and later, name delivery was added. (p101a to p101e ver) i will play with the shop system, there was also something strange when the "private" and "out of area" byte was set on incoming calls. -larry --- "Paul H. Gusciora" <[EMAIL PROTECTED]> wrote: > I have not tried an external CID box, but I assume > that we get 10 > digits all of the time. > > The KX-TD modifies the received CID number according > to the programs. > The raw number and the resulting number must both > match an entry in > the table defined by program 110, else you do not > see the entry from > the table defined by program 111. > > Paul H. Gusciora > San Rafael, CA __ Do you Yahoo!? HotJobs - Search new jobs daily now http://hotjobs.yahoo.com/ _ KX-T Mailing list --- http://kxthelp.com/ Subscription changes: http://kxthelp.com/mailman/listinfo/kxt
KX-T: TD1232-5 DOUBLE CABINET
Tech's & Other List Fans, Whats the rule on the inter-connection of a TD1232-5 and another KSU doubled for expansion? -5 to a -5 or can it be a -5 to a -4 or what other versions can the -5 double with for ext. expansion purposes? Peace multipart/alternative text/plain (text body -- kept) text/html _ KX-T Mailing list --- http://kxthelp.com/ Subscription changes: http://kxthelp.com/mailman/listinfo/kxt
RE: KX-T: TD1232-5 DOUBLE CABINET
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of John Burk Sent: Tuesday, November 05, 2002 9:28 PM Cc: [EMAIL PROTECTED] Subject: KX-T: TD1232-5 DOUBLE CABINET Tech's & Other List Fans, Whats the rule on the inter-connection of a TD1232-5 and another KSU doubled for expansion? -5 to a -5 or can it be a -5 to a -4 or what other versions can the -5 double with for ext. expansion purposes? IIRC you can do a -5 to a -4, but the 5 has to be the master. I haven't seen anything in the 6's yet. Carl Navarro _ KX-T Mailing list --- http://kxthelp.com/ Subscription changes: http://kxthelp.com/mailman/listinfo/kxt
Re: KX-T: Re: pointers for VOIP implementation
I thought it was an analog 1232? - Original Message - From: <[EMAIL PROTECTED]> To: "Dave Phelps" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Tuesday, November 05, 2002 9:33 PM Subject: RE: KX-T: Re: pointers for VOIP implementation | | Actually, a D1232 will support E&M via the T1 module... with this | implementation you will actually get a 'true' switch-to-switch integration, | transparent intercom dialing (if properly set up), access to the 'other' | 1232's trunks, etc. | | How many inter-office channels are you wanting to set up? _ KX-T Mailing list --- http://kxthelp.com/ Subscription changes: http://kxthelp.com/mailman/listinfo/kxt
