Voice over IP and IPX Traffic SurveyReport Update

Voice over IP (and IPX) Traffic Survey/Report Update March 2019

Background Jan 8 th Technology WG conference call: • Voice over IPX traffic survey and report = carry-over item from last year (desire to prioritize & complete) • • • Discussed initial proposal for survey approach and traffic input template • • • End-to-end voice over IPX as a % of total ILD • End-to-end voice over IPX% Voice over IPX mixed with over technologies used to deliver ILD traffic • Inbound voice over IPX% • Outbound voice over IPX% Uncovered issues with i 3 f collect & calculate approach (carrier market share estimates = inaccurate data) Uncovered issues with proposed input template (double counting traffic) Received feedback from Vodafone, Telecom Italia, and Deutsche Telekom in post meeting / email follow-up • • • Confirmed interest to pursue further Confirmed interest in using 3 rd party (3 rd party collects and aggregates traffic data) Request to rework and simplify initial ‘mock-up’ traffic input template Feb 12 Technology WG conference call: • • • Discussed Philippe’s suggestion to modify scope to include voice over IP traffic (either in addition to, or in replace of, voice over IPX) General consensus was to modify scope to include voice over IP IN ADDITION TO voice over IPX (greater participation and visibility) Include voice over IP Inbound, Outbound, End-to-End in addition to voice over IPX Inbound, Outbound, End-to-End (and Total ILD) Carrier Member Capture through easy-to-use carrier traffic input form Participation Required!!!! High Participationof. Rate = Meaningful Sample Size Clear definitions to promote common understanding inputs being requested (Representative of Global ILD Market)

Proposed plan moving forward I 3 forum membership wide communication (Need participation from all carrier members!!!): • • • Send communication to entire i 3 f soliciting carrier member participation (Specific engagement with Technology & Market Data Workgroups) Use 3 rd party (Greg) to collect and aggregate carrier member traffic data (all inputs kept anonymous and confidential) Carrier member points of contact (POCs) to review exercise internally (with stakeholders) and coordinate carrier inputs / response Communication to provide details regarding the exercise and next steps • What we are doing • • Why we are doing it & what you get out of it…. • • • Migration to IP and IPX remains core to i 3 forum mission Understand carrier position in IMS service space Bolster carrier readiness Champion acceleration Gain valuable insight into aggregate traffic levels and trends (indicative of the market) How we are doing it • • Measure & track voice over IP and voice over IPX growth Carrier members populate traffic input form Send to 3 rd party for data aggregation (all inputs kept anonymous and confidential – carriers will only see/receive aggregate market results) Simplified traffic input form can be used to repeat exercise going forward Who is involved • • • Project Team (Thanga, Greg, Filippo – collaborate on – i 3 f communication, project plan, input form, carrier member questions) Carrier Member POCs (POCs requested to coordinate their company’s traffic inputs and response, send populated input form back to 3 rd party facilitator) 3 rd Party facilitator (Greg – collect responses, aggregate data, provide aggregate results)

Proposed traffic input form Simplified form (. xlsx) to capture carrier traffic inputs Responses to reflect how traffic is managed on responding carrier’s voice network Includes previous two calendar years to establish initial trend Definitions: • • • ILD Voice Minutes - Total annual international long distance voice minutes terminated (incudes wholesale, retail & enterprise traffic, excludes domestic traffic) Inbound - Minutes received from a customer Outbound - Minutes sent to a supplier End-to-End - minutes received from a customer and sent to a supplier Vo. IP - all flavors of voice over IP (public and private) Vo. IPX - voice over IPX VLANs only (private, secure, Co. S, SLA enabled) Conditions: • • Carriers must provide inputs for all questions (if No traffic for category just put 0) 2, 3, 4 are all subsets of 1 to avoid double counting minutes, 4 should be exclusive of 2 and 3 2 b is a subset of 2 a, 3 b is a subset of 3 a, and 4 b is a subset of 4 a - voice over IPX minutes are a subset of voice over IP minutes

Proposed timelines To be captured in i 3 f communication (subject to change) • Philippe to send i 3 forum communication with Traffic Input Form – Mar 22 • Directly following Philippe’s email…. to garner increased attention and participation…. • • Filippo to send additional communication directly to Technology WG Suzy to send additional communication directly to Market Data WG • Carrier member POC to coordinate response and send populated form back to Greg - Apr 26 • Greg to aggregate responses and provide initial market view to project team + Philippe – May 10 (aggregate data only) • Project team + Philippe to review market report and disseminate final version accordingly – May 24 (aggregate data only) Proposed Carrier Member POCs (Leader at each carrier that can drive buy-in & action): Should Ibasis and SFR be combined into one Tofane or will separate responses be provided by each? Any other suggested changes to carrier POCs?

THANK YOU