SIP Trunking Best Practices

EMEA Techshare 2009 The Future BeginsSIP Trunking – Best Practices Aaron Miller Systems Engineer – SP Specialist April 1, 2009 EMEA Techshare 2009 Agenda  What‟s the big deal? – What‟s so great about SIP? The Future Begins – Why are organizations moving to SIP trunking?  SIP trunk architecture – Public and Private SIP trunks – Review of TCP/TLS vs. UDP – SES vs. SM – what‟s the right choice for me?  Get it right the first time – Aaron‟s top ten best practices – Closing thoughts EMEA Techshare 2009 Agenda  What‟s the big deal? – What‟s so great about SIP? The Future Begins – Why are organizations moving to SIP trunking?  SIP trunk architecture – Public and Private SIP trunks – Review of TCP/TLS vs. UDP – SES vs. SM – what‟s the right choice for me?  Get it right the first time – Aaron‟s top ten best practices – Closing thoughts EMEA Techshare 2009 What’s so great about SIP?  More than just telephony The Future Begins – SIP supports a wide range of services and enterprise applications • Instant Messaging • Presence Management • Voice enabled, web-based e-commerce The protocol itself is: –Extensible and Simple •Text based, efficient messages – a lightweight protocol –Stable and Secure •Been around since the late 90‟s, enables encryption, authentication and additional security extensions –Interoperable •SIP standards are being adopted by the telecommunications industry EMEA Techshare 2009 Avaya SIP Solution Architecture The Future Begins SIP MM G860 CM CM CM CM MX AVP MX Home SES Edge Aura SES Session Manager (Core Router) Home SES MM CM: SES: MM: MX: AVP: G860: Communication Manager SIP Enablement Services Modular Messaging Meeting Exchange Avaya Voice Portal High Density Trunking GW SIP SIP CMBE CMBE . cost savings are critical for businesses solution – Many greenfield installs are requesting a SIP trunking .EMEA Techshare 2009 Are we in the future yet? IP telephony The Future Begins  SIP trunking is following an adoption model similar to – Businesses on the cutting edge of technology have already adopted SIP trunking programs – Many others are in the process of trialing it in pilot – Interop testing is being worked at a frantic pace between enterprise vendors and service providers  The “Tipping Point” is now – In the down economy. g. e. and the expectation of dwindling. G. TDM revenues – Offer new services and applications to maintain profits – Incumbents need to keep smaller competitors (without TDM capabilities) out of their accounts – Provide one access method for all voice and data services . power consumption and maintenance charges – Flexibility in provisioning / design / resource utilization – Architecturally ready for future applications – Potential cost savings – Enhanced survivability – Use of high fidelity codecs.722  Service Provider motivations to move to SIP trunking – Dwindling.EMEA Techshare 2009 SIP trunking – what’s in it for me?  Enterprise benefits – Reduction on enterprise hardware The Future Begins • Reduction in footprint. 323) trunks are limited to VoIP communications between internal systems/sites • Separate TDM interfaces are required for external communication (partners/suppliers/customers) • Extra cost.Why SIP Trunking? EMEA Techshare 2009 The Future Begins Limitation & Challenges of Private IP (H.323) Trunking • Private IP (H. extra hardware. extra complexity PSTN Local & Long Distance Customers/ Partners/ Suppliers IP WAN IP Data &Telephony LAN LAN Internal Communications IP Phone IP Phone IP Phone IP Phone . 323 LAN LAN IP Phone IP Phone IP Phone IP Phone .’ independent of physical location • Save on toll charges • Prepares for future SIP solutions PSTN Local & Long Distance Customers/ Partners/ Suppliers WAN H.SIP Trunking A Single Pipe to the Cloud EMEA Techshare 2009 The Future Begins • Single IP link for voice/data • Optimize use of WAN access by consolidating voice and data services • Eliminate PSTN interfaces for long-distance and local access • Assign local telephone numbers to any ‘virtual location. EMEA Techshare 2009 Agenda  What‟s the big deal? – What‟s so great about SIP? The Future Begins – Why are organizations moving to SIP trunking?  SIP trunk architecture – Public and Private SIP trunks – Review of TCP/TLS vs. SM – what‟s the right choice for me?  Get it right the first time – Aaron‟s top ten best practices – Closing thoughts . UDP – SES vs. WAN or dedicated circuits.EMEA Techshare 2009 Flavors of SIP Trunking Service Provider Service Provider Enterprise / Contact Center Enterprise / Contact Center The Future Begins Service Provider Enterprise / Contact Center (one or multiple locations) Enterprise / Contact Center Application Servers SIP trunking can be over the LAN. . Routing to the IP address of the server is the key. EMEA Techshare 2009 A SIP Trunking Solution Customers Partners Suppliers The Future Begins Customers Partners Suppliers SIP SP G860 PSTN DS3/ISDN SP SBC Communication Manager CM Branch Edition Enterprise SBC Meeting Exchange SES Modular Messaging SIP SIP SIP Avaya one-X© Communicator Voice Portal . etc … or direct connection – Communication Platform: Server(s). video & audio conferencing. and more application integration – Endpoints: hardphones. Gateway(s). collaboration tools. Presence. SIP Proxies. mobile devices. IM.EMEA Techshare 2009 Building Blocks of SIP Trunking  Service Provider – Service Service Provider The Future Begins Server / Gtwy SBC – Session Border Controller (SBC)  Customer Premise – Edge security device: SBC. etc – Application Servers: messaging. softphones. Firewall. . an SBC. MM. or any real-time protocol converter .EMEA Techshare 2009 When do I need an SES?  An SES is required for two reasons – SIP endpoints The Future Begins – Private SIP trunking with adjuncts. VP  What about TCP/TLS vs. something is required in the “middle” to do protocol translation  What‟s the something? – That‟s up to you and the customer – it could be an SES.e. UDP? – Most (read ALL) SP‟s use UDP for their SIP trunking solutions – In the Enterprise. i. SIP trunking uses TCP or TLS – Therefore. Avaya SIP Trunking Solution CM 4.0 Introduced Direct Connect EMEA Techshare 2009 The Future Begins  For a SIP trunking solution. either an SES or an SBC is required to do the TCP/TLS conversion to UDP SIP SP  This can be done by the SES  Or this can be done by the SBC CM UDP  Or both can be used SBC SES  We‟ll discuss the differences between the SES and an SBC in subsequent slides TCP (or TLS) . EMEA Techshare 2009 SIP Enablement Services with SM ACME SBC SP SIP NW SES SM The Future Begins SES VP AES MM GW CM MX GW CM Endpoints ooo Endpoints ooo Endpoints . EMEA Techshare 2009 Key Points  Sell SIP Enablement Services (SES) for: – SIP Call Center – DO System Integration The Future Begins – Advanced SIP Telephony <1000 SIP Endpoints • Position SM Trial >1000 Endpoints – Application Integration (Voice Portal. Modular Messaging) • Easy Upgrade to SM Later if Necessary – Public SIP Trunking  SES SM Migration Path – Database Conversion Tool Included with SM – Customers Migrate from SES to SM at their own pace . UDP – SES vs.EMEA Techshare 2009 Agenda  What‟s the big deal? – What‟s so great about SIP? The Future Begins – Why are organizations moving to SIP trunking?  SIP trunk architecture – Public and Private SIP trunks – Review of TCP/TLS vs. SM – what‟s the right choice for me?  Get it right the first time – Aaron‟s top ten best practices – Closing thoughts . EMEA Techshare 2009 Ladies and Gentlemen…. The Future Begins Aaron’s Top Ten Best Practices for Deploying SIP Trunking!!! .. avaya.com/devconnect . notably 3261 – Not all vendors implements all the “MUSTs” – Many SPs have equipment from various vendors – Hence the SIP „standard‟ is not tight  Therefore it is absolutely critical that you ensure your SP offer is certified through the Avaya devConnect program  This is really not a “Best Practice” but rather a requirement  If you‟re not sure – – http://www.#10 – Ensure the SP offer has been tested in devConnect – Each have many “SHOULDs” EMEA Techshare 2009 The Future Begins  SIP is described by many IETF RFCs. EMEA Techshare 2009 SIP SP devConnect members  United States – – The Future Begins  EMEA – BT [Germany and Spain] – Club Communications [UK] – COLT [UK and Germany] AT&T BandTel – – – – Bandwidth.com Clear Channel Satellite ConneXon Telecom (911 Enable) Cox Communications – KPN [Netherlands] – – – – – – – Global Crossing Nectar (AGN Network) PAETEC (McLeodUSA) Telcordia Telepacific Verizon Business XO Communications  APAC – Singtel [Singapore] – Telstra [Australia] – TFN [Taiwan] . Avaya and SP Labs are interconnected .Relationships between Avaya and SP engineers start to develop . it follows the SP’s process in their Lab .Collaborative relationships are formed to solve integration issues SP Independent Testing onsite or remote Participation . Usually customer/opportunity driven .Exploratory testing in SP’s lab with limited interactions with Avaya Test Engineering .SP allows Avaya engineers to lead test effort .If Certification occurs.Beta releases of Avaya code are consider for testing .Unwilling to accept Avaya test results for integration certification .SP engineers take the lead role in conducting certification testing Service Provider Independent Testing Limited Participation . certification still requires testing in SP’s Lab .The SP and Avaya start discussion regard “application” fit for Avaya CPE as edge technology to SP service offers.Avaya Tests prior to going to SP lab .Avaya Lab test results are consider valid by SP however.Certification occurs in SP’s Lab with support from Avaya on-site or remotely .Sporadic often urgent demands for support when integration doesn’t work as expected .Background Evolution of Working Relationship with SPs EMEA Techshare 2009 The Future Begins Getting to the Top with SP Certification Collaborative Testing Collaboration Phase Cooperative Phase Support Phase Discovery Phase .Solution architectures are discussed as a team Avaya & SP Cooperative Testing/Certifications . EMEA Techshare 2009 #9 – Use an SBC numerous advantages The Future Begins  A Session Border Controller on the Enterprise edge brings Firewall that can handle real time packets Network Address Translation / topology hiding CLAN load balancing Protocol repair (remember those SHOULDs and MUSTs?) Call Admission Control  Service Provider SBC is to provide protection and topology hiding of their network  Best practice: Enterprise customer should deploy their own SBC  Avaya recommends: – Acme Packet Net-Net SBC . and Match) to specific CLAN.$20K Integrated Firewall Enhanced Security Hardware Price Estimate dependent on resilience . Medpros. IP Endpoints. same subnet Supported Supported Not Supported Customer SBC can terminate signaling and anchor media from Service Providers SBC. CLANs.) NAT Call Admission Control Statically configured (Pattern Load Balanced to Several CLANS. Medpros. Share*. IP Endpoints. This results in less exposure. Customer SBC then speaks directly to CLANs. same subnet Supported Layer 2. Supported Layer 2. No intelligent add/removal of non-responsive Alternate Path or dynamic load CLANs from pool.50K Not Supported Not Supported Not Supprted $5K .SES and SBC Comparison Capability Avaya SES EMEA Techshare 2009 The Future Begins Session Border Controller Inbound Call Routing Local Server Redundancy Geographic Redundancy CM uses TCP or TLS and needs to be converted to UDP for SIP Service Provider Topology Hiding (of Customer's internal addressing. Supported Supported Supported. higher layer/application level/DoS ~$30K . 2 or greater SIP trunking deployments The Future Begins  Very significant enhancements in CM 5.1.1.2 to public – This is also the load of software used in the latest devConnect and SIL testing  Fixes are not being backported to older loads – Keep service packs up to date  Ensure the SES is also on the latest release  Sign up for email notifications to get the latest and greatest PSNs/PCNs for both CM and SES – Check out http://support.com .avaya.EMEA Techshare 2009 #8 – Use CM 5. "caaat" (3 "a"characters).  .info/tutorial.EMEA Techshare 2009 #7 – Be careful with Wi[l]d(5)cards* The Future Begins  “Wildcards” or regular expressions are used when configuring the SES to match host and media maps for both inbound and outbound trunks  {N} The preceding item is matched exactly N times.  * Matches zero or more occurrences of the character immediately preceding.html . ca*t will match "ct" (0 "a"characters).* means match any number of any characters – For example. For example. Matches any single character. the regular expression . and so forth  Online “Tutorial”: Regular Expressions explained – http://www. "cat" (1 "a").regular-expressions. com Be aware that what may work for a current implementation may cause problems as additional media maps or hosts are added .com Matches sip:[email protected] • sip:[email protected] • Doesn’t match • sip:[email protected] • Matches sip:[email protected] Maps EMEA Techshare 2009 The Future Begins • Our Goal: Route Extensions 45010 – 45019 • Our Lab Host Map: ^sip:4501[0-9] ^sip:777[0-9]{3}@example.com ^sip:77*@example. which does have the capability to dynamically balance the trunk amongst different CLANs pools in a VDN  Or.#6 – Be aware of CLAN load balancing. use the Adjunct Route feature and administer the CLAN . or lack thereof a SIP trunk and a CLAN EMEA Techshare 2009 The Future Begins  The SES creates a direct one to one mapping between – No capability for the system to dynamically shift the trunk to another CLAN if there is a fault critical deployments – Potential issues with reliability and redundancy for  This can be resolved by using an SBC. 168..g.1 responsive (failure/network outage.. MM MAS) sip:2000@192. Server 2 sip:2000@192. MM) x2000 Adj. etc).1 balances across the Adjunct Servers associated with the target Adjunct System SES Combo / Home 2: Call 2 Adj..g. Sys. Server 3 sip:[email protected] .1. Sys. MM MAS) sip:[email protected]. fast-failover (~5 sec) to next Adjunct Server (if available) SES Combo / Home 5: Call 4 Adj.2 Adj. Server 1 (e. Server 1 (e..168.2 Adj.3  If an Adjunct Server is non- Adj. Server 3 sip:2000@192. MM) x2000 Adj.168.1.168. (e.1.1.1. (e.g.Adjunct System Routing Logic  SES Round-robin load- EMEA Techshare 2009 The Future Begins Adj.g. Server 2 sip:[email protected]. Example of SES load balancing using EMEA Techshare 2009 The Future Begins the « Adjunct Systems » feature SES Cluster with Network Duplication G650 with 2 CLANs 1 Communication Manager Main and Standby 5 6 2 20000 BHCC Over 4 CLANS is a N+1 CLAN redundancy SIP / Acme Packet 3 4 1 2 G650 with 1 CLANs 3 All calls to the VDN number.g. 0203285594 4 5 6 . e. work with a virtual IP address that front ends the system be on the same subnet – Network duplication offer requires both SES servers to  Also possible to have two SES EDGE (or COMBO) servers in the same enterprise – Duplication can be achieved through CM and the SP through the configuration of backup route patterns – Please note that this can cause potential issues if SIP endpoints are brought into the environment .#5 – Understand your duplication options EMEA Techshare 2009 The Future Begins  SES now offers cabled and network duplication – Both offers are similar. Example config of non-duplicated SES Service Provider EMEA Techshare 2009 The Future Begins Primary Route Pattern Secondary Route Pattern SBC SES A Combo SES B Combo G650 G650 Primary Location 1 G650 G650 ESS Location 2 . CM will never change this field. CM sends outbound call on SIP trunk to mobile phone 4) CM sets History_info field to CPN of 02077775555 5) 6) 7) x5555 SP receives call from Avaya and checks the Diversion Header. which Avaya doesn’t support SP next checks P Asserted Identity. but this is still set to the original CPN of 02012345678. 8) SP is unable to route the call. DDI 02077775555 3) Extension 5555 has EC500 set.#4 . Diversion Header SES Service Provider EMEA Techshare 2009 The Future Begins 02012345678 Calling 0207777555 5 1) Inbound call from CPN 02012345678 2) Call routed over SIP trunk to CM IP phone. this is the number of the mobile extension we’re calling. and the call is rejected .History info vs. also not recognized by the SP Finally the SP checks the FROM field. Diversion Header EMEA Techshare 2009 The Future Begins  CM 5. CSP.History info vs.2 Major enhancement to SIP trunking capabilities with support of Diversion Header  Allows successful call redirect to a SIP Service Provider (SP)  Implemented primarily for EC500 although the following is the full set of supported features: – OPTIM applications EC500. ONE-X. FMC (PBFMC or SPFMC) – Call Forwarding – Call Coverage – Call Vector Redirect  Uses the SIP Diversion Header – Partially implemented the expired IETF draft: draft-levy-sip- diversion-08 – SIP SPs tend not to support the standard History-Info header and prefer to use the Diversion Header instead even though it is nonstandard – Support of the Diversion Header is widely deployed . Diversion Header The Future Begins  New SIP Trunk Group Protocol Variation field “Send Diversion Header? y/n” (default “n”)  The diverting user must be provisioned in public unknown numbering  New SIP Trunk Group Protocol Variation field “Support Request History? y/n” (default “y”) – When the field is set to n(o) the History-Info header will not be transmitted (regardless of protocol signaling indicating the far end supports it) and CM will no longer signal support for it – The Diversion Header and the History-Info header are mutually exclusive and can both be signaled – At least one SP mandates that the History-Info header never enters their network under any condition – Changing this default should be carefully considered and done only when absolutely necessary .EMEA Techshare 2009 History info vs. com INVITE sip:[email protected] Proxy Pizza 100 TRYING Timer previously set to 2 seconds 180 RINGING Now administrable on SIP sig grp form 180 RINGING .#3 – Ensure timer on SIP Sig EMEA Techshare 2009 The Future Begins group is properly administered Aaron INVITE sip:pizza@example. EMEA Techshare 2009 Alternate Route Timer Field The Future Begins  Added in CM 5.1 to provide an administrable value  Alternate Route Timer (sec) on the SIP Signaling Group form •The range is 230 seconds •The default is 6 seconds . there may be a requirement to have dedicated inbound SIP trunks and dedicated outbound SIP trunks encourage the use of outbound trunks first trunks for fall-back purposes  Potential issues with dialplan portability may  For initial roll-out ensure there are traditional TDM .EMEA Techshare 2009 #2 – Consider a phased deployment the implementation The Future Begins  As with any new technology there may be challenges in  Depending on how the Authoritative SIP domains are setup. EMEA Techshare 2009 #1 Is QoS enabled on the network? The Future Begins How will I get feedback on bad calls? What applications does the customer use now? Will I use an SBC or an SES? What is the customer‟s technology roadmap? Does this SP support T.38 FAX? Have we tested with this SP? THINK!!! What are the implications to the dial plan? What is my duplication strategy? Do I need separate trunks for inbound and outbound? . knowledge of SIP trunking will become absolutely critical to everyone in this room design and deploy SIP trunking!  The future begins now – learn and understand how to .EMEA Techshare 2009 Closing thoughts enterprise deployments becoming more refined The Future Begins  SIP trunking is becoming more and more prevalent in  Through continuous test efforts. the protocol is  With the release of Avaya Aura.