Pete,
Table 6/H.450.1 has not changed in Geneva, i.e. the table within the H.450.1 whitepaper you are referring to is still o.k.
Remark:
Since the ISDN like concept of Calling / Connected Line Identification Presentation / Restriction is not known in H.323, types like Table 6/H.450.1 PresentedNumberScreened, etc. have not been used within H.450.2, .3 (Only PresentationAllowedIndicator is used within Call Diversion).
Once we want to make use of ISDN like Identification Presentation / Restriction concept within Supplementary Services, I would for consistency reasons also see the PartyNumber within types like NumberScreened or Address being replaced by EndpointAddress (which would e.g. enable to request presentation restriction at the destination side of an Alias other than PartyNumber).
Karl
============================
Karl Klaghofer
Siemens AG, Dpt. PN VS LP 3
D-81359 Munich, Germany
Hofmannstr. 51
Tel.: +49 89 722 31488
Fax.: +49 89 722 22909
Mail.: karl.klaghofer(a)pn.siemens.de
============================
-----Original Message-----
From: Pete Cordell [SMTP:pete.cordell@BT-SYS.BT.CO.UK]
Sent: Mittwoch, 25. Februar 1998 09:04
To: ITU-SG16(a)mailbag.jf.intel.com
Subject: Addressing information in H.450.1
Dear Karl (or anybody else who can answer),
Please can you assure me that the majority of the partyNumber fields in
Table 6/H.450.1 (white) should indeed refer PartyNumber and not to
EndpointAddress as I would have first expected!!!
Many thanks,
Pete
=================================
Pete Cordell
BT Labs
E-Mail: pete.cordell(a)bt-sys.bt.co.uk
Tel: +44 1473 646436
Fax: +44 1473 645499
=================================
