Check fritz prefix removal behaviour with emergency mappings.
Change-Id: I5de2337ce8ba7c193032b81c129b28c5fefeabf8
(cherry picked from commit ef4b381058a83f7f553e42518c52bef2bc5f799e)
New scenario scenarios/invite_fritz_prefix_removal
- Call 1: A new call is generated towards sip:+431112@invite-fritz-prefix-removal.scenarios.test
Due to fritz prefix removal feature it must be changed into 112@invite-fritz-prefix-removal.scenarios.test
- Call 2: A new call is generated towards sip:+4312000@invite-fritz-prefix-removal.scenarios.test (voicebox)
Due to fritz prefix removal feature it must be changed into 2000@invite-fritz-prefix-removal.scenarios.test
- Call 3: A new call is generated towards sip:0999112@invite-fritz-prefix-removal.scenarios.test
Even if 112 is part of the "special numbers" list in config.yml, the prefix removal cannot happen because 0999
is not in the prefixes list.
Change-Id: I8ca655faf31b9d07f8b103cb3c8cfd05d7bfb065
(cherry picked from commit 7c85a4d806fa4b6af6f71cf28322036baa3f566f)
Since we are mounting in read-only mode the code, we are getting
warnings from pytest executions not able to generate .pytest_cache
directory.
Just define CACHE_DIR in a volumen that is mounted as read-write
Change-Id: I9949877f4d86873f47778ae9a7cddffb45f3932c
SIPP option -trace_logs is now implemented at kct level.
At default it is deactivated and it can be used with -L [caller|responders|all|none] switch.
This let you use <log> directive inside actions for debugging purposes.
Example of logging:
<recv response="100" rtd="1" optional="true">
<action>
<ereg regexp=".*" search_in="hdr" header="Call-ID:" assign_to="1" />
<log message="Got 100 Trying with Call-ID header [$1]"/>
</action>
</recv>
Now , when running with -L switch:
SCENARIOS=invite ./run_tests.sh -C -r -c -L caller
you get file /usr/share/kamailio-config-tests/log/scenarios/invite/sipp_scenario00.log
with the following content:
"
Got 100 Trying with Call-ID header NGCP%invite%///1-140463@10.20.29.2
"
If -L switch is not passed all behaves exactly like before.
Change-Id: I96c0721a2f1db524a2d68b018b2744a84b32e281
Parameter fast_ack=no could be missing depending if we are running CE or PRO.
The regexp has been changed in order to accept both version with fast_ack and without.
Change-Id: I92b3cd043f301c145d820ad113eadf3471ba97e0
This reverts commit 44395a5206.
Reason for revert: too many typos... rebuilding commit from scratch
Change-Id: I68f02faf4ba1d5e43786f797ab967192d2a97ce5
This scenario tests the following situation with call counters:
A calls B, B takes the call
A holds (B is held)
A calls C, C takes the call
A xfers -> B and C are in communication
Change-Id: I2d5401c0bf128d51d2ae656a3c0948a3e24a8beb
I left trace of my local ip address inside invite_record_call scenario..
This commit just removes these lines.
Change-Id: Ib818a536197b07d620b613eb98d689ce52e26b4a
This commit adds 3 more calls to the invite_record_call
scenario testing the behaviour of calls which are not responded
with 200 OK.
Change-Id: If5b832310c610bdafc86a0f850cb8ce65ef532c7
Avp "s:" + branch_id + "callee_rU" must store the value of the rU after
the branching.
Adding test to check this behaviour inside scenario invite_alias_devid.
Change-Id: I4328a71b3f22ea186348bb9317af516ea980a3bb
* provide_scenario.sh: continue even if the domain is not there
when deleting
It seems that API behavior has changed
Change-Id: I6373eba6903491b39623329e29128de059f0b569
* FLOW_VARS or FLOW error, so possible
changes in kamailio.cfg are detected
* produce the _test.diff and .sip files
using the proper json
Change-Id: I39a003b3542283b4080f1c8e5004e826ae98f16e
Guillem Jover
Alessio Garzi
Victor Seva
Sipwise Jenkins Builder
Daniel Grotti
Mykola Malkov
Donat Zenichev