how-to block ads
|
Endymion_
join:2002-09-28
Walls, MS
| reply to wierdo
Re: Back with ISDN, problems--OCLM & RH328
Well I solved most of the problem I've been having, by switching ISPs. As soon as the line was installed out here, I had signed up with Netone. The site looked pretty impressive as they explicitly support ISDN, and the tech that set up the account for me stated he had no problem with the dual-channel connection. Unfortunately however, there was only one usable number at my location--I'm just one mile south of Memphis, Tennessee, and as we're so close to town, our CO is actually there. (As a side note, this let us get Tennessee rates for ISDN, about half as much as the Mississippi rate.) The Netone tech told me that if I did not dial in to a number with the same area code as my ISDN number(s) that typically, the ISDN connection would fail. Two numbers in the area that are local calls were in the Memphis area code 901, the other two that were in Mississippi and local to me were 662 area codes--the ISDN line's area codes are 662 as well. So the Memphis 901 numbers did not work at all, and neither did one of the Mississippi 662 numbers. I would get no connection at all with them.
So the whole time I was troubleshooting this with both routers, I could only get a working connection with one of Netone's local numbers. On a whim, and bearing in mind cautions people have mentioned here in the past, I signed up an account with Localnet. Localnet had one Mississippi 662 number local to me, it connected but once again, no Multilink. So, I tried one of the four Memphis 901 numbers, and wouldn't you know it but the first 901 number I dialed to made a multilink connection on the first try? Something tells me that the CO location may have more to do with this than the area code, although I have a Mississippi area code I know for a fact my CO is in Tennessee/Memphis. But then again it's anybody's guess why the heck I couldn't get any connection at all with Netone's Memphis numbers.
I really should have thought to try another ISP sooner when I had this kind of trouble, I am kicking myself for not thinking of it earlier, especially after all the stuff I went through using ISDN years ago. Now if I could just figure out what's up with the Netgear RH348 I would feel a lot more comfortable. I may kick it to the curb though as I've just grabbed a new Cisco 803 and a used Cisco 804, maybe not necessary but I just want to have a backup. I remember having to live without ISDN for a couple of weeks once upon a time, when lightning destroyed an OCLM I was using. Hate to go through that again.  | |
wierdo
join:2001-02-16
Tulsa, OK
 ·Future Nine Corpor..
·Teliax VOIP
| Isn't the 803 the S/T version of the 804? It won't work unless you buy an NT-1 for it.
As far as changing POPs solving your multilink issues, I'm not at all surprised that many of them no longer work right. It's a rare use, and almost all ISPs are now outsourcing their modem banks to third parties who might not even have that use in mind.
Luckily, with most PRI-fed equipment, a single channel ISDN connection will just work, it's the multilink that requires configuration.
--
It's wierdo, not weirdo. Yes, I know that's not the 'proper' spelling of the similar english language word.  | |
-
|
