Started by an SCM change00443953951.0058525852571570e8cda818242b03b31b5daac6a99177857aafa570e8cda818242b03b31b5daac6a99177857aafarefs/remotes/origin/master570e8cda818242b03b31b5daac6a99177857aafa570e8cda818242b03b31b5daac6a99177857aafarefs/remotes/origin/master570e8cda818242b03b31b5daac6a99177857aafa570e8cda818242b03b31b5daac6a99177857aafarefs/remotes/origin/masterhttps://gerrit.osmocom.org/docker-playgroundfalse#571395255update-osmo-ci-on-slaves-dp #571571falsefalse5711561611SUCCESS1716982866773https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/571/build2-deb11build-ansiblettcn3-asterisk-ims-ue-test/asterisk/pjsip.conf115523644f4371fd892d36f0f9ac8cfb906abcd21716907609000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.deasterisk: pjsip.conf: Stop Asterisk doing unexpected REGISTER on IMS REGISTER should only be done when the IMS APN is ready, and baseband then interface asks it to register. Change-Id: I56249d4138c0a1f5824e089c14c095badc41dc95 2024-05-28 16:46:49 +0200115523644f4371fd892d36f0f9ac8cfb906abcd2asterisk: pjsip.conf: Stop Asterisk doing unexpected REGISTER on IMSeditttcn3-asterisk-ims-ue-test/asterisk/pjsip.confttcn3-asterisk-ims-ue-test/asterisk/pjsip.conf570e8cda818242b03b31b5daac6a99177857aafa1716907609000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.deasterisk: pjsip.conf: Enable USIM Auth over AMI interface Astersik_Tests already implement the related AMI procedures, hence configure Asterisk to use them. Depends: osmo-ttcn3-hacks.git ddc4c709e51b92dae4d10f0c71b062e4719da673 Change-Id: Iab2e9ad21ff6271ae51329608658ffe353173f38 2024-05-28 16:46:49 +0200570e8cda818242b03b31b5daac6a99177857aafaasterisk: pjsip.conf: Enable USIM Auth over AMI interfaceeditttcn3-asterisk-ims-ue-test/asterisk/pjsip.confgithttps://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrol