* Contact with <> format
* tests:
- add received Contact parameter as optional
- use server_id value
* soundsets.yml: unique name
Change-Id: Iad8bba5f1117e6645b07017d3e13d8d8bdd37808
* Contact with <> format
* tests:
- add received Contact parameter as optional
scenarios/invite_allowedcli_match/scenarios/invite_allowedcli_match0005_test.yml.tt2
Change-Id: I3cae99ceecf6cac5be68ec1a21a2d4361cb80dbd
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
* trusted: add domain to from_pattern
so it doesn't affect other scenarios
Change-Id: I6e81034f9eba393164c82293f6cbb9c4cd406496
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
* trusted: add domain to from_pattern
so it doesn't affect other scenarios
Change-Id: I070ed048309b5ec8d4d801e5084d9c3dd5c35971
This will allow to skip the whole provisioning if necessary
* use set_config.sh
* bin/check.sh: don't remove domain if SKIP is set
Change-Id: I0b2d165aced0ce7e57cfddef4c6308e8d7d27da6
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: Ida9b2e06e8de5e042967f08c39ec6f82a7865f60
* bin/sipp.sh: add option to set SIP SERVER_IP
* bin/check.sh: add option to set SIP SERVER_IP
* bin/scenario.pl: add server_ip info to scenario_ids.yml file
* bin/get_config.pl: add server_ip info to output
* bin/run_tests.sh: get server_ip from config and use it
Change-Id: If7a2284827df344eaecfdb5671146a9a79e81ea8
* we have more templates now
* make just one find call per scenario
* remove preds.json file left behind
Change-Id: Ic9983cd238b12134a97c94d2c7844c7391de7108
New kct scenario under scenarios/directory
featuring a whitelist sdp scenario with
PCMA,PCMU,GSM,telephone-event name codes in place.
Change-Id: Iebfe9c19abc6536b50bbdecbdc7a45cb09703c7a
* panel.log can not be presence use panel-fcgi.log as fallback
* define a list of files, easy to maintain
* use sems-b2b.log instead of sems-pbx.log
Change-Id: I6ee8c52224675f8aacd9ea99016868cfb02bc26b
* bin/provide_next_phone.pl was returning the last phone used
* added more info related to PHONE to the output
Change-Id: Ibb83879df5e0c945d2d9c0610633c17d5ce42dca
Create a few scenarios which would check work of lock mechanism for cases when:
- (patchset 1) A has a lock for outgoing (type 2); A calls B; Call is declined with 403;
- (patchset 2) B has a lock for outgoing (type 2); B has a CFU towards C;
A calls B, A gets forwarded to C due to CFU. But the call is locked with 403, since B has lock type 2.
- (patchset 4) B has a lock for outgoing (type 2); B has a CFNA towards C;
A calls B, 480 Temporarily Unavailable is sent back from B,
A gets forwarded to C. But the call is locked with 403, since B has lock type 2.
Change-Id: Ib532cbeefd36dac3dea6271ba7daa9dd4bf5c8a7
The main designation of this scenario is to check out, whether calling side
which uses tel scheme for From/To/Diversion/PAI headers, gets them fixed properly to SIP URI.
Particularity of this scenario is, that A side gets redirected with 302 Temporarily Moved.
Other than that we check out, whether Proxy doesn't admit usage of double Diversion headers present at the same message,
when a new INVITE has been generated by Proxy after receiving the 302.
Change-Id: I0bc82c8ea29915e9a2a3f13b90458b0b89dbc861
Previously there was no indication of what match was falling
* migrate to argparse
* format with black
* resolve some lint issues
* remove unused code
Change-Id: Iac06c29ef832250e322d64473837181d3d4effcb
Victor Seva
Alessio Garzi
Sipwise Jenkins Builder
donat zenichev
Marco Capetta