Voice over IP Interconnect Stephen Kingham Project Manager and Consulting Engineer, Voice and Video over IP AARNet and CSI...
Who is AARNet and CSIRO <ul><li>CSIRO Is Australia’s premier government research organisation, only partially government f...
AARNet Topology http://www.aarnet.edu.au
AARNet VOIP Building Blocks Based on ITU H.323 standards
AARNet VoIP Service, Now <ul><li>Supports all telephony destinations, Toll-by-pass and feature transparency is core busine...
Test Call Scenarios <ul><li>Test key call scenarios and </li></ul><ul><li>PABX/IP Telephone alternate route under all fail...
“ TOLL BYPASS” Business Model
Hop off points for AARNet Members
AARNet VoIP, Tomorrow <ul><li>Research VoIP interconnects between carriers. </li></ul><ul><li>VoIP interconnect pilots wit...
Some key lessons <ul><li>Resource QoS implementation and support as much as the VoIP. </li></ul><ul><li>Use VoIP to switch...
Basis of the Charging Model <ul><li>On-net </li></ul>Hop-off See  http:// voip . aarnet .net.au/AARNet
Some key lessons <ul><li>Although peak bandwidth per call is 24kbps, in practice it is on average 5kbps (using G.729), do ...
VoIPMonitor TOPOLOGY <ul><li>Monitor links to each RNO, and </li></ul><ul><li>Links to each member. </li></ul><ul><li>Shut...
Some key issues for VoIP interconnect. <ul><li>H.323 proxies appear to be the answer for solving these key issues: </li></...
VoIP Carrier Interconnection <ul><li>Signalling system number 7 is not appropriate for VoIP </li></ul>
Outgoing calls from site
Safety of Life <ul><li>Emergency Service providers rely on knowing WHERE someone is, not who.  How do we do it???? </li></ul>
Questions Contact Details, and Thank you URL:  http://www.aarnet.edu.au/ [email_address] Phone +61 2 6276 6223 Mobile +61 ...
Upcoming SlideShare
Loading in …5
×

Presentation file

