home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.dcom.isdn
- Path: sparky!uunet!utcsri!torn!cunews!hobbit.gandalf.ca!cstorry
- From: cstorry@gandalf.ca (Chuck Storry)
- Subject: Re: Length of ISDN addresses
- Message-ID: <1992Sep4.201421.12924@gandalf.ca>
- Organization: Gandalf Data Ltd.
- References: <2343@unet.UUCP> <1992Sep3.123932.23973@gandalf.ca> <5af7f9b6.cb12@dabo.citi.umich.edu>
- Date: Fri, 4 Sep 1992 20:14:21 GMT
- Lines: 31
-
- In <5af7f9b6.cb12@dabo.citi.umich.edu> rees@dabo.citi.umich.edu (Jim Rees) writes:
-
- >In article <1992Sep3.123932.23973@gandalf.ca>, cstorry@gandalf.ca (Chuck Storry) writes:
-
- > The problems we've had with subaddresses is that the content of the subaddress
- > information element is not standardised. It may be encoded as bcd, hex, ascii
- > digit, or as per NSAP in one of many formats. If you're after compatibility
- > with other CPE then this can be a real problem.
-
- >I would consider it a bug if the network imposed any particular structure on
- >the subaddress. Can you give an example of where this is a problem
-
-
- The problem occurs when CPE from one vendor needs to talk to equipment of
- another and they encode/decode the called party subaddress differently.
- Both the originator and recipient must encode the information element
- with the same algorithm. This may work for NSAP provided your equipment
- recognises the encoded NSAP type; ASCII, HEX, etc. But for "type of
- subaddress == User specified" there is of course to agreed to convention
- for the subsequent encoding of the subaddress information field. although
- CCITT does indicate that the odd/even field is for use when the type of
- subaddress is user specified and the coding is BCD.
- D
- D
- D
- decodes the same format (actually specified by NSAP encoding?
- --
- Chuck Storry CAnet: cstorry@gandalf.ca
- Gandalf Data Ltd. Voice: (613) 723-6500
- Nepean, Ontario Fax: (613) 226-1717
- Canada K2E 7M4
-