[cisco-voip] Call flow for device registered to Hybrid Cloud via local PSTN

Thu May 16 01:10:35 EDT 2019

This is another one 😊
At this point they should just call them by numbers.. or maybe follow Ubuntu convention. Something memorable and unique 😊

From: cisco-voip <cisco-voip-bounces at puck.nether.net> on behalf of Lelio Fulgenzi <lelio at uoguelph.ca>
Date: Thursday, 16 May 2019 at 2:09 pm
To: Ryan Huff <ryanhuff at outlook.com>
Cc: "cisco-voip at puck.nether.net" <cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Call flow for device registered to Hybrid Cloud via local PSTN

"As part of the integration between BroadCloud Calling and Webex Teams, Cisco is launching the Cisco Calling App. If a user wants to make a call from Webex Teams, they can cross-launch the calling app."

https://www.zdnet.com/article/cisco-combines-broadcloud-calling-with-webex-teams/

-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<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

On May 15, 2019, at 11:22 PM, Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>> wrote:

I recall one post I read, where it talked about giving the person the option to “launch a separate calling app” which I’m pretty sure they were referring to the broadsoft client.

Is that the WebEx teams calling service then?
-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<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

On May 15, 2019, at 10:39 PM, Ryan Huff <ryanhuff at outlook.com<mailto:ryanhuff at outlook.com>> wrote:
Yup, this stuff is soooooo fluid right now, it’s a contradictory mess 😂. The on-prem registration, IMHO, is ffffaaaarrr from prime time (as you even noted, “preview mode”). I honestly think it’s a bit further out than what the marketing department would have us believe too ;).

Hopefully though, one day, we’ll all have this unified unicorn they’re promising... Jeams?... Jams? ... who knows 😂
Tops to you mate!

On May 15, 2019, at 22:31, Tim Smith <tim.smith at enject.com.au<mailto:tim.smith at enject.com.au>> wrote:
Hi Ryan,

Yeah sorry, I realise you guys were talking WebEx Hybrid Call (formally Spark Hybrid).

Just pointing out there is some new stuff on horizon. Calling from WebEx Teams via CUCM feature.
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_011.html<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.cisco.com%2Fc%2Fen%2Fus%2Ftd%2Fdocs%2Fvoice_ip_comm%2FcloudCollaboration%2Fwbxt%2Fucmcalling%2Funified-cm-wbx-teams-deployment-guide%2Funified-cm-wbx-teams-deployment-guide_chapter_011.html&data=02%7C01%7C%7C9379fa8f35284f2e6bfc08d6d9a6a4be%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636935707083032550&sdata=b4UfPgVLInjyqap7dxRoF7T3PXcBna%2FOW0%2F7GY7maxA%3D&reserved=0>

It looks like this will replace the calling from Teams part of the old Hybrid Call (although not on mobile clients yet) – in fact it seems you have to remove their old Hybrid config to make them work.

Looks like you’d still need to retain Hybrid Call for cloud registered devices.

There was one specific annoyance with the Hybrid Call from the apps, and I can’t find it in my Teams search ☹

Cheers,

Tim

From: Ryan Huff <ryanhuff at outlook.com<mailto:ryanhuff at outlook.com>>
Date: Thursday, 16 May 2019 at 12:14 pm
To: Tim Smith <tim.smith at enject.com.au<mailto:tim.smith at enject.com.au>>
Cc: Jonathan Charles <jonvoip at gmail.com<mailto:jonvoip at gmail.com>>, "cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>" <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: [cisco-voip] Call flow for device registered to Hybrid Cloud via local PSTN

This is Webex Hybrid Calling (which was formerly Spark Hybrid calling). Whether you configure for cloud registered codec devices, or Webex Teams clients, both use cases use the same configuration path / scenario to enable PSTN call via CUCM.
Sent from my iPhone

On May 15, 2019, at 22:08, Tim Smith <tim.smith at enject.com.au<mailto:tim.smith at enject.com.au>> wrote:
Hey guys,

I think this one has changed a little.
We did “Spark hybrid calling” for one customer with the Spark RD devices in CUCM
Honestly, the experience was a little confusing.

I think the new direction is going to be the WebEx Calling via CUCM (it’s in preview mode still)
https://help.webex.com/en-us/n15ylys/Explore-Calling-in-Cisco-Webex-Teams-Unified-CM<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.webex.com%2Fen-us%2Fn15ylys%2FExplore-Calling-in-Cisco-Webex-Teams-Unified-CM&data=02%7C01%7C%7C9379fa8f35284f2e6bfc08d6d9a6a4be%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636935707083042561&sdata=zbKn4%2Bo6qOMVpZuBvCVfY2L1QZF3s80v9w%2FeBPvmAKw%3D&reserved=0>

