
From telecom-request@delta.eecs.nwu.edu  Thu Oct 19 20:43:02 1995
by
1995
20:43:02 -0400
telecomlist-outbound; Thu, 19 Oct 1995 15:27:14 -0500
1995
15:27:11 -0500
To: telecom@eecs.nwu.edu


TELECOM Digest     Thu, 19 Oct 95 15:27:00 CDT    Volume 15 : Issue 442

Inside This Issue:                           Editor: Patrick A. Townson

    Austrian Area Codes (was Re: Interface With European Phones) (Wolf 
Paul)
    Who Wants To Be a Spy? (Chris Mathews)
    Which PBXs Have BRIs Compatible With NI-1? (Lars Poulsen)
    Senate Committee Action on Telecom Rewrite (SB 722) (Richard H. 
Stoddard)
    Reverse Engineering Voice Mail (Gene Cartier)
    Large Cell Phone Cloning Operation in NYC Busted (Robert Casey)
    202 (411) - A Telephone Odyssey (Paul L. Moses)
    New Web Site: Emerging Markets Telecom Developments from ITC (Wm.
Thurmond)
    "Merging Your Organization Onto the Internet" Conference (Peter 
Zuckerman)
    Using *69 to Get Callers ID (Glenn Foote)
    PSDN Rates/Billing/Accounting: How Does This All Work (Robert 
Duckworth)
    Payphone Networking Directory (Tom Moylan)
    ADSI Screen Phone Discussion (Marc H. Morin)
    Conference: Number Portability II and Number Administration (Kevin 
Shea)  


TELECOM Digest is an electronic journal devoted mostly but not
exclusively to telecommunications topics. It is circulated anywhere
there is email, in addition to various telecom forums on a variety of
public service systems and networks including Compuserve and America
On Line. It is also gatewayed to Usenet where it appears as the 
moderated
newsgroup 'comp.dcom.telecom'. 

Subscriptions are available to qualified organizations and individual
readers. Write and tell us how you qualify:

                 * telecom-request@eecs.nwu.edu *

The Digest is edited, published and compilation-copyrighted by Patrick
Townson of Skokie, Illinois USA. You can reach us by postal mail, fax 
or phone at:
                    9457-D Niles Center Road
                     Skokie, IL USA   60076
                       Phone: 500-677-1616
                        Fax: 708-329-0572
  ** Article submission address only: telecom@eecs.nwu.edu **

Our archives are located at lcs.mit.edu and are available by using
anonymous ftp. The archives can also be accessed using our email
information service. For a copy of a helpful file explaining how to
use the information service, just ask.

************************************************************************
*
*   TELECOM Digest is partially funded by a grant from the              
*
* International Telecommunication Union (ITU) in Geneva, Switzerland    
* 
* under the aegis of its Telecom Information Exchange Services (TIES)   
* 
* project.  Views expressed herein should not be construed as represent-
*
* ing views of the ITU.                                                 
*
************************************************************************
*

     In addition, TELECOM Digest receives a grant from Microsoft
     to assist with publication expenses. Editorial content in 
     the Digest is totally independent, and does not necessarily
     represent the views of Microsoft. 
     ------------------------------------------------------------

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 twenty dollars
per year per reader is considered appropriate. See our address above.

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.

----------------------------------------------------------------------



Marko Ruokonen <100031.31@compuserve.com> wrote:

> However, Austria has some strange area codes that are different when
> dialed from within Austria then when dialing from abroad. Vienna has
> an area code of 222 when dialed within Austria, but 1 otherwise.

> That is, you dial:

> 0222 yyy when calling Vienna from within Austria, but
> 011 43 1 yyy when calling Vienna from the US.
> I wonder why this is done, but anyway.

> I'm not sure if there are other area codes that are irregular also.

Actually, area code "1" will work for Vienna from within Austria as
well, now.  The reason it didn't work for a while was to accommodate
long dialing sequences to Vienna numbers (i.e. six and seven digit
subscriber numbers with up to four digit extensions) from abroad,
staying within the 15-digit limit which often applies in these
situations, rather sooner than it was possible to switch the
programming in all of Austria's elderly analog switches. So the new
area code was turned on immediately for international calling, and
somewhat later for domestic calling.

