TCS is always first message, not TCSAck

Pete Cordell pete at TECH-KNOW-WARE.COM
Tue Nov 7 12:21:25 EST 2000


Another option is a TCS 0.6 which contains a token Transmit capability, say
G.711.
Endpoints should accept this as they might have ended up connected to an
announcement IVR.

Pete.

=============================================
Pete Cordell
Tech-Know-Ware
pete at tech-know-ware.com
+44 1473 635863
=============================================

----- Original Message -----
From: Douglas Clowes <dclowes at DINGOBLUE.NET.AU>
To: <ITU-SG16 at mailbag.cps.intel.com>
Sent: 05 November 2000 12:30
Subject: Re: TCS is always first message, not TCSAck


> Paul,
>
> Ugly! That leaves open the decision, for the receiver of the TCS, of when
> you give up on a call because you do not have compatible capabilities.
>
> I can see that an empty-ish TCS could be distinguished from a TCS that
> isn't empty, but contains codecs I can't match. But how many EPs out there
> would already appreciate the distinction? If I send TCS 0.5, will my peer
> drop the call?
>
> Ugly!
>
> Douglas
>
> At 21:13 04/11/2000 -0600, Paul Long wrote:
> >Regarding Douglas' concern, regardless of whether "an EP _should_ be able
to
> >ack a received message, even before sending TCS" (emphasis mine), the
fact
> >remains that it _shall not_ do this, except when indicating that it
> >understands earlyH245Control. The solution to the particular problem he
> >mentions is for the endpoint to send an "almost empty" TCS, or "TCS=0.5"
> >:-). All it contains is sequenceNumber, protocolIdentifier, and--here's
the
> >important part--multiplexCapability. In particular, it doesn't need to
> >contain capabilityTable or capabilityDescriptors, and the
> >multiplexCapability can provide only minimal information. Including
> >multiplexCapability means that it is not an empty TCS and therefore
cannot
> >be mistaken for one, but the endpoint also does not need to know its
> >eventual capabilities at call-startup time.
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> For help on this mail list, send "HELP ITU-SG16" in a message to
> listserv at mailbag.intel.com
>

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For help on this mail list, send "HELP ITU-SG16" in a message to
listserv at mailbag.intel.com



More information about the sg16-avd mailing list