[cisco-voip] Cisco Spark/Hybrid Cloud to CUCM call failes

Mon Mar 30 14:36:16 EDT 2020

Adam,

Thanks for your reply.  I think its a problem with Webex Control hub. I went through a bunch of old Cisco live Hybrid presentations and looked a the debugs from the trouble shooting section. It looks like Control Hub is adding "cluster1" to the invite. Look at the screen shot below.
[cid:85d5ecd3-1b7d-48a2-a297-5ce02053c289]

It should be To: <sip:4866 at domain.com;user=phone>, but control hub has it 4866 at cluster1.domain.com

The Route is correct <sip:cluster1.domain.com;lr>

I think I need to open a case.

________________________________
From: Pawlowski, Adam <ajp26 at buffalo.edu>
Sent: Monday, March 30, 2020 11:44 AM
To: Mike O <mikeeo at msn.com>; James B <james.buchanan2 at gmail.com>; cisco-voip (cisco-voip at puck.nether.net) <cisco-voip at puck.nether.net>
Subject: RE: [cisco-voip] Cisco Spark/Hybrid Cloud to CUCM call failes

Hi Mike,

You need zones and search rules, it doesn’t inherently know what to do with it.

In our system, we have a search rule set for any alias in from the E cluster across a traversal zone towards the C cluster. I sieve out the garbage with call policy language on the E cluster.

On the C itself, I have a neighbor zone back to the UCM cluster with a search rule for the cluster fqdn which is what these requests are going to come in as. That zone is then explicitly configured for the call processing nodes in the cluster.

The E’s default behavior (maybe the C too I don’t route through it otherwise) is to go off and do a search for SRV records for the domain if you let it attempt to search and forward off the internet so that’s probably why you’re seeing that.

So

  *   Traversal zone (c and e)
  *   Search rule to match something on the E -> C over that zone
  *   Neighbor zone (c)
  *   Search rule to match the cluster fqdn C -> UCM over that zone

Then that needs to have a trunk that will accept the call with the right CSS.

I did not reuse ports and have a different trunk for it. I think this is in the guide but the guides are confusing.

Adam

From: cisco-voip <cisco-voip-bounces at puck.nether.net> On Behalf Of Mike O
Sent: Sunday, March 29, 2020 7:37 PM
To: James B <james.buchanan2 at gmail.com>; cisco-voip (cisco-voip at puck.nether.net) <cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Cisco Spark/Hybrid Cloud to CUCM call failes

Hi James,

1) No events linked to any incoming calls On EXP-C. I can make on prem calls to cloud just fine.

2)  Control Hub is configured and Expressway E is correctly configured(according to control hub tests)

3) Yes, we are using a CA Signed cert. TLS is working due to the fact outbound calls to the cloud work fine.

See attached screen shot from CSA it looks like I'm missing a SRV record, but its not referenced in the documentation.

[cid:image001.png at 01D60688.25F39E50]

[cid:image002.png at 01D60688.25F39E50]

________________________________

From: James B <james.buchanan2 at gmail.com<mailto:james.buchanan2 at gmail.com>>
Sent: Sunday, March 29, 2020 6:20 PM
To: Mike O <MikeeO at msn.com<mailto:MikeeO at msn.com>>; cisco-voip (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] Cisco Spark/Hybrid Cloud to CUCM call failes

Hello,

  1.  Are there any logs in the Expressway C for this call at all? Check the Event Logs. That’ll tell you if it ever reaches the C.
  2.  Do you have the Expressway-E configured in the Webex Control Hub as the destination for these calls?
  3.  This type of error can be related to certificates. Are you using a CA-signed certificate on your Expressway E?

Thanks,

James

From: Mike O<mailto:MikeeO at msn.com>
Sent: 29 March 2020 12:10
To: cisco-voip (cisco-voip at puck.nether.net)<mailto:cisco-voip at puck.nether.net>
Subject: [cisco-voip] Cisco Spark/Hybrid Cloud to CUCM call failes

Hi All,

I've racked my brain on this. I cannot get a call from the cloud to the on prem CUCM to work. On-prem to cloud works fine so I know Expressway to cloud TLS is working etc. I've attached a screen shot of the call leg from expressway -E where the call gets rejected with 404 not found. I can ping and resolve cluster1.domain.com (which is the pub).

Thanks,

Mike

[cid:image003.png at 01D60688.25F39E50]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200330/2f59291b/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 93899 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200330/2f59291b/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 24019 bytes
Desc: image002.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200330/2f59291b/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 30502 bytes
Desc: image003.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200330/2f59291b/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 19169 bytes
Desc: image.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200330/2f59291b/attachment-0007.png>