First, so we have what we call our "Employee Access Line" which gives the ability to our employees to be able to call an internal extension from outside the building by calling into a DID number. This Emp Access Line has a System Call Handler in Unity, and a DN (*1898 in DID) and a CTI Route Point in CUCM.
Secondly, we have what is called the "Prompt Recording Application". This has a Directory Number (*1610 in internal) and a CTI Route Point. That DN is also associated to a System Call Handler in Unity as well, but I'm not too clear on why that has a System Call Handler anyway... When you call this extension you are taken to a Call Script in UCCX for changing Prompt messages for UCCX CSQs.
But, what I was trying to do was to allow someone to call into this Employee Access Line from outside the building and be able to dial the 1610 extension to reach the Prompt Recording Application to change prompts and the like... I had opened a TAC Case with the CUCM team, and we were able to finagle the Emp Access Line to automatically forward a call to this Prompt Recording Application. But the problem with that was, that the caller no longer had the ability to choose which extension they wanted to call, so we ended up having to change it back. So I had asked if he thought it was possible to issue a workaround by creating a new extension and have that new extension forward you to the Prompt Recording Application (*DN: 1610). He said that this was probably possible but I would need to open a new case with the Unity team, which I will do if we can't figure this out in here first. He had said that it wouldn't work the way we were trying because one device/DN can olny be associated with one Cisco Application (*i.e. either UCCX or Unity, but NOT both).
So I created a NEW Directory Number (*and a new CTI Route Point) and set it up the same way as when we had the Emp Access Line automatically forwarding to the 1610 extension. But when I call into the Employee Access Line from outside or inside the building and then dial the new DN I created (*DN 1612) I get a Cisco recording that says:
"You cannot be transferred to this number, check the number and try again."
So I googled the recording I heard above and found that this recording has to do with the Restriction Table in Cisco Unity...? Does that sound right?
So I looked at all the Restriction Tables in Cisco Unity and I didn't find anything that would be blocking this number, so I added the 1612 extension in there directly as the first rule in all the tables and made sure the "Blocked" checkbox was NOT checked... But I am still hearing that message above.
If you need them, I can get more specific with the Partitions and CSS's for each of those DNs and Devices that I mentioned above.
If anyone has any thoughts or suggestions, please feel free. It would be much apprectiated!
Forgot to add one other thing... The 1610 Extension, which is the number I want to get transferred to, is also a Unified CM Telephony Trigger: 1610
Thanks in Advance,
Sure, no problem. I have attached the script in a zip file to this post...
As for the User Auth you mentioned. In the script you'll see a variable called username, this is where you set you UCCX Admin username. Then, there is another variable called password, this is where you put the UCCX Admin's password. I changed the values of these vars to descriptions of what they are, so you should be able to see what I'm talking about.
Those username and password variables in the script will be what allows your Manager, or whomever logs in to modify prompts, the ability to actually write the prompt to UCCX.
Lastly, you'll see a variable called pin, whatever you set as the value for this variable, that will be what needs to be entered once you dial the Application's trigger that you assign the script to... Does that make sense?
Also, it's already set this way in the script, but you should keep the parameter attribute of the "pin" variable. This way if you ever want or need to modify the PIN you can do so from the Application's page in UCCX.
Hope that helps!!