Also, Austria has for a number of years had so called "short dialing"
codes whereby Vienna could be reached from several metro areas by
dialling "9" rather than "0222", and these same metro areas could be
reached from Vienna by dialling three-digit codes starting with 9
rather than their 0+3 or 0+4 digit area codes.


W. N. Paul/KSRU * Alcatel Austria AG * Scheydgasse 41 * A-1210 Vienna, 
Austria

wnp@aut.alcatel.at * +43-1-277-22 x2523 (voice)/x118 (fax) * +43-1-774-
1947
(h)

------------------------------



[submittor's note: I copied this from sci.crypt.]

 To:        /sci/crypt

 From misc.job.contract:

New Jersey corp has been asked to define U.S. government electronic
surveillance system to access public telecomm network providers
services/systems.

Expertise of value:  paging/cellular network capabilities/services,
Public data services (e.g. broadband).

Some travel to Wash DC area.

3 openings (Central New Jersey)

Get PGPphone working better soon!!!


patience, persistence, truth,
Dr. mike

------------------------------



My employer is embarking on a search for a new phone system.  Our
corporate parent company has sent us a consultant who specializes in
assisting the local divisions in such efforts, so this is not a
solicitation for proposals. Rather, I want to ask some questions about
ISDN implementations. But first a bit more context.

We need to serve about 40 trunks (10 LEC incoming DID, 10 outgoing
LEC, 10 IXC, 10 to corporate network) by 200 lines for the voice side.

We also would like to integrate about 150 trunks by 200 lines of
ISDN for data use, although we may decide to keep this on a second,
separate switch, because these trunks (6-10 PRIs) and lines will
need to be perpetually reconfigured to serve the lab testing needs
of an engineering group developing ISDN CPE.

But, here is the killer problem: It appears that the ISDN BRI
lines implemented by major PBXs is NOT the same protocol as the 
public ISDN service.

Case in point: We bought a couple of AT&T 8503 voice terminals to play
with on the public network, but it turns out that these can not be
made to work with the public service provided out of an AT&T 5ESS
switch.  (According to the support staff at AT&T's PBX group: This
voice terminal is specifically for use with System 85 and Definity
PBXs.)  This surprising information explains why the manual doesn't
describe how to program a SPID into the units.

But, this would mean that CPE developed for the public network could
not be used on the PBX, either.

Can anyone shed light on this compatibility issue ?


Lars Poulsen   Internet E-mail: lars@RNS.COM
Rockwell Network Systems Phone:        +1-805-562-3158
7402 Hollister Avenue   Telefax:      +1-805-968-8256
Santa Barbara, CA 93117  Internets: designed and built while you wait

------------------------------



The Senate Technology and Energy Committee started going through the
substitute for SB 722 today.  It will reconvene at 8:30am tomorrow
(Thursday, October 19) and will report it out as amended by the end of
the meeting.

The latest word tonight is that full Senate consideration may be moved
up a week and start Tuesday, October 24.

We have made some progress, due in part to the insistence of Rep. Alma
Stallworth (D- Detroit).  The committee adopted some amendments to
Sec. 304B that "make it less bad" but do not solve all of our
concerns. The key changes are as follows:

 1. The call cap was moved up to 400 calls/month.
 2. It restores an unlimited flat rate option.

Our remaining concerns on this section are as follows:

 1. There is no provision that the unlimited option be affordable, and
maybe more importantly, there is no provision that the new 400-call
plan be priced at the level of the current 400-call plan.  Without
that Ameritech could offer us 50 or 100 calls for that rate and
increase the 400-call plan to the point where it isn't a viable
option.
 2. It leaves in provisions for billing based on duration and distance.
As long as Ameritech's goal is to move us in that direction, the
dangers remain.  We are still on the proverbial slippery slope towards
metered service unless those provisions are stricken entirely.

 With these amendments, Sec. 304B reads as follows:

 SEC. 304B.  A PROVIDER OF BASIC LOCAL EXCHANGE SERVICE SHALL DEVELOP
VARIOUS RATE PLANS THAT REFLECT CUSTOMER CALLING PATTERNS THAT SHALL
INCLUDE, BUT NEED NOT BE LIMITED TO,  1 OF THE FOLLOWING AT THE OPTION
OF THE CUSTOMER UNLESS IT IS NOT TECHNOLOGICALLY FEASIBLE:

 (A)  A FLAT RATE ALLOWING UNLIMITED PERSONAL AND DOMESTIC OUTGOING
CALLS.
 (B) A FLAT RATE ALLOWING PERSONAL AND DOMESTIC OUTGOING
CALLS UP TO 400 CALLS PER MONTH PER LINE.  CALLS IN EXCESS OF 400
PER MONTH MAY BE CHARGED AT AN INCREMENTAL RATE AS SET BY THE
PROVIDER UNDER SECTION 304.  IF A CUSTOMER HAS MORE THAN 1 LINE,
THE ALLOWABLE CALLS UNDER THIS SUBDIVISION SHALL BE THE AGGREGATE
OF ALL THE LINES REGARDLESS FROM WHICH LINE THE CALLS ORIGINATE.

 (C) A RATE DETERMINED BY THE TIME DURATION OF SERVICE USAGE
OR THE DISTANCE BETWEEN THE POINTS OF SERVICE ORIGINATION AND
TERMINATION.

 (D) A RATE DETERMINED BY THE NUMBER OF TIMES THE SERVICE IS
USED.

 (E) A RATE THAT INCLUDES 1 OR MORE OF THE RATES ALLOWED BY
THIS SECTION.

 The committee did not address the issue of "rate restructuring" 
in Sec. 304A.  They are quite willing to see rates for residents
outside of the major urban areas increase significantly, perhaps as
much as 200 or 300 percent.

 We honestly believe that if we have REAL competition,
consumers will get better services at lower prices.  But this bill
says that in the name of competition, we are going to double or triple
consumers' rates, but at least they will have a choice of who gouges
them.  That is bad economics and terrible public policy.

 We will continue to push amendments to address these issues and
others.  We will push to have some of them offered during the Senate
debate next week, and we will then start over in the House of
Representatives when it gets there.

 It is important to call your state senator if you have not already
done so.  And if you have, thank you, but please do it again.  We have
to work to improve this bill at every step of the way. We cannot
assume that our concerns will magically be taken care of at some point
down the road.   

 The attention given to these issues online and the calls that
have been generated have clearly had an impact.  But rest assured that
Ameritech will continue to exert its influence at every step and in
between.  Remember, we are dealing with a company that has more
lobbyists than the Big 3 auto companies combined, so we need to keep
it up.  And we need to remind our legislators that it is we, their
constituents, to whom they have to return for re-election.


Richard H. Stoddard                          E-mail: 
stoddard@sojourn.com
Michigan Consumer Federation                         mcf@sojourn.com
Lansing, Michigan

------------------------------



I'm building a Windows NT system to capture and foward voice mail
to other voice mail systems.  Some vendors have been willing to share
their interface specs; others have been less forthcoming.  While some
vendors do support the loose Audio Messaging Interchange Specification
(AMIS) others don't.  Does anyone have any ideas on the best way to
trap the analog and/or digital data exchange between voice mail
products?  Any good tools or recommendations?

You can respond to the group or to me directly and I will make a
summary of the answers.


Gene Cartier
Systems Research & Applications
Arlington, VA    cartierg@sra.com

------------------------------

guest)


