Unable to receive calls - outbound okay
Done. System is responding the same way as before. Asterisk never sees the inbound trunk. It is not until if fails over to the 2nd trunk that the system responds at all.
View ArticleUnable to receive calls - outbound okay
I don't believe it will detect your localnet(s) just your "externaladdress" you need to do that yourself if you are NATting generally. grep ip addr|grep inet will get you on the right track. Maybe you...
View ArticleClik here to view.
Call full external Number from Intern
Hi! venice89: it works for me because I only have to check if the Number starts with something like this:+4978455488 <== All numbers which are starting with +4978455488 are numbers of the location...
View ArticleShut Down Free PBX
Then I recommend that you follow one of the methods described in the link I gave ( I suggest the modprobe one)....
View ArticleUnable to receive calls - outbound okay
Hi Mike, Send again a log of an inbound call. Did you change the NAT settings? Thank you, Daniel FriedmanTrixton LTD.
View ArticleUpgrade FreePBX to version 13
Had the same thing happen after upgrading FreePBX distro to FreePBX 13.Disabled Sangoma MCU module and it's fine.
View ArticleClik here to view.
FreePBX 13 Upgrade Backup Module fails
Just upgraded to FreePBX 13 and then upgrade of backup module from a GUI.This is the screen I got afterwards: Pasted image1273x609 65.9 KB
View ArticleUnable to receive calls - outbound okay
I think I NAT okay. Here are the SIP settings. accounting-services*CLI> sip show settings Global Settings: UDP Bindaddress: 0.0.0.0:5060 TCP SIP Bindaddress: Disabled TLS SIP Bindaddress: Disabled...
View ArticleUnable to receive calls - outbound okay
Hi, The NAT is still on static. It should be public. Fix it. you do not have an inbound route to your DID and that is why it goes to the Any route. There is a cli source lookup on your inbound trunks...
View ArticlePlease help on error messages / AMPORTAL RESTART
Hi, Using FreePBX 12.0.76.2, when I send an AMPORTAL RESTART command, I get two errors: Stopping Restapps daemon > ucp-server@ stop /var/www/html/admin/modules/ucpnode/node >...
View ArticleA security problem: false calls from within the system
Hi, You need to search for the script that inserts this context. Try to run this command in your Linux console: fgrep -R thankuohoh /etc I have a feeling that you are using Elastix and it suppose to...
View ArticleDial extension goes directly to voicemail
Hi, Set the sendrpid=pai in your extensions. Thank you, Daniel FriedmanTrixton LTD.
View ArticleA security problem: false calls from within the system
Thank you for your advice. As I stated in my post I DO NOT use Elastix nor do I have a2billing installed. It is a FreePBX distro. I'm quite aware of the holes existing in Elastix and seldom use it for...
View ArticleA security problem: false calls from within the system
Likely you are using an unpatched "asterisk recordings interface". This was one of the reasons we do module signing now. Note you likely have a system call in some random file that calls every time...
View ArticleA security problem: false calls from within the system
I do use FreePBX 12. Patched long time ago the ARI
View ArticleA security problem: false calls from within the system
do you have any tampered file warnings? try amportal a ma refreshsignatures
View ArticleA security problem: false calls from within the system
Hi, You should had run my command fgrep -R thankuohoh /etc/ or fgrep -R thankuohoh /var/www/ to see where is that file that is inserting this context.I am quite sure that you have a php file that is...
View ArticleA security problem: false calls from within the system
These hacks usually base64 encode things or use a url to pull a script to tmp and run it. grep won't find it.
View ArticleA security problem: false calls from within the system
Hi, It is fgrep not grep. There is a file that is running every night. I would also check the cron library to verify that there is not a new daily cron that is running it. Thank you, Daniel...
View ArticleA security problem: false calls from within the system
wrong again. They compromise a file then they call that file remotely it is not cron.
View Article