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

[Jonathan Charles]

OK, I know it is weird to respond to your own email... but...

The blocking of toll fraud is via MTLS on port 5062 with Cisco... we create
an MTLS session first before accepting the invite.


Jonathan

On Wed, May 15, 2019 at 4:20 PM Jonathan Charles  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@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

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

[Tim Smith]

My favourite meditation is to call TAC and listen to hold music 😊


From: Ryan Huff 
Date: Friday, 17 May 2019 at 2:12 am
To: Anthony Holloway 
Cc: Tim Smith , "cisco-voip@puck.nether.net" 

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

Apologies, didn’t mean to cause the need to meditate 😂
Sent from my iPhone

On May 16, 2019, at 11:02, Anthony Holloway 
mailto:avholloway+cisco-v...@gmail.com>> wrote:
"... this stuff is soo fluid right now, it’s a contradictory mess..."

This bothers me to an unhealthy degree.  I really need to meditate or something.

On Wed, May 15, 2019 at 9:39 PM Ryan Huff 
mailto:ryanh...@outlook.com>> wrote:
Yup, this stuff is soo fluid right now, it’s a contradictory mess 😂. The 
on-prem registration, IMHO, is rrr 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 
mailto:tim.sm...@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://eur02.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%7C0c06fdfb1500415242ba08d6da0f89d8%7C84df9e7fe9f640afb435%7C1%7C0%7C636936157605890504&sdata=70z9uOBPVxB6F%2BpIk9YGMHr1OxsfRoc1%2BJGi61SJ8CU%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 mailto:ryanh...@outlook.com>>
Date: Thursday, 16 May 2019 at 12:14 pm
To: Tim Smith mailto:tim.sm...@enject.com.au>>
Cc: Jonathan Charles mailto:jonv...@gmail.com>>, 
"cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>" 
mailto:cisco-voip@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 
mailto:tim.sm...@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://eur02.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%7C0c06fdfb1500415242ba08d6da0f89d8%7C84df9e7fe9f640afb435%7C1%7C0%7C636936157605920531&sdata=QiAUsNC6BtKjjvJQWQEYxQ3FT7qc8oLU6UredrBrSnU%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 
mailto:cisco-voip-boun...@puck.nether.net>> 
on behalf of Jonathan Charles mailto:jonv...@gmail.com>>
Date: Thursday, 16 May 2019 at 9:30 am
To: Ryan Huff mailto:ryanh...@outlook.com>>
Cc: "cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>" 
mailto:cisco-voip@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 wh

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

[Ryan Huff]

Apologies, didn’t mean to cause the need to meditate 😂

Sent from my iPhone

On May 16, 2019, at 11:02, Anthony Holloway 
mailto:avholloway+cisco-v...@gmail.com>> wrote:

"... this stuff is soo fluid right now, it’s a contradictory mess..."

This bothers me to an unhealthy degree.  I really need to meditate or something.

On Wed, May 15, 2019 at 9:39 PM Ryan Huff 
mailto:ryanh...@outlook.com>> wrote:
Yup, this stuff is soo fluid right now, it’s a contradictory mess 😂. The 
on-prem registration, IMHO, is rrr 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 
mailto:tim.sm...@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://eur02.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%7C0c06fdfb1500415242ba08d6da0f89d8%7C84df9e7fe9f640afb435%7C1%7C0%7C636936157605890504&sdata=70z9uOBPVxB6F%2BpIk9YGMHr1OxsfRoc1%2BJGi61SJ8CU%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 mailto:ryanh...@outlook.com>>
Date: Thursday, 16 May 2019 at 12:14 pm
To: Tim Smith mailto:tim.sm...@enject.com.au>>
Cc: Jonathan Charles mailto:jonv...@gmail.com>>, 
"cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>" 
mailto:cisco-voip@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 
mailto:tim.sm...@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://eur02.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%7C0c06fdfb1500415242ba08d6da0f89d8%7C84df9e7fe9f640afb435%7C1%7C0%7C636936157605920531&sdata=QiAUsNC6BtKjjvJQWQEYxQ3FT7qc8oLU6UredrBrSnU%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 
mailto:cisco-voip-boun...@puck.nether.net>> 
on behalf of Jonathan Charles mailto:jonv...@gmail.com>>
Date: Thursday, 16 May 2019 at 9:30 am
To: Ryan Huff mailto:ryanh...@outlook.com>>
Cc: "cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>" 
mailto:cisco-voip@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 
mailto:ryanh...@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 sig

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

[Jonathan Charles]

It is for Cisco Webex Boards, Room Kits and some SX80s all registered to
the Webex Hybrid Cloud


Jonathan

On Wed, May 15, 2019 at 7:04 PM Brian Meade  wrote:

> Be aware that Call Service Connect is being deprecated for anything
> besides Video Endpoints.
>
> If this is for Webex Teams client, they want you to start looking at
> Unified CM calling in Webex Teams.
>
> 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_01.html
>
>
> If you need something behind hold/resume for mid-call controls or need
> mobile Teams client to work, Cisco is pushing towards having Teams launch
> Jabber for any phone links which can be configured as well.
>
> Long-term goal is to have Teams calling function very similar to Jabber
> softphone for Desktop and mobile.
>
> On Wed, May 15, 2019 at 7:45 PM Ryan Huff  wrote:
>
>> Inbound Flow (PSTN user calls user’s DID):
>>
>> GW > CCM > (per userWebex Hybrid CTI Device) > Exp-C > Exp-E > ControlHub
>> > (rings your cloud registered device)
>>
>> Outbound Flow (cloud registered device calls PSTN via CCM or other
>> on-prem device):
>>
>> Cloud registered device (ControlHub) > Exp-E > Exp-C > CCM (interacts
>> with the dialplan for onnet/offnet calling).
>>
>> Basically, it’s a B2B call that gets 15 pieces of flair added to it so it
>> can utilize your on-prem gateway for PSTN access. When you go through the
>> configuration, One of the steps will lead you to creating CTI devices in
>> communications manager which share the users DID (Essentially, and on
>> premise representation of the cloud registered device). The inbound flow is
>> a little unique as it essentially capitalizes on a bastardized form of SNR
>> to ring the cloud device.
>>
>> As far as security goes, you are mostly at the mercy of traditional call
>> policy rules (or more specifically writing search rules for your zones).
>>
>> I have found the following to be two good "reject" policies that tend not
>> to interfere with most deployments (though they could if the internal URIs
>> match the policy). Most organizations have Directory URIs that ultimately
>> have been inherited from the user's email address or other corporate
>> standardizations which these policies tend to avoid and also tend to deny
>> routing to a surprising amount of obvious junk (typically, I apply CPL at
>> the edge):
>>
>>
>>- ^[0-9,a-z,A-Z]{0,6}@.*
>>   -  The first 0-6 characters are made up of alphanumerics 0-9
>>   and/or upper/lower case letters, “@“ anything
>>  - Example: 123...@domain.com
>>  - Example: noa...@domian.com
>>  - Example: 9...@domain.com
>>
>>
>>- ^[0-9,a-z,A-Z]{0,6}$
>>   - The first 0-6 characters are made up of alphanumerics 0-9 and/or
>>   upper/lower case letter and do not exceed the 6th character
>>   - Example: 1000
>>   - Example: 
>>   - Example: NoAuth
>>   -
>>
>> Good Luck!
>>
>> -Ryan
>>
>> On May 15, 2019, at 19:30, Jonathan Charles  wrote:
>>
>> 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  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
>>> 
>>>
>>> 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 d

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

[Anthony Holloway]

"... this stuff is soo fluid right now, it’s a contradictory mess..."

This bothers me to an unhealthy degree.  I really need to meditate or
something.

On Wed, May 15, 2019 at 9:39 PM Ryan Huff  wrote:

> Yup, this stuff is soo fluid right now, it’s a contradictory mess 😂.
> The on-prem registration, IMHO, is rrr 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  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%7C84df9e7fe9f640afb435%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 
> *Date: *Thursday, 16 May 2019 at 12:14 pm
> *To: *Tim Smith 
> *Cc: *Jonathan Charles , "cisco-voip@puck.nether.net" <
> cisco-voip@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  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%7C84df9e7fe9f640afb435%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  on behalf of
> Jonathan Charles 
> *Date: *Thursday, 16 May 2019 at 9:30 am
> *To: *Ryan Huff 
> *Cc: *"cisco-voip@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  wrote:
>
> You’ll need a specific Webex DNS zone and the traversal trunk really just
> needs to

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

[Tim Smith]

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  on behalf of Lelio 
Fulgenzi 
Date: Thursday, 16 May 2019 at 2:09 pm
To: Ryan Huff 
Cc: "cisco-voip@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
519-824-4120 Ext. 56354 | 
le...@uoguelph.ca<mailto:le...@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 
mailto:le...@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
519-824-4120 Ext. 56354 | 
le...@uoguelph.ca<mailto:le...@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 
mailto:ryanh...@outlook.com>> wrote:
Yup, this stuff is soo fluid right now, it’s a contradictory mess 😂. The 
on-prem registration, IMHO, is rrr 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 
mailto:tim.sm...@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%7C84df9e7fe9f640afb435%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 mailto:ryanh...@outlook.com>>
Date: Thursday, 16 May 2019 at 12:14 pm
To: Tim Smith mailto:tim.sm...@enject.com.au>>
Cc: Jonathan Charles mailto:jonv...@gmail.com>>, 
"cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>" 
mailto:cisco-voip@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 
mailto:tim.sm...@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%2FExpl

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

[Lelio Fulgenzi]

"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
519-824-4120 Ext. 56354 | 
le...@uoguelph.ca<mailto:le...@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 
mailto:le...@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
519-824-4120 Ext. 56354 | 
le...@uoguelph.ca<mailto:le...@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 
mailto:ryanh...@outlook.com>> wrote:

Yup, this stuff is soo fluid right now, it’s a contradictory mess 😂. The 
on-prem registration, IMHO, is rrr 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 
mailto:tim.sm...@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%7C84df9e7fe9f640afb435%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 mailto:ryanh...@outlook.com>>
Date: Thursday, 16 May 2019 at 12:14 pm
To: Tim Smith mailto:tim.sm...@enject.com.au>>
Cc: Jonathan Charles mailto:jonv...@gmail.com>>, 
"cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>" 
mailto:cisco-voip@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 
mailto:tim.sm...@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%7C84df9e7fe9f640afb435%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 alr

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

[Lelio Fulgenzi]

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
519-824-4120 Ext. 56354 | 
le...@uoguelph.ca<mailto:le...@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 
mailto:ryanh...@outlook.com>> wrote:

Yup, this stuff is soo fluid right now, it’s a contradictory mess 😂. The 
on-prem registration, IMHO, is rrr 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 
mailto:tim.sm...@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%7C84df9e7fe9f640afb435%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 mailto:ryanh...@outlook.com>>
Date: Thursday, 16 May 2019 at 12:14 pm
To: Tim Smith mailto:tim.sm...@enject.com.au>>
Cc: Jonathan Charles mailto:jonv...@gmail.com>>, 
"cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>" 
mailto:cisco-voip@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 
mailto:tim.sm...@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%7C84df9e7fe9f640afb435%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 
mailto:cisco-voip-boun...@puck.nether.net>> 
on behalf of Jonathan Charles mailto:jonv...@gmail.com>>
Date: Thursday, 16 May 2019 at 9:30 am
To: Ryan Huff mailto:ryanh...@outlook.com>>
Cc: "cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>" 
mailto:cisco-voip@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 enterpri

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

[Ryan Huff]

Yup, this stuff is soo fluid right now, it’s a contradictory mess 😂. The 
on-prem registration, IMHO, is rrr 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 
mailto:tim.sm...@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%7C84df9e7fe9f640afb435%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 mailto:ryanh...@outlook.com>>
Date: Thursday, 16 May 2019 at 12:14 pm
To: Tim Smith mailto:tim.sm...@enject.com.au>>
Cc: Jonathan Charles mailto:jonv...@gmail.com>>, 
"cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>" 
mailto:cisco-voip@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 
mailto:tim.sm...@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%7C84df9e7fe9f640afb435%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 
mailto:cisco-voip-boun...@puck.nether.net>> 
on behalf of Jonathan Charles mailto:jonv...@gmail.com>>
Date: Thursday, 16 May 2019 at 9:30 am
To: Ryan Huff mailto:ryanh...@outlook.com>>
Cc: "cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>" 
mailto:cisco-voip@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 
mailto:ryanh...@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

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

[Tim Smith]

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

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 
Date: Thursday, 16 May 2019 at 12:14 pm
To: Tim Smith 
Cc: Jonathan Charles , "cisco-voip@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 
mailto:tim.sm...@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%7C3415229c927c4735729d08d6d9a36719%7C84df9e7fe9f640afb435%7C1%7C0%7C636935693163773518&sdata=mKiI9NZtHIy0acs0DrBHnhydCAT10YX9AQVHXWqGH%2BA%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 
mailto:cisco-voip-boun...@puck.nether.net>> 
on behalf of Jonathan Charles mailto:jonv...@gmail.com>>
Date: Thursday, 16 May 2019 at 9:30 am
To: Ryan Huff mailto:ryanh...@outlook.com>>
Cc: "cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>" 
mailto:cisco-voip@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 
mailto:ryanh...@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%7C3415229c927c4735729d08d6d9a36719%7C84df9e7fe9f640afb435%7C1%7C0%7C636935693163783529&sdata=rhoOV7yB%2FqTM7xjIPec0dXyzQ29ijSvsGME7RUenYxE%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 rela

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

[Ryan Huff]

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 
mailto:tim.sm...@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%7C3415229c927c4735729d08d6d9a36719%7C84df9e7fe9f640afb435%7C1%7C0%7C636935693163773518&sdata=mKiI9NZtHIy0acs0DrBHnhydCAT10YX9AQVHXWqGH%2BA%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 
mailto:cisco-voip-boun...@puck.nether.net>> 
on behalf of Jonathan Charles mailto:jonv...@gmail.com>>
Date: Thursday, 16 May 2019 at 9:30 am
To: Ryan Huff mailto:ryanh...@outlook.com>>
Cc: "cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>" 
mailto:cisco-voip@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 
mailto:ryanh...@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%7C3415229c927c4735729d08d6d9a36719%7C84df9e7fe9f640afb435%7C1%7C0%7C636935693163783529&sdata=rhoOV7yB%2FqTM7xjIPec0dXyzQ29ijSvsGME7RUenYxE%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 
mailto:le...@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 Ful

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

[Tim Smith]

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

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  on behalf of Jonathan 
Charles 
Date: Thursday, 16 May 2019 at 9:30 am
To: Ryan Huff 
Cc: "cisco-voip@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 
mailto:ryanh...@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

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 
mailto:le...@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 | 
le...@uoguelph.ca<mailto:le...@uoguelph.ca>

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

Error! Filename not specified.

On May 15, 2019, at 5:20 PM, Jonathan Charles 
mailto:jonv...@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@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7C5b817b

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

[Lelio Fulgenzi]

This is god content. Thanks!

One thing I’ve enabled for adoption reasons, is people being able to use the 
extension as the video address for room kits.

I know this isn’t the best design plan, but we don’t really have any other 
naming convention we could use at the moment.

I’ll have to look at your two reject ideas. Right now, we’re doing explicit 
permits.

-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 | 
le...@uoguelph.ca

www.uoguelph.ca/ccs | @UofGCCS on Instagram, 
Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

On May 15, 2019, at 7:45 PM, Ryan Huff 
mailto:ryanh...@outlook.com>> wrote:

Inbound Flow (PSTN user calls user’s DID):

GW > CCM > (per userWebex Hybrid CTI Device) > Exp-C > Exp-E > ControlHub > 
(rings your cloud registered device)

Outbound Flow (cloud registered device calls PSTN via CCM or other on-prem 
device):

Cloud registered device (ControlHub) > Exp-E > Exp-C > CCM (interacts with the 
dialplan for onnet/offnet calling).

Basically, it’s a B2B call that gets 15 pieces of flair added to it so it can 
utilize your on-prem gateway for PSTN access. When you go through the 
configuration, One of the steps will lead you to creating CTI devices in 
communications manager which share the users DID (Essentially, and on premise 
representation of the cloud registered device). The inbound flow is a little 
unique as it essentially capitalizes on a bastardized form of SNR to ring the 
cloud device.

As far as security goes, you are mostly at the mercy of traditional call policy 
rules (or more specifically writing search rules for your zones).

I have found the following to be two good "reject" policies that tend not to 
interfere with most deployments (though they could if the internal URIs match 
the policy). Most organizations have Directory URIs that ultimately have been 
inherited from the user's email address or other corporate standardizations 
which these policies tend to avoid and also tend to deny routing to a 
surprising amount of obvious junk (typically, I apply CPL at the edge):


  *   ^[0-9,a-z,A-Z]{0,6}@.*
 *The first 0-6 characters are made up of alphanumerics 0-9 and/or 
upper/lower case letters, “@“ anything
*   Example: 123...@domain.com
*   Example: noa...@domian.com
*   Example: 9...@domain.com

  *   ^[0-9,a-z,A-Z]{0,6}$
 *   The first 0-6 characters are made up of alphanumerics 0-9 and/or 
upper/lower case letter and do not exceed the 6th character
 *   Example: 1000
 *   Example: 
 *   Example: NoAuth
 *

