September 1999 - USR-TC - mailman.xmission.com

RE: (usr-tc) Upgrading DSPs
by Stainforth, Matthew 23 Sep '99

23 Sep '99

I'm running 2.0.81 on most of my DSPs and I have no complaints specific to that version. I needed it so I could do NFAS which also seems to work great. On Thursday, September 23, 1999 2:28 PM, K Mitchell [SMTP:mitch@keyconn.net] wrote: > On to my main point, I'm currently running 1.2.60 on all cards and > 4.1.59-6 ARC code. On the DSPs, should I go with 1.2.37 or move up to > 2.0.81? Any problems with either? Same question on the ARC, is 4.2.31-1 > worth bumping up to? > > Thanks, > Kirk > > -- > Kirk Mitchell-General Manager mitch(a)keyconn.net > Keystone Connect Unlock Your World > Altoona, PA 814-941-5000 http://www.keyconn.net > > > - > To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" > with "unsubscribe usr-tc" in the body of the message. > For information on digests or retrieving files and old messages send > "help" to the same address. Do not use quotes in your message. - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.

1 0

Re: (usr-tc) modem that will
by Ahmed Saeed 23 Sep '99

23 Sep '99

>From what is written, it seems that the modem picks up the call fine but there is no packet bus data to tell hiper arc to terminate call. try reset modem slot:x/mod:x Best bet is to go to tcm, and download the parameters from another good working modem. By these steps, you eradicate the packet bus, config values, only other thing might be the packet bus interface for that particular modem. This would come under hardware issue. Ahmed On Tue, 14 Sep 1999, Stainforth, Matthew wrote: > > I'm having a problem with one modem that refuses to pick up. When I watch > the status in performance monitor, I can see the call coming in (RingIn or > RingRcvd states), DNIS and ANI information comes up, but the modem never > picks up the call. I have replaced the DSP NAC and the problem didn't go > away. The only other place I can think to look is to the ARC itself but the > modem interface is UP/UP. I've also tried a full reconfig (restore from > default, save to nvram, reboot, reconfig, save to nvram, reboot) and no > luck. When a user happens to grab that line they hear a long pause of dead > air (maybe 5 seconds or more) and then it starts ringing endlessly. Any > ideas? > > - > To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" > with "unsubscribe usr-tc" in the body of the message. > For information on digests or retrieving files and old messages send > "help" to the same address. Do not use quotes in your message. > - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.

1 0

(usr-tc) TCBox won't make T1 Connect
by Jerry Wright 23 Sep '99

23 Sep '99

We have an older TC Box with digital/analog cards, and a dual T1 setup, as well as NMC and NetServer. Okay... If you set the modem card to Nic, you can dial in on an analog line and connect. If you dial in on the T1, nothing. Now, for a bit, it was working, but I didn't have the pool set properly in the Security Server, and authentication didn't work. That's fixed. Now, call-ins on the T1 say, "Your call did not go through, would you please hang up and dial again." We're set to esf and b8zs, wink start... just what the phone co wants. They say they can't get a wink acknowledge, our NAC passes allinternal tests. Local Digital loopback works, Remote loopback fails, and it says, NO dialtone. Any suggestions??? Jerry Wright www.iaml.net mailto:jwright@iaml.net mailto:jwright@hyperserv.com Internet Access of Moses Lake Hypernet Services. - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.

1 0

Re: (usr-tc) Cisco 802 Connecting to ARC
by Jim Johnson 23 Sep '99

23 Sep '99

Thanks for all the help, but no luck. Anyone want to buy a SLIGHTLY USED Cisco 802 router, the customer we bought it for has moved on. Regards, Jim Jim Johnson wrote: > > We are trying to connect a Cisco 802 to our HiperARC chassis using ISDN > and not having much success. > > Mon Radius shows the router authenticated fine. > > Mon PPP shows only an Outgoing PAP AUTH packet on the link. > > The router shows that it was authenticated. > > But then there is no additional PPP traffic. > > Eventually, the ARC gets an incoming LCP TERM packet from the router > when the router decides to close down the link. > > The radius entry for the router is: > > router Password=secret > Framed-IP-Address=xxx.xxx.32.35, > Framed-IP-Netmask=255.255.255.255, > Framed-Route="xxx.xxx.33.8/30 xxx.xxx.32.35 1" > > I'm sure there is something realy simple I am missing here... > > Thanks, > > -Jim Johnson > > - > To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" > with "unsubscribe usr-tc" in the body of the message. > For information on digests or retrieving files and old messages send > "help" to the same address. Do not use quotes in your message. - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.

1 1

(usr-tc) Latest Netserver code?
by Martin Oberle 23 Sep '99

23 Sep '99

Hi, I have to update my Total Control Netserver to be Y2K. I use the Netserver to dial out. I believe someone posted in this list that the netserver code 3.8 (which I think is the newest) has bug and doesn't support dial out. Is this true? Thanks Martin - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.

1 0

Re: (usr-tc) Channelized T1 vs PRI
by Michael DeMan 22 Sep '99

22 Sep '99

Doesn't PRI have some advantages for error checking, etc. Basically it's easier to trace down and correct line noise problems, signal bounces, etc. than a channelized T1? - mike ---------- >From: "Mike McHenry" <mmchen(a)minn.net> >To: <usr-tc(a)lists.xmission.com> >Subject: RE: (usr-tc) Channelized T1 vs PRI >Date: Wed, Sep 22, 1999, 12:04 PM > >You should be able to busy out channels just like you did before with a CT1. >CT1s also support ANI if configured that way from the telco. The only >functionality I figure you will lose is the ability to take incoming 64k >clear channel ISDN calls on your Total Control chassis. > >Mike McHenry > Systems Administrator > MinnNet Communications, Inc. > >-----Original Message----- >From: owner-usr-tc(a)lists.xmission.com >[mailto:owner-usr-tc@lists.xmission.com]On Behalf Of Stainforth, Matthew >Sent: Wednesday, September 22, 1999 1:49 PM >To: 'usr-tc(a)lists.xmission.com' >Subject: RE: (usr-tc) Channelized T1 vs PRI > > > >Part of the reason we're doing this is because CT1 is cheaper but I've never >used CT1 before and I'm wondering what other functionality we're going to >lose. I gather it will no longer be possible to do busy out the channels >from this end and we'll also probably lose ANI too. Are there any other >drawbacks that I might be overlooking? > >On Wednesday, September 22, 1999 3:46 PM, Mike McHenry >[SMTP:mmchen@minn.net] wrote: >> You should be able to use the same code for either a PRI or a channelized >T1 >> on the DSP, just go into the TCM, select the T1 portion of the DSP (top >LED >> below the power LED), click Configure-->Programmed Settings-->Trunk >Settings >> >> You will see a setting called signal mode, it should be set to robbed bit >> for a channelized T1 and message oriented for a PRI. Unless the telco is >> changing other things (ie switch type, etc) that should be the only >setting >> you need to change when the telco changes your PRI to a channelized T1. >> >> Mike McHenry >> Systems Administrator >> MinnNet Communications, Inc. >> >> -----Original Message----- >> From: owner-usr-tc(a)lists.xmission.com >> [mailto:owner-usr-tc@lists.xmission.com]On Behalf Of Stainforth, Matthew >> Sent: Wednesday, September 22, 1999 1:29 PM >> To: 'usr-tc(a)lists.xmission.com' >> Subject: (usr-tc) Channelized T1 vs PRI >> >> >> >> Overnight tonight the telco is changing one of our T1s to channelized T1 >> from PRI service for testing. I seem to remember that there is different >> code for the dual T1/PRI cards depending on which service you have but I'm >> using all DSPs now and I can't seem to have any CT1 specific code for >these >> cards on TotalService. Does the one code base now support both CT1 and >PRI >> or am I missing something? >> >> Thanks... >> >> Matthew >> >> - >> To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" >> with "unsubscribe usr-tc" in the body of the message. >> For information on digests or retrieving files and old messages send >> "help" to the same address. Do not use quotes in your message. >> >> >> - >> To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" >> with "unsubscribe usr-tc" in the body of the message. >> For information on digests or retrieving files and old messages send >> "help" to the same address. Do not use quotes in your message. > > > >- > To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" > with "unsubscribe usr-tc" in the body of the message. > For information on digests or retrieving files and old messages send > "help" to the same address. Do not use quotes in your message. > > >- > To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" > with "unsubscribe usr-tc" in the body of the message. > For information on digests or retrieving files and old messages send > "help" to the same address. Do not use quotes in your message. > - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.

2 1

(usr-tc) Undocumented DSP debug commands
by Campbell Simpson 22 Sep '99

22 Sep '99

Hi Was wondering if anyone out there has had a play around with the "trc" command on the HiPer DSP cards. The docs on the trc command are very brief and was wondering if anyone had a more complete explanation. What I want to be able to do is capture modem data as a call is in progress in a way similar to the Ascend MAX4000. Frantically typing AT commands to capture call info is not my idea of fun! Any help would be much appreciated. Campbell - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.

1 0

RE: (usr-tc) Channelized T1 vs PRI
by Stainforth, Matthew 22 Sep '99

22 Sep '99

Part of the reason we're doing this is because CT1 is cheaper but I've never used CT1 before and I'm wondering what other functionality we're going to lose. I gather it will no longer be possible to do busy out the channels from this end and we'll also probably lose ANI too. Are there any other drawbacks that I might be overlooking? On Wednesday, September 22, 1999 3:46 PM, Mike McHenry [SMTP:mmchen@minn.net] wrote: > You should be able to use the same code for either a PRI or a channelized T1 > on the DSP, just go into the TCM, select the T1 portion of the DSP (top LED > below the power LED), click Configure-->Programmed Settings-->Trunk Settings > > You will see a setting called signal mode, it should be set to robbed bit > for a channelized T1 and message oriented for a PRI. Unless the telco is > changing other things (ie switch type, etc) that should be the only setting > you need to change when the telco changes your PRI to a channelized T1. > > Mike McHenry > Systems Administrator > MinnNet Communications, Inc. > > -----Original Message----- > From: owner-usr-tc(a)lists.xmission.com > [mailto:owner-usr-tc@lists.xmission.com]On Behalf Of Stainforth, Matthew > Sent: Wednesday, September 22, 1999 1:29 PM > To: 'usr-tc(a)lists.xmission.com' > Subject: (usr-tc) Channelized T1 vs PRI > > > > Overnight tonight the telco is changing one of our T1s to channelized T1 > from PRI service for testing. I seem to remember that there is different > code for the dual T1/PRI cards depending on which service you have but I'm > using all DSPs now and I can't seem to have any CT1 specific code for these > cards on TotalService. Does the one code base now support both CT1 and PRI > or am I missing something? > > Thanks... > > Matthew > > - > To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" > with "unsubscribe usr-tc" in the body of the message. > For information on digests or retrieving files and old messages send > "help" to the same address. Do not use quotes in your message. > > > - > To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" > with "unsubscribe usr-tc" in the body of the message. > For information on digests or retrieving files and old messages send > "help" to the same address. Do not use quotes in your message. - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.

5 4

(usr-tc) An odd authentication problem
by Mike McHenry 22 Sep '99

22 Sep '99

For the past several months people have been reporting a LONG delay in authentication after connecting to our modems. Try as I might I couldn't duplicate this until today. Seems that normal PAP authentication works fine. However, about 1/10th of the time that I dial into my USR equipment using a terminal window I experience the problem. Here is what happens, dial into USR, handshake goes well, I am prompted for my login. After entering my username and hitting enter the USR hangs for about a minute before coming back with "Login incorrect" and then prompts me again for my username. It never asks for a password. Watching things on the radius server I see about 30 lines come across my radius logs saying something like "Error: no username: [] (from nas tc-1.minn.net)" Obviously my one minute delay on login is being caused by the USR timing out on this null username request. The question is why is the USR sending a null radius request and timing out on it? It only does this about 1/10th of the time and it never seems to happen when doing straight PAP. Anyone else run into this before? Mike McHenry Systems Administrator MinnNet Communications, Inc. - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.

1 0

(usr-tc) Channelized T1 vs PRI
by Stainforth, Matthew 22 Sep '99

22 Sep '99

Overnight tonight the telco is changing one of our T1s to channelized T1 from PRI service for testing. I seem to remember that there is different code for the dual T1/PRI cards depending on which service you have but I'm using all DSPs now and I can't seem to have any CT1 specific code for these cards on TotalService. Does the one code base now support both CT1 and PRI or am I missing something? Thanks... Matthew - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.

5 4