3 # <timeout>|<digits to sequence>|<CCR-Initial path file>[|CCR-Termination path file>]
5 # <timeout> is the first step to control the test cases execution. A value of 0 omits
6 # this first step (good to avoid huge load of timers during high performance testing).
8 # All the tests not fulfilled (those where the corresponding answers are not received)
9 # will be eternally keep 'in-progress' state. You could consider them failed after
10 # a specific time. A non-zero timeout step will ensure that this situation is updated
11 # as failed on expiration. Diameter application request timeouts also expire but are
12 # not processed here (not neccessary because reception conditions are enough to block
13 # the flow when something is wrong). Anyway, you could check ADML counters executing
14 # the command: ./operation show-oam
15 # The main problem with a zeroed first timeout step, is that cycle repeats are not
16 # possible except if you reset the pool (hard reset) when close to finish, something
17 # very dificult to monitor.
22 # CCR-Initial + CCR-Termination:
23 5000|7|CCR-I.xml|CCR-T.xml