The deployment guide does talk about the appropriate search rule needed. There 
is a search rule that must match the first entry in CUCM’s Enterprise 
Parameter, “Fully Qualified Cluster Domain”.

I would review the sections that describe the configuration of Expressway-E and 
Expressway-C: 
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/spark/hybridservices/callservices/cmgt_b_ciscospark-hybrid-call-service-config-guide/cmgt_b_ciscospark-hybrid-call-service-config-guide_chapter_0110.html

Sent from my iPhone

On Sep 10, 2018, at 04:28, Dana Tong 
<dana.t...@yellit.com.au<mailto:dana.t...@yellit.com.au>> wrote:

Hi all,

I have made some progress. I can see the call come in to the Expressway-E now 
but the search history says  
x...@cluster1.company.com.au<mailto:x...@cluster1.company.com.au>

My CUCM Enterprise parameter for “Cluster Fully Qualified Domain Name” is 
cluster1.company.com.au<http://cluster1.company.com.au> so it’s learning this 
via AXL on the Expressway Connector.

Do I need some kind of search rule / or transform on my Expressway Edge to 
convert this back to x...@company.com.au<mailto:x...@company.com.au>?

Cheers
Dana


From: Brian Meade <bmead...@vt.edu<mailto:bmead...@vt.edu>>
Sent: Friday, 7 September 2018 9:25 PM
To: Dana Tong <dana.t...@yellit.com.au<mailto:dana.t...@yellit.com.au>>
Cc: Ryan Huff <ryanh...@outlook.com<mailto:ryanh...@outlook.com>>; cisco-voip 
voyp list <cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>>
Subject: Re: [cisco-voip] Webex hybrid call service connect unable to find user

This is when you've got to look through the B2B setup and make sure MTLS is 
setup properly and that the certificates for Webex have been imported into your 
Expressway-E.  If you run diagnostics logging on the Expressway-E for a call, 
do you see anything in the capture for tcp.port==5062?

On Thu, Sep 6, 2018 at 8:43 PM Dana Tong 
<dana.t...@yellit.com.au<mailto:dana.t...@yellit.com.au>> wrote:
Yep. I have an enduser in CUCM with a Mail ID. This portion is okay. I think 
it’s more a call setup from Webex to Expressway Edge problem.

I see no incoming call on the Edge.

[cid:image003.jpg@01D44697.8DA53ED0]


[cid:image004.png@01D44697.8DA53ED0]


[cid:image005.png@01D44697.8DA53ED0]

From: Ryan Huff <ryanh...@outlook.com<mailto:ryanh...@outlook.com>>
Sent: Friday, 7 September 2018 10:35 AM
To: Dana Tong <dana.t...@yellit.com.au<mailto:dana.t...@yellit.com.au>>
Cc: Brian Meade <bmead...@vt.edu<mailto:bmead...@vt.edu>>; cisco-voip voyp list 
<cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>>
Subject: Re: [cisco-voip] Webex hybrid call service connect unable to find user

When you added the WebEx Board, did you select Hybrid Calling for PSTN calling? 
Also, the WebEx Board device, needs represented as an end user in cucm with a 
uri for the OBTP feature to work.
Sent from my iPhone

On Sep 6, 2018, at 20:31, Dana Tong 
<dana.t...@yellit.com.au<mailto:dana.t...@yellit.com.au>> wrote:
So Premise to cloud calls are working. But Webex board to Premise is not 
working.

I don’t see anything in the Edge search history. Is there some tips on what 
logs to review?

Cheers
Dana


From: cisco-voip 
<cisco-voip-boun...@puck.nether.net<mailto:cisco-voip-boun...@puck.nether.net>> 
On Behalf Of Dana Tong
Sent: Friday, 7 September 2018 10:07 AM
To: Brian Meade <bmead...@vt.edu<mailto:bmead...@vt.edu>>
Cc: cisco-voip voyp list 
<cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>>
Subject: Re: [cisco-voip] Webex hybrid call service connect unable to find user

I rebooted the Exp-C Con and it’s now all working.

Cheers
Dana


From: Brian Meade <bmead...@vt.edu<mailto:bmead...@vt.edu>>
Sent: Friday, 7 September 2018 12:22 AM
To: Dana Tong <dana.t...@yellit.com.au<mailto:dana.t...@yellit.com.au>>
Cc: cisco-voip voyp list 
<cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>>
Subject: Re: [cisco-voip] Webex hybrid call service connect unable to find user

I would just manually create the devices.  There are many limitations with 
automatically creating the devices.

On Thu, Sep 6, 2018 at 6:34 AM Dana Tong 
<dana.t...@yellit.com.au<mailto:dana.t...@yellit.com.au>> wrote:
Further to this. When I search all users, the user is present but it looks like 
he controls many phones which is odd.

I’ve tried to register a webex board also for call service connect and it 
reports unable to find a CUCM user with a matching mail ID. However I can 
confirm that I created the user with the matching mail ID.

Thoughts?

Cheers
Dana


From: Dana Tong
Sent: Thursday, 6 September 2018 7:23 PM
To: cisco-voip voyp list 
<cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>>
Subject: Webex hybrid call service connect unable to find user

Hi all,

Trying to deploy Call Service Connect but when I run the process to 
automatically deploy the Spark Remote Device I get a  [User Not Found!].

I am using a text file with a single user name as a test. The username is in 
the same format as the CUCM User ID.

Cheers
Dana


_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7C7433dc27fead46ad4b5008d61459503e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636718771160483392&sdata=q8sCcMzwo%2BWibNF2Zp0MPtJRQe2SAfBqdEOCauHLubw%3D&reserved=0>
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&amp;data=02%7C01%7C%7C7433dc27fead46ad4b5008d61459503e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636718771160639614&amp;sdata=wSLGeuoHZ3uTUhP8i4yG%2Fz04s%2FQ7FheajCLOg2lHGl8%3D&amp;reserved=0
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Reply via email to