cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
4458
Views
0
Helpful
18
Replies

ILS Configuration issue CUCM 9.1.1

Piotr Mlodawski
Level 1
Level 1

Hi,

I have configured ILS on two CUCM 9.1.1 clusters (Hub and Spoke). They authenticate using password (not with certificate). The spoke seems to have registered to the hub. However, the clusters do not seem to see each other.

  Advanced Features -> ILS Configuration ->ILS Clusters and Directory URI Imported Catalogs (bottom section ) is emty on Spoke and on Hub this section contains only Hub cluster.

On the Hub i can see following info:

Found 1 hub cluster(s), 0 spoke cluster(s), and 0 directory URI imported catalog(s).

On the Spoke I can see follwoing info:

Found 0 hub cluster(s), 0 spoke cluster(s), and 0 directory URI imported catalog(s).

The clusters have uniques cluster IDs in Enterprise Parameters.

The tomcat-trust certificates have been exchanged (although this step was not necessary, since I am using password authentication.

If anyone has any ideas, please help.

Thanks

18 Replies 18

I had the same issue, and fixed it using the following procedures

- Remove the cluster domain and fqdn on service parameters in both sites;

- Cancel the registration in the spoke cluster

- Saved the spoke cluster again, with the hub Publisher IP;

- Restarted ILS service

- Wait the synchronize time.

HI

Look i just tested on same version , it was working without any issues.Can you try to make it again :just change the "password" and select HUB after save kindly check that HUB configuration overwrite standalone , and same for Spoke. Check also the SIP trunk between the both clusters "on the sip trunk destination ".Restart service intercluster look up helped me to solve same issue for one of my customers.

Thanks

Hi,

Thanks for tyour promt answer:

1. Yes my intention is to use URI dialing.

 

2. The registration seems to be successful. There is no "Cancel" button anymore. I can change Spoke back to Stanalone cluster. Then change it back to Spoke and enter the IP of the hub as the registration server. I have already doen it before.

3. I have just restarted ILS service on Hub and Spoke. Did not change anything.

Regards

 

 

 

 

 

Issa NDIAYE
Level 1
Level 1

Hello

try this solution:

ON YOUR HQ site:

for each user on End user, specify his uri dialing: like hquser1@cisco.com

 Associate each ip phone with his user (owner id), do same on DN

Create Sip profile by coping the standard, named URI-SIP-PROFILE, on it

check "Use Qualified Domain Name in SIP Request"

Create CSS named URI-CSS and add partition uri directory on it

on CSS of DN user choose URI-CSS

Create SIP Trunk named URI-TRUNK, choose URI-SIP-PROFILE

in inbound call CSS choose URI-CSS

Create SIP Route Pattern to you br like: br.route, choose URI-TRUNK

on Intercluster Directory URI Configuration, check Exchange Direct. uri and on

Route string: hq.route

Go to ILS configuration, choose Hub Cluster, set password (be carfull must same on Br)

click on save, set nothing on ip registration, click ok

ON YOUR BR site:

for each user on End user, specify his uri dialing: like bruser1@cisco.com

 Associate each ip phone with his user (owner id), do same on DN

Create Sip profile by coping the standard, named URI-SIP-PROFILE, on it

check "Use Qualified Domain Name in SIP Request"

Create CSS named URI-CSS and add partition uri directory on it

on CSS on each DN choose URI-CSS

Create SIP Trunk named URI-TRUNK, choose URI-SIP-PROFILE

in inbound call CSS choose URI-CSS

Create SIP Route Pattern to you hq like: hq.route, choose URI-TRUNK

on Intercluster Directory URI Configuration, check Exchange Direct. uri and on

Route string: br.route

Go to ILS configuration, choose Spoke Cluster, set password (be carefull must same on hq)

click on save, set ip address of QH publisher, click ok

after 2 minutes click on Refresh, You ILS successfully registered!!! 

Try dialing URI,

it will work fine:)

 

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: