Distro upgrade broken

[dtobal]

Hi folks!
I did follow the recipts:
My Distro was working properly… PJSIP and SIP fine… TLS, etc
But, I need to upgrade it because new feature is available on the latest… so… following the recipt…

How to update FreePBX Distro:12 correctly?

Whoa! How strange, I have not seen such a list here. But the mistake still remains. [RPM]

fwconsole ma upgradeall
fwconsole chown
fwconsole reload
yum update -y
reboot
… Now… I have an asterisk closing and the logs shows:

Nov 16 19:54:34 sbcasteraws kernel: asterisk[44157]: segfault at 0 ip 00007fcee49e8411 sp 00007fcedc75e6b0 error 4 in res_pjsip.so[7fcee49c2000+62000]
Nov 16 19:55:30 sbcasteraws kernel: asterisk[44163]: segfault at 0 ip 00007fed4ecbb751 sp 00007fed46a265e0 error 4 in res_pjsip.so[7fed4ec8a000+62000]
[root@sbcasteraws log]# cd asterisk/
[root@sbcasteraws asterisk]# tail -n50 full
[2021-11-16 19:55:22] DEBUG[44164] res_pjsip/pjsip_options.c: Qualifying all contacts on AOR ‘ipbxnonono’
[2021-11-16 19:55:22] DEBUG[44164] res_pjsip/pjsip_options.c: Qualifying contact ‘ipbxnonono@@f1fd9ca93998364374d36cf7e5e1afc3’ on AOR ‘ipbxnonono’
[2021-11-16 19:55:22] ERROR[44164] res_pjsip.c: Unable to retrieve PJSIP transport ‘0.0.0.0-udp’
[2021-11-16 19:55:22] DEBUG[44164] res_pjsip.c: 0x7fed9c006640: Wrapper created
[2021-11-16 19:55:22] DEBUG[44164] res_pjsip.c: 0x7fed9c006640: Set timer to 3000 msec
[2021-11-16 19:55:22] DEBUG[44164] res_pjsip/pjsip_resolver.c: Performing SIP DNS resolution of target ‘10.188.1.254’
[2021-11-16 19:55:22] DEBUG[44164] res_pjsip/pjsip_resolver.c: Transport type for target ‘10.188.1.254’ is ‘UDP transport’
[2021-11-16 19:55:22] DEBUG[44164] res_pjsip/pjsip_resolver.c: Target ‘10.188.1.254’ is an IP address, skipping resolution
[2021-11-16 19:55:22] DEBUG[44164] res_pjsip.c: 0x7fed9c006640: PJSIP tsx response received
[2021-11-16 19:55:22] DEBUG[44164] res_pjsip.c: 0x7fed9c006640: Cancelling timer
[2021-11-16 19:55:22] DEBUG[44164] res_pjsip.c: 0x7fed9c006640: Timer cancelled
[2021-11-16 19:55:22] DEBUG[44164] res_pjsip.c: 0x7fed9c006640: Callbacks executed
[2021-11-16 19:55:22] ERROR[44164] res_pjsip.c: Error 171060 ‘Unsupported transport (PJSIP_EUNSUPTRANSPORT)’ sending OPTIONS request to endpoint ipbxnonono
[2021-11-16 19:55:22] DEBUG[44164] res_pjsip.c: 0x7fed9c006640: wrapper destroyed
[2021-11-16 19:55:22] VERBOSE[44164] res_pjsip/pjsip_options.c: Contact ipbxnonono/sip:10.188.1.254:5060 is now Unreachable. RTT: 0.000 msec
[2021-11-16 19:55:22] DEBUG[44164] res_pjsip/pjsip_options.c: AOR ‘ipbxnonono’ now has 0 available contacts
[2021-11-16 19:55:27] DEBUG[44164] res_pjsip/pjsip_options.c: Qualifying all contacts on AOR ‘MSTEAMS’
[2021-11-16 19:55:27] DEBUG[44164] res_pjsip/pjsip_options.c: Qualifying contact ‘MSTEAMS@@ebb7eda27aa2c67cf01629e2c3efd181’ on AOR ‘MSTEAMS’
[2021-11-16 19:55:27] DEBUG[44164] res_pjsip.c: 0x7fed9c006210: Wrapper created
[2021-11-16 19:55:27] DEBUG[44164] res_pjsip.c: 0x7fed9c006210: Set timer to 3000 msec
[2021-11-16 19:55:27] DEBUG[44164] res_pjsip/pjsip_resolver.c: Performing SIP DNS resolution of target ‘sip.pstnhub.microsoft.com’
[2021-11-16 19:55:27] DEBUG[44164] res_pjsip/pjsip_resolver.c: Transport type for target ‘sip.pstnhub.microsoft.com’ is ‘TLS transport’
[2021-11-16 19:55:27] DEBUG[44164] res_pjsip/pjsip_resolver.c: [0x7fed9c008028] Created resolution tracking for target ‘sip.pstnhub.microsoft.com’
[2021-11-16 19:55:27] DEBUG[44164] res_pjsip/pjsip_resolver.c: [0x7fed9c008028] Added target ‘sip.pstnhub.microsoft.com’ with record type ‘35’, transport ‘TLS transport’, and port ‘5061’
[2021-11-16 19:55:27] DEBUG[44164] res_pjsip/pjsip_resolver.c: [0x7fed9c008028] Added target ‘_sips._tcp.sip.pstnhub.microsoft.com’ with record type ‘33’, transport’TLS transport’, and port ‘5061’
[2021-11-16 19:55:27] DEBUG[44164] res_pjsip/pjsip_resolver.c: [0x7fed9c008028] Added target ‘sip.pstnhub.microsoft.com’ with record type ‘1’, transport ‘TLS transport’, and port ‘5061’
[2021-11-16 19:55:27] DEBUG[44164] res_pjsip/pjsip_resolver.c: [0x7fed9c008028] Starting initial resolution using parallel queries for target ‘sip.pstnhub.microsoft.com’
[2021-11-16 19:55:29] DEBUG[44179] res_pjsip/pjsip_resolver.c: [0x7fed9c008028] All parallel queries completed
[2021-11-16 19:55:29] DEBUG[44179] res_pjsip/pjsip_resolver.c: [0x7fed9c008028] SRV record received on target ‘_sips._tcp.sip.pstnhub.microsoft.com’
[2021-11-16 19:55:29] DEBUG[44179] res_pjsip/pjsip_resolver.c: [0x7fed9c008028] Added target ‘sip.pstnhub.microsoft.com’ with record type ‘1’, transport ‘TLS transport’, and port ‘5061’
[2021-11-16 19:55:29] DEBUG[44179] res_pjsip/pjsip_resolver.c: [0x7fed9c008028] SRV record received on target ‘_sips._tcp.sip.pstnhub.microsoft.com’
[2021-11-16 19:55:29] DEBUG[44179] res_pjsip/pjsip_resolver.c: [0x7fed9c008028] Added target ‘sip2.pstnhub.microsoft.com’ with record type ‘1’, transport ‘TLS transport’, and port ‘5061’
[2021-11-16 19:55:29] DEBUG[44179] res_pjsip/pjsip_resolver.c: [0x7fed9c008028] SRV record received on target ‘_sips._tcp.sip.pstnhub.microsoft.com’
[2021-11-16 19:55:29] DEBUG[44179] res_pjsip/pjsip_resolver.c: [0x7fed9c008028] Added target ‘sip3.pstnhub.microsoft.com’ with record type ‘1’, transport ‘TLS transport’, and port ‘5061’
[2021-11-16 19:55:29] DEBUG[44179] res_pjsip/pjsip_resolver.c: [0x7fed9c008028] A record being skipped on target ‘sip.pstnhub.microsoft.com’ because NAPTR or SRV record exists
[2021-11-16 19:55:29] DEBUG[44179] res_pjsip/pjsip_resolver.c: [0x7fed9c008028] New queries added, performing parallel resolution again
[2021-11-16 19:55:29] DEBUG[44211] res_timing_timerfd.c: Expected to acknowledge 1 ticks but got 2 instead
[2021-11-16 19:55:29] DEBUG[44179] res_pjsip/pjsip_resolver.c: [0x7fed9c008028] All parallel queries completed
[2021-11-16 19:55:29] DEBUG[44179] res_pjsip/pjsip_resolver.c: [0x7fed9c008028] A record received on target ‘sip.pstnhub.microsoft.com’
[2021-11-16 19:55:29] DEBUG[44179] res_pjsip/pjsip_resolver.c: [0x7fed9c008028] A record received on target ‘sip2.pstnhub.microsoft.com’
[2021-11-16 19:55:29] DEBUG[44179] res_pjsip/pjsip_resolver.c: [0x7fed9c008028] A record received on target ‘sip3.pstnhub.microsoft.com’
[2021-11-16 19:55:29] DEBUG[44179] res_pjsip/pjsip_resolver.c: [0x7fed9c008028] Resolution completed - 3 viable targets
[2021-11-16 19:55:29] DEBUG[44164] res_pjsip/pjsip_resolver.c: [0x7fed9c008028] Address ‘0’ is 52.114.132.46:5061 with transport ‘TLS transport’
[2021-11-16 19:55:29] DEBUG[44164] res_pjsip/pjsip_resolver.c: [0x7fed9c008028] Address ‘1’ is 52.114.76.76:5061 with transport ‘TLS transport’
[2021-11-16 19:55:29] DEBUG[44164] res_pjsip/pjsip_resolver.c: [0x7fed9c008028] Address ‘2’ is 52.114.14.70:5061 with transport ‘TLS transport’
[2021-11-16 19:55:29] DEBUG[44164] res_pjsip/pjsip_resolver.c: [0x7fed9c008028] Invoking user callback with ‘3’ addresses
[2021-11-16 19:55:29] DEBUG[44164] res_pjsip/pjsip_message_filter.c: Re-wrote Contact URI host/port to 10.188.1.90:5071 (this may be re-written again later)
[2021-11-16 19:55:29] DEBUG[44164] netsock2.c: Splitting ‘52.114.132.46’ into…
[2021-11-16 19:55:29] DEBUG[44164] netsock2.c: …host ‘52.114.132.46’ and port ‘’.
[2021-11-16 19:55:29] DEBUG[44163] res_pjsip/pjsip_transport_events.c: Reliable transport ‘tlsc0x7fed9c2f3d78’ state:CONNECTED
[root@sbcasteraws asterisk]#

