Solved Mikrotik SIP ALG

Status
Not open for further replies.

davidm85

Customer
Joined
Jan 15, 2018
Messages
14
Reaction score
3
I recently installed a new router a Mikrotik Hex.

When I first ran the 'firewall checker' sip alg was not detected.
But now it states 'failed', although the sip alg is deactivated on the router.

What could cause this problem?

thanks
 
I had intermittent test issues with the Firewall Tester using a Mikrotik. My system works just fine. I do see they do not have an outbound SNAT on the Mikrotik instructions but I have found my system to be more stable with it.
 
thx for the replies.

I've checked all the setting from the 3CX doc but everything seems fine.

The error about the sip alg test keeps comming up.

the strange part is that with the first run, everything was ok
 
thx @Brian Cross but when I run the tool, I get an access denied message (run the tool as administrator)

upload_2018-1-31_9-0-26.png
 
Hmm local firewall on or something?
 
the windows firewall is off,
and the mikrotek router has factory settings, with just the 3CX settings
 
I
thx @Brian Cross but when I run the tool, I get an access denied message (run the tool as administrator)
T could be that it can't bind to port 5060 because something else is using it. If you ran this on the 3CX Server, for sure 5060 is being used by 3CX. Stop all 3CX services and try running this tool again (as admin), maybe this helps...
 
Hi,

this was indeed the problem, when i shutdown the services and disable the 5060 udp and tcp rule, the test works.

I also had a conversation with one of your colleagues, and the sip alg test works in 3CX when i disable the 5060 - udp rule in the router. Strange behavior, because all settings are taken from the 3CX mikrotik guide
 
Makes sense I usually run it on a workstation on the network not on off the 3cx server. So what was the verdict SIP ALG off?
 
With the help of the mikrotik forum I managed to solve the issue, I had to add a setting to the router firewall settings for 3CX protocols.
I had to set incoming interface= wan interface.
 
Glad to see the issue has been resolved and thank you for updating the thread with your solution
 
  • Like
Reactions: mlugmayr
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,881
Messages
589,535
Members
164,739
Latest member
wmlcon