Home News & Events Partners White Papers Resources  

Solutions

Service Provider
Enterprise VoIP VPN
Least Cost Routing
Cisco VoIP Networks
OpenSER / SER
Route Server
NexOSS

 

 

NexSRS VoIP Peering Server   Download

The NexSRS server is a feature rich, high performance routing and CDR collection server for VoIP networks.

The NexSRS server may be deployed as a external route server, or service control point (VoIP SCP), for multiple softswitches or session border controllers. 

Or, the NexSRS server can be deployed as a VoIP peering server for secure access control, routing and CDR collection for direct peer to peer traffic among anonymous VoIP networks.

Key Features:

  • Comprehensive routing features for VoIP devices and subnets

  • Trunk group routing and routing based on gateway or softswitch partitions

  • Time of day and day of week routing

  • Routing based on calling number for intra-state routing or customized local calling areas

  • VoIP routing based on any combination of rank ordering and load balancing

  • Called and Calling number translation based on DNIS, ANI, time of day, day of week

  • Bar calls based on any combination of DNIS, ANI, or IP address of source or destination

  • Call gapping

  • Auditing module available

  • Real time CDR collection from source and destination networks

  • Automated call blocking based on credit status

  • Support for queries to external route servers based on OSP or ENUM

  • CALEA module for secret diversion of calls based on any combination of ANI, DNIS, source IP or destination IP address.

  • Support for Cisco GKTMP protocol.

  • X.509 certificate authority

  • Messages encrypted using SSL / TLS

  • Broad Platform Support: Cisco, Asterisk, OpenSER, SIP Express Router, Stratus, Veraz, and others.

  • The NexSRS sever can be combined with NexOSS which offers the additional features of Least Cost and Grade of Service routing, QoS reports and alerts, Traffic Analysis reports, CDR rating and hourly billing and profitability reports - by customer and route.

NexSRS as a Route Server (VoIP SCP)

NexSRS may be configured as a route server and CDR collection server for a VoIP signaling device such as a softswitch, gatekeeper, SIP proxy or session border controller.  In this type of deployment, the NexSRS server provides the intelligence and scale for routing features that cannot be provided by a VoIP signaling device.  For example, since many VoIP signaling devices cannot support a large least cost routing table, this function is off-loaded to the NexSRS server which can support a routing table with 2,000,000+ destinations.  An example call scenario for this type of deployment is described below.  A single VoIP Switch is shown in the diagram, but typically multiple VoIP signaling platforms of different types could are served in parallel by one or more NexSRS servers sharing the load. 

1.   A call originates from the Source VoIP Device and is routed to the VoIP Switch.

2.   The VoIP Switch sends a routing query to the NexSRS server.  The NexSRS performs a route lookup and returns a list of IP addresses of devices which can complete the call to the called number.  The NexSRS can translate the calling or called number as needed.

3.   The call is routed from the VoIP Switch to the Destination VoIP Device which completes the call.

4.   At the end of the call, the VoIP Switch sends a call detail record to the NexSRS server.

NexSRS as a Secure Peering Server

The NexSRS server may also be used as a secure peering server for authorizing and accounting for direct peer to peer communications between anonymous VoIP networks.  For direct peering, each VoIP peer must enroll with the NexSRS certificate authority to obtain the NexSRS server's public key.  Also, the NexSRS server signs the certificate request from each VoIP device.  This feature requires the certificate authority and security features available only on the Solaris version of the NexSRS server.  The call scenario in the diagram below illustrates the NexSRS server being used as a peering server.

1.   A VoIP call originates from the Source VoIP Device.

2.   The Source VoIP Device sends a route query to the NexSRS server which returns a list of IP addresses of devices which can terminate the call.  Included with each address is a digitally signed peering token authorizing the call.

3.   The Source VoIP Device sends a SIP Invite or Q.931 call setup message directly to the destination peer.  The peering token is included in the SIP Invite or Q.931 call setup message.

4.   The Destination VoIP Device validates the peering token with the NexSRS server's public key.  If the token is valid, the Destination VoIP Device accepts the call.

5.   When the call is finished, both the source and destination devices send call detail records to the NexSRS server.

ClearIP Peering Engine

The ClearIP Peering Engine is an OEM version of the NexSRS server for vendors who want a private label, full featured, commercial OSP server.

About  |  Contact  |  Jobs  |  Blog  |  Privacy  | Search
Copyright © 2003-2007 TransNexus, Inc.
TransNexus, OSP Nexus, NexOSS, ClearIP, OSP Secured, NexTransit, Nex1, LookAhead Routing, PeeringHouse, Peering Engine, NexAudit, OSPrey, OSP Toolkit & RAMS are trademarks of TransNexus, Inc.  Patents: US 6,426,955; AU 748468; SG 200001336-7; IL 135131; UK 1016261; US 6,665,271; US 6,205,211; US 6,751,652, US 6,426,955, US 6,996,093, CA 2,304,214, US 7,203,956