tests/channels/pjsip/sdp_mandatory_lines: Added test to check the validity of SDP s= and o= lines#125
tests/channels/pjsip/sdp_mandatory_lines: Added test to check the validity of SDP s= and o= lines#125AlexisHadj wants to merge 1 commit intoasterisk:masterfrom
Conversation
github-actions
bot
added
pr-submit-testing-in-progress
pr-submit-tests-failed
and removed
pr-submit-testing-in-progress
labels
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
Workflow PRCheck failed |
AlexisHadj
force-pushed
the
testRFC8866
branch
2 times, most recently
from
f244934 to
efa28b1
Compare
github-actions
bot
added
pr-submit-testing-in-progress
pr-submit-tests-passed
and removed
pr-submit-tests-failed
pr-submit-testing-in-progress
labels
|
Workflow PRCheck completed successfully |
AlexisHadj
force-pushed
the
testRFC8866
branch
from
efa28b1 to
964d28a
Compare
github-actions
bot
added
pr-submit-testing-in-progress
and removed
pr-submit-tests-passed
labels
|
cherry-pick-to: 20 |
github-actions
bot
added
pr-submit-tests-passed
and removed
pr-submit-testing-in-progress
labels
github-actions
bot
dismissed
their stale review
Pull Request Checklist Complete
|
Workflow PRCheck completed successfully |
…idity of SDP s= and o= lines This new test verifies that the SDP Session Name (s=) and Origin (o=) lines are present and contain valid data, as required by RFC 8866. 1-Added SIPp scenario to initiate a call with validation on the SDP session (s=) and origin (o) lines. 2-Added Asterisk configuration (pjsip.conf, extensions.conf) to support the test. 3-Registered the new test in the pjsip test suite.
AlexisHadj
force-pushed
the
testRFC8866
branch
from
964d28a to
18ddb17
Compare
github-actions
bot
added
pr-submit-testing-in-progress
pr-submit-tests-passed
and removed
pr-submit-tests-passed
pr-submit-testing-in-progress
labels
|
Looking at the failing task above it seems to me that this statement: asterisk-test-pr: 1754 is causing the grief. 1754 is the associated PR that this test scenario is meant to be testing. Any insight is appreciated |
Don't worry about it. It was an issue with a workflow issue I made yesterday morning. |
github-actions
bot
added
pr-submit-tests-passed
and removed
pr-submit-tests-passed
recheckpr
pr-submit-testing-in-progress
labels
|
Workflow PRCheck completed successfully |
2 participants
This new test verifies that the SDP Session Name (s=) and
Origin (o=) lines are present and contain valid data, as required by RFC 8866.
1-Added SIPp scenario to initiate a call with
validation on the SDP session (s=) and origin (o) lines.
2-Added Asterisk configuration (pjsip.conf, extensions.conf) to
support the test.
3-Registered the new test in the pjsip test suite.