Thanks for your reply Todd, I have connected the two bare wires provided by my telco to the middle two pins of the RJ45 cable that came with the NETServer. When I power up the NETServer, the I-modem lights are solid orange for a few seconds then they rapidly flash orange. (This does not change even if I have the ISDN lines unplugged.) I have tried changing the Switch type, saving the changes with at&w and then resetting the modems with atz!. According to the documentation the lights should follow this pattern: solid orange, rapid orange, slow orange, solid green, off. Once the LED goes off this means they are ready to receive calls. What I am getting after giving the ATZ! command is: solid orange, rapid orange. And that is it. When I issue the ati12 command to the modems the Physical Interface and Data Layer are both INACTIVE. The only thing I haven't looked into is the SPID numbers. We use EURO-ISDN and the documentation says that EURO-ISDN protocol does not require SPIDs. Any ideas on what could be wrong? Many thanks, David. ----- Original Message ----- From: "Support(at)inet2000.com" <support@inet2000.com> To: <dthomas@sunnycyprus.net>; "Discussion relating to the 3Com/US Robotics Total Control modem systems." <usr-tc@mailman.xmission.com> Sent: Tuesday, July 22, 2003 10:19 PM Subject: Re: [USR-TC] USRobotics NETServer/16 I-modem ISDN problem
Hi. We have some MP8 I-Modems, which are a bit different but substantially the same. The first thing I'd check is the cables, since you built them yourself. You should be able to use a standard phone cable for testing. The RJ45 connectors are obviously bigger, but the phone connectors will fit properly in a subset of the connector. Try it and you'll see what I mean.
When you turn them on, it's normal to see a sequence of ORANGE, SLOW BLINKING ORANGE, RED if the modems are not configured yet. Sometimes on ours, the RED is replaced with FAST BLINKING ORANGE, so perhaps that's what you're seeing. ISDN Modems need to be programmed with the right Switch type and most importantly the right SPID number before they will be able to find and sync with the Telco's equipment. Unlike regular modems, you can't simply switch lines around and have them work - you'd need to also re-program each side of your modem, and ISDN Modems have two channels and each needs to be programmed with the right SPID.
Now, perhaps you've already done all this, but I didn't see any other replies and I thought I'd start at the beginning in case you hadn't. :-) -Todd Chamberlain
From: "David Thomas" <dthomas@sunnycyprus.net>
I purchased a USRobotics NETServer/16 I-modem to use with these ISDN lines. The NETServer is using the following firmware/software: NETServer Plus 8/16 - Euro-ISDN only Version: 4.0.14 NETServer Manager Plus 8/16 - Euro-ISDN only Version: 1.1 which I downloaded from 3com's support pages. I have followed the instructions on the NETServer Manager and documentation from the website. I have 4 ISDN BRI lines which were each installed as two bare wires by the local telecom. I have connected these two bare wires to pins 4 and 5 on the RJ-45 cable that came with the unit.
According to the documentation, after connecting the ISDN lines and configuring the I-modems, the LED lights should change from yellow/amber to green and then go off indicating that the lines are ready to receive calls. Also, when the I-modems are issued the ATI12 command the Physical Interface and Data Layer should both be A CTIVE.
However, after following the instructions, the ATI12 command still shows both to be INACTIVE and the LED lights are still flashing yellow, eight per second. I have checked the ISDN line voltage and they are all fine.
I am obviously missing something here. Can anyone offer any assistance and point me in the right direction?
TIA,
Dr. David T. Thomas, Kyrenia, North Cyprus.
_______________________________________________ USR-TC mailing list USR-TC@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc