8 industries, 128 companies and only 10 made our list!



hello investors we're going back to our roots we looked at 128 companies from 8 different industries and only 10 made our list come on let's go swim in with the sharks and find out who they are please don't forget to Like and subscribe to this channel hit that bell so you don't miss a single episode and tell your friends about it so they can join in the discussion is where we are diving right in with the electric utility central us first company up is M GE Energy ticker mg e e their yield is 2.0 percent and that's on $69 and seven cents a share this is valid the 14th of June 2019 you can see that mg energy is not qualified for cash flow or earnings per share but they are a div 0 17 years of increasing dividends per share no flat years in here and that's actually 18 years because we've added another year to the look here's what that looks like on the long term trend now okay they're a div 0 but really does this trend line get anybody terribly excited I don't think so here's what that looks like only year-to-year change alright also in the electric utilities central is WEC Energy Group ticker WEC their yield is a more respectable 3.0 percent that's filled with gold because that is greater than the 2.6 percent benchmark that I use that's on a valid price of $81 and 29 cents they are not qualified for cash flow or earnings per share but they are also a div 0 17 in this case 18 years of increasing dividends per share here's what that looks like on the long-term trend now that's a little bit better slope to the dividend line and here's their year-to-year change we're going to change industries now going to the telecom services telecom services includes companies like AT&T Intelsat Iridium Sprint t-mobile US Cellular and Verizon but look only two companies made the list this first one Shenandoah telecom ticker sh e n is only yielding 0.8 percent but that's probably not why you buy a telecom company that's on a valid price of $39.95 they are qualified as a cash flow zero so they've had seventeen in this case eighteen years of increasing cash flow per share but they are not qualified for earnings per share or dividends per share here's what their long-term trend looks like and here is what they're your your changes look like alright now also in this industry is telephone data systems TDS their yield is a little bit better 2.2 percent that's on twenty nine dollars and 56 cents a share and they are qualified as a div zero but they are not qualified by cash flow or earnings per share here's what their long-term trend looks like I mean that cash flow and earnings are bouncing all around but their relative you know overall they're just flat and their earnings per share is well pretty much flat excuse me their dividends per share is also pretty much flat here's what the year to your changes look like now telecom equipment alright cisco cisco that's a name everybody probably recognizes CSCO is the ticker they are 2.6 percent and that's on a valid price of fifty three dollars and 23 cents now Cisco's doing a little better than some of the other folks we've looked at here they are qualified as a cash flow one so they've had 17 in this case 18 years of increasing cash flow with the exception of this one- year here as they went from Oh a 209 they are also an e-1 so 17 years of increasing earnings per share with the exception again of this one time frame Oh 809 and I think we all know what was going on during that time frame so probably not a big surprise now they did not pay dividends for a long time but once they started paying dividends you can see that those dividends have increased every year now here's what this looks like on the long-term trend now that really isn't that bad nice upward trends and once they started paying dividends they've had a nice upward trend on their dividends Cisco is also doing really well in this current world situation they have Wickard their supply chains so that they're not dependent on Chinese supply and they should do good against not only the tariff issues but also concerns that some people have with the Chinese companies in this telecom world here's their year-to-year change right now also in the telecom equipment world is Qualcomm QC om their yield is three point six percent and they are a div zero 17 this case 18 years of increasing dividends per share no flat years here's their long-term trend where they had a nice slope here then they got into some trouble and now they're picking it back up again we'll see how that plays out their dividends remember they're a div zero and you can see a nice steady pretty smooth progression along the dividend per share and here is their year-to-year change all right changing industries now we're in the pharmacy services all right now there were only five companies in pharmacy services CVS health diplomat pharmacy pet med Rite Aid and Walgreens boots Alliance Walgreens the only one that made the list WBA their yield is 3.4 percent and that's on $51.50 they are qualified as a div zero here's what that looks like on the long term trend all in all not too bad there's some nice upward flow if you want some exposure to the pharmacy industry this might be the place to go here's their year-to-year changes changing industries yet again we're in the auto parts world now Eaton Corporation eet and their yield is 3.7 percent and that's on $77.77 a lot of sevens there now they are a div one so they had 17 years of increasing dividends with the exception of this one flat year from Oh 8 oh nine we all know what was going on back during that time frame and pretty good that they were able to keep it flat instead of a negative here's what that looks like on the year-to-year trend excuse me on the long-term trend and here was their year-to-year changes now also in the auto parts world you've probably a little more familiar with these folks genuine parts GPC I know I am their yield is three point zero percent on 100 dollars and eighty-eight cents they are a div zero so they did not even have a flat year back here where eaten it did here is their long-term trend and here's the year year now we had nobody from the toiletries and cosmetics industries which was folks like Avon Helena Troy Estee Lauder they didn't even not a single one of those companies made the list so that takes us right into cable TV and cable TV you're talking about folks like cable one Comcast that you see here Dish Network Ecostar but Comcast is the only one that made the last CMC si their yield is two point zero percent on forty one dollars and forty cents but they are not qualified at dividends per share they are qualified as a cash flow one you can see they had a flat year here I mean excuse me a negative year here from oh five two oh six and they are an easy row so or 17 years of increasing earnings per share here's their long term trend line again you're not buying into these guys for income necessarily but for other reasons in your portfolio here's their year-to-year change alright so let's see how they all stack up here you've got ten companies that made the list remember this was out of a total of 128 companies in 8 different industries now of these you've got some relatively good yields going on here and with the highest being eaten at 3.7 but that is you don't want to give one compared to genuine which is lower at 3.0 which is still respectable but they've managed to keep their dividends going up every year alright I would love to hear what you think about all these companies ask me about the companies that didn't make the list from the industries that you thought maybe should have been on there and we can explore why they didn't make the list and I'd like to know do you own any of these companies if so why did you buy into them you all have a great week

