DOC

4S ITSP User Manual

By Nicholas Graham,2014-09-18 10:39
6 views 0
4S ITSP User Manual4S I

    4S ITSP Solution

    A turnkey infrastructure

    for advanced Voice-over-IP

    telecommunication

snom technology Aktiengesellschaft,

    Gradestr. 46, 12347 Berlin, Germany,

    Represented by Dr. Christian Stredicke

    (Executive Board)

Filename: 4S.ITSP.<DATE>.doc Total Pages: 25 Created: 1.9.2005 Dr. Harry Behrens Status: Confidential 1 Last saved: 9/18/2012 10:40:00 AM, Dr. Harry Behrens Revision 1 ? 2005 snom technology AG

4S ITSP Solution

Table of Contents

    1 Overview ............................................................................... 3 1.1 Features ............................................................................... 3

    1.1.1 Call Termination ............................................................... 3

    1.1.2 Trunking and Peering ........................................................ 3

    1.1.3 NAT traversal................................................................... 4

    1.1.4 PSTN Integration .............................................................. 4

    1.1.5 Customization and Branding .............................................. 4

    1.1.6 CDR Generation, AAA and Billing Integration ....................... 4

    1.1.7 Flexible routing to multiple Gateways, LCR .......................... 4

    1.1.8 Configuration ................................................................... 4

    1.1.9 Voicemail ........................................................................ 5

    1.1.10 Security ....................................................................... 5

    1.1.11 Quality of Service (QoS) ................................................. 5

    1.1.12 Capacity Planning and Availability .................................... 5 2 snom technology AG ............................................................... 5 3 System Overview ................................................................... 6 3.1 System Layout ...................................................................... 6 3.2 Internal Structure .................................................................. 9 3.3 User Agents ........................................................................ 10 3.4 Session Border Controller ..................................................... 10 3.5 Proxy/Registrar ................................................................... 10 3.6 Mediaserver ........................................................................ 10 3.7 Application Server................................................................ 11 3.8 PSTN gateway ..................................................................... 11 4 System Requirements ........................................................... 11 5 Installation and Configuration ................................................ 11 5.1 Installation Packages ........................................................... 12 5.2 Install Application Server (AS) ............................................... 12

    5.2.1 Install XAMPP ................................................................ 12

    5.2.2 Configure XAMPP ............................................................ 12

    5.2.3 T0: Test LAMPP .............................................................. 13

    5.2.4 Install 4S ITSP Business Logic ......................................... 14

    5.2.5 Configure BL Settings ..................................................... 15

    5.2.6 T1: Test Business Logic................................................... 16 5.3 Configure database for local setup ......................................... 16 5.4 4S Session Border Controller (SBC) ....................................... 17

    5.4.1 Installing the 4S SBC ...................................................... 17

    5.4.2 Configure the 4S SBC for ITSP mode ................................ 17 5.5 4S Forking Proxy ................................................................. 18

    5.5.1 Installing the 4S Proxy .................................................... 18

    5.5.2 Configuration of Forking Proxy ......................................... 18

    5.5.3 T2: Basic Call ................................................................ 21 5.6 4S Media Server .................................................................. 21

    5.6.1 Configure 4S Mediaserver ............................................... 22 Filename: 4S.ITSP.<DATE>.doc Total Pages: 25 Created: 1.9.2005 Dr. Harry Behrens Status: Confidential 2 Last saved: 9/18/2012 10:40:00 AM, Dr. Harry Behrens Revision 1 ? 2005 snom technology AG

4S ITSP Solution

6 System Integration (SI) ........................................................ 24

    7 Support and Maintenance (SM) .............................................. 24

