[cisco-voip] Separate cluster for third party SIP clients with SIP/ICT trunk to production

[Kent Roberts]

So no session manager?  Or is that in the mix as well?


Kent

> On Sep 28, 2019, at 16:50, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
> 
> 
> 
> Yup. That’s the plan. I was just wondering if be6k was more “user friendly” with fewer configurable options. More like a key system or something. 
> 
> It’s looking more and more like just another cluster. I may even consider recommending we “outsource” that. 
> 
> -sent from mobile device-
> 
> Lelio Fulgenzi, B.A. | Senior Analyst
> Computing and Communications Services | University of Guelph
> Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
> 519-824-4120 Ext. 56354 | lelio at uoguelph.ca
>  
> www.uoguelph.ca/ccs | @UofGCCS on Instagram, Twitter and Facebook
>  
> 
> 
>> On Sep 28, 2019, at 6:46 PM, Tim Smith <tim.smith at enject.com.au> wrote:
>> 
>> What version are you running?
>> Should be able to just spin up a new cluster and point it at same ELM / PLM / Smart Licensing account I think?
>> Share/pool your licensing
>>  
>> Cheers,
>>  
>> Tim
>>  
>> From: cisco-voip <cisco-voip-bounces at puck.nether.net> On Behalf Of Lelio Fulgenzi
>> Sent: Sunday, 29 September 2019 8:07 AM
>> To: Jeremy Bresley <brez at brezworks.com>
>> Cc: cisco-voip at puck.nether.net
>> Subject: Re: [cisco-voip] Separate cluster for third party SIP clients with SIP/ICT trunk to production
>>  
>>  
>> The primary goal for the separate cluster would be to remove all networking restrictions. SIP devices could (attempt to) register from any on-premise network. 
>>  
>> Secondary goal would be to be ready for a cloud service migration. 
>> 
>> -sent from mobile device-
>> 
>> 
>> Lelio Fulgenzi, B.A. | Senior Analyst
>> Computing and Communications Services | University of Guelph
>> Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
>> 519-824-4120 Ext. 56354 | lelio at uoguelph.ca
>>  
>> www.uoguelph.ca/ccs | @UofGCCS on Instagram, Twitter and Facebook
>>  
>> 
>> 
>> On Sep 28, 2019, at 6:00 PM, Jeremy Bresley <brez at brezworks.com> wrote:
>> 
>> BE6K is exactly the same software, just a different way to buy bundled hardware and Cisco/Vmware licensing.  You have the opportunity when you buy the hardware to get a discounted package of 35 UCL/CUWL standard/CUWL Meetings licenses.
>> 
>> Ordering guide has more information:
>> https://www.cisco.com/c/en/us/products/collateral/unified-communications/business-edition-6000/guide-c07-739442.html?dtid=osscdc000283
>> Is your goal of a separate cluster that it's going to be managed under a separate administrative domain, or to restrict calls to/from certain devices?
>> 
>> Jeremy
>> 
>> On 9/28/2019 5:46 PM, Lelio Fulgenzi wrote:
>>  
>> I was thinking about the possibility of spinning up a separate cluster for third party SIP device registration and then setting up a trunk (either SIP or ICT) to the production. 
>>  
>> Is BE6000 any “simpler” than a full fledged CUCM install? Or is it the exact same?
>>  
>> Does ICT (still) allow for CSS mapping per device? So whatever CSS it had on one cluster, it will be mapped to the other?
>>  
>> I want to be able to offer up third party sip registration, but without having to open up access to the production cluster. 
>>  
>> This would be namely devices used by other departments for security, etc. 
>>  
>> Benefit of this second cluster would be if we do decide to migrate calling to the cloud, we’d maintain the small cluster and build a route path to the cloud via whatever option is available. 
>>  
>> Thoughts?
>> 
>> -sent from mobile device-
>> 
>> 
>> Lelio Fulgenzi, B.A. | Senior Analyst
>> Computing and Communications Services | University of Guelph
>> Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
>> 519-824-4120 Ext. 56354 | lelio at uoguelph.ca
>>  
>> www.uoguelph.ca/ccs | @UofGCCS on Instagram, Twitter and Facebook
>>  
>> 
>> 
>> 
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190928/a060ce4a/attachment.htm>