<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Back with ISDN, problems--OCLM &#x26; RH328 in ISDN</title>
<link>http://www.dslreports.com/forum/r20762613</link>
<description></description>
<language>en</language>
<pubDate>Fri, 04 Dec 2009 21:06:23 EDT</pubDate>
<lastBuildDate>Fri, 04 Dec 2009 21:06:23 EDT</lastBuildDate>

<item>
<title>Re: Back with ISDN, problems--OCLM &#x26; RH328</title>
<link>http://www.dslreports.com/forum/remark,20768573</link>
<description><![CDATA[<A HREF="/useremail/u/848934"><b>rec9140</b></A> : Plain and simple to do MLPPP on ISDN requires the ISP be setup to handle it.<br><br>The symptoms you post are EXACTLY what you get when your ISP is BROKEN for MLPPP.<br><br>The RAS servers need to be set to <br><br>1) Accept MLPPP<br>2) Accept MLPPP SAME RAS SAME BLADE<br>3) Accept MLPPP SAME RAS DIFFERENT BLADE<br>4) Accept MLPPP DIFFRENENT RAS<br><br>9 out of 10 #3 & #4 is what gets you on busy POP's.<br><br>Many of the POP's are now run by POP aggregators as mentioned and they have intentionally disabled MLPPP. <br><br>MLPPP can be done on either ISDN or V.90/92 aka shotgun modem mode. Many POP providers don't like this as it totally wacks out the normal 10:1 modem ratio many keep on a POP port. Thats why you normally pay quite a bit more for 2B MLPPP ISDN or v.90/92 and even more if you want to hog it 24/7.<br><br>Getting this fixed if its not a local ISP is pretty much going to be a nightmare. Find a LOCAL ISP that has a clue on ISDN and knows how to setup the RAS at their POP. Its not that hard, its actually a few clicks in the setup, but if its not done, your hosed. Also RADIUS needs to be setup to allow this too. Many ISP's get the RADIUS side, but the RAS servers are not setup correctly so things go awry.<br><br>LOCAL ISP's with LOCAL TECH's and their OWN LOCAL POP's are the cure for ISDN. <br><br>When I was forced to use ISDN that was the only way to ensure I got 2B MLPPP service. Finding one can be a real problem now days I am sure, but in rural areas you find dial up (ISDN is really dial up) ISP's tend to prosper and it may be easier. <br><br>Look for ISP's that say local owned and operated and have OWN POP's.<br><small>--<br>Ban all copyright, trademarks, and IP laws!//Lorem ipsum ei pro stet equidem labores, at enim animal expetenda nec. Ea vix argumentum dissentiunt, usu esse ridens ex.</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20768573</guid>
<pubDate>Thu, 10 Jul 2008 07:53:26 EDT</pubDate>
</item>

