open source open standards example of openser with osp [email protected]
TRANSCRIPT
3
Open Standards
• Open Source Projects based on Open Standards offer:
– Low cost– Flexibility– No Risk of being locked into a Proprietary Solution
• SIP applications• Web Standards that enable new SIP applications
– HTTP (SHTTP)– XML
4
OpenSER
OpenSER is an Open Source SIP Proxy• Very high reliability and performance• Very widely deployed• Very flexible
History• 2002 SIP Express Router (SER) Project• 2005 OpenSER forked from SER• 2008 June
– OpenSER changes names to Kamailio– OpenSIPS forked from OpenSER
5
OpenSER V1.2 Performance
• OpenSER has very high performance with OSP routing and accounting.
• OpenSER on a server with two, dual core Xeon CPUs can route and collect CDRs for over 500 million minutes per month of wholesale VoIP traffic.
0%
10%
20%
30%
40%
50%
60%
70%
80%
90%
100%
50 100 150 200
Calls per Second
CP
U U
tili
zati
on
OpenSER V1.1
OpenSER V1.2
SER 2.0
OpenSER Performance on a single core of an Intel 5140 2.33 CPU
6
• Value proposition begins with low price• Flexibility and innovation becomes a competitive
advantage– Load balance high call rates across multiple carriers
• Call Centers• Call Broadcasts
– Campaigns
– School systems
• DID services
SIP Trunking & DID Services
7
SIP Trunking & DID Services
PSTNCarrier 5
PSTNCarrier 4
PSTNCarrier 2
PSTNCarrier 1
PSTNCarrier 3
OSPServer
Enterprise
Enterprise
EnterpriseEnterprise
8
Overview of OSP Server
• ETSI OSP protocol defines standardized messages for the secure exchange IP based sessions.
• An OSP server is a web server• Resembles SOAP, VXML and CCXML
• Message Formats• Multipurpose Internet Mail Extensions (MIME)• eXtensible Markup Language (XML)• Secure MIME
• Communication Protocols
OSP Peering Protocol
XML Presentation
HTTP V1.0
SSL / TLSTCP port 80
TCP port 443
IP
9
OpenSER and OSP
OpenSER
RoutingQuery &
Response
Call DetailRecords
Source Network
Destination Network
OSPServer
10
Enterprise VoIP VPN
• Secure peering architecture provides VoIP VPN
Internet
CallCenter
Headquarters
SalesOffice
BranchOffice
Manufacturing
1. Centralized routing
2. Secure inter-office access control
3. Centralized accounting
4. Autonomous local operation
5. Minimum bandwidth
1. Centralized routing1. Centralized routing
2. Secure inter-office access control
1. Centralized routing
2. Secure inter-office access control
3. Centralized accounting
1. Centralized routing
2. Secure inter-office access control
3. Centralized accounting
4. Autonomous local operation
InternetVoIP VPN
OSPServer
1. Enrollment2. Route Authorization3. SIP INVITE with Digitally Signed Token4. CDR collection
11
Inter-Network Peering
OpenSER
RoutingQuery &
ResponseCall DetailRecords
Source Network
Destination Network
OSPServer
OpenSER
ValidatePeeringToken
12
Tiered Peering
Internet
OSPServerOSP
Server
PeeringServer
• Secure peering among multiple peering networks.
OSPServerOSP
Server
PeeringServer
SIP INVITE with tokenfor Purple network
YellowPeeringNetwork
PurplePeeringNetwork
1. Auth.Request
3. Auth.Response
2. Auth.Request
4. Auth.Response
13
Cascading Settlements
Internet
OSPServerOSP
Server
PeeringServer
• Secure, end to end accounting ensures every network is compensated.
YellowPeeringNetwork
PurplePeeringNetwork
SourceCDR
Dest.CDR
SourceCDR
Dest.CDR
OSPServerOSP
Server
PeeringServer
14
OSP Message Example
HTTP/1.1 200 OKServer: IP address of OSP serverDate: Thu, 12 May 2005 18:32:59 GMTConnection: Keep-AliveKeep-Alive: timeout=3600, max=5000Content-Length: 1996Content-Type: text/plain
<?xml version='1.0'?><Message messageId='11703738491' random='21655'><AuthorizationResponse componentId='11703738490'><Timestamp>2005-05-12T18:32:59Z</Timestamp><TransactionId>4785098287068543017</TransactionId><Destination> <CallId encoding='base64'>MTExNTkxOTE3Ny45</CallId> <DestinationInfo type='e164'>Called Number</DestinationInfo> <DestinationSignalAddress>[IP Address:Port]</DestinationSignalAddress>
HTTP Header
OSP Message
15
OSP Message Example (cont.)
<AuthorizationResponse componentId='11703738490'><Timestamp>2005-05-12T18:32:59Z</Timestamp><TransactionId>4785098287068543017</TransactionId><Destination> <CallId encoding='base64'>MTExNTkxOTE3Ny45</CallId> <DestinationInfo type='e164'>Called Number</DestinationInfo> <DestinationSignalAddress>[IP Address: Port]</DestinationSignalAddress> <UsageDetail> <Amount>14400</Amount> <Unit>s</Unit> </UsageDetail> <ValidAfter>2005-05-12T18:27:59Z</ValidAfter> <ValidUntil>2005-05-12T18:37:59Z</ValidUntil> <DestinationProtocol>sip</DestinationProtocol> <SourceInfo type='e164'>Calling Number</SourceInfo> <Token encoding='base64'> Vj0xCnI9MjE2NTUKYz0KQz03Nzc3Nzc3Nzc3Cmk9TVRFeE5Ua3hPVEUzTnk0NQphPT IwMDUtMDUtMTJUMTg6Mjc6NTlaCnU9MjAwNS0wNS0xMlQxODozNzo1OVoKST00Nz
Unique Transaction ID per call
Call ID from source device
Called Number may be translated
IP Address of Called Number
Call authorized for 14440 seconds Call authorized
to start in 10 minute window
Protocol may be SIP, H323, IAX, …
Digitally signed of token
16
More About OSP & OpenSER
• Instructions for building OpenSER with OSP support: http://www.transnexus.com/White%20Papers/Multi-Lateral_Peering_with_SER_V2.0.pdf
• OSP client library:
http://sourceforge.net/projects/osp-toolkit/
• OpenSER performance with OSP: http://www.transnexus.com/White%20Papers/OpenSER-SER_Comparison.htm