1. © 2009 Avaya Inc. All rights reserved. Introduction to SIP Trunking Alan Klein Consulting Systems Engineer alanklein@avaya.com February 2009

2. © 2009 Avaya Inc. All rights reserved. Flavors of SIP Trunking Service Provider Enterprise / Contact Center (one or multiple locations) Enterprise / Contact Center Application Servers SIP trunking can be over the LAN, WAN or dedicated circuits. SIP trunking can be over the LAN, WAN or dedicated circuits.

3. © 2009 Avaya Inc. All rights reserved. Building Blocks of SIP Trunking Service Provider –Service –Session Border Controller (SBC) Customer Premise –Edge security device: SBC, Firewall, etc –Communication Platform: Server(s), Gateway(s), SIP Proxies, etc –Application Servers: messaging, video & audio conferencing, collaboration tools, IM, Presence, and more –Endpoints: hardphones, softphones, mobile devices, application integration Service Provider SBC Server / Gtwy … or direct connection

4. © 2009 Avaya Inc. All rights reserved. Building a SIP Trunk (Drag & Drop) Service Provider Avaya Communication Manager (IP-PBX) Avaya SIP Enablement Server (SIP Proxy) Session Border Controller Application Notes for Configuring Avaya Communication Manager SIP Trunking to a Typical SIP Service Provider – Issue 1.1 http://www.avaya.com/master-usa/en- us/resource/assets/applicationnotes/genspsiptrk-v1-1.pdf

5. © 2009 Avaya Inc. All rights reserved. Service Provider SIP Proxy Architecture 3rd party systems High Density Gateways (Avaya G860) Voice Portal Outsourcer Communication Manager systems Branch Agents Remote Agents Business Applications Conferencing Unified Messaging

6. © 2009 Avaya Inc. All rights reserved. CM to ITSP (Outbound call) If the Far-end Domain is filled out then the “Request URI” and the “To” headers will reflect the information. The Public-unknown numbering plan inserts the From extension. The Near-end Clan for the signaling group has an ip- network-region authoritative domain that will appear in the “From” header.

7. © 2009 Avaya Inc. All rights reserved. 7 © 2007 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA

8. © 2009 Avaya Inc. All rights reserved. The Enterprise Infrastructure Alan Klein Consulting Systems Engineer alanklein@avaya.com February 2009

9. © 2009 Avaya Inc. All rights reserved. LAN Avaya Communication Manager G650 Gateways Digital/Analog IP Phone IP WAN A E B D C The Enterprise Infrastructure Micro Sites G250 S8300 LSP or basic survivability Small Sites G350 S8300 LSP or basic survivability Medium Sites G450’s S8300 LSP Large and/or Backup Sites G650, ESS

10. © 2009 Avaya Inc. All rights reserved. Limitation & Challenges of Private IP (H.323/SIP) Trunking IP WAN PSTN Local & Long Distance PSTN Local & Long Distance IP Data &Telephony Private IP (H.323/SIP) trunks are limited to VoIP communications between internal systems/sites Separate TDM interfaces are required for external communication (partners/suppliers/customers) Extra cost, extra hardware, extra complexity Customers/ Partners/ Suppliers LAN TDM interfaces Why SIP Trunking? IP Phone External Communications Internal Communications

11. © 2009 Avaya Inc. All rights reserved. SIP Trunking A Single Pipe to the Cloud WAN PSTN Local & Long Distance PSTN Local & Long Distance H.323 SIP Customers/ Partners/ Suppliers LAN IP Phone Single IP link for voice/data Optimize use of WAN access by consolidating voice and data services Reduce PSTN interfaces for long-distance and local access Assign local telephone numbers to any ‘virtual location,’ independent of physical location Prepares for future SIP solutions

12. © 2009 Avaya Inc. All rights reserved. Components of SIP Trunking Solution SIP Modular Messaging Voice Portal CM Branch Edition Communication Manager SES Meeting Exchange SBC DS3/ISDN G860 IP Office Customers Partners Suppliers Avaya one-X © Communicator ITSP PSTN SIP Customers Partners Suppliers

13. © 2009 Avaya Inc. All rights reserved. 13 © 2007 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA