SIP Trunk warning log

Good morning

I have several SIP Trunks established and working correctly but when I execute the asterisk -rvvvv command I get the following messages

[root@freepbx ~]# asterisk -rvvvvv
Asterisk 16.25.0, Copyright (C) 1999 - 2021, Sangoma Technologies Corporation and others.
Created by Mark Spencer [email protected]
Asterisk comes with ABSOLUTELY NO WARRANTY; type ‘core show warranty’ for details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it under
certain conditions. Type ‘core show license’ for details.

Connected to Asterisk 16.25.0 currently running on freepbx (pid = 29286)
[2023-03-29 10:33:36] WARNING[918]: res_pjsip_outbound_registration.c:1053 handle_registration_response: ‘405’ fatal response received from ‘sip:172.24.164.7’ on registration attempt to ‘sip:SIP_TRUNK_CCM(MULTICLIENTE)@172.24.164.7’, retrying in ‘30’ seconds
[2023-03-29 10:33:44] WARNING[23226]: res_pjsip_outbound_registration.c:1053 handle_registration_response: ‘405’ fatal response received from ‘sip:172.31.252.145’ on registration attempt to ‘sip:[email protected]’, retrying in ‘30’ seconds
[2023-03-29 10:33:49] WARNING[918]: res_pjsip_outbound_registration.c:1045 handle_registration_response: 403 Forbidden fatal response received from ‘sip:10.52.5.232:5060’ on registration attempt to ‘sip:[email protected]:5060’, retrying in ‘30’ seconds
[2023-03-29 10:34:06] WARNING[918]: res_pjsip_outbound_registration.c:1053 handle_registration_response: ‘405’ fatal response received from ‘sip:172.24.164.7’ on registration attempt to ‘sip:SIP_TRUNK_CCM(MULTICLIENTE)@172.24.164.7’, retrying in ‘30’ seconds
[2023-03-29 10:34:14] WARNING[18986]: res_pjsip_outbound_registration.c:1053 handle_registration_response: ‘405’ fatal response received from ‘sip:172.31.252.145’ on registration attempt to ‘sip:[email protected]’, retrying in ‘30’ seconds
[2023-03-29 10:34:18] WARNING[918]: res_pjsip_outbound_registration.c:837 schedule_retry: Temporal response ‘503’ received from ‘sip:172.26.1.5’ on registration attempt to ‘sip:[email protected]’, retrying in ‘60’
[2023-03-29 10:34:19] WARNING[23226]: res_pjsip_outbound_registration.c:837 schedule_retry: Temporal response ‘401’ received from ‘sip:10.52.5.232:5060’ on registration attempt to ‘sip:[email protected]:5060’, retrying in ‘60’
[2023-03-29 10:34:23] WARNING[23226]: res_pjsip_outbound_registration.c:837 schedule_retry: Temporal response ‘503’ received from ‘sip:172.26.1.4’ on registration attempt to ‘sip:[email protected]’, retrying in ‘60’
[2023-03-29 10:34:24] WARNING[11042]: res_pjsip_outbound_registration.c:837 schedule_retry: Temporal response ‘503’ received from ‘sip:192.168.21.18’ on registration attempt to ‘sip:[email protected]’, retrying in ‘60’
[2023-03-29 10:34:36] WARNING[11042]: res_pjsip_outbound_registration.c:1053 handle_registration_response: ‘405’ fatal response received from ‘sip:172.24.164.7’ on registration attempt to ‘sip:SIP_TRUNK_CCM(MULTICLIENTE)@172.24.164.7’, retrying in ‘30’ seconds
[2023-03-29 10:34:44] WARNING[918]: res_pjsip_outbound_registration.c:1053 handle_registration_response: ‘405’ fatal response received from ‘sip:172.31.252.145’ on registration attempt to ‘sip:[email protected]’, retrying in ‘30’ seconds
[2023-03-29 10:35:06] WARNING[918]: res_pjsip_outbound_registration.c:1053 handle_registration_response: ‘405’ fatal response received from ‘sip:172.24.164.7’ on registration attempt to ‘sip:SIP_TRUNK_CCM(MULTICLIENTE)@172.24.164.7’, retrying in ‘30’ seconds
[2023-03-29 10:35:14] WARNING[18986]: res_pjsip_outbound_registration.c:1053 handle_registration_response: ‘405’ fatal response received from ‘sip:172.31.252.145’ on registration attempt to ‘sip:[email protected]’, retrying in ‘30’ seconds
[2023-03-29 10:35:18] WARNING[11042]: res_pjsip_outbound_registration.c:837 schedule_retry: Temporal response ‘503’ received from ‘sip:172.26.1.5’ on registration attempt to ‘sip:[email protected]’, retrying in ‘60’
[2023-03-29 10:35:19] WARNING[11042]: res_pjsip_outbound_registration.c:1045 handle_registration_response: 403 Forbidden fatal response received from ‘sip:10.52.5.232:5060’ on registration attempt to ‘sip:[email protected]:5060’, retrying in ‘30’ seconds
[2023-03-29 10:35:23] WARNING[11042]: res_pjsip_outbound_registration.c:837 schedule_retry: Temporal response ‘503’ received from ‘sip:172.26.1.4’ on registration attempt to ‘sip:[email protected]’, retrying in ‘60’
[2023-03-29 10:35:24] WARNING[23226]: res_pjsip_outbound_registration.c:837 schedule_retry: Temporal response ‘503’ received from ‘sip:192.168.21.18’ on registration attempt to ‘sip:[email protected]’, retrying in ‘60’
[2023-03-29 10:35:36] WARNING[918]: res_pjsip_outbound_registration.c:1053 handle_registration_response: ‘405’ fatal response received from ‘sip:172.24.164.7’ on registration attempt to ‘sip:SIP_TRUNK_CCM(MULTICLIENTE)@172.24.164.7’, retrying in ‘30’ seconds
[2023-03-29 10:35:44] WARNING[18986]: res_pjsip_outbound_registration.c:1053 handle_registration_response: ‘405’ fatal response received from ‘sip:172.31.252.145’ on registration attempt to ‘sip:[email protected]’, retrying in ‘30’ seconds
[2023-03-29 10:35:49] WARNING[11042]: res_pjsip_outbound_registration.c:837 schedule_retry: Temporal response ‘401’ received from ‘sip:10.52.5.232:5060’ on registration attempt to ‘sip:[email protected]:5060’, retrying in ‘60’

Do you know what can be produced?

405 is method not allowed. You are trying to register with something that doesn’t use registrations.

403 is forbidden, and generally means you are not a known user, or you provided the wrong password.

503 is a catchall error, and you will need to ask the provider.

401 isn’t normally a reason to wait 60 seconds. That suggests you have no credentials to offer for that provider. (Does it really say “temporal” and not “temporary”?)

It really says temporal. It does mean temporary though. :slight_smile:

Hello

After changing the SIP Trunk configuration, the messages have no longer jumped

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