Cisco Industrial Ethernet Switches for Industrial Networks



the use of IP based devices is becoming commonplace in today's industrial world and often in remote harsh environments but as manufacturing transportation systems and utilities add more and more of these devices getting power to each one can be a complex and costly challenge to begin a qualified electrician is needed to help plan and install additional wiring to support each device and with more wiring comes the need for additional protection through more circuit breakers and transient or surge filters then what happens after all of this is put into place and you need to move some of the devices or add even more that's expensive and inflexible you need a better solution Cisco industrial Ethernet switches are the answer designed specifically for industrial applications the rugged Cisco ie 2000 and 3000 series switches leverage industry-leading Enterprise Ethernet switching solutions to extend Ethernet and proven standards-based technology to industrial networks and now these switches also feature power over ethernet in both fixed and modular solutions providing extended power options for p OE capable end devices modular cisco IE 3000 layer 3 switches can support up to 4 p OE or p OE + ports per module or up to 8 p OE ports per system while also providing a number of additional non pol ii ports for further network connectivity options and new cisco IE 2000 layer 2 switches now include 4 p OE or boe plus ports in a fixed form factor in addition to its non VOE ports these switches eliminate the need for extra wiring and outlets while providing up to fifteen point four watt boe or twenty five point five watt boe plus per port now you can not only easily add new devices such as closed-circuit surveillance cameras door entry badge readers IP phones and wireless access points throughout each location but also move them as needed without an overhaul of your electrical layout Cisco industrial Ethernet switches can consolidate your industrial networks and securely converge them with your corporate network to create a single secure network infrastructure this results in one network to manage higher availability improve quality of service and new collaboration opportunities using video and voice technologies and now power over ethernet support also helps reduce total cost of ownership and complexity to find out more about cisco IE 2000 and IE 3000 series switches visit us on the web you

CUCM ILS Configuration Walk Through With SME Setup



