A MjSip-based server implementation is also available. It can be used as Registrar, Redirect, Stateless Proxy or Stateful Proxy.

The main features of the MjSip Server are:

• it is easily configurable via a simple text-based file,
• it is fully compliant with RFC 2631 and successors, moreover it is backward compatible with the previous RFC 2543 standard (e.g. it support both loose and strict routing, different expires field formats, etc.),
• it can act as Registrar, and/or Proxy, and/or Redirect server,
• both a stateless or stateful implementations are available,
• it include a simple java-based local database, used for maintain user contacts and/or authentcation credentials,
• it implements standard Digest authentication (when selected),
• it can easily be interfaced with external LDAP repository or MySQL database (a example of such interfaces will be soon available),
• it can fork calls to more than one contact URLs (it supports multiple registrations),
• it is possible to select different registration policies (register only pre-registered/known users, or also new users),
• it is possible to select different proxying policies (proxy only calls coming from registered users and/or directed to registered users, or from/to all users),
• it can authoritatively administrate multiple domanis,
• etc.

The MjServer can be easily configured by means of a text-based configuration file.

The MjServer is available open source under the terms of the GNU GPL license (general Public License), and can be easily modified and extended as required.

Is is distributed as jar binaries or togheter with the mjsip stack with all source files.

Very soon it will be available support for

• interfacing with LDAP and/or MySQL interfaces,
• providing authentication through the use of a back-end RADIUS server,
• multiple authentication schemes (like 3GPP AKA, RADIUS-based, etc.)

Moreover, a SIP Server acting as Session Border Controller has been also implemented and will be soon available.