November 1999 - sg16-avd - lists.packetizer.com

Problem in Connect Message in H.2250 V3
by Aseem Agarwal 23 Nov '99

23 Nov '99

Hi All There is a problem in the additions made to Q.931 part of Connect message in H.2250V3. Two new IEs have been added AFTER User-to-User IE. The IE codes for the new IEs added are: Connected Number : 0x4c Connected Subaddress: 0x4d The IE code for User-to-User is 0x7e According to Q.931 coding Rules [section: 4.5.1], the IEs in a message should be in ascending order of their respective code values. These two IEs should be added after Date/Time IE. Comments ? aseem(a)trillium.com

3 6

H.323 Mobility Meeting Meeting Minutes
by Roy, Radhika R, ALARC 22 Nov '99

22 Nov '99

Hi, Everyone: The detail of our next H.323 Ad Hoc Group conference call is as follows: Next Conference Call Information and Agenda Date: November 29,1999 Time: 8:00 AM to 10:00 AM (Pacific Standard Time (PST)) Reservation # 13617781 Number port reserved: 30 Ports Conference Call Bridge call in number: +1 (415)-904-2888 Passcode: 6752410 (IMTC Representative for facilitating the conference call: Senthil Sengodan, Nokia, senthil.sengodan(a)nokia.com. We appreciate IMTC for facilitating the conference call) Agenda: 1. Call to Order & Opening Remarks 2. Attendance Registration 3. Introduction and Numbering of Contributions: 4. Agenda Review and Approval 4a. Review H.323 Mobility Ad Hoc Meeting report 5. Correspondence to other standards groups: Discussed and identified other standards group like TIPHON, IMTC, IMT-2000 ITU-T SG-11, 3GPP for correspondence 6. Old Business 6a. review Carry over contributions 6b. H.323 Mobility Functional Entities (HLF, VLF, AuF, IWF) 6c. H.323 Mobility Architecture: 6d. 7. New Business 7a. H.323 Interworking with PLMNs (H.246 Annex E scope, Goal and work plan) 8. Meeting Schedule 8a. Discuss next conference call meetings 9. Review Assignments 10. Review Workplan 11. Open Discussion 12. Adjourn Paul Reddy (Intel), Ad Hoc Editor of H.246 Annex E is hereby requested to conduct the meeting. (Some members wanted to know whether any member of SG16 other than the sponsor company may conduct the meetings. We are open to the fact any SG16 member can conduct the meeting irrespective of the fact whether the conference calls are facilitated/hosted/sponsored by a particular company. Every SG16 member is welcome to conduct the meeting.) All contributions will be allocated on or before November 25. The uploading of the documents should be done by November 26 (12:00 AM EST USA). Please contact Paul K. Reddy, Intel Architecture Labs, Intel Corporation, 2111 NE 25th Avenue, Hillsboro, OR - 97124, USA, Office Phone # +1 (503)-264-9896, paul.k.reddy(a)INTEL.COM, http://standard.pictel.com/ftp/avc-site/Incoming/H323_Mobility/ for obtaining the MTD number and uploading the document. The meeting minutes of the last conference call held on November 17, 1999: Conference Call Meeting Summary 1. Call to Order & Opening Remarks Conference call started at 8:15 am, Tuesday, November 17, 1999 hosted by Intel Corporation. 2. Attendance Registration See roster below. 3. Introduction and Numbering of Contributions: MTD-14 A total of 14 contributions were submitted and uploaded to the standards.pictel.com server for reviewing and discussion during this conference call. See the contribution list table below. Contribution MTD-14 was introduced by Intel and AT&T with the list of all H.323 mobility related contributions at SG16 meeting in Red Bank, NJ, USA and for the conference call meeting on November 17, 1999. Contributions are upload and are available for review at: http://standards.pictel.com/ftp/avc-site/Incoming/H323_Mobility/Conference_C all_11_17_1999 and http://standards.pictel.com/ftp/avc-site/9910_Red 4. Agenda Review and Approval Contribution MTD-01 (Agenda, from conference call chair) reviewed and accepted as modified ( * add to the agenda item 5, TIPHON, IMTC, IMT-2000 ITU-T SG11, 3GPP standards group for correspondence * reassign the MTD-03a contribution to agenda item 6 instead of agenda item 6b) 4a. Review H.323 Mobility Ad Hoc Meeting report TD-65.doc TD-65 document was included into the MTD-03a document by the H.323 Annex H editor, deferred to review MTD-03a 5. Correspondence to other standards groups Discussed and identified other standards group like TIPHON, IMTC, IMT-2000 ITU-T SG-11, 3GPP for correspondence 6. Old Business :- MTD-02a, MTD-03a, MTD-04a * Contribution MTD-02a: AT&T presented this document with the summary of the H.323 Mobility work at Red Bank, NJ, USA meeting. * Contribution MTD-03a: H.323 Annex H Editor from Motorola presented this document with inclusion of TD-16, TD-42b and TD-65 as the main H.323 Annex H document. The following changes were suggested by the group: 1. Section 4. Scope: Keep first sentence and delete the rest of the paragraph. 2. Section 5.1: change the title to "Basic concepts that could be used to provide H.323 Mobility" 3. Section 5.2: remove reference to IMT-2000, the title should read as "Mobility Management applicable to H.323" and beginning of the paragraph should read as "H.323 should support the Mobility Management defined as:" * Contribution MTD-04a: H.323 Annex H Editor from Motorola presented this document with new sections to be added to the main H.323 Annex H document. Group agreed to include section 8 title and section 10 title of the MTD-04a document into the main H.323 Annex H document. The section title which are agreed are: 1. H.323 Roaming Interworking with Non-H.323 Networks 2. Non-H.323 Supplementary Services Interwroking 6a. review TD-16, TD-42b TD-16, TD-42b documents were included into the MTD-03a document by the H.323 Annex H editor, deferred to review MTD-03a 6b. H.323 Mobility Functional Entities (HLF, VLF, AuF, IWF):- MTD-06, MTD-07, MTD-09 Contributions MTD-06, MTD-07, MTD-09 are carried over to next conference call, which is scheduled on November 29,1999. 6c. H.323 Mobility Architecture: MTD-05a, MTD-08 Contributions MTD-05a and MTD-08 are carried over to next conference call, which is scheduled on November 29,1999. 6d. 7. New Business 7a. H.323 Interworking with PLMNs (H.246 Annex E scope, terms of reference and work plan): MTD-13, MTD-10a Contributions MTD-13 and MTD-10a are carried over to next conference call, which is scheduled on November 29,1999. 8. Meeting Schedule 8a. Discuss next conference call meetings: MTD-11, MTD-12 * Contribution MTD-11: "Nokia's proposal for IMTC to facilitate all future conference calls only, was agreed by the H.323 Mobility Ad Hoc group. Under the conditions that the SG16 Mobility Ad-Hoc group will continue to work within the ITU SG16 Q13/14 bylaws and procedures. And that the SG16 Mobility Ad-Hoc group was no obligation to IMTC." H.323 Mobility Ad Hoc group agreed to have next conference call on November 29, 1999 from 8:00 AM to 10:00 AM (Pacific Standard Time (PST)) and IMTC to make arrangement for the conference call bridge. * Contribution MTD-12: This contribution from AT&T was withdrawn after the MTD-11 was accepted by the group. 9. Review Assignments 10. Review Workplan 11. Open Discussion * On behalf of Ad Hoc Mobility Group, Radhika Roy, AT&T discussed the H.246 Annex E work progress and requested Paul Reddy, Intel to work as Unofficial Editor to make progress on the H.246 Annex E document, since this group cannot make decision on the Editorship. Intel agreed to work as an unofficial Editor of the H.246 Annex E Document and will bring in a contribution on H.246 Annex E for next conference call. All companies interested in H.246 Annex E are requested to submit contribution for the next conference call. 12. Adjourn Conference call Meeting adjourned Tuesday, November 17, 1999 at 10:20 AM (PST). Attendance Registration for H.323 Mobility Conference Call on November 17, 1999 Name Company Phone FAX E-Mail Paul K. Reddy Intel Corporation 503-264-9896 503-264-3375 paul.k.reddy(a)intel.com <mailto:paul.k.reddy@intel.com> Vineet Kumar Intel Corporation 503-264-3439 503-264-3375 vineet.kumar(a)intel.com <mailto:vineet.kumar@intel.com> Jaakko Sundquist Nokia jaakko.sundquist(a)nokia.com Peeter Pruuden Nokia peeter.pruuden(a)nokia.com Senthil Sengodan Nokia senthil.sengodan(a)nokia.com Pekka Nokia Nokia Radhika R. Roy AT&T rrroy(a)att.com Marc Roelands Siemens marc.roelands(a)siemens.atea.be Edgar Martinez Motorola martinze(a)cig.mot.com Paul Guram Motorola lpg019(a)email.mot.com Milo Orsic Lucent Technology orsic(a)lucent.com Stephen Terrill Ericsson stephen.terrill(a)ericsson.com <mailto:stephen.terrill@ericsson.com> Goesta Linder Ericsson gosta.linder(a)lme.ericsson.se Anders Svennevik Ericsson Anders.Svennevik(a)era.ericsson.se <mailto:Anders.Svennevik@era.ericsson.se> Michael D. Gallagher Synacom Technology mike(a)synacom.com <mailto:mike@synacom.com> Stu Jeffery Synacom Technology stu(a)synacom.com <mailto:stu@synacom.com> Paul E. Jones Cisco paul.jones(a)ties.itu.int <mailto:paul.jones@ties.itu.int> Nextone Barry Aronson Toshiba Corp. baronson(a)acm.org Laurent Thiebaut Alcatel +33 (0)1 3077 0645 laurent.thiebaut(a)alcatel.fr <mailto:laurent.thiebaut@alcatel.fr> Ameneh Zahir-Emami Alcatel Ameneh.Zahir-Emami(a)alcatel.fr <mailto:Ameneh.Zahir-Emami@alcatel.fr> Contributions submitted for H.323 Mobility Conference Call on November 17, 1999 LA MTD Source Title MTDs in the Conf. Call, Nov. 17, 1999 1a Intel H.323 Mobility Ad Hoc Group Interim meeting via Conference Call Agenda 2a AT&T H.323 Mobility Ad Hoc Group Activity Report 3a Motorola Annex-H (User, Terminal and Service Mobility in H.323) 4a Motorola To Complete the H.323 Annex-H draft outline 5a Motorola Integrating 3GPP's option-1 architecture into the H.323 wireless IP mobility system and a full migration from GPRS to a Multimedia IP network proposal 6 Nokia H.323 Annex H Functional Architecture and Reference Points 7 Ericsson "Definition of terms for H.323 Annex H". 8 Alcatel Integrating 3GPP's architecture into the H.323 wireless IP mobility system 9 Alcatel Clear Split of functions between Call Control and (radio) Access networks /Annex-H (User, Terminal and Service Mobility in H.323) 10a Motorola IMT-2000 Global Roaming and Interworking Scenarios 11 Nokia, Intel IMTC Proposal to host future conference calls for H.323 Mobility Ad Hoc group interim ITU-T SG16 Q13/14 work 12 AT&T AT&T's proposal to host next H.323 Mobility Ad Hoc group conference call. 13 Intel H.246 Annex E Goal and Workplan 14 Intel, AT&T List of all H.323 Mobility contribution at SG16 Q13/14 meeting in Red Bank, NJ,USA and Nov 17,1999 conference call Best Regards, Radhika R. Roy H.323 Ad Hoc Mobility Group AT&T +1 732 420 1580 rrroy(a)att.com > >

1 0

OBJECT IDENTIFIER for ISUP
by Francois Audet 22 Nov '99

22 Nov '99

Anybody has an idea what the OBJECT IDENTIFIER should be for the different versions of ISUP? ETSI, ANSI? ----- 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

Definitions of terms for [Robustness]
by Maureen Stillman 22 Nov '99

22 Nov '99

We need to begin a debate of the terms for robustness. The following by Radhika Roy of AT&T is a first set of definitions for your review and comment. Note: The following definitions are a part of the document referenced below: Study Group 16 Delayed Contribution: D.225 (WP 2/16) Santiago, Chile, 17-28 May 1999 Question(s): 13/16 SOURCE*: USA TITLE: Framework for Reliable H.323 Gatekeeper Architectures AUTHOR: Roy, Radhika [rrroy(a)ATT.COM] Reliability: To have the robust GK architecture for increasing reliability (e.g., appropriate redundancy in the architecture as well as robustness of the software codes). Availability: To provision the GK architecture with implications for both the planned (e.g., upgrading, maintenance, etc.) and unplanned (e.g., failures) outages of the GK itself or its components to meet the desired availability goal (e.g., appropriate redundancy in the architecture based on trade-offs between the planned and unplanned outages). Serviceability: To include provision for outage tolerances in the GK level architectural framework to meet the service level requirements (e.g., if 24-hour a day, 7-day a week, and 365-day a year is the requirement for the GK, the GK architectural scheme can be provisioned with redundancy to meet the requirement considering the outages). Recoverability: To keep proper provision within the GK architecture for the recovery time as well as for any signaling messages that might have been in transit at the time of failure Scalability: To be able to increase the throughput by the GK architecture as more resources are put to the system considering the fact that a GK might be used by a large user community (e.g., capability to provide automatic load balancing within the GK architecture with proper redundancy considering outages). Context: To be able to maintain context across multiple requests with minimum latency within a session by the GK architecture in view of outages. Security: To provide adequate security with redundant GK architectures in the event of failures as well as during replications. -- maureen Maureen Stillman Member of Scientific Staff Voice: (607)273-0724 x62 Nokia IP Telephony Fax: (607)275-3610 127 W. State Street Mobile: (607)227-2933 Ithaca, NY 14850 e-mail: maureen.stillman(a)nokia.com www.nokia.com