Heard on the radio (news program) about a very big cell phone cloning
operation being busted a few days ago.  Something about that their
customers were mostly drug dealers.


[TELECOM Digest Editor's Note: Anyone have anything they care to add on
this?  Any other details known?    PAT]

------------------------------



Well, maybe I've been reading TELECOM Digest too much lately but I had 
an
experience the other day I thought might provide a data point or two for
someone out there.

I live in northern VA and wanted to call an acquaintance in DC, so I 
tried to
call directory assistance.

First try:

1 202 411  ->  interrupt tone.  "We're sorry, your call cannot be 
completed
as dialed..."

then

202 411 -> same interrupt tone and message

then

1 202 555 1212 -> same interrupt tone and message.  Only difference is 
that
the call went through after dialing 1 202 555 for some reason

then

202 555 1212 -> same result

OK.  I now dial "0" and ask the operator.  She connects me to the AT&T
operator, who tells me to use 202 555 1212!

I try again and still nothing.

Finally I called the operator again and this time a different operator
tells me to simply use 411, without an area code.  That worked.

I wonder if the same thing happens from MD (301) to DC, or from DC to
VA or MD?


Paul

------------------------------



                                      



I would like to make my first contribution to this newsgroup.  I have
been working on putting together a web site dedicated to emerging
markets telecommunications developments, located at:

