Dalton Jim

Secure Peering with Asterisk TM [email_address] VON.x – San Jose, CA March 2008

What is Secure Peering? ,[object Object],Internet Call Center Headquarters Sales Office Branch Office Manufacturing Peering Server Sales Office

Establishing PKI Security Services Certificate Authority (CA) for Peer to Peer Authorization (OSP Server) Client Device requests public-key and certificate from CA CA sends its public key and its certificate Client Device sends certificate request to CA CA returns signed certificate Asterisk Sign with CA private key VoIP Device Information VoIP Device Public Key Certified by Cert. Authority CA Signature Certificate Peering Server

Benefits of secure multi-lateral peering ,[object Object],[object Object],[object Object],[object Object],[object Object]

Examples of Secure Peering ,[object Object],[object Object],[object Object],[object Object]

Enterprise VoIP Network ,[object Object],Internet Call Center Headquarters Sales Office Branch Office Manufacturing 1. Centralized routing 2. Secure inter-office access control 4. Autonomous local operation 3. Centralized accounting 1. Centralized routing 2. Secure inter-office access control 3. Centralized accounting 4. Autonomous local operation 5. Minimum bandwidth 5. Minimum bandwidth 1. Centralized routing 1. 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

Enterprise VoIP VPN ,[object Object],Internet Call Center Headquarters Sales Office Branch Office Manufacturing 1. Centralized routing 2. Secure inter-office access control 3. Centralized accounting 4. Autonomous local operation 5. Minimum bandwidth 1. Centralized routing 1. 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 Peering Server 1. Enrollment 2. Route Authorization 3. SIP INVITE with Token 4. CDR collection Internet VoIP VPN

Wholesale Inter-Carrier Services ,[object Object],Internet

Wholesale Inter-Carrier Services ,[object Object],Internet Peering Server Route Lookup OSP Server OSP Server

Wholesale Inter-Carrier Services ,[object Object],Internet Peering Server OSP Server OSP Server Dest. CDR Source CDR

Tiered Peering ,[object Object],Internet Peering Server Peering Server Yellow Peering Network Purple Peering Network OSP Server OSP Server OSP Server OSP Server SIP INVITE with token for Purple network 1. Auth. Request 3. Auth. Response 2. Auth. Request 4. Auth. Response

Tiered Peering CDR Reporting ,[object Object],Internet Peering Server Yellow Peering Network Purple Peering Network Peering Server OSP Server OSP Server Source CDR Dest. CDR Source CDR Dest. CDR OSP Server OSP Server

DUNDi ,[object Object],[object Object],[object Object]

DUNDi Clearinghouse ,[object Object],[object Object],[object Object],2¢ / minute! rate / minute? ,[object Object],[object Object],[object Object],Peering Server Token Request

DUNDi Clearinghouse ,[object Object],[object Object],SIP INVITE with token ,[object Object],Peering Server CDR CDR

DUNDi Clearinghouse ,[object Object],$ $ Peering Server

Details of Secure Peering ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],OSP Peering Protocol XML Presentation HTTP V1.0 SSL / TLS TCP port 80 TCP port 443 IP

OSP Message Example HTTP/1.1 200 OK Server: IP address of OSP server Date: Thu, 12 May 2005 18:32:59 GMT Connection: Keep-Alive Keep-Alive: timeout=3600, max=5000 Content-Length: 1996 Content-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

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, … Digital signature of token ensures non-repudiation

Tools for Secure Peering ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Dalton Jim

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (20)

Destacado

Destacado (8)

Similar a Dalton Jim

Similar a Dalton Jim (20)

Más de Carl Ford

Más de Carl Ford (20)

Último

Último (20)

Dalton Jim