PETER CUTLER SCOTT PAGE. November 15, 2011

Transcription

1 Future of Fax: SIP Trunking PETER CUTLER SCOTT PAGE November 15, 2011

2 QUESTIONS AND ANSWERS

3 TODAY S SPEAKERS Peter Cutler Vice President of Sales Instant InfoSystems Scott Page Subject Matter Expert Dialogic

4 AGENDA Why are we here? Why all the talk about SIP Trunking? Fax is part of the SIP Infrastructure How SIP works How will SIP work for you?

5 WHY ARE WE HERE?

6 WHAT IS DRIVING SIP TRUNKING Organizations look for ways to lower costs Combine voice and data Moving to an IP infrastructure What does this mean for fax?

7 FAX IS PART OF THE SIP INFRASTRUCTURE Many organizations moving to VoIP Looking to lower telcocosts by combining voice and data Organizations are leveraging existing infrastructure Utilizing SIP for fax is not as easy as it looks Experience and technical knowledge will make the difference in a successfulsip trunk implementation for fax

8 FAX AND SIP TRUNKING Scott Page Dialogic

9 DRIVER : ENTERPRISE ADOPTION OF THE IP-PBX IP-PBX enables a converged voice and data network Leverage the corporate LAN / WAN Why Put Voice / Fax on an IP Network? Convergence reduces operating expense Centralized PBX and Voice and Fax Servers Using VoIP / FoIP reduces telephony costs IP-PBX Deployment drives interest in FoIP As part of the migration to VoIP, enterprises want to move their fax infrastructure to IP Direct FoIP interoperability with IP-PBX infrastructure Cisco, Avaya, Siemens, Alcatel, Shoretel, etc Leverage IP-PBX PSTN gateway or SBC infrastructure

10 DRIVER: VOICE AND FAX OVER IP VoIP alternative to business class PSTN services Analog FXO trunk replacements T1/E1 PRI trunk replacements Lower cost service advertised 25% to 70% savings of traditional PSTN services Leverages Broadband Data Connections Converged voice and data services Shared bandwidth Dynamically allocated FoIP alternative to business class PSTN services Requires T.38 fax relay method end-to-end Requires well managed network for G.711 Pass-Through method Requires tested interoperability

11 WHAT IS A SIP TRUNK? Provided by Internet Telephony Service Providers (ITSPs) Voice over Internet Protocol (VoIP) service based on Session Initiation Protocol (SIP) IP-based connection to ITSP, instead of TDM Allows ITSPs to deliver Telephone Services and Unified Communications to customers equipped with PBX facilities

12 SIP TRUNKING AND FAX This isn t a plug and play application Gateways require specific configurations Configuring with gateways and carrier Small mistake can lead to transmission failures Interoperability require expertise Integrating with existing applications

13 SIP SERVICES: NETWORK EDGE CONSTRAINTS Constraint Firewalls / NAT Traversal SIP Interoperability SIP Security Legacy Integration Demarcation Issue Many enterprise firewalls arenot capable of handling SIP traffic Many SIP-based services and SIP-based customer premise equipment arenot interoperable out of the box SIP services havesecurityvulnerabilities such as denial of service attacks, SPIT and toll fraud Many existing PBX systems are not SIP capable, or require substantial upgrades to support SIP Many SIPservices need a demarcation point or boundary between the service provider and the enterprise premise

14 THE SIP INTEROPERABILITY CHALLENGE The SIP standard leaves substantial room for interpretation and implementation choices. This leads to variance between the entities that create SIP solutions, both equipment vendors and service providers. SIP interoperability is only assured through compliance testing. "Interoperability is a challenge facing SIP trunking. There are organizations such as the SIP Forum looking to solve such problems, but at the end of the day, realized end-to-end solutions for customers with multiple vendor and service provider solutions will continue to be an obstacle. Rebecca Swensen, research analyst for IDC covering Enterprise Mobility and IP Communications Services.

15 FOIP HIGH LEVEL OVERVIEW PSTN PSTN T.30 Gateway G.711 T.38 Telephone network used to make and receive phone calls (Public Switch Telephone Network) Standard protocol for transmitting faxes across the PSTN Router designed for managing data, VoIP, FoIP, and video traffic (translates T.30 to standardsbased SIP and T.38) Standard VoIP Codecs (such as G.711) were designed for voice and allow for some latency, jitter and packet data loss ITU standard protocol for transmitting faxes across an IP network in real time

16 SIP TRUNKING TRANSPORT METHODS SIP Trunks typically use three different methods to transport fax calls G.711 Voice G.711 used for all calls (voice and fax) Pass-through Fax calls only change to G.711 from lower speed codec T.38 Fax Relay Fax calls transported using T.38 standard Fax Method T.38 Fax Relay G.711 Voice Pass-through Pros Cons Highest fax success rates can be achieved Cleanest solution from signaling and media point of view Use less bandwidth than G.711 Interoperability between different vendors Not offered by some Service Providers Most widely deployed Simplest solution Consumes a large amount of bandwidth for all calls Sensitive to impairments, no redundancy Provides bandwidth savings as G.729 voice call only upspeeds to G.711 if call is fax Interoperability between different vendors Not supported by Cisco Unified Communications Manager and Dialogic SR140 Sensitive to impairments, no redundancy

17 CONCLUSIONS SIP & FAX = T.38 MOST RELIABLE FOIP Compliant to industry standards Meets regulatory requirements / receipt confirmations Addresses network impairment issue that plagues G.711 pass-through technique Uses much less bandwidth ~ 35% of the bandwidth required by G.711 Standard for real time IP Fax defined by ITU Widely adopted by solution providers, infrastructure manufacturers and service providers Dialogic was a primary contributor to the T.38 spec

18 INSIDE THE FAX SESSION: FOIP + SIP TRUNKING Enterprise FoIP Servers T.38/ T.30 Enterprise Session Border Controller (optional) T.38/ T.30 Service Provider IP Gateway(s) T.30 Traditional Fax Machine Desktop Fax Application SIP Trunk PSTN image conversion engine Firewall / NAT Traversal image conversion engine T.30 protocol SIP Security / Interoperability T.30 protocol Multi- Function Peripheral T.38 end point protocol IP network interface T.38 data Network Demarcation IP IP T.38 data T.38 fax relay protocol IP PSTN T.30 data PSTN interface

19 ARE YOU READY? A certain level of complexity to implement fax in a SIP environment Many moving parts to consider Technical expertise needed Implementation partners assist with integrations and unique environments

20 NEXT STEPS

21 AREAS TO CONSIDER Fax Server Gateway PBX Carrier

22 QUESTIONS & ANSWERS

23 THANK YOU! InstantInfoSystems.com