January 2004 - USR-TC - mailman.xmission.com

RE: [USR-TC] Login & PW!!!
by Kirti S. Bajwa 09 Jan '04

09 Jan '04

Mike: So clear answer. THANKS. Please answer couple of other questions: Your Suggestion: ================ client 123.123.123.123 { secret = mysecret shortname = nas1 nastype = usrhiper } My "clients.conf" file: ======================= client 12.21.237.0/24 { secret = mysecret shortname = nas1 nastype = tc } 1) There are two HiPer ARC cards, each with two LAN ports for a total of 4 IP addresses. My setting are "clients 12.21.237.0/24". Is there any problem with this? 2) My understanding is that the "nastype" for 3Com HiPer box should be "tc"! Please correct me. Thanks. Kirti -----Original Message----- From: Mike Cisar [mailto:mcisar@iul.net] Sent: Friday, January 09, 2004 3:25 PM To: 'Discussion relating to the 3Com/US Robotics Total Control modemsystems.' Subject: RE: [USR-TC] Login & PW!!! Hi Kirti, > In freeRADIUS file naspasswd (/usr/local/etc/raddb/naspasswd) > has an entry for NAS as follows: > <NAS ip-address> <login-Name> <password> > Is the <NAS ip-address> of NAS is the IP address assigned to > HiPerARC or something else? > What is the <login-Name>? Where is it setup in 3Com TC? > Where is the <password> setup in 3Com TC? > I also notice that in "naspasswd" file the sample > <login-Name> is "!root". I understand the "root" login-Name > but why "!" ahead of it? What does it mean? A couple of things, firstly you don't need to enter anything in the naspasswd file if you are using a USR/3Com HiPER ARC. Those entries were only needed on the older pre-HiPER USR/3Com systems. On those older systems freeradius actually had to telnet in using the special username of !root (which specifically logs you into the terminal server) in order to do some functions such as check which users are online. The HiPER ARC does all of this through SNMP so the entries are no longer needed. About all you need to configure is something like the following into your clients.conf (substituting the IP address of your HiPER ARC, the correct secret and short name)... client 123.123.123.123 { secret = mysecret shortname = nas1 nastype = usrhiper } Cheers, >>>>> Mike <<<<< _______________________________________________ USR-TC mailing list USR-TC(a)mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc

2 1

Login & PW!!!
by Kirti S. Bajwa 09 Jan '04

09 Jan '04

Hello List: This question is for somebody who is using 3Com TC with freeRADIUS!!! In freeRADIUS file naspasswd (/usr/local/etc/raddb/naspasswd) has an entry for NAS as follows: <NAS ip-address> <login-Name> <password> Is the <NAS ip-address> of NAS is the IP address assigned to HiPerARC or something else? What is the <login-Name>? Where is it setup in 3Com TC? Where is the <password> setup in 3Com TC? I also notice that in "naspasswd" file the sample <login-Name> is "!root". I understand the "root" login-Name but why "!" ahead of it? What does it mean? Lots of questions & thanks. Kirti

3 2

RE: [USR-TC] Login & PW!!!
by Kirti S. Bajwa 09 Jan '04

09 Jan '04

Thanks. -----Original Message----- From: Lewis Bergman [mailto:lbergman@wtxs.net] Sent: Friday, January 09, 2004 2:46 PM To: Discussion relating to the 3Com/US Robotics Total Control modem systems. Subject: Re: [USR-TC] Login & PW!!! On Friday 09 January 2004 01:31 pm, Kirti S. Bajwa wrote: > Hello List: > > This question is for somebody who is using 3Com TC with freeRADIUS!!! > > In freeRADIUS file naspasswd (/usr/local/etc/raddb/naspasswd) has an entry > for NAS as follows: > > > <NAS ip-address> <login-Name> <password> > > Is the <NAS ip-address> of NAS is the IP address assigned to HiPerARC or > something else? > What is the <login-Name>? Where is it setup in 3Com TC? > Where is the <password> setup in 3Com TC? > > I also notice that in "naspasswd" file the sample <login-Name> is "!root". > I understand the "root" login-Name but why "!" ahead of it? What does it > mean? I don't use freeRadius but I use ICRadius which was developed by one of the developers of the freeradius deal. I believe that file is only used if you are going to call external scripts that would need to login to the NAS. TC would do most things via SNMP. The "!" is standard programming term for "NOT". As in Don't use the root user and password here because someone might be able to get it, use it, and whipe you out. But, yes, that would normally be the ARC password. -- Lewis Bergman Texas Communications 4309 Maple St. Abilene, TX 79602-8044 915-695-6962 ext 115 _______________________________________________ USR-TC mailing list USR-TC(a)mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc

