This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "MNCC <-> SIP bridge". The branch, zecke/mt-mncc-call has been updated discards 6288a7172809dc62debada14c3274aa1449f2105 (commit) via b8e802851dd586b3e08799886cf4b144463b970f (commit) via a4970327f2e050f697dd4e75fa1931902aa6c1de (commit) via 00a43e20ab4e16ac3822d204d98f7d8e2f11b7c2 (commit) via 916348b7dcbd3f5fb4b672c3e18f6dd092cea146 (commit) This update added new revisions after undoing existing revisions. That is to say, the old revision is not a strict subset of the new revision. This situation occurs when you --force push a change and generate a repository containing something like this: * -- * -- B -- O -- O -- O (6288a7172809dc62debada14c3274aa1449f2105) \ N -- N -- N (b8e802851dd586b3e08799886cf4b144463b970f) When this happens we assume that you've already had alert emails for all of the O revisions, and so we here report only the revisions in the N branch from the common base, B. Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://cgit.osmocom.org/osmo-sip-connector/commit/?id=b8e802851dd586b3e0879… commit b8e802851dd586b3e08799886cf4b144463b970f Author: Holger Hans Peter Freyther &lt;holger(a)moiji-mobile.com&gt; Date: Sun Mar 27 16:49:23 2016 +0200 mncc: Handle REJ_IND from the NITB In case a call can not be connected we will receive a REJ.IND. Inform the other leg and release the call. http://cgit.osmocom.org/osmo-sip-connector/commit/?id=a4970327f2e050f697dd4… commit a4970327f2e050f697dd4e75fa1931902aa6c1de Author: Holger Hans Peter Freyther &lt;holger(a)moiji-mobile.com&gt; Date: Sun Mar 27 16:45:35 2016 +0200 mncc: Stop timer when starting the release process http://cgit.osmocom.org/osmo-sip-connector/commit/?id=00a43e20ab4e16ac3822d… commit 00a43e20ab4e16ac3822d204d98f7d8e2f11b7c2 Author: Holger Hans Peter Freyther &lt;holger(a)moiji-mobile.com&gt; Date: Sun Mar 27 16:43:45 2016 +0200 mncc: On timeout release the other leg as well In case we don't receive the response we had expected let us take down the other part of the call as well. http://cgit.osmocom.org/osmo-sip-connector/commit/?id=916348b7dcbd3f5fb4b67… commit 916348b7dcbd3f5fb4b672c3e18f6dd092cea146 Author: Holger Hans Peter Freyther &lt;holger(a)moiji-mobile.com&gt; Date: Sun Mar 27 17:02:39 2016 +0200 mncc: Begin to implement MT call handling for SIP->MNCC Initiate the setup request that should result in the call getting all the way to the connected state at some point in time. The device I test with sadly rejects the call too soon. ----------------------------------------------------------------------- Summary of changes: doc/examples/osmo-sip-connector.cfg | 7 ++----- src/mncc.c | 31 ++++++++++++++++++++++++++++++- 2 files changed, 32 insertions(+), 6 deletions(-) hooks/post-receive -- MNCC <-> SIP bridge