- sg16-avd - lists.packetizer.com

Provisional report of the Red Bank meeting
by Sakae OKUBO 25 Oct '99

25 Oct '99

Dear Q12-14/16 experts, Please be advised that a provisional report of the Red Bank meeting is available at the following place: ftp://standard.pictel.com/avc-site/Incoming/APC-1748.zip or http://standard.pictel.com/ftp/avc-site/Incoming/APC-1748.zip This is an integration of TD-53a (general, Q12), TD-54a (Q13) and TD-47c (Q14) with minimum editing. I will later refine it with all Annexes and the list of participants. I hope this will be useful for your debriefing. Please also be advised that all TDs and missing APC documents have been uploaded to /9910_Red directory. 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

Question on Intels new annex-j h.246 proposal..
by Edgar Martinez 24 Oct '99

24 Oct '99

Dear Paul, An offical new annex-j for h.246 has been opened, proposed by Intel. Which is Interworking H.323 terminals with the legacy GSM and ANSI wireless networks. What this is proposing is a (MSC+VLR) Gateway that provides H.323 access to the Public Land Mobile Network (PLMN). All the voice and supplementary services will still be provided by the Legacy MSCs. And the data services only by H.323. APC 1671 "H.323 with USIM and PLMN Interworking" and APC 1672 "User Mobility and Service Mobility Services for Wireless Subscribers with H.323 terminals accessing MM over IP and PLMN Networks" Question: Does Intel foresee the same concepts, that is using an adjunct (swithed/IP) Gateway used with the legacy Class-5 switches PSTN? to support H.323 terminals on Class 5 switches? Thanks, Edgar Martinez

1 0

All in One
by Harris 23 Oct '99

23 Oct '99

Start your own 1-900 business or Adult Web Site Business! People are making $$$ week, after week in the 1-900 business. We'll teach you all of our incredible secrets that will take your new exciting business to a whole new level! It's The Simplest and Most Exciting Business You Could Ever Start! *You'll use our "state" of the art equipment! *You'll use our "Live 1 on 1 Psychics" & "Chat Line" girls! *You'll use our incredible Date Line program(s)! No chargebacks! Quick payouts! No expertise needed! Complete programs start at only $99 (no additional charges) The only thing you'll have to do is advertise! This is an excellent turnkey business. We also have excellent turnkey programs if you want to own your own "top" of the line adult web site. ACT NOW!!! For a free color brochure: reply to: mailto:santl9@enotify.com?subject=brochure With the following information: Name:_________________ Address:_________________ City/State/Zip:_________________ email address:_________________ Telephone:_________________ (optional) ///////////////////////////////////////////// To be removed permanantly from this list reply to: mailto:p.deen@angelfire.com?subject=remove /////////////////////////////////////////////

1 0

H323mobility:Meeting report
by Edgar Martinez 23 Oct '99

23 Oct '99

Dear All, Please see attached TD-65 from the NJ meeting. We still need to add sections for interworking for example: Non-H.323 Roaming, Mobility and Handover Interworking with H.323 Networks and Terminals. Additional Parameters to Support H.323 Mobile Network and non-H.323 Mobile Station Interworking. Non-H.323 Mobile Station Automatic Registration and Roaming H.323 Interworking Call Flows. H.323 IP Mobility Network Interworking with C7/SS7 INAP. Thanks, Edgar Martinez

1 0

Re: RTCP port number
by El-Gebaly, Hani 22 Oct '99

22 Oct '99

First, I apologize to the reflector if this question has been answered multiple times before. Is there a FAQ for this mailing list? IMO, option 1 is absolutely valid. Some apps may not honor the odd/even rule, and if I recall correctly this requirement has been relaxed a bit in H.323 (correct me if I am wrong). It has been suggested in a few occasions that the odd/even rule is an RTP rule and not an H.225.0 despite the fact that it is mentioned in the spec. Also it is not only "+1", rather the following odd number since the "+1" port may be busy. You can specify an RTCP odd address in OLC for RTCP receive reports and once you get the OLC from the remote endpoint, use the same odd RTCP for Tx reports, and use the lower even number for RTP port and that way you will still be fully compliant. Here is an example START_PDU: ============================= START PDU ============================ LAYER: H245 DIRECTION: Sent PDU_TYPE: OpenLogicalChannel Forward Logical Channel Number: 257 Unicast Address: IP, 209.218.18.91 TSAPIdentifier: 1161 END_PDU: ================================ END PDU ============================= START_PDU: ============================= START PDU ============================ LAYER: H245 DIRECTION: Sent PDU_TYPE: OpenLogicalChannelAck Forward Logical Channel Number: 257 frwrdMltplxAckPrmtrs: H2250LCAPs_mdChnnl: Unicast Address: IP, 209.218.18.91 TSAPIdentifier: 1160 H2250LCAPs_mdCntrlChnnl: Unicast Address: IP, 209.218.18.91 TSAPIdentifier: 1161 END_PDU: ================================ END PDU ============================= START_PDU: ============================= START PDU ============================ LAYER: H245 DIRECTION: Received PDU_TYPE: OpenLogicalChannelAck Forward Logical Channel Number: 257 frwrdMltplxAckPrmtrs: H2250LCAPs_mdChnnl: Unicast Address: IP, 209.218.18.82 TSAPIdentifier: 1030 H2250LCAPs_mdCntrlChnnl: Unicast Address: IP, 209.218.18.82 TSAPIdentifier: 1031 END_PDU: ================================ END PDU ============================= START_PDU: ============================= START PDU ============================ LAYER: H245 DIRECTION: Received PDU_TYPE: OpenLogicalChannel Forward Logical Channel Number: 257 H2250LCPs_mdCntrlChnnl: Unicast Address: IP, 209.218.18.82 TSAPIdentifier: 1031 END_PDU: ================================ END PDU ============================= regards, Hani -----Original Message----- From: Mohamed Mustafa [mailto:M.Mustafa@SDXPLC.COM] Sent: Friday, October 22, 1999 6:15 AM To: ITU-SG16(a)MAILBAG.INTEL.COM <mailto:ITU-SG16@MAILBAG.INTEL.COM> Subject: Re: RTCP port number Hani, Thanks for your reply. There are still a few points I'm not clear on. Your first four points are consistent with my current understanding of the OLC/OLCA messages. I'll elaborate on these points just to try and avoid the ambiguities of my previous email: There are two optional TransportAddress fields (mediaChannel and mediaControlChannel) within the forward logical channel parameters section of the OLC request message. H.245 specifies that the mediaChannel field should not be included in the OLC request when the transport is unicast. The mediaControlChannel field, if present in the OLC request, specifies the address on which the sender of the OLC will be listening for media control messages. If the mediaControlChannel field is not present in the OLC request, this indicates that a control session is not required. The mediaChannel and mediaControlChannel fields are also present in the OLCA response message. The mediaChannel field must be present in a OLCA response when the transport is unicast, and it specifies the address to which the sender of the corresponding OLC must transmit the media. The mediaControlChannel field in the OLCA response specifies the address on which the sender of the OLCA will be listening for media control messages for this session. The mediaControlChannel should only be included in the OLCA response if a media control channel is required (i.e., only if the mediaControlChannel field was present in the corresponding OLC request). Therefore, assuming a control channel is required, each endpoint must transmit and receive three transport address in order to establish a bi-directional media stream; 1) RTCP address in OLC (a1), 2) RTP address in OLCA (a2), and 3) RTCP address in OLCA (a3). To use a single bi-directional RTCP channel, each endpoint must specify the same address in a1 and a3. The +1 rule requires the port numbers in a1 and a3 to be odd, and that a2 and a3 are identical except for the port number where it is one less in a2 compared to a3. My initial question was regarding the case where one of the endpoints supplies a set of addresses where a1 and a2 do not conform to the +1 rule. There are two possibilities in this case: 1) a1 and a3 are the identical - i.e., single bi-directional RTCP channel, but a2 and a3 do not conform to the +1 rule. 2) a2 and a3 conform to the +1 rule - i.e., 2 unidirectional RTCP channels. My original question can be more precisely worded as: Is option 1 valid? Thanks again, Mohamed

1 0

H.450.x related
by Sunil Chandra 22 Oct '99

22 Oct '99

Dear Karl, Why do the H.450 recommendations not talk about the use of RAS protocol? Is it not required (unlikely, I feel it is required)? With regards, Sunil

1 0

Re: RTCP port number
by Mohamed Mustafa 22 Oct '99

22 Oct '99

Hani, Thanks for your reply. There are still a few points I'm not clear on. Your first four points are consistent with my current understanding of the OLC/OLCA messages. I'll elaborate on these points just to try and avoid the ambiguities of my previous email: There are two optional TransportAddress fields (mediaChannel and mediaControlChannel) within the forward logical channel parameters section of the OLC request message. H.245 specifies that the mediaChannel field should not be included in the OLC request when the transport is unicast. The mediaControlChannel field, if present in the OLC request, specifies the address on which the sender of the OLC will be listening for media control messages. If the mediaControlChannel field is not present in the OLC request, this indicates that a control session is not required. The mediaChannel and mediaControlChannel fields are also present in the OLCA response message. The mediaChannel field must be present in a OLCA response when the transport is unicast, and it specifies the address to which the sender of the corresponding OLC must transmit the media. The mediaControlChannel field in the OLCA response specifies the address on which the sender of the OLCA will be listening for media control messages for this session. The mediaControlChannel should only be included in the OLCA response if a media control channel is required (i.e., only if the mediaControlChannel field was present in the corresponding OLC request). Therefore, assuming a control channel is required, each endpoint must transmit and receive three transport address in order to establish a bi-directional media stream; 1) RTCP address in OLC (a1), 2) RTP address in OLCA (a2), and 3) RTCP address in OLCA (a3). To use a single bi-directional RTCP channel, each endpoint must specify the same address in a1 and a3. The +1 rule requires the port numbers in a1 and a3 to be odd, and that a2 and a3 are identical except for the port number where it is one less in a2 compared to a3. My initial question was regarding the case where one of the endpoints supplies a set of addresses where a1 and a2 do not conform to the +1 rule. There are two possibilities in this case: 1) a1 and a3 are the identical - i.e., single bi-directional RTCP channel, but a2 and a3 do not conform to the +1 rule. 2) a2 and a3 conform to the +1 rule - i.e., 2 unidirectional RTCP channels. My original question can be more precisely worded as: Is option 1 valid? Thanks again, Mohamed -----Original Message----- From: El-Gebaly, Hani [mailto:hani.el-gebaly@intel.com] Sent: 21 October 1999 18:32 To: 'Mohamed Mustafa' Subject: Re: RTCP port number Mohamed, Here is how it works: (1) Openchannel specifies the reverse RTCP address (IP and port) that it will receive RTCP information on (RTCP receive reports). (2) It does not specify any RTP or RTCP send ports. (3) openchannelAck specifies the RTP address that the acknowledging terminal will receive on RTP data and the channel owner (one who initiated openchannel) will stream to (send) RTP data. (4) openchannelAck also specifies RTCP address that the channel owner (initiator) ought to send RTCP sener reports data of this channel on. (5) Note that RTP address != RTCP address. Usually the port numbers are shifted by one. (6) RTP uses an even port number and the corresponding RTCP stream uses the next higher (odd) port number (7) A Terminal may choose to retain the same IP port for RTCP Send and Receive reports. So the RTP port is not sent in the OLC rather returned in the OLCA. regards, Hani -----Original Message----- From: Mohamed Mustafa [mailto:M.Mustafa@SDXPLC.COM] Sent: Thursday, October 21, 1999 8:05 AM To: ITU-SG16(a)MAILBAG.INTEL.COM <mailto:ITU-SG16@MAILBAG.INTEL.COM> Subject: RTCP port number Hi Everyone, Annex A of recommendation H.225.0 states that "RTP uses an even port number and the corresponding RTCP stream uses the next higher (odd) port number". Can anyone clarify what the RTCP port number should be if an endpoint uses two different RTP port numbers (one for transmitting and one for receiving). To avoid confusion, I'll describe the specific scenario I'm trying to resolve; Following completion of the H.245 capability exchange and master/slave determination, the following messages are exchanged to establish a pair of unidirectional media streams between the two endpoints. 1). A transmits an OpenLogicalChannel request to B specifying the port number (a1) that it will use to transmit the RTP packets 2). B transmits an OpenLogicalChannel request to A specifying the port number (b1) that it will use to transmit the RTP packets 3). B transmits an OpenLogicalChannelAck response to A specifying the port number (b2) which the RTP packets should be transmitted to 4). A transmits an OpenLogicalChannelAck response to B specifying the port number (a2) which the RTP packets should be transmitted to Normally, a1 and a2 are the same so there is no confusion as to A's RTCP port number. However, the Phone Dialer application that comes with Windows 2000 does not use the same port numbers in the OLC and the OLCA messages. Thanks, Mohamed

1 0

RTCP port number
by Mohamed Mustafa 21 Oct '99

21 Oct '99

Hi Everyone, Annex A of recommendation H.225.0 states that "RTP uses an even port number and the corresponding RTCP stream uses the next higher (odd) port number". Can anyone clarify what the RTCP port number should be if an endpoint uses two different RTP port numbers (one for transmitting and one for receiving). To avoid confusion, I'll describe the specific scenario I'm trying to resolve; Following completion of the H.245 capability exchange and master/slave determination, the following messages are exchanged to establish a pair of unidirectional media streams between the two endpoints. 1). A transmits an OpenLogicalChannel request to B specifying the port number (a1) that it will use to transmit the RTP packets 2). B transmits an OpenLogicalChannel request to A specifying the port number (b1) that it will use to transmit the RTP packets 3). B transmits an OpenLogicalChannelAck response to A specifying the port number (b2) which the RTP packets should be transmitted to 4). A transmits an OpenLogicalChannelAck response to B specifying the port number (a2) which the RTP packets should be transmitted to Normally, a1 and a2 are the same so there is no confusion as to A's RTCP port number. However, the Phone Dialer application that comes with Windows 2000 does not use the same port numbers in the OLC and the OLCA messages. Thanks, Mohamed

