Call control groups in UCCX

Answered Question
Sep 19th, 2011

Hello All. We are creating Call Control Groups in UCCX 8.5 for the agents and noticed something strange. We initially created a call control group that had 10 CTI ports. We started at 2550 and it created the phones and DN's in CUCM 8.6 fine. We then deleted the CTI ports and DN's in CUCM first and then deleted the call control group in UCCX. We do realize now that we could have deleted the group in UCCX and the phone's and DN's would have been removed automatically from CUCM. However after doing the manual delete if we create a new call control group and start at 2550 it will not start at 2550 but jumps to 2560. It somehow thinks the 2550-2559 ports are still there even though they are removed from CUCM. Do I need to restart some service so that UCCX recognizes these ports again?

Thanks,

Phil

I have this problem too.
0 votes
Correct Answer by Aaron Harrison about 2 years 7 months ago

Hi Phil

Basically when you deleted the CTI Port devices, the DNs are not deleted, they are orphaned. Go to Route Plan Report (in the CCMAdmin call routing menu) and run it, change the drop-down box to 'unassigned DNs'. You'll see your 255x DNs, and you can deleted them from there.

They are then available to be created from UCCX. UCCX basically checks whether the numbers exist, and if they already exist (including as orphaned/unassigned DNs) it skips over them until it finds the next free number.

Regards

Aaron

Please rate helpful posts..

Correct Answer by frzhang about 2 years 7 months ago

Restart AXL CTI Manager in CUCM may help. UCCX tells CUCM to create CTI ports from your specified starting number, CUCM decides the rest.

  • 1
  • 2
  • 3
  • 4
  • 5
Average Rating: 5 (2 ratings)
Correct Answer
frzhang Mon, 09/19/2011 - 11:27

Restart AXL CTI Manager in CUCM may help. UCCX tells CUCM to create CTI ports from your specified starting number, CUCM decides the rest.

Correct Answer
Aaron Harrison Mon, 09/19/2011 - 13:58

Hi Phil

Basically when you deleted the CTI Port devices, the DNs are not deleted, they are orphaned. Go to Route Plan Report (in the CCMAdmin call routing menu) and run it, change the drop-down box to 'unassigned DNs'. You'll see your 255x DNs, and you can deleted them from there.

They are then available to be created from UCCX. UCCX basically checks whether the numbers exist, and if they already exist (including as orphaned/unassigned DNs) it skips over them until it finds the next free number.

Regards

Aaron

Please rate helpful posts..

pbradley435 Tue, 09/20/2011 - 06:00

Frzhang, that did create the correct starting number once I restarted those services in CUCM.

Aaron, I did do a test on this and did see the orphaned DN's. Once I removed them it did start at the correct number after I removed the call control group from CCX. I tried just changing the port count to one then moving up to a higher number and that did not work. Thanks!

hadysalah Wed, 09/05/2012 - 09:10

we faced the same problem we tried waht you said above but the same issue and when restart the standby UCCX  server , the problem solved

Actions

Login or Register to take actions

This Discussion

Posted September 19, 2011 at 6:39 AM
Stats:
Replies:4 Avg. Rating:5
Views:2219 Votes:0
Shares:0
Tags: uccx8.5
+

Related Content

Discussions Leaderboard