Multiple Holiday Greetings in System Call Handler for UC 7.0

Hi All,
Is there any way to play individual Holiday Greetings in a System Call Handler in UC 7.0, i.e. XMas Day Greeting gets played on XMas Day and New Year's Greeting gets played on New Year
As far as Cisco's Doc's I havent seen anywhere this being specified.
Any helpful would be greatly appreciated.
Regards
Sam Wilson

Hi David,
Thanks for your prompt reply.
So does it mean I have to record the greetings before every holiday and set it, or there is a way, to fall it over to a different Call Handler each with unique Holiday Greetings.
Regards
Sam Wilson

Similar Messages

Multiple Holiday Schedules on one Call Handler

Hello, I search previously for a solution to this problem, but have been unsuccessful. I am running Cisco Unity Connection 8.5.1.
Current Setup:
Company has a system call handler named "Company AA" that serves as their autoattendant for answering incoming calls.
Company has a holiday schedule associated to "Company AA" which includes recognized holidays, and an personalized greeting recording stating they are closed for the holiday.
What needs done:
Company has scheduled staff meetings throughout the year. These need to be input into the system so that on these dates/times, a different personalized greeting recording plays stating that they are closed. This needs to be a different recording than the normal Holiday greeting (so I cant just add the dates to the already existing holiday greeting).
Is this possible with Cisco Unity Connection?
Thanks!
Derek

Hello Derek,
It is possible, however, you will need to create a different Call Handler and Schedule per Holiday, in this example I am going to use just 3 holidays (July 4th, January 1st and December 25th. The process is kind of complex, but here we go.
1st: Create the Call Handlers:
Create a CallHandler for the Company AA
Create a CallHandler for January 1st
Create a CallHandler for July 4th
Create a CallHandler for December 25th
2nd: Create the Holiday Schedules
Create a Holiday Schedule for the Company AA CallHandler and add all the holidays here (January 1st, July 4th, and December 25th).
Create a Holiday Schedule for the January 1st CallHandler and add just the July 4th, and December 25th holidays here
Create a Holiday Schedule for the July 4th CallHandler and add just the December 25th holiday here
Create a Holiday Schedule for the   December 25th CallHandler and do not add any holdays
3rd: Create the System Schedules
Create a System Schedule for the Company AA CallHandler and associate it to the Company AA Holiday Schedule (Define your working/after hours schedule here).
Create a System Schedule for the January 1st CallHandler and associate it to the January 1st Holiday Schedule (Make it 24/7)
Create a System Schedule for the July 4th CallHandler and associate it to the July 4th Holiday Schedule (Make it 24/7)
Create a System Schedule for the December 25th CallHandler and associate it to the December 25th Holiday Schedule (Make it 24/7)
4rd: Call Handler configuration
Company AA
Go to the Company AA CallHandler, and under Active Schedule select the Company AA System Schedule.
Setup the Closed and Standard Greetings/Transfer Rules as you wish.
Go to the Holiday Greeting and select Nothing and uncheck the Play the "Record Your Message at the Tone" Prompt options under Callers Hear.
Under the After Greeting section, select Call Handler >> January 1st >> Go Directly to Greetings.
Check the Greeting Enabled with No End Date and Time option and save the configuration
January 1st
Go to the January 1st CallHandler, and under Active Schedule select the January 1st System Schedule.
Go to the Standard Greeting and setup the message that you want to play during January 1st here, if you want to transfer the call, you will need to change the Standard Call Transfer Rule as well.
Go to the Holiday Greeting and select Nothing and uncheck the Play the "Record Your Message at the Tone" Prompt options under Callers Hear.
Under the After Greeting section, select Call Handler >> July 4th >> Go Directly to Greetings.
Check the Greeting Enabled with No End Date and Time option and save the configuration
July 4th
Go to the July 4th CallHandler, and under Active Schedule select the July 4th System Schedule.
Go to the Standard Greeting and setup the message that you want to play during July 4th here, if you want to transfer the call, you will need to change the Standard Call Transfer Rule as well.
Go to the Holiday Greeting and select Nothing and uncheck the Play the "Record Your Message at the Tone" Prompt options under Callers Hear.
Under the After Greeting section, select Call Handler >> December 25th >> Go Directly to Greetings.
Check the Greeting Enabled with No End Date and Time option and save the configuration
December 25th
Go to the December 25th CallHandler, and under Active Schedule select the December 25th System Schedule.
Go to the Standard Greeting and setup the message that you want to play during December 25th here, if you want to transfer the call, you will need to change the Standard Call Transfer Rule as well.
Go to the Holiday Greeting and select Nothing and uncheck the Play the "Record Your Message at the Tone" Prompt options under Callers Hear.
Notes:
     As mentioned above, this process is complex and the best way to achieve this will be to create an excel table with the settings of every CallHandler so you can check them before implementing this in production, please note that the last Call Handler Holiday Schedule is empty, as well as the Holiday Greeting of this CallHandler since it will only play the Standard Greeting (24/7) schedule.
     The second
     The third thing you need keep in mind is that if you need to change the working hours schedule, you will do it on the main CallHandler only (Company AA), since the other system schedules are used only for holiday and during the holiday those are set to work 24/7.
Explanation:
     This implementation of distinctive holidays works because when the AA CallHandler check the holiday schedule during July 4th, it will send the the call to the holiday greeting since it is marked as a holiday on its schedule, the holiday greeting of the AA will send the call to the January 1st Call Handler; then, the January 1st CallHandler will do the same, since July 4th is marked as a holiday, it will forward the call to the Holiday Greeting which will send it to another CallHandler (July 4th). When the call gets to July 4th CallHandler it checks its schedule, since no holidays are marked on this particular CallHandler for July 4th, it will check whether it should play the Standard or Closed greeting, since this schedule was setup as 24/7, it will play the Standard Greeting of the July 4th CallHandler and stop hunting.
I hope you this helps you and feel free to shoot me with any questions you might have.
HTH
--espereir

Restore default greeting for system call handler

Unity Connection 8.0.3
There is a default system call handler called "Opening Greeting". A while ago I changed the greeting for that call handler without first saving a copy of the default greeting, and now I want to revert it to the default. How can I do that?
I think the default greeting said, "Hello, Cisco Unity Connection messaging system. From a touch tone telephone you may dial an extension at any time. For a directory of extensions press 4, otherwise, please hold to leave a general message".

Thanks. Unity Conn won't let me disable the standard greeting, but I can change it to "Callers Hear: System Default Greeting" instead of "My Personal Recording" which I have it set to now. I assume that's what you meant. Yes, I did try that, but then I hear, "sorry opening greeting is not available", so that's no good.

Unity Connection 9.1 - System Call Handler Question

Hi,
I would like to use Unity Conncetion 9.1 to transfer calls to different extensions depending on the time of day:
For example; between 07.00 and 19.00, do not play a greeting and transfer to an extension (no mailbox), outside of the times above, again do not play a greeting and transfer to a different extension.
I have configured a CTI RP and set the extension to forward all to VM. The system call handler has an active schedule of 07.00-19.00 and has a standard transfer rule set up to transfer the calls to the relevant extension. I have also configured a closed transfer rule to transfer the call to the alternative extension after 19.00. The issue I have is that when dial the original extension I get the standard greeting. How do i get Unity to transfer the call without playing the greeting?
Thanks,
Phil

Hi Phil,
You need to:
1) enable the closed greeting
2) set the standard and closed greetings to "callers hear nothing"
3) in the standard and closed greetings, after the greeting, set it to call handler, select the same call handler, and set it to attempt transfer.
4) make sure the standard and closed transfer rules are enabled, set the respective extensions to transfer to, set them to release to switch, and uncheck "Play the 'Wait While I Transfer Your Call' Prompt" for both of them.

Hunt Group to System Call Handler

Hello Everyone,
Here's my problem, I manage the phones for two companies with two different phone schemes.
One company is fine but the other one is one I'm having trouble with,
When someone calls from the outside, it goes to a hunt group from the hunt group, they are to be forwarded to a System Call Handler with an extension.
The number forwards just fine but Unity Connection doesn't pick up the call it just keeps ringing. Is there anyway to track the call flow to see what extension is being dialed from the hunt group?
Versions of the Unity / CCM are 7.x and 7.x
Thanks in advance
-Kyle S.

Hi Kyle,
If you look on the Hunt Pilot page under the Forward settings you should see where the
call is supposed to Forward to. I would try this Tool from the great suite of Unity Tools to have a look
at the call flow if it is hitting Unity Connection;
Port Status Remote Monitor for Connection (rPSM)
http://www.ciscounitytools.com/Applications/CxN/PortStatusMonitorCUC7x/PortStatusMonitorCUC7x.html
Cheers!
Rob

How can I change the default message after System Call Handler transfer error?

Hi,
I'm using Unity Connection 9.1 and System Call Handlers to allow to join internal extensions (not reachable from the PSTN).
I succeeded but I would like to change the default message played when the extension dialed is not known. I tried with Error greetings but nothing changed.
Thanks for your help.
Regards,
Julien

