Use H.245 tunnelling.
Also, H.323v4 will explain how to do TCS and M/S at the same time as fastStart during call setup so that they be completed extremely rapidly. See 8.2.3 of the H.323v4 draft.
If you need H.323v2 or v3, you can still use H.245 tunnelling, and initiate TCS and M/S from the called end as soon as possible (right after sending fastStart)
-----Original Message----- From: Dan Davidson [mailto:dan.davidson@commatch.com] Sent: Tuesday, October 31, 2000 1:09 AM To: 'Paul E. Jones' Cc: h323implementors Subject: RE: Fast Connect - Switching to H.245 procedure / UII vs. Keypad IE
(This mail is a fusion of two previously separated streams: Fast Connect - Switching to H.245 procedure and UII vs. Keypad IE)
Paul, All this would mean that when using fast connect to set-up a call against and IVR (i.e. calls in which DTMF are sent immediately after call set-up), H.245 UII messages shall be used for DTMF transport and the first H.245 UII message has to be preceded by Capability Exchange and Master Slave Determination procedures. Isn't this slow ( and I'm not counting in all the TCP connection set-up when tunnelling is not supported)?
Isn't there a faster, standardised, way to convey DTMF when using fast connect ?
Thanks, Dan
-----Original Message----- From: Paul E. Jones [mailto:paulej@packetizer.com] Sent: Tuesday, October 31, 2000 7:59 AM To: Dan Davidson; h323implementors@imtc.org Subject: Re: UII vs. Keypad IE
Dan,
An endpoint that communicates with a SET device may certainly do this-- and must if they expect to get DTMF digits from a SET device. However, two non-SET devices should not use this method. As far as I know, there is no means of signaling to the other endpoint that you have the "capability" of using the keypad IE. That means that any non-SET device must use UII.
That might be something worth considering as a means of removing further dependencies on H.245. We could very easily add such support and signal it within H.225.0. However, I have seen no proposals for that.
Paul
-----Original Message----- From: Paul E. Jones [mailto:paulej@packetizer.com] Sent: Tuesday, October 31, 2000 7:59 AM To: Dan Davidson; h323implementors@imtc.org Subject: Re: Fast Connect - Switching to H.245 procedure
Dan,
There's nothing hidden there. Essentially, this text is re-enforcing the idea that Fast Connect does not somehow bypass any of the H.245 messages (except that channels are opened). When starting H.245, you send the H.245 terminal capability set and the master/slave determination messages as appropriate.
Paul
----- Original Message ----- From: "Dan Davidson" dan.davidson@commatch.com To: h323implementors@imtc.org Sent: Monday, October 30, 2000 2:38 PM Subject: Fast Connect - Switching to H.245 procedure
The H.323v2 Recommendation describes the Fast Connect procedure and
mentions
that if necessary, a H.245 connection can be established.
It also mentions: " When H.245 procedures are activated,
all mandatory
procedures of H.245 that normally occur upon initiation of an H.245
connection shall be
completed prior to initiation of any additional H.245 procedures."
Question: What are the H.245 mandatory procedures the recommendation
refers
to ?
Dan
Please send E-mail to contact@imtc.org mailto:contact@imtc.org to subscribe or unsubscribe from this list
Please send E-mail to contact@imtc.org mailto:contact@imtc.org to subscribe or unsubscribe from this list