caller ID and implementer's guide

[Paul Long]

Pete,

Of course one can do anything with proprietary solutions, which is what you
have described in both cases here.

Paul Long
Smith Micro Software, Inc.

        -----Original Message-----
        From:   Pete Cordell [SMTP:pete.cordell at BTINTERNET.COM]
        Sent:   Tuesday, May 11, 1999 2:36 PM
        To:     ITU-SG16 at MAILBAG.INTEL.COM
        Subject:        Re: caller ID and implementer's guide

        My two cents - each worth one cent each...

        1) You should only send private information in a clear text field to
an
        entity that you trust to honour the request not to display it.  If you
know
        enough about the entity to trust it, you probably know enough about it
to
        know whether it will accept octet 3a.

        2) If you must send this information to an entity that you don't know
        anything about, you could take further ownership of the use of Q.931
and
        define a new IE and IE identifier (such as 0x6e or hi-jack one of the
ids
        that you are very unlikely to use - 0x43) to mean 'calling party
number with
        presentation restriction'.  This would have the same format as a
normal
        Q.931 calling party number.

        Pete

        =============================================
        Pete Cordell
        pete.cordell at btinternet.com
        =============================================