Dialuphell
join:2006-01-29
|  New ISDN Service
I recently scored a couple new Cisco 804 routers off of ebay and just signed up with ATT IOC-S ISDN service. Trying to configure the router with the Cisco Fast Step software, it can not find the switch information. I entered this info manually, and it errors out stating that it can not make an ISDN call. It recommends that I check the cables and or call ATT. Anybody have any suggestions? How do I know that I have ISDN service to the NID on the side of my house? I tried the other router, and it does the same. I swapped a couple wires around on my side of the NID, and verified that I can get POTS service on the line in the house that I intended on using for ISDN.
Any suggestions are appreciated |
|
ahammer
join:2008-01-06
Maricopa, AZ | do you have the console cable?..
seems like a dumb ? but just make sure becuse that console port is not a ethernet port. |
|
Splitpair
Premium
join:2000-07-29
Cow Towne | reply to Dialuphell
Has AT&T installed the ISDN yet?
Wayne |
|
Dialuphell
join:2006-01-29
| reply to Dialuphell
Well I finally got the ISDN line working to the house. ATT had some additional work to do on their end after they said that It was operational. (I have to say that the $137 install fee was well spent taking into account that it took 1-2 technicians almost a week non-stop to get the line to work.)
New problem...
I signed up with LocalNet ISP. I configured the Cisco 804 using the FastStep software. Surfing the internet does not work using the web site name, nor does punching in the IP directly into the browser. I can not ping a web site using the name but can using the IP address. The modem shows that channel 1 is connected. The internet does work when dialing the ISP using the analog modem in the tower. I can call out using an analog phone plugged into the phone ports in the back of the modem. What should I try next? |
|
wierdo
join:2001-02-16
Tulsa, OK
 ·Future Nine Corpor..
·Teliax VOIP
| said by Dialuphell  :Well I finally got the ISDN line working to the house. ATT had some additional work to do on their end after they said that It was operational. (I have to say that the $137 install fee was well spent taking into account that it took 1-2 technicians almost a week non-stop to get the line to work.) New problem... I signed up with LocalNet ISP. I configured the Cisco 804 using the FastStep software. Surfing the internet does not work using the web site name, nor does punching in the IP directly into the browser. I can not ping a web site using the name but can using the IP address. The modem shows that channel 1 is connected. The internet does work when dialing the ISP using the analog modem in the tower. I can call out using an analog phone plugged into the phone ports in the back of the modem. What should I try next? You either need to manually set the DNS server addresses on your computer or configure the router's DHCP server with them. I think you can do that in Fast Step, but I'm not sure.
If you know how to use the console, log in, type 'sh run' and look for the line that says 'ip dhcp pool something'. When you find it, go into enable mode ('enable', and type in your password), then type 'ip dhcp pool something', where something is what you saw in the running configuration. Then type 'dns-server dns-server-ip-1 dns-server-ip-2' (replace the italicized bits with your actual DNS server addresses, you can enter one to eight addresses). After that, hit control Z to exit configuration mode.
Renew your address on your computer (in most versions of window typing 'ipconfig /renew' will do the trick, if not, use windows' repair feature) Make sure everything works. If so, type 'copy run start' to make the running configuration the startup configuration. If not, reboot the router and your old configuration will be restored.
Cisco's DHCP configuration guide is here. It details all the options, although some probably don't apply to the 804, the ones you need should be the same.
--
It's wierdo, not weirdo. Yes, I know that's not the 'proper' spelling of the similar english language word.  |
|
Dialuphell
join:2006-01-29
1 edit | reply to Dialuphell
Thanks everybody for all of the help... ATT finally got the ISDN line working after about 2 weeks and I needed about 2 weeks to get the 804 configured.
I still have a question. I signed up for IOC S thru ATT. I configured the 804 to drop a line if a voice call is being made or received. The router will drop the call for an outbound call but when someone calls, and I am on the 'puter, the caller will only receive a busy signal. Is this normal with ATT, IOC S, ISDN, and or the Cisco 804?
Thanks! |
|
wierdo
join:2001-02-16
Tulsa, OK
·Future Nine Corpor..
·Teliax VOIP
| said by Dialuphell :Thanks everybody for all of the help... ATT finally got the ISDN line working after about 2 weeks and I needed about 2 weeks to get the 804 configured. I still have a question. I signed up for IOC S thru ATT. I configured the 804 to drop a line if a voice call is being made or received. The router will drop the call for an outbound call but when someone calls, and I am on the 'puter, the caller will only receive a busy signal. Is this normal with ATT, IOC S, ISDN, and or the Cisco 804? You need 'additional call offering' to get that functionality. (Essentially, it's what they call call waiting on ISDN) It's nice, because it won't drop a channel until you actually pick up the phone, so if you decide not to answer, you never drop back to 64k.
I don't recall there being any configuration in IOS needed to enable it, but it's been a long time, so I may have just forgotten.
--
It's wierdo, not weirdo. Yes, I know that's not the 'proper' spelling of the similar english language word. |
|