314 views
278 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
314
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Example shows an AARNet Member and the AARNet Hop Off in to a Public Telephone Carrier. ISDN is ETSI or Australian TS13. H.323 Gateway uses G.729a 8kbps voice compression. H.323 Gatekeeper resolves Telephone number (E.164) to IP address H.323 used to establish connection to remote H.323 device or Gateway. Technology is enabling for PABX less sites. AARNet Voice supports fax but NOT modems. Shares data bandwidth (26kbps per active call) Router and PABX provide the routing and look ahead alternate routing. Router supplies bytes and calls for billing. Voice and Data groups will need to be co-ordinated.
  • Example shows an AARNet Member and the AARNet Hop Off in to a Public Telephone Carrier. ISDN is ETSI or Australian TS13. H.323 Gateway uses G.729a 8kbps voice compression. H.323 Gatekeeper resolves Telephone number (E.164) to IP address H.323 used to establish connection to remote H.323 device or Gateway. Technology is enabling for PABX less sites. AARNet Voice supports fax but NOT modems. Shares data bandwidth (26kbps per active call) Router and PABX provide the routing and look ahead alternate routing. Router supplies bytes and calls for billing. Voice and Data groups will need to be co-ordinated.
  • Example shows an AARNet Member and the AARNet Hop Off in to a Public Telephone Carrier. ISDN is ETSI or Australian TS13. H.323 Gateway uses G.729a 8kbps voice compression. H.323 Gatekeeper resolves Telephone number (E.164) to IP address H.323 used to establish connection to remote H.323 device or Gateway. Technology is enabling for PABX less sites. AARNet Voice supports fax but NOT modems. Shares data bandwidth (26kbps per active call) Router and PABX provide the routing and look ahead alternate routing. Router supplies bytes and calls for billing. Voice and Data groups will need to be co-ordinated.
  • VoIP traffic is routed using the Gatekeeper to the most appropriate Gateway. In most cases today traffic is routed to the AARNet hop off Gateways in strategic locations around the country, but it there significant traffic to other VoIP enabled PABXs and to PABXless sites (IP Telephones). Telephony traffic originates from VoIP enabled PABXs and IP Telephones connected to the IP Network. Note that VoIP traffic from all IP Telephones originates from H.323 Proxies to gain QoS from the AARNet cloud. At at March this network is carrying 7000 calls per working day.
  • AARNet2 is the seconds implementation of AARNet and is based on ATM connections between each Regional Centres. AARNet Member institutions connect to the Regional Hub for TCP/IP Connectivity to AARNet and the rest of the Internet. One of the envisaged projects for AARNet2 was to put voice over AARNet2, in addition to demonstrating high speed distributed computing and Video Conferencing. Voice over ATM is available and work extremely well. The down fall is that ATM is not available to all locations, where as today where ever there is a telephone there is also a TCP/IP connection not far away. VoIP, is this the technology that will eventually bring Voice and Data together? Never before has there been so much movement by Data vendors to include Voice capability and never before has PABX vendors moved so fast for anything, and so fast at putting IP into their PABXs. But look carefully, it sounds easy, and some of it is, but it is not easy building Production grade Voice networks. Potential for Sector Wide Carrier Tariffs. Carrier could “blow us out of the water” with a super low price and would be the best outcome of the project.
  • Billing New Charging Philosophy (both parties charged) Can still use PABX Centric TIMS
  • AARNet2 is the seconds implementation of AARNet and is based on ATM connections between each Regional Centres. AARNet Member institutions connect to the Regional Hub for TCP/IP Connectivity to AARNet and the rest of the Internet. One of the envisaged projects for AARNet2 was to put voice over AARNet2, in addition to demonstrating high speed distributed computing and Video Conferencing. Voice over ATM is available and work extremely well. The down fall is that ATM is not available to all locations, where as today where ever there is a telephone there is also a TCP/IP connection not far away. VoIP, is this the technology that will eventually bring Voice and Data together? Never before has there been so much movement by Data vendors to include Voice capability and never before has PABX vendors moved so fast for anything, and so fast at putting IP into their PABXs. But look carefully, it sounds easy, and some of it is, but it is not easy building Production grade Voice networks. Potential for Sector Wide Carrier Tariffs. Carrier could “blow us out of the water” with a super low price and would be the best outcome of the project.
  • AARNet2 is the seconds implementation of AARNet and is based on ATM connections between each Regional Centres. AARNet Member institutions connect to the Regional Hub for TCP/IP Connectivity to AARNet and the rest of the Internet. One of the envisaged projects for AARNet2 was to put voice over AARNet2, in addition to demonstrating high speed distributed computing and Video Conferencing. Voice over ATM is available and work extremely well. The down fall is that ATM is not available to all locations, where as today where ever there is a telephone there is also a TCP/IP connection not far away. VoIP, is this the technology that will eventually bring Voice and Data together? Never before has there been so much movement by Data vendors to include Voice capability and never before has PABX vendors moved so fast for anything, and so fast at putting IP into their PABXs. But look carefully, it sounds easy, and some of it is, but it is not easy building Production grade Voice networks. Potential for Sector Wide Carrier Tariffs. Carrier could “blow us out of the water” with a super low price and would be the best outcome of the project.
  • It appears that the familiar method of interconnecting VoIP networks using the “traditional” ITU-T Signaling System No 7 is not appropriate. Will a variation of SS No7 work or will it strangle the innovation possible with VoIP? It is not entirely the fault of Marketing departments that Telephone feature transparency does not function across Carriers. AARNet and CSIRO are looking for VoIP Networks interested in sponsoring research in this area. Interconnect will not only need to accommodate the billing as does SS No7 but will also need to match QoS.
  • Example shows an AARNet Member and the AARNet Hop Off in to a Public Telephone Carrier. ISDN is ETSI or Australian TS13. H.323 Gateway uses G.729a 8kbps voice compression. H.323 Gatekeeper resolves Telephone number (E.164) to IP address H.323 used to establish connection to remote H.323 device or Gateway. Technology is enabling for PABX less sites. AARNet Voice supports fax but NOT modems. Shares data bandwidth (26kbps per active call) Router and PABX provide the routing and look ahead alternate routing. Router supplies bytes and calls for billing. Voice and Data groups will need to be co-coordinated. There are already sites that are only IP. Some day soon there will be VoIP “only” Carriers in Australia. Which Carrier will be in the best position to supply services to these Customers, a VoIP Carrier or a PSTN Carrier? Video could have a similar topology for H.323 Video (IP) to H.320 Video (ISDN) Gateways.
  • Presentation file

    1. 1. Voice over IP Interconnect Stephen Kingham Project Manager and Consulting Engineer, Voice and Video over IP AARNet and CSIRO [email_address] Ph +61 2 6276 6223 John Barlow Network Engineer AARNet [email_address] Ph +61 2 6276 6903
    2. 2. Who is AARNet and CSIRO <ul><li>CSIRO Is Australia’s premier government research organisation, only partially government funded. http://www.csiro.au </li></ul><ul><li>AARNet Is the Australian Academic Research Network, linking Australia’s Universities, premier research and cultural centres to the internet. http://www.aarnet.edu.au </li></ul>
    3. 3. AARNet Topology http://www.aarnet.edu.au
    4. 4. AARNet VOIP Building Blocks Based on ITU H.323 standards
    5. 5. AARNet VoIP Service, Now <ul><li>Supports all telephony destinations, Toll-by-pass and feature transparency is core business. </li></ul><ul><li>Savings range up to 90% off RRP. </li></ul><ul><li>Traffic: connects around 16,000 telephone calls per day, and growing. </li></ul><ul><li>Uses a root Gatekeeper and some feeders. </li></ul><ul><li>AARNet backbone supports QoS. </li></ul><ul><li>QoS is policed at ingress – accesslist (yuk). </li></ul><ul><li>VoIP hackers are policed – accesslist (yuk). </li></ul><ul><li>Billing system, based on calling IP address. </li></ul><ul><li>QoS network management actively changes H.323 routing around problems. </li></ul><ul><li>Test lab </li></ul>
    6. 6. Test Call Scenarios <ul><li>Test key call scenarios and </li></ul><ul><li>PABX/IP Telephone alternate route under all failure conditions </li></ul>
    7. 7. “ TOLL BYPASS” Business Model
    8. 8. Hop off points for AARNet Members
    9. 9. AARNet VoIP, Tomorrow <ul><li>Research VoIP interconnects between carriers. </li></ul><ul><li>VoIP interconnect pilots with research institutions in US, Korea, Singapore, Czech Republic, Brazil. </li></ul><ul><li>VoIP interconnect with two Australian Carriers. </li></ul><ul><li>Implement a smarter Gatekeeper. </li></ul><ul><li>Get H.323 proxies working in production. </li></ul><ul><li>Change method of policing QoS. </li></ul><ul><li>Change method of authorising VoIP calls. </li></ul><ul><li>Change billing system to be based on bytes rather than time (both ends pay …). </li></ul><ul><li>Support IP Telephones. </li></ul><ul><li>Support VIDEO as well as audio (native as well conferencing and gateways back to ISDN). </li></ul>
    10. 10. Some key lessons <ul><li>Resource QoS implementation and support as much as the VoIP. </li></ul><ul><li>Use VoIP to switch call, do not use PABXs. </li></ul><ul><li>Reduces faults in private telephone networks. </li></ul><ul><li>VoIP using G.729 is resilient against packet loss. </li></ul><ul><li>Enabling QoS to get over the brief periods of congestion is needed, even on Gigabit. </li></ul><ul><li>Billing model need to change from traditional telephony to data constructs. </li></ul>
    11. 11. Basis of the Charging Model <ul><li>On-net </li></ul>Hop-off See http:// voip . aarnet .net.au/AARNet
    12. 12. Some key lessons <ul><li>Although peak bandwidth per call is 24kbps, in practice it is on average 5kbps (using G.729), do your own maths on the cost! </li></ul><ul><li>Huge changes looming for management of basic telephony. AARNet has started a working group to assist migration from PABX to IP Telephones. </li></ul>
    13. 13. VoIPMonitor TOPOLOGY <ul><li>Monitor links to each RNO, and </li></ul><ul><li>Links to each member. </li></ul><ul><li>Shutdown destinations that fail. </li></ul><ul><li>http://lattice. aarnet .net.au/ VoIPMonitor </li></ul><ul><li>Client only tests local links </li></ul>
    14. 14. Some key issues for VoIP interconnect. <ul><li>H.323 proxies appear to be the answer for solving these key issues: </li></ul><ul><ul><li>Providing access between domains, or Internet into LAN based IP telephones. </li></ul></ul><ul><ul><li>Policing use of QoS. </li></ul></ul><ul><ul><li>Authenticating who is making the VoIP call. </li></ul></ul><ul><li>Gateways need to authenticate VoIP calls through an intelligent Gatekeeper or a clearing house sever using OSP. </li></ul>
    15. 15. VoIP Carrier Interconnection <ul><li>Signalling system number 7 is not appropriate for VoIP </li></ul>
    16. 16. Outgoing calls from site
    17. 17. Safety of Life <ul><li>Emergency Service providers rely on knowing WHERE someone is, not who. How do we do it???? </li></ul>
    18. 18. Questions Contact Details, and Thank you URL: http://www.aarnet.edu.au/ [email_address] Phone +61 2 6276 6223 Mobile +61 419 417 471 [email_address] Phone +61 2 6276 6690

    ×