1 Overview

    The snom 4S ITSP solution is a complete off-the-shelf voice delivery plat-form enabling service providers to deliver SIP-based VoIP service. It provides service providers with a complete prepaid voice delivery plat-form with integrated pricing and billing.

    The system is hardware-independent and highly configurable to the carri-er‟s specific needs.

    It combines the SIP capabilities of the well-proven 4S suite of software such as the snom 4S Session Border Controller/NATfilter with the flexibili-ty of a HTTP-based application server.

    All persistent data is stored in an SQL database allowing for maximum flexibility in configuration and provisioning.

Key Features

    • Carrier grade ITSP solution

     • 100% SIP-compliant software solution (RFC3261 et al.)

     • Supports all major SIP user agents

     • Supports all major PSTN gateways and softswitches

     Web-based User Portal

     Web-based Admin Portal

    • Far-end NAT traversal for all SIP user agents

     • Support for inbound (DID/DDI) and outbound PSTN calls (PSTN break-out)

     • Central management through web and database interfaces

     Full scalability for redundancy and capacity planning upon request

     • Configurable to pre-paid or post-paid

     • Can be extended to support Class 5 services and hosted PBX

     • Can be extended to IP Centrex functionality

1.1 Features

    1.1.1 Call Termination

    Provide voice and other media services to any SIP-based user agent. 1.1.2 Trunking and Peering

    Support for both upstream and downstream connectivity. Downstream the system routes calls to PSTN gateways and softswitches. Upstream it pro-vides trunking to IP PBXs, i.e. it connects an external (PSTN) number (and SIP URI) to the inbound side of the IP PBX. This is analogous to an exter-nal ISDN line being connected to a PBX.

    Filename: 4S.ITSP.<DATE>.doc Total Pages: 25 Created: 1.9.2005 Dr. Harry Behrens Status: Confidential 3 Last saved: 9/18/2012 10:40:00 AM, Dr. Harry Behrens Revision 1 ? 2005 snom technology AG

4S ITSP Solution

1.1.3 NAT traversal

    NAT problems are a thing of the past. The 4S ITSP solution handles all types of NAT including symmetric and needs no configuration whatsoever on the user agent. In fact, the less the provider relies on the user agents to use STUN or UPnP for NAT traversal, the more effective the service is. 1.1.4 PSTN Integration

    Based on proven interoperability with all major SIP PSTN gateways, the system can be configured for smooth PSTN breakout as well as Direct In-ward Dialling (DID), CLIR and other call termination services. 1.1.5 Customization and Branding

    All user and administration interfaces can be tailored to the provider‟s 1specifications. 2The system is built around an SQL database (DB) which holds all business

    information. User credentials, destinations, gateways, time bands, credit information and all other information pertaining to a prepaid voice delivery platform are stored in the DB. Using standard import/export utilities from any desktop (e.g. MS Excel, MS Access, VBA...) business data can be changed and effectuated in real-time.

    Where needed, new features can be added by loading additional software modules into the application server.

    1.1.6 CDR Generation, AAA and Billing Integration

    3CDRs are stored in the SQL database. All accounting is done in real-time

    and users can check their latest balance through their personal web pages. Upon requests CDR format can be configured to the provider‟s needs.

    1.1.7 Flexible routing to multiple Gateways, LCR

    Each destination for which break-out is supported can be assigned to a separate downstream gateway. Through simple changes in the business 4logic of the application server least-cost routing (LCR) scenarios can be

    easily implemented.

    1.1.8 Configuration

    A web-based admin portal is provided with the system.

     1 This is charged for separately. 2 currently we use mySQL, but porting to other databases is easy 3 In fact calls are automatically terminated once the balance drops to 0. 4 ask snom for terms and conditions Filename: 4S.ITSP.<DATE>.doc Total Pages: 25 Created: 1.9.2005 Dr. Harry Behrens Status: Confidential 4 Last saved: 9/18/2012 10:40:00 AM, Dr. Harry Behrens Revision 1 ? 2005 snom technology AG

