Document IPW-111 TIPHON Perspective on VoIP Numbering John Horrocks (DTI) Tiphon WG4 Chair

2 Tiphon Numbering relates to services not technology Regulation depends on services not technology IP can support many different services Aiming primarily at needs of telcos who migrate services onto IP Naming based on E.164 for public telephony (alternatives not excluded) Expect telcos will want protected boundaries so design for step/step call set-up with migration to end-end (hacking, quality control, call related charging, culture) Not dependent on public E.164-IP resolution system for starting

3 Names and Addresses: Basics-1 Name: Unique identifier of communicating entity, used by network, may be structured for user and contain geographic information Address: Location of entity in terms of network structure

4 Names and Addresses: Basics-2 Acknowledgement: DGTP Netherlands

5 Main current work areas IETF: IPTEL general work based on SIP ENUM selection of means to communicate with E.164 number, based on DNS, precursor to use of SIP for call IETF: PINT Control connection between PSTN dial-up access and ISP Tiphon: E.164 to IP resolution Acknowledgement: DGTP Netherlands

6 Where Tiphon fits in IP address E.164 Services Tiphon E.164 Services Choice E.164URLSIP ENUM IPTEL Acknowledgement: DGTP Netherlands (Search engines)

7 Different service concepts Voice telephony service E.164 Switched circuit networks IP networks Common service model Switched circuit networks IP networks SCN telephony E.164 IP telephony + E.164 Different service model ETSI Tiphon H.323 IETF SIP Acknowledgement: DGTP Netherlands

8 Common service numbering Acknowledgement: DGTP Netherlands Needed for E IP resolution No updating from users or IP based operators without allocation from NRA Customers of IP operators allocated E.164 numbers under this system

9 The Future: Multi-Everything Multiple Users (different roles, different persons, distinctive alerting) Multiple terminals Multiple accesses (eg fixed, mobile 1, mobile 2) Multiple service providers Multiple services (eg telephony, fax data, video)

10 Future caller needs

11 Future solutions Avoid a wholly new system allow smooth market-led migration Grow E.164 for different roles/labels Hide E.164 with better terminals and search engines Work needed on privacy vs exchange of information to facilitate search engines

12 Tiphon Approach Many different voice related services supported on IP E.164 use depends on service implemented Interconnected networks with real boundaries Allow Step-by-step call set-up

13 Any information on called party E.164 number (directory number) SCN switch Called E.164 Routing E.164 Ingress IP gateway Route on called E.164 Route on routing E.164 Service information may be accessed either from SCN or IP Next hop information Routing mostly uses tables in SCN switches. One switch may use IN for service information SCN technologyIP technology If present Next hop information Terminal information Called or Routing E.164 Called or Routing E.164 Called or Routing E.164 Calling terminal Address book Search engine or Directory Search resolution Service resolution (may be repeated) Service information Gatekeeper Home Gatekeeper E.164-IP Resolver Gatekeeper Service information could also be accessed by later gatekeepers There are various options for this signalling E.164-IP Resolver E.164-IP Resolver E IP routing resolution (may be repeated) E IP routing resolution (may be repeated) E IP local endpoint resolution (may be repeated) H.225 signalling IP address for media IP address for media Media

14 Possible network boundary Possible network boundary Cd(E.164) R(E.164) Ingress Gateway Possible network boundary SCN switch SCN switch SCN switch Signalling Media Terminal (or gateway back to SCN) Call control Service control Opens media Media I’face Signalling I’face Media IP Routing (UDP) Uses IP address from call control contains implicit call identification Uses available interconnections may give some quality control Signalling Cd(E.164) = Called E.164 number R(E.164) = Routing E.164 number SCNIP Service control Home Gatekeeper Resolves R(E.164) into IP address for Gatekeeper at destination Possible extension to SCN Ingress Gatekeeper Possible network boundary Routes on IP address but carries calling & called E.164 Checks availability of terminal Negotiates IP addresses for media channel Call control Service resolution Service information Cd(E.164) R(E.164) H.225 signalling IP address of terminal media port

15 SC CC BC MC SC CC BC MC CC BC MC 11 - Connect pairs (M2i,MTi), (M2o, M1o) 11 - Connect pairs (M2i,MTi), (M2o, M1o) 2a - S2i 2b - M1o reserved 2b - M1o reserved 5b - M2i, M2o reserved 5b - M2i, M20 reserved 5a - STi 12 - Connect may contain M2i M2i 3 - Set-up contains S1o may contain M1o When 2a +2b received M1o 13 - Activate media Ingress Gateway Home Gateway Call set-up direction Terminal 1a - Cd R(E.164) or Cd (E.164) 1b - Reserve media 1b - Reserve media E IP Routing Resolution 4b - Reserve media 4b - Reserve media 4a - Cd R(E.164) E IP Local Endpoint Resolution 7 - Reserve media 7 - Reserve media M1o M2i S2i S1o S2o M2o STi MTi 10 - Connect may contain MTi MTi 6 - Set-up contains S2o may contain M2o M2o 9 - Activate media 9 - Activate media Start Signalling Bearer 8 - MTi Reserved 8 - MTi Reserved

16 Network 1 Gateway Network 2 Gateway Call set-up direction 4b - Reserve media 4b - Reserve media 4a - Cd R(E.164) M1o M2i S2i S1o S2o M2o 6 - Set-up contains S2o, M2o 8 - Connect pairs (M2i,M3i), (M2o, M1o) 8 - Connect pairs (M2i,M3i), (M2o, M1o) M1i 2a - S2i 2b - M1i, M1o reserved 2b - M1i, M1o reserved 7 - Connect 5b - M2i, M2o reserved 5b - M2i, M20 reserved 5a - S3i 9 - Connect may contain M2i M2i 1a - Cd R(E.164) 1b - Reserve media 1b - Reserve media 3 - Set-up contains S1o may contain M1o When 2a +2b received M1o 10 - Connect pairs (M1i,M2i), (M1o, M0o) 10 - Connect pairs (M1i,M2i), (M1o, M0o) Start SC CC BC MC SC CC BC MC