ictinnovations / ictfax

Open Source Fax Server Software supporting inbound and outbound faxing. ICTFAX can be used in following faxing scenarios Web to fax, Fax to Web or Online Fax Email to fax and fax to email ATA / Extensions to send and receive faxes via Fax machine using internet REST based Fax API’s to integrate with third party applications and automate business process G.711 based Fax Origination / Termination / Gateway T.38 based Fax Origination / Termination PSTN based Fax Origination / Termination / Gateway
http://www.ictfax.org
GNU General Public License v3.0
173 stars 60 forks source link

Upon restart of Freeswitch: sofia.c:3146 Error Creating SIP UA for profile #23

Closed herrep closed 5 years ago

herrep commented 5 years ago

After having configured a provider in ictfax and restarting freeswitch, freeswitch reports upon startup:

2019-06-20 12:40:57.387645 [ERR] sofia.c:3146 Error Creating SIP UA for profile: external-ipv6 (sip:mod_sofia@[::1]:5080;transport=udp,tcp) ATTEMPT 2 (RETRY IN 5 SEC) 2019-06-20 12:40:57.387645 [ERR] sofia.c:3146 Error Creating SIP UA for profile: internal-ipv6 (sip:mod_sofia@[::1]:5060;transport=udp,tcp) ATTEMPT 2 (RETRY IN 5 SEC) 2019-06-20 12:41:02.407612 [ERR] sofia.c:3146 Error Creating SIP UA for profile: external-ipv6 (sip:mod_sofia@[::1]:5080;transport=udp,tcp) ATTEMPT 3 (RETRY IN 5 SEC) 2019-06-20 12:41:02.407612 [ERR] sofia.c:3156 Error Creating SIP UA for profile: external-ipv6 (sip:mod_sofia@[::1]:5080;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. 2019-06-20 12:41:02.407612 [ERR] sofia.c:3146 Error Creating SIP UA for profile: internal-ipv6 (sip:mod_sofia@[::1]:5060;transport=udp,tcp) ATTEMPT 3 (RETRY IN 5 SEC) 2019-06-20 12:41:02.407612 [ERR] sofia.c:3156 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.

Besides, I also received the following errors during startup: 2019-06-20 12:40:53.885229 [CRIT] switch_loadable_module.c:1522 Error Loading module /usr/lib64/freeswitch/mod/mod_rtc.so **/usr/lib64/freeswitch/mod/mod_rtc.so: cannot open shared object file: No such file or directory** 2019-06-20 12:40:53.885283 [CRIT] switch_loadable_module.c:1522 Error Loading module /usr/lib64/freeswitch/mod/mod_verto.so **/usr/lib64/freeswitch/mod/mod_verto.so: cannot open shared object file: No such file or directory** 2019-06-20 12:40:54.507221 [CRIT] switch_loadable_module.c:1522 Error Loading module /usr/lib64/freeswitch/mod/mod_dialplan_asterisk.so **/usr/lib64/freeswitch/mod/mod_dialplan_asterisk.so: cannot open shared object file: No such file or directory** 2019-06-20 12:40:54.533554 [CRIT] switch_loadable_module.c:1522 Error Loading module /usr/lib64/freeswitch/mod/mod_b64.so **/usr/lib64/freeswitch/mod/mod_b64.so: cannot open shared object file: No such file or directory** 2019-06-20 12:40:54.533611 [CRIT] switch_loadable_module.c:1522 Error Loading module /usr/lib64/freeswitch/mod/mod_opus.so **/usr/lib64/freeswitch/mod/mod_opus.so: cannot open shared object file: No such file or directory** 2019-06-20 12:40:54.535465 [INFO] mod_sndfile.c:388 2019-06-20 12:40:54.537589 [CRIT] switch_loadable_module.c:1522 Error Loading module /usr/lib64/freeswitch/mod/mod_png.so **/usr/lib64/freeswitch/mod/mod_png.so: cannot open shared object file: No such file or directory** 2019-06-20 12:40:54.586700 [CRIT] switch_loadable_module.c:1522 Error Loading module /usr/lib64/freeswitch/mod/mod_flite.so **/usr/lib64/libflite.so.1: undefined symbol: snd_pcm_hw_params_any**

All in all, the result is that registrations to my SIP provider do not work.

plochu commented 5 years ago

Are you sure that Freeswitch service is running?

herrep commented 5 years ago

I posted log files from freeswitch above. Why do you believe that freeswitch is not running, when freeswitch drops messages in its own log file? This is the reason why I ask for support: Freeswitch runs, but reports errors as listed above.

herrep commented 5 years ago

This problem is caused by a failed binding based on IPv6. After re-configuring freeswitch to use IPv4 this problem is gone.

jlmendo11 commented 4 years ago

I LET THIS HERE FOR PEOPLE WHO NEED HELP: The way I solved this problem was by removing all the files and directories ended in "ipv6" in the "sip_profiles" directory (mine was at /etc/freeswitch/sip_profiles):

rm -rf /etc/freeswitch/sip_profiles/external-ipv6 rm -f /etc/freeswitch/sip_profiles/external-ipv6.xml rm -f /etc/freeswitch/sip_profiles/internal-ipv6.xml