Tom,
I agree with Vineet. I also like to point out that in The H.GCP documents in
paragraph 6.1 the requiremenst section 2 specify audio only. On the other
hand there is a multimedia hints in number 3 and 5.
Roni Even
-----Original Message-----
From: Kumar, Vineet <vineet.kumar(a)INTEL.COM>
To: ITU-SG16(a)MAILBAG.INTEL.COM <ITU-SG16(a)MAILBAG.INTEL.COM>
Date: יום רביעי 21 אפריל 1999 19:36
Subject: Re: Media Gateway Control Requirements
>Tom,
>
>Seems that multimedia is …
[View More]not a requirement in the Megacodraft. I would
>assume that Multimedia would be a requirement from SG16 because that's what
>we do.
>
>vineet
>
>-----Original Message-----
>From: Tom-PT Taylor [mailto:taylor@NORTELNETWORKS.COM]
>Sent: Monday, April 19, 1999 7:41 AM
>To: ITU-SG16(a)MAILBAG.INTEL.COM
>Subject: Media Gateway Control Requirements
>
>
>If Megaco and SG 16 are to come up with a common Media Gateway control
>protocol, we must agree on the requirements. I am attaching a zipped copy
>of the latest draft of the Megaco requirements document, with the hope that
>SG 16 experts will feel free to comment on it. You can pass comments
either
>to this list or to megaco(a)standards.nortelnetworks.com.
>
>A version of this document will be submitted as a Delayed Contribution to
>the Santiago meeting. Depending on the number of comments we receive, that
>version may be the attached one or a revision of it.
>
> <<draft-ietf-megaco-reqs-02.zip>>
>
>Tom Taylor
>E-mail: taylor(a)nortelnetworks.com (internally Tom-PT Taylor)
>Tel.: +1 613 736 0961 (ESN 396-1490)
>FAX: same number by prior arrangement (manual answer).
>
[View Less]
Chris,
Just trying to understand the problem fully before jumping in with a
suggested solution:
How are you expecting people to call via this gateway?
Is the intention to place a call to multiple destionationInfos, specifying
first an alias that identifies the gateway, followed by a full phone number
starting 408 or 409? If not, what is the intended action from an endpoint
attempting to call through this gateway?
Regards,
Chris (P)
--
Dr Chris Purvis - Senior Development Engineer, WAVE CC …
[View More]Software
Madge Networks Ltd, Wexham Springs, Framewood Road, Wexham, Berks. ENGLAND
Phone: +44 1753 661 359 email: cpurvis(a)madge.com
> -----Original Message-----
> From: Rob B [mailto:robb112@HOTMAIL.COM]
> Sent: 21 April 1999 12:17
> To: ITU-SG16(a)MAILBAG.INTEL.COM
> Subject: Re: FW: RRQ Registration in H.323 V2
>
>
> Gaurav,
>
> Nope, it is one single logical gateway. It has only one
> terminalAlias (something like voip-gw.hotmail.com) But it
> supports outgoing voice calls to area codes 408 and 409.
>
> As specified in section 7.2.2 of H.323 V2 spec para 2
> "The use of multiple transport addresses may simplify
> the routing of calls to specific ports". I am trying to
> simplify routing in my gateway.
>
> Is the above statement in H.323 V2 correct now? Is there
> anyone on the list who has tried to do something like
> above?
>
> Or is it that, to acheive my goal I have to divide
> my gateway into logical H.323 entities which I am
> not sure is needed.
> (if each registration of RRQ is allocated a different
> endpoint identifier then from GK perspective there are
> multiple H.323 entities).
>
> Regards,
> -Chris
>
> PS: Endpoint identifier is allocated by GK and returned
> to endpoint via RCF. (The same endpoint identifier will
> be used in keep alive RRQs.) If multiple RRQ's like I proposed
> in my original mail is allowed by H.323 V2 then the
> second RRQ would copy the endpoint identifier from
> first RCF.
>
> >Hi Chris,
> > As per my understanding, you are talking of different logical
> gateways
> >that
> >are bundled together into a single *box*. Each such logical gateway
> must
> >register with the gatekeeper. The terminalAlias could be used to
> identify
> >the
> >logical GW and the callSignalAddress would specify the contact point.
> Hence,
> >you
> >would have to send 2 RRQs. Also, the endpointIdentifier is generated
> by the
> >GK
> >and returned in the RCF and so cannot be specified by the GW at time
> of
> >registration.
> >
> > Any comments?
> >
> >Regards,
> >Gaurav Makkar
> >
> >
> >
> >I have a question on RRQ registration in H.323V2. Let us say
> >I have a gateway that supports area codes 408, 409. I want
> >my gatekeeper to route calls to area codes 408 and 409
> >to my local TCP ports 2000 and 3000 respectively. How should
> >I construct my RRQ message?
> >
> >Shall I send two RRQs with same endpoint identifier
> >(because I have only one gateway) with tuples
> ><408, 2000> and <409, 3000>.
> >
> ><x,y> means: x: carried in SupportedProtocols.prefix
> > y: carried in callSignallingAddress of RRQ message
> >
> >Is my understanding correct?
> >
> >-Chris Rob
> >
> >
> >_______________________________________________________________
> >Get Free Email and Do More On The Web. Visit http://www.msn.com
>
>
> _______________________________________________________________
> Get Free Email and Do More On The Web. Visit http://www.msn.com
>
[View Less]
Hi,
because of problem with our mail server 16-17 of April 1999
Your mail, you sent in these days to email address
elid(a)radvision.rad.co.il
was lost. I would like to ask you to resend the email.
Regards,
Postmaster, RADVision ltd.
Dear SG16 colleagues,
Attached please find Mr. Tosco's additional information on the Santiago
meeting.
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
************************************************…
[View More]***********
Date: Tue, 20 Apr 1999 13:53:11 +0200
From: Tosco Federico <Federico.Tosco(a)CSELT.IT>
To: "Blaschitz, Michael" <michael.blaschitz(a)infonova.at>,"DeGrasse, Bruce"
<b.degrasse(a)cwix.com>, Freundlich <ggf(a)lucent.com>,"Geary, Tom"
<tom.geary(a)CONEXANT.COM>,"Okubo, Sakae"
<okubo(a)giti.or.jp>,"Robin-Champigneul, Yves"
<yves.robinchampigneul(a)cnet.francetelecom.fr>,"Skran, Dale"
<Dale.Skran(a)ascend.com>,"Thom, Gary" <gthom(a)delta-info.com>
MIME-version: 1.0
Dear all,
Returning from the coordination meeting held in Geneva on Saturday April 17,
I give you some information about events connected to the SG16 meeting in
Santiago.
* It is confirmed that an International Workshop will be held on
Monday, May 17
* There will be a conference dinner on Wednesday, May 19
* There will be a farewell lunch on Saturday, May 29, in a famous
vineyard near Santiago (in the conference web site there is an incorrect
indication about the date)
* Please see the conference site (http://www.ict.uchile.cl/itut.sg16/)
for further information
Best regards
Federico
CSELT
Via Reiss Romoli 274
10148 TORINO
Italy
Tel.: +39 0112285321
Fax: +39 0112285295
E_mail: federico.tosco(a)cselt.it
[View Less]
Gaurav,
Nope, it is one single logical gateway. It has only one
terminalAlias (something like voip-gw.hotmail.com) But it
supports outgoing voice calls to area codes 408 and 409.
As specified in section 7.2.2 of H.323 V2 spec para 2
"The use of multiple transport addresses may simplify
the routing of calls to specific ports". I am trying to
simplify routing in my gateway.
Is the above statement in H.323 V2 correct now? Is there
anyone on the list who has tried to do something like
above?
Or …
[View More]is it that, to acheive my goal I have to divide
my gateway into logical H.323 entities which I am
not sure is needed.
(if each registration of RRQ is allocated a different
endpoint identifier then from GK perspective there are
multiple H.323 entities).
Regards,
-Chris
PS: Endpoint identifier is allocated by GK and returned
to endpoint via RCF. (The same endpoint identifier will
be used in keep alive RRQs.) If multiple RRQ's like I proposed
in my original mail is allowed by H.323 V2 then the
second RRQ would copy the endpoint identifier from
first RCF.
>Hi Chris,
> As per my understanding, you are talking of different logical
gateways
>that
>are bundled together into a single *box*. Each such logical gateway
must
>register with the gatekeeper. The terminalAlias could be used to
identify
>the
>logical GW and the callSignalAddress would specify the contact point.
Hence,
>you
>would have to send 2 RRQs. Also, the endpointIdentifier is generated
by the
>GK
>and returned in the RCF and so cannot be specified by the GW at time
of
>registration.
>
> Any comments?
>
>Regards,
>Gaurav Makkar
>
>
>
>I have a question on RRQ registration in H.323V2. Let us say
>I have a gateway that supports area codes 408, 409. I want
>my gatekeeper to route calls to area codes 408 and 409
>to my local TCP ports 2000 and 3000 respectively. How should
>I construct my RRQ message?
>
>Shall I send two RRQs with same endpoint identifier
>(because I have only one gateway) with tuples
><408, 2000> and <409, 3000>.
>
><x,y> means: x: carried in SupportedProtocols.prefix
> y: carried in callSignallingAddress of RRQ message
>
>Is my understanding correct?
>
>-Chris Rob
>
>
>_______________________________________________________________
>Get Free Email and Do More On The Web. Visit http://www.msn.com
_______________________________________________________________
Get Free Email and Do More On The Web. Visit http://www.msn.com
[View Less]
Greetings,
After some delay, I have completed the edits coming out of the Monterey
meeting for the Implementers Guide. Please review the changes and verify
that everything is as expected.
I have incorporated (I believel) all of the relevent text mentioned in the
Meeting report namely:
APCs 1511,1512, 1520, 1522, 1533, 1506, and TDs 10, 14, 33.
If I do not have any comments back by 4/16/99 then I will integrate these
changes with the complete document in preparation for the Chile meeting.
…
[View More]Best Regards,
jimt.
MetaTel - Boston, MA
mailto:jim.toga@metatel.com +1-781-891-9000
PGP keyID E746 1CE4 CEC0 C91E 7190 65CA 70B1 B1D2 6A1E A2B7
[View Less]
The following is an excerpt from H.225 V3:
7.17 Message Not Understood
This message is sent whenever an H.323 endpoint receives a RAS message it
does not understand.
RequestSeqNum - Shall be the requestSeqNum of the unknown message, if it can
be decoded, and zero otherwise.
But in the ASN.1 included, the range for the request sequence number is:
Requestseqnum ::= INTEGER (1..65535)
With my latest version of the OSS compiler, I get a constraint violation
attempting to send …
[View More]a zero request identifier. Is zero still the correct
value when unable to decode a received PDU?
Mike
Michael Ely
mely(a)paknetx.com
http:\\www.paknetx.com
[View Less]
If Megaco and SG 16 are to come up with a common Media Gateway control
protocol, we must agree on the requirements. I am attaching a zipped copy
of the latest draft of the Megaco requirements document, with the hope that
SG 16 experts will feel free to comment on it. You can pass comments either
to this list or to megaco(a)standards.nortelnetworks.com.
A version of this document will be submitted as a Delayed Contribution to
the Santiago meeting. Depending on the number of comments we …
[View More]receive, that
version may be the attached one or a revision of it.
<<draft-ietf-megaco-reqs-02.zip>>
Tom Taylor
E-mail: taylor(a)nortelnetworks.com (internally Tom-PT Taylor)
Tel.: +1 613 736 0961 (ESN 396-1490)
FAX: same number by prior arrangement (manual answer).
[View Less]
Rob B <robb112(a)HOTMAIL.COM> on 04/16/99 11:34:28 PM
Hi Chris,
As per my understanding, you are talking of different logical gateways that
are bundled together into a single *box*. Each such logical gateway must
register with the gatekeeper. The terminalAlias could be used to identify the
logical GW and the callSignalAddress would specify the contact point. Hence, you
would have to send 2 RRQs. Also, the endpointIdentifier is generated by the GK
and returned in the RCF and so cannot …
[View More]be specified by the GW at time of
registration.
Any comments?
Regards,
Gaurav Makkar
I have a question on RRQ registration in H.323V2. Let us say
I have a gateway that supports area codes 408, 409. I want
my gatekeeper to route calls to area codes 408 and 409
to my local TCP ports 2000 and 3000 respectively. How should
I construct my RRQ message?
Shall I send two RRQs with same endpoint identifier
(because I have only one gateway) with tuples
<408, 2000> and <409, 3000>.
<x,y> means: x: carried in SupportedProtocols.prefix
y: carried in callSignallingAddress of RRQ message
Is my understanding correct?
-Chris Rob
_______________________________________________________________
Get Free Email and Do More On The Web. Visit http://www.msn.com
[View Less]
