Brian Waters | 13d9601 | 2017-12-08 16:53:31 -0600 | [diff] [blame] | 1 | ####################### |
| 2 | # This file contains the description of configuration and general information about the |
| 3 | # "test_app" extension. |
| 4 | |
| 5 | # This extension provides a simple way to send a predefined message over the Diameter Network. |
| 6 | # It may be used to test the Routing or other base mechanisms from the Diameter network. |
| 7 | |
| 8 | # In order to enable this extension, the main freeDiameter configuration file |
| 9 | # must contain the following declaration: |
| 10 | # LoadExtension = "extensions/app_test.fdx" : "/path/to/app_test.conf" ; |
| 11 | # Note that the conffile may be omitted, in which case default parameters will be assumed. |
| 12 | ####################### |
| 13 | |
| 14 | |
| 15 | ####################### |
| 16 | # Configuration of the test message |
| 17 | |
| 18 | # This application is defined as a Vendor-Specific application. |
| 19 | # Since freeDiameter does not have a IANA-assigned Vendor ID, we let a configurable value here: |
| 20 | # vendor-id = 999999; |
| 21 | |
| 22 | # The application id. Same remark as previously. |
| 23 | # appli-id = 999999; |
| 24 | |
| 25 | # The command code for Test-Request and Test-Answer. The range 0xfffffe-ffffff (dec: 16777215) is reserved for experimental use. |
| 26 | # cmd-id = 16777214; |
| 27 | |
| 28 | # The AVP id for the test. |
| 29 | # avp-id = 345678; |
| 30 | |
| 31 | # Another AVP id for long payload test. default to value 0, meaning this is not used. |
| 32 | # long-avp-id = 0; |
| 33 | |
| 34 | # Define the payload length of the long-avp. Default 5000 bytes. |
| 35 | # long-avp-len = 5000; |
| 36 | |
| 37 | |
| 38 | ####################### |
| 39 | # Configuration of the extension behavior |
| 40 | |
| 41 | # The mode for the extension. |
| 42 | # - server: Answer incoming requests. The signal is ignored. |
| 43 | # - client: Send a request when the signal is received, and measure the time to receiving answer. |
| 44 | # - both: acts as client and server |
| 45 | # mode = both; |
| 46 | |
| 47 | # The behavior can be changed by specifying additional "benchmark;" keyword. |
| 48 | # When this keyword appears, it changes the behavior as follow: |
| 49 | # - server is silent on message reception, only the activity summary is displayed every 30 seconds |
| 50 | # - client attempts to send as many messages as possible during 10 seconds and counts them. |
| 51 | # The benchmark keyword can be followed optionally by two integers: |
| 52 | # duration is the time for the measurement, in seconds (default 10). |
| 53 | # concurrency is the number of messages that can be on the wire before waiting for an answer (default 100). |
| 54 | # benchmark [duration concurrency]; |
| 55 | |
| 56 | |
| 57 | ####################### |
| 58 | # Client-specific configuration |
| 59 | |
| 60 | # The Destination-Realm for the message |
| 61 | # (default is sending to same realm as local peer). |
| 62 | # dest-realm = "foreign.net"; |
| 63 | |
| 64 | # The Destination-Host for the message. |
| 65 | # (default is not providing this AVP). |
| 66 | # dest-host = "server.foreign.net"; |
| 67 | |
| 68 | # The User-Name for the message (may be useful for some routing tests). |
| 69 | # (default is not providing this AVP). |
| 70 | # user-name = "user@server.foreign.net"; |
| 71 | |
| 72 | # The signal that triggers sending the test message |
| 73 | # Note: Symbolic names are not recognized, you must use integers |
| 74 | # signal = 10; |