All VoIP Peering Needs is a Good CDR - PowerPoint PPT Presentation

1 / 14
About This Presentation
Title:

All VoIP Peering Needs is a Good CDR

Description:

Thousands of anonymous peers. Complete and efficient route discovery. LERG. LNP database ... SourceAlternate type='transport' [Proxy IP Address] /SourceAlternate ... – PowerPoint PPT presentation

Number of Views:36
Avg rating:3.0/5.0
Slides: 15
Provided by: jimdaltont
Category:
Tags: cdr | voip | anonymous | good | needs | peering | proxy

less

Transcript and Presenter's Notes

Title: All VoIP Peering Needs is a Good CDR


1
All VoIP Peering Needs is a Good CDR
  • New Market Peering
  • 30 November 2006
  • Jim.Dalton_at_TransNexus.com

2
VoIP Peering Quote of the Year
  • If you want VoIP to kill SS7, then VoIP has to
    completely replicate everything SS7 does.
  • Tom Kershaw
  • Economist

3
The Worlds Largest Voice Peering Fabric
  • The US SS7 Network (PSTN)
  • Thousands of anonymous peers
  • Complete and efficient route discovery
  • LERG
  • LNP database
  • An efficient economic model
  • Multi-lateral financial settlement
  • Independent clearinghouses

4
SS7 Voice Peering Fabric
LERG
LNP
Multi-lateral Clearinghouse
5
VoIP Peering Clearing Settlementis Bilateral
Peer 1
Peer 6
Peering Service Provider
CDRs
CDRs
CDRs
Peer 2
Peer 5
Session Border Controller
CDRs
CDRs
Peer 3
Peer 4
CDRs
CDRs
6
ENUM Federation Peering
Peering Service Provider
Peer 1
ENUM Directory
Peer 6
CDRs
CDRs
Peer 5
Peer 2
CDRs
CDRs
Peer 3
Peer 4
CDRs
CDRs
7
Multi-lateral Clearing Settlement
Multi-lateral Clearinghouse
Peer 1
Peer 6
CDRs
CDRs
Peer 5
Peer 2
CDRs
CDRs
Peer 3
Peer 4
CDRs
CDRs
8
Carrier Access Billing (CABS) CDR
  • 2020090708315900035E89E890000000000000000000000000
    00000000000000000000000001200000000000000000000000
    00000000000000000112300000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    0000000000
  • 11010107082810706632000000010404872393720469000000
    18201140160008330020003500000100000000300000600001
    000310215E89000000000000000000000000000000000DJ3Z0
    00833000000000000346040496100000000901730000000000
    0000000000
  • 11010107082810706632000000010706454515220469000000
    18200945390002011020003500000100000000300000600001
    000310215E89000000000000000000000000000000000DJ3Z0
    00201100000000000346040496100000000901730000000000
    0000000000
  • 11010107082910404200999900010404418101020537000000
    10001003310008090020003500003100000000308000600001
    000310221E89040000000000000000000000000000000DJ3Z0
    00809000000000007473040441810000000301730000000000
    0000000000
  • 11010107082910404200999900010404418121220537000000
    10001501520008033020003500003100000000308000600001
    000310221E89040000000000000000000000000000000DJ3Z0
    00803300000000007473040441810000000301730000000000
    0000000000
  • 11010107082910404200999900010404418121220537000000
    10001636220000566020003500003100000000308000600001
    000310221E89040000000000000000000000000000000DJ3Z0
    00056600000000007473040441810000000301730000000000
    0000000000
  • 11010107082910404200999900010404961040520537000000
    10001756430000034020003500003100000000308000600001
    000310221E89040000000000000000000000000000000DJ3Z0
    00003400000000007473040441810000000301730000000000
    0000000000
  • 11010107082910404200999900010404961040520537000000
    10002001090001018020003500003100000000308000600001
    000310221E89040000000000000000000000000000000DJ3Z0
    00101800000000007473040441810000000301730000000000
    0000000000

9
ETSI Settlement CDR
ltUsageIndication componentId"47850982870685430174
"gt ltTimestampgt2005-05-12T173333Zlt/Timestampgt ltRo
legtsourcelt/Rolegt ltTransactionIdgtTransaction
IDlt/TransactionIdgt ltCallId encoding"base64"gtCall
IDlt/CallIdgt ltSourceInfo type"e164"gtCalling
Numberlt/SourceInfogt ltDeviceInfo
type"transport"gtSource IP Addresslt/DeviceInfogt
ltSourceAlternate type"transport"gtProxy IP
Addresslt/SourceAlternategt ltDestinationInfo
type"e164"gtCalled Numberlt/DestinationInfogt ltDesti
nationAlternate type"transport"gtDestination IP
addresslt/DestinationAlternategt ltUsageDetailgt
ltAmountgt23lt/Amountgt ltIncrementgt1lt/Incrementgt
ltUnitgtslt/Unitgt ltStartTimegt2005-05-12T1733
10Zlt/StartTimegt ltAlertTimegt2005-05-12T174212
Zlt/EndTimegt ltEndTimegt2005-05-12T174227Zlt/End
Timegt ltConnectTimegt2005-05-12T174217Zlt/Conne
ctTimegt ltReleaseSourcegt0lt/ReleaseSourcegt lt/Usa
geDetailgt
10
OSP Clearinghouse Example
OSP Server
11
Call Accounting
OSP Server
12
Multiple Clearinghouses
OSP Server
OSP Server
Internet
Purple Clearinghouse Network
Yellow Clearinghouse Network
13
Call Accounting
OSP Server
OSP Server
Internet
Purple Clearinghouse Network
Yellow Clearinghouse Network
14
OSP Details
  • OSP is a message set for inter-domain pricing,
    authorzation and accounting
  • OSP messages
  • XML format
  • Transmitted via HTTP
  • An OSP server is a web server
  • ETSI TS 101 321
  • OSP Enabled VoIP devices
  • Cisco, Veraz, Stratus, Sansay, Covergence,
    OpenSER, SIP Express Router, Asterisk
Write a Comment
User Comments (0)
About PowerShow.com