Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

Solving the BYOD Problem with Open Standards

  • Soyez le premier à commenter

  • Soyez le premier à aimer ceci

Solving the BYOD Problem with Open Standards

  1. 1. Solving the BYOD Problem with Open StandardsSession 4:Hosted by John Drolet eZuce Vice President Sales / Channel OperationsMarch 10, 2013 / Bentley Univesity / Boston MA
  2. 2. 2Session Title & Abstract;Solving the BYOD Problem with Open StandardsEffective adoption of a BYOD policy is driven by an open system and openstandards. We will talk about each along with the human element of theBYOD challenge.
  3. 3. Let’s define the BYOD dilemma and the opportunityIn 2013 there will be more mobile devices than people.Tech Flash - Washington Post Feb 27, 2013, 9:46am EST* “For the first time, the number of mobile devices this year connected to the Internet globally will surpass the worldwide population. With the rise in tablets, more people own multiple mobile devices, leading to the surge. While there were 3.2. billion mobile users by last count, the number of devices is expected to climb to 7.4 billion this year, up from 6.8 billion in 2012. Worldwide population, meanwhile, is slower growing at roughly 7.1 billion.”*
  4. 4. Some of the BYOD Driving Factors• Single number reach and efficiency• Unified applications push integration – Single log on – One voicemail box – Click to dial regardless of device being used – Aps should be portal and connect into the Enterprise work flow. • Need to be cautious that cellular providers don’t silo the offer.• Executing on the promise of interoperability – Hardware should migrate• Intellectual property issues surrounding use of personal cell phones in the enterprise. – Case study published featuring major drug company
  5. 5. eZuce and openUC are built for the BYOD reality• eZuce openUC™ allows the enterprise or institution to – We believe… – …in building an enterprise on standards like SIP/XMPP/WebRTC – …with the backbone SIP/XMPP based applications and end user devices and clients can interface easily. – …in and will participate in the enormous innovation at the client level, especially on mobile and tablet devices. Enter webRTC.• We don’t believe, there is a good excuse to not follow the standards
  6. 6. eZuce and openUC are built for the BYOD reality> An Open Platform with strong support of standards will provide the platform for integration today and in the future.> Let’s discuss the BYOD with our guests
  7. 7. Panel DiscussionErnesto Calderon – North America Support Manager, GrandstreamSteve Johnson President - Ingate
  8. 8. GXP1100/1105 • Single SIP account • 4 XML programmable soft keys • HD audio • Single network port • Integrated PoE (GXP1105 only)Grandstream Networks, Inc.
  9. 9. GXP2124v2 • 4 lines keys and 4 SIP accounts • 24 + 4 BLF hard keys • 5-way conferencing • HD Audio • Electronic Hook Switch Support for Plantronics headsets • 2 x 10M/100M/1000M Ethernet ports with integrated PoE, RJ9 headset jackGrandstream Networks, Inc.
  10. 10. GXP2200 Android ™ Multimedia Phone• Android v2.3, 4.3” capacitive touch screen LCD• 2 x 10/100/gigabit network ports with integrated PoE• Bluetooth• Up to 6 SIP accounts• Electronic Hook Switch• HD Audio Grandstream Networks, Inc.
  11. 11. Grandstream Networks, Inc. VoIP Product Lines
  12. 12. The SIP trunking enabler Solutions for SIPWe enable SIP communication for business
  13. 13. The State of SIP 210 IETF RFCs govern SIP SIP Forum is establishing profiles  SIP Trunking – SIPConnect 1.1  Video Relay Services  User Agents SIP is stable, but Vendors and service providers can still choose how to support SIP Trunks Commonality will come in time For now Session Border Controllers can help resolve differences
  14. 14. Why does the Enterprise need an SBC Interoperability Security Other Normalization of SIP  NAT and Firewall traversal  Far End NAT Traversal  To enable placement of the PBX behind the   Back to Back User Agent Disaster recovery firewall allows the SBC to normalize  Quality of Service signalling  Security through deep packet  Encryption inspection  To keep the PBX secure  Demarcation Point  To monitor call quality with MOS  Intrusion Detection / Prevention scores  To prevent Denial of Service Attacks  Diagnostics  Authentication  Logging and Wire Shark traces  To prevent toll fraud The E-SBC puts the enterprise in control of its SIP implementation
  15. 15. Network Installation Options 16
  16. 16. Ingates Product Family SIParator® 95/96/97 Firewall® 2950/2960/2970 SIParator® 51/56/66 Firewall® 1510/1560/1660 1800/3000/8000 Calls* 4 500 Mbit/s 300 000 Packets/s SIParator® 21 150/400/1000 Calls* Firewall® 1210 500/700/900 Mbit/s Software 28 500/50 000/90 0000 Packets/s Firewall/SIParator ® 25 - 10 000 Calls*Ingate IX78 50 Calls* 200 Mbit/s Can be installed on a 10 000 Packets/s virtual machine or 50 Calls* natively x86 Linux Servers 90 Mbit/s (industry-standard PC architecture) 17 000 Packets/s *) Calls = Concurrent RTP Sessions = SIP Trunks 17 17
  17. 17. Please contact me at any time: Steve Johnson President Mail & SIP: steve@ingate.com Direct: 1-603-883-6569
  18. 18. Panel DiscussionQuestions and answersQuestion 1: A call is being set up between a Grandstream phone and running through anIngate SBC. How does the SIP standard insure that the call will be crystal clear?Question 2: Ingate; How easy is it to qualify a SIP trunking provider working with Ingateequipment?Question 3: Grandstream; Does the Android operating system being built into your phoneindicate the war is lost and the desk phone is going away? Or is it a complimentaryevolution?Question 4: Audience?

    Soyez le premier à commenter

    Identifiez-vous pour voir les commentaires


Nombre de vues


Sur Slideshare


À partir des intégrations


Nombre d'intégrations









Mentions J'aime