hi everyone welcome to our presentation my name is John Muir's MA and I'm a Cisco collaboration instructor at sunset learning in this video we're going to show you the step by step process of configuring Cisco ILS the inter cluster lookup service in GDP our global dial and replication service and we're going to be using SME session management Edition we're going to show you how you can dramatically simplify the dial plan our goal for this video is to give you solutions we're going to show you the step by step process of configuring inter cluster lookup service so that you can dramatically simplify the dial plan in your own collaboration environment wouldn't it be great if there was just a single address that we could use to communicate with an end user right if you wanted to talk to Bob you didn't have to remember Bob cell phone bob's desk phone bob's beeper bob's car phone no you could just use bob's address it could even be his email address that's what Uniform Resource identifier you are eyes are their addresses that can be look just like an email address and Unified Communication Manager allows you to associate that to endpoints so that's all you got to do whether you want to call Bob or you want to call me dial one address Unified Communication Manager will forward that to all of the endpoints all of the phones that are associated to that user the problem is if you have multiple clusters because now Unified Communication Manager it doesn't know what to do if you dial in address and it's not in its local database then what what does it do then where does it go it simply doesn't know in this example we've got multiple users in the same company and so we're using email addresses and therefore the domain name is the same at SL I'd suc labs comm the problem is we've got users on multiple clusters we're on cluster a and we were to dial jeido at sli – you see lab com what would our cluster a do it would look in as a route plan report and it wouldn't see jeido but it wouldn't have any idea where to send the call and therefore we would have to statically or manually add J Doe at SL ID s you see labs pointing to the B cluster there's going to be a lot of manual configuration if we want to use this technology over multiple clusters well fortunately there's a solution that's exactly the problem that ILS solves so before we get started with configuring it let's take a look at what the heck is ILS ILS is the inter-cluster lookup service and it's a service that's configured on multiple clusters ILS will then automatically update Unified Communication Manager with the current status of the remote clusters hey man here are all the different URI numbers that are on cluster B and I'll go ahead and send them to cluster a so that cluster a has that information if you're an end-user on cluster a and you dial any of the extensions that live on B well a will now know okay I've heard of that guy he's on cluster B let me send the call over to B if that didn't happen automatically we'd have to manually put that in okay so one aspect is that it updates other clusters and then the flip side of that is that we learn from these other clusters so that we don't have to manually put that information in that's the big benefit of using ILS the ILS service once we activate it on a cluster is only going to run I'm the unified communication manager publisher so only one server the pub is going to run the ILS service but all of the servers in our cluster are going to benefit they're all going to learn the information from the ILS updates they just won't have to run the service the gdpr is the global dial plan replication and this is in addition to ILS and it allows you to send other numbers across the cluster in addition to just the URI you can add the URIs but also alternate numbers pattern so you can have number patterns as you can send to other clusters and you can use plus C 164 alternate numbers and if those all fail you can send public switched telephone network failover numbers like hey here's how to reach me over the the LAN but if the wind goes down then forget everything I said change your numbers around totally differently and then send it to the public switch telephone network then again that just simplifies the dial plan because you don't have to add that information in manually it's done automatically and now that brings us to the third component SME session management edition well the first two in a cluster lookup service and global dial and replication services are used to share endpoint information numbers and you are eyes between the clusters the SME is a is not a service it's a server it's an actual Cisco Unified Communication Manager cluster except it doesn't have phones registered to it it has trunks it's job is to act as a centralized aggregation point if we didn't have an SME server and we had multiple clusters well we'd have to make a lot of trunks let's take a look here we can see that we've got four clusters a B C and D and without session management Edition just plain ups just plain old Cisco clusters we would have to make a trunk from all of our clusters to and from the other clusters so we'd have to have a trunk from A to B and then from B to a we'd have to have a trunk from A to D and D to a we'd have to have a trunk from A to C and C to a we'd have to have a trunk from B to C and C to B and finally B and D would have to be trumped but we missed one we'd have to have a trunk between C and D we'd have to have what 1012 trunks we'd have to create 12 different trunks if we wanted to be able to communicate both directions between all clusters and with SME we can eliminate a lot of the configuration the session management Edition in the center well it a great we don't need to have trunks to all the different clusters we just need to have a trunk from each cluster to the SME server and then a trunk back each device has a trunk there and a trunk back so if you're the administrator and you go to cluster a you don't have to have a trunk to all the different clusters nope just one trunk to the session management Edition server and then they have a trunk back and that's it so now if users on cluster a want to talk to users on a cluster B or C or D they just send it out of their one trunk the trunk to the session management Edition server now I want to take a look at what exactly are we going to accomplish in our demonstration what are the step by step configuration solutions that we're going to go over here's what we're going to accomplish in this demonstration we've got two clusters blue and red the blue cluster has an an end-user John and he's going to represent the potentially thousands of users and endpoints that would be registered to the blue cluster and John is going to live in the sli des UC labs comm that's his domain space that's his email address we've got another cluster the red cluster ami is the user there and she represents potentially thousands of users that could be registered to the red cluster she's also in the SL ID suc labs.com domain that's her email address so we want to be able to call these endpoints using these URI addresses and we need to tell our cluster hey if you're in the blue cluster and you dial ami at sli to suc labs comm you've got to go over here to the red cluster and vice-versa we're going to use SME to tie this together so here's what we're going to have we're going to have a SIP trunk that travels from blue to the SME then we're going to have a SIP trunk from the SME back to blue and we'll go ahead and do the same thing to the red cluster so those are the only trunks that we need to make then we'll turn on ILS we'll go to all red blue and purple the SME server will activate ILS on all three and then we'll simply say hey if you're in the blue cluster and you want to call Amy then just send it to the SME server it'll handle it and that's all blue has to know we're going to go through and set up the step-by-step process of configuring ILS and SME and the first thing that we're going to do is access the blue cluster which I've done here I've had to change the resolution on my screen to demonstrate this one step and that's because it's located under call routing at the very bottom of the menu global dialing and this is where we can see learn patterns learn numbers etc we're going to set the partitions for learn numbers and patterns so these are the things that we're going to learn from red we want to determine what are what are the partitions going to be what are the locks and then if we want our phones to be able to call these learned patterns we have to give our phones permission so we're going to change the partition for learn numbers and patterns to outbound that's just a partition that I'm going to use and make sure that my internal phones have permission to use the outbound partition and then once that's done save and click OK we've got the partition set the next step is going to be to modify the enterprise ID to set the cluster ID we'll go to system enterprise parameters and the cluster ID is set to stand alone but every publisher that's going to participate in ILS has to have a unique ID so we'll go ahead and set our blue server to have a cluster idea of blue and click Save we're get a pop-up message that looks ominous and it says hey you're gonna have to restart all services that's alright we can actually ignore that just click OK and then apply and then ok again we've set the cluster ID and now we can go ahead and turn on ILS ILS is located under advanced features ILS configuration and then we can set our role right now we're a standalone but the whole point of using ILS is that we're no longer alone that's right our server has friends and we want it to communicate with them so we're going to change the role too we can set it to be either a hover spoke the difference is that hubs share information and share all the learned patterns with other hubs and spokes spokes only talk to hubs we're on the blue server and it's going to communicate directly to the SME the centralized session management Edition server and that's it so there's no reason to be anything other than a spoke for our blue publisher so we'll set that to spoke we want to check the box that that allows us to exchange dial plant information with others it's kind of the whole point we want to communicate with other servers the route string that we advertise this is going to be our name so when we send something to the SME server it's going to be sourced from whatever we put here we'll go ahead and call this the blue dot SLI – you see labs.com that'll be our name that our centralized SME server will see all of our numbers source from we want to go ahead and synchronize we'll change that to every two minutes and now we need to authenticate all of the servers that we're going to communicate with which in this instance is only going to be the SME server but we still need to have a common form of authentication that all of the servers use we're gonna have a total of three servers in the ILS process and they're all going to use the same password be sure to uncheck use TLS certificates if you're not going to use certificates because if you keep it checked even though you're setting a password and you just forget to undo that it can take hours to synchronize so unpick that and then make sure that the password matches on all the duvall the servers it needs to be eight characters or more I'll go ahead and set that and that's it we'll click Save and then we get the pop-up that asks us who we're gonna talk to who are you going to send and receive ILS information from this is the SME server and its IP address is 10.15 dot 1.15 we're going to activate the ILS service so we'll click OK click OK again the service is going to be activated it's ready to start sharing and sending and receiving information and now we need to set the other servers to participate we'll go ahead and go into the red server next and we'll turn on the same settings and features and then we'll configure the SME server here we are with a red server and I went to call routing global dial and replication and I'm going to set the partitions for the learn patterns and numbers I've also got a partition on this server called outbound so I'm going to use that for the patterns and numbers that are going to come in we'll set those to outbound and click Save we're setting our permissions for the learned patterns and numbers the next step is going to be to change the cluster ID or go to system Enterprise parameters change the cluster ID from standalone to read ignore the restart all services pop-up message click Save and then apply click OK now we need to activate ILS we'll do that under advanced features ILS configuration we're going to make this server a spoke as well because it's going to communicate with the session management Edition server that's it will change the advertised route string from the name of the server to read and check the box to exchange global dial an information we want to use the same password so we'll uncheck use TLS check the use password and then set the same password that's going to be used on all three servers once that's done we'll go ahead and click Save and we're going to put the session management Edition server's IP address in here 10.15 dot 1.15 we're going to activate the ILS service click OK click OK again it's going to take a few moments to refresh and get that service started and while that's happening let's go into the session management Edition server and do the same thing we don't need to set the partitions on the SME server because it doesn't have any phones it's not going to be placing sending or receiving calls itself we're just going to go ahead and change the cluster ID and then activate the ILS service we'll go to system Enterprise parameters will change the cluster ID from standalone to session management or SME something that makes sense for you ignore the pop-up click OK save and apply click okay and now we're going to set the ILS service so we'll go to advanced ILS configuration this server is going to be the hub it's the only hub we're going to have and again that means that it'll share routes and share learn patterns with other spokes and hubs when you're set up as a spoke it doesn't mean that you're only going to learn from the hub it means that you only share what you know with the hub but all of the servers are going to have the same information they're all going to learn the same thing it's just who do you pass it on to we'll make this a hub the advertised route string doesn't necessarily matter for this one choose SME changed the synchronize to two minutes I think I forgot to do that on the red server tick the box to exchange dial plan of replication information and then set the same password once the password is set click Save and now we need to pick one of our spokes that we're going to talk to both of our spokes are pointing to the SME server but the SME server asked to point to somebody and so we'll go ahead and have that point to the blue server 10.1 dot 5.15 click OK click OK while that's loading I'm gonna jump back to the red server and make sure that the synchronize is set to every 2 minutes and then just what I thought I did forget to change the synchronize every from 10 minutes down to 2 minutes on the red cluster so go ahead and save that now what will happen is we'll give it a few minutes and these servers will synchronize from the red cluster we'll be able to see the the SME cluster will show up we can go to the blue cluster and we'll see the SME cluster show up and then we can log on to the SME cluster and we'll see that we're synchronized to both blue and red the next question is what are we going to be advertising what numbers are we going to send to the other clusters from our red cluster we can advertise site codes we can advertise patterns we can advertise you our eyes to do that let's go into the device phone there's a few different ways we can go about this but we'll look at the individual phone itself we'll start there so we've got a phone registered used by Amy we'll click on that from here we'll click on her her number 3001 and now we've got a few options we can scroll down and well in addition to dialing 3001 and reaching her that way making the phone ring by dialing this extension we can drop down and we can set an enterprise alternate number which can be anything you'd like so if there's some other number that you want to dial to make this phone ring you could say hey if anyone dials 8 to 2 plus the extension then that would cause the phone to ring all right so that's one number if you want to advertise it to other clusters using ILS go ahead and tick the box advertise globally be ILS but in order to to have this number be reachable in order for somebody to be able to dial this number we have to associate it with the partition even if we leave it in the none partition it still has to be associated to some partition if we don't tick that box then nobody can call the phone it's not gonna ring at all we also have the option of setting a plus u1 64 alternate number now plus e 1 64 globalized call routing but even if we're not using globalized call routing we can still take advantage of this this can be any number you'd like you may be this is your public switch telephone network your d ID number five two two five five five any digit you'd like whatever you want to add there go ahead and then if you want to advertise it to other clusters tick the box and it will dynamically show up on the SME server and then the SME is going to pass it to the blue server users at the blue cluster will be able to call us with either one of these numbers again in order to make sure that it's reachable tick the box add to local route partition whether you assign it to a partition or not it still has to be checked we've also got the ability to set you our eyes and we can set that at the number or we can set that at the user account here Amy at SL I'd suc labs comm this URI was set at the end user account it's given a partition the directory URI partition and we're not able to change that individually we can set one partition for all created URIs at the user account so one partition for the whole cluster if we add an individual URI at the line which we can do maybe amy is a member of the helpdesk and we could say help at cisco comm or any other domain name you'd like it does not have to be a globally routable domain name it can be whatever you set the partition so these partitions can be set individually for the URI is created on the line and then if you want to advertise to other users and other clusters via ILS then tick the advertise globally via ILS tick box that's it Save let me show you that if you go to user management end-user and you select your user accounts there's the URI right there the directory URI keep in mind that if you import users from Microsoft the URI can come from your Microsoft email address so it can be your exchange address you pull the users in to Unified Communication Manager from Microsoft that URI is populated via the email address and then it's associated to any phone that this users associated to so now we can call the user by dialing their email address and it will ring all of the Cisco phones that that users associated to advertise that via ILS to other clusters and now everybody in the organization regardless of what cluster they're on will be able to reach ami in this example via her email address pretty cool feature and there's still other options for sending patterns to other clusters via ILS under call routing if we were going to drop down to global dial and replication we've got if you look very closely I'm sure it's it's kind of tiny for you but we've got learned patterns and learn numbers so we can see hey what are we learning from other clusters but we've also got a setting that says hey which patterns do you want to advertise and that's what I want to show you so if we click advertise patterns and add new we can advertise patterns to other clusters so we could say hey whatever you want send it to other clusters and then they can dial that pattern and reach us and what else is useful is in addition to sending them a pattern we can send them instructions if the pattern fails if the trunks down all of this ILS stuff is based over trunks we're going to be using SIP trunks to communicate over IP between our clusters well I can send you all the numbers that I want but if that SIP trunk is down I can't call you I can't reach those numbers well then what then we're just out of luck but with the advertised pattern configuration you can send them back up instructions let me change my resolution again and then I'll show you how to set the back up pattern in addition to advertising other patterns to our clusters we can add a description maybe internal numbers and then which pattern do we want to advertise maybe we want to tell them 8:00 to 2:00 anything anything anything anything so if they dial that seven digit pattern go ahead and send it to the red cluster we can specify whether it's going to be an enterprise pattern or a plus C 164 pattern and then we have the option of deciding whether or not to send PSTN failover instructions we could say hey if if you try to call this number but the trunk doesn't work the wine is down let's go ahead and strip three digits that way if they were dial eight to two 3001 maybe it would get rid of the eight to two they would just be left with the four digit extension and then what well now we'll prefix maybe one or nine if they have to dial 9 to get an outside line if it's long-distance you could add nine one followed by our area code five two two five five five so it would if somebody were to dial eight to two 3001 it would completely change the number to nine one five two two five five five 3001 and from the Blues perspective or whoever's getting this that number should suffice in order to reach the PSTN they would be able to call us using their PSTN gateway that's the idea again it's totally optional we'll go ahead and add that and we would expect these numbers with these instructions to show up on both the SME and the blue cluster so from our red cluster we've configured it to advertise you our eyes patterns alternate numbers and enterprise alternate numbers let's take a look and see because we would expect blue to have learned about those we could go and look at the route plan report that's one place that would show us everything everything that we know and from here if we scroll down we see that we've learned 8 to 2 the one I just sent we've learned 5 to 2 5 5 5 3001 that was the the alternate number that we set on the from the red cluster 8 to 3001 that was the enterprise alternate number that we set we scroll down a little bit further we've seen that we've learned the URIs as well so we've actually learned five different numbers and patterns including you our eyes from our red cluster all of those came from ILS we didn't have to do anything on the the blue cluster to learn that well so now what we've learned about these patterns from ILS but we have to be able to call them from the blue cluster and the only information we have is this route string red dot SLI – you see labs.com that was set on the red cluster in our ILS configuration so we have to tell the blue cluster hey if you call one of these numbers you have to send it to this name well that's not enough information the blue cluster needs some more clusters communicate with one another using trunks so we have to tell our blue cluster what trunk do I use if I want to send a call to another cluster well the first thing that we have to do is create a SIP trunk well ok actually the first thing that we have to do before we do the first thing is create a sip profile we have to modify some settings that are going to be used on the profile that'll be attached to the SIP trunk which will point to the session management Edition server and then we'll come in and take this route string and we'll associate it to a sip route pattern which tells the cluster if you see a number that goes to this name use this trunk well tie it all together first thing that we're going to do before we do the first thing is go into device settings device settings sip profile and we cannot change any of the default system profiles but we can copy them so we'll select a standard sip profile copy it and then give it a new name and can be whatever you'd like I'm just going to use SME sip profile and then the setting that we want to change is actually up here we're going to tick the box use fully qualified domain name and sip requests save and now we're ready to do the first thing which is create the SIP trunk device trunk add new and we're going to create a standard basic SIP trunk next we can give it a name SME trunk we could give it a description we'll put it in the default device pool and then we'll scroll down under outbound calls in the calling and connected party info format drop-down box we're going to choose deliver URI and DN and connected party if available so this trunk can pass both URI addresses and directory numbers we need to configure the IP address and this is going to be the IP address of our SME server because that's where this SIP trunk is going and then the last two things we need to set are the SIP trunk security profile we'll go ahead and use the default non secure SIP trunk profile and then we need to attach our SIP profile alright so we've got that information we'll go ahead and save and then be sure to reset I've seen hundreds of SIP trunks maybe thousands or it maybe just seems like thousands of SIP trunks that they just haven't worked when students are configuring them one side or one of the server's forgets to reset it you make a change I add a SIP trunk you save it but if you don't take the time to reset it it doesn't work that's a hard thing to troubleshoot when everything is configured properly but it just needs this reset button so as a good friend of mine once said if it ain't Hooten try rebooting well that had to do with analog gateways but it works with SIP trunks as well good advice to heed we've got both of our SIP trunks now we need to make the SIP route patterns and associate the learned patterns which its respective trunks we're going to call routing SIP route pattern add new for the first one we can use red dot SLI so if the if the session management Edition server sees a number destined from this route string how does it communicate with it what does it use it uses the red trunk and now we're going to do the same thing for blue in fact we can copy this one and just change the word red to blue and change the trunk let's go look at our route plan report and we can see that we've learned about these numbers they're sourced from route strings both red and blue anything that's sourced from this route string used this trunk if I see anything that's sourced from this route string use this trunk now we need to go in to read and do the same thing we need to make sure that we have a sip profile create a sip trunk that points to SME and then we'll be able to test will find our sip profile copy it give it a name and then tick the box use fully qualified domain name save make our SIP trunk add new standard SIP trunk this is going to point to the SME server give it a name default device pool and scroll down under outbound calls and we'll go ahead and set deliver URI and DN give it the IP address of the SME server 10.15 dot 1.15 the non-secure SIP trunk profile and under SIP profile we'll give it the SME sip profile save and reset close we've got our SIP trunk and if we go to a route plan report we have the patterns that were advertising and we've learned one we've learned the John at SLI comm SLI juicy labs comm and if we want to call that we need a sip route pattern we need to tell the red cluster if you want to call something that source from blue use the trunk that goes to the SME server so go to call routing tip route pattern add new under ipv4 pattern will put the blue dot SLI – you see labs comm and will point it to our SME trunk take a look at the route plan report and we can see that if we want to call John at SLI des you see labs it's sourced from this route string and our red cluster knows that that route string is going to lead to the SME trunk we're ready to test and I've went ahead on the blue cluster if we were to go into the phone and take a look I've added some speed dials because we want to be able to call me and SLI – you see labs and help that SL help at Cisco com those were the two you are eyes that red is advertised we've learned about the ILS we've also learned about some patterns so we're using a 79 62 like phone I can't dial a URI but these speed dials will allow me to to call those numbers before we dial I want to take a look at the route plan report from Blues perspective because these are the numbers again we've learned about and we want to call we're going to call help we're going to call Amy we've learned about them and we'll go ahead and call other learned patterns well dial eight to 3001 that's associated to the red phone as is the five two two five five five 3001 those are all associated to the red phone we'll go ahead and test those from our blue phone here we have our two phones we've got the 2001 phone which is registered to the blue cluster and then we have the 3000 in one phone which is registered to the red cluster we can dial the the first pattern which is eight to three thousand and one from blue hello so that pattern works we learned about that through ILS and we sent it through our session management Edition server it works perfectly let's test the you our eyes first we'll do the help that's the help at Cisco comm hello that one works fine as well and then we'll test ami and that one fails well there's a specific reason that it fails and I want to show you that I didn't want to correct that without showing you exactly why this URI doesn't work and then we'll fix it and then hopefully it should work back here on the blue cluster in the route plan report we can see the number that we learned from ami or from the red cluster is ami at sli desu you see labs well that's the same address that I put on the phone in the speed dial there's no partition so it's not a permissions issue why does it fail well let's take a look at the blue phone take a look at the speed dial just to make sure that maybe I maybe I put the wrong address in no that's it Amy at SLI des you see labs the reason the call fails is because it's case sensitive the number that I put in is lowercase Amy the number I learned is capital capital a to a click on Amy and we'll change that from lowercase a to capital a Save reset the phone reset clothes and we'll test that call again I'll use the blue phone and click the Amy speed dial which now has a capital A which matches the number that's learned in the route pattern via ILS hello and that works perfectly so keep that in mind that when you're dialing the numbers are case-sensitive if you want to turn that off well we can do that under enterprise parameters back here on the blue cluster we would go to a system enterprise parameters and we can use the control F to search URI and the URI lookup policy we want to change that from case sensitive to case insensitive save apply this is going to reset everything in the cluster we'll go back to the phone click on the blue phone and I'll change ami uppercase a back to ami lowercase a and because we changed the enterprise parameter it should work either way close it and then reset the phone reset close let's test it out again back here on the blue phone we've changed Amy's address to lowercase and we've learned about it uppercase but because we changed the enterprise parameter it should work keep in mind because we're using the SMA solution and i LS Amy's located on a different cluster so we have to change that URI case-sensitive Enterprise parameter on all three clusters not just blue but the central and red and I went ahead and change it on both SME and red as well as what we just saw on blue so it should work fine hello and it does so if we change the case-insensitive setting on all of the servers that are participating in the ILS solution then it works fine lowercase or uppercase well that brings us to the end of our demonstration and hopefully you guys found this useful and informative my name is John Muir's MA and on behalf of all of us at sunset learning thanks for spending your time with us hopefully we can do it again soon