<item>
<title>Re: Back with ISDN, problems--OCLM &#x26; RH328</title>
<link>http://www.dslreports.com/forum/remark,20768387</link>
<description><![CDATA[<A HREF="/useremail/u/317310"><b>wierdo</b></A> : Isn't the 803 the S/T version of the 804? It won't work unless you buy an NT-1 for it.<br><br>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.<br><br>Luckily, with most PRI-fed equipment, a single channel ISDN connection will just work, it's the multilink that requires configuration.<br><small>--<br>It's w<i>ie</i>rdo, not w<i>ei</i>rdo. Yes, I know that's not the 'proper' spelling of the similar english language word. ;)</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20768387</guid>
<pubDate>Thu, 10 Jul 2008 05:32:54 EDT</pubDate>
</item>

<item>
<title>Re: Back with ISDN, problems--OCLM &#x26; RH328</title>
<link>http://www.dslreports.com/forum/remark,20768104</link>
<description><![CDATA[<A HREF="/useremail/u/695860"><b>Endymion_</b></A> : 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.<br><br>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.<br><br>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. :)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20768104</guid>
<pubDate>Thu, 10 Jul 2008 01:59:02 EDT</pubDate>
</item>

<item>
<title>Re: Back with ISDN, problems--OCLM &#x26; RH328</title>
<link>http://www.dslreports.com/forum/remark,20762664</link>
<description><![CDATA[<A HREF="/useremail/u/317310"><b>wierdo</b></A> : While I can't help with your specific problem, having never owned an OCLM, there's a wealth of info on comp.dcom.isdn. Search that group on google groups.<br><br>I would be surprised if it's a problem with the OCLM, though, since everything I've read praises it for being nearly bulletproof.<br><br>What do the OCLM's logs say? (you may have to turn on debugging or something to get useful logging, I don't know) If it can only log to syslog, that'll make it a bit more interesting, but there seems to be googleable information about how to make OSX's syslog daemon listen on the network.<br><small>--<br>It's w<i>ie</i>rdo, not w<i>ei</i>rdo. Yes, I know that's not the 'proper' spelling of the similar english language word. ;)</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20762664</guid>
<pubDate>Wed, 09 Jul 2008 05:58:45 EDT</pubDate>
</item>

<item>
<title>Back with ISDN, problems--OCLM &#x26; RH328</title>
<link>http://www.dslreports.com/forum/remark,20762613</link>
<description><![CDATA[<A HREF="/useremail/u/695860"><b>Endymion_</b></A> : Well guys, I am back troving for ISDN information. Around 2002 or so I got an ISDN line at my rural home after several years of the runaround from Bellsouth about DSL, when I lived here and used it, it was great, apart from a big phat pipe, everything that I wanted, and all was well.<br><br>Now I've moved away and my mother somehow managed to get DSL for all of a year before Bellsouth, now AT&T, yanked the service after first downgrading it, seems they found that they could divert her slower DSL and get it to new developments (apartments and such with more customers) and make more money than servicing her, so I got her set up with ISDN. (Another chore I'm sure everyone here is familiar with.) I gave my mom the two old routers that I had left, I never got around to selling them on ebay so it's lucky that I kept them around, but I'm having some issues.<br><br>First up, I've gone with netone for the ISP. The tech who set up my account was pretty helpful and even told me he uses ISDN at his home, hopefully this will pan out in the form of more help if I can't get a solution here.<br><br>With my OCLM I cannot get a Multilink connection, no matter what. Some how I do not tend to think this would be netone's fault, as the tech mentioned that he turned on the setting to allow for multiple dial-ins while I was on the phone with him. I can get both B1 and B2 channels to function with the phones on either jack, and B1 or B2 will each work with the netone dial, just not Multilink.<br><br>Second, I tried the RH348. Which I could not honestly remember if I ever managed to get working to my satisfaction before, it was kind of a backup. Anyway, the RH348 creates an ISDN connection with the proper SPID settings, and as near as I can understand the proper Internet Settings and PPP settings via the Telnet (which I have to use, I'm on a Mac here) this router only dials without ever passing that internet connection along to the computer. I've been pulling my hair out over this one as there is nothing obvious, or even obscure that I can find which should be preventing it from giving over that data to the Mac. Oh and, no matter setting for Multilink with the RH348, this router only ever seems to connect with the B1 line as well! Something that leaves me wondering how far I can get if I try problem-solving with netone, what with the OCLM having a similar issue. At least I get an internet connection with the OCLM though!<br><br>On a related note I was looking back at other threads on these two routers and noticed that there is not a single post that goes back further than 2004, meaning a lot of the helpful info that I and several others posted here way back when seems to have fallen off a cliff, I think the furthest back I could click was page 20something. Is all that info gone for good? Seems a shame to see so many faces have disappeared, but even worse that so much good info has vanished.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20762613</guid>
<pubDate>Wed, 09 Jul 2008 04:48:11 EDT</pubDate>
</item>

</channel>
</rss>