It’s not parity with the Hybrid Calling yet. (i.e. I think it’s only desktop)
Either way, I’d check out all the details first.

If you are not already on there, make sure you are on the Fabian bot in WebEx teams. (Not sure if it’s partners only)
These hybrid features are really starting to rock and roll now.

Cheers,

Tim

From: cisco-voip <cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>> on behalf of Jonathan Charles <jonvoip at gmail.com<mailto:jonvoip at gmail.com>>
Date: Thursday, 16 May 2019 at 9:30 am
To: Ryan Huff <ryanhuff at outlook.com<mailto:ryanhuff at outlook.com>>
Cc: "cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>" <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: [cisco-voip] Call flow for device registered to Hybrid Cloud via local PSTN

Thanks!... looks like I have some more reading to do... so how does it prevent anyone from sending a pstn number to my expressway? How does it authenticate the Webex devices to pass calls to CUCM for?

Customer has enterprise licensing, so they should be able to do whatever they want...

Jonathan

On Wed, May 15, 2019 at 6:16 PM Ryan Huff <ryanhuff at outlook.com<mailto:ryanhuff at outlook.com>> wrote:
You’ll need a specific Webex DNS zone and the traversal trunk really just needs to support pre-loaded route headers and SIP parameter preservation (those are the most significant differences over the traversal / neighbor zone you might have setup for B2B).

It’s a simple enough configuration, but there are a few more moving parts than what the marketing may lead one to believe. Here is the configuration documentation: 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://eur01.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%7C9379fa8f35284f2e6bfc08d6d9a6a4be%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636935707083052566&sdata=IqckJHIvkNb6K%2BisMklzbeQGcw0P1tT9oTr8x98t5cw%3D&reserved=0>

Oh and don’t forget to enable MTLS on the edge and also be aware the ControlHub now requires CCM 11.5.1SU3 or better (it detects CCM version via call connector on Exp-C). It wouldn’t allow you to enable hybrid calling on cloud registered devices otherwise.

You can technically still get away using Expressway 8.11.4, but that’ll soon be a deprecated version for hybrid calling (you’ll get an alarm about it), so might as well go to 12.5.2 and be done with it.

BTW, if you try to upgrade an 8.x Expressway to 12.5.x, you will interact with GLO for the 12.x release key (can’t do it from the self service portal because the existing 8.x virtual license is already associated to a PAK and GLO has to invalidate that relationship first, then hash your new keys to 12.5.x).

Good Luck!

- Ryan

On May 15, 2019, at 18:42, Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>> wrote:

Very good question. From what I understand, there’s a special traversal link built and it’s all “built-in” and uses the CSS of the remote destination or something like that.

I’ve read absolutely zero docs about this. This is all based on a quick convo I had. I had the same worries and if I recall correctly, my worries were somewhat alleviated.

However, that being said, there is only one template in control hub, so if your user needs a different setup on their remote destination (or something like that) you need to go make a manual change.

It’s sorta like how there’s only one licensing template in control hub for new users. We’re gonna struggle with that. We might have to engage (professional) services which make uses of APIs to assign different services for different users in webex. But I digress.

-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<tel:519-824-4120;56354> | lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>

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

Error! Filename not specified.

On May 15, 2019, at 5:20 PM, Jonathan Charles <jonvoip at gmail.com<mailto:jonvoip at gmail.com>> wrote:
Enabling Cisco hybrid call and routing calls to the PSTN using local gateway (via Expressway C/E pair).

What search rules do we need on the E and C?

How do we prevent toll fraud if we have E.164 patterns inbound on our Expressways?

Am I being paranoid?

Jonathan
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7C9379fa8f35284f2e6bfc08d6d9a6a4be%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636935707083072582&sdata=xwvFYihs4n%2FJ6sznh%2FnyKz4mZGaBs8HWhiAQKB5g%2BB0%3D&reserved=0>
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7C5b817b962f3e419f017508d6d986a8fe%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636935569711652307&sdata=UCJB8OKg5UlpRWHaTtp6Y2AJNzpfh6NmVWdejkBYmDI%3D&reserved=0<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7C9379fa8f35284f2e6bfc08d6d9a6a4be%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636935707083082587&sdata=JNr14W7VbsgSfh98z8kW%2Fj2oM6jmJWve79PbnKFDDB8%3D&reserved=0>
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto: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/20190516/7c3f7fca/attachment.htm>