Segfaulting when linking channel

[tsolace]

I don't know what linking is, but when I right-click any channel as admin and click "link", mumsi segfaults.

[slomkowski]

By linking you mean linking channels with each other? Is there any meaningful output? If no, please run Mumsi in debug mode.

[tsolace]

When my channel "Gateway" is linked (by right-clicking Gateway and clicking Link), this is what it looks like when starting mumsi and attempting to join:

2015-12-13 16:57:30,265 [INFO] Pjsua: 16:57:30.265    pjsua_acc.c  Adding account: id=sip:11012021909@proxy.ideasip.com
2015-12-13 16:57:30,265 [INFO] Pjsua: 16:57:30.265    pjsua_acc.c  .Account sip:11012021909@proxy.ideasip.com added with id 0
2015-12-13 16:57:30,265 [INFO] Pjsua: 16:57:30.265    pjsua_acc.c  .Acc 0: setting registration..
2015-12-13 16:57:30,305 [INFO] Pjsua: 16:57:30.305   pjsua_core.c  ...TX 570 bytes Request msg REGISTER/cseq=36950 (tdta0x2418d00) to UDP 208.97.25.11:5060:
REGISTER sip:proxy.ideasip.com SIP/2.0
Via: SIP/2.0/UDP 158.69.161.22:5060;rport;branch=z9hG4bKPjc7226387-8358-4d6d-a6b2-0e64ae05667d
Max-Forwards: 70
From: <sip:11012021909@proxy.ideasip.com>;tag=de0e8531-ff20-40e2-8deb-7786924f0f29
To: <sip:11012021909@proxy.ideasip.com>
Call-ID: d11f75ad-562a-456e-aae8-1860a9c73715
CSeq: 36950 REGISTER
User-Agent: Mumsi Mumble-SIP gateway
Contact: <sip:11012021909@158.69.161.22:5060;ob>
Expires: 300
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Content-Length:  0

--end msg--
2015-12-13 16:57:30,306 [INFO] Pjsua: 16:57:30.306    pjsua_acc.c  ..Acc 0: Registration sent
2015-12-13 16:57:30,306 [INFO] : Application started.
2015-12-13 16:57:30,393 [INFO] SipCommunicator: Register: code=200
2015-12-13 16:57:30,512 [INFO] mumlib.Transport: Sending version information.
2015-12-13 16:57:30,513 [DEBUG] mumlib.Transport: Sending 33 bytes of data.
2015-12-13 16:57:30,513 [INFO] mumlib.Transport: Sending authententication.
2015-12-13 16:57:30,513 [DEBUG] mumlib.Transport: Sending 28 bytes of data.
2015-12-13 16:57:30,513 [DEBUG] mumlib.Transport: Received 55 B of data (49 B payload, type 0).
2015-12-13 16:57:30,513 [DEBUG] mumlib.Transport: Calling external ProcessControlMessageFunction.
2015-12-13 16:57:30,513 [DEBUG] mumlib.BasicCallback: version: v1.2.8. 1.2.8-2/X11/Debian GNU/Linux 8.2 (jessie)

2015-12-13 16:57:31,021 [DEBUG] mumlib.Transport: Received 60 B of data (54 B payload, type 15).
2015-12-13 16:57:31,021 [INFO] mumlib.Transport: Set up cryptography for UDP transport. Sending UDP ping.
2015-12-13 16:57:31,021 [DEBUG] mumlib.Transport: Sending UDP ping.
2015-12-13 16:57:31,021 [DEBUG] mumlib.Transport: Sending 14 B of data UDP asynchronously.
2015-12-13 16:57:31,021 [DEBUG] mumlib.Transport: Sent 14 B via UDP.
2015-12-13 16:57:31,021 [DEBUG] mumlib.Transport: Received 32 B of data (26 B payload, type 21).
2015-12-13 16:57:31,021 [DEBUG] mumlib.Transport: Calling external ProcessControlMessageFunction.
2015-12-13 16:57:31,021 [DEBUG] mumlib.BasicCallback: codecVersion.
2015-12-13 16:57:31,021 [DEBUG] mumlib.Transport: Received 16 B of data (10 B payload, type 7).
2015-12-13 16:57:31,021 [DEBUG] mumlib.Transport: Calling external ProcessControlMessageFunction.
2015-12-13 16:57:31,021 [DEBUG] MumbleChannelJoiner: Channel Root available (0)
2015-12-13 16:57:31,021 [DEBUG] mumlib.Transport: Received 92 B of data (86 B payload, type 7).
2015-12-13 16:57:31,021 [DEBUG] mumlib.Transport: Calling external ProcessControlMessageFunction.
2015-12-13 16:57:31,021 [DEBUG] MumbleChannelJoiner: Channel Gateway available (1)
2015-12-13 16:57:31,022 [DEBUG] mumlib.Transport: Received 10 B of data (4 B payload, type 7).
2015-12-13 16:57:31,022 [DEBUG] mumlib.Transport: Calling external ProcessControlMessageFunction.
Segmentation fault

The issue doesn't occur when the channel is not linked.

[slomkowski]

The issue is fixed with commit slomkowski/mumlib@a4f511d.