- sg16-avd - lists.packetizer.com

Current list of registered contributions
by Noriko Hosokawa 27 Jul '99

27 Jul '99

Dear Q.12-14/16 experts, Attached please find the list of registered contributions as of 15:00 (Tokyo time) Tuesday 27 July. Those documents yet to be uploaded are marked with *. If you have uploaded your document but it is marked, please accept my apology and re-send it to the /Incoming directory. If you have not yet uploaded your document, please take your prompt action. Your cooperation is requested to make the Berlin meeting productive. Best regards, Sakae OKUBO (Mr.) *********************************************************** Waseda Research Center Telecommunications Advancement Organization of Japan (TAO) 5th Floor, Nishi-Waseda Bldg. 1-21-1 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan Tel: +81 3 5286 3830 Fax: +81 3 5287 7287 e-mail: okubo(a)giti.or.jp ******************************************************** Documents for Q.12-14/16 Rapporteur meeting in Berlin (2-6 August 1999) The documents can be retrieved as ftp://standard.pictel.com/avc-site/9908_Ber/APC-1???.??? or http://standard.pictel.com/ftp/avc-site/9908_Ber/APC-1???.??? * yet to be uploaded # to be uploaded after the SG11 Rapporteur meeting this week ------------------------------------------------------------------------ APC- Source Title ------------------------------------------------------------------------ 1555 ITU-T SG8 Recommendation T.38 Indications in Recommendation H.245 (TD1/WP2 of the SG16 Santiago meeting) 1556 ITU-T SG11 Support of IN services for H.323 and other IP Network based terminals (TD4/WP2 of the SG16 Santiago meeting) 1557 ITU-T SG9 Draft New Rec. J.Web "Distribution of Sound and Television Programmes over the Internet "Webcasting"" (TD22/WP2 of the SG16 Santiago meeting) 1558 ITU-T SG2 Routing of Multimedia Connections When Interworking with PSTN, ATM, and IP Networks (TD24/GEN of the SG16 Santiago meeting) 1559 SG16 WP2 Proposed Organisation going forward to new Study Period 1560 Editor (E Martinez) Annex-H (User and Service Mobility in H.323) Proposed Architecture 1561 Editor (G Hellstrom) H.323 Annex G Text Conversation and Text SET 1562 L M Ericsson H.gcp Modification proposals for Text Conversation 1563 Editor Draft H.323 Annex J: Security for H.323 Annex F 1564 L M Ericsson H.224 Modified for text conversation 1565 DataBeam Corporation Usage of Expanded T.35 Country Codes in Recommendations H.225.0,H.245, and H.283 1566 Editor H.243 Draft revised ITU-T Recommendation H.243 (white doc.) 1567 L M Ericsson Generic Service ControlTransport 1568 Lucent and AT&T H.245 Generic Capabilities Definition and H.225 Packetization Specification for the North American Cellular/PCS TDMA Vocoders (ACELP and US1) 1569 BT and Tech-Know-Ware Editorial Clarifications to H.323 and the Implementer's Guide 1570 BT and Tech- Know-Ware Clarifications on Third-Party Pause 1571 Rapporteur for Q.12/16 (S Okubo) Status of Draft Amendment 7 to H.222.0|ISO/IEC 13818-1 -- Carriage of ISO/IEC 14496 (MPEG-4) content over H.222.0|ISO/IEC 13818-1 (MPEG-2) System streams 1572 Editor (K Sakai) Draft Implementor's Guide for H.321 V2 1573 Editor (S Okubo) Draft Implementor's Guide for H.310 V2 1574 SG16 Correspondence Representative to DAVIC (S Okubo) DAVIC work on TV Anytime and TV Anywhere system 1575 Rapporteur for Q.19/16 (S Hayashi) H.245 Capability Definition and H.225.0 Packetization Specification for G.729 1576 Japan Guideline for assigning the T.35 terminal provider codes in Japan 1577 Oki et al Proposed modifications to resolve the inconsistent ASN.1 syntaxes between T.38 Annex B and H.245 1578 Oki et al Proposed additional liasion to SG8 on T.38 Appnedix II 1579 Hitachi, Ltd. Prototype system of H.262 layered video transmission 1580 the IETF Megaco Working Group Media Gateway control protocol architecture and requirements 1581 Lucent Technologies and Nortel Networks H.323 v3 and H.225 v3 Support for Improved Alias Registrations 1582 Lucent Technologies H.323 v3 and H.225 v3 Endpoint Registration Clarifications 1583 Siemens AG Error in Coding Bearer Capabilities 1584 Siemens AG Inter-Zone Addressing 1585 Siemens AG Correction of Alias Conflict in H.225.0v3 1586 Siemens AG Identification of Gateway Protocol 1587 Siemens AG Null AliasAddress 1588 SIEMENS Restricted Numbers/Aliases in Supplementary Service APDUs 1589 SIEMENS Work on Supplementary Service Interworking started 1590 SIEMENS Draft H.450.9 "Call Completion Supplementary Services for H.323 1591 AT&T, VocalTec, DataBeam and Alcatel Functional Requirements and Service Classes to Support QOS in H.323 1592 Lucent Technologies Q.SIG Transport in H.323 Systems *1593 PictureTel and Nortel Networks Backward compatibility and clarification text in H.323 Annex C *1594 PictureTel Problem with XRS (Message Not Understood) RAS message *1595 PictureTel Additional information in ARQ for Gateway calls *1596 PictureTel H.245 support for G.722.1 *1597 Siemens Feature key management extensions for H.323 SET terminals 1598 VocalTec Communications Ltd Adopting a Pragmatic Approach to IPT-IN InterWorking 1599 VocalTec Clarifications to the fast connect procedure 1600 VocalTec Comments on Transporting DTMF in H.323 1601 VocalTec Changes to H.323 to support operation via basic NAT devices #1602 VocalTec Communications Ltd IN-IPT interworking - feecback from the SG11 Rapporteur #1603 VocalTec Communications Ltd and Marconi Communications Ltd Scope definition of Annex D to H.246 1604 VocalTec Changes to H.248 to assure H.323 GW interoperability *1605 Intel Corporation Proposed Terms of Reference for H.323 Mobility 1606 Cisco Systems Proposal for Transporting User Input via RTP 1607 Cisco Systems Proposal for Enforcing Symmetric Codec Operation with Fast Connect 1608 Tech-Know-Ware and Lucent H.GCP/Megaco Structured Message Encoding Using an ASCII Line Format 1609 Lucent Technologies Support for Q.931 TNS and NSF IEs in H.225.0 *1610 Q.14 Rapporteur Changes to H.248 Proposed by IETF Megaco 1611 RAD Data Communications LTD Proposals for the next version of H.341 MIB 1612 Lucent Technologies,Intel Corporation,FORE Systems Inc.,Teles AG Proposing structured media and bearers for H.248, 1613 Lucent Technologies Proposal for PUT and DELETE commands in H.248, 1614 Lucent Technologies Scripting framework for H.248, 1615 Lucent Technologies H.242 package for support of decomposed H.323-to-H.320 gateways in H.248 1616 LM Ericsson H.GCP and encoding in networks 1617 LM Ericsson Signalling Transport for H.GCP 1618 LM Ericsson Handling of Optional H.GCP commands 1619 LM Ericsson Notification Indicators in H.323 1620 LM Ericsson Signalling Transport in H.323 *1621 LM Ericsson Draft H.246 Annex C *1622 Lucent Technologies Expression of Gateway Call Capacity 1623 Lucent Technologies Need for the Q.931 Disconnect and Release Messages in H.225.0 1624 TAO Some considerations on the new Annex to H.323 for high quality audiovisual communications 1625 Oki Electric Indsutry Editorial errors in H.450.5 and H.450.7 1626 Nortel Networks Tunneling of Q.SIG information in H.225.0 1627 IETF Megaco Working Group R2 Package for MEGACO Protocol 1628 IETF Megaco Working Group Megaco IP Phone Media Gateway *1629 IETF Megaco Working Group Basic Packages For Megaco/H.248 *1630 Cisco Systems,Inc. SDP Encoding for H.248. *1631 Tech-Know-Ware and BT A Package based Extensible Object-Oriented Framework for H.225 1632 Lucent Technologies, Tech-Know-Ware, Intel Corporation, FORE Systems, VocalTec Communications, Teles AG Structured Syntax for H.248 1633 Mitel Proposals for Enhanced Feature Support in H.323 1634 Intel Security tokens for releaseComplete UUIE 1635 Telcordia Technologies Mapping H.245 semantics to SDP 1636 Telcordia Technologies Comparing EBNF and ASN.1 for text encoding *1637 Rapporteur Q13 Protocols for Trunking and Access Gateways *1638 LucentTechnologies Gatekeeper Modification of Destination Addresses *1639 LucentTechnologies Trunk and Line Selection in H.323 Gateways 1640 Nortel Networks Clarification on the use of E.164 numbers *1641 Lucent Interoperabity between H.323 Systems using G.711 and SD/CNG 1642 Alcatel and Nortelnetworks Reference to af-saa-0124.000 specification in H.323.V3 1643 MPEG Liaison Statement from SC 29/WG 11 to ITU-T SG 16 on MPEG-4 Over H.32x Terminals [SC 29/WG 11 N 2887] ----------------------------------------------------------------------------

