I installed Fusionpbx on a new Debian 10 (x86) system a bit ago and did an Advanced/Upgrade of the Source, Schema and App defaults. Then I attempted to add a couple of phones to the new system. They both were working fine on an older version of FB. The extensions I added are 1004 and 1010.
The only fields I used are Extension, Password, VM Password. The reset were left as default. Enabled is true and both the domain and context are the same. There is nothing in the log that would indicate the registration was attempted. The only thing out of the ordinary is a second domain I attempted to delete. It said it was deleted but Freeswitch is still compaining. Here are the last few lines of the log:
I attempted to use the sofia profile internal siptrace on command but it failed with
Invalid Profile [internal]
So I went over to Advanced/Sip Profiles and everything looks fine. 4 profiles all Enabled.
But when I go to Status/SIP Status I only see the external-ipv6 and internal-ipv6 profiles running. If I try to start the internal profile I get:
It looks like I didn't get the domain removed. I'm guessing it left Fustionpbx but FS still thinks it is there.
How can i convince FS to lose the domain? I searched all the config files I could find for that IP address to no avail. I'm guessing it's somewhere in the database but I have no idea how to exorcise it.
Thanks,
Jim.
The only fields I used are Extension, Password, VM Password. The reset were left as default. Enabled is true and both the domain and context are the same. There is nothing in the log that would indicate the registration was attempted. The only thing out of the ordinary is a second domain I attempted to delete. It said it was deleted but Freeswitch is still compaining. Here are the last few lines of the log:
2020-09-30 09:16:31.110393 [NOTICE] switch_utils.c:658 Adding 192.168.0.0/16 (allow) [] to list nat.auto
2020-09-30 09:16:31.110393 [NOTICE] switch_utils.c:658 Adding 100.64.0.0/10 (allow) [] to list nat.auto
2020-09-30 09:16:31.110393 [NOTICE] switch_core.c:1539 Created ip list loopback.auto default (deny)
2020-09-30 09:16:31.110393 [NOTICE] switch_utils.c:658 Adding 127.0.0.0/8 (allow) [] to list loopback.auto
2020-09-30 09:16:31.110393 [NOTICE] switch_utils.c:658 Adding ::1/128 (allow) [] to list loopback.auto
2020-09-30 09:16:31.110393 [NOTICE] switch_core.c:1546 Created ip list localnet.auto default (deny)
2020-09-30 09:16:31.110393 [NOTICE] switch_core.c:1549 Adding 192.168.2.25/255.255.255.0 (allow) to list localnet.auto
2020-09-30 09:16:31.110393 [NOTICE] switch_core.c:1574 Created ip list domains default (deny)
2020-09-30 09:16:31.110393 [INFO] mod_enum.c:884 ENUM Reloaded
2020-09-30 09:16:31.110393 [INFO] switch_time.c:1430 Timezone reloaded 530 definitions
2020-09-30 09:16:31.110393 [WARNING] switch_core.c:1627 Cannot locate domain 192.168.2.34
2020-09-30 09:16:31.110393 [NOTICE] switch_core.c:1574 Created ip list lan default (allow)
2020-09-30 09:16:31.110393 [NOTICE] switch_utils.c:658 Adding 192.168.42.42/32 (allow) [] to list lan
I attempted to use the sofia profile internal siptrace on command but it failed with
Invalid Profile [internal]
So I went over to Advanced/Sip Profiles and everything looks fine. 4 profiles all Enabled.
But when I go to Status/SIP Status I only see the external-ipv6 and internal-ipv6 profiles running. If I try to start the internal profile I get:
2020-09-30 09:37:06.290357 [DEBUG] sofia.c:4628 dtmf-type [rfc2833]
2020-09-30 09:37:06.290357 [DEBUG] sofia.c:4628 dtmf-duration [2000]
2020-09-30 09:37:06.290357 [INFO] sofia.c:6028 Setting MAX Auth Validity to 0 Attempts
2020-09-30 09:37:06.290357 [NOTICE] sofia.c:6195 Started Profile internal [sofia_reg_internal]
2020-09-30 09:37:06.290357 [DEBUG] sofia.c:3158 Creating agent for internal
2020-09-30 09:37:06.290357 [INFO] mod_enum.c:884 ENUM Reloaded
2020-09-30 09:37:06.290357 [ERR] sofia.c:3259 Error Creating SIP UA for profile: internal (sip:mod_sofia@192.168.2.34:5060;maddr=192.168.2.34;transport=udp,tcp) ATTEMPT 1 (RETRY IN 5 SEC)
2020-09-30 09:37:06.290357 [INFO] switch_time.c:1430 Timezone reloaded 530 definitions
2020-09-30 09:37:11.290407 [ERR] sofia.c:3259 Error Creating SIP UA for profile: internal (sip:mod_sofia@192.168.2.34:5060;maddr=192.168.2.34;transport=udp,tcp) ATTEMPT 2 (RETRY IN 5 SEC)
2020-09-30 09:37:16.290404 [ERR] sofia.c:3259 Error Creating SIP UA for profile: internal (sip:mod_sofia@192.168.2.34:5060;maddr=192.168.2.34;transport=udp,tcp) ATTEMPT 3 (RETRY IN 5 SEC)
2020-09-30 09:37:16.290404 [ERR] sofia.c:3269 Error Creating SIP UA for profile: internal (sip:mod_sofia@192.168.2.34:5060;maddr=192.168.2.34;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.
It looks like I didn't get the domain removed. I'm guessing it left Fustionpbx but FS still thinks it is there.
How can i convince FS to lose the domain? I searched all the config files I could find for that IP address to no avail. I'm guessing it's somewhere in the database but I have no idea how to exorcise it.
Thanks,
Jim.