> I would like to see Livingston move to a position of more widely
> disseminating technical tips such as for the case with PCTel/Zoltrix/driver
> v 2.17.
>
> Another example: I can find nothing on the Livingston web site or
> Livingston mailing lists useful in resolving an ISDN cause code 81.
That's probably not a good example. Why?
ISDN cause codes are generic and can be found elsewhere. Go to
www.infosee.com and type ISDN CAUSE CODE LIST, and you will be flooded
with hundreds of locations of detailed lists and descriptions.
I like that Livingston remains Livingston specific. I suppose it WOULD be
a good idea to post information relating to isdn even tho it would be
redundant to what already out on the net. That way you dont have to search
for it. Or at least post the url's. (I think im gonna h'url if I have to
say URL again)
>
> As an investor in PM2 and PM3 capital goods, IMHO it would increase the
> productivity of everyone involved, as well as potentially reducing
> Livingston's tech support costs.
Maybe so, but as mentioned before, cause codes are cause codes whether it
be portmanglers, Assend, Motorola Buttsniffers, Courier Eye-Modems, USR
TOTAL Out of Controls, Crisco's, etc... I could go on, but I wont in fear
that I might be banned from the list.
What I would like to see more of is interoperating tech notes on how to
get the pm 3 to work with ________, but they have that covered pretty
well.
I have some good info on getting 25's and 50's to talk to OR-U's and 5 BRI
cards, BTW, in both the remote AND host configurations.
BTW, here is an isdn cause code list:
1.
Unallocated (unassigned) number
2.
No route to specified transit network
3.
No route to destination
6.
Channel Unacceptable
7.
Call awarded and being delivered in
an established channel
16.
Normal call clearing
17.
User busy
18.
No user responding
19.
No answer from user (user alerted)
21.
Call Rejected
22.
Number changed
26.
Non selected user clearing
27.
Destination out of order
28.
Invalid number format
29.
facility rejected
30.
Response to status enquiry
31.
Normal, unspecified
34.
No circuit/channel available
38.
Network out of order
41.
Temporary failure
42.
Switching equipment congestion
43.
Access information discarded
44.
Requested circuit/channel not available
47.
Resources unavailable, unspecified
49.
Quality of service unavailable
50.
Requested facility not subscribed
57.
Bearer capability not authorised
58.
Bearer capability not presently available
63.
Service or option not available, unspecified
65.
Bearer capability not implemented
66.
Channel type not implemented
69.
Requested facility not implemented
70.
Only restricted digital information
bearer capability is available
79.
Service or option not implemented, unspecified
81.
Invalid call reference value
Definition of 81: The remote equipment received a call with a call
reference that is not currently in use on
the user-network interface.
82.
Identified channel does not exist
83.
A suspended call exists, but this call identity does not
84.
Call identity in use
85.
No call suspended
86.
Call having the requested call identity has been cleared
88.
Incompatible destination
91.
Invalid transit network selection
95.
Invalid message, unspecified
96.
Mandatory information element is missing
97.
Message type nonexistent or not implemented
98.
Message not compatible with call state or
message type nonexistent or not implemented
99.
Information element nonexistent or not implemented
100.
Invalid information element contents
101.
Message not compatible with call state
102.
Recovery on timer expiry
111.
Protocol error, unspecified
127.
Interworking, unspecified
These codes indicate the reason for ISDN call failure or
completion.
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~
Jake Messinger 713-772-6690 jake@ams.com
Advanced Medical Systems, Inc. jake@uh.edu
8300 Bissonnet #400
Houston, Texas 77074 http://www.ams.com/~jake
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~