Property of i3 Forum (all rights reserved) Analysis of T.38 protocol Survey results, carrier’s remarks and suggestions Contact Points: Dr. Jerzy Soldrowsky.

Slides:



Advertisements
Similar presentations
Commetrex Corporation Mike Coffee CEO, Commetrex SIP Forum FoIP Task Group FoIP In Carrier Networks UC-SIP Trunking Summit FoIP Session.
Advertisements

Early Media Authorization Under what conditions should negotiated media flow prior to 200 OK (INVITE)? Richard Ejzak.
NETW-250 Troubleshooting Last Update Copyright Kenneth M. Chipps Ph.D. 1.
H. 323 Chapter 4.
A Presentation on H.323 Deepak Bote. , IM, blog…
Voice over IP Fundamentals
Security in VoIP Networks Juan C Pelaez Florida Atlantic University Security in VoIP Networks Juan C Pelaez Florida Atlantic University.
ETSI Workshop on Quality Issues for IP Telephony 8-9 June 1999, Sophia Antipolis, France ETSI PROJECT TIPHON overview of QoS activities ETSI Workshop on.
1 Roch H. Glitho- Ericsson/Concordia UniversityJanuary 2008 INSE 7110 – Winter 2008 Value Added Services Engineering in Next Generation Networks Week #4,
© 2006 Cisco Systems, Inc. All rights reserved. Optimizing Converged Cisco Networks (ONT) Module 2: Cisco VoIP Implementations.
Commetrex Corporation Mike Coffee CEO Commetrex Co-Chair SIP Forum FoIP Task Group Phase II FoIP Testing.
SIP Testing Methodology Elie Cohen ProLab PM 17/01/2003.
© 2006 Cisco Systems, Inc. All rights reserved Introducing VoIP Networks.
11 TROUBLESHOOTING Chapter 12. Chapter 12: TROUBLESHOOTING2 OVERVIEW  Determine whether a network communications problem is related to TCP/IP.  Understand.
CHAPTER 13 Gateway Control Protocols. Media Gateway Control Protocol: MGC: Media Gateway Controller MG: Media Gateway Master/Slave relationship MG handles:
Testing SIP Services Over IP. Agenda  SIP testing – advanced scenarios  SIP testing - Real Life Examples.
Session Initiation Protocol (SIP) By: Zhixin Chen.
ICE Jonathan Rosenberg dynamicsoft. Issue 1: Port Restricted Flow This case does not work well with ICE right now Race condition –Works if message 13.
A General approach to MPLS Path Protection using Segments Ashish Gupta Ashish Gupta.
SIP, Session Initiation Protocol Internet Draft, IETF, RFC 2543.
Voice over Internet Protocol (VoIP) Training and Development.
TCP: Software for Reliable Communication. Spring 2002Computer Networks Applications Internet: a Collection of Disparate Networks Different goals: Speed,
1 Media Gateway Benoit Bégué 2006 Study for EE department. EE526 with Professor Dan Keun Sung.
Signaling interworks in PSTN and Voice-over-IP networks
Presented by Zhi-Hong Guo Instructed by Assistant Professor Quincy Wu
1 Fax and Modem Training May Modem Types.
RTP Relay Support in Intelligent Gateway Author: Pieere Pi
Data Communications and Networks
DTMF & Universal User Key Input Skip Cave InterVoice-Brite Inc.
For discussion purposes. No implementation assurances 1 Consult 21 Interconnect Working Group NGN Interconnect - PSTN Emulation Technical Consultation.
Signaling & Network Control Dr. Eng. Amr T. Abdel-Hamid NETW 704 Winter 2006 Intelligent Networks.
VoIP security : Not an Afterthought. OVERVIEW What is VoIP? Difference between PSTN and VoIP. Why VoIP? VoIP Security threats Security concerns Design.
July 10, 2006rtpsec BOF IETF-661 Best Effort SRTP Phil Zimmermann Alan Johnston.
NAT Traversal Speaker: Chin-Chang Chang Date:
Commetrex Corporation Mike Coffee CEO, Commetrex SIP Forum FoIP Task Group “What About Fax?” UC-SIP Trunking Summit FoIP Session.
CHAPTER 14 PSTN and VoIP Interworking. Cisco Packet Telephony: Connection Control Call Control Services.
SIP Interoperability Testing Alan Percy Director of Business Development AudioCodes, Inc. Booth #822.
MGCP Megaco H.248 by Bob Young. MGCP - Megaco - H.248 "It's all one."
Call Control with SIP Brian Elliott, Director of Engineering, NMS.
1 © 2003, Cisco Systems, Inc. All rights reserved. CCNA 2 Module 9 Basic Router Troubleshooting.
University of the Western Cape Chapter 12: The Transport Layer.
QUALCOMM Incorporated 1 Protocol Options for BSN- BSMCS Controller Interface Jun Wang, Kirti Gupta 05/16/2005 Notice: Contributors grant a free, irrevocable.
NATIONAL INSTITUTE OF SCIENCE & TECHNOLOGY VOICE OVER INTERNET PROTOCOL SHREETAM MOHANTY [1] VOICE OVER INTERNET PROTOCOL SHREETAM MOHANTY ROLL # EC
Omar A. Abouabdalla Network Research Group (USM) SIP – Functionality and Structure of the Protocol SIP – Functionality and Structure of the Protocol By.
William Stallings Data and Computer Communications
Security, NATs and Firewalls Ingate Systems. Basics of SIP Security.
VoIP Signaling Protocols A signaling protocol is a common language spoken by telephones and call-management servers, the PSTN, and legacy PBX systems as.
Session Initiation Protocol (SIP) Chapter 5 speaker : Wenping Zhang data :
SIP working group IETF#70 Essential corrections Keith Drage.
SIP Performance Benchmarking draft-ietf-bmwg-sip-bench-term-01 draft-ietf-bmwg-sip-bench-meth-01 March 22, 2010 Prof. Carol Davids, Illinois Inst. of Tech.
CSE5803 Advanced Internet Protocols and Applications (14) Introduction Developed in recent years, for low cost phone calls (long distance in particular).
Voice and Video over IP.
SIP-H.323 Interworking Group RRR-1 IETF-48 SIP-H.323 Interworking Requirements draft-agrawal-sip-h323-interworking-reqs-00.txt Hemant.
MEGACO SIP State Machine Inter-conversion and Message Translation
The Session Initiation Protocol - SIP
3/10/2016 Subject Name: Computer Networks - II Subject Code: 10CS64 Prepared By: Madhuleena Das Department: Computer Science & Engineering Date :
1 Personal Mobility Management for SIP-based VoIP Services 王讚彬 國立台中教育大學資訊工程學系
I3 forum Fax over IP: achieving an industry solution Jerzy Sołdrowski Network Architect Telekomunikacja Polska S.A. i3 forum Technical Workshop Warsaw,
Technical Specification for Fax over IPX service Madrid February 2010.
سمینار تخصصی What is PSTN ? (public switched telephone network) تیرماه 1395.
by Kiran Kumar Devaram Varsha Mahadevan Shashidhar Rampally
Instructor Materials Chapter 2: Point-to-Point Connections
IP Telephony (VoIP).
Protocols and the TCP/IP Suite Overview and Discussion
Instructor Materials Chapter 9: Transport Layer
May 2004 Fax and Modem Training.
PPP PROTOCOL The First semester
Chapter 2: Point-to-Point Connections
Chapter 4: Access Control Lists (ACLs)
Voice Over Internet Protocol
Presentation transcript:

Property of i3 Forum (all rights reserved) Analysis of T.38 protocol Survey results, carrier’s remarks and suggestions Contact Points: Dr. Jerzy Soldrowsky (editor of T.38 document in i3F WS “Technical Aspects”) Telecom Poland Dr. Alessandro Forcina (chairman of i3F WS “Technical Aspects”) Telecom Italia Sparkle

Property of i3 Forum (all rights reserved) Survey results based on 10 Carriers answers Purpose: To investigate most frequent faults during fax connection. To determine most suspected: 1.Call phase 2.Section in connection chain 3.Most frequently used profile

Property of i3 Forum (all rights reserved) Declared faults per call phase

Property of i3 Forum (all rights reserved) Declared faults per connection chain section IP network Carrier A IP network Carrier B BG Carrier A owned VoIP network (3) TDM network (1) Third party owned VoIP network (7) Outgoing direction Incoming direction Interconnection link (7) (4) Fax type:  G.3 fax  B/W

Property of i3 Forum (all rights reserved) Most frequently used profile Transport – TCP/UDPTL/RTP- 2/7/2 Transition method – MGC and Autonomous 4/5 Error correction method – FEC/Redundancy/none 4/4/2 Training – local/transferred 3/6 Modulation – V.17/ 14.4 kbit/s SG3 fax – officially not supported, G.711 VBD, G3 fallback or unstable

Property of i3 Forum (all rights reserved) Carrier’s remarks and other suggestions

Property of i3 Forum (all rights reserved) Wrong error codes CPE gateways for Retail not correctly handling the SIP Re- Invite with T.38 media offered in the SDP. If the media type is not supported, the UAS (originating gateway) must send a 415 (Unsupported Media) error to the requesting UAC (terminating gateway). Many gateways sent 488 (Not Acceptable Here) or 606 (Not Acceptable), those errors are also handled by the network gateway (UAC) and the media reverts to G.711 which allows the fax to complete. H.248 is reported back to the MGC as error code 401 if a media attribute like T.38 is not supported on the MG. MGCP returns as error code 518. When these error codes are received by the MGC, the call is torn down as a Signaling Failure.

Property of i3 Forum (all rights reserved) Terminal – Gateway incompatibility If Internet-aware Fax devices supports T.38 only and Media Gateway supports G.711 upspeed only it is not possible to rollback to G.711 upspeed mode when a T.38 session request is not accepted by the other endpoint. Signalling is setup properly (T.38 ports opened), but fax device doesn’t generate a required messages for T.38 implementation on VoIP GW-A using ATAs or for GW-B own fax protocols for conversion Gr. 3 Fax VoIP GW-B PSTN Gr. 3 Fax VoIP GW-A PSTN Gr. 3 Fax ATA Gr. 3 Fax T.30T.38 T.30 FaxoverIP (FoIP)

Property of i3 Forum (all rights reserved) Terminal – Gateway incompatibility Non standard fax of different types (encrypting equipment). Proprietary Inband protocol for Encryption key distribution to support fax encryption High Quality fax (High resolution) with very long distance calls (Europe to Japan/Australia) Those problems have been solved by the NGN vendor by modifying in a proprietary way the T38 protocol (between their own media gateways) or by disabling T38 on the fly and moving to G711. Most failures on VoIP GW-B (VoIP network) No T.38 implementation on VoIP GW-B Incompatibilities of ATAs or fax machines (IAF) Buffer and timer errors

Property of i3 Forum (all rights reserved) SDP Offer/Answer ITU-T T.38 Annex D : it is worth considering the possibility to further define the SDP parameters, in order to specify whether each one is negotiable or declarative, and the range of permitted values and default values.

Property of i3 Forum (all rights reserved) Fax discrimination Echo canceller (EC): ITU-T T.38 does not specify if the use of Echo Canceller is recommended when switching from audio to T.38 during fax discrimination phase. It could happen that echo canceller use affects fax setup announcement tones, thus impacting fax startup phase. For most of the fax calls that fail, we observe that the common indication is ‘no signal detected’ This immediately follows T.38 (re- Invite) which is supposed to be after fax tone detection CNG (calling tone) or CED (called tone). CED and CNG however, are optional tones for T.38, presumably because, although the T.30 fax protocol requires them, not all fax machines comply. Thus the Preamble (V21) is always present in the signalling, but not necessarily CED. When we check the T38 media negotiation (in particular UDPTL), the signals appear to be in order, the right media ports are opened, and yet no signal is detected. Staff have reported an observation that T.38 fax “no signal detected” failures occur more frequently for fax calls when CED is not present, that for T.30 compliant signals which have CED. This has not been checked rigorously however.

Property of i3 Forum (all rights reserved) Transition problems MG incompatibility in autonomous transition method. It needs the Media Gateway to be able to generate/understand supplier dependant (not standard) RTP packets (e.g. Cisco NSE) in order to indicate the will to switch from audio to T.38. SIP ReINVITE messages for switching from audio to G.711 (for ‘CED’ tone transmission): ITU-T T.38 does not specify any indication, to use in the SDP part of the SIP ReINVITE message, as a reason regarding modem or fax transmission. As a result, the Call Agent uses global configuration for G.711 audio channel setup (e.g. use of VAD or audio-driven configuration) that can affect the subsequent fax tone sending. SIP ReINVITE messages for switching to T.38: ITU-T T.38 does not specify if the “user=phone” string in the “From” and “To” SIP fields is globally accepted between carriers.

Property of i3 Forum (all rights reserved) During facsimile transmission Loss of packets Delay and jitter