PJSIP died after module upgrade - Bad magic number

General Help
1

Hi,

I had been using FreePBX 12 for about two months without problem, but yesterday I updated the modules (like I have always done) and since, PJSIP stopped working, Not only on trunks but also for devices. Bad magic number, Object is likely destroyed.

Any idea what might have gone wrong? Anyone experiencing anything similar?

The log is full of such entries:

[2014-12-12 14:13:48] WARNING[13249] pjsip: tsx0x7f591c002 .Failed to send Request msg OPTIONS/cseq=13230 (tdta0x7f591c001070)! err=171060 (Unsupported transport (PJSIP_EUNSUPTRANSPORT))
[2014-12-12 14:13:48] ERROR[13249] res_pjsip.c: Error attempting to send outbound OPTIONS request to endpoint
[2014-12-12 14:13:48] ERROR[13249] astobj2.c: bad magic number for object 0x7f591800e238. Object is likely destroyed.
[2014-12-12 14:13:48] ERROR[13249] res_pjsip/pjsip_options.c: Unable to send request to qualify contact sip:[email protected]:5060
[2014-12-12 14:13:48] WARNING[13250] pjsip: tsx0x7f5918005 .Failed to send Request msg OPTIONS/cseq=25989 (tdta0x7f5918004230)! err=171060 (Unsupported transport (PJSIP_EUNSUPTRANSPORT))
[2014-12-12 14:13:48] ERROR[13250] res_pjsip.c: Error attempting to send outbound OPTIONS request to endpoint
[2014-12-12 14:13:48] ERROR[13250] astobj2.c: bad magic number for object 0x7f591c000f68. Object is likely destroyed.
[2014-12-12 14:13:48] ERROR[13250] res_pjsip/pjsip_options.c: Unable to send request to qualify contact sip:[email protected]:5060

2

Have you tried restarting?

3

Yes, a number of times. Also tried to update freepbx, all modules… no use. PJSIP is completely dead. CHAN_SIP works fine so I am now migrating all extensions to chan_sip and changing ports so I do not have to visit all extensions at may locations to reconfigure the clients…

4

After an update this is still working fine for me so nothing on the freepbx side. i would attempt to update asterisk as well