[Megaco] Digitmap syntax

G'Day,

The =
assumption behind E.12 was that the payload was symmetrical. We could =
add a
note =
stating this but I believe the additional of an extra parameter is =
beyond
an IG =
item. There no way to add an extra parameter to an event and =
maintain
backward =
compatibility, it would have to be a new =
event.

Regards,  =
Christian

That is a =
very good issue. There is no parameter in the current =
event
notice to =
indicate which of the two payloads changed. While many =
use
symmetric =
payload types this is certainly not a requirement. I =
suppose
we should =
consider adding a parameter of enumeration type with values =
of
send, =
recv, sendRecv to include with the =
notice.

Kevin =
Boyle is our new Implementors Guide editor (as of the end of =
the
SG16 =
meeting today, I am handing over the editorship rather than do =
that
as well =
as rapporteur). Kevin can propose a fix for discussion on the =
list.

Seunghan =
Choi wrote:

  =

Hi, =
All.

Is there =
the case that RTPpayload type(Rx CodecType) in localDescriptor and =
RTPpayload type(Tx CodecType) in remoteDescriptor is =
different?
If there =
is that case, Which does the rtppltype mean, Rx CodecType or Tx =
CodecType, in E.12 Payload =
Transition?

Thanks.

    =

  =

G'Day,

The assumption behind E.12 =
was that the payload was symmetrical. We could add =
a
note stating this but I believe =
the additional of an extra parameter is =
beyond
an IG item. There no way to add =
an extra parameter to an event and =
maintain
backward compatibility, it =
would have to be a new event.

Regards,  =
Christian

That is a very good issue. =
There is no parameter in the current =
event
notice to indicate which of the =
two payloads changed. While many =
use
symmetric payload types this is =
certainly not a requirement. I =
suppose
we should consider adding a =
parameter of enumeration type with values =
of
send, recv, sendRecv to include =
with the notice.

Kevin Boyle is our new =
Implementors Guide editor (as of the end of =
the
SG16 meeting today, I am =
handing over the editorship rather than do =
that
as well as rapporteur). Kevin =
can propose a fix for discussion on the =
list.

Seunghan Choi =
wrote:

  =

Hi, =
All.

Is there the case that =
RTPpayload type(Rx CodecType) in localDescriptor and RTPpayload type(Tx =
CodecType) in remoteDescriptor is =
different?
If there is that case, Which =
does the rtppltype mean, Rx CodecType or Tx CodecType, in E.12 Payload =
Transition?

Thanks.

    =

  =

G'Day,

The =
assumption behind E.12 was that the payload was symmetrical. We could =
add a
note =
stating this but I believe the additional of an extra parameter is =
beyond
an IG =
item. There no way to add an extra parameter to an event and =
maintain
backward =
compatibility, it would have to be a new =
event.

Regards,  =
Christian

That is a =
very good issue. There is no parameter in the current =
event
notice to =
indicate which of the two payloads changed. While many =
use
symmetric =
payload types this is certainly not a requirement. I =
suppose
we should =
consider adding a parameter of enumeration type with values =
of
send, =
recv, sendRecv to include with the =
notice.

Kevin =
Boyle is our new Implementors Guide editor (as of the end of =
the
SG16 =
meeting today, I am handing over the editorship rather than do =
that
as well =
as rapporteur). Kevin can propose a fix for discussion on the =
list.

Seunghan =
Choi wrote:

  =

Hi, =
All.

Is there =
the case that RTPpayload type(Rx CodecType) in localDescriptor and =
RTPpayload type(Tx CodecType) in remoteDescriptor is =
different?
If there =
is that case, Which does the rtppltype mean, Rx CodecType or Tx =
CodecType, in E.12 Payload =
Transition?

Thanks.

    =

  =

G'Day,

The assumption behind E.12 =
was that the payload was symmetrical. We could add =
a
note stating this but I believe =
the additional of an extra parameter is =
beyond
an IG item. There no way to add =
an extra parameter to an event and =
maintain
backward compatibility, it =
would have to be a new event.

Regards,  =
Christian

That is a very good issue. =
There is no parameter in the current =
event
notice to indicate which of the =
two payloads changed. While many =
use
symmetric payload types this is =
certainly not a requirement. I =
suppose
we should consider adding a =
parameter of enumeration type with values =
of
send, recv, sendRecv to include =
with the notice.

Kevin Boyle is our new =
Implementors Guide editor (as of the end of =
the
SG16 meeting today, I am =
handing over the editorship rather than do =
that
as well as rapporteur). Kevin =
can propose a fix for discussion on the =
list.

Seunghan Choi =
wrote:

  =

Hi, =
All.

Is there the case that =
RTPpayload type(Rx CodecType) in localDescriptor and RTPpayload type(Tx =
CodecType) in remoteDescriptor is =
different?
If there is that case, Which =
does the rtppltype mean, Rx CodecType or Tx CodecType, in E.12 Payload =
Transition?

Thanks.

    =

  =

G'Day,

The =
assumption behind E.12 was that the payload was symmetrical. We could =
add a
note =
stating this but I believe the additional of an extra parameter is =
beyond
an IG =
item. There no way to add an extra parameter to an event and =
maintain
backward =
compatibility, it would have to be a new =
event.

Regards,  =
Christian

That is a =
very good issue. There is no parameter in the current =
event
notice to =
indicate which of the two payloads changed. While many =
use
symmetric =
payload types this is certainly not a requirement. I =
suppose
we should =
consider adding a parameter of enumeration type with values =
of
send, =
recv, sendRecv to include with the =
notice.

Kevin =
Boyle is our new Implementors Guide editor (as of the end of =
the
SG16 =
meeting today, I am handing over the editorship rather than do =
that
as well =
as rapporteur). Kevin can propose a fix for discussion on the =
list.

Seunghan =
Choi wrote:

  =

Hi, =
All.

Is there =
the case that RTPpayload type(Rx CodecType) in localDescriptor and =
RTPpayload type(Tx CodecType) in remoteDescriptor is =
different?
If there =
is that case, Which does the rtppltype mean, Rx CodecType or Tx =
CodecType, in E.12 Payload =
Transition?

Thanks.

    =

  =