1 0

Minutes of the [Robustness] telecon on November 17, 1999
by Maureen Stillman 22 Nov '99

22 Nov '99

Minutes of H.323 Robustness Teleconference - November 17, 1999 Prepared by Maureen Stillman, Nokia Next Teleconference: Will be held on Tuesday, December 14 at 11AM EST USA. Nokia will host this again. Please send e-mail to maureen.stillman(a)nokia.com if you wish to join in. Agenda for the next teleconference: Discuss failure scenarios that have been posted to the mailing list by the robustness working group. Action items from this teleconference: 1. Post meeting minutes to mailing list 2. Post terms and definitions from submission D.225 Santiago Chile from R. Roy of AT&T to mailing list to kick off a discussion of terms. 3. Everyone needs to post to the SG16 mailing list one or more failure scenarios that require robustness/recovery mechanisms. Please complete this by December 6 and include in the subject heading the keyword [Robustness]. Anyone is welcome to send a scenario, so please join in. Attending the 11/16 teleconference: Rich Bowen rkbowen(a)cisco.com Paul Jones Paul.jones(a)ties.itu.int Radhika Roy rrroy(a)att.com Orit Levin orit(a)radvision.com Terry Anderson tla(a)lucent.com Kumar, Vineet vineet.kumar(a)intel.com Michael Corrigan Michael_Corrigan(a)mw.3com.com Robert Callaghan Robert.Callaghan(a)ICN.siemens.com Glen Freundlich ggf(a)lucent.com Boaz Michaely Boaz_Michaely(a)vocaltec.com Jean-philippe Caradec caradec(a)piano.grenoble.hp.com Maureen Stillman maureen.stillman(a)nokia.com Yorg Ott jo(a)tzi.uni-bremen.de Michael Vortensy at Vocaltech (please send me your e-mail address) Ed Federmeyer Ed_Federmeyer(a)mw.3com.com Sasha Ruditsky at Radvision (please send me your e-mail address) Summary of Teleconference: Robert Callaghan reported that the direction of the rapporteurs from Study Group 16 was that the robustness working group produce a submission that could be debated and voted on at the February meeting in Geneva. Given this deadline, the group decided on the following course of action: Step 1: Describe scenarios to determine which failures exist (see action item number 3). Step 2: Examine scenarios and determine means to deal with them Step 3: Determine short term measures for dealing with failures and propose them at the Geneva meeting. Discussion: Definition of terms for robustness: We need to define terms. This was supposed to happen on the mailing list over the last month, but no one sent any input. It was suggested that we use R. Roy's definitions in section 2 of D.225 as a starting point for the discussion. These definitions will be posted to the mailing list (see action item 2). Short Term Issue #1: The problem of defining the alternate gatekeeper mechanism is not quite solved. Some of problems with it in the H.323 document were brought up at the Red Bank meeting. Short Term Issue #2: The standard's document does not adequately describe whether we are referring to a TCP connection or a call signaling channel. What is the difference between a disconnect versus an IP failure? We need to carefully go through the standard and clarify in each place clarify what precisely is meant by "call signaling channel". Short Term Issue #3: For systems currently compliant with H.323 v3 or lower, if a call is disrupted the endpoint is left in a "hung" state, meaning that you can't make another call to the endpoint and you can't recover. It was suggested that we deallocate or clear the resources associated with these "hung" calls so that the endpoint can receive new calls and operate normally again. The group decided that we need to perform further analysis before we decide on how to deal with this issue. Goals: The group formulated the following (incomplete) list of goals for the robustness work: 1) Recovery from GK crash 2) Recovery from other components crashing including gateways, MCUs, MGC, etc. 3) GW switching NIC cards during a call 4) Call signaling channel fails; but we don't want to lose a call already in progress between two endpoints. 5) How do you detect a failure? 6) What are the procedures for recovery from a failure? 7) Clarify on how to reestablish call signaling Legacy Issue: Once we have decided on robustness mechanisms, these would be included in version 4 or later of the standard. How do we deal with earlier versions of H.323 that don't handle robustness? How do we deal with the fact that in an operational system some components will support robustness mechanisms and some will not? Call Signaling Channel Issue: Standard currently says that the call signaling channel can be closed during a call and the call will continue. It also states that the call signaling channel can be reopened, but it doesn't say how. The problem is that we don't know how to associate the new connection with any ongoing call. A second problem is that we may need the call signaling channel to establish supplementary services. If the channel has been closed, then we may want to bring it back up for supplementary services. Scenarios: It was decided that the work of the robustness group should be scenario driven. We need to determine what failure scenarios are likely to occur in order to understand how to correct them. It was decided that everyone from the group would submit one or more scenarios in time for the next teleconference for discussion (see action item 3). Please submit these to the list by December 6. Simple Scenario: We discussed the most simple and basic scenario (outlined by Y. Ott): Corporate Environment - 1 gatekeeper; all calls are gatekeeper routed; H.225 up and running; might be using fastconnect; two endpoints have a call in progress Gatekeeper goes down or fails - the two endpoints lose the call signaling channel We agree that such a call needs to be continued - how this should be done is a problem that needs to be solved. -- maureen Maureen Stillman Member of Scientific Staff Voice: (607)273-0724 x62 Nokia IP Telephony Fax: (607)275-3610 127 W. State Street Mobile: (607)227-2933 Ithaca, NY 14850 e-mail: maureen.stillman(a)nokia.com www.nokia.com