4S ITSP Solution

    Simple table-driven configurations as well as more complex scripted sce-narios are easily realized.

    1.1.9 Voicemail

    Each user can be provisioned with a voicemail account. Upon reception of new messages, the mailbox sends message waiting indications (MWI) by E-Mail to predefined destinations that have subscribed to these notifica-tions.

    1.1.10 Security

    All service delivery can be encrypted using SIPS and HTTPS. The session border controller provides topology hiding, header stripping as well as ba-sic CALEA (legal intercept functionality).

    1.1.11 Quality of Service (QoS)

    Quality of service is a major issue in delivering voice services over packet-switched networks. The snom 4S ITSP solution supports QoS based on DiffServ by packet labeling. This allows carriers to differentiate themselves by providing constant and dependable level of service. We also have con-siderable experience in integrating the 4S ITSP Solution

    1.1.12 Capacity Planning and Availability

    The snom 4S ITSP solution is a pure software solution. Based on a strict policy of keeping no local state in any core system, failing of any unit will result in no loss of state in a redundant scenario. This means that any lev-el of availability (99.99% or 99.999%) can be configured by provisioning an appropriate number of parallel units.

    Based on standard DNS-based configurations any number of parallel units can be provisioned for capacity planning. Fail-over and Capacity Planning can be combined to provide highly available systems for any level of throughput.

    Most of the redundancy planning can be done at the network layer. Only the application server (AS) and the database (DB) needs to be configured at a higher layer.

2 snom technology AG

    snom technology AG (?snom“) provides complete solutions for VoIP sys-

    tems. snom is committed to open standards, especially the IETF suite of RFCs surrounding SIP (RFC3261).

    Using snom technology provides interoperability with all major vendors in the industry, allowing customers to assemble a “best-of-breed” network

    based on snom technology.

    We assure interoperability through membership in the VoIP Interoperabil-ity Alliance (VIA) and participation in industry-wide events like the annual SIPit.

    Filename: 4S.ITSP.<DATE>.doc Total Pages: 25 Created: 1.9.2005 Dr. Harry Behrens Status: Confidential 5 Last saved: 9/18/2012 10:40:00 AM, Dr. Harry Behrens Revision 1 ? 2005 snom technology AG

4S ITSP Solution

snom‟s core products are:

    ; VoIP telephones (snom190, snom320 and snom360)

    ; snom 4S

    o ITSP Solution

    o IP PBX

    o Session Border Controller/NATfilter (SBC)

    snom products can be assembled and configured to build

    ; IP-PBX systems for business offices

    ; IP-Centrex systems to provide an ASP-model for PBX services 5; class5 backbones for VoIP ITSPs

    ; SIP-based service network for value-added multimedia and messag-

    ing services

    3 System Overview

    The system consists of two logical parts:

    1. signaling and media control (SIP, RTP)

    2. application logic, routing, accounting, billing

On a physical layer, the system will consist of the following components:

    1. User Agents

    2. snom 4S Session Border Controller (SBC)

    3. Application Server

    3.1. HTTP Server

    3.2. Database Server

    3.3. Business Logic

    4. snom 4S Proxy/Registrar

    5. snom 4S Mediaserver

    6. PSTN Gateway (PGW)

    3.1 System Layout

The overall network layout is shown below. This diagram shows the gen-

    eral connection between the main units.

    The 4S Session Border Controller (SBC) constitutes the edge and the only external interface of the network underlying the 4S ITSP Solution.

    It is the central port of entry for all signaling and media, handling all NAT

    traversal and media relay.

     5 Internet Telephony Service Provider Filename: 4S.ITSP.<DATE>.doc Total Pages: 25 Created: 1.9.2005 Dr. Harry Behrens Status: Confidential 6 Last saved: 9/18/2012 10:40:00 AM, Dr. Harry Behrens Revision 1 ? 2005 snom technology AG

4S ITSP Solution

