Slimelite BBS

7 [1 of 14] ISDN FAQ

Back to CYBERSPACE

From Dave Osborne · 1996-04-04 02:35 · #75335 in CYBERSPACE

"Bob Larribeau" <p00136@psilink.com>
"David E. Martin" <dem@hep.net>
------------------------------

2.16) Data Encapsulation for IP over ISDN

A decision was made at the Amsterdam IETF to state that all systems
wishing to guarantee IP interoperability should implement PPP.  Such
systems may also implement the Frame Relay or X.25 encapsulations, and
an RFC will be published delineating how, when it is known that the
encapsulations are limited to that set of three, they may be
distinguished by examination of the first correctly checksummed and
HDLC bit-stuffed packet.

Many implementations are using PPP so that they can negotiate
compression and/or multilink operation.

There is an Internet Draft from the Point-to-Point Protocol Working
Group of the Internet Engineering Task Force that describes the use of
PPP over ISDN.  This draft is named draft-ietf-pppext-isdn-NN.txt in
the internet-drafts Shadow Directories on nic.ddn.mil, nnsc.nsf.net,
nic.nordu.net, ftp.nisc.sri.com, munnari.oz.au, Germany.EU.net and on
many, many other mirror archives.  This is also discussed in RFC 1356
by Malis, et. al.

A common practice in most European countries is raw IP packets
delimited by HDLC flags.  Another common practice is an encapsulation
using simple HDLC in layer 1, X.75 (LAPB, usually I-frames) in layer 2
and, sometimes, T.70 in layer 3.  PPP is used instead of HDLC/X.75/T.70
when the network doesn't provide the callers telephone number eg. when
emulating a modem or the callers number is lost on telephone company
borders.  In this case, caller authentication is done via PAP/CHAP
instead.

sklower@toe.CS.Berkeley.EDU (Keith Sklower)
cherkus@UniMaster.COM (Dave Cherkus)
kumquat@hill.com (Gary C. Kessler)
muftix@junior.bintec.de (Juergen Ernst Guenther)
cabo@Informatik.Uni-Bremen.DE (Carsten)
------------------------------

2.17) Full Motion Video over ISDN

In ISDN, video isn't a "service being offered" - at least not for
low/midrange quality. You buy the proper equipment for both
subscribers, plug it in, and place the call. Just like speaking French
on ISDN isn't something being offered - it is something you just do,
yourself.

Video telephony over narrowband ISDN is governed by a suite of ITU-T
(formerly CCITT) interoperability standards.  The overall video
telephony suite is known informally as p * 64 (and pronounced
'p star 64'), and formally as standard H.320.   H.320 is an "umbrella"
standard;  it specifies H.261 for video compression, H.221, H.230, and
H.242 for communications, control, and indication, G.711, G.722, and
G.728 for audio signals, and several others for specialized purposes.
A common misconception, exploited by some equipment manufacturers, is
that compliance with H.261 (the video compression standard) is enough
to guarantee interoperability.

Bandwidth can be divided up among video, voice, and data in a
bewildering variety of ways.  Typically, 56kbps might be allocated to
voice, with 1.6kbps to signalling (control and indication signals) and
the balance allocated to video.

An H.320-compatible terminal can support audio and video in one B
channel using G.728 audio at 16 kb/s.  For a 64 kb/s channel, this
leaves 46.4 kb/s for video (after subtracting 1.6 kb/s for H.221
framing).

The resolution of a H.261 video image is either 352x288 (known as CIF)
or 176x144 (known as quarter-CIF or QCIF).  The frame rate can be
anything from 30 frames/second and down.  Configurations typically use
a 2B (BRI) or a 6B (switched-384 or 3xBRI with an inverse multiplexer)
service, depending on the desired cost and video quality. In a 384kbps
call, a video conferencing system can achieve 30 frames/second at CIF,
and looks comparable to a VHS videotape picture. In a 2B BRI call, a
standard video phone can achieve 15 frames/second at CIF.

Those who have seen the 1B video call in operation generally agree that
the quality is not sufficient for anything useful like computer based
training - only for the social aspect of being able to *see* Grandma as
well as hear her (sort of like the snapshot pictures you make with that
$5 camera with no controls).

A 2B picture, on the other hand, is for all practical purposes
sufficient for remote education, presentations etc. Rapidly changing
scenes are still not very well handled, but as soon as the picture
calms down, the sharpness and color quality are impressive (considering
that only two plain phone channels are being used). With 2B+D being the
standard BRI, this kind of picturephone will be usable "everywhere"
(including private homes).

However, it should still be noted that 6xB or H0 does allow for dramatic
improvement in picture quality compared to 2xB.  In particular, H.320
video/audio applications will often allocate 56kbps for audio, leaving
only 68.8kbps for video when using 2xB.  On the other hand, using H0
would get you 326.4kbps for video with 56kbps for audio. Alternative
audio algorithms can improve picture quality over 2xB by not stealing
as many bits.  Note that 6B is not identical to H0; the latter is a
single channel which will give you 80kbps above that of six separate B
channels.  Inverse multiplexors can be used to combine B channels.

ketil@edb.tih.no (Ketil Albertsen,TIH)
kevin@newshost.pictel.com (Kevin Davis)
oj@vivo.com (Oliver Jones)
mikes2@cc.bellcore.com (Mike Souryal)
------------------------------

2.18) What is a SPID? How come my ISDN device won't work without one?

SPIDs are Service Profiles IDs.  SPIDs are used to identify what sort
of services and features the switch provides to the ISDN device.
Currently they are used only for circuit-switched service (as opposed
to packet-switched).  Annex A to ITU recommendation Q.932 specifies the
(optional) procedures for SPIDs.  They are most commonly implemented by
ISDN equipment used in North America.


When a new subscriber is added, the telco personnel allocate a SPID
just as they allocate a directory number.  In many cases, the SPID
number is identical to the (full ten digit) directory number.  In other
cases it may be the directory number concatinated with various other
strings of digits, such as digits 0100 or 0010,  1 or 2 (indicating the
first or second B channel on a non-centrex line), or 100 or 200 (same
idea but on a centrex line) or some other, seemingly arbitrary string.
Some people report SPIDs of the form 01nnnnnnn0 for  AT&T custom and
01nnnnnnn011 for NI-1, where n is the seven digit directory number.
It is all quite implementation dependent.

The subscriber needs to configure the SPID into their terminal (i.e.
computer or telephone, etc., not their NT-1 or NT-2) before they will
be able to connect to the central office switch.

When the subscriber plugs in a properly configured device to the line,
Layer 2 initialization takes place, establishing the basic transport
mechanism.  However if the subscriber has not configured the given SPID
into their ISDN device, the device will not perform layer 3
initialization and the subscriber will not be able to make calls.  This
is, unfortunately, how many subscribers discover they need a SPID.

Once the SPID is configured, the terminals go through an
initialization/identification state which has the terminal send the
SPID to the network in a Layer 3 INFOrmation message whereby the
network responds with an INFO message with the EID information element
(ie). Thereafter the SPID is not sent again to the switch. The switch
may send the EID or the Called Party Number (CdPN) in the SETUP message
to the terminal for the purpose of terminal selection.

SPIDs should not be confused with TEIs (terminal endpoint identifiers).
--- MsgPost 1.1
 * Origin: Center Field ISDN 901.368.4702 (1:123/301)