1 0

[Fwd: Re: [Fwd: H.323 Mobility: post meeting]]
by Edgar Martinez [1] 19 Nov '99

19 Nov '99

Dear Roberto, I did think we have agreed on the VLF, HLF and AuF definitions, yet. Those terms came out of the Ad-hoc meeting in Redbank. Ed -------- Original Message -------- From: wnk(a)fub.it (Roberto Winkler) Subject: Re: [Fwd: H.323 Mobility: post meeting] To: "Edgar Martinez [1]" <martinze(a)cig.mot.com> Hello, I may have missed some crucial piece of information but can somebody provide me with the number of the contribution where the entities VLF, HLF and AuF are defined ? Thanks very much and best regards Robzerto Winkler >FYI > >-------- Original Message -------- >From: "Edgar Martinez [1]" <martinze(a)cig.mot.com> >Subject: H.323 Mobility: post meeting >To: "H.323 Mobility" <ITU-SG16(a)mailbag.cps.intel.com> > >Dear All, > >I have updated MTD-03 Annex- H outline >now MTD-03b as requested >by the Ad-hoc group. > >For each section I have identify where the section >and text came from. Where we stray from the >annex H "Terms of Reference" it has been noted in >the document e.g., to delete part of "Scope". > >I have also added the change marks and a document >history table to MTD-3b. > >All the documents have been place in: > >http://people.itu.int/~emartine/temp/SG16-mobility/ConfCall_Nov17-99/ > >You also can get access via > >http://people.itu.int/~emartine/ > >Regards, >-- >Edgar Martinez - Principal Staff Engineer >Email mailto:martinze@cig.mot.com >FAX 1-847-632-3145 - - Voice 1-847-632-5278 >1501 West Shure Drive, Arlington Hgts. IL 60004 >Public: TIPHON & Other Stds - http://people.itu.int/~emartine/ >Private:TIPHON & Other Stds - http://www.cig.mot.com/~martinze/ > >------------------------------------------------------------------- >Mail archive for TIPHON_WG7 can be browsed at the following url : > > http://www.etsi.org/tiphon/mailing.htm >------------------------------------------------------------------- Roberto Winkler Senior Researcher Fondazione Ugo Bordoni Via B. Castiglione, 59 00142 Rome Italy tel +39 0654803411 fax. +39 0654804404 e-mail wnk(a)fub.it