When establishing and managing dialogs it communicates with the appli-

    cation server (AS) when any of the following Event Slots occur:in any of 6the following contexts:

    1. Authentication

    2. Registration

    3. Dialog

    Within each of these contexts the SBC passes parameters relevant to the current dialog to the AS.

    The AS executes the appropriate business logic (PHP programs) using the connected database for all persistent state information such as user, credit, rate, gateway.

    The SBC uses a 4S Proxy or a 4S IP PBX to fork authorized calls. This

    unit then

    ; either forwards the call to the PSTN gateway

    ; or sends it to the SIP user agent (SUA)

    in that case the call is forwarded (back) through the SBC The Web Admin portals both for users and administrators of the system both interact directly with the AS.

     6 These contexts directly (1:1) correspond to settings in the web admin interface of the 4S Session Border Controller. Filename: 4S.ITSP.<DATE>.doc Total Pages: 25 Created: 1.9.2005 Dr. Harry Behrens Status: Confidential 7 Last saved: 9/18/2012 10:40:00 AM, Dr. Harry Behrens Revision 1 ? 2005 snom technology AG

4S ITSP Solution

Filename: 4S.ITSP.<DATE>.doc Total Pages: 25 Created: 1.9.2005 Dr. Harry Behrens Status: Confidential 8 Last saved: 9/18/2012 10:40:00 AM, Dr. Harry Behrens Revision 1 ? 2005 snom technology AG

4S ITSP Solution

3.2 Internal Structure

    The internal structure of the 4S ITSP solution is given in the diagram be-

    low:

Filename: 4S.ITSP.<DATE>.doc Total Pages: 25 Created: 1.9.2005 Dr. Harry Behrens Status: Confidential 9 Last saved: 9/18/2012 10:40:00 AM, Dr. Harry Behrens Revision 1 ? 2005 snom technology AG

4S ITSP Solution

3.3 User Agents

    7User Agents are assumed to be SIP-compliant as per RFC3261.

    3.4 Session Border Controller

    The SBC is the point of entry for all UAs. It is closely linked to the proxy/registrar (PR).

    Together the SBC and the PR manage the signalling for all incoming calls/sessions/dialogs.

    The SBC‟s main role is to make network topology transparent to UAs and SIP servers. Specifically, it assists UAs in traversing their own private-address networks (via NAT) to access SIP and RTP (for data) services pro-vided through public-address networks.

    In addition it enables NAT-to-NAT communication, when both endpoints are in a private network.

    3.5 Proxy/Registrar

    The Proxy/Registrar is the centerpiece of any VoIP infrastructure. It pro-vides the main routing and forking intelligence of the 4S ITSP solution. It holds no state of its own and is completely controlled by the SBC. The SBC “operates” the proxy by sending it SIP URIs with a number of

    parameters. The proxy executes these with a built-in script engine and forks calls accordingly.

    The only configuration needed for the proxy registrar is its ITSP control script.

    3.6 Mediaserver

    The Mediaserver provides management of media streams. Based on SIP-based communication, complex voice applications (IVR, voice portals etc.) can be realized.

    These applications can be combined to provide full functionality for IP-PBX or IP-Centrex systems.

    The Mediaserver provides customers with the ability to combine Voice- and Video-over-IP with Instant Messaging and Presence Management to provide a rich Unified Communication experience with full support for mul-timedia.

    In the 4S ITSP solution the 4S Mediaserver is used for voicemail, balance announcements and - through an additional module interactive voice

    response (IVR).

    The Mediaserver is controlled through two interfaces:

    1. SIP signaling with the proxy being the controller.

     7 RFC2543-based UAs may or may not interoperate Filename: 4S.ITSP.<DATE>.doc Total Pages: 25 Created: 1.9.2005 Dr. Harry Behrens Status: Confidential 10 Last saved: 9/18/2012 10:40:00 AM, Dr. Harry Behrens Revision 1 ? 2005 snom technology AG

Report this document

For any questions or suggestions please email
cust-service@docsford.com