30 Years of the Digest ... founded August 21, 1981
Add this Digest to your personal
or 
The Telecom Digest for May 28, 2012
Volume 31 : Issue 129 : "text" Format
====== 30 years of TELECOM Digest -- Founded August 21, 1981 ======
|
Telecom and VOIP (Voice over Internet Protocol) Digest for the
Internet. All contents here are copyrighted by Bill Horne and
the individual writers/correspondents. Articles may be used in other
journals or newsgroups, provided the writer's name and the Digest are
included in the fair use quote. By using any name or email address
included herein for any reason other than responding to an article
herein, you agree to pay a hundred dollars to that person, or email address
owner.
Addresses herein are not to be added to any mailing list, nor to be
sold or given away without the explicit written consent of the owner of
that address. Chain letters, viruses, porn, spam, and miscellaneous junk
are definitely unwelcome.
We must fight spam for the same reason we fight crime: not because we
are naive enough to believe that we will ever stamp it out, but because
we do not want the kind of world that results when no one stands
against crime. - Geoffrey Welsh
See the bottom of this issue for subscription and archive details
and the name of our lawyer, and other stuff of interest.
|
Date: Sat, 26 May 2012 19:49:00 -0400
From: Monty Solomon <monty@roscom.com>
To: telecomdigestmoderator.remove-this@and-this-too.telecom-digest.org.
Subject: APPLE-SA-2012-05-07-1 iOS 5.1.1 Software Update
Message-ID: <p06240859cbe7151ef748@[10.0.1.2]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
APPLE-SA-2012-05-07-1 iOS 5.1.1 Software Update
iOS 5.1.1 Software Update is now available and addresses the
following:
Safari
Available for: iPhone 3GS, iPhone 4, iPhone 4S,
iPod touch (3rd generation) and later, iPad, iPad 2
Impact: A maliciously crafted website may be able to spoof the
address in the location bar
Description: A URL spoofing issue existed in Safari. This could be
used in a malicious web site to direct the user to a spoofed site
that visually appeared to be a legitimate domain. This issue is
addressed through improved URL handling. This issue does not affect
OS X systems.
CVE-ID
CVE-2012-0674 : David Vieira-Kurz of MajorSecurity
(majorsecurity.net)
WebKit
Available for: iPhone 3GS, iPhone 4, iPhone 4S,
iPod touch (3rd generation) and later, iPad, iPad 2
Impact: Visiting a maliciously crafted website may lead to a cross-
site scripting attack
Description: Multiple cross-site scripting issues existed in WebKit.
CVE-ID
CVE-2011-3046 : Sergey Glazunov working with Google's Pwnium contest
CVE-2011-3056 : Sergey Glazunov
WebKit
Available for: iPhone 3GS, iPhone 4, iPhone 4S,
iPod touch (3rd generation) and later, iPad, iPad 2
Impact: Visiting a maliciously crafted website may lead to an
unexpected application termination or arbitrary code execution
Description: A memory corruption issue existed in WebKit.
CVE-ID
CVE-2012-0672 : Adam Barth and Abhishek Arya of the Google Chrome
Security Team
Installation note:
This update is only available through iTunes, and will not appear
in your computer's Software Update application, or in the Apple
Downloads site. Make sure you have an Internet connection and have
installed the latest version of iTunes from www.apple.com/itunes/
iTunes will automatically check Apple's update server on its weekly
schedule. When an update is detected, it will download it. When
the iPhone, iPod touch or iPad is docked, iTunes will present the
user with the option to install the update. We recommend applying
the update immediately if possible. Selecting Don't Install will
present the option the next time you connect your iPhone, iPod touch,
or iPad.
The automatic update process may take up to a week depending on the
day that iTunes checks for updates. You may manually obtain the
update via the Check for Updates button within iTunes. After doing
this, the update can be applied when your iPhone, iPod touch, or iPad
is docked to your computer.
To check that the iPhone, iPod touch, or iPad has been updated:
* Navigate to Settings
* Select General
* Select About. The version after applying this update
will be "5.1.1".
Information will also be posted to the Apple Security Updates
web site:
http://support.apple.com/kb/HT1222
This message is signed with Apple's Product Security PGP key,
and details are available at:
https://www.apple.com/support/security/pgp/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.16 (Darwin)
iQEcBAEBAgAGBQJPpBcyAAoJEGnF2JsdZQeexJYH/0aYO0MULFXYARidSV22JdjG
a1+yXKn8Rv2vv+8yStgKK2mWu18hvYWQ+whtvCzs1OefiVsq1nOvdCL1G62ybcYv
O9BiHEDsuu+On2nAPiglu+luokByKLlZcIaM1Qa3pXHkiI8jlH7y7XuuoFsVt1Vc
284JgvV/sHnvesne2GsNyoRBJjfkliqXCgb1zmQWO9xX7HEJCaMNlc5Bwdonm26q
3OEKr2UQxvmWCbnCroiQ5KmEM+gLJSfLLOymow9xa4gM8aM87BXGWNMEKVs8LRLm
dHngmEmzEa/Fx9PnR7rqjTCAMS8hR7aFcCYNTWjfR+keRXx7OHhCm88MfndryS8=
=qhqL
-----END PGP SIGNATURE-----
Date: Sat, 26 May 2012 21:43:59 -0700
From: John David Galt <jdg@diogenes.sacramento.ca.us>
To: telecomdigestmoderator.remove-this@and-this-too.telecom-digest.org.
Subject: Re: From Comcast, TV as data center
Message-ID: <jpsbeh$apl$1@blue-new.rahul.net>
The Globe wrote:
> A new service from cable television giant Comcast Corp. could turn
> the home TV into a home data center, tracking everything from
> business appointments to household security.
We already have this. It's called a PC with Internet service. Many viewers,
including myself, have already taken to using it as a complete substitute for
"television" in all its other forms.
The only remaining step is for the remaining content providers to figure out
that they have more to gain by moving there than by continuing to pretend that
their use of old equipment protects them against copyright infringement.
(Or that their vertical semi-integration with cable and satellite TV companies
can continue to keep them afloat.)
The music and talk shows I care most about, including Glenn Beck, have already
made the move. Most of the rest of us have nothing to lose by following them.
Date: Sat, 26 May 2012 22:43:12 -0400
From: tlvp <mPiOsUcB.EtLlLvEp@att.net>
To: telecomdigestmoderator.remove-this@and-this-too.telecom-digest.org.
Subject: Re: Q.: Message waiting light ... how?
Message-ID: <3o75rtjurspt.1ms2fsbw8ffw4$.dlg@40tude.net>
On 26 May 2012 17:06:48 -0000, John Levine wrote:
>>So, my question is: what sorts of signal on the line might be causing that
>>lamp to light? or to extinguish?
>
> Look up the ADSI standard. There are specific tone signals to turn
> the message waiting light on and off.
>
> R's,
> John
Thanks, John. Actually, ADSI is far too undisambiguated for Google to be
much help. But [ ADSI Message Waiting Signal Standard ] brought up a
Wikipedia article that may well have answered everything I was wondering:
: Some [stand-alone Caller-ID] units will also display the text "MESSAGE WAITING"
: (similar to ADSI-compliant telephones). These units do not use visual FSK to activate
: their red LEDs, but instead, they briefly "pick-up" the line at certain intervals (normally,
: within two minutes of a new call) to check for a "stuttered" dial tone. The presence
: of a stutter dial tone will activate a red LED; while absence will deactivate it.
... both what might cause it to go flashing when there's no voicemail
service for it to be reporting about, and why 5-10 seconds worth of fresh
dial-tone may bring that flashing to a halt.
http://en.wikipedia.org/wiki/Message-waiting_indicator
Cheers, and thanks again, -- tlvp
--
Avant de repondre, jeter la poubelle, SVP.
Date: Sun, 27 May 2012 04:34:34 +0000 (UTC)
From: "Adam H. Kerman" <ahk@chinet.com>
To: telecomdigestmoderator.remove-this@and-this-too.telecom-digest.org.
Subject: Feature Group B CICs and CACs prior to expansion
Message-ID: <jpsasq$r04$3@news.albasani.net>
http://www.atis.org/inc/Docs/finaldocs/CIC-Assignment-Guidelines-Final-Document-05-25-12.doc
I noticed this paper, which includes a short history of Carrier Identification
Code assignments.
CICs identify a carrier. The Carrier Access Code, the actual dialing sequence
used by the calling party, incorporates the CIC.
Prior to April, 1993, CICs were assigned for Fg.B and Fg.D access from the
same pool. Fg.B CIC codes expanded to 4 digits at that time. I was trying
to remember the Fg.B CAC prior to expansion. I thought it was 950-0XXX
where X is any digit 0-9. With expansion, 0 was prepended to CIC.
However, checking the NANPA list, there are also 1XXX CICs, suggesting that
some three-digit CICs had 1 prepended. Prior to expansion, was the CAC also
950-1XXX for certain carriers?
I found a note that 9000 possible CICs can be assigned in Fg.B because
switches cannot distinguish between 950-0XXX and 950-1XXX. Can someone
explain the conflict?
With Fg.B CIC expansion, 5XXX range was opened. 6XXX range will be opened
next, but this range hasn't yet been opened. Then it goes to 2XXX.
In April, 1995, Fg.D codes were expanded to four digits. "0" was prepended
to existing codes, and the CAC changed from 10XXX to 101XXXX. I found a
note that Fg.B CICs as 4 digits could be reserved for Fg.D assignment
after code expansion.
CICs were first assigned in 1981. They were two digits. Were these used
for anything more than intercarrier billing and settlements? Were there
CACs at the time from any exchange?
CICs expanded to three digits in 1983. Was "0" prepended to existing CICs?
Where and when were CACs first dialable as either Fg.B or Fg.D?
How many 950 prefixes were assigned before its use as Fg.B CAC?
Date: Sun, 27 May 2012 09:01:33 -0700 (PDT)
From: "John C. Fowler" <johnfpublic@yahoo.com>
To: telecomdigestmoderator.remove-this@and-this-too.telecom-digest.org.
Subject: Re: Q.: Message waiting light ... how?
Message-ID: <1338134493.9236.YahooMailClassic@web160304.mail.bf1.yahoo.com>
Replying to Message-ID: <1gnfwe7pv4kmy$.h6pz9hyzkp3c.dlg@40tude.net>
tlvp wrote:
> For about a year, now, sporadically, our little ILEC-supplied, stand-alone,
> Caller-ID box has taken to flashing an amber "Message Waiting" light after
> an unanswered inbound call has stopped ringing.
...
> We have no ILEC-supplied voice mail, so there's no actual message awaiting
> us. And going off-hook long enough to hear 5-10 seconds worth of dial tone
> is enough to make that "Message Waiting" lamp turn off.
If this is a regular POTS line from the phone company, chances are the
box is just going off hook and listening for a stutter dial tone, to
indicate a message waiting, any time after the phone has been used. I
have multiple phones with line-in-use indicators, and I see this
happening all the time, where the line-in-use lights up a few seconds
after I hang up, then goes out again after a couple of seconds. I
figure it's one of the phones that has a "Message Waiting" light on
it, checking to see if anyone called while I was on the phone.
If the dial tone is impure or there is some sort of noise going on
during the check, your Caller-ID box might be fooled into thinking
it's a voice mail indication. When you go off hook yourself, it
assumes you've heard the stutter dial tone, so it can turn its light
out now.
Of course, digital lines have a completely different way of doing this.
John C. Fowler, johnfpublic@yahoo.com
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, mostly non-commercial educational
service offered to the Internet by Bill Horne. All the contents
of the Digest are compilation-copyrighted. You may reprint articles in
some other media on an occasional basis, but please attribute my work
and that of the original author.
The Telecom Digest is moderated by Bill Horne.
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 (C) 2012 TELECOM Digest. All rights reserved.
Our attorney is Bill Levant, of Blue Bell, PA.
Finally, the Digest is funded by gifts from generous readers such as
yourself who provide funding in amounts deemed appropriate. Your help
is important and appreciated. A suggested donation of fifty dollars
per year per reader is considered appropriate. See our address above.
Please make at least a single donation to cover the cost of processing
your name to the mailing list.
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.
End of The Telecom Digest (5 messages)
Return to Archives ** Older Issues