33 Years of the Digest ... founded August 21, 1981
Copyright © 2014 E. William Horne. All Rights Reserved.
The Telecom Digest for Dec 7, 2014
|What is right and what is practicable are two different things. - James Buchanan|
See the bottom of this issue for subscription and archive details.
|Date: Fri, 5 Dec 2014 19:49:41 -0500 From: tlvp <mPiOsUcB.EtLlLvEp@att.net> To: firstname.lastname@example.org. Subject: Re: Dialup to 844 # fails at LCP. Is it telecom or server? Message-ID: <email@example.com> On 05 Dec 2014 03:24:36 -0400, Mike Spencer wrote: > I have two dialup ISPs, one of which is working. > Now the [other] telco has dropped out of the deal. [Their phone] > number answers, the modem handshake completes and I get a > connection. Then the server fails to respond in any way to LCP > ConfReq packets. After 10 tries, my pppd client drops the > connection. Fail. [Moderator snip] Most likely there's a subtle change required in the Windows DUN connectoid settings, or their Linux counterparts. Only the ISP can tell you for sure, if you can provide them all the settings you'd been using, and ask them how, if at all, they'd need to be modified. HTH. Cheers, -- tlvp -- Avant de repondre, jeter la poubelle, SVP.|
|Date: Fri, 5 Dec 2014 07:51:00 -0800 (PST) From: Neal McLain <firstname.lastname@example.org> To: email@example.com. Subject: Re: Markey: Fox 25, Verizon need to settle fee beef Message-ID: <firstname.lastname@example.org> On Thursday, December 4, 2014 6:14:48 PM UTC-6, Garrett Wollman wrote: > In article <email@example.com>, > Neal McLain <firstname.lastname@example.org> wrote: > > >And which is the Act that gives 21st Century Fox (owner of WFXT Boston > >"Fox25") the right to demand retransmission consent fees from Verizon? > > > >http://tinyurl.com/27492358 > > > > Fox doesn't own WFXT any more -- they traded it to Cox for KTVU > Oakland and another station in some smaller market I've already > forgotten. So I see. Even their website has gone 404 since my previous post. http://tinyurl.com/27492358 But CJR's "Who Owns What" website hasn't caught up yet. As of 9:45 AM CDT today (12/5/14), WFXT is still on the 21st Century Fox page. http://www.cjr.org/resources/?c=21st_century_fox Neal McLain 12-05-14 0950 CDT|
|Date: Fri, 5 Dec 2014 12:28:33 -0800 From: email@example.com (Dave Platt) To: firstname.lastname@example.org. Subject: Re: Dialup to 844 # fails at LCP. Is it telecom or server? Message-ID: <email@example.com> In article <firstname.lastname@example.org>, Mike Spencer <email@example.com> wrote: >Support at the ISP say, "Gee, it works for me. Must be your >phone line." > >Ha. My phone line works fine for the other dialup ISP, both Win and >Linux. I get the banner text from the new server without funny >chars. My USR modem diagnostics report no blers, no retrains, good >SNR. Carrying a laptop to another phone line in 902-688-nnnn (instead >of my 902-543-nnnn) exchange produces the same good connection with >failure of LCP after the connection. > >Is there any way this could be attributed to the various ways/options >by which toll-free numbers are routed? Or other telco factors that I >don't understand? (And that perhaps the ISP guys don't either?) > >I'd welcome any suggestions that I can pass on to the ISP, either >about getting the 844 number set up right for this purpose or about >configuring the the server to which it connects. Can you "sniff" the serial port connection during the login, and attempt at a PPP handshake? Some dialup servers send the greeting text, require a username/password login, and then start the PPP negotiation and authentication after you've successfully "logged in". Others send the greeting text, wait for a username/password login, but will recognize an LCP "handshake" attempt and will skip around the normal login. You might have a problem in which (1) the new connection requires that your computer send your username/password combination (or some other sentinal) in order to get as far as PPP negotiation, or (2) your computer is already trying to "log in" prior to starting PPP/LCP, but your username/password combination is being rejected. If you aren't seeing bit-level errors, then it's probably not your phone line. One thing you could try - turn off V.42/V.42bis error correction and compression, and try the call again. Dial up the 844 number manually (e.g. using miniterm or kermet) and just observe what happens after you connect and see the banner text. If you see a "}" every few seconds, it's an indication that there is a timing slip somewhere in the connection... two phone switches are talking to one another, but don't have their bit-clocks properly synchronized to a standard source. That can raise hell with a dialup connection... V.42 will try to recover from the injection of bad data, but reliability will suffer.|
TELECOM Digest is an electronic journal devoted mostly to telecom- munications topics. It is circulated anywhere there is email, in addition to Usenet, where it appears as the moderated newsgroup 'comp.dcom.telecom'.
TELECOM Digest is a not-for-profit educational service offered to the Internet by Bill Horne.
The Telecom Digest is moderated by Bill Horne.
43 Deerfield Road
Sharon MA 02067-2301
bill at horne dot net
This Digest is the oldest continuing e-journal about telecomm- unications on the Internet, having been founded in August, 1981 and published continuously since then. Our archives are available for your review/research. We believe we are the oldest e-zine/mailing list on the internet in any category! URL information: http://telecom-digest.org Copyright © 2014 E. William Horne. All rights reserved.
Finally, the Digest is funded by gifts from generous readers such as yourself. Thank you!
All opinions expressed herein are deemed to be those of the author. Any organizations listed are for identification purposes only and messages should not be considered any official expression by the organization.