10 fn s12
TRANSCRIPT
SIP still connecting the Islands
Richard ShockeyChairman Board of Directors SIP Forum
Shockey Consulting
2427 Silver Fox Lane
Reston, VA 20291
Voice +1 703 593 2683
Skype/AIM/LinkedIn/Facebook – rshockey101
Background
• Founded in 2000
• Leading Non-‐Profit IP Communications IndustryAssociation
• Membership comprised of Corporate “Full Members”that support the Forum and pay annual dues,Academic Institutions and Individual “Participant”Members (free membership category)
• Help make SIP work better
SIP Forum Full Member Companies
Progress ?
The Evolution of Enterprise VoIP• First : Replace the RJ-‐11
– Immediate gains in CAPEX as single wiring harness simplifies campusmanagement.
– Greenfield ROI – NO Brainer
• Second : Replace the TIE Lines– Integrate Enterprise wide Dial Plan Management into single IP
Network. Immediate OPEX gains.
• Third : Replace the PRI (Today) SIP Trunking– All IP E2E
• Fourth : Direct Peering with Business Partners– The 40-‐40-‐20 rule
• Fifth : Seamless Campus/Mobility Integration– Its not fixed Mobile Convergence its Substitution
PBX to SIP Service Provider (SSP)SIP Trunking
• Increasing progress.• Market awareness increasing monthly ..
• Better Faster Cheaper• ROI is clearly demonstrable• 40% savings increasingly reported
• SIPforum’s SIPconnect 1.0 and soon 1.1• http://www.sipforum.org/sipconnect
• Carrier support increasing among Incumbents, CLEC’s andparticularly MSO’s (Good numbers)
• So Long as PSTN (PRI’s) is used as the inter-‐VOIP “default”network service will be degraded as it must transversemultiple networks
Why SIPconnect?
SIP is nearly 150 individual “Request for Comments” standardsfrom the IETF
– Nearly 100 more are in the pipeline
• Industry needed a standard implementable “profile of SIP”
• Users needed brand awareness of SIP Trunking features andbenefits
• Maintain “Voice Centric” focus
• Strengthen MUST vs SHOULD ‘requirements to implement’for both PBX and Service providers
• Create forum for interoperability compliance
• Class 5 is dying ( its about time) though the FCChasn’t been told yet. Title 4?
• Collapse of Nortel has put Carriers on notice• So what are you going to do with those DMS 250 / 500’s– End of Life letters for 5ESS?
• SIP networks are still being “Dumbed Down” at the point ofcarrier interconnection
• Considerable progress however.
SIP Service Provider to SIP ServiceProvider SIP Trunking
Service Provider to Service ProviderSIP Trunking
• GSM Operators (IPX/Pathfinder) – InternationalInterconnects (i3Forum) and the North American CableOperators (CableLabs) are in general technicalagreement.
• Conversion held up due to substantial capital constraints.– The economics in Telecoland not healthy even in
mobility.• CAPEX trap. Mobile Data Backhaul dominates.
• TN routing data Carrier ENUM initiatives are the loomingissues– SIPD base routing still dominates ( Who is the Carrier of Record?)
FAX• Ongoing issue• Contrary to popular opinion FAX is still a
essential communications service and is actuallyincreasing in popularity due to regulatoryrequirements ( HIPAA – SOX )
• Sort of works with G.711 – G.729 (no way) orwith any HD voice codec.
• SIPforum Fax task group coordinating withi3Forum.
E.164 resolution• This is not a ENUM lecture ..
• Advanced service delivery based on E.164numbering will not occur without killing offTCAP/SS7 eventually.
• Good news its in the field, well supported and it works.MMS success story
• The future of SIP and the teleco industry istied to making the Voice Service relevant. HDvoice needs a new signaling model.
OSS/BSS problems• Architecture is sexy billing systems are not.• Carriers are Spending Millions to accommodate SIP
Trunking and in the process canalizing existing revenue.• Number Routing Databases not standardized
– Provisioning IP data in intra vs inter carrier routing tables.
• In general operational issues related to OSS/BSS arebeing lost in the shuffle.
• CONCLUSION : We still have a long way to go.
The real industry problem is Layer 8(financial)
• Money is the answer what is the question ?
ARPU