Acceleport RAS 8 won't accept incoming calls?

I’ve got a major problem with my RAS card…
We’ve just moved premises at work, and since we’ve moved, I cannot get the RAS card to work properly. The RAS ports do not seem to see incoming calls - the phone line just rings and rings.

I have one port working on it - but this is only because I’ve put an external modem between the card itself, and the socket in the wall - I’m sure that with the old setup, we just plugged the phonelines direct from the RAS card into the wall sockets.

I have no clue when it comes to modems as to what to do with them. I know that we have moved exchanges since we’ve moved - could this be the source of my problem?? Can anyone suggest what I can check, or what settings I might need to change in order to resolve this problem??

Thanks,

Sarah

I’m not sure what operating system you’re using, but generally speaking, you’ll want to open the modem port with a terminal emulation program. In Windows you could use Hyperterminal, in Unix flavors you could “cu” to the modem.

Once connected, issue command AT, you should see an “OK” result. If you get that, try dialing into that line from some other modem, you should see “RING” repeated over each time it rings. If you see that, issue command ATA and the modem should answer.

If any part of what I listed above fails, which part and what do you see instead?

Sarah,

You should look at the service that is using the modems of the RAS/8 adapter. For example in Windows 2000 the service is called “Routing and Remote Access”. This service needs to be running with out errors to accept the inbound calls. If you suspect hardware issues then a manual test of the modem using something like HyperTerminal or CU to verify that you can see the RING of an inbound call. For additional troubleshooting assistance, Please Contact Digi Tech Support using the on-line E-Service form.

http://www.digi.com/support/eservice/eservicelogin.jsp

I’m using Win2k server SP4

I couldn’t find hyperterminal on my system?
Tried telnetting etc but it won’t work

I’ve queried the modem (port 6) via the device manager, and this is the part of the log file which shows the query:

07-22-2004 11:10:47.828 - TSP(0000): Making call
07-22-2004 11:10:47.828 - Passthrough On
07-22-2004 11:10:47.828 - TSP(0000): LINEEVENT: LINECALLSTATE_CONNECTED
07-22-2004 11:10:53.890 - TSP(0000): Dropping call
07-22-2004 11:10:53.890 - Passthrough Off
07-22-2004 11:10:53.890 - 57600,8,N,1, ctsfl=1, rtsctl=2
07-22-2004 11:10:53.937 - Initializing modem.
07-22-2004 11:10:53.937 - TSP(0000): Closing Call
07-22-2004 11:10:53.953 - Send: AT
07-22-2004 11:10:54.203 - Recv: OK
07-22-2004 11:10:54.203 - Interpreted response: OK
07-22-2004 11:10:54.218 - Send: AT &F E0 V1 &D2 &C1 S0=0 S95=41
07-22-2004 11:10:54.484 - Recv: OK
07-22-2004 11:10:54.484 - Interpreted response: OK
07-22-2004 11:10:54.500 - Send: ATS7=120S30=0L3M1\N3%C3&K3B0N1X3
07-22-2004 11:10:54.765 - Recv: OK
07-22-2004 11:10:54.765 - Interpreted response: OK
07-22-2004 11:10:54.765 - Waiting for a call.
07-22-2004 11:10:54.781 - Send: ATS0=0
07-22-2004 11:10:55.015 - Recv: OK
07-22-2004 11:10:55.015 - Interpreted response: OK
07-22-2004 11:10:55.015 - TSP(0000): LINEEVENT: LINECALLSTATE_DISCONNECTED(0x1)
07-22-2004 11:10:55.015 - TSP(0000): LINEEVENT: LINECALLSTATE_IDLE
07-22-2004 11:11:10.375 - 57600,8,N,1, ctsfl=1, rtsctl=2
07-22-2004 11:11:10.390 - Initializing modem.
07-22-2004 11:11:10.406 - Send: AT
07-22-2004 11:11:10.671 - Recv: OK
07-22-2004 11:11:10.671 - Interpreted response: OK
07-22-2004 11:11:10.687 - Send: AT &F E0 V1 &D2 &C1 S0=0 S95=41
07-22-2004 11:11:10.953 - Recv: OK
07-22-2004 11:11:10.953 - Interpreted response: OK
07-22-2004 11:11:10.968 - Send: ATS7=120S30=0L3M1\N3%C3&K3B0N1X3
07-22-2004 11:11:11.234 - Recv: OK
07-22-2004 11:11:11.234 - Interpreted response: OK
07-22-2004 11:11:11.234 - Waiting for a call.
07-22-2004 11:11:11.250 - Send: ATS0=0
07-22-2004 11:11:11.484 - Recv: OK
07-22-2004 11:11:11.484 - Interpreted response: OK
07-22-2004 11:12:27.609 - TSP(0000): Making call
07-22-2004 11:12:27.609 - Passthrough On
07-22-2004 11:12:27.609 - TSP(0000): LINEEVENT: LINECALLSTATE_CONNECTED
07-22-2004 11:12:33.453 - TSP(0000): Dropping call
07-22-2004 11:12:33.453 - Passthrough Off
07-22-2004 11:12:33.453 - 57600,8,N,1, ctsfl=1, rtsctl=2
07-22-2004 11:12:33.500 - Initializing modem.
07-22-2004 11:12:33.500 - TSP(0000): Closing Call
07-22-2004 11:12:33.515 - Send: AT
07-22-2004 11:12:33.750 - Recv: OK
07-22-2004 11:12:33.750 - Interpreted response: OK
07-22-2004 11:12:33.765 - Send: AT &F E0 V1 &D2 &C1 S0=0 S95=41
07-22-2004 11:12:34.031 - Recv: OK
07-22-2004 11:12:34.031 - Interpreted response: OK
07-22-2004 11:12:34.046 - Send: ATS7=120S30=0L3M1\N3%C3&K3B0N1X3
07-22-2004 11:12:34.312 - Recv: OK
07-22-2004 11:12:34.312 - Interpreted response: OK
07-22-2004 11:12:34.312 - Waiting for a call.
07-22-2004 11:12:34.328 - Send: ATS0=0
07-22-2004 11:12:34.578 - Recv: OK
07-22-2004 11:12:34.578 - Interpreted response: OK
07-22-2004 11:12:34.578 - TSP(0000): LINEEVENT: LINECALLSTATE_DISCONNECTED(0x1)
07-22-2004 11:12:34.578 - TSP(0000): LINEEVENT: LINECALLSTATE_IDLE

Thanks,

Sarah

Um, I feel very silly now that I’ve discovered what the problem is!!

I didn’t realise that phone cables and modem cables use different pins…and yes, I was using a phone cable…so obvisouly the card would never detect a call coming in because the call was coming in on the wrong pins…

Thank you all for your help!!!

Sarah