1 0

RE: [USR-TC] Problems getting DSP's to "Answer"
by Adam Barnhill 06 Jan '04

06 Jan '04

Dial In Address dnis Dial In/Out Trunk Start Signal Type wink Ack Wink On Dial In Address Info Receive Disable I suggest the following: Dial In Address ANI Dial In/Out Trunk Start Signal Type wink Ack Wink On Dial In Address Info Receive Enabled Caller ID is ANI not DNIS. DNIS would be the number dialed, not the customer home number. Generally ANI is not available with CHT-1, four digit DNIS is more common. Verify how many digits are being sent, and make sure the TC config complies. Lastly if you really did mean DNIS, set your modems to respond to it. Go into modem->programmed settings->DNIS Access Codes DNIS default string use AT&N0 I don't have any experience with loop/start configs so, best of luck on that one. -- Adam -----Original Message----- From: usr-tc-bounces+adam=semo.net(a)mailman.xmission.com [mailto:usr-tc-bounces+adam=semo.net@mailman.xmission.com] On Behalf Of Carl Duescher Sent: Tuesday, January 06, 2004 8:56 AM To: usr-tc(a)mailman.xmission.com Subject: [USR-TC] Problems getting DSP's to "Answer" We just started replacing our PM3's with TC1000 boxes. The problem we are having, is when I get the box setup at two seperate locations, the T1's come up and everything looks great, however when you call the box you get nothing but dead air (basically a modem isn't answering). This has happened in two locations, one that is served off a GTD-5 and one is served off a DMS-10. In working with the telco on the DMS-10 switch, we discovered that is the circuit is set to send the digits from the call (caller ID), AND I set the option on the HiperDSP to 'Ack Wink On Dial Address Info' a modem will then answer. Does anyone know if there is a way we could work around this without having the telco change things? Here is how the PM3 is configured followed by my options set in the TC1000 box: PM3 Configuration ---------------------- line0 - T1 Inband DS0 --------------- Status: UP Framing: D4 Encoding: AMI PCM: u-law Signaling: Trunk E&M wink start TC1000 Configuration Framing Mode dsx1D4 Line Coding Options dsx1AMI Circuit Identifier Loopback Configuration dsx1NoLoop Signal Mode robbedBit Transmit Clock Source loopTiming NIC Type longHaul Response to Remote Loopback ignore Jitter Attenuation attenJitterOnRcvr Transmit Line Build Out dB0pt0 Dial In Address dnis Dial In/Out Trunk Start Signal Type wink Ack Wink On Dial In Address Info Receive Disabled Dial Out Address Delay 70 Dial In/Out Trunk Type eAndMTypeII Primary Switch Type priSw5ESS Idle Byte Pattern 254 Receiver Gain dB26 Tone Type dtmf Number of DTMF Tones 4 Send Code dsx1SendNoCode External Signaling Mode (will take effect next boot) none Overlap Receiving Mode disable Overlap Receiving Inbound Digits Expected 12 Overlap Receiving Timeout Delay 12 This is how it is set when we get 'dead air' when calling into the box. In order to get an answer the telco must configure for digits to be sent and as mentioned before, we must enable the ack wink on dial in address info. Here is the config we have on the GTD-5 switch for the PM3's and then followed by the TC1000 box. We get the same problem as we do with the DMS-10, just dead air. I have not worked with the telco on this problem so I don't know if a similiar work around might help but note that the circuits served off the GTD-5 are loop start and not wink. PM3 Config ---------------------- line0 - T1 Inband DS0 --------------- Status: UP Framing: D4 Encoding: AMI PCM: u-law Signaling: FXS loop start TC1000 Config Framing Mode dsx1D4 Line Coding Options dsx1AMI Circuit Identifier Loopback Configuration dsx1NoLoop Signal Mode robbedBit Transmit Clock Source loopTiming NIC Type longHaul Response to Remote Loopback ignore Jitter Attenuation attenJitterOnRcvr Transmit Line Build Out dB0pt0 Dial In Address dnis Dial In/Out Trunk Start Signal Type wink Ack Wink On Dial In Address Info Received disabled Dial Out Address Delay 70 Dial In/Out Trunk Type loopStart Primary Switch Type priSw5ESS Idle Byte Pattern 254 Receiver Gain dB26 Tone Type dtmf Number of DTMF Tones 4 Send Code dsx1SendNoCode External Signaling Mode (will take effect next boot) none Overlap Receiving Mode disable Overlap Receiving Inbound Digits Expected 12 Overlap Receiving Timeout Delay 12 Thank you in advance for any advice you may have. _______________________________________________ USR-TC mailing list USR-TC(a)mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc

2 1

Problems getting DSP's to "Answer"
by Carl Duescher 06 Jan '04

06 Jan '04

We just started replacing our PM3's with TC1000 boxes. The problem we are having, is when I get the box setup at two seperate locations, the T1's come up and everything looks great, however when you call the box you get nothing but dead air (basically a modem isn't answering). This has happened in two locations, one that is served off a GTD-5 and one is served off a DMS-10. In working with the telco on the DMS-10 switch, we discovered that is the circuit is set to send the digits from the call (caller ID), AND I set the option on the HiperDSP to 'Ack Wink On Dial Address Info' a modem will then answer. Does anyone know if there is a way we could work around this without having the telco change things? Here is how the PM3 is configured followed by my options set in the TC1000 box: PM3 Configuration ---------------------- line0 - T1 Inband DS0 --------------- Status: UP Framing: D4 Encoding: AMI PCM: u-law Signaling: Trunk E&M wink start TC1000 Configuration Framing Mode dsx1D4 Line Coding Options dsx1AMI Circuit Identifier Loopback Configuration dsx1NoLoop Signal Mode robbedBit Transmit Clock Source loopTiming NIC Type longHaul Response to Remote Loopback ignore Jitter Attenuation attenJitterOnRcvr Transmit Line Build Out dB0pt0 Dial In Address dnis Dial In/Out Trunk Start Signal Type wink Ack Wink On Dial In Address Info Receive Disabled Dial Out Address Delay 70 Dial In/Out Trunk Type eAndMTypeII Primary Switch Type priSw5ESS Idle Byte Pattern 254 Receiver Gain dB26 Tone Type dtmf Number of DTMF Tones 4 Send Code dsx1SendNoCode External Signaling Mode (will take effect next boot) none Overlap Receiving Mode disable Overlap Receiving Inbound Digits Expected 12 Overlap Receiving Timeout Delay 12 This is how it is set when we get 'dead air' when calling into the box. In order to get an answer the telco must configure for digits to be sent and as mentioned before, we must enable the ack wink on dial in address info. Here is the config we have on the GTD-5 switch for the PM3's and then followed by the TC1000 box. We get the same problem as we do with the DMS-10, just dead air. I have not worked with the telco on this problem so I don't know if a similiar work around might help but note that the circuits served off the GTD-5 are loop start and not wink. PM3 Config ---------------------- line0 - T1 Inband DS0 --------------- Status: UP Framing: D4 Encoding: AMI PCM: u-law Signaling: FXS loop start TC1000 Config Framing Mode dsx1D4 Line Coding Options dsx1AMI Circuit Identifier Loopback Configuration dsx1NoLoop Signal Mode robbedBit Transmit Clock Source loopTiming NIC Type longHaul Response to Remote Loopback ignore Jitter Attenuation attenJitterOnRcvr Transmit Line Build Out dB0pt0 Dial In Address dnis Dial In/Out Trunk Start Signal Type wink Ack Wink On Dial In Address Info Received disabled Dial Out Address Delay 70 Dial In/Out Trunk Type loopStart Primary Switch Type priSw5ESS Idle Byte Pattern 254 Receiver Gain dB26 Tone Type dtmf Number of DTMF Tones 4 Send Code dsx1SendNoCode External Signaling Mode (will take effect next boot) none Overlap Receiving Mode disable Overlap Receiving Inbound Digits Expected 12 Overlap Receiving Timeout Delay 12 Thank you in advance for any advice you may have.

3 10

Does anyone have the model of memory for 333NMC card
by Stephen Rivera - WRCA.Net 05 Jan '04

05 Jan '04

Happy New Years. Looking to see if anyone has the exact memory type for the 333NMC. This is the memory slot module, not the removable 64MB Compactflash(SANDISK). Fits on smaller processing card mounted on main board. Any information would be helpful. Also have immediate need for MultiSpan Cards and 333NMC cards. Good opportunity to cash out on the MultSpans. I will pay you top $$$ ********************************************************************* Steve Rivera IM: srivera711 (877)WRCANET x102 for more product info got www.wrca.net Providing Hardware Solutions Since 1981.

1 0

Problem with NMC card
by Jason Keeling 05 Jan '04

05 Jan '04

I have a new rack I am trying to get up and running, but when I try and set the LAN IP to the desired IP address and save the settings to NVRAM, I get the following error: Error: Networks should be on different Interface Subnets. I've looked around at the other settings (WAN etc.) and all of those are set to a different network address, so I'm not sure what the error involves. Thanks for the help in advance. -- Jason Keeling Texas Communications 1389 N. Harvey Mitchell Pkwy. Bryan, Tx. 77803 979-775-6239 --- [This E-mail was scanned for viruses by Declude Virus]

3 3