Michael -

You're right.  In NetMeeting 3.01 they're more in line
with what the H.323 protocol suggests for making
combined H.323/T.120 calls.  First an H.323 call is
placed and when logical channels are negotiated for
Video and Audio in H.245, a third logical channel is
negoatiated for T.120 data.  Only then is the T.120
call actually placed.  The neat thing is that if you
have a H.323 proxy or H.323/H.320 gateway, you can
specify a port other than 1503 for netmeeting to
establish the T.120 connection with.

I figure that they've got a fallback mechanism for
interoperability with T.120-only entities - by
attempting a T.120 call to port 1503 if the H.323 call
completely fails.

Ciril Thomas

--- "Fennell, Michael" <[EMAIL PROTECTED]> wrote:
> 
> I run separate H.323 and T.120 bridges on the same
> machine.  With NM2.x,  I
> would get a list of T.120 conferences available when
> I called.  After
> picking one, the T.120 connection would be made,
> then the H.323 connection.
> Worked perfectly for us.
> 
> Now, I *just* noticed (we normally use an
> application built on the SDK that
> makes separate data and audio calls) that if I use
> NM3.0.1, the H.323
> connection is made but not the T.120.  I have a
> feeling that it makes the
> H.323 connection then tries to open a T.120 data
> channel through it, though
> I don't have a simple way to test this.
> 
> If only the T.120 bridge is running on the machine
> I'm calling, the
> connection happens normally.
> 
> Anyone else see this?  Luciano?
> 
> Thanks,
> Michael Fennell
>
-----------------------------------------------------------------------
> http://www.meetingbywire.com/Mailinglist.htm for
> unsubscribe information
>
-----------------------------------------------------------------------
> 
> 

__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com
-----------------------------------------------------------------------
http://www.meetingbywire.com/Mailinglist.htm for unsubscribe information
-----------------------------------------------------------------------

Reply via email to