3 Limitation & Challenges of Private IP (H.323/SIP) Trunking Why SIP Trunking?Limitation & Challenges of Private IP (H.323/SIP) TrunkingPrivate IP (H.323/SIP) trunks are limited to VoIP communications between internal systems/sitesSeparate TDM interfaces are required for external communication (partners/suppliers/customers)Extra cost, extra hardware, extra complexityCustomers/ Partners/ SuppliersPSTNLocal &Long DistanceTDM interfacesExternal CommunicationsTDM interfacesIP WANExternal CommunicationsIP Data &TelephonyLANLANInternal CommunicationsIP PhoneIP PhoneIP PhoneIP Phone
4 SIP Trunking A Single Pipe to the Cloud Single IP link for voice/dataOptimize use of WAN access by consolidating voice and data servicesReduce PSTN interfaces for long-distance and local accessAssign local telephone numbers to any ‘virtual location,’ independent of physical locationPrepares for future SIP solutionsCustomers/ Partners/ SuppliersPSTNLocal &Long DistanceSIPSIPWANH.323LANLANIP PhoneIP PhoneIP PhoneIP Phone
5 Flavors of SIP Trunking Service ProviderEnterprise / Contact Center (one or multiple locations)Enterprise / Contact CenterApplication ServersPublic SIP TrunkingPublic SIP Trunks are used to provide access to the PSTN through SIP-enabled Service Providers such as AT&T and Verizon Business.Communication Manager 4.0 and later support direct SIP trunking to SIP Service Providers without the SIP Enablement Services (SES).If the SIP Service Provider does not support TCP or TLS, Communication Manager will need to interface to a Session Border Controller such as the Covergence SBC to perform protocol conversion from TCP or TLS to UDP. Communication Manager supports SIP over TCP and TLS whereas most SIP Service Providers only support UDP.For U.S. Service Providers, DevConnect testing for Public SIP Trunking is highly recommended, but not required.For non-U.S. Service Providers, DevConnect testing for Public SIP Trunking is required.Private SIP TrunkingPrivate SIP Trunks are used to network Communication Manager to other SIP devices within the Enterprise such as other Communication Manger instances or even third-party PBXs.Communication Manager Private SIP Trunking to 3rd party (non-Avaya) SIP devices, PBXs, gateways, applications, etc. require CM product management approval. This is true regardless of whether there is an Avaya SES or a SIP Proxy in an element such as a Session Border Controller in the configuration. Product management will take the following into consideration in making its approval decision:Customer relationshipBusiness opportunity/revenue potential3rd party device/manufacturerPrior experience with similar configurationsSuccessful testing via Proof of Concept lab, System Interoperability Test Lab, or DevConnect labSIP trunking can be over the LAN, WANor dedicated circuits.
6 Building Blocks of SIP Trunking Server / GtwyService ProviderSBCService ProviderServiceSession Border Controller (SBC)Customer PremiseEdge security device: SBC, Firewall, etcCommunication Platform: Server(s), Gateway(s), SIP Proxies, etcApplication Servers: messaging, video & audio conferencing, collaboration tools, IM, Presence, and moreEndpoints: hardphones, softphones, mobile devices, application integration… or direct connection
8 SIP Trunking - Overview SIP phone (future)SIPProvider(s)IP DECTIP phone (46xx/56xx/T3 IP)T1/E1/ISDNProvider(s)Digital phone (24xx/54xx/T3)IP Office acts as a SIP gatewayAnalog phoneAnalogProvider(s)No need for a SIP phone to make/receive a SIP callSIP Trunks are licensed in increments of 1, 5, 10 and 20 (up to 128 channels)Benefits – Lower operational costsLower cost/flat rate calls with Internet Telephony SPsOffers back-up to Analog/Digital Trunks + Number PortabilityFuture-proof your investment
9 SIP Trunking – IP Office Interoperability Internet Engineering Task Force (IETF) RFC SupportAll the major RFC’s are supported to ensure SIP interoperability with most Service ProvidersSome of the vendors that we have performed Interoperability with;North America:AGN (US)AT&T/SBC (US)Bandtel (US)Cbeyond (US)Curry IP Solutions (US)XO (US)FWD / Free-World Dialup (US)Global Crossing (US)Les.net (Canada/USA)
10 Will CM Support SIP Trunks from XYZ SP? DevConnect compliance testingFor U.S. SIP SPs, no longer a requirement but still HIGHLY RECOMMENDEDNo change to non-U.S. Service Providers; DevConnect compliance testing requiredContact:Professional Services engagement for enterprise customersIn-region R&DContact: In-region Product Manager
11 SIP SP – DevConnect Members United StatesAT&TBandTelBandwidth.comClear Channel SatelliteConneXon Telecom (911 Enable)Cox CommunicationsGlobal CrossingNectar (AGN Network)PAETEC (McLeodUSA)TelcordiaTelepacificVerizon BusinessXO CommunicationsEMEABT [Germany and Spain]Club Communications [UK]COLT [UK and Germany]KPN [Netherlands]APACSingtel [Singapore]Telstra [Australia]TFN [Taiwan]
12 Communication Manager systems ArchitectureHigh Density Gateways(Avaya G860)Service Provider3rd partysystemsVoicePortalSIPProxyOutsourcerBusiness ApplicationsBranchAgentsRemote AgentsCommunication Manager systemsConferencingUnified Messaging
15 The Enterprise Infrastructure BLarge and/or Backup SitesG650, ESSIP PhoneAvaya Communication ManagerG650 GatewaysALANIP WANCMedium SitesG450’sS8300 LSPThe primary server contains all the licensingSingle system to manage and maintainView system wide trunk informationManage call routing based on location (best service routing).All translation are automatically synchronized with alternate survivable servers in the system.ANY GatewayEDigital/AnalogDMicro SitesG250S8300 LSP or basic survivabilitySmall Sites G350S8300 LSP or basic survivability
16 Building a SIP Trunk (Drag & Drop) Service ProviderApplication Notes for Configuring Avaya Communication Manager SIP Trunking to a Typical SIP Service Provider – Issue 1.1Session Border ControllerAvaya SIP Enablement Server (SIP Proxy)Avaya Communication Manager (IP-PBX)
17 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.Understand that the URI is the routable portion of the request where the To is the Logical recipient of the request and the From is the Initiator of the request.