Re: Suggestions to solve this problem..

On Mon, 23 Jun 2008 11:27:48 -0700, Don Bowey <dbowey@xxxxxxxxxxx>
wrote:

On 6/23/08 10:24 AM, in article bpjv54p1ag3dqh0o89117gaubccnpd3aor@xxxxxxx,
"Jeff Liebermann" <jeffl@xxxxxxxxxx> wrote:

Thank you for the history and clarification. So far, that's the most
coherent explanation I've read describing the terms. Unfortunately,
the supplied documentation isn't anywhere near as clear. To make
things worse, the docs mix in some computer lingo and talk about
"bridging" (a computer term) between ports.

But "bridging" is also sometimes done in the analog world, such as
"bridging" together two compatible phone lines, or bridging one hybrid port
to another, etc.

I hadn't heard the term used for intentionally connecting two lines.
Certainly "bridged taps" which are a different animal.

Fairly close. I worked in the battery room at the Melrose frame in
Smog Angeles. Later punching wires at the Kester frame. A bit of
microwave experience back at Melrose. I had to go back to skool or I
would have been drafted. If you have problems with my credibility,
search Google Groups for posting with my name. (Hmmm... 19,800
articles).
<http://groups.google.com/groups?as_uauthors=Jeff+Liebermann>

Battery rooms of large offices were interesting places. The huge
motor-generator chargers were impressive.

The CO where I worked at didn't have a motor-generator. It was
adjacent to the Smog Angeles main public library, where the noise and
vibration would have caused problems. It was several really big
transformers, cabinets full of some kind of rectifier, and some oil
drum capacitors. Lots of big rheostats, gauges and dials. It's been
so long that I don't recall how it was regulated (or even if it was
regulated). There was some construction in progress around the
battery room, so I was re-assigned to a crew that was "reinforcing"
cable bundles into the Kester Ave CO.

Can you give a link to some of the evil documents? I suspect much of it is
aimed at Engineers rather than end users. As such, digital or not,
transmission coding and signaling and the like must be included.

They're not evil or even horrible. They're just useless.
I'm playing with a Zoom 5801 FXO/FXS box.
<http://www.zoom.com/techsupport/voip/voip_5801.shtml>
and a Linksys/Sipura SPA-921:
<http://www.linksys.com/servlet/Satellite?c=L_Product_C2&childpagename=US%2FLayout&cid=1139435693953&pagename=Linksys%2FCommon%2FVisitorWrapper>
Both devices were apparently intended to be installed by a qualified
and experienced dealer, using pre-configured templates dispensed with
a TFTP server or web server using XML. I'm not sure who is the target
audience of the docs, but it's certainly not the independent end user
trying to make it work without dealer assistance.

I did manage to find some useful hints and setup guides scattered all
over the network. Also, copies of dealer only utilities, which were
somewhat useful.

In the distant past, I taught myself Cisco IOS command line
programming. I've dealt with routers, switches, and gateways, where
the configuration was in the Chinese dialect of English. I've dealt
with really creative SNMP MIB databases. I've even read the IEEE
802.11 docs without having my brain turned to mush. I survived all
these things which required heroics beyond that of the common user.
However, none of these are as cryptic and incomprehensible as the
settings in these VoIP adapters.

I also interrogated my supplier as to the possibility of a VoIP
adapter or phone that was intended to be programmed (provisioned) by
mere mortals. Nope. He said they were all essentially the same.

True. But it's the new service providers who are giving or selling to you,
the poorly written documentation of their services and equipment, not the
telcos. I think there is a propensity for their writers to write a blog
showing how smart they believe themselves to be, rather than to write in
simple terms that can be easily understood. In the Technical Publications I
wrote, I always included a tutorial. The industry owes such thing to their
customers.

I'm not ready too blame anyone for my inability to get the VoIP
adapters working. I think this is just a case of someone taking the
firmware source code defines, and converting that into a giant table
of settings. That works, if the target reader is as knowledgeable as
the original programmer. Let's just say I'm disappointed.

I've written a few manuals on stuff I've designed. I've also edited
quite a few manuals and one book. I tend to learn more by examples
than by explanations. Therefore, I ask for short explanation, but
good examples. My recommended pattern is:
1. One simple example to show the syntax.
2. One useful example to show what can be done. This example should
work and actually do something when invoked.
3. One complex example to show what a power user might find useful.
This has worked well in OS manuals and application manuals. It's a
marginal fit for hardware manuals. Some things, like dial codes,
would do well with 3 such examples. However, the various on/off
settings don't need such detail.

Rant to the people who sell you the service and equipment.

Well, the Linksys came from a vendor on eBay who probably doesn't know
anything. The Zoom came from a friend in the VoIP business who is too
busy to answer my questions, but is trying his best to do so anyway.
You can correctly accuse me of causing my own problems, but that's
that way one learns how this stuff works. (Note that my domain is
LearnByDestroying.com). I've jumped in with both feet into all manner
of unfamiliar waters and never had anywhere as much difficulties as
with these two VoIP adapters.

Midnight and I'm dead tired. Enough ranting for now....

--
Jeff Liebermann jeffl@xxxxxxxxxx
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558
.

Relevant Pages

  • Re: Suggestions to solve this problem..
    ... settings in these VoIP adapters. ... I also interrogated my supplier as to the possibility of a VoIP ... I've written a few manuals on stuff I've designed. ...
    (sci.electronics.design)
  • Re: Suggestions to solve this problem..
    ... coherent explanation I've read describing the terms. ... SIP related settings are negotiated with the service ... I also interrogated my supplier as to the possibility of a VoIP ... I've written a few manuals on stuff I've designed. ...
    (sci.electronics.design)
  • Re: curious about how wireless to wired network bridges work
    ... There are sometimes gems of actual functional info ... Telco manuals are written in a foreign language. ... to be accused of getting into the computah business. ... Sounds like VOIP on landlines is problematic too. ...
    (alt.internet.wireless)
  • Re: Which?
    ... I would have said no. Do you have an explanation? ... There is some disagreement among writing reference manuals about ... when you should capitalize an independent clause following a colon. ... The capitalisation of "scripture" raises my eyebrows further. ...
    (alt.usage.english)
  • Re: VOIP codecs and interoperability (was "Re: my future telephones") [telecom]
    ... VOIP noob question: if a VOIP provider is going to interoperate with an ILEC ... Looking right now at my old AT&T 3B1 manuals and the Voice Power ...
    (comp.dcom.telecom)