1. Global SIP Dialling Plans (SIP Peering using key pads) SIP Workshop APAN Tokyo Japan 25 January 2005

2. 2 Agenda 9:10 The SIP.edu Initiative (about 15 minutes) by Dennis Baron, MIT and Chair of Internet2 SIP Working Group 9:25 Internet Subscriber Number (ISN) trial (about 20 mins) by Ben Teitelbaum of Internet2 9:45 ENUM to peer VoIP Networks (about 10 minutes ) by Stephen Kingham 9:xx Using a hierarchy of SIP Servers. by Quincy Wu and Stephen Kingham 9:55 Open/Panel discussion until 10:30. how R&D networks might peer their SIP networks.

3. 3 Introduction SIP Peering is already done when the domain is known because the DNS does all the work. eg anyone can call sip:Stephen.Kingham@aarnet.edu.au. These talks and discussion is about supporting the 12 button user interface, or specifically routing using numbers where the domain in NOT known.

4. 4 Peering already works for Peering using a full sip:address@domain.name ©Stephen Kingham@aarnet.edu.au

5. 5 by Dennis Baron, MIT and Chair of Internet2 SIP Working Group http://www.internet2.edu/sip.edu/ See separate slide pack. Talk on SIP.edu ©Stephen Kingham@aarnet.edu.au

6. 6 by Ben Taitelbaum, Internet2 wheel http://www.internet2.edu/sip.edu/isn/ See separate slide pack. ITAD Subscriber Numbers (ISNs) ©Stephen Kingham@aarnet.edu.au

7. Using ENUM to peer SIP Workshop APAN Tokyo Japan 25 January 2005

8. 8 Routing Telephone numbers! WWW and email work by using the Domain Name Service (DNS). –DNS turns human addresses into Internet addresses, –DNS on its own is very uninteresting or useful! The ENUM standard teaches DNS about Telephone numbers! –VoIP users can discover that they can make VoIP calls to a number without routing it first to the PSTN! –Traditional Carriers around the world do not like ENUM. Join the ACMAs ENUM Trial, ref: enum.edu.au ©Stephen Kingham@aarnet.edu.au

9. 9 ENUM (SIP and H.323 Routing) ©Stephen Kingham@aarnet.edu.au

10. 10 Getting your telephone number delegated in the DNS! The TLD owner of the golden ENUM tree is ITU-T. The ITU-T will only allocate the E.164 country code to the relevant countries government that has the number. Well that is the trick! Some countries have it, some are in trials, most do not, just maybe some will never get it. ©Stephen Kingham@aarnet.edu.au

11. 11 Private ENUM DNS trees I propose APAN could consider two possibilities to enable research: The private tree run by the ccTLD in the APAN Region, known as Asia Pacific ENUM Engineering Team (APEET). http://www.apenum.org/. APAN H.323-SIP Working group is working with APEET on the processes so that APAN Members can get ENUM delegations. http://www.apenum.org/ I understand Internet2 community use Pulver. APAN members would then programme their SIP Servers to look up each ENUM trees looking for a hit, starting with the golden tree?. ©Stephen Kingham@aarnet.edu.au

12. 12 Using a Hierarchy of SIP Proxies Perhaps as an interim…… ;-) Refer to H.323 Global Dialling Scheme. Several Root Servers all know the E.164 prefix for each Country SI PServer Country SIP Servers know the E.164 prefixs of Organisational SIP Servers. All static!!! Ref: http://www.apan.net/wg/voip/sip-peering/index.html http://www.apan.net/wg/voip/sip-peering/index.html ©Stephen Kingham@aarnet.edu.au

13. 13 Using a Hierarchy of SIP Proxies (all static or use TRIP) ©Stephen Kingham@aarnet.edu.au

14. 14 H.323 routing (all static configuration) ©Stephen Kingham@aarnet.edu.au

15. 15 http://www.voip-info.org/wiki-DUNDi Is another option tabled by an APAN Member. ASTERISK DUNDi PROTOCOL

16. 16 Open Discussion An interesting question to ask is for how long will we need to support such an interface?