Disable the scenario as a temporary workarround to allow
k-c-t to complete even if there are some issues in Asterisk service.
Revert this commit as soon as the issues in Asterisk are solved.
Change-Id: Ic10aafadd9d0ded5ecfc4a000e42d1dca7ec8703
Added tests:
* scenarios/invite_hm
* scenarios/invite_hm_callforward
* scenarios/invite_hm_peerout
Add a new file descriptors for the tests:
* pro.yml
If the file is present and the PROFILE is CE, then
the test isskipped because not in scope.
Change-Id: I8da41d764ef352d3caf592f31894e0c58399ed07
Additionally increased the timeout of the sipp simulations.
This is necessary to avoid failures of the tests in case kamailio
takes a bit more time to preocess the incoming SIP message.
Change-Id: I60856430f28b081d74e484b2346894dd13a38d11
In order to avoid packer ordering issue, some of the pause time
were increased in the following scenarios:
* scenarios/invite_concurrent_max
* scenarios/invite_concurrent_max_out
* scenarios/invite_concurrent_max_out_per_account
* scenarios/invite_concurrent_max_per_account
* scenarios/invite_voicebox
Change-Id: Idaa6e2c816967c2d1a90f74ab9d3e7ed8783ae63
* Original option '-c' in run_tests.sh has been modified
in '-C'
* Add new option '-c' in run_tests.sh to execute a query on MySQL
after each test to extract the generated CDRs.
* Add new option '-c' in get_results.sh to compare the extracted
CDRs with the referece provided in the scenario (cdr_test.yml.tt2).
* Modified option 'mediator.interval' from 10 to 1 during the test
execution in order to speedup the cdrs generation.
* Updated README file with the latest changes.
* Added basic cdr_test for all the scenarios.
Change-Id: Ifffd686003fa5e3a1ac4ba76c502011d7fdb21bb
A new scenario called invite_trusted_anonymous has been added to verify
the new improvement on the allow_trusted kamailio function that should
check the PAI header in case the From is anonymous.
Additionally:
* Introduced a new API interface to allow configuration of trusted
sources. To do that, just add a file named 'trusted.yml' in the
scenario folder.
* Improved the callforward API interface to allow more sophisticated
callforward configuration. Now it is possible to configure all the
types of CF as well sources, bnumbers and timeset.
* Removed from the output the noisy parenthesis '{}' result of
ngcp-kamctl commands
Change-Id: I5ed54d063bcda2d5df7004b9cad671644e021def
- the hop-by-hop ACK is now generated by the LB and not relayed so it does not
have any P-NGCP-Src-* headers and Contact
- remove pause before ACK that was causing retransmission
- REFER method used to be filtered from Allow on messages coming from proxy or
sbc but not those coming from UA. it makes sense to do it everywhere I think
- in invite_retrans the retransmission is now absorbed on lb so there is one
message less in proxy logs and other message numbers are shifted forward by one
Change-Id: If6e05368fe72df7636dff43d18572eff821f16c4
The errors is not due to re-transmission, but packet ordering.
It seems that, in high loaded systems, kamailio proxy takes too
much time to process some packages causing an unexpected order.
Increasing the wait time from 500ms to 600ms give 100ms more to the
proxy to process the packet and send it out in the expected order.
Change-Id: Idccd6c7b95c428cbee519bb6cf779c6a8dfc3e82
* Added start/return ROUTE_EXIT and start/return ROUTE_ENTRY
* Updated caller/callee xavp content validation
* Updated ngcp-kamctl calls to the new rpc format
Change-Id: I166a638a7a1f0ef5102db666180eb83e8b47d6e4
These functions do internal error checks and will die on their own.
They return undef whenever the YAML file is empty, so we should not
abort on those.
Change-Id: Ifd61b98d3a95ee9b15ff240fbd5db0c1029c98e3