Skip to content

Changes

Summary

  1. asterisk-master: Use pjproject from external git repo (details)
  2. ttcn3-asterisk: Configure new IMS ConnHdlr (details)
  3. asterisk: pjsip.conf: Mark templates accordingly (details)
  4. asterisk: manager.conf: Give more permissions to AMI user (details)
  5. 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.

Change-Id: I73f3323db1b6897fc43215578b0a011fdb6909c5
The file was modified make/Makefile
The file was modified asterisk-master/Dockerfile
Commit eb47b4961b3ff706822f4c0aa4a47677285e13db by Pau Espin Pedrol
ttcn3-asterisk: Configure new IMS ConnHdlr

Configure new component added to Asterisk_Tests to emulate an IMS Core.

Depends: osmo-ttcn3-hacks.git Change-Id Ibbbadd54b7facf4ef7384499704e742f482a1252
Change-Id: I0ee6cb8955fc4f7dec3db97c768430905374f115
The file was modified ttcn3-asterisk-ims-ue-test/Asterisk_Tests.cfg
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).

Reference: https://docs.asterisk.org/Fundamentals/Asterisk-Configuration/Asterisk-Configuration-Files/Templates/Template-Syntax/

Change-Id: Ia132c2e90cf6ee44145ca2e2555cf2dc6c1cfd51
The file was modified ttcn3-asterisk-ims-ue-test/asterisk/pjsip.conf
Commit cfe6d7e91938c9691a2d2335cc5b3d3bc0330ff0 by Pau Espin Pedrol
asterisk: manager.conf: Give more permissions to AMI user

These are required to use eg. PJSIPRegister command, otherwise Asterisk
answers with "Permission Denied".

It also seems to help in getting more events from Asterisk.

Change-Id: Ia77a9d88758f648a5539dbc7511b75c20fe7dd6b
The file was modified ttcn3-asterisk-ims-ue-test/asterisk/manager.conf
Commit 2862c344f08523c116e018df3183fef0259cb5ee by Pau Espin Pedrol
ttcn3-asterisk: Update Asterisk_Tests.cfg to adapt to new AMI_Adapter implementation

Change-Id: I8d89e1694347f93e84c692d23b375062e003878e
The file was modified ttcn3-asterisk-ims-ue-test/Asterisk_Tests.cfg