Switching to H.245

Francois Audet audet at NORTELNETWORKS.COM
Thu May 17 14:06:38 EDT 2001


Guys,
 
H.323/8.1.7.2 says :

After establishment of a call using the Fast Connect procedure, either
endpoint may determine that it is necessary to invoke call features that
require the use of H.245 procedures. Either endpoint may initiate the use of
H.245 procedures at any point during the call, using tunnelling as described
in 8.2.1 (if h245Tunnelling remains enabled) or a separate H.245 connection.
The process for switching to a separate H.245 connection is described in
8.2.3.<?xml:namespace prefix = o ns =
"urn:schemas-microsoft-com:office:office" />

8.2.3 says:

When H.245 encapsulation or Fast Connect is being used, either endpoint may
choose to switch to using the separate H.245 connection at any time.

There seem to be some contradiction in there: is it "after establishment" or
"at any time"?
 
Do you have to wait for after CONNECT to establish a separate H.245 channel
or not?
 
The case I'm interested in would be to send SETUP with fastStart, then
receive ALERTING with fastStart. Then can either end initiate H.245  before
CONNECT? If so, what if third party pause and redirection  is initiated
before CONNECT?
 
----
François AUDET, Nortel Networks
mailto:audet at nortelnetworks.com <mailto:audet at nortelnetworks.com> , tel:+1
408 495 3756
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.packetizer.com/pipermail/sg16-avd/attachments/20010517/977fdd85/attachment-0003.html>


More information about the sg16-avd mailing list