Hello @urbanet ,
This is freeswitch issue we have checked with developers, but it will take time for them to check what is the issue with freeswitch as its not related to ASTPP.
Thanks,
Palak.
Hello @urbanet ,
This is freeswitch issue we have checked with developers, but it will take time for them to check what is the issue with freeswitch as its not related to ASTPP.
Thanks,
Palak.
Is not true because I have a FreeSWITCH same linux distribution and same version and works without this issue.
Dear @PALAK, let me agree with @SOCIAL; the issue appears when ASTPP receives some registration(or re-registration) from some SIP device directly, AND WHEN THE ORIGINATING IP ADDRESS IS NOT IN THE LIST OF ALLOWED IP´s (under <Accounts/Customers/SIP Devices>); if the originating IP is in the list, then the issue does NOT occur…so, the issue depends on how ASTPP is managing permissions or registrations…
Maybe you could suggest: “ok, add the IP to the list and the problem is solved”… sadly, no…because I have multiple SIP endpoints originating from the same IP(my freePBX); adding the only freePBX IP to the list, avoids individual identification of each endpoint…ASTPP charges calls to only one account, instead recognize each endpoint.
(i hope my explaination clarifies the issue… thanks!)
My particular problem with this issue
Hello @urbanet ,
Can you please remove core.db of freeswitch then restart freeswitch. Then please monitor it.
Thanks.
Hi @PALAK. ok, done…
Hello @urbanet
can you please log this over → https://jira.astppbilling.org/ and share the details so we can check the error.
Thanks.
@urbanet I have the same issue using freeswitch repo or compiling from sources so the problem is ASTPP. My personal opinion: leave this project. This is only one of the problems ASTPP has. Regards
@urbanet if you can share your ssh information with us then go ahead and share it on samir.doshi@inextrix.com, we would like to dig into that. We are not able to reproduce that issue in our environment.
@smrdoshi really, THANKS.!
email with credentials has been sent to you.
Details, network diagram and a brief of our infrastructure sent too.
I´m very pending of your connection.
Regards.
Hello @urbanet,
This is to update you that we have successfully connected to your server and we also monitor the fs_cli logs but we couldn’t observe such error while we are monitoring it. We have also tried to register the sip device and it was failed to connect and not received any logs in fs_cli. To reproduce the issue we need your support. Please contact my skype id below :
Hello @urbanet,
Thank you for connecting and cooperating to regenerate the error " [ERR] switch_utils.c:4584 Unknown message digest md5". We checked together and fixed the error and you also have confirmed from your end.
Here is summary of the steps we performed to overcome an issue:
Step 1: yum update openssl-devel
Step 2: cd /var/lib/freeswitch/db/ and take backup of core.db
Step 3: rm -rf core.db
Step 4: systemctl restart freeswitch
Step 5: systemctl restart php-fpm
Step 6: Go to fs_cli and run reloadacl and reload mod_sofia
@dhruvil.panchal please receive my “THANKS” for your support.
YES, the problem was solved.
ASTPP is going GREAT now.
I still have some questions; (still researching ASTPP)
PS: @SOCIAL, here the solution for you.
Hello good day, i tried, follow the steps to solve the issue, but not work, on step 1, don’t make any update, so when end all steps, don’t working, what version of spenssl must to have? . Thank you for your help.
Hi @imendezj
I have bad news for you and for my virtual friend Dhruvil …
Steps and procedure described by @dhruvil.panchal were very effective when he applied the procedure…
some days later, the issue re-appeared…“okay” (i told myself)…“just let´s run again the @dhruvil.panchal procedure and no problem…”
…yes…the procedure solved the issue…for three days…and again…and again…and again…
I don´t know if this has relation with the OpenSSL version…but the issue re-appears …
…sorry @dhruvil.panchal
Hi,
I think is a hashing password problem between ASTPP and FreeSWITCH. In pure FreeSWITCH NEVER this happens.
Regards
Hello @urbanet,
Please check and do below steps:
Step 1: Check mod_hash module: Make sure that the mod_hash module is loaded and configured properly in FreeSWITCH. You may want to check the “/etc/freeswitch/autoload_configs/modules.conf.xml” file to ensure that the module is loaded, and check its configuration in the “/etc/freeswitch/autoload_configs/hash.conf.xml” file.
Step 2: Restart FreeSWITCH: After making any changes to the software or configuration, restart FreeSWITCH to ensure that the changes take effect.
Hi @dhruvil.panchal thanks for following-up…
<!-- Required to run astpp -->
<load module="mod_xml_curl"/>
<load module="mod_json_cdr"/>
<load module="mod_hash"/>
<!-- <load module="mod_nibblebill"/> -->
<!--<load module="mod_xml_cdr"/>-->
…
…
<configuration name="hash.conf" description="Hash Configuration">
<remotes>
<!-- List of hosts from where to pull usage data -->
<!-- <remote name="Test1" host="10.0.0.10" port="8021" password="ClueCon" interval="1000" /> -->
</remotes>
</configuration>
I am also having this issue for quite sometimes. It looks like it may be a FreeSwitch issue & addressed in this issue, as well as closed after this pull-request.
What is the optimal way to incorporate the latest FreeSwitch code & test whether it fixes the issue in the ASTPP v6.0? I’ll appreciate any other suggestion to try, otherwise I may need to revert to an older version of ASTPP.
NB: My versions of modules.conf.xml
& hash.conf.xml
look exactly similar as @urbanet posted in the last replies.