1. Download the tar ball. 2. create a user named BOL B2BUA. # adduser BOL B2BUA set the user password: # passwd BOL B2BUA 3. Untar the B2BUA tar into the BOL B2BUA home directory using the command: - Linux: tar -C /home/BOL B2BUA -xvzf BOL B2BUA-n.n.n.tar.gz or you can modify the startup.sh script for your own environment. Where: n.n.n is the version number. 4. add a directory in the /tools ( root user privilege needed ). Extract the tools.tar.gz into the tools directory using the following command: mkdir -vp /tools && tar -C /tools tools.tar.gz 5. USING THE SOFTWARE -------------------------------------------------------------------- [BOL B2BUA@ngsw-dev3 /home/BOL B2BUA]$ ./BOL B2BUA -h program built at: Dec 7 2006 10:34:00 ProductName: BOL B2BUA ProductVersion: v3.1 (build 20061123) Usage: ./BOL B2BUA [-V] [-h] [-b] [-d] [-f log-filename] [-v DEBUG_LEVEL] [-c config_file] [-p port] DESCRIPTION -V Product Info -b build information -d do not fork into background (no daemon mode) -f log-filename output log to log-filename -v DEBUG_LEVEL set the debug level DEBUG_LEVEL available options log output Priorities (from the highest to lowest) : LOG_EMERG /** system is unusable */ LOG_ALERT /** action must be taken immediately */ LOG_CRIT /** critical conditions */ LOG_ERR /** error conditions */ LOG_WARNING /** warning conditions */ LOG_NOTICE /** normal but significant condition */ LOG_INFO /** informational */ LOG_DEBUG /** debug-level messages */ LOG_DEBUG_STACK /** stack debug-level messages */ LOG_DEBUG_OPER /** stack operator debug-level messages */ LOG_DEBUG_HB /** heartbeat debug-level messages */ LAST_PRIORITY /** an alias for the last cpLog priority level, for use in bounds-checking code */ -c config_file specify a configfile To execute the B2BUA, reading its configuration from a flat file: ./b2bua -c b2bConfig.xml -v LOG_INFO -f b2b.log Example scenerio using the b2bConfig.xml: +---<-------> RADIUS | 192.168.0.20 | proxy, RADIUS <--------> B2bUA <-----> UA2 192.168.0.20:5060 192.168.0.40:15060 192.168.0.78:5067 6. If you need a higher capacity b2bua, please contact us to acquire commercial License. The BOL B2BUA will generate a keyreq.dat under the same directory as your current directory. This is used for the commercial License key generation. If you are using the Trial Version, there will be a 20 capacity (20 concurrent calls) limit on the B2BUA. 7. Please read the README for detail information about BOL B2BUA.