mvts & portabilling
DESCRIPTION
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 - PowerPoint PPT PresentationTRANSCRIPT
PORTAONEMVTS & PortaBilling
Integration between MVTS (Mera VoIP Transit Softswitch)
and PortaBilling100
Vancouver, BC July 2004
Porta Software http://www.portaone.com
Mera Networks http://www.mera-voip.com
Infrastructure for global communications
PORTAONEMVTS & 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
PORTAONE
Integration between MVTS and PortaBilling100
Endpoint registration (authentication) Call authorization Call routing Billing completed calls
Operations performed in tandem by MVTS and PortaBilling100:
PORTAONEEndpoint registration
Endpoint attempts to register with gatekeeper (MVTS)
MVTS PortaBilling100
Upon successful authentication, MVTS registers the endpoint
MVTS sends authentication request to PortaBilling100
PortaBilling100 verifies that such an account exists, is not blocked, and so on
PortaBilling100 sends confirmation or rejection
PORTAONECall authorization
After the time is up, or the customer disconnects, the call is cleared and accounting is sent to PortaBilling100
MVTS
Called party
Calling party
PortaBilling100
MVTS sends authorization request to PortaBilling100
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
Endpoint attempts to make a call
PORTAONECall routing
MVTS PortaBilling100
•Vendor A – preference 5, $0.05/min
•Vendor B – preference 6, $0.07/min
•Vendor C – preference 5, $0.04/min
A
B
C
2
1
3
B,C,A
PortaBilling searches the available routes and classifies them according to preference/price
MVTS requests routing for the specified number
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
PORTAONERouting 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
PORTAONEBilling completed calls
MVTSPortaBilling100
Called party
Calling 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
After the call is disconnected, MVTS sends the accounting to PortaBilling100
PORTAONE
H323 and SIP network interconnection
Session Border Controller (protocol converter)
SIP-based network
H323-based network
The protocol converter can be used to integrate several networks using different protocols.
PORTAONEPortaSwitch & 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
PORTAONE
SIP<->H323 network interconnection with PortaSwitch+SIP-HIT
H323 network
PortaSIP
SIP-HIT
PortaBilling100
PortaSIP provides end-point registration, NAT traversal, etc.
SIP-HIT provides call transition to H323 networks
Calls to H323 destinations are routed to SIP-HIT
PortaBilling100 provides authentication, number translation, authorization, routing and billing of completed calls
PORTAONEConclusion
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.