Hello,
what I would like for next RouterOS releases is:
- SIP client
To offer VoIP services to my Customers right know I have to use ATA (Linksys) placed behind MT CPEs. In this way, ATA works as router and MT CPE in bridge, so I cannot use all RouterOS capabilities: customer's network is behing ATA that works as router. With this situation, I'm moving to cheaper CPEs (UBNT Nanostation) because there is no sense to pay more money for MT CPE without having the possibility to use its features. What I would like to have is a CPE with a SIP client embedded and a PoE with a RJ11 port, to connect normal telephone to it.
-web interface
a web interface that allows guest login for limited operations: lan management, dhcp settings, dest-nat,... In this way customers might do normal operations on CPE like they can do with a normal ADSL router on the market

Awating good news from MT staff...
Rgds

Hello,
what I would like for next RouterOS releases is:
- SIP client
-web interface
Awating good news from MT staff...
Rgds

I agree with both!

Also it would be nice to have routerboard with rj-11 port, to use it as clients cpe

forget the sip client, how about a sip proxy, thats even better.

I've opened support request about any kind of telephony in MT and response was 'not planned'. It's sad thing.

Right now, i see that for V.35 or multiple E1/T1 connections i would use some old Ci*O or A*d-T*n router.
Also for SIP gateways for homes, normal ATA.

There is VERY BIG market for installations with 1-2 FXS ports on CPE, maybe a microPCI card with add on?
When you offer Internet by wireless customers ask for phones, and when it gets closed in CPE on the roof it's OK, if it need additional devices it costs more, it's not acceptable.

There was (still IS?) support for Linux Telephony project in MicroTik, but i see that this project is very obsolete, examples are for H323 and only for interconnecting with Ci*O and not very usable for me.

Support for SIP client and 1-2 FXS ports would be very much apprieciated.

SIP Helper needs to be fixed before anything else imho.

All VoIP features must be usable, one by one. Maybe SIP first - yes.

I vote for making router and wireless features better - stay out of phone business

Having said that... if it worked good then I suppose I'd use it but I'd rather the MT guys focused on having the best most stable router. They won't be done with this job until my upstreams quite using cisco and juniper and start using MT. There is a reason they don't and it doesn't have anything to do with telephony features....

Scott