1 0

AD Hoc Mobility Gorup Activities
by Roy, Radhika R, ALARC 18 Nov '99

18 Nov '99

Hi, Everyone: I have to report few things after yesterday's conference call as follows: 1. I have requested both editors - Ed Martinez and Paul Reddy to prepare the yesterday's meeting minutes and send it to me for distribution to the SG16 reflector. 2. Both editors have also been requested to prepare a tentative meeting agenda for the upcoming conference call to be held on November 29 and send it to me for distribution to the SG16 reflector. IMTC representative has also been requested to send the conference bridge information for distribution along with the meeting agenda. We provide our sincere thanks to the IMTC for facilitating the SG16 conferencing. 3. All contributions will be allocated on or before November 25. The uploading of the documents should be done by November 26 (12:00 AM EST USA). Please contact Paul K. Reddy, Intel Architecture Labs, Intel Corporation, 2111 NE 25th Avenue, Hillsboro, OR - 97124, USA, Office Phone # +1 (503)-264-9896, paul.k.reddy(a)INTEL.COM, http://standard.pictel.com/ftp/avc-site/Incoming/H323_Mobility/ for obtaining the MTD number and uploading the document. 4. The final agenda for the upcoming conference call on Novemebr 29 will be sent by me (along with editors) on November 26. 5. I will request one of the editors or any other SG16 member to conduct the conference as per agenda on the November 29th conference call (while I plan to act as a moderator behind the scene as I did in the yesterday's conference call). 6. Editors are hereby requested to clearly indicate in the edited documents what has been added as new and what has been in the previous version. The general principle is that editors will add new things based discussions held in the conference calls, discussions via SG16 emails, APCs, TDs, and MTDs. (However, SG16 members are welcomed to discuss any item with editors on one-to-basis to clarify additional points. Editors may include any of those items if these are consistent with the general principle. If editors feel that additional points that need to be included based on private conversations and are not covered in the public discussion as indicated in the general principle, they indicate clearly in the document that those items have been included after private discussions.) 7. I plan to send brief notes related to H.323 Annex I and H.246 Annex E soon. We have seen that Ed Martinez of Motorola had already sent the revised version of H.323 Annex H so promptly that we appreciate his work. We also thanks Paul Reddy of Intel who is working so hard in helping to make the activities of the Ad Hoc Group a success. Finally, we all have been very much encouraged to see the amount of support provided by all members through their lively discussions, contributions, and bringing new ideas for creation of H.323 mobility standards solving complex problems. Definitely, we can make it!! Radhika R. Roy H.323 Ad Hoc Mobility Group AT&T + 1 732 420 1580 rrroy(a)att.com PS: Paul - Kindly put this email as another MTD for the upcoming meeting.

