We need to update a list of scenarios for k-c-t in the master repo, in order to let CE-trunk nightly runs (by Jenkins) be working again.
For now Jenkins marks CE-trunk build as failed, reason - not actual k-c-t scenarios.
Change-Id: I1a5152149b3bb066574655c74fff162a82ebc20b
Even if the video support is disabed by the callee, a codec has to be
provided in the reply. Addin coded 34 equel to the one received in the
initial INVITE.
The missing codec was causing SEMS to add an empty line after the
sdp m= line causing rtpengine to return:
error: Failed to parse SDP
Change-Id: I80227c9dd9a34a21b278d9b069d5af88eb504655
* cseq: use \d+ since sems can use random and CE/PRO are different
* support alias_numbers
* numbers on display names
Change-Id: I7f94718cd9363a20124baae51347763dbd3fb234
* Makefile: add missing test_generate_test rule
* remove yaml.dump and build directly the simple YAML
output ourselfs. It was generating strange indentation
even with indent=None with using [% %] for some cases
Change-Id: Iacf927cf21b5d127c625168a049d6a1bd9606fc3
* when reading yaml, that value became hex
* lint yaml using visual code plugin
* TODO: introduce pre-commit and create rule for avoid this
issue in the future
Change-Id: I866024ba51b6bbec7449275bb6ea56e2f7e6bb4d
> root@09127d41b4c6:/code# ./bin/check_sip.py
> Traceback (most recent call last):
> File "/code/./bin/check_sip.py", line 259, in <module>
> args = parser.parse_args()
> File "/usr/lib/python3.9/argparse.py", line 1830, in parse_args
> args, argv = self.parse_known_args(args, namespace)
> File "/usr/lib/python3.9/argparse.py", line 1863, in parse_known_args
> namespace, args = self._parse_known_args(args, namespace)
> File "/usr/lib/python3.9/argparse.py", line 2100, in _parse_known_args
> self.error(_('the following arguments are required: %s') %
> File "/usr/lib/python3.9/argparse.py", line 2585, in error
> self.print_usage(_sys.stderr)
> File "/usr/lib/python3.9/argparse.py", line 2555, in print_usage
> self._print_message(self.format_usage(), file)
> File "/usr/lib/python3.9/argparse.py", line 2521, in format_usage
> return formatter.format_help()
> File "/usr/lib/python3.9/argparse.py", line 295, in format_help
> help = self._root_section.format_help()
> File "/usr/lib/python3.9/argparse.py", line 226, in format_help
> item_help = join([func(*args) for func, args in self.items])
> File "/usr/lib/python3.9/argparse.py", line 226, in <listcomp>
> item_help = join([func(*args) for func, args in self.items])
> File "/usr/lib/python3.9/argparse.py", line 333, in _format_usage
> action_usage = format(optionals + positionals, groups)
> File "/usr/lib/python3.9/argparse.py", line 408, in _format_actions_usage
> start = actions.index(group._group_actions[0])
> IndexError: list index out of range
Change-Id: I8cc8d73a785fb164ff7b9568076eab10bd53f77d
* sipp_scenario00.xml => sipp_scenario00.msg
sipp_scenario_responder00.xml => sipp_scenario_responder00.msg
so sipp_scenario00_test.yml.tt2 and sipp_scenario_reponder00_test.yml.tt2
makes more sense
Change-Id: Iab9db5122774dbc32101195e639ab6fef9b23236
We are adding a new approach/tool used to check out SIP messages
received, and unlike the existing way of doing that (using what has come/gone in front of the Proxy),
the usage of sipp logs will be introduced.
The idea is that we are looking for received SIP messages at both
the originator(s) and recipient(s) side, and then using what we've gotten,
run checks based on _test.yml.tt2 templates prepared in advance for each scenario, example:
* sip_messages00_test.yml.tt2
* sip_messages_responder00_test.yml.tt2
- add missing options to help command
- bin/check.sh: use T option to select what to do with checks
- get_results.sh: remove deprecated -P -T options
Change-Id: I2d0084fa59694ffd009736205a092a35f6864669
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: Ic9333ad40bee717c4681f7c4e01f1a2292981dfa
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: Ia9c2d32f2d4d5e7918eb415df5ef40e11a9f2c7f
> {"message":"Customer already has a pbx pilot subscriber.","code":"422"}
To avoid this error on provisioning all at once
Change-Id: Iaa0f519ae62e0b67c14bcd587b1e35c758afae3c
SCA notifications for multi-device case are now
working properly so we can reactivete those scenarios
Change-Id: Ic32b430c84dfb0036d63e33a5e651ef7e66939a2
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: I038473a950350d8a3a2953fefbab02d310554558
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: Ieaaf6290acbabff0a420d26534c9fc5c76eb3178
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: Ia9628182aa19bcfcce8976a097d4f17e852b5ec3
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: If5337d34d703c4f946c34a74dac1b5692ef02e5d
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: I0bfa4f1825b95b6d4af8bb3c5fae511a8beaaf1a
> {"message":"Customer already has a pbx pilot subscriber.","code":"422"}
To avoid this error on provisioning all at once
Change-Id: Icc36123a64e4f657d154a08eadc50e8f90e1f459
It will be called by jenkins to figure out what are the failed scenarios
so next run will run just those
Change-Id: I7e7dcbe0e52a13606e1a03a4d28e35a9c404e931
> 15:09:50 /code/./tests/test_yaml_format.py:66: YAMLLoadWarning: calling
> yaml.load() without Loader=... is deprecated, as the default Loader is
> unsafe. Please read https://msg.pyyaml.org/load for full details.
Change-Id: I56c6b11bee0ed2c42b61d4a20ac97327e0fb725d
Regenerate from scratch all pbx scenarios.
This is needed because the pbx removal changed drastically
the flow and every pbx scenario is failing.
Temporarly moved scenarios
* incoming_shared_line
* invite_shared_line
to disabled folder in order to don't block the nightly tests.
Change-Id: I236bfc64b86e88809a55b04a9a92ab2e702f915d
* tests will be using sip_ext interface bt default
* -s option to allow skip detection and use config.yml values
Change-Id: I6135c9dc7c08033085edb6cdb11446f1e2524aaf
* helper to set or detect IP to use in the tests
* uses IP of the first interface with sip_ext type detected
* bin/network_config.pl: set dummy1 too
* config.yml:
subscribers will use dummy1: 10.20.29.2/30
peers will use dummy0: 172.30.1.2/30
* pyproject.toml: black settings
Change-Id: Ibe59cde090b22e7631b87ffdecc706f3de391078
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: I3d4799ce63859318fa59ac6326dd48bc33a44e24
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: I5f72525f3b341d2d21fbf2cf9e12af01e1c9eda7
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: I9fd0806a713551d76eea6738cbd03b34be36f593
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: Ifbf3a88f92b2d6183c792ee7acdf57ef927cb9cd
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: I1c89268f60444e5ef400705f16cb0b457ebb5cf3
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: Ib39f68152d4da57d6104c2eab54d5232bc1f878e
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: I521e6f68a206638cc28731d0d7bf726675c6a356
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: If803617720a36c19c82084d0d1b58d5ec23c7005
Donat Zenichev
Marco Capetta
Victor Seva
Alessio Garzi