configuration.xml.svn-base

在Diameter3588协议的基础上开发的软件

                                     sent to the redirect host
                    4  ALL_APPLICATION - All messages for the application
                                     requested MAY be sent to the redirect host
                    5  ALL_HOST    - All messages that would be sent to the
                                     host that generated the Redirect-Host 
                                     MAY be sent to the redirect host
                    6  ALL_USER    - All messages for the user requested MAY 
                                     be sent to the redirect host -->
             <redirect_usage>0</redirect_usage>

             <!-- For each route, there is a set of applications
                  that are supported. This is used by the base
                  protocol library as the second index to resolving
                  a route for a message --> 
             <application>

                  <!-- Application Id is used as a second key for 
                       routing queries. See details above -->
                  <application_id>1</application_id>

                  <!-- For vendor specific application id's. As
                       per RFC this should be 0 for standard
                       track applications. Otherwise, this
                       value is used in conjunction with
                       application_id as a second search key -->
                  <vendor_id>0</vendor_id>

                  <!-- For each application, there can be a set
                       of servers support it. Each server has
                       a metric associated with it and the 
                       routing engine chooses the server in
                       metric order (0 being highest) -->
                  <peer_entry>

                      <!-- Diameter peer serving this realm and
                           application id. This server name
                           MUST exits in the peer table for
                           this route to be active.
                      <server>server1.research.org</server>
 
                      <!-- Metric value for this server entry.
                           The higher the value, the lower the
                           preference. 0 is the highest value
                           and entries with equal value will 
                           be resolve in the order they are
                           defined in this configuration file -->
                      <metric>1</metric>  
                  </peer_entry>
                  <peer_entry>
                      <server>server2.research.org</server>
                      <metric>5</metric>  
                  </peer_entry>
             </application>
             <application>
                  <application_id>
                       <id>1</id>
                       <type>1</type>
                  </application_id> 
                  <peer_entry>
                      <server>server1.research.org</server>
                      <metric>1</metric>  
                  </peer_entry>
                  <peer_entry>
                      <server>server6.research.org</server>
                      <metric>5</metric>  
                  </peer_entry>
             </application>
          </route>

          <!-- The definition of a default route is the same
                as for any other route. The existance of a
                default route means that all no-match queries
                will result in a default route return -->
          <default_route>
             <realm>research.telcordia.com</realm>
             <role>full</role> 
             <application>
                  <application_id>
                       <id>1</id>
                       <type>1</type>
                  </application_id> 
                  <peer_entry>
                      <server>server1.research.org</server>
                      <metric>1</metric>  
                  </peer_entry>
                  <peer_entry>
                      <server>server2.research.org</server>
                      <metric>5</metric>  
                  </peer_entry>
             </application>
             <application>
                  <application_id>
                       <id>5</id>
                       <type>1</type>
                  </application_id> 
                  <peer_entry>
                      <server>server1.research.org</server>
                      <metric>1</metric>  
                  </peer_entry>
                  <peer_entry>
                      <server>server6.research.org</server>
                      <metric>5</metric>  
                  </peer_entry>
             </application>
          </route>
      </route_table>
   </transport_mngt>

   <!-- Session manager configuration table. This section
        consist of fixed elements that MUST exists -->
   <session_mngt>

      <!-- Dictates the maximum number of concurrent
           sessions that will be maintained by open
           diameter. These include both auth and acct
           sessions -->
      <max_sessions>10000</max_sessions>

      <!-- The following dictates default values for
           auth sessions -->
      <auth_sessions>

         <!-- Stateful session flag. If set to 1, then
              server will enforce stateful sessions and
              clients will hint for stateful sessions. If
              set to 0 or if missing then stateless sessions.

              The value of auth-session state can actually 
              negotiated between client and server. So for 
              the server, auth-session-state is used as follows:

              1. If the request message sent by the client 
                 contains an auth-session-state, the server 
                 check's it's own configuration. If the values 
                 are equal then the server uses that value to 
                 determine statefulness. If the values are not 
                 equal and the server's configuration is set to 
                 AAA_SESSION_STATE_MAINTAINED, then the client's 
                 value determines the statefulness of the session. 
                 If the values are not equal and the server's 
                 configuration is NOT AAA_SESSION_STATE_MAINTAINED 
                 then the server's configuration determines the 
                 statefulness.
              2. If the request message sent by the client does 
                 not contain an auth-session-state, the server 
                 check's the settings of SetAuthSessionState() 
                 function. If SetAuthSessionState() returns a 
                 value, it is used to determine the statefulness 
                 of the session otherwise the configuration value 
                 is used.

              Based on the above policy, the server will return 
              an auth-session-state avp in answer message.

              For the client:

              1. The initial request sent by the client can contain 
                 an auth-session-state value as a hint to the server. 
                 This value is taken from the settings of SetAuthSessionState() 
                 function. If SetAuthSessionState() returns a value, 
                 it is used to as a hint value otherwise the configuration 
                 value is used.
              2. If the answer message sent by the server contains 
                 an auth-session-state, then that value will be used 
                 by the client. If no auth-session-state avp is sent, 
                 then the hint sent in (1) is used.
           -->
         <stateful>1</stateful>

         <!-- Timeout in seconds before a session requires 
              re-authentication. For stateless sessions, a value
              of zero(0) will cause the client session to be maintained
              indefinitely. For stateless server sessions, the library
              will ask you periodically if you want to reclaim the session
              in ReClaimSession() method -->
         <session_timeout>30</session_timeout>

         <!-- Timeout in seconds before a session is 
              terminated regardless of wether it has
              been re-authenticated -->
         <lifetime_timeout>360</lifetime_timeout>

         <!-- Grace period after lifetime timeout before
              full termination -->
         <grace_period_timeout>30</grace_period_timeout>

         <!-- Timeout before subsequent ASR messages
              are sent if the inital attempt fails -->
         <abort_retry_timeout>20</abort_retry_timeout>

      </auth_sessions>

      <!-- The following dictates default values for
           acct sessions -->
      <acct_sessions>

         <!-- Timeout in seconds before a session requires 
              re-authentication -->
         <session_timeout>30</session_timeout>

         <!-- Record interim interval dictated to the client
              if this entity is a server or hint to the server
              if this is a client -->
         <interim_interval>5</interim_interval>

         <!-- Realtime required value dictated to the client
              if this entity is a server or hint to the server
              if this is a client -->
         <realtime>1</realtime>

      </acct_sessions>

   </session_mngt>

   <!-- Log section dictates the verbose levels that
        the library generates as well as target outputs -->
   <log>

      <!-- The following are the available log levels
           that can be "enabled" or "disabled" -->
      <flags>
         <debug>disabled</debug>
         <trace>disabled</trace>
         <info>disabled</info>
      </flags>

      <!-- The following are the target outputs of
           the logs. It can be a combination of
           each entry -->
      <target>
         <!-- enables or disables terminal output -->
         <console>enabled</console>
         <!-- enables or disables syslog output -->
         <syslog>disabled</syslog>
      </target>
   </log>
</configuration>