Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
452
Views
5
Helpful
1
Replies

UCCX - CTI RP showing as registered to inactive server

us10610
Level 4
Level 4

‎03-23-2015 01:32 PM - edited ‎03-15-2019 06:06 AM

Product Ver: 8.5.1.11002-22

When creating a new trigger from the primary UCX server, it is created on UCM but registered to the secondary UCX server. Receiving a busy when dialing the newly created RP's all of which appear to be registered to the secondary UCX node. The systems appear to be sync'd without errors and I'm at a loss of how this process is supposed to work.

 

Another side note, is that we've hit a software defect which requires an upgrade. The known defect (CSCtz14497) was causing a crash dump and required us to disable the VoIP monitor on both nodes as a work around. Currently the cluster shows partial service but seemed to be expected considering this service state.

 

Any help understanding how the RP creation process works or better yet some suggestions of how to resolve this issue would be appreciated.

 

Thanks,

Greg

 

Labels:
0 Helpful
1 Reply 1

Jonathan Schulenberg
Hall of Fame
Hall of Fame

‎03-24-2015 07:17 PM

This isn't necessarily the cause of your problem. Both CCX nodes always register the CTI RP and CUCM sends call events to both nodes; only the node with mastership responds with the Call Redirect command to one of its CTI Ports. Because /ccmadmin lacks a mechanism of showing multiple registered IPs for a CTI RP it just shows the most recent one. Depending on how things happened (e.g. last node booted) this could be either node.

  • Does the trigger work if you assign it to a known-working application? In other words, are you sure this isn't a script problem?
  • Did you deal with Media Termination support? If the Call Control Group doesn't provide it by default you need to select a CMT group.
    If you're totally lost by this statement, delete your new Trigger and copy an existing one that works, changing only the settings you need.
  • What happens if you failover to the secondary node after-hours? Does the call suddenly work? This would suggest something is hung on the first node and it's probably easier to just reboot it and move on with your life.
  • Are the Trigger CSS and Redirecting CSS setting the same between a working and non-working trigger?

 

Customers Also Viewed These Support Documents