Is SER a SIP server reserved for professionals? Is the configuration language of ser.cfg so complex that SIP novices should stay away? Should we post a sign at the entrance: “Beginners, please go to”?

These kind of questions cropped up in a serdev thread that started out with how to handle user locations for large scale deployments.

The thousands of subscribers on serusers, who are they? How do they use SER? What do they miss?

The reality is that we don’t know, and it’s difficult to find out. A poll will only reveal what a handful of people say.

So, it basically boils down to self-selection, those participating in discussions on serdev and serusers should be allowed to decide. Lurkers, beware, unless you speak, SER may be something different tomorrow!

IMO, we need to decide how broad we should go in targeting the SIP community. And this should also be influenced by where SIP people perceive SER to be. No way SER is going to be positioned as SIP PBX, that position has been taken by Asterisk. On the other hand, I have seen Asterisk installations that really shouldn’t have been done on Asterisk.

I think most people realize that SER is a workhorse for SIP proxying and routing, as well as a very efficient registrar. It COULD also be a very powerful front-end for application servers of various kinds. In fact, it already is that front-end for SER Media Server (SEMS). And it has formed the basis for the Fraunhofer FOKUS OpenIMS project. These observations may point to SER’s natural position.

Leave a Reply

Post Navigation