Thanks David....Been wondering why my SIP helper never seemed to work; just reboot the Mikrotik! Recently installed a Cisco SPA8000 for testing on PBX loop start lines. Found phantom ringing that turned out to be a hacker. For some reason, restricting the IP inside the SPA8000 wasn't working, so I placed it inside my network. One way audio led me to this video. Now I've used the firewall to block unwanted SIP messages. Thanks again
I see this is an older presentation. And hopefully i can get an answer to this. I manage a Broadsoft where the SIP server is in the public domain. We must disable any alg for our calls to properly process. As in the presentation, a broadsoft does route all calls to the layer 3 addresses and relies on the layer 7 to keep the private addresses in the messages. We ran into an issue on MikroTik where we had the SIP setting disabled, but were ablet o witness ALG changes still in the headers. I think they were port related, not IP addresses. Is there any movement on allowing the MikroTik to pass this traffic without modifying it? We are using NAT Masquerade for the inside traffic. Thank you
Hey david I'm unable to understand one simple thing. When NAT already exists who can change the private to public IP's, then why need a SIP ALG to do the exactly same thing?
Thank you Mikrotik staff for the opportunity for the give this presentation. Keep up the good work!
As a former Avaya Support Engineer I felt Offended with your comments.. But the presentation was very good.. 👍 Very well explained. 😁
Hi David, this is great, thank you very much for this knowledge! I've learned about sip ALG!
Hi David. I just put into practice your lesson. I just works as a swiss watch. Thanks you!!!
Thanks David....Been wondering why my SIP helper never seemed to work; just reboot the Mikrotik! Recently installed a Cisco SPA8000 for testing on PBX loop start lines. Found phantom ringing that turned out to be a hacker. For some reason, restricting the IP inside the SPA8000 wasn't working, so I placed it inside my network. One way audio led me to this video. Now I've used the firewall to block unwanted SIP messages. Thanks again
Thanks for this.. Very informative... !!
mantap pak David Attias!!..easy to understand, and thank you for sharing video and presentation in pdf.
This help me a lot, Thanks for sharing 😘
Great and simple explanation. Thank you.
great presentation. Congratulations!
Thanks a lot David.
This presentation is pretty cool!
Bad russian accent brah! From Moscow with love.
I see this is an older presentation. And hopefully i can get an answer to this. I manage a Broadsoft where the SIP server is in the public domain. We must disable any alg for our calls to properly process. As in the presentation, a broadsoft does route all calls to the layer 3 addresses and relies on the layer 7 to keep the private addresses in the messages. We ran into an issue on MikroTik where we had the SIP setting disabled, but were ablet o witness ALG changes still in the headers. I think they were port related, not IP addresses. Is there any movement on allowing the MikroTik to pass this traffic without modifying it? We are using NAT Masquerade for the inside traffic.
Thank you
Thank you!
Hey david I'm unable to understand one simple thing. When NAT already exists who can change the private to public IP's, then why need a SIP ALG to do the exactly same thing?
ALG manipulates the layer 7 protocol data (mostly IP announcements) which is what the SIP nodes are programmed to use for instructions
Thanks Dimitri :)
To Difficult for me! Do not understand!