The Deployment_MSTeams _Ribbon SBC on CORE
- 1. COLLABORATE SEAMLESSLY WITH MICROSOFT TEAMS, A TECHNOLOGY INTEGRATION
- 2. INTRODUCTION ABOUT TECHNOLOGY EVOLUTION FROM LEGACY SYSTEM TO VOIP AND COLLABORATIVE SOLUTION. Traditional landline phones rely on the Public Switched Telephone Network (PSTN), which transmits voice calls over dedicated copper wires. Voice over Internet Protocol (VoIP) is a technology that allows you to make and receive phone calls over a broadband internet connection instead of a traditional analog phone line. The IP phones with H323 and SIP were introduced to make and receive calls with least cost models over Internet .
- 3. Cloud Telephony - pay as you go model. Cloud Telephony Solutions Transform communication infrastructure with cloud telephony solutions. Empower business with scalable, reliable, and feature-rich communication capabilities. • Virtual PBX Systems: Replace traditional phone systems with cloud-based PBX solutions for flexible call routing, voicemail, and extensions. • Unified Communication Platforms: Integrate voice, video, messaging, and collaboration tools into a unified cloud-based platform for seamless communication. • Call Center Solutions: Enhance customer interactions with cloud-based call center software, including IVR systems, call routing, and analytics. Office 365 Solutions Access a comprehensive suite of productivity tools, including Microsoft Word, Excel, PowerPoint, Teams, and more, with cloud-based storage and collaboration features.
- 4. Hybrid telephony solution, on-premises SBC and Microsoft Teams integration
- 5. Overview of Ribbon SBC portfolio
- 6. UNDERSTANDING EMS, EMA & PSX COMPONENTS IN RIBBON SBC • An Element Management System (EMS) manages specific types of one or more network elements within a telecommunication management network (TMN). It’s the job of the EMS within a network element to manage functions and capabilities, but not necessarily traffic. The EMS communicates upward to higher-level systems of network management (NMS), in order to manage the traffic between itself and other network elements. The EMS is a critical part of the telecommunications management solution. One reason is that the EMS is the only exposed network element within the TMN and acts as the mediator of the information. It also controls the network elements within a network management system. R • Platform Manager functionality referred to as EMA Platform Mode, or simply Platform Mode. The two modes now available in the EMA are: EMA Mode (default mode when accessing EMA) EMA Platform Mode EMA consists of the following component's:- EMA Platform Mode - Login Window EMA Platform Mode - Monitoring EMA Platform Mode - Administration EMA Platform Mode - Troubleshooting • Ribbon's Policy and Routing Server (PSX) is a centralized policy and routing solution that unifies policy and routing decisions for Session Border Controllers (SBCs) in an organization. PSX can help manage sessions for multiple services, including unified communications, collaboration and conferencing, contact centers, PBX migration, and SIP trunking. It can also simplify dial plan management and call routing decisions for both internal and external calls.
- 7. SBC LICENSES MODELS Node-Locked Licensing Network-Wide Licensing Network-Wide Domain Licensing •Node-Locked Licensing - This is the traditional and most common method of licensing on SBC. All sessions and features are locked to a specific SBC node which is identified through its hardware serial number or Virtual Machine Universal Unique Identifier (UUID). •Network-Wide Licensing - Ribbon provides a network-wide licensing (NWL) option for customers who do not want licensing capacity to be defined on each node level. Instead, they purchase a total number of sessions, and a feature set intended to meet the requirements of their entire network. Note, NWL uses the same underlying node-locked licenses, but additional ‘burst’ licenses are installed to allow flexibility in capacity. •Network-Wide Domain Licensing – Network-wide domain licensing (NWDL) licensing is offered to SBC SWe cloud deployments where SBC instances may be brought up and down dynamically based on traffic. In this model, a domain license is bound to the domain through public/private key-pairing and it defines the features and capacity allowed for all nodes within the domain. When a new SBC node is brought up, it can leverage licenses from the domain pool.
- 8. About media bypass with Direct Routing Media bypass enables you to shorten the path of media traffic and reduce the number of hops in transit for better performance. With media bypass, media is kept between the Session Border Controller (SBC) and the client instead of sending it via the Microsoft Phone System. Microsoft Teams media bypass is a setup that lets voice traffic flow directly between Teams users and a company's session border controller (SBC). This avoids sending voice traffic over the internet to the Microsoft cloud if teams client is in the same network as the SBCs.
- 10. Deployment of Microsoft Teams Direct routing
- 11. Teams side configuration on SBC (SBC Side) a. IP Interface Group b. Zone c. SIP Signaling Port d. DNS Group e. Packet Service Profile (PSP) f. IP Signaling Profile (IPSP) g. SIP Trunk Group h. IP Static Route Configuration on PSX - Teams Side Configuration 1. Creating Gateway 2. Creating Global SIP Domain Name 3. Creating IP Peer 4. Creating Routing label 5. Creating Standard Routing 6. Creating Local Ringback Tone Profile (LRBT Profile) 7. Creating IP Signaling Profile (IPSP Profile) 8. Creating Packet Signaling Profile (PSP Profile) 9. Configuration Required for Teams Media Bypass 10. Create Zone 11. Configure Teams Trunk Group Allowing of Firewall ports Network configuration Provide public IP for SBC FW Create a new dedicated one-to-one NAT on the perimeter firewall: Public IP <> Pkt0 Ifc Internal Zone Private IP FW TPAR application Public FQDN for SBC Ribbon vendor Assess and validate SBC/PSX proposed configurations Generate and apply certificate to be used for TLS encryption on the SIP trunk a. TLS Configuration b. Generating a CSR with OpenSSL c. Generate required certificates d. Attach TLS Profile to SIP Signaling Port High Level configuration for Teams DR routing
- 12. There really is no default interface group that comes with the system. So we create an interface group to hold one or more IP addresses, that get assigned to one or more physical ports. Typically, one IP Interface Group contains only one IP Interface (IP Address). Keep in mind that an IP Address Interface Group is Address Context specific. There are other objects, which we’ll discuss in later modules, that point to these interface groups. You can have up to 2,048 interface groups per SBC 5000 Series and up to 4000 in the case of the SBC7000.
- 13. ZONE •A Zone is permanently bound to an Address Context •Zones are normally allocated by customer, carrier, organization, or service level •Zone Objects Include − IP Peer(s) (Signaling Endpoints) − SIP or H323 Trunk Group(s) − SIP Signaling Port / H323 Signaling Port A zone in its most basic format represents the customer premise. This means that it will contain information related to how other SIP devices will be able to interact with the SBC in this Address Context. The Zone will then be a container for this information. Also, a Zone is bound to a particular Address Context, and can not belong to any other Address Context. Zones are normally allocated either by a customer, carrier, enterprise organization, or service level agreement. A maximum of 2048 zones can be allocated in the SBC5000 series and 4000 in the SBC7000.
- 14. SIP Signaling Ports deal with SIP signaling, setting up and tearing down calls between customers endpoints over IP Trunk Groups. Now SIP Signaling Ports are bounded to Zones, this means that a single SIP Signaling Port can only belong to a single Zone. Additionally, a single SIP Signaling Port can only point to one IP Interface Group. That IP Interface Group has to be in the same Address Context as the Zone that the SIP Signaling Port belongs to. Typically, we have one SIP Signaling Port per zone. SIP Signaling Ports are capable of supporting multiple transport protocols or a single protocol. For example, you might have a Signaling Port that only does SIP UDP. It is possible to enable TCP and TCP/TLS as well, making it more versatile and robust dealing with different endpoints on a customer premise. A maximum of 2048 SIP Signaling Ports can be allocated in the SBC5000 series and 4000 in the SBC7000
- 15. Trunk Groups can either be SIP or H323 and they’re usually associated with the media traffic of a customer endpoint. Multiple SIP Trunk Groups can be hosted in the same Zone. An Ingress SIP Trunk Group is selected by matching the IP address of the signaling peer on the customer side to an entry in the Ingress IP Prefix table associated with that trunk group. This limits who can use the trunk group. The IP Prefix table is provisioned when you build the Trunk Group. It’s one of the parameters inside of a SIP Trunk. You can have a mix of IPv4 and IPv6 prefixes that can be added to the same
- 16. An IP Peer is an endpoint. When we’re routing traffic to a customer, that traffic is associated with a SIP Signaling Port and a trunk group and a next hop. That next hop object is an IP Peer. You can have one or more IP Peers in a Zone, just like you can have multiple trunk groups. The primary purpose of this object is to facilitate outbound call routing and reference to this object is returned by the policy server (embedded routing engine) to indicate the IP address of the next hop for the call. For inbound calls we also search an IP Peer table in case there are any special features allocated to that Peer. This will be explained later in the provisioning module. Endpoint traffic coming inbound to the trunk group may or may not have an entry in the IP Peer Table.
- 17. Here we have two networks, one belonging to our Internal Network (that is our trusted side) and one belonging to an External network like a Carrier (Untrusted). These networks are separated by a Session Border Controller. Then there will be some basic objects that would be configure on both sides in order to allow the SBC to talk to both networks. For whatever reason, the decision was made to create use the default Address Context for our internal side and add a new Address Context outside of the default for the external side. Then, in Address Context default we created: • IG_INTERNAL, which will contain an IP interface named IF_INTERNAL. This interface is reachable from the Internal Network and might or not be associated to a VLAN. • ZONE_INTERNAL, which contains: • PEER_INTERNAL, the next hop for the traffic in our internal network • TG_NTERNAL, to be used for the media traffic on the internal side • SIG PORT, the signaling port that the SIP devices in the internal network will talk to. In the external side we created: • IG_EXTERNAL, containing IF_EXTERNAL. This interface should be reachable from the External network • ZONE_EXTERNAL contains: • PEER_EXTERNAL, which is the next hop for the traffic associated to this zone • TG_EXTERNAL, that will be associated to the media in this external side of our deployment • SIG PORT, which is the signaling port that the devices in the external network will talk to.