1 0

Re: Problem in Connect Message in H.2250 V3
by Lop Ng 18 Nov '99

18 Nov '99

unsubscibe -----Original Message----- From: Guntram Diehl [mailto:gdiehl@INNOVAPHONE.COM] Sent: Thursday, November 18, 1999 12:55 AM To: ITU-SG16(a)MAILBAG.INTEL.COM Subject: Re: Problem in Connect Message in H.2250 V3 Hi, I would say the table does not indicate a order of the IEs. The order of the IEs within the message is determined by the code value. Guntram > -----Original Message----- > From: Aseem Agarwal [mailto:aseem@trillium.com] > Sent: Wednesday, November 17, 1999 11:44 PM > To: h323implementors(a)imtc.org > Cc: ITU-SG16(a)mailbag.cps.intel.com > Subject: Problem in Connect Message in H.2250 V3 > > > Hi All > > There is a problem in the additions made to Q.931 part of Connect > message in H.2250V3. Two new IEs have been added AFTER > User-to-User IE. > > The IE codes for the new IEs added are: > Connected Number : 0x4c > Connected Subaddress: 0x4d > > The IE code for User-to-User is 0x7e > > According to Q.931 coding Rules [section: 4.5.1], the IEs in > a message > should be in ascending order of their respective code > values. These two > IEs should be added after Date/Time IE. > > Comments ? > > aseem(a)trillium.com > -------------------------------------------------------------- > ----------- > for list subscription instructions, > send email to h323implementors-request(a)imtc.org with text "info" > >

1 0

H.323 Mobility: post meeting
by Edgar Martinez [1] 18 Nov '99

18 Nov '99

Dear All, I have update MTD-03 Annex- H outline now MTD-03b as requested by the Ad-hoc group. For each section I have identify where the section and text came from. Where we stray from the annex H "Terms of Reference" it has been noted in the document e.g., to delete the part of "Scope". I have also added the change marks and a document history table to MTD-3b. All the documents have been place in: http://people.itu.int/~emartine/temp/SG16-mobility/ConfCall_Nov17-99/ You also can get access via http://people.itu.int/~emartine/ Regards, -- Edgar Martinez - Principal Staff Engineer Email mailto:martinze@cig.mot.com FAX 1-847-632-3145 - - Voice 1-847-632-5278 1501 West Shure Drive, Arlington Hgts. IL 60004 Public: TIPHON & Other Stds - http://people.itu.int/~emartine/ Private:TIPHON & Other Stds - http://www.cig.mot.com/~martinze/

1 0

unsubscribe
by wlp 18 Nov '99

18 Nov '99

unsubscribe

1 0