1 0

APC-1643 Liaison from MPEG
by Sakae OKUBO 27 Jul '99

27 Jul '99

Dear Q.12-14/16 experts, The following document has been registered and uploaded as APC-1643. SOURCE : MPEG TITLE : Liaison Statement from SC 29/WG 11 to ITU-T SG 16 on MPEG-4 Over H.32x Terminals [SC 29/WG 11 N 2887] PURPOSE: Liaison - Information FILE : APC-1643.txt Best regards, Sakae OKUBO (Mr.) *********************************************************** Waseda Research Center Telecommunications Advancement Organization of Japan (TAO) 5th Floor, Nishi-Waseda Bldg. 1-21-1 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan Tel: +81 3 5286 3830 Fax: +81 3 5287 7287 e-mail: okubo(a)giti.or.jp ***********************************************************

1 0

APC-1606 and APC-1607
by Rich Bowen 26 Jul '99

26 Jul '99

Dear Mr. Okubo: Please find attached the following contributions for the Berlin meeting: o APC-1606, "Proposal for Transporting User Input via RTP" o APC-1607, "Proposal for Enforcing Symmetric Codec Operation with Fast Connect" I apologize for sending these contributions to the mailing list - for some reason I am encountering errors when trying to upload them to the FTP site. Regards, Rich -------------------------------------------------------------------- Richard K. Bowen Cisco Systems, Inc. rkbowen(a)cisco.com Research Triangle Park, NC --------------------------------------------------------------------

