1 / 12

MVTS & PortaBilling

MVTS & PortaBilling. Infrastructure for global communications. Integration between MVTS (Mera VoIP Transit Softswitch) and PortaBilling100. Porta Software http://www.portaone.com Mera Networks http://www.mera-voip.com. Vancouver, BC July 2004. MVTS features

gautam
Télécharger la présentation

MVTS & PortaBilling

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MVTS & PortaBilling Infrastructure for global communications Integration between MVTS (Mera VoIP Transit Softswitch) and PortaBilling100 Porta Software http://www.portaone.com Mera Networks http://www.mera-voip.com Vancouver, BC July 2004

  2. 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

  3. Integration between MVTS and PortaBilling100 • Endpoint registration (authentication) • Call authorization • Call routing • Billing completed calls Operations performed in tandem by MVTS and PortaBilling100:

  4. Endpoint registration Endpoint attempts to register with gatekeeper (MVTS) MVTS PortaBilling100 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

  5. 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 MVTS 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

  6. Call routing MVTS requests routing for the specified number A PortaBilling searches the available routes and classifies them according to preference/price PortaBilling100 MVTS 3 B A list of routes is returned to MVTS 1 B,C,A MVTS attempts to send the call via the first route 2 If that fails, MVTS tries the second route, and so on C • Vendor A – preference 5, $0.05/min • Vendor B – preference 6, $0.07/min • Vendor C – preference 5, $0.04/min

  7. 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

  8. Billing completed calls After the call is disconnected, MVTS sends the accounting to PortaBilling100 Called party PortaBilling100 MVTS 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

  9. 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.

  10. 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

  11. 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 PortaBilling100 SIP-HIT Calls to H323 destinations are routed to SIP-HIT SIP-HIT provides call transition to H323 networks PortaSIP

  12. Conclusion 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. [

More Related