Started by an SCM change00554344341.00921092106075f8e407ca7ee56cbed77043d4c4f26f74fa8d8b05f8e407ca7ee56cbed77043d4c4f26f74fa8d8b0refs/remotes/origin/master5f8e407ca7ee56cbed77043d4c4f26f74fa8d8b05f8e407ca7ee56cbed77043d4c4f26f74fa8d8b0refs/remotes/origin/master5f8e407ca7ee56cbed77043d4c4f26f74fa8d8b05f8e407ca7ee56cbed77043d4c4f26f74fa8d8b0refs/remotes/origin/masterhttps://gerrit.osmocom.org/docker-playgroundfalse#607434255update-osmo-ci-on-slaves-dp #607607falsefalse6071611076SUCCESS1721297469840https://jenkins.osmocom.org/jenkins/view/osmo-gsm-tester/job/update-osmo-ci-on-slaves-dp/607/build2-deb11build-ansiblettcn3-asterisk-ims-ue-test/asterisk/extensions.conf5f8e407ca7ee56cbed77043d4c4f26f74fa8d8b01721227704000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.deasterisk: extensions.conf: Allow extra MO call from SIP UA which HOLDed previous call We need to keep track of the SIP UA using the IMS endpoint, so that when the IMS call is set on HOLD we can identidy that the same SIP UA can still initiate new calls on the IMS endpoint. Related: SYS#7003 Change-Id: Idad9e613669466f3aac8b1c7b43f8d9b6e0494e6 2024-07-17 16:48:24 +02005f8e407ca7ee56cbed77043d4c4f26f74fa8d8b0asterisk: extensions.conf: Allow extra MO call from SIP UA which HOLDededitttcn3-asterisk-ims-ue-test/asterisk/extensions.confgithttps://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrol