asterisk-master: Use pjproject from external git repo (details)
ttcn3-asterisk: Configure new IMS ConnHdlr (details)
asterisk: pjsip.conf: Mark templates accordingly (details)
asterisk: manager.conf: Give more permissions to AMI user (details)
ttcn3-asterisk: Update Asterisk_Tests.cfg to adapt to new AMI_Adapter (details)
Commit
fdef271404312ed08c4d0d95c328bbab51fc39fa
by Pau Espin Pedrol
asterisk-master: Use pjproject from external git repo
By default, asterisk.git build system will fetch pjproject tarball from https://raw.githubusercontent.com/asterisk/third-party/master/pjproject/$(PJPROJECT_VERSION), where PJPROJECT_VERSION is defined in asterisk/third-party/versions.mak: PJPROJECT_VERSION=2.14 On top of that, it applies some patches adapting build system, found in asterisk/third-party/pjproject/patches/.
The build system also allows to use an out-of-tree pjproject (eg from a git repo) by symlinking the directory to asterisk/third-party/pjprojec/source/.
This is all documented in asterisk/third-party/pjproject/README-hacking.md.
Since we want to develop on pjproject too, fetch our own pjproject.git repo, where we can push changes, and build asterisk using that repo.
Bear in mind that, when asterisk.git builds with out-of-tree pjproject, it wont apply pjproject patches under asterisk.git/third-party/pjproject/patches. Hence, I created an "asterisk/2.14" branch in our pjproject.git repo which points to tag "2.14" (the one used by asterisk 20.7.0, which we use), and has the 2 patches applied on top. Then, we have our own "sysmocom/2.14" branch on top of that "asterisk/2.14" branch, where we put our development. WIP development can also be done in whatever branch on top of "asterisk/2.14" branch.
Commit
2426a45db1639308a0ba7c1a109f5d20480dfcc5
by Pau Espin Pedrol
asterisk: pjsip.conf: Mark templates accordingly
Mark templates as such, in order to remove error messages during asterisk setup when trying to apply the templates (which lack fields such as "username", provided by config sections using the templates).