1 0

reference to the ATMF specification af-saa-0124.000
by Ameneh Zahir-Emami 26 Jul '99

26 Jul '99

Hello, This is Ameneh Zahir. I have been chairing the H323 gateway over ATM activity over the past 2 years in the ATM-Forum. The ATM-Forum is glad that this specification is referred to in the H323V3 recommendation. In order for the ITU-T organization to keep this reference in its determined version of H323.V3 I was told that you need an official ITU form to be filled. Because the ATM-Forum is meeting this week (starting today) it was almost impossible to meet the SG16 rapporteur's meeting deadline. I hope it is not too late for you to consider this contribution which is purely administrative. I uploaded it on the picture-tel website server under: ITU-af124.doc. Unfortunately it does not have any APC number. I would like to apologize and hope that if not in Berlin then in September during the interim meeting this contribution will be considered. Best regard. Ameneh Zahir Alcatel

2 1

APC-1626 and APC-1640
by Francois Audet 26 Jul '99

26 Jul '99

I have uploaded: APC-1626 "Tunneling of Q.SIG information in H.225.0" APC-1640 "Clarification on the use of E.164 numbers" ----- François Audet Tel:+1 408 565 5675 mailto:audet@NortelNetworks.com <mailto:audet@NortelNetworks.com> Nortel Networks Fax:+1 408 565 2375 http://www.NortelNetworks.com <http://www.nortelnetworks.com/>

1 0

draft-hellstrom-avt-rtp-text-01.txt Result of Oslo discussion.
by Gunnar Hellstrom 26 Jul '99

26 Jul '99

The draft rtp specification for text conversation that is discussed in the IETF AVT group is now available in the following URL. www.omnitor.se/english/standards/rtp/draft-hellstrom-avt-rtp-text-01.txt It is referenced in the H.323 Annex G Text Conversation draft that is entered as a contribution to the ITU-T Q13/16 meeting next week as document APC1561. I would like to receive comments on this draft. I am aware of the following points that might need discussion. 1. Timestamp clock frequency. I had put a low figure 10 Hz in the specification. It was questioned and proposed that a figure of some thousands should be selected. I am willing to accept that, and propose that 1000 Hz is used. A millisecond per tick is a handy figure. This will however lead to the timestamp offset in the redundancy data headers that use only 14 bits, flip around in only 16 seconds. If correct timing information is wanted, the data flush procedure described in next section should be used. 2. Retransmission of text before a pause. Text does not flow continously, but only when a user enter text. Therefore, a recommended procedure could specify that for the redundancy scheme, it is advisable to send the ISO 10646 synch character FEFF after some inactivity timer to flush out redundant data - see section 3.4. 3. Recommended procedures section. In the draft that accompanies this mail, section 3 documents the recommended procedures for using the payload format. Does the group want it to be kept there or shall it be moved to the specification specifying use of this RTP Payload? ( The first user being H.323 Annex G) Any other comments are welcome. Gunnar Hellström ----------------------------------------------- Gunnar Hellstrom LM Ericsson E-mail gunnar.hellstrom(a)omnitor.se Tel +46 751 100 501 fax +46 8 556 002 06

1 0

uploaded new document
by Mickey Nasiri 26 Jul '99

26 Jul '99

Dear colleagues, I have uploaded the document Q11-J-07 to ftp://standards.pictel.com/q11-site/dropbox/ This document is the same as document APC-1564 (White H.224 modified for text conversation with correction). Best regards //Mickey -- //Mickey Nasiri Ericsson Telecom AB Home Communications SE-126 25 STOCKHOLM Tel: +46-8-719 38 61 Mob: +46-70-319 38 61 email: mickey.nasiri(a)ericsson.com

1 0

APC-1609 Uploaded
by Robert J. Abrams 26 Jul '99

26 Jul '99

APC-1609, a proposal to support Q.931 TNS and NSF IEs in H.225.0, has been uploaded to the Incoming directory of the FTP site. Bob Abrams Lucent Technologies

1 0

APC-1580 - Megaco/H.248 reqs - uploaded
by Nancy-M Greene 26 Jul '99

26 Jul '99

I've just uploaded APC-1580 - Media Gateway control protocol architecture and requirements. It is the same as the internet-draft ftp://ftp.ietf.org/internet-drafts/draft-ietf-megaco-reqs-05.txt put out June 25th. Mr. Okubo, Please note that the source for this document is the IETF Megaco Working Group, and NOT Nortel Networks as I previously indicated. Nancy -------------------------------------------------------------------------- Nancy M. Greene Internet & Service Provider Networks, Nortel Networks T:514-271-7221 (internal:ESN853-1077) E:ngreene@nortelnetworks.com

1 0

APC1634
by El-Gebaly, Hani 26 Jul '99

26 Jul '99

Dear Q12/13/14 experts, I uploaded APC1634.doc to the Incoming directory. This is a proposal to add security tokens to the releaseComplete message. Regards, Hani ElGebaly Intel Corp.

1 0

Comment on APC-1636 (Was: Documents uploaded)
by Pete Cordell 26 Jul '99

26 Jul '99

Well it seems the Telcordia crowd still haven't read my proposal!!!!!! What I am proposing is an ASN.1-LIKE specification. That means similar to, but not exactly the same as. In my proposal your line: quarenteenProcessing QuarenteenProcessing OPTIONAL would be represented as: quarenteenProcessing AS q QuarenteenProcessing OPTIONAL. and q would be used as the on the wire tag for precisely the reasons quoted in APC-1636. If there are worries that this isn't ASN.1 (if that is worth worrying about!), then all you have to do is go through removing any AS specifiers either manually or automatically. It's no big deal. Pete ============================================= Pete Cordell pete(a)tech-know-ware.com ============================================= -----Original Message----- From: Hong Liu <lhong(a)RESEARCH.TELCORDIA.COM> To: ITU-SG16(a)MAILBAG.INTEL.COM <ITU-SG16(a)MAILBAG.INTEL.COM> Date: 26 July 1999 17:01 Subject: Documents uploaded >Hi, all, > >I have uploaded two contributions from Telcordia Technologies to the ftp >incoming directory for the Berlin meeting: > >APC-1635: Mapping H.245 Semantics to SDP >APC-1636: Comparing EBNF and ASN.1 for Text Encoding > >Cheers, > >--Hong >

2 1

Comment on apc-1612 Re: Documents uploaded
by Steve.Carr＠ICN.SIEMENS.COM 26 Jul '99

26 Jul '99

I'm not sure why the MG needs to know the OPC/DPC and CIC, there could just be a common naming of DS0s between the MGC and MG, and the MGC would map to OPC/DPC/CIC. However, if they are needed, then the Network Indicator (2 bits) should also be included. In addition, in the US (and China) SS7 Point Codes are 24 bits, and the CIC is 14 bits, not 14, 14 and 12 as shown in section 3.4 Steve Carr Unisphere Solutions John Segers <jsegers(a)LUCENT.COM> on 07/26/99 10:33:24 AM Please respond to Mailing list for parties associated with ITU-T Study Group 16 <ITU-SG16(a)mailbag.cps.intel.com> To: ITU-SG16(a)mailbag.cps.intel.com cc: (bcc: Steve Carr/Internet/ICN) Subject: Documents uploaded All, I just uploaded the following documents for the Berlin meeting to <ftp://standard.pictel.com/ftp/avc-site/Incoming/>: * apc-1612.zip Title: Proposing structured media and bearers for H.248 Source: Lucent Technologies, Intel Corporation, FORE Systems Inc., Teles AG * apc-1613.zip Title: proposal for PUT and DELETE commands in H.248 Source: Lucent Technologies * apc-1614.zip Title: Scripting framework for H.248 Source: Lucent Technologies * apc-1615.zip Title: H.242 package for support of decomposed H.323-to-H.320 gateways in H.248 Source: Lucent Technologies * apc-1632.zip Title: Structured syntax for H.248 Source: Lucent Technologies, Tech-Know-Ware, Intel Corporation, FORE Systems, VocalTec Communications, Teles AG Regards, John Segers -- John Segers email: jsegers(a)lucent.com Lucent Technologies Room HE 306 Dept. Forward Looking Work phone: +31 35 687 4724 P.O. Box 18, 1270 AA Huizen fax: +31 35 687 5954

1 0

APC-1633 uploaded
by Dave Walker 26 Jul '99

26 Jul '99

Dear Colleagues, I have uploaded APC-1633, Proposals for Enhanced Feature Support in H.323, to the Incoming directory. Dave Walker Mitel Corporation Ontario, CANADA

1 0

APCs 1581, 1582 uploaded
by Rex Coldren 26 Jul '99

26 Jul '99

Dear Q.12-14 experts, I've uploaded the following proposals to the Incoming directory: - APC-1581 H.323 v3 and H.225 v3 Support for Improved Alias Registrations - APC-1582 H.323 v3 and H.225 v3 Endpoint Registration Clarifications Regards, Rex

1 0

Documents uploaded
by Hong Liu 26 Jul '99

26 Jul '99

Hi, all, I have uploaded two contributions from Telcordia Technologies to the ftp incoming directory for the Berlin meeting: APC-1635: Mapping H.245 Semantics to SDP APC-1636: Comparing EBNF and ASN.1 for Text Encoding Cheers, --Hong

1 0

Re: APCs 1592, 1623 uploaded
by Orsic, Milo (Milo) 26 Jul '99

26 Jul '99

Need for the Q.931 Disconnect and Release Messages in H.225.0 Ye! Ye! Cheers, Milo > ---------- > From: Glen Freundlich[SMTP:ggf@LUCENT.COM] > Reply To: Mailing list for parties associated with ITU-T Study Group > 16 > Sent: Monday, July 26, 1999 10:19 AM > To: ITU-SG16(a)mailbag.cps.intel.com > Subject: APCs 1592, 1623 uploaded > > Dear Q.12-14 experts, > > I've uploaded the following proposals to the Incoming directory: > > - APC-1592 Q.SIG Transport in H.323 Systems > > - APC-1623 Need for the Q.931 Disconnect and Release Messages in H.225.0 > > Regards, > Glen > > -- > Glen Freundlich ggf(a)lucent.com > Lucent Technologies office: +1 303 538 2899 > 11900 N. Pecos fax: +1 303 538 3907 > Westminster, Colorado 80234 USA >

1 0

APCs 1592, 1623 uploaded
by Glen Freundlich 26 Jul '99

26 Jul '99

Dear Q.12-14 experts, I've uploaded the following proposals to the Incoming directory: - APC-1592 Q.SIG Transport in H.323 Systems - APC-1623 Need for the Q.931 Disconnect and Release Messages in H.225.0 Regards, Glen -- Glen Freundlich ggf(a)lucent.com Lucent Technologies office: +1 303 538 2899 11900 N. Pecos fax: +1 303 538 3907 Westminster, Colorado 80234 USA

1 0

Documents uploaded
by John Segers 26 Jul '99

26 Jul '99

