Why does Asterisk constantly write notice?

Asterisk Asterisk Support
1

OS: Alpine Linux 3.16
Asterisk: 18.15.1

I have configured Asterisk based on configuration files. Everything works as needed. Then I decided to transfer everything to the realtime database, via ODBC. Everything has been set up successfully, everything works, but now I have a notice constantly displayed in my logs:

[Mar 15 17:26:46] NOTICE[36]: res_pjsip/config_transport.c:768 transport_apply: Transport 'transport-tls' is not fully reloadable, not reloading: protocol, bind, TLS (everything but certificate and private key if filename is unchanged), TCP, ToS, or CoS options.
[Mar 15 17:27:03] NOTICE[35]: res_pjsip/config_transport.c:768 transport_apply: Transport 'transport-udp' is not fully reloadable, not reloading: protocol, bind, TLS (everything but certificate and private key if filename is unchanged), TCP, ToS, or CoS options.
[Mar 15 17:27:03] NOTICE[36]: res_pjsip/config_transport.c:768 transport_apply: Transport 'transport-udp' is not fully reloadable, not reloading: protocol, bind, TLS (everything but certificate and private key if filename is unchanged), TCP, ToS, or CoS options.
[Mar 15 17:27:03] NOTICE[36]: res_pjsip/config_transport.c:768 transport_apply: Transport 'transport-udp' is not fully reloadable, not reloading: protocol, bind, TLS (everything but certificate and private key if filename is unchanged), TCP, ToS, or CoS options.
[Mar 15 17:27:03] NOTICE[35]: res_pjsip/config_transport.c:768 transport_apply: Transport 'transport-udp' is not fully reloadable, not reloading: protocol, bind, TLS (everything but certificate and private key if filename is unchanged), TCP, ToS, or CoS options.
[Mar 15 17:27:03] NOTICE[36]: res_pjsip/config_transport.c:768 transport_apply: Transport 'transport-udp' is not fully reloadable, not reloading: protocol, bind, TLS (everything but certificate and private key if filename is unchanged), TCP, ToS, or CoS options.
[Mar 15 17:27:03] NOTICE[36]: res_pjsip/config_transport.c:768 transport_apply: Transport 'transport-udp' is not fully reloadable, not reloading: protocol, bind, TLS (everything but certificate and private key if filename is unchanged), TCP, ToS, or CoS options.
[Mar 15 17:27:40] NOTICE[36]: res_pjsip/config_transport.c:768 transport_apply: Transport 'transport-tls' is not fully reloadable, not reloading: protocol, bind, TLS (everything but certificate and private key if filename is unchanged), TCP, ToS, or CoS options.
[Mar 15 17:27:40] NOTICE[36]: res_pjsip/config_transport.c:768 transport_apply: Transport 'transport-tls' is not fully reloadable, not reloading: protocol, bind, TLS (everything but certificate and private key if filename is unchanged), TCP, ToS, or CoS options.
[Mar 15 17:28:34] NOTICE[36]: res_pjsip/config_transport.c:768 transport_apply: Transport 'transport-tls' is not fully reloadable, not reloading: protocol, bind, TLS (everything but certificate and private key if filename is unchanged), TCP, ToS, or CoS options.
[Mar 15 17:28:34] NOTICE[36]: res_pjsip/config_transport.c:768 transport_apply: Transport 'transport-tls' is not fully reloadable, not reloading: protocol, bind, TLS (everything but certificate and private key if filename is unchanged), TCP, ToS, or CoS options.

As far as I understand - the notification is not an error. Why is it output with such a constant frequency? Is there any way to configure this parameter or go back to *.conf again?

Just in case, I will provide my connection configuration with the database.

/etc/odbc.ini:

[asterisk]
Description = PostgreSQL connection to 'asterisk' database
Driver      = PostgreSQL
Database    = asterisk
Servername  = localhost
UserName    = asterisk
Password    = asterisk
Port        = 5432

/etc/odbcinst.ini:

[PostgreSQL]
Description = ODBC for PostgreSQL
Driver64    = /usr/lib/psqlodbcw.so

/etc/asterisk/res_odbc.conf:

[asterisk]
enabled => yes
dsn => asterisk
username => asterisk
password => asterisk
pre-connect => yes

/etc/asterisk/sorcery.conf:

[res_pjsip]
endpoint=realtime,ps_endpoints
auth=realtime,ps_auths
aor=realtime,ps_aors
domain_alias=realtime,ps_domain_aliases
contact=realtime,ps_contacts
registration=realtime,ps_registrations
transport=realtime,ps_transports

[res_pjsip_endpoint_identifier_ip]
identify=realtime,ps_endpoint_id_ips

/etc/asterisk/extconfig.conf:

[settings]
ps_endpoints => odbc,asterisk
ps_auths => odbc,asterisk
ps_aors => odbc,asterisk
ps_domain_aliases => odbc,asterisk
ps_endpoint_id_ips => odbc,asterisk
ps_contacts => odbc,asterisk
ps_registrations => odbc,asterisk
ps_transports => odbc,asterisk

Maybe I forgot to configure something else?

2

It’s because you are storing transports in realtime. Don’t do it. Just don’t. Every time it goes to look for transport info it has to update the state, and will print that message.

1 Like
3

Just a theoretical question - then why was this done?

4

Nothing really needs to be done to support things like that. It just occurs due to the underlying implementation.

5

Thanks)

6

I’ll also give my general realtime comment: If you use realtime then you increase your exposure to problems, because if your database has problems then your Asterisk can have problems.

1 Like
7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.