From Dave Osborne · 1996-04-04 02:35 · #75336 in CYBERSPACE
TEIs identify the terminal at Layer 2 for a particular interface
(line). TEIs will be unique on an interface, whereas SPIDs will be
unique on the whole switch and tend to be derived from the primary
directory number of the subscriber. Although they are used at
different layers, they have a 1-to-1 correspondence so mixing them up
isn't too dangerous. TEIs are dynamic (different each time the terminal
is plugged into the switch) but SPIDS are not. Following the
initialization sequence mentioned above the 1-to-1 correspondence is
established. TEIs are usually not visible to the ISDN user so they are
not as well known as SPIDs.
The "address" of the layer 3 message is usually considered to be the
Call Reference Value (also dynamic but this time on a per call basis)
as opposed to the SPID, so the management entity in the ISDN device's
software must associate EID/CdPN on a particular TEI and Call Reference
Number to a SPID.
There are some standards that call for a default Service Profile, where
a terminal doesn't need to provide a SPID to become active. Without
the SPID however, the switch has no way of knowing which terminal is
which on the interface so for multiple terminals an incoming call would
be offered to the first terminal that responded, rather than to a
specific terminal.
sorflet@bnr.ca (winston (w.l.) sorfleet)
cstorry@gandalf.ca (Chuck Storry)
------------------------------
2.19) Will ISDN terminal equipment that works in one country
work properly when it is installed in another country?
There are four major problem areas.
The first has to do with voice encoding, and is only a problem if the
equipment is a telephone. Equipment designed for use in North America
and Japan uses mu-law encoding when converting from analog to digital,
whereas the rest of the world uses A-law. If the equipment has a
switch for selecting one or the other of these encoding types, then
there will not be a problem with the voice encoding.
The second has to do with the way the equipment communicates with the
telephone exchange. There are interoperability problems because
* there are so many different services (and related parameters) that the
user can request and
* each country can decide whether or not to allow the telephone exchange
to offer a given service and
* the specifications that describe the services are open to interpretation
in many different ways.
So, as with other interoperability problems, you must work with the vendors
to determine if the equipment will interoperate. This is a basic problem;
it impacts all ISDN equipment, not just voice equipment.
The third has to do with homologation, or regulatory approval. In most
countries in the world the manufacturer of telephone equipment must
obtain approvals before the equipment may be connected to the network.
So, even if the equipment works with the network in a particular
country, it isn't OK to hook it up until the manufacturer has jumped
through the various hoops to demonstrate safety and compliance. It is
typically more expensive to obtain world-wide homologation approvals
for a newly-developed piece of ISDN equipment than it is to develop it
and tool up to manufacture it.
A fourth issue is in the US the TA and NT1 are both provided by the
customer, while in Europe the NT1 is provided by telephone company.
Stated differently, if you walk into a store in the US and buy
something to plug into an ISDN line it may be designed as a one-piece
unit that connects to point U. In Europe you would get something that
plugs into point T. Thus you might take a piece of US-originated
equipment to Europe and find that it won't work because the jack in
Europe is a T interface and the plug on your US equipment is a U
interface.
There are attempts to remedy this situation, particularly for BRI
ISDN. In North America, the National ISDN User's Forum is coming
up with standards that increase the uniformity of ISDN services.
In Europe, a new standard called NET3 is being developed.
msun@ntmtv.com (Ming Sun)
marc@dumbcat.sf.ca.us (Marco S Hyman)
jwb@capek.rdt.monash.edu.au (Jim Breen)
keyman@Eng.Sun.COM (Dave Evans)
oj@vivo.com (Oliver Jones)
wmartin@nsa.bt.co.uk (William Martin)
oppedahl@panix.com (Carl Oppedahl)
------------------------------
2.20) Will ISDN terminal equipment that works with one vendor's ISDN
switch work properly when used with another vendor's switch?
[Ed. Note: The title is edited from the previous faq to try to fit in
with the preceding question]
[Also, this seems to imply that there are only two implementations
to worry about and it is very US-centric. This section needs to be
reworked]
When the National ISDN-1 standard is implemented, there will be a single
standard for how TE communicates with the CO (the call setup dialogue).
Until that time, you may encounter two different varieties of CO equipment,
each with its own call setup dialogue:
* ATT 5ESS
* Northern Telecom DMS100
Some ISDN TE equipment can be configured to communicate with either;
some works with only one variety.
Jim.Rees@umich.edu (Jim Rees)
jerry@watchman.sfc.sony.com (Jerry Scharf)
------------------------------
2.21) Do different manufacturers' Terminal Adaptors interoperate when
used asynchronously?
There is a standard up to 19.2k (V.110) but above that there is no real
standard implemented. However, in practice there is a fair degree of
interoperability (even when the TA's manual tells you otherwise)
because many TAs use the same chip set (supplied by Siemens) which
happily goes up to 38.4. TAs from different suppliers that are using
the Siemens chips have a fair chance of interoperating at up to 38.4k.
wmartin@nsa.bt.co.uk (William Martin)
------------------------------
2.22) Why do I get only about 19.2k throughput from my TA?
The problems in using TA's are the same as those in using fast modems.
You only get the throughput that your serial port can handle. The
serial ports of many machines struggle to receive at 19.2k. Sending is
easier to implement efficiently. Many machines will happily send data
to a TA at 38.4, but choke down to around 19.2k or lower when receiving
(with lots of retries on ZMODEM file transfer).
wmartin@nsa.bt.co.uk (William Martin)
------------------------------
2.23) How long should call setup take when using a TA?
The "less than a second" call setup sometimes claimed seems to be rare.
TAs have a negotiation phase and it typically takes around 4 seconds
to get through to the remote site.
wmartin@nsa.bt.co.uk (William Martin)
--
3.01) How do I find out about getting ISDN in my area?
EURIE contact data:
Country Company name tel / fax
=========== ================ ====================== ===================
Austria PTT Austria Mr Michael Schneider +43 1 317 30 39
+43 1 31 3.13.66.63
Belgium BELGACOM Mr Egied Dekoster +32 2/213.46.49
+32 2/921.02.13
Denmark Tele Danmark Mr Soren Christensen +45 3399 6940
+45 3314 5625
Finland Telecom Finland Mr Terho Salo +358 31 243 22 67
+358 31 243 23 83
Finland The ATC Finland Mr Matti Tammisalo +358 0 606 35 08
+358 0 606 33 22
France France Telecom Mr Pascal Meriaux +331 44 44 53 59
--- MsgPost 1.1
* Origin: Center Field ISDN 901.368.4702 (1:123/301)