Google Answers Logo
View Question
Q: INS1500 ISDN/PRI Standard ( Answered,   2 Comments )
Subject: INS1500 ISDN/PRI Standard
Category: Computers > Algorithms
Asked by: spedia-ga
List Price: $150.00
Posted: 08 Feb 2003 13:20 PST
Expires: 10 Mar 2003 13:20 PST
Question ID: 158875
we need a document describing the INS1500 ISDN PRI standard in Japan
(used by NTT). Especially the Q931 portion of it. We have the ISDN
that describes Lucent 5ESS and ATT 4ESS switches and need to
differentiate the INS1500 by NTT from these switches.

Request for Question Clarification by websearcher-ga on 08 Feb 2003 15:02 PST
Hello spedia:

Thanks for the challenging question. 

I've been able to find three promising documents that might be a start
to what you're looking for. However, I'm unfamiliar with this
technology, so I'm not sure whether any of them are on the right
track. If you would please have a look at the three and tell me if any
of them are worth pursuing further, that would be a lot of help.

1. Cause and Location Codes
Take note of:
Received INS 1500 Specific Cause Code Mappings
SIP to ISUP/ISDN Cause Codes

2. Ethernet Switches - INS1500

3. ISDN Jargon Buster
Quote: "INS1500: NTT's INS1500 is an ISDN Primary Rate Interface
(PRI). It consists of 23 B channels (Bearer channels) for data
transmission and one D channel (Delta or Data channel). Unlike INS64,
INS1500 requires a fiber optic connection between the customer and
NTT. INS1500 can be boosted up to 24 B channels by using a separate
INS64 line for the D channel. The 23 B channels can be multiplexed
together for a maximum data rate of 1.5 Mbps."

I look forward to your reply. 


Clarification of Question by spedia-ga on 08 Feb 2003 15:16 PST
The provided answers are just generic material (mainly cisco tech
support documentation that has already been researched and does not
contain the information required).

We need the actual RFC or other technical document (ITU, TTC or other
Telco organization document that describes the SIGNALING used for
Q.931 INS1500). Generic mesages in proprietory products (such as
Cisco) are not of interest to us.

Request for Question Clarification by websearcher-ga on 08 Feb 2003 15:31 PST
Hi spedia:

Thanks for the clarification. I was unable to find anything that fits
your description on the Web. Perhaps another one of our researchers
will have better luck.


Request for Question Clarification by pafalafa-ga on 08 Feb 2003 16:50 PST
Hello Spedia,

I marvel at people like yourself who actually understand the technical
nuts and bolts of modern telecommunications.  I don't!  And while I
think I've found the document you need, I hesitate to post it because
my understanding in this area is razor thin. sounds like you're looking for the signaling specs for a
Telco Switch with a PRI ISDN Q.931 Interface.  If that's the case,
then I can send you directly to the link on the web where you can buy
the 344-page document that specifies the ISDN user to network Q931
interface for call control.  The document itself costs about $100,
beyond anything you'll spend here at Google Answers.

An important caveat though, is this.  I haven't looked at the document
myself to verify that it is, in fact, the standard for the INS1500
used by NTT (and even if I *did* have a chance to look at it, I'm
still not sure I could glean the answer).  However, from what you
describe, this seems to be the Q931 piece of what you're looking for.

I'm sorry to leave things so iffy.  If you would like me to post the
link as an answer, let me know.  Or if you have an alternative
suggestion, let me know that as well.

Clarification of Question by spedia-ga on 08 Feb 2003 18:30 PST
OK. The purposes of the whole procedure is not to issue a generic
search via web (we have gone through this process already with no
luck). Nothing that a search engine can return as a result in the top
30 lists will be capable of answering this question.
The problem comes from the fact that the INS1500 ISDN/PRI standard is
Japanese and it lacks English documentation. Our efforts could not
produce a single good reference URL, that will help us allow our ISDN
router to interface to INS1500 equipment.

If you are referring to these web sites:

we have been all over them already. I need a document that will
describe the Q.931 specs of INS1500 ISDN/PRI equipment used by NTT
(Japanese Telco). I do not need a generic Q.931 reference because the
chances are we already have it.