This distro was Asterisk-16.10 with res_pjsip.c compiled to rewrite FQDN and SIP too (chan_sip.c).
I didn’t recompiled it after the upgrade. Should I?

Do I really need change Asterisk in the code? Isn’t there any Asterisk SIP Settings inside the Distro to force FQDN instead ExternIP?

This Distro is working fine as an SBC, but I need to migrate my SIP to PJSIP with TLS 1.2. My pre-upgrade Distro didnt have TLS1.2 and it was bugging with SIP/REFER from MS TEAMS when a call was in Hold. So… I am upgrading to be TLS1.2 compatible, and fix HOLD with PJSIP.

Someone could help me? How can I debug and fix this segmentfault?

Thanks!

[billsimon]

@dtobal

This distro was Asterisk-16.10 with res_pjsip.c compiled to rewrite FQDN and SIP too (chan_sip.c).
I didn’t recompiled it after the upgrade. Should I?

If you compiled your own custom code, I don’t think we call that “Distro” here. But others might correct me if I am wrong.

You won’t be able to use modules compiled for an older version on your newer version.

Folks at VitalPBX contributed this patch for using DNS name rather than IP in the fields Microsoft cares about, though I don’t know whether it’s being considered for inclusion into Asterisk: https://github.com/eagle26/asterisk/commit/203b6ebb9b976a496e524fc41b3b4f2b7480fff1.patch

[dtobal]

Any chance of update/upgrade? Rollback the original library? Because I didnt change alot of code. I just change the parameter about externip/fqdn and replace the res_pjsip.so and chan_sip. I have the original files. Could I restore them before do the update?

[jcolp (Joshua Colp)]

There has been no issue created, or code review put up with license agreement signed. Until that is done, the patch can not be taken and put into Asterisk. Oh, you may have meant from their side instead! Ha, I can’t speak to that so disregard my post if so.

[dtobal]

Joshua, no way to use FQDN instead externip without recompiling the code?

[jcolp (Joshua Colp)]

There is no such functionality in Asterisk as of this time.

[billsimon]

I don’t believe they offered the patch to the Asterisk project; they only posted it publicly.