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

RE: [USR-TC] Tune-up
by Joel - Fox Computers 29 Jan '05

29 Jan '05

Mine never rings at all, soon as you dial, you hear carrier. Your switch type probably isn't set right yet. Or some other trunk setting is not configured correctly. You did load factory defaults on the DSP? If you didn't, then I'd say you need to. If this happens after you've loaded defaults and set your switch type, then your switch type is probably wrong. You have to understand that there's a LOT more to this than just ringing, answering, and connecting. You can have a lot of things wrong and it will still do that. But if something's wrong you can have the long answering delay, slow modem communication, a lot of disconnects, etc. You have to load defaults and verify the correct switch setting, or you're just asking for problems. - Joel -----Original Message----- From: Kirti S. Bajwa [mailto:kbajwa@tib.com] Sent: Saturday, January 29, 2005 9:21 AM To: 'Discussion relating to the 3Com/US Robotics Total Control modemsystems.' Subject: [USR-TC] Tune-up Hello List: Finally I have 3COM responding to Dial-in & is working. Thank you all for all the help & suggestions. Without your help, I will still be scratching my head. Next question. I notice that when I dial-in, 3COM is letting the phone/connection ring for about 30 seconds before the authentication sequence is started. I have set the modems (HiPer DSP) to answer on the first ring. Why does it take so long? Are there any tune-up settings for 3COM? Kirti _______________________________________________ USR-TC mailing list USR-TC(a)mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc

1 0

Tune-up
by Kirti S. Bajwa 29 Jan '05

29 Jan '05

Hello List: Finally I have 3COM responding to Dial-in & is working. Thank you all for all the help & suggestions. Without your help, I will still be scratching my head. Next question. I notice that when I dial-in, 3COM is letting the phone/connection ring for about 30 seconds before the authentication sequence is started. I have set the modems (HiPer DSP) to answer on the first ring. Why does it take so long? Are there any tune-up settings for 3COM? Kirti

1 0

RE: [USR-TC] Authentication
by Joel - Fox Computers 27 Jan '05

27 Jan '05

