Hi, I would like to propose a feature request on RouterOS v7.

In Ci*** IOS they have Ci*** Unified Communications Manager Express, looks like pretty simple, but mostly they're using SCCP, but since most general VoIP they use SIP, why not try to fork Asterisk into RouterOS v7?

Looks like simple, won't burden router's resource, adds great feature to the RouterBOARD itself, so offices can have VoIP capability only with RouterBOARD without having to have separate Asterisk or FreePBX server.

I hope my feature request would be implemented and makes MikroTik the best router in the world!

In Ci*** IOS they have Ci*** Unified Communications Manager Express, looks like pretty simple, but mostly they're using SCCP, but since most general VoIP they use SIP, why not try to fork Asterisk into RouterOS v7?

Please NOT asterisk. If SIP would get to be added into RouterOS let it be at least FreeSwitch.

This seems unnecessary, a Router shouldn't try and run all these services, as it may affect performance of its core functionality.

Additionally, when these extra features are added they rarely function as well as a stand alone product with proper support and development.

Hi,
+1 for VoIP support but not for Asterisk.
For that, you can use metarouter and load OpenWRT on it and install Asterisk on OpenWRT in metarouter; Asterisk hereby take your RouterBOARD will be activated.

This seems unnecessary, a Router shouldn't try and run all these services, as it may affect performance of its core functionality.

Additionally, when these extra features are added they rarely function as well as a stand alone product with proper support and development.

totally agree with you there are small and cheap appliances for voip

one example

http://www.elastix.com/portfolio-item/microucs/

i prefer mikrotik to focus efforts on networking, not another functions

I am VoIP engineer and agree with you. It is bad idea.
It is unnecessary to add VoIP services in MT, except to improve this traffic.

VoIP service for one way, and routing/filtering on another way.

Not sure about having an actual PBX built into RouterOS [because you can already do whatever you want with metarouters], but more options on the SIP ALG would be useful.

simple SIPproxy/RTPproxy totally needed, it would boost MikroTik sales numbers by lower implemetation barrier as configure SIP through NAT is tricky and SIPproxy could replace NAT traversal

since your automatic SIP-ALG does not works well in most cases!

simple SIPproxy/RTPproxy totally needed, it would boost MikroTik sales numbers by lower implemetation barrier as configure SIP through NAT is tricky and SIPproxy could replace NAT traversal

since your automatic SIP-ALG does not works well in most cases!

Cisco SCCP RTP / SIP proxy support is really needed if RB has any hope of entering into the North American Mid-Large market, today we can't even consider using RB as a VPN hardware client for the 1's of users we have. Honestly, RB would be perfect as it offers an outstanding value, but since we can't easily implement support for Cisco SCCP VoIP endpoints using RB as a hardware VPN end point (SSTP/IPSEC/OpenVPN) and standard Cisco SCCP enabled handsets.

I'm not sure why Mikrotik should implement an ALG for SCCP protocol since Cisco has moved their SPA series phones and most of their other devices to SIP protocol. SIP is the accepted standard for a while. SCCP is slowly being retired. I use Mikrotik's implementation of ALG and it works fine for me. From what I've seen Mikrotik does not seem get involved with conforming to one vendor's implementation of anything, I agree with them on that.

LLDP-Med would be a nice addition for Voip, so that the voice VLAN can be automatically detected by phones. This is a switch feature.

This is true for example for Mitel - Aastra phones that know how to get the voice vlan from LLDP. Probably other brands today have LLDP-Med support.

Other phones need to get it through DHCP using the untagged VLAN, and switch to the tagged VLAN. This is a more complicated setup. Technically LLDP-Med is the best solution. The only thing you have to do is to declare the VLAN as a voice VLAN on each switch. After this the voice VLAN is announced through LLDP-Med to phones, that will switch and listen to the right tagged VLAN.

Fast and efficient. Using a tagged VLAN for phones is mandatory as soon as you want to use the second port on phones to connect computers to a separate VLAN.

LLDP-Med is available on HP Procurve / Aruba switches, probably other brands like Netgear. I did use it successfully on Procurve switches.

I just gave a presentation on SIP ALG at the Mikrotik MUM in Denver Colorado 2017 explaining everything about SIP ALG in RouterOS
watch here:
https://youtu.be/tM7wyKdnIKA