asterisk users - May 2022 - [External] Asterisk 18.12.0 question

On Fri, May 13, 2022 at 1:05 PM Dan Cropp <dan at amtelco.com> wrote:
> I have been using Asterisk 18.11.2.
>
> Just tried Asterisk 18.12.0 and am running into a problem with the
> res_pjsip_transport_websocket.
>
>
>
> Using Ubuntu 20
>
> I use a bash shell script to compile Asterisk with settings.
>
> I didn’t modify any settings from Asterisk 18.11.2 build that works.
>
> After compiling, I make an install .deb pkg that wraps all the Asterisk
> support and use this dpkg to install on other boxes.  Eliminates the need
> to compile and everything on customer boxes.
>
>
>
> All this process works great for Asterisk 18.11.2 (and did so for several
> other Asterisk versions prior to 18.11.2).
>
>
>
> I can run Asterisk on the box I compile on.
>
> However, the boxes I install the .deb pkg, Asterisk always complains that
> it cannot load the res_pjsip_transport_websocket module.
>
>
>
> I have looked at all the dependencies and confirmed I am copying all the
> .so from my compile box to this new box I install on.
>
>
>
> Did something change with the res_pjsip_transport_websocket where it
> requires something new?
>
> Does PJSIP 2.12 require something new that the previous PJSIP version
> Asterisk used did not require?
>
The res_pjsip_transport_websocket module is the exact same between the two
versions. I'm not aware of anything new PJSIP 2.12 requires. You'd have
to
show what it actually says when attempting to load the module.

-- 
Joshua C. Colp
Asterisk Technical Lead
Sangoma Technologies
Check us out at www.sangoma.com and www.asterisk.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20220513/819969df/attachment.html>

Hi Joshua,

Thank you for helping me diagnose this.

Interesting that they are the exact same between versions.
File sizes are slightly different between the two when I compile them.  18.12.0
would have any new default configurations that were not part of 18.11.2, such as
aeap.  Some codecs also seem to be defaulted now.  Not sure if that makes a
difference.  After this e-mail, I will try disabling some of the new additions. 
Maybe that will resolve things.
18.11.2 408136
18.12.0 411856

Here is output as it loads the res_pjsip_transport_websocket.so being loaded on
18.11.2…

Loading app_stack.so.
  == AGI Command 'gosub' registered
  == Registered application 'StackPop'
  == Registered application 'Return'
  == Registered application 'GosubIf'
  == Registered application 'Gosub'
  == Registered custom function 'LOCAL'
  == Registered custom function 'LOCAL_PEEK'
  == Registered custom function 'STACK_PEEK'
  == app_stack.so => (Dialplan subroutines (Gosub, Return, etc))
Loading res_pjsip_path.so.
  == res_pjsip_path.so => (PJSIP Path Header Support)
Loading res_pjsip_transport_websocket.so.
  == WebSocket registered sub-protocol 'sip'
  == res_pjsip_transport_websocket.so => (PJSIP WebSocket Transport Support)
Loading res_stasis_recording.so.
  == res_stasis_recording.so => (Stasis application recording support)
Loading res_pjsip_nat.so.
  == res_pjsip_nat.so => (PJSIP NAT Support)
Loading res_pjsip_diversion.so.
  == res_pjsip_diversion.so => (PJSIP Add Diversion Header Support)

Here is what logs show on 18.12.0….

Loading app_stack.so.
  == AGI Command 'gosub' registered
  == Registered application 'StackPop'
  == Registered application 'Return'
  == Registered application 'GosubIf'
  == Registered application 'Gosub'
  == Registered custom function 'LOCAL'
  == Registered custom function 'LOCAL_PEEK'
  == Registered custom function 'STACK_PEEK'
  == app_stack.so => (Dialplan subroutines (Gosub, Return, etc))
Loading res_pjsip_path.so.
  == res_pjsip_path.so => (PJSIP Path Header Support)
Loading res_pjsip_transport_websocket.so.
Loading res_stasis_recording.so.
  == res_stasis_recording.so => (Stasis application recording support)
Loading res_pjsip_nat.so.
  == res_pjsip_nat.so => (PJSIP NAT Support)
Loading res_pjsip_diversion.so.
  == res_pjsip_diversion.so => (PJSIP Add Diversion Header Support)
…
[May 13 12:34:08] WARNING[1400]: loader.c:2393 load_modules: Some non-required
modules failed to load.
[May 13 12:34:08] WARNING[1400]: loader.c:2487 load_modules: Module
'chan_sip' has been loaded but was deprecated in Asterisk version 17 and
will be removed in Asterisk version 21.
[May 13 12:34:08] ERROR[1400]: loader.c:2508 load_modules: Error loading module
'app_queue.so', missing dependency: res_monitor
[May 13 12:34:08] ERROR[1400]: loader.c:2508 load_modules:
res_pjsip_transport_websocket declined to load.
[May 13 12:34:08] WARNING[1407]: chan_sip.c:35470 deprecation_notice: chan_sip
has no official maintainer and is deprecated.  Migration to
[May 13 12:34:08] WARNING[1407]: chan_sip.c:35471 deprecation_notice: chan_pjsip
is recommended.  See guides at the Asterisk Wiki:
[May 13 12:34:08] WARNING[1407]: chan_sip.c:35472 deprecation_notice:
https://wiki.asterisk.org/wiki/display/AST/Migrating+from+chan_sip+to+res_pjsip
[May 13 12:34:08] WARNING[1407]: chan_sip.c:35473 deprecation_notice:
https://wiki.asterisk.org/wiki/display/AST/Configuring+res_pjsip

Because some of our customers have refused to migrate to PJSIP, we still compile
support for chan_sip.
However, we make sure to disable the chan_sip web support in the configuration
files.

Dan
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20220513/298a36b7/attachment.html>