1 0

subscribe
by Fiorenzo Gamba 21 Oct '99

21 Oct '99

-- \\\|/// \\ ~ ~ // (/ @ @ /) +-------------------------oOOo-(_)-oOOo-----------------------------+ Engenieer School of Fribourg Fiorenzo GAMBA Project developer db. de Pérolles 80 1705 Fribourg -Switzerland- Phone : ++41 26 429 67 43 E_mail : fiorenzo.gamba(a)eif.ch http://www.eif.ch Our lab : http://artemis.eif.ch:8080 +-------------------------------------------------------------------+ Oooo. .oooO ( ) ) ( ) ) ) / \ ( (_/ \_)

1 0

Signaling Transport (Fwd: I-D ACTION:draft-ietf-sigtran-sctp-01.txt)
by Chip Sharp 19 Oct '99

19 Oct '99

FYI, This is the baseline text of the Simple Common Transport Protocol being defined by sigtran for transporting PSTN signaling. Chip >X-SMAP-Received-From: outside >Date: Tue, 19 Oct 1999 06:53:04 -0400 >Reply-To: Internet-Drafts(a)ietf.org >Sender: "Signaling Transport (sigtran)" > <SIGTRAN(a)STANDARDS.NORTELNETWORKS.COM> >Comments: RFC822 error: <W> Incorrect or incomplete address field >found and > ignored. >From: Internet-Drafts(a)ietf.org >Subject: I-D ACTION:draft-ietf-sigtran-sctp-01.txt >To: SIGTRAN(a)STANDARDS.NORTELNETWORKS.COM > >A New Internet-Draft is available from the on-line Internet-Drafts >directories. >This draft is a work item of the Signaling Transport Working Group of the >IETF. > > Title : Simple Control Transmission Protocol > Author(s) : R. Stewart, Q. Xie, K. Morneault, C. Sharp, > H. Schwarzbauer T. Taylor, I. Rytina, > M. Kalla, L. Zhang, V. Paxson > Filename : draft-ietf-sigtran-sctp-01.txt > Pages : 36 > Date : 18-Oct-99 > >This document describes the Simple Control Transmission Protocol >(SCTP). SCTP was designed to transport PSTN signalling messages over >IP networks, but is capable of broader application. >SCTP is an application-level datagram transfer protocol operating on >top of an unreliable datagram service such as UDP. It offers the >following services to its users: >- acknowledged error-free non-duplicated transfer of user data >- application-level segmentation to conform to discovered MTU size >- sequenced delivery of user datagrams within multiple streams, >with an option for order-of-arrival delivery of individual >datagrams >- optional multiplexing of user datagrams into SCTP datagrams, >subject to MTU size restrictions >- enhanced reliability through support of multi-homing at either or >both ends of the association. >The design of SCTP includes appropriate congestion avoidance behaviour >and resistance to flooding and masquerade attacks. > >A URL for this Internet-Draft is: >http://www.ietf.org/internet-drafts/draft-ietf-sigtran-sctp-01.txt > >Internet-Drafts are also available by anonymous FTP. Login with the username >"anonymous" and a password of your e-mail address. After logging in, >type "cd internet-drafts" and then > "get draft-ietf-sigtran-sctp-01.txt". > >A list of Internet-Drafts directories can be found in >http://www.ietf.org/shadow.html >or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > >Internet-Drafts can also be obtained by e-mail. > >Send a message to: > mailserv(a)ietf.org. >In the body type: > "FILE /internet-drafts/draft-ietf-sigtran-sctp-01.txt". > >NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this > feature, insert the command "ENCODING mime" before the "FILE" > command. To decode the response(s), you will need "munpack" or > a MIME-compliant mail reader. Different MIME-compliant mail readers > exhibit different behavior, especially when dealing with > "multipart" MIME messages (i.e. documents which have been split > up into multiple messages), so check your local documentation on > how to manipulate these messages. > > >Below is the data which will enable a MIME compliant mail reader >implementation to automatically retrieve the ASCII version of the >Internet-Draft. >Content-Type: text/plain >Content-ID: <19991018121940.I-D(a)ietf.org> > >ENCODING mime >FILE /internet-drafts/draft-ietf-sigtran-sctp-01.txt > ><ftp://ftp.ietf.org/internet-drafts/draft-ietf-sigtran-sctp-01.txt> Support NetAid! http://www.netaid.org -------------------------------------------------- Chip Sharp Consulting Engineering Cisco Systems Telco Bio-region Reality - Love it or Leave it. --------------------------------------------------

1 0