2. VoIP enabling legacy products David Duffett, Aculab

3. Our agenda  Defining the challenge  Gateways; principles and practice  Pitfalls to avoid  Implementation advice

4. My job for the next few minutes  Keep you awake and engaged!  Maintain non-commercialism  Raise the right questions to enable you to make the best choices when VoIP enabling your legacy equipment  But first…

5. VoIP: where are we now? Time Expectations Hype Adoption Scepticism

6. Defining the challenge PSTN Primary rate link IP network VoIPVoIP

7. Gateways  Used to connect dissimilar interfaces Circuit switched equipment Packet switched network Gateway A – law  – law G.711 G.723.1 G.729 (A+B) Q.931 TDM SIP RTP Packet switched network H.323 RTP

8. Traditional gateway Call control Media H.323 SIP RTP T1 signalling T1 bearers

9. Decomposed gateway Media gateway controller Media gateway H.323 SIP RTP T1 signalling T1 bearers Media gateway RTPT1 bearers Media gateway RTP T1 bearers H.248/MEGACO/MGCP

10. Gateway: choices  H.323 or SIP or BOTH?  Gatekeeper  Registrar, proxy  T1, E1 or both protocols?  Codecs  Proprietary or open standards?

11. Gateway: considerations  Protocol capabilities  Existing equipment  Current network provider  Potential solutions  Quality of Service  IP network provider  Type of traffic  Conferencing, ASR, SVI

12. Gateway: considerations  What other work might the solution do?  Routing  CLI/DDI authentication  Number portability  Address translation  Billing information

13. Gateway used for routing IP network PSTN Legacy interface PBX ACD Gateway

15. Gateway: buy or build?  Flexibility  Cost  Business objectives  Skill levels

16. Gateway: buy or build?  Support requirements  Protocol support  ROI

17. Gateway  If your solution needs to be custom made be sure to use open standard components  Interoperability is key

18. Pitfalls to avoid  Don’t get intimidated by your existing:  Equipment provider  Network provider  Don’t be a CHEAP JERK!  Buying the cheapest off the shelf option may leave you in trouble Reliability Changes

19. Implementation advice  Think RESPONSIBILITIES  You  Network provider  Equipment (component or solution) provider  Think FUTURE  How will things change Protocols Scaling

20. Implementation advice  Think SOLUTIONS  Don’t be afraid to ask questions, and to question the answers you get  There is a rich supply of people to help you here at the conference

21. Haben Sie etwa Fragen? Cuestiones? Any questions? Quel questionnes? Haben Sie etwa Fragen? Cuestiones? Haben Sie etwa Fragen? Cuestiones? Any questions? Quel questionnes? Cuestiones? Quel questionnes? Any questions?

22. Summary  Defining the challenge  Look at the precise functionality required  Gateways  Choices and considerations  Pitfalls  Don’t get hustled, and don’t be a cheap schmuck  Implementation advice  THINK first, spend next

23. Thank you David Duffett david.duffett@aculab.com Stand no. 303