Just tried this on my 9.1 and 10.0(1) servers and it worked fine.
I went to the opening greeting call handler, selected the "error" greeting, set the greeting to play my personal greeting (it defaults to the system generated greeting), recording "hey, you dialed the wrong number" and then called in and during the opening greeting I dialed "88" - I heard "hey, you dialed the wrong number" and then it repeated the opening greeting recording as it should.
the default action after playing your custom greeting in this case is to "restart greeting" - which is why the opening greeting plays again.
Not sure what you did in your testing with the error greeting - check to make sure you have it set to play your personal greeting instead of the default system greeting - since you can't disable the error greeting there's not a lot of other items I can think of to check.

System call support for unicodes

Hi Solaris guru,
One of my application (C,Solaris2.7) is required to work in multiple languages. This application makes use of system & C library calls. Is it possible for a japanese user to create file names in japanese? if so how will I able to use these names (let's assume unicodes) with standard system calls and library routines which consider file names has char *?
I have noticed that Solaris provides wchar_t and (wchar.h) wide string library calls (Ex, wprintf, wscanf, wcstrcmp etc). are there any similar w-version of system calls?
I greatly appreciate your help.
Cheers
Ramesh

I don't know of a Solaris system call to copy files. I do know there is no such C or C++ standard library function.
It's easy enough to write a file copy routine, however.
C++ 4.2 is obsolete and no longer supported. It predates the 1998 C++ standard by a few years.
But using old-style C++, here is a copy-file routine:
#include <fstream.h>
int copyfiles(const char* i, const char* o)
ifstream in(i, ios::in|ios::binary);
ofstream out(o, ios::out|ios::binary);
out << in.rdbuf();
return !(!in && !out);
You pass it the names of the input and output files. It opens the files in binary mode, copies input to output if possible, and reports status by returning 1 for success and 0 for failure.
Using standard C++, the routine looks like this:
#include <fstream>
bool copyfiles(const char* i, const char* o)
std::ifstream in(i, std::ios::binary);
std::ofstream out(o, std::ios::binary);
out << in.rdbuf();
return !(!in && !out);

System call "copy" for C++ compiler 4.2?

System call "rename" is very close to what I am looking for but "copy" is better because I need to keep the original file. Where I can find it, or any equivalent?
MM
[email protected]

I don't know of a Solaris system call to copy files. I do know there is no such C or C++ standard library function.
It's easy enough to write a file copy routine, however.
C++ 4.2 is obsolete and no longer supported. It predates the 1998 C++ standard by a few years.
But using old-style C++, here is a copy-file routine:
#include <fstream.h>
int copyfiles(const char* i, const char* o)
ifstream in(i, ios::in|ios::binary);
ofstream out(o, ios::out|ios::binary);
out << in.rdbuf();
return !(!in && !out);
You pass it the names of the input and output files. It opens the files in binary mode, copies input to output if possible, and reports status by returning 1 for success and 0 for failure.
Using standard C++, the routine looks like this:
#include <fstream>
bool copyfiles(const char* i, const char* o)
std::ifstream in(i, std::ios::binary);
std::ofstream out(o, std::ios::binary);
out << in.rdbuf();
return !(!in && !out);

Calls not being directed tomy System Call Handler

I built a small auto attendant for an acquisition group of users moving to our head office, there are two toll free numbers as well as 4 DIDs, the carrier began forwarding these on move day to the pilot number of my AA.
The issue is that the toll free numbers work but the DIDs do not, they are routing to the UC default opening greeting for some reason rather than my AA call handler.
It's as though for some reason call manager is sending something different for these DIDs as opposed to the TFs and the UC doesn't know what to do with them so it sends to the default greeting.
Any ideas as to what may be happening would be greatly appreciated.
Regards,
Andrew Bardowell
Thomson Reuters

Not to worry everyone problem solved, apologies for this time waster.
The DIDs were forwarded as redirecting numbers instead of sending without as with the toll free numbers even though I specifically asked the carrier to check this on cut over night.
Consequently when the toll free numbers come in they work correctly while the DIDs do not. The TFs because the tech who worked on those programmed them to send just the called number (caller ID) and the calling number.
The tech working the DIDs sent a redirecting number as well (the original DID) which confused Unity Connection.

Deleting System Call Handlers in Unity 7.x

I am trying to delete a system call handler for a conference room extension we have. When I try and delete it I get an error message "Operation cannot be completed because the object is in use" How can I find out what its linked to so I can remove the link and delete the system call handler.

Bill et al,
For handlers (interview, directory, system, etc) that refuse to go away, follow the same process as above but use this query:
run cuc dbquery unitydirdb select * from vw_handlerreference where objectid in (select objectid from tbl_handler where fn_tolower(displayname) = lower('myhandler'));
Replace myhandler with the actual display name of the handler.
Example:
run cuc dbquery unitydirdb select * from vw_handlerreference where objectid in (select objectid from tbl_handler where fn_tolower(displayname) = lower('Goodbye'));
objectid                             displayname                   referencetype referrerobjectid                     referrerobjecttype
6b2bb401-f362-4010-8c4b-b389e4ac7eb6 Opening Greeting              AfterMessage 3cbc5620-28b9-4757-8e20-138bbb5f8a27 3
6b2bb401-f362-4010-8c4b-b389e4ac7eb6 Operator                      AfterMessage 97ce3eab-4eb4-4627-acbf-627bb98cbd8d 3
6b2bb401-f362-4010-8c4b-b389e4ac7eb6 Primary                       AfterMessage 83b42c0c-38eb-47bd-8e95-a917b55b678d 3
6b2bb401-f362-4010-8c4b-b389e4ac7eb6 Primary                       AfterMessage cd3764df-6ff9-4856-9910-abdc73e7125d 3
6b2bb401-f362-4010-8c4b-b389e4ac7eb6 RobWeimann                    AfterMessage 132b5cfe-e045-42ee-bcd0-2b7d86ce7cbf 3
6b2bb401-f362-4010-8c4b-b389e4ac7eb6 System Call Handler Template AfterMessage 51f8b56a-61ac-4909-9dba-17aa18556571 3
6b2bb401-f362-4010-8c4b-b389e4ac7eb6 System Directory Handler      NoInput       a6dea20d-f5a9-4f76-be60-8aa8994c3037 6
6b2bb401-f362-4010-8c4b-b389e4ac7eb6 System Directory Handler      NoSelection   a6dea20d-f5a9-4f76-be60-8aa8994c3037 6
6b2bb401-f362-4010-8c4b-b389e4ac7eb6 abell                         AfterMessage b55f1562-45e3-4b54-9e55-7a6d4ac081b2 3
6b2bb401-f362-4010-8c4b-b389e4ac7eb6 ebell                         AfterMessage 75c3f060-c5bf-4d24-9ffa-d056362dce47 3
6b2bb401-f362-4010-8c4b-b389e4ac7eb6 manoj3                        AfterMessage 8304ac82-63fa-4e80-9cc1-6b8052d73575 3
6b2bb401-f362-4010-8c4b-b389e4ac7eb6 miyazaki                      AfterMessage 8ce70dbd-9a6b-4ee6-8387-8a1dc4ced323 3
6b2bb401-f362-4010-8c4b-b389e4ac7eb6 operator                      AfterMessage d0906380-687c-448f-a078-d8b8b7bfa3d1 3
6b2bb401-f362-4010-8c4b-b389e4ac7eb6 undeliverablemessagesmailbox AfterMessage 964fd52e-ed65-4992-b9fe-22cc7e39f560 3
99% of the cases I've seen are with users that have a caller input option configured to point to the specific call handler. In that case, you'll see a "TTx" under the referencetype column where x=0-9. Example, TT7 means caller input key 7 is configured to send to the call handler you're trying to remove.
Hope that helps everyone,
Brad

Unity call handler problem

Hello,
If somebody can help me with Unity configuration, I will be appritiated.
I`ve got a number 555 with system call handler configured on Unity and all call gets forwarded to VM. When I am calling to 555 from my phone everything works fine. But when I try to forward all calls from another extention, let`s say from 444 to 555, I am hiting default Unity greetings for the number 555 instead of system one.
Any ideas much appritiated !
Maxim

Hi Maxim,
This is the expected behavior as Unity will see the Forwarded number
of 444 instead of 555 and doesn't know what to do with it.
So, let's say you want to route 444 to the 555 Call Handler.
You could create a Voicemail Profile in CUCM called "555 Transfer or whatever" which points to DN 555 (**Voicemail Box Mask = 555).
Apply this new profile to 444 (under DN config page VM-Profile in CUCM) and when calls route through 444 and forward to voicemail they will receive the 555 Call Handler Greeting etc.
You could also use the Forwarded Routing Rule set up in Unity to create a rule for this 444 to 555 forwarding.
Cheers!
Rob
"I don't know how, I don't know when
But you and I will meet again "
- Tom Petty

No Call Forward to Call Handler

Hi,
we have cucm 8.6 and cuc 8.6
inbound call from ITSP transferred to CUC call handler for opening greetings and by pressing '0' it transfers to operator.
i want to configure custom busy message when operator is busy with other calls.
i configured another call handler with number 1660 and forwarded the operator calls to the call handler if busy.
the busy message is playing when i dialed the number 1660 from any extension, but the calls not getting transferred when the operator is busy.
i tried with forward all calls to the callhandler and getting the message ' cannot be reachable'.
i configured busy message on opening greeting call handler itself, in the callhandler "greetings" section's "busy" option, it didn't work as the call already got transferred to cucm.so its not coming back to callhandler if the ext is busy.
please can anyone guide me to configure busy message for operator.

Hi Anas,
i tried as you said,
its transferring the call if extension is busy by skipping welcome greetings, it's not what i wanted.
i need if any inbound call comes from ITSP first the welcome message with IVR plays, if the caller press '0' then only it should transfer to operator, if the operator is busy then it should play "Operators Busy" message.

Setting up PLAR with Cisco Unity Connection Call Handler

This is a lab setup and Im doing it to learn. No customer involvement.
Setup
Analog phones - FXS Port - 2951 Router - FXS port - FXO Port - 2951 Router - CUCM 9 - UC 9
|------------PSTN Emulator-------------| |-----MGCP GW----------|
I have a CTI Route Point configured as DN 7000 and it has the default VM profile. The CTI RP is set to FWD All to VM.
The FXO port is set to PLAR to 7000.
When I dial from the PSTN analog phones through the FXO port, I hear the first ring, the FXO port answers, then I hear what sounds like the recorded message beginning to play. Immediately after, I hear the recorded message "You cannot be transferred to this number. Check the number and try again."
I dont do anything and within a second or two, I hear the recorded message for the system call handler start.
I did some more testing. I added an E1 trunk between the PSTN and the MGCP gateway. In the CUCM, I created another CTI Route Point with a DN that I could dial from my PSTN cloud. I also set that CTI Route point up to Call FWD all to VM.
When I dial using the E1 trunk, the call hits the system call handler as expected and I hear my recorded greeting (as expected).
However, calling through the FXS-FXO tie line consistently gets me the error message recording followed by my recorded greeting.
Im currently using loopstart on the tie line, though I have also tried ground start with no difference.
Any ideas?
Jeff

If I understand correctly, you want outside calls to go directly to the call handler but internal calls to ring whatever phone this extension is on.
If I am understanding correctly, then this will probably resolve it. For the purposes of the explanation I will assume that extension 1000 is the number in question:
Create a new partition, we'll just call it ToVM or something like that
Create a new CTI route point with extension 1000 and put it in the ToVM partition, forward all calls for this CTI route point to voicemail
If you don't have one already, create a calling search space for the voice gateway. Call it Gateway-CSS. This should have the same partitions that the gateway can normally call, but it should also have the ToVM partition and that partition should be HIGHER in the list than the partition that has the normal extension 1000 on it.
Apply Gateway-CSS to the gateway
Configure the normal extension 1000 (not in the ToVM partition) the way that you want it to work.
Now when external callers dial 1000 they will go to the call handler because that partition is higher in the CSS and the CTI Route point should be hit first. Internal callers will ring the phone (or whatever it is) because they only have access to the regular internal partition (and not ToVM) that 1000 is in.
This is all assuming that I understand you correctly!

SYSTEM-CALL statement

Hi experts,
please help to give some detials about below statment:
system-call init-text <p_text> using <p_field> program <program_name>.
and i got one issue with above statement:
system-call init-text p_text using 'SCN_PROJN' program 'SAPDBPSJ'.
it seems that to get field description of 'SCN_PROJN' of logical database 'PSJ'. but after this statement p_text get value as 'CN_PROJN' instead of 'Project Definition'. this issue happens after system upgrade.
please give some suggestion about above issue.
thanks a billion.
Aumas.

SYSTEM-CALL is for SAP internal use only and has been replaced by kernel methods (see ABAP documentation). You should not use this statement as a customer, and if there is a problem with SAP standard code, then check for OSS notes.
Thomas

System Call in Classes - CL_IXML

Hi Gurus,
Please interpret this code.
system-call ixml did 259129538 parameters cl_ixml=>the_ixml me rval.
Regards,
G.Srinivasan.

Hi,
system calls are used by SAP to call specific functionality of the SAP kernel... in this case, a system call is made using some parameters, including an attribute of class CL_IXML.
You can get some info on the general principle by checking the command system-call in the online help.
Note that system calls are for internal SAP implementation and use only, and should not be replicated in a customer program, since their interfaces or behaviours are not (publicly) documented and are subject to change without further notice.
Regards,
Trond
Edited by: Trond Stroemme on Nov 21, 2008 9:20 AM

Multiple Holiday Greetings in System Call Handler for UC 7.0

Similar Messages

Maybe you are looking for