Subject: RE: [Megaco] Re: Packages extension (question 2)

From: "Kevin Boyle" <[email-masked]>
Date: Thu, 2 Jun 2005 18:22:19 -0400

I will note that the event 'dd/*' actually has problems that make it
difficult, if not impossible, to use.  In fact, any package with an event
that requires a parameter will have problems with this syntax.

Remember that dd/* means "all events in the dd package".  This include the
dd/ce event.  This event requires a DigitMap descriptor or name as a
parameter of the event.  Because there is no way to indicate parameters that
are unique to a single event amongst a wildcarded group like this, the
specification of the dd/ce violates its definition.  dd/* ought to be NACKed
by a receiving MG as not containing required parameters.

Kevin

-----Original Message-----
From: [email-masked] [mailto:[email-masked]] On Behalf Of
Julio Martinez-Minguito (AL/EAB)
Sent: Thursday, June 02, 2005 3:14 AM
To: [email-masked]
Subject: [Megaco] Re: Packages extension (question 2)

Hi:

Thanks for your mails that had help me a lot to understand the syntax of the
extended packages.
But I still have another question:

Signals syntax is:
  dg/pt {tl = [d0, d1]}
But is it valid
  dg/d1
being d1 a signal in 'dg'?

For the events and observed events descriptor we have:
  Events = 1 { dd/std {tl = [d2, d3, d4]}}
  ObservedEvents = 1 { dd/std {tid = d2} }

If the events descriptor is:
  Events = 1 { dd/* }
Is it valid
  ObservedEvents = 1 { dd/d2 }
or should be
  ObservedEvents = 1 { dd/std {tid = d2} }

thanks for your help, Julio

And for the observed events descriptor

   dd/std {tl = [d2, d3, d4]}, tonedet/std {tl = [d2, d3, d4]}} and it
detects f.e. "d2" stat tone:
  ObservedEvents = 1 { dd/std {tid = d2} }, or
  ObservedEvents = 1 { tonedet/std {tid = d2} } ?

Please see answers below inline.

At 12:23 AM 9/4/2002, Fhuval Hittay wrote:

	Thanks for answer, but there is one more question. "tonedet" package
has "std"
	event with "tl" parameter, and that parameter has only one possible
value "*".
	Suppose such a situation: MG received following Events descriptor
	Events = 1 { tonedet/std {tl = *} }
	and it detects "d2" start tone. Which ObservedEvents descriptor MG
has to notify
	ObservedEvents = 1 { tonedet/std {tid = *} }
	or something different?
Events descriptor above would match no events as tonedet itself has no
individual events ids. The only reason * is defined in tonedet is such that
it does not have to be defined in all the packages that extents it, since
the meaning of * is exactly the same no matter what package it is defined
in. So you should really use this:
Events = 1 { dd/std {tl = *} }
and then on d2 start detect MG will send ObservedEvents = 1 { dd/std {tid =
d2} }

	But there is said "Extensions to this package would add
	additional possible values for tone id". Does it mean that instead
of "*" we
	could use "dd" package's tones?
Not instead, but in addition to, and only in scope of dd package (see
above).

	And what about "tonegen" package? In section E.3.3 is said:
	"No tone ids are specified in this package. Packages that extend
this package
	can add possible values for tone id as well as adding individual
tone signals".
	Does it mean, that if "dd" package extends "tonegen" package, we can
use
	"tonegen/pt {tl = [d0, d1]}" form?
No, other way around, that means that dd package can use tonegen's signals
and its params, that is:
"dd/pt {tl = [d0, d1]}"

Cheers.
        Aleks

	Thanks in advance.

	-----------------------------

	From:  Aleksandr Ryabin <[email-masked]>
	Subject:  Re: [Megaco] Packages extension

	>Hi,
	>
	>         Usage of signal/event IDs apply only in the scope of the
package
	>which defines them, or packages that extends that package.
	>Thus you can not use d0 in tonegen, it does not know what d0 is.
	>
	>To clarify, let say there is another packages dgx which also
extends
	>tonegen and also defines d0, like dg package, but it means
something
	>different.
	>If you were to use base package to access d0 then you would get the
same
	>tonegen/pt {tl = [d0, d1]}  As you can see there is no way to
distinguish
	>which package is being used: dg or dgx.
	>
	>The answers to your questions below are:
	>dg/pt {tl = [d0, d1]}
	>dd/std {tl = [d2, d3, d4]}
	>Events = 1 { dd/std {tl = [d2, d3, d4]}}
	>ObservedEvents = 1 { dd/std {tid = d2} }
	>
	>Cheers.
	>         Aleks
	>
	>At 01:19 AM 9/3/2002, Fhuval Hittay wrote:
	>>  Hello all!
	>>In RFC there is said that "dg" package extends "tonegen" package,
and does
	>it
	>>mean that I can use:
	>>    dg/pt {tl = [d0, d1]}
	>>instead of:
	>>    tonegen/pt {tl = [d0, d1]} ?
	>>
	>>Also "dd" package extends "tonedet" package. And instead of:
	>>    tonedet/std {tl = [d2, d3, d4]}
	>>I can use:
	>>    dd/std {tl = [d2, d3, d4]} ?
	>>
	>>Question is: What is the difference between theese two forms of
usage?
	>Which
	>>ObservedEvents descriptor MG has to return if it has following
	>>EventsDescriptor:
	>>   Events = 1 { dd/std {tl = [d2, d3, d4]}, tonedet/std {tl = [d2,
d3,
	>d4]}}
	>>and it detects f.e. "d2" stat tone:
	>>  ObservedEvents = 1 { dd/std {tid = d2} },
	>>or
	>>  ObservedEvents = 1 { tonedet/std {tid = d2} } ?
	>>
	>>Please, answer ASAP. Thanks in advance.
	>>_______________________________________________

_______________________________________________
Megaco mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/megaco

_______________________________________________
Megaco mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/megaco