Invalid profile "external-ipv6"

Status
Not open for further replies.

Heinrich

New Member
Jul 2, 2022
4
0
1
70
Bremen, Germany
Hello all,

i am trying to setup a IPV6-only installation of FusionPBX. Reason is, i am on a home network behind NAT and i want to avoid any potential NAT-problems with voip over NAT.

My problem is that i cannot start the "external-ipv6" profile because the system deems it "Invalid".
If i try to start it, i get a message "Started successfully" but it is not running. If i click "rescan" (whatever that means), i get "Invalid profile". Clicking on the profile link does not show the profile but only an empty line.

How can i find the error in the profile?

FusionPBX 5.0.1
freeswitch-1.10.7.-release
Debian GNU/Linux 11 running in a VM under Vmware EXSi.
Let me know if you need any more info, i am new to this list.

Thanks for any help,

-Heinrich


Code:
sofia status
Name            Type        Data                                    State    Action
external        Profile    sip:mod_sofia@192.168.178.41:5080                RUNNING (0)     
internal-ipv6    Profile    sip:mod_sofia@[2a03:4000:xxxx:yyyy:1000::41]:5060    RUNNING (0)     
internal        Profile    sip:mod_sofia@192.168.178.41:5060                RUNNING (0)     
Status
UP 0 years, 0 days, 0 hours, 19 minutes, 6 seconds, 667 milliseconds, 180 microseconds
FreeSWITCH (Version 1.10.7 -release 64bit) is ready
0 session(s) since startup
0 session(s) - peak 0, last 5min 0
0 session(s) per Sec out of max 30, peak 0, last 5min 0
1000 session(s) max
min idle cpu 0.00/100.00
Current Stack Size/Max 240K/8192K
 
Check the port number associated with external profile. It might be 5060, because external_sip_port variable is not assigned. I found out by setting internal ipv6 profile to disabled.
 
Go into fs_cli and do a: reload mod_sofia

That should show you the error within that, it will be pretty verbose.
 
Thank you for your replies. Setting sip ports to 5080 and 5081 (tls) fixed this. I wonder why this is done automatically for IP4 but not for IP6.
Also thanks for the hint about fs_cli. I did not know about this.
 
I have the same error, reload mod_sofia and have the next errors, do you have the problems??

2022-11-27 17:59:00.038152 100.00% [DEBUG] sofia.c:3369 Set params for internal
2022-11-27 17:59:00.038152 100.00% [DEBUG] sofia.c:3416 Activated db for internal
2022-11-27 17:59:00.038152 100.00% [ERR] sofia.c:3296 Error Creating SIP UA for profile: internal-ipv6 (sip:mod_sofia@[::1]:5060;transport=udp,tcp) ATTEMPT 1 (RETRY IN 5 SEC)
2022-11-27 17:59:00.038152 100.00% [DEBUG] sofia.c:3454 Starting thread for external
2022-11-27 17:59:00.038152 100.00% [DEBUG] sofia.c:3046 Launching worker thread for external
2022-11-27 17:59:00.038152 100.00% [INFO] switch_core_sqldb.c:1840 sofia:internal Starting SQL thread.
2022-11-27 17:59:00.038152 100.00% [DEBUG] sofia.c:3454 Starting thread for external-ipv6
2022-11-27 17:59:00.038152 100.00% [DEBUG] sofia.c:3046 Launching worker thread for external-ipv6
2022-11-27 17:59:00.038152 100.00% [DEBUG] sofia.c:3454 Starting thread for internal
2022-11-27 17:59:00.038152 100.00% [DEBUG] sofia.c:3046 Launching worker thread for internal
2022-11-27 17:59:01.538176 99.93% [CONSOLE] switch_loadable_module.c:1768 Successfully Loaded [mod_sofia]
2022-11-27 17:59:01.538176 99.93% [NOTICE] switch_loadable_module.c:172 Adding Endpoint 'sofia'
2022-11-27 17:59:01.538176 99.93% [NOTICE] switch_loadable_module.c:172 Adding Endpoint 'rtp'
2022-11-27 17:59:01.538176 99.93% [NOTICE] switch_loadable_module.c:329 Adding Application 'sofia_sla'
2022-11-27 17:59:01.538176 99.93% [NOTICE] switch_loadable_module.c:329 Adding Application 'sofia_stir_shaken_vs'
2022-11-27 17:59:01.538176 99.93% [NOTICE] switch_loadable_module.c:389 Adding API Function 'sofia'
2022-11-27 17:59:01.538176 99.93% [NOTICE] switch_loadable_module.c:389 Adding API Function 'sofia_gateway_data'
2022-11-27 17:59:01.538176 99.93% [NOTICE] switch_loadable_module.c:389 Adding API Function 'sofia_username_of'
2022-11-27 17:59:01.538176 99.93% [NOTICE] switch_loadable_module.c:389 Adding API Function 'sofia_contact'
2022-11-27 17:59:01.538176 99.93% [NOTICE] switch_loadable_module.c:389 Adding API Function 'sofia_count_reg'
2022-11-27 17:59:01.538176 99.93% [NOTICE] switch_loadable_module.c:389 Adding API Function 'sofia_dig'
2022-11-27 17:59:01.538176 99.93% [NOTICE] switch_loadable_module.c:389 Adding API Function 'sofia_presence_data'
2022-11-27 17:59:01.538176 99.93% [NOTICE] switch_loadable_module.c:419 Adding JSON API Function 'sofia.status'
2022-11-27 17:59:01.538176 99.93% [NOTICE] switch_loadable_module.c:419 Adding JSON API Function 'sofia.status.info'
2022-11-27 17:59:01.538176 99.93% [NOTICE] switch_loadable_module.c:621 Adding Chat interface 'sip'
2022-11-27 17:59:01.538176 99.93% [NOTICE] switch_loadable_module.c:681 Adding Management interface 'mod_sofia' OID[.1.3.6.1.4.1.27880.1001]
2022-11-27 17:59:05.038177 99.90% [ERR] sofia.c:3296 Error Creating SIP UA for profile: internal-ipv6 (sip:mod_sofia@[::1]:5060;transport=udp,tcp) ATTEMPT 2 (RETRY IN 5 SEC)
2022-11-27 17:59:10.038179 99.90% [ERR] sofia.c:3296 Error Creating SIP UA for profile: internal-ipv6 (sip:mod_sofia@[::1]:5060;transport=udp,tcp) ATTEMPT 3 (RETRY IN 5 SEC)
2022-11-27 17:59:10.038179 99.90% [ERR] sofia.c:3307 Error Creating SIP UA for profile: internal-ipv6 (sip:mod_sofia@[::1]:5060;transport=udp,tcp)
The likely causes for this are:

1) Another application is already listening on the specified address.
2) The IP the profile is attempting to bind to is not local to this system.
2022-11-27 17:59:10.038179 99.90% [DEBUG] sofia.c:3576 Write lock internal-ipv6
2022-11-27 17:59:10.038179 99.90% [DEBUG] sofia.c:3589 Write unlock internal-ipv6
 
Thank you for your replies. Setting sip ports to 5080 and 5081 (tls) fixed this. I wonder why this is done automatically for IP4 but not for IP6.
Also thanks for the hint about fs_cli. I did not know about this.
how did u do that can u help me out i am facing the same problem brother
 
Status
Not open for further replies.