Request for Question Clarification by pafalafa-ga on 08 Feb 2003 19:42 PST
OK, that helps, big time.  I don't have an answer for you yet, but I'm
still on it.  I'll let you know if anything turns up.

Request for Question Clarification by pafalafa-ga on 09 Feb 2003 13:50 PST
Hello again.  Like I said, I'm still on the job.

I have found something, but the question is, do you have this already,
or is it something new (and if new, is it something of interest?).

There are some documents that describe technical standards in Japan
that are written in English.  They are prepared by a group called the
TTC, and from what I can tell, the full standards are in Japanese,
while more often than not, only comrehensive summaries are in English
(there are exceptions though, and some full standards appear to be
available in English as well).  These follow a coding/numbering
convention similar to the ITU so that the standard JT-Q931 is the
Japanese corollary to Q931 as established by ITU.

A piece of the JT-Q931 standard is below.  

"JT-Q931 ISDN User-Network Interface Layer 3 Specification for
@@@@Basic Call Control

1. Relations with international standards
This Standard is based on the ITU-T Recommendation Q.931 approved in
the SG11
meeting( March 1993) and the changes approved in the SG11 meeting(May
2. Summary of differences from the international recommendations
(1) Of the optional items in ITU-T Recommendation Q.931, the following
have been selected as the TTC standards. (Corresponding Chapter and
Section numbers are shown in parentheses).
(A) Because the support of 2 octets is always essential as the length
of a Call Reference, a 2-octet Call Reference is regarded as the
unified standard. A 1- or 2-octet Call Reference for the primary-rate
interface, however, is specified to be sent as a network option.
(B) As the sending procedure of the Called Party Number from the
calling party, en bloc sending is considered as a standard and the
overlap sending is non-standard.
Because the en bloc sending procedure as the basic procedure shares
the functions of the overlap sending procedure, the two procedures are
unified into one; namely, the en bloc sending procedure.
(C) As the incoming call procedure to the called party, the en bloc
procedure is considered as a standard, while the overlap procedure is
The en bloc incoming call procedure is viable in Japan, since the
fixed numbering plan is employed there. In addition, the en bloc
incoming call procedure as the basic procedure shares all the
functions of the overlap procedure. Therefore, the en bloc incoming
call procedure is considered as a standard.

(D)The incoming call procedure over a data link with SAPI=16 on the
D-channel for packet-mode is regarded as non-standard.( only
the procedures making use of the SAPI=0 data link are regarded as
standard, while those making use of the SAPI=16 link are considered to
be provisional and their necessity can not be identified. As
information, it is specified in the ITU-T
Recommendation Q.931 that terminals implemented with the procedures
with the SAPI=16 must be implemented with also the procedures with the
SAPI=0 to guarantee terminal portability .
(2) TTC has analyzed the optional items in ITU-T Recommendation Q.931
and they are summarized, except for (1) above, in Table 1 of this

And so on.  The full document is 3-pages, and downloadable.  

There are many other English-language standards documents available
from TTC. They are organized in the following categories:

Inter-network Transmission 
ISDN Inter-network Signalling 
Packet / Frame Relay 
Mobile Communications 
ISDN User-Network Interface 
Infrared Communications 
Network Management 
Voice Coding 
Video Coding / AV Communications  

I am simply not competent to tell you which ones are most relevant to
your needs.

Is this on the right track?  Let me know, so I can investigate more


Clarification of Question by spedia-ga on 09 Feb 2003 14:26 PST
As I already mentioned the TTC site is already explored. Look several
passages above. We have this already. I do not know how this whole
Google process work. I am not that interested in finding someone to
search the web for us, as I am interested in finding someone with
experience in the industry who can provide is with the appropriate
document or its source.

Request for Question Clarification by pafalafa-ga on 09 Feb 2003 14:54 PST
The process works like this.  A large number of researchers with a
whole host of different experiences and backgrounds see your question.
 Anyone can try to respond by (1) making use of their own knowledge
(2) searching for information, or (3) finding the right people to get
an answer.

I can't do (1), I've tried (2) with no success yet, and am now looking
into (3).

If no one comes up with an answer, then you've paid only a fifty cents
listing fee -- not a bad investment, if you ask me.

Request for Question Clarification by pafalafa-ga on 18 Feb 2003 17:28 PST
Hello Spedia,

No, I haven't forgotten about you.  I have received some information
in regard to my many inquiries about INS1500 standards, and I have a
link to detailed technical specs, in English.

The specs reference INS-Net1500 from NTT, which *I believe* to be one
and the same as INS1500, but I have been unable yet to confirm this. 
The intro to the document says this:

"This technical reference document explains about the INS Net and the
interface to the telecommunication machinery connected with the INS
Net and offers technical information that would be a reference in
designing telecommunication machinery.

Nippon Telegraph and Telephone Corpration (NTT) does not guarantee the
telecommunication quality by the contents of this document.

Conditions that terminal equipment should provide are established in
regulation about technical condition of a terminal connection on
telecommunication service, and this document includes a part of
INS Net offers “INS Net 64„ (basic interface) service that can use two
information channels and a 16kbit/s signaling channel, and, besides,
it also offers “INS Net 1500„ (primary rate interface) service that
can use higher bitrate channels such as 384kbit/s and 1536kbit/s. Both
of them may be available the circuit-mode and packetmode services."


There are several volumes available, and others "under construction"
that will become available at some future date:

  Volume 1
(Outline) -7th edition-  
 Volume 2
(Layer 1 and 2 Specifications) -4th edition-  
 Volume 3
(Layer 3 Circuit-switching) -5th edition-  
 Volume 4
(Additional service for Layer 3 Circuit-switching) -5th edition-  
 Volume 5 <-- Under Construction -->
(Packet-switching) -4th edition-  
 Volume 6 <-- Under Construction -->
(Transmission system of metallic subscriber loop for basic interface)
-3rd edition-
 Volume 7 <-- Under Construction -->
(Transmission system of light subscriber loop for primary rate
interface) -2nd edition-
I've included detailed table of contents for Vol. 3 below, so you can
see what it looks like.  If this looks like a possibility to you, do
you want me to post it now as an answer, or wait until I can confirm
that INS1500 and INS Net1500 are one and the same?

Let me know.



Vol.3 (Layer 3 Circuit-switching) 5th edition

The Preface (PDF File, 2pages 32K)
Description method of this document

1.   General (PDF File, 1page 32K)
  1.1   Scope of the Recommendation
  1.2   Application to interface structures

2.   Overview of call control (PDF File, 9pages 95K)
  2.1   Circuit-switched calls
    2.1.1   Call states at the user side of the interface   Null (U0)   Call Initiated (U1)   Overlap sending (U2)   Overlap call proceeding (U3)   Call Delivered (U4)   Call Present (U6)   Call Received (U7)   Connect Request (U8)   Incoming Call Proceeding (U9)   Active (U10)   Disconnect Request (U11)   Disconnect Indication (U12)   Suspend Request (U15)   Resume Request (U17)   Release Request (U19)   Overlap Receiving (U25)
    2.1.2   Call states at the network side of the interface   Null (N0)   Call Initiated (N1)   Overlap Sending (N2)   Outgoing Call Proceeding (N3)   Call Delivered (N4)   Call Present (N6)   Call Received (N7)   Connect Request (N8)   Incoming Call Proceeding (N9)   Active (N10)   Disconnect Request (N11)   Disconnect Indication (N12)   Suspend Request (N15)   Resume Request (N17)   Release Request (N19)   Call Abort (N22)   Overlap Receiving (N25)
  2.2   Temporary signaling connections
    2.2.1   Call states at the user side of the interface   Null (U0)   Call Initiated (U1)   Overlap Sending (U2)   Outgoing Call Proceeding (U3)   Call Delivered (U4)   Call Present (U6)   Call Received (U7)   Connect Request (U8)   Incoming Call Proceeding (U9)   Active (U10)   Release Request (U19)   Overlap Receiving (U25)
    2.2.2   Network Call states   Null (N0)   Call Initiated (N1)   Overlap Sending (N2)   Outgoing Call Proceeding (N3)   Call Delivered (N4)   Call Present (N6)   Call Received (N7)   Connect Request (N8)   Incoming Call Proceeding (N9)   Active (N10)   Release Request (N19)   Call Abort (N22)   Overlap Receiving (N25)
  2.3   States associated with the global call reference
    2.3.1   Call states at the user side of the interface   Null (Rest 0)   Restart Request (Rest 1)   Restart (Rest 2)
    2.3.2   Call states at the network side of the interface   Null (Rest 0)   Restart Request (Rest 1)   Restart (Rest 2)

3.   Message function definitions and content (PDF File, 44pages 347K)
  3.1   Messages for circuit mode connection control
    3.1.1   [ALERTING]
    3.1.2   [CALL PROCEEDING]
    3.1.3   [CONNECT]
    3.1.5   [DISCONNECT]
    3.1.6   [INFORMATION]
    3.1.7   [NOTIFY]
    3.1.8   [PROGRESS]
    3.1.9   [RELEASE]
    3.1.10   [RELEASE COMPLETE]
    3.1.11   [RESUME]
    3.1.13   [RESUME REJECT]
    3.1.14   [SETUP]
    3.1.15   [SETUP ACKNOWLEDGE]
    3.1.16   [STATUS]
    3.1.17   [STATUS ENQUIRY]
    3.1.18   [SUSPEND]
    3.1.20   [SUSPEND REJECT]
  3.2   Message for the control of user signalling bearer service
    3.2.1   [ALERTING]
    3.2.2   [CALL PROCEEDING]
    3.2.4   [CONNECT]
    3.2.6   [INFORMATION]
    3.2.7   [RELEASE]
    3.2.8   [RELEASE COMPLETE]
    3.2.9   [SETUP]
    3.2.10   [SETUP ACKNOWLEDGE]
    3.2.11   [STATUS]
    3.2.12   [STATUS ENQUIRY]
    3.2.13   [USER INFORMATION]
  3.3   Messages used with the global call reference
    3.3.1   [RESTART]
    3.3.3   [STATUS]

4.   General message format and information elements coding (PDF File,
80pages 536K)
  4.1   Overview
  4.2   Protocol discriminator
  4.3   Call reference
  4.4   Message type
  4.5   Other information elements
    4.5.1   Coding rules
    4.5.2   Extensions of codesets
    4.5.3   Locking shift procedure
    4.5.4   Non-locking shift procedure
    4.5.5   Bearer capability
    4.5.6   Call identity
    4.5.7   Call state
    4.5.8   Called party number
    4.5.9   Called party subaddress
    4.5.10   Calling party number
    4.5.11   Calling party subaddress
    4.5.12   Cause
    4.5.13   Channel identification
    4.5.14   Congestion level
    4.5.15   Date/time
    4.5.16   Display
    4.5.17   High layer compatibility
    4.5.18   Keypad facility
    4.5.19   Low layer compatibility
    4.5.20   More data
    4.5.21   Network-specific facilities
    4.5.22   Notification indicator
    4.5.23   Progress indicator
    4.5.24   Repeat indicator
    4.5.25   Restart indicator
    4.5.26   Segmented message
    4.5.27   Sending complete
    4.5.28   Signal
    4.5.29   Transit network selection
    4.5.30   User-User
  4.6   Network-specific information element
    4.6.1   Advice of charge
    4.6.2   Blocking channel identification
    4.6.3   General notification
    4.6.4   Redirecting number

5.   Circuit-switched call control procedures (PDF File, 56pages 410K)
  5.1   Call establishment at the originating interface (originating
    5.1.1   Call request
    5.1.2   Information channel selection-originating
    5.1.3   Overlap sending
    5.1.4   Invalid call information
    5.1.5   Outgoing call proceeding   Enbloc call setup   Overlap sending
    5.1.6   Notification of interworking at the originating interface
    5.1.7   Call delivered
    5.1.8   Call connected
    5.1.9   Call rejection
    5.1.10   Transit network selection
  5.2   Call establishment at the destination interface (the
destination procedure)
    5.2.1   Incoming call
    5.2.2   Compatibility checking
    5.2.3   Information channel selection - destination   SETUP message delivered by point-to-point data link   SETUP message delivered by broadcast data bank
    5.2.4   Overlap sending
    5.2.5   Call confirmation   Response to the SETUP message   Receipt of CALL PROCEEDING and ALERTING   Called user clearing during incoming call
establishment   Call failure
    5.2.6   Notification of interworking at the terminating interface
    5.1.7   Call accept
    5.2.8   Active indication
    5.2.9   Non-selected user clearing
  5.3   Call clearing
    5.3.1   Terminology
    5.3.2   Exception conditions
    5.3.3   Clearing initiated by the user
    5.3.4   Clearing initiated by the network   Clearing when in-band tones/announcements provided   Clearing when in-band tones/announcements not provided   Completion of clearing
    5.3.5   Clear collision
  5.4   In-band tones and announcements
  5.5   Restart procedure
    5.5.1   sending RESTART
    5.5.2   Receipt of RESTART
  5.6   Call rearrangements suspend/resume*j
    5.6.1   Call suspension
    5.6.2   Call suspended
    5.6.3   Call suspend error
    5.6.4   Call re-establishment
    5.6.5   Call resume errors
    5.6.6   Double suspension
    5.6.7   Call re-arrangement notification controlled by an NT2
  5.7   Call collisions
  5.8   Handling of error conditions
    5.8.1   Protocol discriminator error
    5.8.2   Message too short
    5.8.3   Call reference error   Invalid call reference format   Call reference procedural errors
    5.8.4   Message type or message sequence errors
    5.8.5   General information element errors   Information element out of sequence   Duplicated information elements
    5.8.6   Mandatory information element errors   Mandatory information element missing   Mandatory information element content error
    5.8.7   Non-mandatory information element errors   Unrecognized information element   Non-mandatory information element content error   Unexpected recognized information elements
    5.8.8   Data link reset
    5.8.9   Data link failure
    5.8.10   Status enquiry procedure
    5.8.11   Receiving a STATUS message
  5.9   User notification procedure
  5.10   Identification and selection of basic telecommunication
  5.11   Signaling procedure for bearer capability selection
    5.11.1   The procedure at the originating user that indicates to
allow bearer capability selection.   Normal procedure   Exceptional procedures
    5.11.2   The procedures for bearer capability selection at the
destination side   Normal procedures   Exceptional procedures
    5.11.3   The procedures for interworking with private ISDNs   The procedures at the calling user for indicating
permission of bearer capability selection   The procedures at the called public ISDN for bearer
capability selection   Normal procedures   Exceptional procedures
  5.12   The signaling procedures for high layer compatibility
    5.12.1   The procedures at the originating user that indicate
allowing high layer compatibility selection.   Normal procedure   Exceptional procedures
    5.12.2   The procedures for high layer compatibility selection at
the destination side   Normal procedures   Exceptional procedures
    5.12.3   The procedures for interworking with private ISDNs   The procedures at the calling user for indicating
permission of high layer compatibility selection   The procedures at the called public ISDN for high
layer compatibility selection   Normal procedures   Exceptional procedures

6.   Procedures for user-to-user signaling bearer service call control
(PDF File, 3pages 32K)
  6.1   General
  6.2   Call establishment
  6.3   Transfer of USER INFORMATION messages
  6.4   Congestion control of USER INFORMATION messages
  6.5   Call clearing

7.   Circuit-mode multirate (64kbit/s base rate) procedures (PDF File,
6pages 63K)
  7.1   Call setup at the calling interface
    7.1.1   Compatibility information
    7.1.2   Channel selection
    7.1.3   Interworking
  7.2   Call setup at the called interface
    7.2.1   Compatibility information
    7.2.2   Channel selection   Point-to-point configuration   Point-to-multipoint configuration
    7.2.3   Interworking
  7.3   Call clearing
  7.4   Restart procedure
  7.5   Call rearrangement

8.   System parameters (PDF File, 4pages 63K)
  8.1   Timers in the network side
  8.2   Timers in the user side

9.   Usage of cause and location (PDF File, 18pages 189K)
  9.1   General description
  9.2   Cause
  9.3   Cause definitions
    9.3.1   Normal class   Cause No.1: unallocated (unassigned) number   Cause No.2: no route to specified transit network   Cause No.3: no route to destination   Cause No.6: channel unavailable   Cause No.7: call delivered to an established channel   Cause No.16: normal disconnection   Cause No.17: user busy   Cause No.18: no user responding   Cause No.19: no answer from user (user alerted)   Cause No.20: subscriber absent   Cause No.21: call rejected   Cause No.22: subscriber number changed   Cause No.26: non-selected user clearing   Cause No.27: destination interface out of order   Cause No.28: invalid number format (incomplete
number)   Cause No.29: facility rejected   Cause No.30: response to STATUS ENQUIRY   Cause No.31: normal class, unspecified
    9.3.2   Resource unavailable class   Cause No.34: no circuit / channel available   Cause No.38: network out of order   Cause No.41: temporary failure   Cause No.42: switching equipment congestion   Cause No.43: access information   Cause No.44: requested circuit / channel not available   Cause No.47: resource unavailable class, unspecified
    9.3.3   Service not available class   Cause No.49: Quality of Service not available   Cause No.50: requested facility not subscribed   Cause No.57: bearer capability not permitted   Cause No.58: bearer capability not presently available   Cause No.63: service or option not available class,
    9.3.4   Service not implemented class   Cause No.65: non-implemented bearer capability
specified   Cause No.66: non-implemented channel type specified   Cause No.69: non-implemented facility requested   Cause No.70: only restricted digital information
bearer capability is available   Cause No.79: service or option not implemented class,
    9.3.5   Invalid message class   Cause No.81: invalid call reference values used   Cause No.82: invalid channel number used   Cause No.83: specified suspended call identity number
not used   Cause No.84: suspended call identity number in use   Cause No.85: no suspended call   Cause No.86: specified suspended call has been cleared   Cause No.87: user is not CUG member   Cause No.88: incompatible destination   Cause No.91: invalid transit network selection   Cause No.95: invalid message class, unspecified
    9.3.6   Procedure error (e.g., unknown message) class   Cause No.96: mandatory information element is missing   Cause No.97: message type not defined or not
implemented   Cause No.98: message incompatible with call state or
message type not defined or not implemented   Cause No.99: information element not defined or not
implemented   Cause No.100: invalid information element contents   Cause No.101: message incompatible with call state   Cause No.102: recovery on timer expiry   Cause No.111: procedure error class, unspecified
    9.3.7   Interworking class   Cause No.127: interworking class, unspecified
  9.4   Example of cause and location in the busy condition

ANNEX 1   the SDL diagrams (PDF File, 62pages 441K)
ANNEX 2   Compatibility checking (PDF File, 6pages 63K)
ANNEX 3   Transit network selection (PDF File, 2pages 32K)
ANNEX 4   D-channel backup procedures (PDF File, 3pages 32K)
ANNEX 5   Cause definitions (PDF File, 1page 32K)
ANNEX 6   Cause list (PDF File, 6pages 95K)
ANNEX 7   Examples of information elements coding (PDF File, 11pages
ANNEX 8   Use of Progress indicator (PDF File, 2pages 32K)
ANNEX 9   Examples of cause value and location for busy conditions
(PDF File, 1page 32K)
ANNEX 10   Point-to-point and point-to-multipoint connection
procedures (PDF File, 4pages 95K)
ANNEX 11   Extensions for symmetric call operation (PDF File, 3pages
ANNEX 12   Bearer services specification (circuit-switched) (PDF File,
2pages 32K)
ANNEX 13   Selection of optional items for TTC standard (PDF File,
8pages 95K)
ANNEX 14   Message segmentation procedures (PDF File, 10pages 95K)
ANNEX 15   Low layer compatibility negotiation (PDF File, 2pages 32K)
ANNEX 16   The method for sending called numbers and so on
(Circuit-mode) (PDF File, 2pages 32K)
ANNEX 17   Connection with Emergency telephony (PDF File, 1page 32K)
ANNEX 18   Conditions for originating (PDF File, 1page 32K)
ANNEX 19   Appendix of TTC Recommendation JT-Q931 (partial) (PDF File,
26pages 284K)
ANNEX 20   Principle for low layer information encoding (PDF File,
9pages 95K)
ANNEX 21   Network-specific facility selection (PDF File, 1page 32K)
ANNEX 22   Procedures for establishment of bearer connection prior to
call acceptance (PDF File, 1page 32K)
ANNEX 23   Optional procedures for bearer service change (PDF File,
2pages 66K)
ANNEX 24   Restriction the signaling length on the user/network
interface (PDF File, 2pages 32K)
ANNEX 25   Number establishment principle (PDF File, 10pages 95K)

Cover sheet & Table of Contents & Last cover sheet (PDF File, 10pages

Clarification of Question by spedia-ga on 19 Feb 2003 08:59 PST

This looks like something that we may need. However, we need the
actual documentation not just a URL link to explore. Can you provide
the actual documentation (not just the index).

Request for Question Clarification by pafalafa-ga on 19 Feb 2003 09:33 PST
Hello Spedia,

Thanks for getting back to me, but I didn't fully understand your
comment that you "need the actual documentation, not just a link..."

The link I mentioned HAS all the includes several
hundred pages of technical docouments in three volumes and dozens of
appendices, with additional volumes "under construction" that should
appear in the future.

Do you want me to provide the link as an answer so you can download
the documents directly?  Or did you want me to download them myself
and pass them along to you (this is possible, but not as simple or
fast as a direct download yourself).  I just need to know how you wold
like to proceed, and I'm happy to oblige.

Request for Question Clarification by pafalafa-ga on 20 Feb 2003 06:06 PST
Hello again,

Given the positive nature of your comment and arimathea-ga's very
helpful (and much appreciated) acknowledgement that INS1500 is in fact
the same thing as INS Net-1500, I will post the link to the full
technical documentation tomorrow.  This will give you time to sort
through the information I've provided thus far to confirm that it is,
indeed, the information you were seeking.
Subject: Re: INS1500 ISDN/PRI Standard
Answered By: pafalafa-ga on 21 Feb 2003 11:47 PST
Hello Spedia, and thanks for your question -- this has been one of the
most challenging I've worked on yet.

The English language documents you are seeking can be found at:

FYI, the Japanese counterpart of this site is:

I found the site by a simple search on "INS1500", followed by a
massive e-mail campaign to all the people I identified in my search
that looked like they might be able to help out.

An e-mail response from the US Trade Representative's office, led me
to a contact for NTT in Washington, DC, who then referred me to a
contact at NTT in Japan.

The reply from NTT identified the sites above, but was unsigned except
for the following:

Nippon Telegraph and Telephone East Corporation(Mcon)

I hope this information meets you needs, and then some.

Request for Answer Clarification by spedia-ga on 23 Feb 2003 08:47 PST
Well, these documents have been already reviewed by our engineers
(beginning of February), however, they do not provide the level of
technical information that we need.

We need the exact communication protocol, not just a generic reference
to the standard.

This is definitely not the document that we are looking for.

Clarification of Answer by pafalafa-ga on 23 Feb 2003 09:21 PST
I have a fairly extensive contacts list now, in NTT and elsewhere, and
I am certainly willing to put it to use in answering your question. 
But I'd like your help in clarifying exactly what it is I should be

You said in your comment you need the "exact communication protocol". 
I thought that's what I had provided.  What information is missing? 
The documents I referenced offer about 1,000 pages of technical specs
intended, according to NTT, to provide "technical information that
would be a reference in designing telecommunication machinery."  I
need to better understand the missing piece of the picture.

Can you give me a link to an existing "communication protocol" (such
as the ones you have for Lucent 5ESS and ATT 4ESS switches) so that I
can see the distinction between what you need, and what I have offered
thus far.

The more information you can provide to me, the better I can focus my
follow-up efforts.

Subject: Re: INS1500 ISDN/PRI Standard
From: arimathea-ga on 19 Feb 2003 08:58 PST
INS Net-1500 is indeed the same as INS1500, and pala's standard is
just what you're probably looking for.
Subject: Re: INS1500 ISDN/PRI Standard
From: hankkarl-ga on 22 Apr 2004 12:44 PDT
pafalafa-ga has pointed to the correct standard for implementation. 
It has SDL diagrams and everything.  If these documents do not provide
enough information for your engineers to implement INS1500, I suggest
you license a commercial ISDN stack, such as the one sold by TeleSoft

Important Disclaimer: Answers and comments provided on Google Answers are general information, and are not intended to substitute for informed professional medical, psychiatric, psychological, tax, legal, investment, accounting, or other professional advice. Google does not endorse, and expressly disclaims liability for any product, manufacturer, distributor, service or service provider mentioned or any opinion expressed in answers or comments. Please read carefully the Google Answers Terms of Service.

If you feel that you have found inappropriate content, please let us know by emailing us at with the question ID listed above. Thank you.
Search Google Answers for
Google Answers  

Google Home - Answers FAQ - Terms of Service - Privacy Policy