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/wip/sip-invite-cancel has been created at 9b6b73207d503524057d008875835b627cd70b6c (commit) - Log ----------------------------------------------------------------- http://cgit.osmocom.org/osmo-sip-connector/commit/?id=9b6b73207d503524057d0… commit 9b6b73207d503524057d008875835b627cd70b6c Author: Holger Hans Peter Freyther &lt;holger(a)moiji-mobile.com&gt; Date: Thu Mar 24 22:45:03 2016 +0100 WIP.. http://cgit.osmocom.org/osmo-sip-connector/commit/?id=47e5dc5de9c569b8c22c7… commit 47e5dc5de9c569b8c22c7af90bc8a07d25c33059 Author: Holger Hans Peter Freyther &lt;holger(a)moiji-mobile.com&gt; Date: Thu Mar 24 21:37:10 2016 +0100 mncc: Refactor and reduce some code clones for sanity checks Not every message might have the size of gsm_mncc and the size check is done inside each routine. Routines that relate to calls now share the code to check the size and the look-up to find the leg. http://cgit.osmocom.org/osmo-sip-connector/commit/?id=b04b02004dceebf9ef5d8… commit b04b02004dceebf9ef5d80434a51a7ed8ea42294 Author: Holger Hans Peter Freyther &lt;holger(a)moiji-mobile.com&gt; Date: Thu Mar 24 21:02:36 2016 +0100 mncc: Prepare alerting and and connecting the call What is not done is to actually set-up rtp that it can flow to the now confirmed remote. http://cgit.osmocom.org/osmo-sip-connector/commit/?id=b734b15a81825c54d168f… commit b734b15a81825c54d168fd2cf796854ef3a4ce19 Author: Holger Hans Peter Freyther &lt;holger(a)moiji-mobile.com&gt; Date: Thu Mar 24 21:01:18 2016 +0100 mncc: Handle disconnect and release the call Send a release request and release the leg on conformation http://cgit.osmocom.org/osmo-sip-connector/commit/?id=ec8ba33b23ca098ed9d88… commit ec8ba33b23ca098ed9d88613615bd044b1526321 Author: Holger Hans Peter Freyther &lt;holger(a)moiji-mobile.com&gt; Date: Thu Mar 24 18:48:45 2016 +0100 mncc: In case of an unexpected REL.IND inform the other leg about it I had modified my code to do nothing after having sent the PROCEEDING message. First the MS will issue a DISCONNECT.IND (which I ignored) and then there will be REL.IND. Let's inform the other leg about this event and let's assume the call will then be terminated. http://cgit.osmocom.org/osmo-sip-connector/commit/?id=a2ca56b0f25b75bc6b5e8… commit a2ca56b0f25b75bc6b5e8b0eda64bca09d0d4f87 Author: Holger Hans Peter Freyther &lt;holger(a)moiji-mobile.com&gt; Date: Thu Mar 24 18:47:25 2016 +0100 call: Change to past tense and move code after the free Reading the "releasing" log output sounded like one more message had been sent and this code is waiting for something. Take a copy of the call id and then print that the call has been released. http://cgit.osmocom.org/osmo-sip-connector/commit/?id=a3ebfa26c31c0f81a60e6… commit a3ebfa26c31c0f81a60e6764cb7d5cd66b329c49 Author: Holger Hans Peter Freyther &lt;holger(a)moiji-mobile.com&gt; Date: Thu Mar 24 18:33:49 2016 +0100 mncc: Log commands in hex to find the name more easily in mncc_protocol.h In the long run we should print these by name and not by the number but as the table is in OpenBSC and I did not want to copy it we will have to cope with the numbers a little longer. http://cgit.osmocom.org/osmo-sip-connector/commit/?id=282da0d5d153abf8d5115… commit 282da0d5d153abf8d51159aefd2c7c55fa7ee103 Author: Holger Hans Peter Freyther &lt;holger(a)moiji-mobile.com&gt; Date: Thu Mar 24 18:26:24 2016 +0100 call/mncc: Set proceeding and deal with release based on this state Let's inform the MS that we have collected everything to move forward with the call. A new way to release the call is required in this state. http://cgit.osmocom.org/osmo-sip-connector/commit/?id=81b52da75458508be2d71… commit 81b52da75458508be2d71c277005006c50322b4d Author: Holger Hans Peter Freyther &lt;holger(a)moiji-mobile.com&gt; Date: Thu Mar 24 18:24:47 2016 +0100 call: Re-order includes from local to osmocom to system Let's follow the self first, local next, osmocom, system order of include files. http://cgit.osmocom.org/osmo-sip-connector/commit/?id=c5f20ddf3b9f18d24ce38… commit c5f20ddf3b9f18d24ce38915b0593b93586b5620 Author: Holger Hans Peter Freyther &lt;holger(a)moiji-mobile.com&gt; Date: Thu Mar 24 18:24:02 2016 +0100 app: Release the call by releasing the initial request This will then go through the release procedure of the relevant call instead of letting it timeout on the initial leg. http://cgit.osmocom.org/osmo-sip-connector/commit/?id=4319330c411e059918d45… commit 4319330c411e059918d457593d76253757060ee4 Author: Holger Hans Peter Freyther &lt;holger(a)moiji-mobile.com&gt; Date: Thu Mar 24 17:35:42 2016 +0100 mncc: Extract the RTP port information before continuing These need to be used by the SIP leg to move forward. ----------------------------------------------------------------------- hooks/post-receive -- MNCC <-> SIP bridge