All, I just uploaded the following documents for the Berlin meeting to <ftp://standard.pictel.com/ftp/avc-site/Incoming/>: * apc-1612.zip Title: Proposing structured media and bearers for H.248 Source: Lucent Technologies, Intel Corporation, FORE Systems Inc., Teles AG * apc-1613.zip Title: proposal for PUT and DELETE commands in H.248 Source: Lucent Technologies * apc-1614.zip Title: Scripting framework for H.248 Source: Lucent Technologies * apc-1615.zip Title: H.242 package for support of decomposed H.323-to-H.320 gateways in H.248 Source: Lucent Technologies * apc-1632.zip Title: Structured syntax for H.248 Source: Lucent Technologies, Tech-Know-Ware, Intel Corporation, FORE Systems, VocalTec Communications, Teles AG Regards, John Segers -- John Segers email: jsegers(a)lucent.com Lucent Technologies Room HE 306 Dept. Forward Looking Work phone: +31 35 687 4724 P.O. Box 18, 1270 AA Huizen fax: +31 35 687 5954

1 0

APC-1625 uploaded
by 千村保文 26 Jul '99

26 Jul '99

Dear Q.13 experts, I just uploaded APC-1625 to the FTP site (AVC site). The document has the following Title: "Editorial errors in H.450.5 and H.450.7" BestRegards, Yasubumi CHIMURA Oki Electric Industry Co.,Ltd.

1 0

APC-1577 uploaded
by 千村保文 26 Jul '99

26 Jul '99

Dear Q.12,13,14 experts, I just uploaded APC-1577 to the FTP site (AVC site). The document has the following Title: "Proposed modifications to resolve the inconsistent ASN.1 syntax between T.38 Annex B and H.245" BestRegards, Yasubumi CHIMURA Oki Electric Industry Co.,Ltd.

1 0

APC-1579 Uploaded
by toshiaki 26 Jul '99

26 Jul '99

Dear Q12,13 experts, I just uploaded APC-1579 to the FTP site (AVC/Incoming site). The document has the following Title: "Prototype system of H.262 layered video transmission" Best Regards, -- $B!v!v!v!!!! (BToshiaki Suzuki $B!J (Btoshiaki(a)crl.hitachi.co.jp) $B!v!v!v (B $B!v!v!v!!!! (BHitachi, Ltd., Central Research Laboratory $B!v!v!v (B $B!v!v!v!!!! (BNetwork Systems Research Department $B!v!v!v (B $B!v!v!v!!!! (BPhone: +81-42-323-1111 $B!? (B Fax: +81-42-327-7740 $B!v!v!v (B

1 0

uploaded APC 1598-ATT1
by Boaz Michaely 26 Jul '99

26 Jul '99

APC 1598-ATT1, "Report of Joint meeting ITU-T SG11/ ETSI SPAN3/ ETSI TIPHON on IN for Voice/Multimedia over IP" has been uploaded to "ftp://standard.pictel.com/ftp/avc-site/Incoming/APC-1598.zip" Regards, Boaz Michaely Senior Program Manager, Advanced Technologies VocalTec Communications Ltd e-mail boaz(a)vocaltec.com Tel +44 411 181 782

1 0

uploaded APC 1598 "Adopting a Pragmatic Approach to IPT-IN InterWorking"
by Boaz Michaely 26 Jul '99

26 Jul '99

APC 1598, "Adopting a Pragmatic Approach to IPT-IN InterWorking" has been uploaded to "ftp://standard.pictel.com/ftp/avc-site/Incoming/APC-1598.zip" Regards, Boaz Michaely Senior Program Manager, Advanced Technologies VocalTec Communications Ltd e-mail boaz(a)vocaltec.com Tel +44 411 181 782

1 0

APC-1576 uploaded
by 千村保文 26 Jul '99

26 Jul '99

Dear Q.12,13,14 experts, I just uploaded APC-1576 to the FTP site (AVC site). The document has the following Title: "T.35 terminal provider codes for non-standard facilities in Japan BestRegards, Yasubumi CHIMURA Oki Electric Industry Co.,Ltd.

1 0

Contribution APC-1611
by Alex Shulman 26 Jul '99

26 Jul '99

Hello all, A contribution APC-1611 have been posted. The contribution contains the issues I would like to bring to a discussion at the ITU STG 16 meeting in Berlin. SOURCE : RAD Data Communications LTD. TITLE : Proposals for the next version of H.341 MIB PURPOSE: Proposal *********************************************************** Alexandra Shulman Senior Development Engineer, VoIP Poject RAD Data Communications LTD. 31 Habarzel st. Tel-Aviv, Israel Tel 972-3-7657589 Fax 972-3-6455305 e-mail alexa(a)rad.co.il ***********************************************************

1 0