[cisco-voip] How difficult is hybrid call (connector) setup ?

Ryan Huff ryanhuff at outlook.com
Tue Jul 2 22:25:41 EDT 2019


It all comes down to what you are using your Expressways for. In a Webex Hybrid call connect scenario you could in theory, have calls with source uri’s using your domain, which in a pure B2B scenario is usually something you’d deny with a call policy.

As I understand it, the dedicated Expressway recommendation (outside of pure capacity reasons) is to make it easier to write call policies that don’t interfere with other use cases since Expressway doesn’t really have a partitioning mechanism (outside of what you can do with search rules).

You really have to go to the Ninja master level with your regular expressions in your search rules and call polices to get multiple use cases setup and using call policies to reduce toll fraud... and have everything work.

... and this is where Cisco should, in my opinion, step up to the plate a little. The best answer really shouldn’t be, “just deploy and use another Expressway”.

Yes, that is easier than refining CPL and search rules, but many customers run tight compute/storage budgets (Ex. be6k) and cant always spin up more Expressways.

-R

On Jul 2, 2019, at 22:06, Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>> wrote:

Ok. Thanks.

I think we’re on a low version of expressway. I’ll have to confirm.

My memory is failing, and I can’t find it in my notes, but in one session they talked about using a separate pair of C’s and E’s or have a high risk of toll fraud.

I believe it was in my Sunday techtorial. I’ll have to reach out to them.

-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<x-apple-data-detectors://1/0>
519-824-4120 Ext. 56354<tel:519-824-4120;56354> | lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>

www.uoguelph.ca/ccs<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.uoguelph.ca%2Fccs&data=02%7C01%7C%7Cc007f1e5951c4fe8148208d6ff5afe84%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636977163613983703&sdata=eA%2F4KJe0VRJ%2FijsYobqcETIGcYwju9f7Q5zZa0XiPAM%3D&reserved=0> | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

On Jul 2, 2019, at 9:49 PM, Ryan Huff <ryanhuff at outlook.com<mailto:ryanhuff at outlook.com>> wrote:

It’s not that bad (maybe 1 - 2 hours to get a functional test going).

The most unexpected thing I think you may run into is the use/need for MTLS (TCP:5062) between the Edge and Control Hub. Also, your Expressway version should be 12.5.x (I think 8.11.4 may still work but you’ll get an alarm telling you to upgrade if it does work).

Outside of that, it’s a splash of nerd knob turning in the control hub, some search rule / traversal & dns zone magic in Expressway C/E and setting up the management/call connector in Expressway, you can even re-use a MRA (unified communications) traversal client/server (or create a dedicated traversal if so inclined).

Here is the guide you’d want to follow for it and it’s pretty complete and well written: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/spark/hybridservices/callservices/cmgt_b_ciscospark-hybrid-call-service-config-guide.html<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.cisco.com%2Fc%2Fen%2Fus%2Ftd%2Fdocs%2Fvoice_ip_comm%2FcloudCollaboration%2Fspark%2Fhybridservices%2Fcallservices%2Fcmgt_b_ciscospark-hybrid-call-service-config-guide.html&data=02%7C01%7C%7Cc007f1e5951c4fe8148208d6ff5afe84%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636977163613993708&sdata=Ryhmmh%2F1SxqFB8uOU6S%2FTWioJ5IUVgDkjxCEUk0SdvE%3D&reserved=0>

Thanks,

Ryan

On Jul 2, 2019, at 21:30, Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>> wrote:


On a scale from 1 to 10, how difficult and/or time consuming is it to setup call hybrid connector with WebEx?

I’m just about convinced that I’d rather register our room devices and SX20s to the cloud. But people would like to be able to dial extensions and PSTN numbers. Being able to use our audio bridges would also be of benefit (ya, I understand the irony of 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<x-apple-data-detectors://1/0>
519-824-4120 Ext. 56354<tel:519-824-4120;56354> | lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>

www.uoguelph.ca/ccs<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.uoguelph.ca%2Fccs&data=02%7C01%7C%7Cc007f1e5951c4fe8148208d6ff5afe84%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636977163613993708&sdata=OIht9e0rIYKhqiZKeK1AY7AmCK6CCCdNKhMyDVC82us%3D&reserved=0> | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7C9235159648ab4fda30f808d6ff55f95c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636977142054880224&sdata=pMRyrYjCx8kKeTKrdkE5EHylZ5bfL2ZVHhf3x6mcVGs%3D&reserved=0<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7Cc007f1e5951c4fe8148208d6ff5afe84%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636977163614013724&sdata=MCEZTuAXxzwx4dNYP9whusRuEQSg46mNNn%2FpPZOSUoo%3D&reserved=0>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190703/84ad9779/attachment.htm>


More information about the cisco-voip mailing list