Mvts portabilling
1 / 12

MVTS & PortaBilling - PowerPoint PPT Presentation

  • Uploaded on

MVTS & PortaBilling. Infrastructure for global communications. Integration between MVTS (Mera VoIP Transit Softswitch) and PortaBilling100. Porta Software Mera Networks Vancouver, BC July 2004. MVTS features

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about 'MVTS & PortaBilling' - gautam

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Mvts portabilling
MVTS & PortaBilling

Infrastructure for global communications

Integration between MVTS (Mera VoIP Transit Softswitch) and PortaBilling100

Porta Software

Mera Networks

Vancouver, BC July 2004

Mvts portabilling100

MVTS features

H323 gatekeeper and proxy (both signaling and media) functionality

Secure network peering, network topology hiding

Dynamic modification of network topology

Flexible routing, fail-over routing

Seamless interoperability with equipment from different vendors (Cisco, Quintum, VocalTec, Clarent, Samsung, NSG, D-Link, etc.)

NAT/Firewall solution

PortaBilling features

Web interface for service provisioning (accounts, customers, rates, CDRs, etc.)

Real-time authentication and authorization of calls

Flexible routing management (multiple vendors, routing preferences, least-cost routing (LCR), custom routing plans for individual customers)

Real-time billing of completed calls, ASR and cost/revenue reports

MVTS & PortaBilling100

Integration between mvts and portabilling100
Integration between MVTS and PortaBilling100

  • Endpoint registration (authentication)

  • Call authorization

  • Call routing

  • Billing completed calls

Operations performed in tandem by MVTS and PortaBilling100:

Endpoint registration
Endpoint registration

Endpoint attempts to register with gatekeeper (MVTS)



MVTS sends authentication request to PortaBilling100

PortaBilling100 verifies that such an account exists, is not blocked, and so on

PortaBilling100 sends confirmation or rejection

Upon successful authentication, MVTS registers the endpoint

Call authorization
Call authorization

Endpoint attempts to make a call

MVTS sends authorization request to PortaBilling100

Called party

PortaBilling100 verifies that such an account exists, whether calling this destination is allowed, and what is the maximum allowed call duration



PortaBilling100 sends confirmation (including maximum credit time) or rejection

MVTS connects the call

After the time is up, or the customer disconnects, the call is cleared and accounting is sent to PortaBilling100

Calling party

Call routing
Call routing

MVTS requests routing for the specified number


PortaBilling searches the available routes and classifies them according to preference/price





A list of routes is returned to MVTS



MVTS attempts to send the call via the first route


If that fails, MVTS tries the second route, and so on


  • Vendor A – preference 5, $0.05/min

  • Vendor B – preference 6, $0.07/min

  • Vendor C – preference 5, $0.04/min

Routing in portabilling100
Routing in PortaBilling100

  • Routes can be arranged into preference groups (according to parameters such as quality, ASR, etc.)

  • For routes within the same group, least-cost routing (LCR) can be applied

  • If necessary, huntstop can be used to “cut off” lower priority routes

  • An optimal route list is calculated in real time for every call

Billing completed calls
Billing completed calls

After the call is disconnected, MVTS sends the accounting to PortaBilling100

Called party



PortaBilling charges the account/customer who made the call and calculates the termination cost, depending on which vendor was used

New CDR, balance modification

Calling party

H323 and sip network interconnection
H323 and SIP network interconnection

H323-based network

SIP-based network

Session Border Controller (protocol converter)

The protocol converter can be used to integrate several networks using different protocols.

Portaswitch sip hit

PortaSwitch allows:

Easy web-based provisioning and management of SIP accounts

Auto-configuration tool for SIP UAs (Cisco ATA, etc.)

Class 5 features (call transfer, abbreviated dialing, customer-based numbering plans, etc.)

Special features (follow-me services, unified messaging integration, etc.)

SIP-HIT allows:

Terminating calls to legacy H323 networks or receiving calls from such networks

Codec conversion, solving vendor incompatibility issues

Optional usage of MVTS for advanced call handling

PortaSwitch & SIP-HIT

Sip h323 network interconnection with portaswitch sip hit
SIP<->H323 network interconnection with PortaSwitch+SIP-HIT

PortaSIP provides end-point registration, NAT traversal, etc.

H323 network

PortaBilling100 provides authentication, number translation, authorization, routing and billing of completed calls



Calls to H323 destinations are routed to SIP-HIT

SIP-HIT provides call transition to H323 networks



Porta Software's PortaBilling/PortaSIP and MERA Networks' MVTS are highly symbiotic products - the "yin and yang" of VoIP.

Each component's functionality ideally fits the other's to create a complete and perfect VoIP solution, with scalable architecture and open protocols for easy integration.