1. B2bUa uses b2bConfig.xml to configure run time parameters. Refer to the
README.b2bUa for the details of each field.  B2bUA can run with/without 
Authentiction/billing. When running with authentication and billing on, 
make sure that radiusServer is running.

2. The relavant sections in B2bConfig.xml that you may want to change
***
--
  <SIP>
     <Local>
       <Port>5065</Port>
       <Transport>UDP</Transport>
     </Local>
--
The port field defines the port B2bUa is listening on for any incoming
SIP message.Set it to any free port higher than 1024.
****

***
---
     <Proxy_Server>
       <Address>172.19.175.76</Address>
       <Port>7078</Port>
     </Proxy_Server>
---
Define the location of B2bUa's next-hop, where any incoming request to B2bUa
will be forwarded.
*****

*****
---
    <Billing_Server>
       <Address>172.19.175.156</Address>
       <Authentication_Port>1812</Authentication_Port>
       <Accounting_Port>1813</Accounting_Port>
       <Password>vovida</Password>
    </Billing_Server>
---
Address and port where radiusServer is running. The ports are fixed to 
1812, 1813.  The password should match the secret given in server.cfg 
of radiusServer.

****

****
---
  <PrePaid>
    <Billing>
       <Option>free</Option>
---
Valid options are free, mandatory,optional
    free - No auth/billing, radius server is not needed
    mandatory - Call will not go through if billing server can not be reached.
    optional -  Authentication will be done, and if passed call will go
                through even if the billing server can not be reached.
****

4. Sample test scenario
    Calling from 5001 to 5002 via b2bUa. 

    Cisco7960 (5001) ->  B2bUA  --> Cisco7960(5002)
                          |
                          |
                         radiusServer
5. The radiusServer is a simple test server which can understand Radius 
message and returns a preconfigured Auth response message for every call. 
You can modify server.cfg file to configure the  response. Start an xterm 
and run radius server

shell>./radiusServer
     
6. To run b2bUa
      ./b2bUa -d -vLOG_DEBUG -c b2bConfig.xml  



What to expect when you run the test:
1. B2bUa in not a registar so it does not respond to REGISTER messages.
2. The default setting in server.cfg set the pre-paid call duration to be
120 seconds. Any call longer than 120 seconds gets tear-down by B2bUa.
3. In the radiusServer window you should see AccessRequest response, start
billing, interim billing and stop billing request.
4. Should the caller/callee hangs up before 120 sec. the call should tear-down
cleanly.
