We need to actualize scenarios when checking usage fmtp description in SDP bodies,
due to late changes in the RTPEngine behavior
(when processing offer/answer with/without fmtp for the 101th event).
Change-Id: I47f97cba69345fb0fdce777831e7f23cc37a79b3
Remove route ROUTE_CHECK_TIMER_SUPP_REQ because not
used anymore in the system
Remove check if variable $x_hdr(Supported) because not
used anymore in the config and thus not printed by cfgt
module in log files
Change-Id: I9335ed36fd04d053c188062455def9706d97e2d7
We need to update a list of k-c-t scenarios because of
the last updates in a way how we process 'timer' extension in
the Supported / Require headers.
Now additionally in most of the scenarios we enter:
- route[ROUTE_CHECK_TIMER_SUPP_REQ]
- route[ROUTE_REMOVE_TIMER_SUPP_REQ]
Change-Id: Icc6f70957c932cadd8d9c81896038e6fd9b4374f
* 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
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: Ib001caccb0fd2c3d6c3295d4dc9333f26c518642
Victor Seva
Alessio Garzi
dzenichev
Fabricio Santolin da Silva
Marco Capetta