Hi Nick,
I found when did asterisk -cvvvvvv next:
2017-02-06 09:56:12] WARNING[9024]: res_odbc.c:1560 odbc_obj_connect: res_odbc: Error SQLConnect=-1 errno=0 [unixODBC][Driver Manager]Data source name not found, and no default driver specified
[2017-02-06 09:56:12] WARNING[9024]: res_odbc.c:1370 _ast_odbc_request_obj2: Failed to connect to asteriskcdrdb
[2017-02-06 09:56:12] NOTICE[9024]: res_odbc.c:923 load_odbc_config: Registered ODBC class ‘asteriskcdrdb’ dsn->[MySQL-asteriskcdrdb]
Also I found massive warning messages.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:30551 build_peer: ‘tcp’ is not a valid transport type when tcpenable=no. If no other is specified, the defaults from general will be used.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:30551 build_peer: ‘tls’ is not a valid transport type when tlsenable=no. If no other is specified, the defaults from general will be used.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31197 display_nat_warning: !!! PLEASE NOTE: Setting ‘nat’ for a peer/user that differs from the global setting can make
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31198 display_nat_warning: !!! the name of that peer/user discoverable by an attacker. Replies for non-existent peers/users
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31199 display_nat_warning: !!! will be sent to a different port than replies for an existing peer/user. If at all possible,
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31200 display_nat_warning: !!! use the global ‘nat’ setting and do not set ‘nat’ per peer/user.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31201 display_nat_warning: !!! (config category=‘100’ global force_rport=‘Yes’ peer/user force_rport=‘No’)
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31197 display_nat_warning: !!! PLEASE NOTE: Setting ‘nat’ for a peer/user that differs from the global setting can make
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31198 display_nat_warning: !!! the name of that peer/user discoverable by an attacker. Replies for non-existent peers/users
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31199 display_nat_warning: !!! will be sent to a different port than replies for an existing peer/user. If at all possible,
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31200 display_nat_warning: !!! use the global ‘nat’ setting and do not set ‘nat’ per peer/user.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31201 display_nat_warning: !!! (config category=‘101’ global force_rport=‘Yes’ peer/user force_rport=‘No’)
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:30551 build_peer: ‘tcp’ is not a valid transport type when tcpenable=no. If no other is specified, the defaults from general will be used.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:30551 build_peer: ‘tls’ is not a valid transport type when tlsenable=no. If no other is specified, the defaults from general will be used.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31197 display_nat_warning: !!! PLEASE NOTE: Setting ‘nat’ for a peer/user that differs from the global setting can make
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31198 display_nat_warning: !!! the name of that peer/user discoverable by an attacker. Replies for non-existent peers/users
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31199 display_nat_warning: !!! will be sent to a different port than replies for an existing peer/user. If at all possible,
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31200 display_nat_warning: !!! use the global ‘nat’ setting and do not set ‘nat’ per peer/user.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31201 display_nat_warning: !!! (config category=‘105’ global force_rport=‘Yes’ peer/user force_rport=‘No’)
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:30551 build_peer: ‘tcp’ is not a valid transport type when tcpenable=no. If no other is specified, the defaults from general will be used.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:30551 build_peer: ‘tls’ is not a valid transport type when tlsenable=no. If no other is specified, the defaults from general will be used.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31197 display_nat_warning: !!! PLEASE NOTE: Setting ‘nat’ for a peer/user that differs from the global setting can make
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31198 display_nat_warning: !!! the name of that peer/user discoverable by an attacker. Replies for non-existent peers/users
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31199 display_nat_warning: !!! will be sent to a different port than replies for an existing peer/user. If at all possible,
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31200 display_nat_warning: !!! use the global ‘nat’ setting and do not set ‘nat’ per peer/user.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31201 display_nat_warning: !!! (config category=‘106’ global force_rport=‘Yes’ peer/user force_rport=‘No’)
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:30551 build_peer: ‘tcp’ is not a valid transport type when tcpenable=no. If no other is specified, the defaults from general will be used.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:30551 build_peer: ‘tls’ is not a valid transport type when tlsenable=no. If no other is specified, the defaults from general will be used.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31197 display_nat_warning: !!! PLEASE NOTE: Setting ‘nat’ for a peer/user that differs from the global setting can make
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31198 display_nat_warning: !!! the name of that peer/user discoverable by an attacker. Replies for non-existent peers/users
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31199 display_nat_warning: !!! will be sent to a different port than replies for an existing peer/user. If at all possible,
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31200 display_nat_warning: !!! use the global ‘nat’ setting and do not set ‘nat’ per peer/user.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31201 display_nat_warning: !!! (config category=‘107’ global force_rport=‘Yes’ peer/user force_rport=‘No’)
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31197 display_nat_warning: !!! PLEASE NOTE: Setting ‘nat’ for a peer/user that differs from the global setting can make
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31198 display_nat_warning: !!! the name of that peer/user discoverable by an attacker. Replies for non-existent peers/users
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31199 display_nat_warning: !!! will be sent to a different port than replies for an existing peer/user. If at all possible,
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31200 display_nat_warning: !!! use the global ‘nat’ setting and do not set ‘nat’ per peer/user.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31201 display_nat_warning: !!! (config category=‘111’ global force_rport=‘Yes’ peer/user force_rport=‘No’)
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31197 display_nat_warning: !!! PLEASE NOTE: Setting ‘nat’ for a peer/user that differs from the global setting can make
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31198 display_nat_warning: !!! the name of that peer/user discoverable by an attacker. Replies for non-existent peers/users
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31199 display_nat_warning: !!! will be sent to a different port than replies for an existing peer/user. If at all possible,
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31200 display_nat_warning: !!! use the global ‘nat’ setting and do not set ‘nat’ per peer/user.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31201 display_nat_warning: !!! (config category=‘112’ global force_rport=‘Yes’ peer/user force_rport=‘No’)
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:30551 build_peer: ‘tcp’ is not a valid transport type when tcpenable=no. If no other is specified, the defaults from general will be used.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:30551 build_peer: ‘tls’ is not a valid transport type when tlsenable=no. If no other is specified, the defaults from general will be used.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31197 display_nat_warning: !!! PLEASE NOTE: Setting ‘nat’ for a peer/user that differs from the global setting can make
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31198 display_nat_warning: !!! the name of that peer/user discoverable by an attacker. Replies for non-existent peers/users
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31199 display_nat_warning: !!! will be sent to a different port than replies for an existing peer/user. If at all possible,
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31200 display_nat_warning: !!! use the global ‘nat’ setting and do not set ‘nat’ per peer/user.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31201 display_nat_warning: !!! (config category=‘151’ global force_rport=‘Yes’ peer/user force_rport=‘No’)
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31197 display_nat_warning: !!! PLEASE NOTE: Setting ‘nat’ for a peer/user that differs from the global setting can make
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31198 display_nat_warning: !!! the name of that peer/user discoverable by an attacker. Replies for non-existent peers/users
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31199 display_nat_warning: !!! will be sent to a different port than replies for an existing peer/user. If at all possible,
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31200 display_nat_warning: !!! use the global ‘nat’ setting and do not set ‘nat’ per peer/user.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31201 display_nat_warning: !!! (config category=‘155’ global force_rport=‘Yes’ peer/user force_rport=‘No’)
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:30551 build_peer: ‘tcp’ is not a valid transport type when tcpenable=no. If no other is specified, the defaults from general will be used.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:30551 build_peer: ‘tls’ is not a valid transport type when tlsenable=no. If no other is specified, the defaults from general will be used.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31197 display_nat_warning: !!! PLEASE NOTE: Setting ‘nat’ for a peer/user that differs from the global setting can make
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31198 display_nat_warning: !!! the name of that peer/user discoverable by an attacker. Replies for non-existent peers/users
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31199 display_nat_warning: !!! will be sent to a different port than replies for an existing peer/user. If at all possible,
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31200 display_nat_warning: !!! use the global ‘nat’ setting and do not set ‘nat’ per peer/user.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31201 display_nat_warning: !!! (config category=‘100’ global force_rport=‘Yes’ peer/user force_rport=‘No’)
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31197 display_nat_warning: !!! PLEASE NOTE: Setting ‘nat’ for a peer/user that differs from the global setting can make
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31198 display_nat_warning: !!! the name of that peer/user discoverable by an attacker. Replies for non-existent peers/users
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31199 display_nat_warning: !!! will be sent to a different port than replies for an existing peer/user. If at all possible,
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31200 display_nat_warning: !!! use the global ‘nat’ setting and do not set ‘nat’ per peer/user.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31201 display_nat_warning: !!! (config category=‘101’ global force_rport=‘Yes’ peer/user force_rport=‘No’)
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:30551 build_peer: ‘tcp’ is not a valid transport type when tcpenable=no. If no other is specified, the defaults from general will be used.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:30551 build_peer: ‘tls’ is not a valid transport type when tlsenable=no. If no other is specified, the defaults from general will be used.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31197 display_nat_warning: !!! PLEASE NOTE: Setting ‘nat’ for a peer/user that differs from the global setting can make
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31198 display_nat_warning: !!! the name of that peer/user discoverable by an attacker. Replies for non-existent peers/users
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31199 display_nat_warning: !!! will be sent to a different port than replies for an existing peer/user. If at all possible,
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31200 display_nat_warning: !!! use the global ‘nat’ setting and do not set ‘nat’ per peer/user.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31201 display_nat_warning: !!! (config category=‘105’ global force_rport=‘Yes’ peer/user force_rport=‘No’)
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:30551 build_peer: ‘tcp’ is not a valid transport type when tcpenable=no. If no other is specified, the defaults from general will be used.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:30551 build_peer: ‘tls’ is not a valid transport type when tlsenable=no. If no other is specified, the defaults from general will be used.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31197 display_nat_warning: !!! PLEASE NOTE: Setting ‘nat’ for a peer/user that differs from the global setting can make
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31198 display_nat_warning: !!! the name of that peer/user discoverable by an attacker. Replies for non-existent peers/users
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31199 display_nat_warning: !!! will be sent to a different port than replies for an existing peer/user. If at all possible,
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31200 display_nat_warning: !!! use the global ‘nat’ setting and do not set ‘nat’ per peer/user.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31201 display_nat_warning: !!! (config category=‘106’ global force_rport=‘Yes’ peer/user force_rport=‘No’)
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:30551 build_peer: ‘tcp’ is not a valid transport type when tcpenable=no. If no other is specified, the defaults from general will be used.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:30551 build_peer: ‘tls’ is not a valid transport type when tlsenable=no. If no other is specified, the defaults from general will be used.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31197 display_nat_warning: !!! PLEASE NOTE: Setting ‘nat’ for a peer/user that differs from the global setting can make
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31198 display_nat_warning: !!! the name of that peer/user discoverable by an attacker. Replies for non-existent peers/users
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31199 display_nat_warning: !!! will be sent to a different port than replies for an existing peer/user. If at all possible,
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31200 display_nat_warning: !!! use the global ‘nat’ setting and do not set ‘nat’ per peer/user.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31201 display_nat_warning: !!! (config category=‘107’ global force_rport=‘Yes’ peer/user force_rport=‘No’)
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31197 display_nat_warning: !!! PLEASE NOTE: Setting ‘nat’ for a peer/user that differs from the global setting can make
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31198 display_nat_warning: !!! the name of that peer/user discoverable by an attacker. Replies for non-existent peers/users
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31199 display_nat_warning: !!! will be sent to a different port than replies for an existing peer/user. If at all possible,
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31200 display_nat_warning: !!! use the global ‘nat’ setting and do not set ‘nat’ per peer/user.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31201 display_nat_warning: !!! (config category=‘111’ global force_rport=‘Yes’ peer/user force_rport=‘No’)
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31197 display_nat_warning: !!! PLEASE NOTE: Setting ‘nat’ for a peer/user that differs from the global setting can make
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31198 display_nat_warning: !!! the name of that peer/user discoverable by an attacker. Replies for non-existent peers/users
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31199 display_nat_warning: !!! will be sent to a different port than replies for an existing peer/user. If at all possible,
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31200 display_nat_warning: !!! use the global ‘nat’ setting and do not set ‘nat’ per peer/user.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31201 display_nat_warning: !!! (config category=‘112’ global force_rport=‘Yes’ peer/user force_rport=‘No’)
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:30551 build_peer: ‘tcp’ is not a valid transport type when tcpenable=no. If no other is specified, the defaults from general will be used.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:30551 build_peer: ‘tls’ is not a valid transport type when tlsenable=no. If no other is specified, the defaults from general will be used.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31197 display_nat_warning: !!! PLEASE NOTE: Setting ‘nat’ for a peer/user that differs from the global setting can make
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31198 display_nat_warning: !!! the name of that peer/user discoverable by an attacker. Replies for non-existent peers/users
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31199 display_nat_warning: !!! will be sent to a different port than replies for an existing peer/user. If at all possible,
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31200 display_nat_warning: !!! use the global ‘nat’ setting and do not set ‘nat’ per peer/user.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31201 display_nat_warning: !!! (config category=‘151’ global force_rport=‘Yes’ peer/user force_rport=‘No’)
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31197 display_nat_warning: !!! PLEASE NOTE: Setting ‘nat’ for a peer/user that differs from the global setting can make
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31198 display_nat_warning: !!! the name of that peer/user discoverable by an attacker. Replies for non-existent peers/users
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31199 display_nat_warning: !!! will be sent to a different port than replies for an existing peer/user. If at all possible,
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31200 display_nat_warning: !!! use the global ‘nat’ setting and do not set ‘nat’ per peer/user.
[2017-02-06 09:56:12] WARNING[9024]: chan_sip.c:31201 display_nat_warning: !!! (config category=‘155’ global force_rport=‘Yes’ peer/user force_rport=‘No’)
Also
[2017-02-06 09:56:12] NOTICE[9024]: res_odbc.c:1528 odbc_obj_connect: Connecting asteriskcdrdb
[2017-02-06 09:56:12] WARNING[9024]: res_odbc.c:1560 odbc_obj_connect: res_odbc: Error SQLConnect=-1 errno=0 [unixODBC][Driver Manager]Data source name not found, and no default driver specified
[2017-02-06 09:56:12] WARNING[9024]: res_odbc.c:1370 _ast_odbc_request_obj2: Failed to connect to asteriskcdrdb
[2017-02-06 09:56:12] WARNING[9024]: cel_odbc.c:142 load_config: No such connection ‘asteriskcdrdb’ in the ‘cel’ section of cel_odbc.conf. Check res_odbc.conf.
I believe the massive warning block is avout pjsip which is I’m not going to load but only the real problem I could found is the problem with connection to asteriskcdrdb DB. I think, may be I’m wrong it should not be impact on connection between FreePBX and Asterisk.
Also I found the port number for Asterisk manager in Asterisk side was 5038 and for FreePBX was 8088. I’ve change it to 5038, but it didn’t help.
Still have the same picture “Unable to find Asterisk result”