ASTERISK-28096: pjsip: PJPROJECT 2.8 causes test failure

[Home]

Summary: ASTERISK-28096: pjsip: PJPROJECT 2.8 causes test failure

Reporter: Corey Farrell (coreyfarrell) Labels: pjsip

Date Opened: 2018-10-09 13:19:59 Date Closed: 2019-01-22 15:06:55.000-0600

Priority: Major Regression? Yes

Status: Closed/Complete Components: pjproject/pjsip

Versions: 13.24.0 GIT 15.7.0 16.1.0 Frequency of
Occurrence

Related
Issues:
causes ASTERISK-28085 testsuite: Figure out why chan_sip blind transfer tests are failing.

is caused by ASTERISK-28059 PJSIP: Update bundled PJPROJECT to version 2.8

Environment: Attachments:

Description: {{tests/apps/chanspy/chanspy_barge}} has been locking up lately. I've determined this is caused by the patches \[1\] which upgraded to pjproject-2.8. Reverting the two patches allows the chanspy_barge test to pass (it takes 11 seconds). Tested against 13.

\[1\]: https://gerrit.asterisk.org/#/q/status:merged+topic:ASTERISK-28059

Comments: By: Asterisk Team (asteriskteam) 2018-10-09 13:20:18.266-0500

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].
By: Corey Farrell (coreyfarrell) 2018-10-10 05:56:32.721-0500

I'm not confident there is actually any issue with Asterisk. It's possible this is only an issue for pjsua in which case this could be purely a testing issue.
By: Joshua C. Colp (jcolp) 2018-10-10 06:03:14.088-0500

This would not surprise me.
By: Kevin Harwell (kharwell) 2018-10-26 17:41:53.798-0500

A patch that went out in 2.8 was made to pjsua that made it so the TCP transport is now defaulted if both UDP and TCP are enabled. This caused test failures in those testsuite tests that used pjsua via a subprocess as endpoints as they were expected to use UDP. Passing '--no-tcp' as a command line should suffice to fix these tests.

However, in the chanspy_barge test I ended up rewriting it to remove the pjsua dependency altogether as the test didn't really need to use pjsua (or any external endpoint) at all (could just use local channels).