UCXN: Can't Uncheck "Ignore Caller Input"

[MitelInMyBlood]

UNITY CXN 8.02

One of my call handlers has "Ignore Caller Input" checked for the alternate greeting. The customer wants to change this but for some reason I am unable to. If I make the change & try to save it, ucxn errors-out with "Internal System Error". It does not matter whether the alternate greeting is enabled or disabled.

The template from which this CH was built does not have 'Ignore Caller input' checked for the Alternate greeting so I'm unsure how this came into being in the first place unless someone intentionally (or unintentionally) placed a check mark there. In any case I need to undo it so callers can select options during times when the call handler is in "alternate greeting" mode.

Obviously I'm looking for a fix that does not involve deleting and rebuilding the call handler from scratch.... Been there & done that.

Thanks in advance



Original MUG/NAMU Charter Member

 

[whykap]

I have not seen this before nor can I duplicate it. Is it checked then but you can't uncheck it? Any other call handlers having that same behavior?
I wonder if you have a dependancy somewhere (not sure what that would be though).

 

[MitelInMyBlood]

Thanks.

I talked to a local CCNA-Voice about it today. The opinion given was that the call handler had somehow become corrupted (root cause unknown). We were left with 2 options; reboot ucxn which still may not fix it else delete the call handler and rebuild it. I went with the latter option as the lesser of two evils. A 3rd option to open a TAC case was also suggested, but my job closely resembles that of a fireman and around here Rome is burning daily, so you cut your losses and move on.

As background, this call handler was created last week to take the place of a simple Octel Type-1 "announce-only" mailbox and since UCXN has the option of accepting caller input and redirecting the (call handler owner) to the greetings administrator, I figured that would be easier for my end user to grasp than having to learn & remember how to access the Greetings Administrator via other means. It worked flawlessly.... for about 72 hours.


Original MUG/NAMU Charter Member

 

[MitelInMyBlood]

A UCXN system reboot looks more and more likely. I was able to rebuild the flaky Call Handler to get the end user satisfied, but now I cannot delete the old corrupted CH. I checked for dependencies and there are none, though any attempt to delete the CH will abort stating that some resources are still in use.

Original MUG/NAMU Charter Member

 

[whykap]

when you login to the server via cli, after you autenticate with the administtrator credentials, do you get any errors thrown at you? Just curious.

 

[MitelInMyBlood]

Nothing out of the ordinary, just the usual admin: prompt.




Original MUG/NAMU Charter Member

 

[whykap]

Just checking as there are some bugs out there but not what I was thinking here.
I doubt a reboot will fix this. I would open a TAC case as something seems to be corrupt. Never seen this before.

 

[MitelInMyBlood]

Thanks (I think) Just what I need to do... spend another 2 hrs on the phone in a noisey server room trying to communicate with someone with bad diction and a heavy Hindu accent. I know those guys are smart but at times it's awful hard (for me) to understand some of them.


Original MUG/NAMU Charter Member

 

[MitelInMyBlood]

I had some time to research this some more today and was finally successful in getting the Call Handler deleted. It seems that even though no dependencies were shown, there were still a few screens that had "other than" default data in them. By going through every screen and setting all fields back at default values, I was finally able to delete this call handler.

Lesson learned: Just because UCXN says there are no dependencies, you cannot depend on that as being the gospel truth. Any fields containing anything other than factory default settings must be put back to their original default values before attempting to delete a Call Handler.


Original MUG/NAMU Charter Member