Good Luck!

-Ryan

On May 15, 2019, at 19:30, Jonathan Charles 
mailto:jonv...@gmail.com>> wrote:

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 
mailto:ryanh...@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

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

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

[Brian Meade]

Be aware that Call Service Connect is being deprecated for anything besides
Video Endpoints.

If this is for Webex Teams client, they want you to start looking at
Unified CM calling in Webex Teams.
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_01.html


If you need something behind hold/resume for mid-call controls or need
mobile Teams client to work, Cisco is pushing towards having Teams launch
Jabber for any phone links which can be configured as well.

Long-term goal is to have Teams calling function very similar to Jabber
softphone for Desktop and mobile.

On Wed, May 15, 2019 at 7:45 PM Ryan Huff  wrote:

> Inbound Flow (PSTN user calls user’s DID):
>
> GW > CCM > (per userWebex Hybrid CTI Device) > Exp-C > Exp-E > ControlHub
> > (rings your cloud registered device)
>
> Outbound Flow (cloud registered device calls PSTN via CCM or other on-prem
> device):
>
> Cloud registered device (ControlHub) > Exp-E > Exp-C > CCM (interacts with
> the dialplan for onnet/offnet calling).
>
> Basically, it’s a B2B call that gets 15 pieces of flair added to it so it
> can utilize your on-prem gateway for PSTN access. When you go through the
> configuration, One of the steps will lead you to creating CTI devices in
> communications manager which share the users DID (Essentially, and on
> premise representation of the cloud registered device). The inbound flow is
> a little unique as it essentially capitalizes on a bastardized form of SNR
> to ring the cloud device.
>
> As far as security goes, you are mostly at the mercy of traditional call
> policy rules (or more specifically writing search rules for your zones).
>
> I have found the following to be two good "reject" policies that tend not
> to interfere with most deployments (though they could if the internal URIs
> match the policy). Most organizations have Directory URIs that ultimately
> have been inherited from the user's email address or other corporate
> standardizations which these policies tend to avoid and also tend to deny
> routing to a surprising amount of obvious junk (typically, I apply CPL at
> the edge):
>
>
>- ^[0-9,a-z,A-Z]{0,6}@.*
>   -  The first 0-6 characters are made up of alphanumerics 0-9 and/or
>   upper/lower case letters, “@“ anything
>  - Example: 123...@domain.com
>  - Example: noa...@domian.com
>  - Example: 9...@domain.com
>
>
>- ^[0-9,a-z,A-Z]{0,6}$
>   - The first 0-6 characters are made up of alphanumerics 0-9 and/or
>   upper/lower case letter and do not exceed the 6th character
>   - Example: 1000
>   - Example: 
>   - Example: NoAuth
>   -
>
> Good Luck!
>
> -Ryan
>
> On May 15, 2019, at 19:30, Jonathan Charles  wrote:
>
> 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  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
>> 
>>
>> 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 t

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

[Ryan Huff]

Inbound Flow (PSTN user calls user’s DID):

GW > CCM > (per userWebex Hybrid CTI Device) > Exp-C > Exp-E > ControlHub > 
(rings your cloud registered device)

Outbound Flow (cloud registered device calls PSTN via CCM or other on-prem 
device):

Cloud registered device (ControlHub) > Exp-E > Exp-C > CCM (interacts with the 
dialplan for onnet/offnet calling).

Basically, it’s a B2B call that gets 15 pieces of flair added to it so it can 
utilize your on-prem gateway for PSTN access. When you go through the 
configuration, One of the steps will lead you to creating CTI devices in 
communications manager which share the users DID (Essentially, and on premise 
representation of the cloud registered device). The inbound flow is a little 
unique as it essentially capitalizes on a bastardized form of SNR to ring the 
cloud device.

As far as security goes, you are mostly at the mercy of traditional call policy 
rules (or more specifically writing search rules for your zones).

I have found the following to be two good "reject" policies that tend not to 
interfere with most deployments (though they could if the internal URIs match 
the policy). Most organizations have Directory URIs that ultimately have been 
inherited from the user's email address or other corporate standardizations 
which these policies tend to avoid and also tend to deny routing to a 
surprising amount of obvious junk (typically, I apply CPL at the edge):


  *   ^[0-9,a-z,A-Z]{0,6}@.*
 *The first 0-6 characters are made up of alphanumerics 0-9 and/or 
