Transcript Commetrex_Three Phases of FoIP Deployment

Commetrex Corporation
The Three Phases of FoIP
Deployment
Mike Coffee
CEO Commetrex
Co-Chair SIP Forum
FoIP Task Group
[email protected]
A Marriage of Necessity
Carriers
Vendors
Fax Relay
T.38
Emitting/on-ramp
Gateway
PSTN
Transmitting
Fax
Receiving/off-ramp
Gateway
Packet
Network
Real-Time
Packet-Based
Fax
PSTN
Receiving
Fax
T.30
http://www.commetrex.com
3
T.38 Deployment Phases:
• Phase I, intra-enterprise: 1998-2008+
• Phase II, SIP trunking: 2007+
• Phase III, tandem carriers: 2011+
Intra-Enterprise
Fax Terminal
T.38
Phase I
ATA
PSTN
Enterprise LAN
Enterprise
Gateway
FoIP Fax
Server
And Now…Bring on The
ITSPs & Carriers!
T.38
Phase II
IP
Carrier
Fax Terminal
ITSP
IP
Carrier
ATA
IP
Carrier
Enterprise LAN
ILEC
Router
FoIP Fax
Server
Fax Terminal
Separating the Issues
SIP:17705555555
@12.34.456.78
FoIP Fax
Server
FoIP Fax
Server
SIP & T.38
Voice Is Easy!
• Voice is generally the default
• Agree on a codec
• Enable the media stream
• Take care of jitter-buffer management
• Get rid of echo
• You’re done!
• Call set-up timing not critical.
But in Fax…
Timing is everything.
FoIP…It’s About Time
• Computer-to-computer protocol (T.30)
• Synchronous modems
• Media stream, which begins in G.711,
•
wants to be renegotiated and switched to
T.38
Timing is everything!
Phase III: Tandem-CarrierBased Fax
Fax Terminal
ILEC
PSTN
IP Carrier
IP Carrier
ATA
ITSP
IP Carrier
TDM Carrier
Fax Terminal
ILEC
PSTN
ILEC
PSTN
ITSP
IP Carrier
Fax Terminal
Fax Terminal
ATA
So…What about testing?
• Many networks are untested for FoIP.
• Many firewalls and other network elements
•
are not correctly configured.
Excessive signaling delay remains
undiagnosed
Plan Your FoIP Trip
Some Results:
In a Recent Broadcast Test
200 out of 2000 calls
had late-arriving T.38 re-Invites
leading to fax failures.
Outbound to ITSP
Remote off hook
T.38 re-Invite
G.711 Audio
Caller
DIS
Callee
Point of no return
T.38 re-Invite
here. Bye-bye fax.
So…
Can our industry respond
effectively to these problems?
SIP Forum FoIP
Task Group Goal:
Develop and publish the guidelines
(recommended practices) that will
reduce the implementation
problems that are today hindering
IP-based fax deployments in
carrier-based applications.
Copyright © 2010 SIP Forum
The i3 Forum said “YES”
These Carriers said “Yes”!
•
•
•
•
•
•
•
Deutsche Telekom
iBasis
SFT
OTEGLOBE
TATA
Telkom SA
WIS
•
•
•
•
•
•
Telekom Italia
Sparkle
Telecom Poland
Telefonica
Reach
FSB
Telenor
Testing Report
INTERNATIONAL INTERCONNECTION
FORUM
FOR SERVICES OVER IP
(i3 FORUM)
www.i3forum.org)
Workstream “Technical Aspects”
(
Testing Report
Fax over IP service
(September 2011)
I3 Testing Results
Using international-carrier SS7-based
routing, call-completion rates were
nominally 50%.
Next Steps
Best Practices Recommendations
In Q4
Intelligent Routing
• User=fax
• ENUM
User=Fax
RFC 3261, section 25.1, URI Parameters
user-param = "user=" ( "phone" / "ip" / other-user)
So, other-user = fax.
ENUM: Tells you where you
want to go
• Convert E.164 numbers to DNS lookup
• Returns URI of user’s ENUM record
• Record contains info on all services
• HD voice is driver
• But what about fax?
• Used for IP-only routing
SPEERMINT helps you get
there
• Session PEERing for Multimedia
•
•
•
INTerconnect
Part of Real-Time Applications and
Infrastructure study area (ENUM, SIP,
Sigtran, etc)
Indentify, signal, and route real-time
communication sessions
Picks up where ENUM leaves off
SIP Forum & i3 Forum
FoIP Task Groups…
Will We Solve the
Phase II & III problems?