Sippy Softswitch IP to IP Authentication

IP to IP Authentication is core to the Sippy Softswitch's foundation configuration, delivering significant flexibility to calls management for your successful business implementation.

Note: This document is to complement the Sippy VoIP Softswitch Introduction Video Tutorial, Youtube video primarily to highlight IP Authentication on the call origination side and revisit termination IP Authentication.

Termination IP Authentication

As has been displayed in the Sippy VoIP Softswitch Introduction Video Tutorial, IP Authentication is achieved on the termination, supplier side, of the Sippy Softswitch with the Vendor's "Connection" concept (Vendor > Connection).

A "Vendor" is a flexible entity that can be considered as your A-Z Termination Supplier, an Interconnect, Carrier, or for GSM Gateways, IP-PBX's or various other implementations, for call termination to the upstream or egress side of the call. Each Vendor can be assigned as many individual "Connections" as required, empowering flexibility for number translations, capacity and CPS limitations, quality monitoring and many other specific parameters.

The following images provide a brief overview of the steps for IP Authentication for origination and termination only. Additional configuration is required to pass calls successfully.

Navigate to Vendor in Sippy's Customer Menu, under the "My Vendors" sub-section, to configure termination IP side. Add new Vendor and/or select Open Connections to add IP to existing Vendor (see above).

Existing Connections are shown in the table, listed in this example as Gateway1, Gateway2, and Gateway3. Your configuration will add one additional Connection to this list for Authentication. Add new Connection (see above) for the new IP to be authenticated for routing.

Provide a Connection Name for reference in the Connections table and add IP address into "Destination" field (see above). Save and Close to add the IP address to your list of Authenticated IP's, in your Vendor's Connections table.

The Vendor's "Connections" table now shows the IP address that has been configured. The IP of presented as "SIP:" (showing selected protocol of Connection) has been configured as an example (see above). This completes the termination configuration of your IP to IP business model.

Note: If working with a new Sippy Softswitch, additional configurations are required to succeed in the next step of this document, specifically adding the new Connection to a Routing Group as a Routing Entry. With existing routing and billing parameters already set up, following this document will result in completed IP to IP authentication. Watching the Youtube video will walk through the additional steps required or follow the Wholesale Scenario checklist for additional assistance.

Origination IP Authentication

Once the fundamental configuration is completed regarding vendor's rates, routing preferences, and billing parameters, origination IP Authentication can be configured.

An Account relates to an entity matching centralized CDR's and a single Balance relating to all authenticated calls from the originating source. The Account is a flexible entity that can be used for a versatile range of business and client requirement, with both Digest and flexible IP/CLI/CLD authentication methods. An Account is the location of your originating IP Authentication for ingress traffic. Each Account can have as many specified "Authentication Rules" as required, increasing security against fraudulent traffic, and flexibility for specific call routing and billing.

To add originating IP Authentication, Navigate to an Account in Sippy's Customer Menu to configure the IP of call origination. If a new Account is to be created for your client, add Account with the Add button (see above). Configure Account parameters and save your new Account. Select the Action dropdown menu that corresponds with the newly created Account and click on the Authentication Rules option.

Add Authentication Rule. Configure originating IP Address in Remote IP field (see above). Save and Close to add rule. Additional parameters can be used for flexible authentication or restriction of traffic from a specified remote IP address. See additional online resources for more information.

The Account's Authentication Rules table now shows the IP address that has been configured. IP: has been configured as an example (see above).

This completes the origination configuration of your IP to IP model and your client will then be able to pass calls using the configurations of this Account.

Additional online resources

Sippy Fundamentals videos:

Sippy online documentation: