SRE 3.0 Major Upgrade Extends Capabilities

Netaxis release major upgrade to Session Routing Engine with SRE 3.0

The Netaxis Session Routing Engine (SRE) has become an essential part of a VoIP network operator infrastructure. It’s simple to use drag and drop GUI provides operational cost savings and API driven interfaces to third party databases such as ENUM, LDAP Active Directory and QoS massively improves functionality and makes it easy to integrate.

Release 3.0 introduces two major architectural improvements :

  • Service providers can now design and implement their own database structure essentially moving  the SRE into the world of a truly standard product and making it a scalable proposition in the market.
  • A multitenant architecture drives role based access allowing international telcos to manage global routing. This simplifies an operator network by reducing the number of POPs required  to service different international markets. In-country personnel can manage their own customers without being able to see the subscribers of neighbouring countries.

SRE has many flexible use cases including inbound, outbound and centralised routing and also supports Microsoft Direct Routing for Teams.

Versioning is a very powerful aspect of the software. It allows a network operator to have: 

  • Two databases loaded onto their platform with one nominated as the primary. 
  • The secondary database can be used for development work or as an instant rollback in the event that a new primary database develops a problem.

versioning in SRE 3.0

This is not the same as running two SREs as a High Availability pair. Each one of the pair has the two databases.

SRE can also be operated on a geographically distributed basis with different routing databases in different regions or countries for example.

The SRE is aware of the Carrier’s Voice Products (Platinum, Gold, Premium etc as they are actually implemented in the platform. Least Cost Routing can be complemented with QoS based routing.  In this case when a trunk is skipped due to bad quality or other issues it can be easily removed from the network routing path. 

Customized alarms based on traffic thresholds can support the upselling process. Barring is available and can be combined with different logic and conditions and thus no longer based on a static feature in an old-fashioned Switch.

Please contact us for information on SRE3.0 or check out this page.