http://www.intl-tech.com

This is International Technology Consultants (Washington, DC) web
site, and includes monthly reports on China, Latin America and East
Europe/NIS as well as links to other sites of interest.

At present, we are establishing links. If you would like to
establish a link with our organization, please e-mail me at :


itcmktg@aol.com

As the site is new, any comments or suggestions regarding the site
would be appreciated. Thanks.


William Thurmond     ITC

------------------------------



                         National Conference on
              MERGING YOUR ORGANIZATION ONTO THE INTERNET
                  Theme: Successful Implementation
                         November 13-16, 1995
     Sheraton National Hotel * Arlington, Va. (Washington, D.C.)

  This Conference Teaches Workable Internet Implementation Solutions

                           ABOUT THE CONFERENCE

SCOPE AND PURPOSE

The conference is organized to benefit both current and prospective
users of the Internet, including executives, managers,
technical/communications specialists and contracting professionals.
Focused workshops explore special interest areas, while the conference
sessions give attendees an opportunity to expand their knowledge of
practical marketing and operating applications, management methods and
technical information.

WHAT YOU WILL LEARN

This intensive program of workshops and conference sessions is designed 
to facilitate usage of the Internet by any organization. It will assist 
your organization in implementing all aspects of a successful Internet 
strategy including:

* Defining the business uses for Internet and developing an integrated
  Internet strategy

* Implementation including: the connection,  servers, user workstations,
  training

* Security considerations and solutions

* Business applications including: marketing, ordering, customer support

* World Wide Web servers and page development.

WHO SHOULD ATTEND:

* Managers and technical staff needing an understanding of the Internet
  potential and usage

* Business and government managers responsible for improving the
  operations of their organizations  

* Private sector executives responsible for marketing products and
  services 

* Operations personnel involved in MIS, IRM, systems operations, network
  management and other aspects of implementing Internet usage.

CONFERENCE VOLUME

Collections of presentation and reference materials will be provided
to each participant of the conference, briefings and technical
workshops.  Participants will also receive "Internet: A Knowledge
Odyssey (Business Edition)," a multimedia reference guide and tutorial
on CD-ROM, designed for business and professional users.

HIGHLIGHTS

27 Plenary and Concurrent Sessions:
* User Track
* Implementation Track
* Applications Track

MANAGEMENT WORKSHOPS:
* Increasing Internet Productivity with the Latest Tools
* Conducting Business Over the Internet
* Developing a Corporate Internet Strategy

TECHNICAL WORKSHOPS:
* Security Systems on the Internet
* Setting Up and Operating Internet Gateways and Web Servers
* Constructing a Successful Web Site

In cooperation with:
D.C. Chapter -- Internet Society
Association of Online Professionals
Capital PC User Group

Conference Management by:
U.S. Professional Development Institute

             FOR ADDITIONAL INFORMATION CONTACT:

Mail:   USPDI, 1738 Elton Road, Suite 304; Silver Spring, MD 20903
Phone:  301/445-4400
Fax:    301/445-5722 
Web:    http://www.clark.net/pub/uspdi/int95.html

------------------------------



      Can someone explain the exact workings of the Ameritech offering
of "Call Back" as it is used from a single residential line.  In my
part of the country, this is the *69 function and calls (dials) the
last person to call you.
 
      According to the friendly people at the business office <humor
here> it works totally in the central office with the person who
initiates the call back hearing _nothing_ until the ringing signal is
passed.  This eliminates the possibility of capturing the actual
number by recording <decoding> the tones.  This is supposedly mandated
by the Ohio Public Utility Commission at the request of those
businesses (battered women and the like) that need this protection.
 
      Is this right, or did something get left out in the explanation.
 
      Comments anyone ??


Glenn "Elephant" Foote ...... glnfoote@freenet.columbus.oh.us

------------------------------



I'm trying to find out more about PSDN but the local telco hasn't
called back :-) I'll keep trying but they seem awfully busy with the
big customers.

As I understand it, the telco has a network and I can use it.

I also understand there are many ways to connect to this network,
SW56, ISDN, T1, PRI, etc, etc.

Now is this an X.25 net or what?  Do I run X.25 with their assigned
addressing?  How do they charge for network usage?

What about all those important things I don't know I should be
asking about?


Bob Duckworth WB4MNF 960 Ralph McGill Blvd. Atlanta GA 30306-4447 
404-888-0389
Internet: gp310ad@prism.gatech.edu -or- rmd@ka4ybr.atlanta.com fax
404-892-2301

------------------------------



Can anyone point me to a directory listing the addresses/email
addresses/ phone numbers of people who have set up and maintain
networks of coin-operated telephones in the U.S.?  I also would like
to find any associations or trade magazines devoted to payphone
management.


Reply to: 

Tom Moylan     tmoylan@crl.com
http://www.harborside.com/tcenter/callcard/

------------------------------



I am interested in getting a discussion going on Analog Display
Services Interface (ADSI).  Here are a few questions to get the
discussion going.

- How is the screen menu updated?  Is it via a 1200 baud modem?
- Are the menu buttons sent back as DTMF keystrokes?
- Does the spec only cover text displays?  How much variation is allowed 
  in the screen phone,  ie.  number of rows and columns?
- What is the mechanism that is used to 'determine' the presence of an 
  ADSI complient device?
- I am aware that Philips and NorTel have ADSI complient devices.  
Anyone 
  else?
- Any input on how the trials are going would be interesting.  Is this 
technology expected to be widely adopted or is it yet another fringe 
technology?


Marc Morin
morin@waterloo.hp.com
519-883-3057

------------------------------



This is an updated change for our Conference "Number Portability II &
Number Administration".

The following information is the correct information.  Only the dates
of the conference have changed due to an unexpected, significant
conflict.

NUMBER PORTABILITY II & NUMBER ADMINISTRATION

Where:  Sheraton Meadowlands Hotel - East Rutherford, New Jersey
When:   November 28 & 29, 1995

Purpose:  To provide an opportunity for attendees to hear from the
experts, focus on the current issues and discuss the critical 
changes facing the industry relating to local competition, number
portability and number administration.

Presenter List and Topics:

John Shea - Principal, JFS Telecom Consulting
 --Introduction and Overview (+)

Christine Walker - US Intelco Networks
 --Overview of the LANP network architecture and activities in the
Rochester NY portion of the New York 
 --State Number Portability Trial.  Are we closer to a national
standard?

Ronald Conners - NANP Administrator, Bellcore
 --Roles and Responsibilities of the current North American Numbering
Plan Administrator and the status of 
 --the FCC Report and Order.  What is the NANC, and what is its role?

Penn Pfautz - DMTS, AT&T
 --Overview of the LRN network architecture and the outlook for
implementation.  What are the --implications of the selection in 
Illinois?

Terry Appenzeller - Vice President-Open Market Strategy, Ameritech
 --Status of the activities at the Illinois Commerce Commission and the
work of the LNP Workshop.  Are we 
 --closer to a national standard?

Alex Harris - Vice President-Regulatory Affairs, MFS Communications
Co.
 --An overview of MFS Communications Co. and plans for 1996.  Where are
the hot spots for competition 
 --and how important is number portability?

Mark Foster - Principal, MFS Associates
 --An infrastructure for number portability administration.  National?
Regional?  Local?

Matthew Harthun - FCC
 --Number Portability from the national regulatory perspective.

John C. Nowell - Andersen Consulting, LLP (invited)
 --Specifics to be announce

One or two more presenters are expected.

For more information, contact Kevin Shea at (201) 535 2765 or email to
telres@Gramercy.ios.com


Kevin Shea
Telecom Research Services
telres@Gramercy.ios.com

------------------------------

End of TELECOM Digest V15 #442
******************************

                                                                     