Lewis is correct. What you are calling "hashed" is CHAP, and what you are calling "cleartext" is PAP. Most ISP's RADIUS servers I've ever dealt with (including my own) use PAP. For Dialup Internet, you rarely need the level of security provided by CHAP. On top of that, most people with in-place RADIUS servers have them set up for PAP. I believe that in order to use CHAP your RADIUS needs to store the passwords differently, and this can require removing and re-adding all of the users for an existing RADIUS server (at least I know that's the case with Win2K IAS). So most people just use PAP. But the default on the TC is CHAP. To change it - do this your ARC: set ppp receive_authentication pap save all Then you should be able to authenticate without a problem. On the ARC, to test authentication without actually dialing up, enter the command: _auth username password It should come back with either Authenticated or Not and you'll know it's working. - Joel -----Original Message----- From: Kirti S. Bajwa [mailto:kbajwa@tib.com] Sent: Wednesday, January 26, 2005 4:23 PM To: 'Discussion relating to the 3Com/US Robotics Total Control modemsystems.' Subject: RE: [USR-TC] Authentication Hello List: I want to educate myself about 'cleartext password' or 'hashed password' authentication. Here is the problem: I am trying to setup a 3com NAS & a (freshly installed) RADIUS (freeRADIUS) authentication server. I tested the RADIUS server by 'radtest' and then 'NTRagPing' utility. The RADIUS server authenticates like a charm. Then I tried to dial-in to test that 3COM is doing its job. The authentication is rejected. It seems that the RADIUS server is expecting password in 'cleartext' format but is not getting them in that from 3COM. Please, help me with the following: (1) How & what format (cleartext or hashed)the passwords is passed from 3COM NAS to Radius Server? (2) Where is the setting for 'cleartext' or 'hashed' password in 3COM? Is it in HiPer NMC or HiPer ARC settings? I have read the documents for the last 3 days and have not found the answer. Thanks. Kirti _______________________________________________ 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] Authentication
by Kirti S. Bajwa 26 Jan '05

26 Jan '05

Hello List: I want to educate myself about 'cleartext password' or 'hashed password' authentication. Here is the problem: I am trying to setup a 3com NAS & a (freshly installed) RADIUS (freeRADIUS) authentication server. I tested the RADIUS server by 'radtest' and then 'NTRagPing' utility. The RADIUS server authenticates like a charm. Then I tried to dial-in to test that 3COM is doing its job. The authentication is rejected. It seems that the RADIUS server is expecting password in 'cleartext' format but is not getting them in that from 3COM. Please, help me with the following: (1) How & what format (cleartext or hashed)the passwords is passed from 3COM NAS to Radius Server? (2) Where is the setting for 'cleartext' or 'hashed' password in 3COM? Is it in HiPer NMC or HiPer ARC settings? I have read the documents for the last 3 days and have not found the answer. Thanks. Kirti

2 1

RE: [USR-TC] add DNS host
by Kirti S. Bajwa 26 Jan '05

26 Jan '05

Todd: I am testing these servers. They are not operational yet. They are on our internal network sitting behind a firewall therefore not accessable at this time. The IP addresses may change. I listed the IP addresses as planned when these servers become production servers. Thank you. Kirti -----Original Message----- From: Todd Bertolozzi [mailto:berto@core.com] Sent: Wednesday, January 26, 2005 3:35 PM To: Discussion relating to the 3Com/US Robotics Total Control modemsystems. Subject: Re: [USR-TC] add DNS host Looking at this again I'm confused on what the ip of your dns servers are. You're going to want to use the "correct" ip which is something below: ns1.tibinternet.net 12.21.237.10 ns2.tibinternet.net 12.21.237.11 ns1.tibinternet.net (first dns server) listens on eth0:1 12.21.237.20 ns2.tibinternet.net (second dns server) listens on eth0:1 12.21.237.21 I don't get any of them to resolve nor ping. Todd ----- Original Message ----- From: "Todd Bertolozzi" <berto(a)core.com> To: "Discussion relating to the 3Com/US Robotics Total Control modemsystems." <usr-tc(a)mailman.xmission.com> Sent: Wednesday, January 26, 2005 3:07 PM Subject: Re: [USR-TC] add DNS host > To be honest I'm not real sure what the difference between add dns host and > add dns server is. Based on what you've said this is what I would do: > > add dns server 12.21.237.20 preference 1 name "ns1.tibinternet.net" > add dns server 12.21.237.21 preference 2 name "ns2.tibinternet.net" > set dns domain_name tibinternet.net > save all > > To verify what the above did on your hiperarc try these: > > list dns servers > show dns settings > resolve name www.google.com > > Todd > > > ----- Original Message ----- > From: "Kirti S. Bajwa" <kbajwa(a)tib.com> > To: "'Discussion relating to the 3Com/US Robotics Total Control > modemsystems.'" <usr-tc(a)mailman.xmission.com> > Sent: Wednesday, January 26, 2005 2:48 PM > Subject: RE: [USR-TC] add DNS host > > > > Hello List: > > > > I am setting HiPer ARC and need help in setting up dns host. Here is > better > > explanation: > > > > I have the following servers: > > > > fw.tibinternet.net 12.21.237.9 > > ns1.tibinternet.net 12.21.237.10 > > ns2.tibinternet.net 12.21.237.11 > > rdx.tibinternet.net 12.21.237.12 > > mail.tibinternet.net 12.21.237.13 > > data.tibinternet.net 12.21.237.14 > > > > I am using djbDNS software for my DNS application. (if you are not > familiar > > with djbDNS, please see http://cr.yp.to/djbdns.html) In djbDNS, DNS Cache > > server is called 'dnscache' and runs on a server and listens to DNS > queries > > on a dedicated IP address. My DNS server settings are as follows: > > > > ns1.tibinternet.net (first dns server) listens on eth0:1 12.21.237.20 > > ns2.tibinternet.net (second dns server) listens on eth0:1 12.21.237.21 > > > > My questions is; when I 'add dns host' on HiPer ARC, which IP address > should > > I use? > > > > Is it the IP address of the server (12.21.237.10/11) or IP address on > which > > DNS server (dnscache) listens on (12.21.237.20/21)? > > > > Thank you in advance. > > > > Kirti > > > > > > _______________________________________________ > > USR-TC mailing list > > USR-TC(a)mailman.xmission.com > > http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc > > > > > _______________________________________________ > USR-TC mailing list > USR-TC(a)mailman.xmission.com > http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc > _______________________________________________ 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] add DNS host
by Kirti S. Bajwa 26 Jan '05

26 Jan '05

Hello List: I am setting HiPer ARC and need help in setting up dns host. Here is better explanation: I have the following servers: fw.tibinternet.net 12.21.237.9 ns1.tibinternet.net 12.21.237.10 ns2.tibinternet.net 12.21.237.11 rdx.tibinternet.net 12.21.237.12 mail.tibinternet.net 12.21.237.13 data.tibinternet.net 12.21.237.14 I am using djbDNS software for my DNS application. (if you are not familiar with djbDNS, please see http://cr.yp.to/djbdns.html) In djbDNS, DNS Cache server is called 'dnscache' and runs on a server and listens to DNS queries on a dedicated IP address. My DNS server settings are as follows: ns1.tibinternet.net (first dns server) listens on eth0:1 12.21.237.20 ns2.tibinternet.net (second dns server) listens on eth0:1 12.21.237.21 My questions is; when I 'add dns host' on HiPer ARC, which IP address should I use? Is it the IP address of the server (12.21.237.10/11) or IP address on which DNS server (dnscache) listens on (12.21.237.20/21)? Thank you in advance. Kirti

2 2

WTB: USR Hiper DSP E1 cards
by Stephen Rivera - WRCA.Net 25 Jan '05

25 Jan '05

PN's vary based on what you have. I'm interest in any or all of these. 69-003456-00 Total Control E1 HiPer DSP NAC 69-002072-00 Total Control E1 HiPer DSP NAC w/ daughtarcard 993787-00 Total Control E1 HiPer DSP Card Set R2-CAS 992267-00 Hiper DSP E1 - 30 Channel Modem card set Let me know what you have. Must be working. Steve Rivera WR Consultant Associates, Inc. Dir: 732-833-2111 x102 IM: srivera711 www.wrca.net Providing Network Hardware Since 1981.

1 0

RE: [USR-TC] RE: Busy signal!!!
by Kirti S. Bajwa 25 Jan '05

25 Jan '05

Joel: I just changed on setting, the "Primary Switch Type" and the 'Busy Signal' is gone. Thanks again. Kirti Joel: Thank you for your suggestions. I plan to setup/test 3Com by following them. One question: How to reset Hiper DSL to factory defaults? Thanks again. Kirti -----Original Message----- From: Joel - Fox Computers [mailto:jfox@foxcomputers.com] Sent: Sunday, January 23, 2005 7:05 PM To: Discussion relating to the 3Com/US Robotics Total Control modemsystems. Subject: RE: [USR-TC] RE: Busy signal!!! Importance: High Kirti - Here's the thing with getting PRI's going, and although I don't consider myself an "expert", to my knowledge and from my experience, this is all there is to it: 1. Reset your Hiper DSP(s) to factory defaults, and reset it. 2. Go into the Trunk Settings on the DSP and set the "Primary Switch Type" to whatever kind of switch the telco is using. (This is usually the one and only piece of info you need to know, as far as trunk settings). Save your settings and do a hardware reset on the card. (FYI - in my experience, all of those trunk settings on the DSP are really only needed for CT1's. PRI's are more standardized and always work with the default settings. The only thing you have to change is the switch type, which I believe basically determines the messaging protocol on the D-channel or something like that.) ALSO... note that sometimes the telco will tell you the wrong switch type. For example, they may say it's a 5ESS, which it may physically be a 5ESS, but if they configured your PRI as what they call "standard", it's actually running as an NI2. On a 5ESS switch, they have to configure your PRI as what they call a "custom" in order for 5ESS to be the correct setting. I think we had a similar confusion with a DMS100 one time also, if I remember correctly. I gather that from things I've heard that NI2 is like an old standard, and a lot of different switches support NI2 and a lot telcos still provision PRI's as NI2 PRI's. ONE More thing - I've found that even with the wrong switch type specified, a lot of times the line will still ring. It can still cause busy signals, but more often strange things like intermittent drop out on your D-channel, calls not hanging up, or other funny things happening. But when you've got a constant busy signal on the line, it usually ends up being an ARC issue. 3. Once the DSP card reboots, it should take calls. If it does you're done. If it still doesn't, then the problem is with your Hiper ARC, go on to step 4. 4. If you have only more than one Hiper ARC, take one of them out of the machine. (technically, this is just to avoid conflicts related to chassis awareness, card ownership, whatever. If you need both ARC's, you can configure and put the second one back in after you get the chassis taking calls). 5. Connect a terminal to the serial port on the ARC that's in the machine. Enter the command "delete config" and "Y" when prompted. This will reboot the ARC with factory defaults. 6. When the ARC starts up and prompts you, go through the "Quick Setup" and do the most-simple, most basic config you can. Give it an IP address, default Gateway, a radius server, admin password, dns servers, and an IP address pool. When asked if you want to use chassis awareness, answer YES for now. (This should work fine with just one ARC). When it's all done, do a "save all" and then a "reboot". 7. When the Hiper ARC is rebooted, and comes back to a "Hiper>>" prompt, try to dial it. If it rings, you're working, now just finish configuring the ARC, or delete the config again and set it up the way you want. If it still gives a busy signal, go on to step 8. 8. Disable NMC chassis awareness. To do this, enter the command "disable nmc chassis", press enter, then use the "reboot" command to reboot the Hiper ARC. 9. After the ARC boots, enter the following commands: set chassis slot 1-14 card hdm_24 ports 23 own y save all reboot 10. This time, when the ARC reboots, it should ring. If not, there's something wrong with the PRI from the Telco, wrong with your DSP card(s), or wrong with your Hiper ARC. If you have a second ARC, you might try pulling out the one you have in now and putting in the one you took out in step 4, and then follow steps 5-9 again and see if it works this time. In addition - should say, I prefer to have the latest TCS 4.5 code on the cards before doing this. Now - this may all seem simplified, and depending on how much of the config you do to the ARC, it may or may not work. But these steps DO get the PRI to ring in EVERY time, as long as you don't have broken hardware and you know the correct switch type at the telco. Hope that helps. - Joel -----Original Message----- From: Kirti S. Bajwa [mailto:kbajwa@tib.com] Sent: Sunday, January 23, 2005 5:31 PM To: 'usr-tc(a)mailman.xmission.com' Subject: FW: [USR-TC] RE: Busy signal!!! Hello List: I did not receive any response to my post. In my last discussion with Sprint, they informed me that there is no setting they normally provide for an ISDN-PRI's. I have been changing settings to see if something works. I have some new findings: (1) I can test the 3Com with a UID/PW by using the "_auth UID PW" command (2) When I connect a ISDN-PRI line into HiPer DSP, the D-Channel gets locked. Then when I dial-into the line, it is /busy/. Is this information sufficient for somebody to give some hints? Thanks in advance. Kirti -----Original Message----- From: Kirti S. Bajwa [mailto:kbajwa@tib.com] Sent: Thursday, January 20, 2005 1:36 PM To: 'Discussion relating to the 3Com/US Robotics Total Control modem systems.' Subject: RE: [USR-TC] RE: Busy signal!!! Hello list: I am dead end. I posted this message over two months ago. I still have not been able to get settings from the telco (Sprint). Is there anybody in Tennessee who has a ISDN-PRI line (1D+23B) from Sprint? If you do, I appreciate if I can get the settings for the trunk from you!! If somebody has any other suggestion please let me know. Please respond. Thanks in advance. Kirti -----Original Message----- From: Todd Bertolozzi [mailto:berto@core.com] Sent: Wednesday, November 24, 2004 1:48 PM To: Discussion relating to the 3Com/US Robotics Total Control modemsystems. Subject: Re: [USR-TC] RE: Busy signal!!! I'd try to verify the dsp span settings with the telco. In particular things such as dnis/ani and the number of digits being sent by the switch. If you aren't on the same page with the telco as far as though settings go you can get busy signals. Todd ----- Original Message ----- From: "Kirti S. Bajwa" <kbajwa(a)tib.com> To: "'Discussion relating to the 3Com/US Robotics Total Control modemsystems.'" <usr-tc(a)mailman.xmission.com> Sent: Wednesday, November 24, 2004 12:42 PM Subject: RE: [USR-TC] RE: Busy signal!!! > Todd: > > Thank you for your reply. > > chassis awareness is ENABLED > list chassis does show port 23 > > Any other suggestion? > > Kirti > > -----Original Message----- > From: Todd Bertolozzi [mailto:berto@core.com] > Sent: Wednesday, November 24, 2004 11:52 AM > To: Discussion relating to the 3Com/US Robotics Total Control > modemsystems. > Subject: Re: [USR-TC] RE: Busy signal!!! > > > There could be a variety of things that cause this. How do you have your > chassis awareness setup? > > When you're in the arc and do a list chassis command does everything look > correct as far as number of ports=23, etc? > > Todd > ----- Original Message ----- > From: "Kirti S. Bajwa" <kbajwa(a)tib.com> > To: "'Discussion relating to the 3Com/US Robotics Total Control > modemsystems.'" <usr-tc(a)mailman.xmission.com> > Sent: Wednesday, November 24, 2004 11:20 AM > Subject: [USR-TC] RE: Busy signal!!! > > > > Hello List: > > > > I finally got 3Com box (1-HiPer NMC, 2-Hiper ARC & 10-Hiper DSP) setup. > > Today, I connected a T1-PRI ISDN line to test. But as soon as I connect, > the > > line gives busy signal. > > > > What setting causes this. /Please Help/. Thank you in advance. > > > > Kirti > > > > _______________________________________________ > > USR-TC mailing list > > USR-TC(a)mailman.xmission.com > > http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc > > > > > _______________________________________________ > USR-TC mailing list > USR-TC(a)mailman.xmission.com > http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc > > _______________________________________________ > USR-TC mailing list > USR-TC(a)mailman.xmission.com > http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc > _______________________________________________ USR-TC mailing list USR-TC(a)mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc _______________________________________________ USR-TC mailing list USR-TC(a)mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc _______________________________________________ USR-TC mailing list USR-TC(a)mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc _______________________________________________ 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] RE: Busy signal!!!
by Kirti S. Bajwa 24 Jan '05

24 Jan '05

Joel: Thank you for your suggestions. I plan to setup/test 3Com by following them. One question: How to reset Hiper DSL to factory defaults? Thanks again. Kirti -----Original Message----- From: Joel - Fox Computers [mailto:jfox@foxcomputers.com] Sent: Sunday, January 23, 2005 7:05 PM To: Discussion relating to the 3Com/US Robotics Total Control modemsystems. Subject: RE: [USR-TC] RE: Busy signal!!! Importance: High Kirti - Here's the thing with getting PRI's going, and although I don't consider myself an "expert", to my knowledge and from my experience, this is all there is to it: 1. Reset your Hiper DSP(s) to factory defaults, and reset it. 2. Go into the Trunk Settings on the DSP and set the "Primary Switch Type" to whatever kind of switch the telco is using. (This is usually the one and only piece of info you need to know, as far as trunk settings). Save your settings and do a hardware reset on the card. (FYI - in my experience, all of those trunk settings on the DSP are really only needed for CT1's. PRI's are more standardized and always work with the default settings. The only thing you have to change is the switch type, which I believe basically determines the messaging protocol on the D-channel or something like that.) ALSO... note that sometimes the telco will tell you the wrong switch type. For example, they may say it's a 5ESS, which it may physically be a 5ESS, but if they configured your PRI as what they call "standard", it's actually running as an NI2. On a 5ESS switch, they have to configure your PRI as what they call a "custom" in order for 5ESS to be the correct setting. I think we had a similar confusion with a DMS100 one time also, if I remember correctly. I gather that from things I've heard that NI2 is like an old standard, and a lot of different switches support NI2 and a lot telcos still provision PRI's as NI2 PRI's. ONE More thing - I've found that even with the wrong switch type specified, a lot of times the line will still ring. It can still cause busy signals, but more often strange things like intermittent drop out on your D-channel, calls not hanging up, or other funny things happening. But when you've got a constant busy signal on the line, it usually ends up being an ARC issue. 3. Once the DSP card reboots, it should take calls. If it does you're done. If it still doesn't, then the problem is with your Hiper ARC, go on to step 4. 4. If you have only more than one Hiper ARC, take one of them out of the machine. (technically, this is just to avoid conflicts related to chassis awareness, card ownership, whatever. If you need both ARC's, you can configure and put the second one back in after you get the chassis taking calls). 5. Connect a terminal to the serial port on the ARC that's in the machine. Enter the command "delete config" and "Y" when prompted. This will reboot the ARC with factory defaults. 6. When the ARC starts up and prompts you, go through the "Quick Setup" and do the most-simple, most basic config you can. Give it an IP address, default Gateway, a radius server, admin password, dns servers, and an IP address pool. When asked if you want to use chassis awareness, answer YES for now. (This should work fine with just one ARC). When it's all done, do a "save all" and then a "reboot". 7. When the Hiper ARC is rebooted, and comes back to a "Hiper>>" prompt, try to dial it. If it rings, you're working, now just finish configuring the ARC, or delete the config again and set it up the way you want. If it still gives a busy signal, go on to step 8. 8. Disable NMC chassis awareness. To do this, enter the command "disable nmc chassis", press enter, then use the "reboot" command to reboot the Hiper ARC. 9. After the ARC boots, enter the following commands: set chassis slot 1-14 card hdm_24 ports 23 own y save all reboot 10. This time, when the ARC reboots, it should ring. If not, there's something wrong with the PRI from the Telco, wrong with your DSP card(s), or wrong with your Hiper ARC. If you have a second ARC, you might try pulling out the one you have in now and putting in the one you took out in step 4, and then follow steps 5-9 again and see if it works this time. In addition - should say, I prefer to have the latest TCS 4.5 code on the cards before doing this. Now - this may all seem simplified, and depending on how much of the config you do to the ARC, it may or may not work. But these steps DO get the PRI to ring in EVERY time, as long as you don't have broken hardware and you know the correct switch type at the telco. Hope that helps. - Joel -----Original Message----- From: Kirti S. Bajwa [mailto:kbajwa@tib.com] Sent: Sunday, January 23, 2005 5:31 PM To: 'usr-tc(a)mailman.xmission.com' Subject: FW: [USR-TC] RE: Busy signal!!! Hello List: I did not receive any response to my post. In my last discussion with Sprint, they informed me that there is no setting they normally provide for an ISDN-PRI's. I have been changing settings to see if something works. I have some new findings: (1) I can test the 3Com with a UID/PW by using the "_auth UID PW" command (2) When I connect a ISDN-PRI line into HiPer DSP, the D-Channel gets locked. Then when I dial-into the line, it is /busy/. Is this information sufficient for somebody to give some hints? Thanks in advance. Kirti -----Original Message----- From: Kirti S. Bajwa [mailto:kbajwa@tib.com] Sent: Thursday, January 20, 2005 1:36 PM To: 'Discussion relating to the 3Com/US Robotics Total Control modem systems.' Subject: RE: [USR-TC] RE: Busy signal!!! Hello list: I am dead end. I posted this message over two months ago. I still have not been able to get settings from the telco (Sprint). Is there anybody in Tennessee who has a ISDN-PRI line (1D+23B) from Sprint? If you do, I appreciate if I can get the settings for the trunk from you!! If somebody has any other suggestion please let me know. Please respond. Thanks in advance. Kirti -----Original Message----- From: Todd Bertolozzi [mailto:berto@core.com] Sent: Wednesday, November 24, 2004 1:48 PM To: Discussion relating to the 3Com/US Robotics Total Control modemsystems. Subject: Re: [USR-TC] RE: Busy signal!!! I'd try to verify the dsp span settings with the telco. In particular things such as dnis/ani and the number of digits being sent by the switch. If you aren't on the same page with the telco as far as though settings go you can get busy signals. Todd ----- Original Message ----- From: "Kirti S. Bajwa" <kbajwa(a)tib.com> To: "'Discussion relating to the 3Com/US Robotics Total Control modemsystems.'" <usr-tc(a)mailman.xmission.com> Sent: Wednesday, November 24, 2004 12:42 PM Subject: RE: [USR-TC] RE: Busy signal!!! > Todd: > > Thank you for your reply. > > chassis awareness is ENABLED > list chassis does show port 23 > > Any other suggestion? > > Kirti > > -----Original Message----- > From: Todd Bertolozzi [mailto:berto@core.com] > Sent: Wednesday, November 24, 2004 11:52 AM > To: Discussion relating to the 3Com/US Robotics Total Control > modemsystems. > Subject: Re: [USR-TC] RE: Busy signal!!! > > > There could be a variety of things that cause this. How do you have your > chassis awareness setup? > > When you're in the arc and do a list chassis command does everything look > correct as far as number of ports=23, etc? > > Todd > ----- Original Message ----- > From: "Kirti S. Bajwa" <kbajwa(a)tib.com> > To: "'Discussion relating to the 3Com/US Robotics Total Control > modemsystems.'" <usr-tc(a)mailman.xmission.com> > Sent: Wednesday, November 24, 2004 11:20 AM > Subject: [USR-TC] RE: Busy signal!!! > > > > Hello List: > > > > I finally got 3Com box (1-HiPer NMC, 2-Hiper ARC & 10-Hiper DSP) setup. > > Today, I connected a T1-PRI ISDN line to test. But as soon as I connect, > the > > line gives busy signal. > > > > What setting causes this. /Please Help/. Thank you in advance. > > > > Kirti > > > > _______________________________________________ > > USR-TC mailing list > > USR-TC(a)mailman.xmission.com > > http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc > > > > > _______________________________________________ > USR-TC mailing list > USR-TC(a)mailman.xmission.com > http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc > > _______________________________________________ > USR-TC mailing list > USR-TC(a)mailman.xmission.com > http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc > _______________________________________________ USR-TC mailing list USR-TC(a)mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc _______________________________________________ USR-TC mailing list USR-TC(a)mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc _______________________________________________ USR-TC mailing list USR-TC(a)mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc _______________________________________________ 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] RE: Busy signal!!!
by Joel - Fox Computers 24 Jan '05

24 Jan '05

Kirti - Here's the thing with getting PRI's going, and although I don't consider myself an "expert", to my knowledge and from my experience, this is all there is to it: 1. Reset your Hiper DSP(s) to factory defaults, and reset it. 2. Go into the Trunk Settings on the DSP and set the "Primary Switch Type" to whatever kind of switch the telco is using. (This is usually the one and only piece of info you need to know, as far as trunk settings). Save your settings and do a hardware reset on the card. (FYI - in my experience, all of those trunk settings on the DSP are really only needed for CT1's. PRI's are more standardized and always work with the default settings. The only thing you have to change is the switch type, which I believe basically determines the messaging protocol on the D-channel or something like that.) ALSO... note that sometimes the telco will tell you the wrong switch type. For example, they may say it's a 5ESS, which it may physically be a 5ESS, but if they configured your PRI as what they call "standard", it's actually running as an NI2. On a 5ESS switch, they have to configure your PRI as what they call a "custom" in order for 5ESS to be the correct setting. I think we had a similar confusion with a DMS100 one time also, if I remember correctly. I gather that from things I've heard that NI2 is like an old standard, and a lot of different switches support NI2 and a lot telcos still provision PRI's as NI2 PRI's. ONE More thing - I've found that even with the wrong switch type specified, a lot of times the line will still ring. It can still cause busy signals, but more often strange things like intermittent drop out on your D-channel, calls not hanging up, or other funny things happening. But when you've got a constant busy signal on the line, it usually ends up being an ARC issue. 3. Once the DSP card reboots, it should take calls. If it does you're done. If it still doesn't, then the problem is with your Hiper ARC, go on to step 4. 4. If you have only more than one Hiper ARC, take one of them out of the machine. (technically, this is just to avoid conflicts related to chassis awareness, card ownership, whatever. If you need both ARC's, you can configure and put the second one back in after you get the chassis taking calls). 5. Connect a terminal to the serial port on the ARC that's in the machine. Enter the command "delete config" and "Y" when prompted. This will reboot the ARC with factory defaults. 6. When the ARC starts up and prompts you, go through the "Quick Setup" and do the most-simple, most basic config you can. Give it an IP address, default Gateway, a radius server, admin password, dns servers, and an IP address pool. When asked if you want to use chassis awareness, answer YES for now. (This should work fine with just one ARC). When it's all done, do a "save all" and then a "reboot". 7. When the Hiper ARC is rebooted, and comes back to a "Hiper>>" prompt, try to dial it. If it rings, you're working, now just finish configuring the ARC, or delete the config again and set it up the way you want. If it still gives a busy signal, go on to step 8. 8. Disable NMC chassis awareness. To do this, enter the command "disable nmc chassis", press enter, then use the "reboot" command to reboot the Hiper ARC. 9. After the ARC boots, enter the following commands: set chassis slot 1-14 card hdm_24 ports 23 own y save all reboot 10. This time, when the ARC reboots, it should ring. If not, there's something wrong with the PRI from the Telco, wrong with your DSP card(s), or wrong with your Hiper ARC. If you have a second ARC, you might try pulling out the one you have in now and putting in the one you took out in step 4, and then follow steps 5-9 again and see if it works this time. In addition - should say, I prefer to have the latest TCS 4.5 code on the cards before doing this. Now - this may all seem simplified, and depending on how much of the config you do to the ARC, it may or may not work. But these steps DO get the PRI to ring in EVERY time, as long as you don't have broken hardware and you know the correct switch type at the telco. Hope that helps. - Joel -----Original Message----- From: Kirti S. Bajwa [mailto:kbajwa@tib.com] Sent: Sunday, January 23, 2005 5:31 PM To: 'usr-tc(a)mailman.xmission.com' Subject: FW: [USR-TC] RE: Busy signal!!! Hello List: I did not receive any response to my post. In my last discussion with Sprint, they informed me that there is no setting they normally provide for an ISDN-PRI's. I have been changing settings to see if something works. I have some new findings: (1) I can test the 3Com with a UID/PW by using the "_auth UID PW" command (2) When I connect a ISDN-PRI line into HiPer DSP, the D-Channel gets locked. Then when I dial-into the line, it is /busy/. Is this information sufficient for somebody to give some hints? Thanks in advance. Kirti -----Original Message----- From: Kirti S. Bajwa [mailto:kbajwa@tib.com] Sent: Thursday, January 20, 2005 1:36 PM To: 'Discussion relating to the 3Com/US Robotics Total Control modem systems.' Subject: RE: [USR-TC] RE: Busy signal!!! Hello list: I am dead end. I posted this message over two months ago. I still have not been able to get settings from the telco (Sprint). Is there anybody in Tennessee who has a ISDN-PRI line (1D+23B) from Sprint? If you do, I appreciate if I can get the settings for the trunk from you!! If somebody has any other suggestion please let me know. Please respond. Thanks in advance. Kirti -----Original Message----- From: Todd Bertolozzi [mailto:berto@core.com] Sent: Wednesday, November 24, 2004 1:48 PM To: Discussion relating to the 3Com/US Robotics Total Control modemsystems. Subject: Re: [USR-TC] RE: Busy signal!!! I'd try to verify the dsp span settings with the telco. In particular things such as dnis/ani and the number of digits being sent by the switch. If you aren't on the same page with the telco as far as though settings go you can get busy signals. Todd ----- Original Message ----- From: "Kirti S. Bajwa" <kbajwa(a)tib.com> To: "'Discussion relating to the 3Com/US Robotics Total Control modemsystems.'" <usr-tc(a)mailman.xmission.com> Sent: Wednesday, November 24, 2004 12:42 PM Subject: RE: [USR-TC] RE: Busy signal!!! > Todd: > > Thank you for your reply. > > chassis awareness is ENABLED > list chassis does show port 23 > > Any other suggestion? > > Kirti > > -----Original Message----- > From: Todd Bertolozzi [mailto:berto@core.com] > Sent: Wednesday, November 24, 2004 11:52 AM > To: Discussion relating to the 3Com/US Robotics Total Control > modemsystems. > Subject: Re: [USR-TC] RE: Busy signal!!! > > > There could be a variety of things that cause this. How do you have your > chassis awareness setup? > > When you're in the arc and do a list chassis command does everything look > correct as far as number of ports=23, etc? > > Todd > ----- Original Message ----- > From: "Kirti S. Bajwa" <kbajwa(a)tib.com> > To: "'Discussion relating to the 3Com/US Robotics Total Control > modemsystems.'" <usr-tc(a)mailman.xmission.com> > Sent: Wednesday, November 24, 2004 11:20 AM > Subject: [USR-TC] RE: Busy signal!!! > > > > Hello List: > > > > I finally got 3Com box (1-HiPer NMC, 2-Hiper ARC & 10-Hiper DSP) setup. > > Today, I connected a T1-PRI ISDN line to test. But as soon as I connect, > the > > line gives busy signal. > > > > What setting causes this. /Please Help/. Thank you in advance. > > > > Kirti > > > > _______________________________________________ > > USR-TC mailing list > > USR-TC(a)mailman.xmission.com > > http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc > > > > > _______________________________________________ > USR-TC mailing list > USR-TC(a)mailman.xmission.com > http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc > > _______________________________________________ > USR-TC mailing list > USR-TC(a)mailman.xmission.com > http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc > _______________________________________________ USR-TC mailing list USR-TC(a)mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc _______________________________________________ USR-TC mailing list USR-TC(a)mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc _______________________________________________ USR-TC mailing list USR-TC(a)mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc

1 0