upper/lower case letters, “@“ anything
*   Example: 123...@domain.com
*   Example: noa...@domian.com
*   Example: 9...@domain.com

  *   ^[0-9,a-z,A-Z]{0,6}$
 *   The first 0-6 characters are made up of alphanumerics 0-9 and/or 
upper/lower case letter and do not exceed the 6th character
 *   Example: 1000
 *   Example: 
 *   Example: NoAuth
 *

Good Luck!

-Ryan

On May 15, 2019, at 19:30, Jonathan Charles 
mailto:jonv...@gmail.com>> wrote:

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 
mailto:ryanh...@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

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 
mailto:le...@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 te

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

[Charles Goldsmith]

It's only a matter of time that the SCCP phones will not function with the
latest features.  I realize that the 79x5's just went EOL a couple of years
ago, but we've had SIP only phones for at least 8 years now.

On Wed, May 15, 2019 at 6:22 PM Lelio Fulgenzi  wrote:

> Whoa.
>
> 
> Unified CM Device Requirements
>
> Hybrid Call Service is supported only with Cisco SIP phones and Cisco
> Jabber clients that are registered to Unified CM.
>
> *SCCP phones may encounter problems due to the 48-character limitation on
> the destination address. *
>
> 
>
> *-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 <519-824-4120;56354> | le...@uoguelph.ca
>
>
>
> www.uoguelph.ca/ccs | @UofGCCS on Instagram, Twitter and Facebook
>
>
>
> [image: University of Guelph Cornerstone with Improve Life tagline]
>
> On May 15, 2019, at 7:16 PM, Ryan Huff  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
>
> 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  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 <519-824-4120;56354> | le...@uoguelph.ca
>
>
>
> www.uoguelph.ca/ccs
> 
>  |
> @UofGCCS on Instagram, Twitter and Facebook
>
>
>
> [image: University of Guelph Cornerstone with Improve Life tagline]
>
> On May 15, 2019, at 5:20 PM, Jonathan Charles  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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> 
>
> ___
> cisco-voip mailing

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

[Jonathan Charles]

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  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
>
> 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  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 <519-824-4120;56354> | le...@uoguelph.ca
>
>
>
> www.uoguelph.ca/ccs
> 
>  |
> @UofGCCS on Instagram, Twitter and Facebook
>
>
>
> [image: University of Guelph Cornerstone with Improve Life tagline]
>
> On May 15, 2019, at 5:20 PM, Jonathan Charles  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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> 
>
> ___
> cisco-voip mailing list
> cisco-voip@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%7C84df9e7fe9f640afb435%7C1%7C0%7C636935569711652307&sdata=UCJB8OKg5UlpRWHaTtp6Y2AJNzpfh6NmVWdejkBYmDI%3D&reserved=0
>
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

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

[Lelio Fulgenzi]

Whoa.


Unified CM Device Requirements

Hybrid Call Service is supported only with Cisco SIP phones and Cisco Jabber 
clients that are registered to Unified CM.

SCCP phones may encounter problems due to the 48-character limitation on the 
destination address.



-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 | 
le...@uoguelph.ca

www.uoguelph.ca/ccs | @UofGCCS on Instagram, 
Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

On May 15, 2019, at 7:16 PM, Ryan Huff 
mailto:ryanh...@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

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 
mailto:le...@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 | 
le...@uoguelph.ca

www.uoguelph.ca/ccs
 | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

On May 15, 2019, at 5:20 PM, Jonathan Charles 
mailto:jonv...@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@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@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%7C84df9e7fe9f640afb435%7C1%7C0%7C636935569711652307&sdata=UCJB8OKg5UlpRWHaTtp6Y2AJNzpfh

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

[Ryan Huff]

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

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 
mailto:le...@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 | 
le...@uoguelph.ca

www.uoguelph.ca/ccs
 | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

On May 15, 2019, at 5:20 PM, Jonathan Charles 
mailto:jonv...@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@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@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%7C84df9e7fe9f640afb435%7C1%7C0%7C636935569711652307&sdata=UCJB8OKg5UlpRWHaTtp6Y2AJNzpfh6NmVWdejkBYmDI%3D&reserved=0
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

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

[Lelio Fulgenzi]

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 | 
le...@uoguelph.ca

www.uoguelph.ca/ccs | @UofGCCS on Instagram, 
Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

On May 15, 2019, at 5:20 PM, Jonathan Charles 
mailto:jonv...@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@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

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

[Jonathan Charles]

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@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip