[GnomeMeeting-list] RADVISION

[Damien Sandras <dsandras seconix com>]

If I remember correctly, somebody once told me about problems when
connecting GM to RadVision software.

Here is the solution.

If that person reads that mail, then please mail me back :-)

-----Message suivi-----

> From: Jerry Albro <Galbro cosmocom com>
> To: openh323 openh323 org
> Subject: RE: [OpenH323]h245Address compatibility problem?
> Date: 17 Apr 2002 10:14:57 -0400
> 
> Typical Radvision applications use a file called config.val to configure the stack at startup. 
> 
> As noted earlier on this list, it seems some developers are apparently so intimidated by the file format they don't change the default Radvision file, not even to change the productId field from 'Test application' :-)
> 
> Anyway, in the Radvision config file, one section looks like this:
> 
> 
> 1 Q931 = 0
> +  responseTimeOut = 15
>    connectTimeOut = 60
>    callSignalingPort = 1720
>    maxCalls = 20
>    earlyH245 = 1
>    h245Tunneling = 1
>    manualAccept = 1
> 
> 
> The 'earlyH245' parameter specifies that the H245 signaling address be presented in the setup message. Simply comment out the line with a # character and your problem goes away. 
> 
> It is possible to configure the stack totally in memory programmatically, so it is possible that this file does not exist, but it probably does.
> 
> If you do go hacking in the config.val file, note that it represents an ASN.1 tree. So the first column specifies the nesting level. A number sets a specific level, and + or - makes the entry one deeper or higher in the tree, and blank is the same level. Many entries like the 'earlyH245' are booleans that are true if present and false if missing. Changing the '= 1' to '= 0' does exactly nothing in these cases.
> 
> - Jerry Albro
> 
> 
> 
> 
> 

-- 
 _	Damien Sandras
(o-	GnomeMeeting - H.323 Video-Conferencing application -
//\		web:  http://www.gnomemeeting.org/
v_/_	FOSDEM 2002  - Free Software and Open Source Developers Meeting -
		web:  http://www.fosdem.org/