CUE 8.6.4 Call Hold Step

Hi ,
Customer requirement is that when PSTN caller call into branch AA is invoked,He presses Zero call will be sent to a hunt group of operators. While caller is still waiting it is required that he hears a MoH from branch flash not a ringing tone.
Head Office contain CUCM Cluster 8.6.2,CUC 8.6.2 and CUE 8.6.4 branch is registered to CUCM using JTAPI/CTI and in case of failover to SRST it uses SIP.
Call Scenario Required as follow:
PSTN Caller-->FXO-->AA(Welcome)-->Press "0"-->Operator Huntgroup (Caller hears MoH instead of ringback while call is ringing on ip phones operators)
Please advie your help.
Thanks.

trying from boothelper, here is log on tftp server;
Connection received from 172.83.112.12 on port 2001 [02/04 11:22:36.864]
Read request for file . Mode octet [02/04 11:22:36.864]
OACK: [02/04 11:22:36.864]
Using local port 55558 [02/04 11:22:36.864]
TIMEOUT waiting for Ack block #0 [02/04 11:22:51.934]
Connection received from 172.83.112.12 on port 2002 [02/04 11:23:16.457]
Read request for file . Mode octet [02/04 11:23:16.457]
OACK: [02/04 11:23:16.457]
Using local port 55559 [02/04 11:23:16.457]
TIMEOUT waiting for Ack block #0 [02/04 11:23:31.527]
Connection received from 172.83.112.12 on port 2003 [02/04 11:23:56.066]
Read request for file . Mode octet [02/04 11:23:56.066]
OACK: [02/04 11:23:56.066]
Using local port 62995 [02/04 11:23:56.066]
TIMEOUT waiting for Ack block #0 [02/04 11:24:11.135]
Connection received from 172.83.112.12 on port 2004 [02/04 11:24:35.658]
Read request for file . Mode octet [02/04 11:24:35.658]
OACK: [02/04 11:24:35.658]
Using local port 62996 [02/04 11:24:35.658]
TIMEOUT waiting for Ack block #0 [02/04 11:24:50.721]
Connection received from 172.83.112.12 on port 2005 [02/04 11:25:15.260]
Read request for file . Mode octet [02/04 11:25:15.260]
OACK: [02/04 11:25:15.260]
Using local port 50115 [02/04 11:25:15.260]
TIMEOUT waiting for Ack block #0 [02/04 11:25:30.329]

Similar Messages

Plz tell me BDC CALL TRANSACTION steps with simple example

hi,
plz tell me the steps
BDC CALL TRANSACTION steps with simple example

Hi,
BATCH DATA COMMUNICATION
About Data Transfer In R/3 System
When a company decides to implement the SAP R/3 to manage business-critical data, it usually does not start from a no-data situation. Normally, a SAP R/3 project comes into replace or complement existing application.
In the process of replacing current applications and transferring application data, two situations might occur:
? The first is when application data to be replaced is transferred at once, and only once.
? The second situation is to transfer data periodically from external systems to SAP and vice versa.
? There is a period of time when information has to be transferred from existing application, to SAP R/3, and often this process will be repetitive.
The SAP system offers two primary methods for transferring data into SAP systems. From non-SAP systems or legacy system. These two methods are collectively called ?batch input? or ?batch data communication?.
1. SESSION METHOD
2. CALL TRANSACTION
3. DIRECT INPUT
Advantages offered by BATCH INPUT method:
1. Can process large data volumes in batch.
2. Can be planned and submitted in the background.
3. No manual interaction is required when data is transferred.
4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.
To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a ?data transfer? program must map the data from the external system into the data structure required by the SAP batch input program.
The batch input program must build all of the input to execute the SAP transaction.
Two main steps are required:
? To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
? To pass the table to SAP for processing.
Prerequisite for Data Transfer Program
Writing a Data Transfer Program involves following prerequisites:
Analyzing data from local file
Analyzing transaction
Analyzing transaction involves following steps:
? The transaction code, if you do not already know it.
? Which fields require input i.e., mandatory.
? Which fields can you allow to default to standard values.
? The names, types, and lengths of the fields that are used by a transaction.
? Screen number and Name of module pool program behind a particular transaction.
To analyze a transaction::
? Start the transaction by menu or by entering the transaction code in the command box.
(You can determine the transaction name by choosing System ? Status.)
? Step through the transaction, entering the data will be required for processing your batch input data.
? On each screen, note the program name and screen (dynpro) number.
(dynpro = dyn + pro. Dyn = screen, pro = number)
? Display these by choosing System ? Status. The relevant fields are Program (dynpro) and Dynpro number. If pop-up windows occur during execution, you can get the program name and screen number by pressing F1 on any field or button on the screen.
The technical info pop-up shows not only the field information but also the program and screen.
? For each field, check box, and radio button on each screen, press F1 (help) and then choose Technical Info.
Note the following information:
- The field name for batch input, which you?ll find in its own box.
- The length and data type of the field. You can display this information by double clicking on the Data Element field.
? Find out the identification code for each function (button or menu) that you must execute to process the batch-input data (or to go to new screen).
Place the cursor on the button or menu entry while holding down the left mouse button. Then press F1.
In the pop-up window that follows, choose Technical info and note the code that is shown in the Function field.
You can also run any function that is assigned to a function key by way of the function key number. To display the list of available function keys, click on the right mouse button. Note the key number that is assigned to the functions you want to run.
Once you have program name, screen number, field name (screen field name), you can start writing.
DATA TRANSFER program.
Declaring internal table
First Integral Table similar to structure like local file.
Declaring internal table like BDCDATA
The data from internal table is not transferred directly to database table, it has to go through transaction. You need to pass data to particular screen and to particular screen-field. Data is passed to transaction in particular format, hence there is a need for batch input structure.
The batch input structure stores the data that is to be entered into SAP system and the actions that are necessary to process the data. The batch input structure is used by all of the batch input methods. You can use the same structure for all types of batch input, regardless of whether you are creating a session in the batch input queue or using CALL TRANSACTION.
This structure is BDCDATA, which can contain the batch input data for only a single run of a transaction. The typical processing loop in a program is as follows:
? Create a BDCDATA structure
? Write the structure out to a session or process it with CALL TRANSACTION USING; and then
? Create a BDCDATA structure for the next transaction that is to be processed.
Within a BDCDATA structure, organize the data of screens in a transaction. Each screen that is processed in the course of a transaction must be identified with a BDCDATA record. This record uses the Program, Dynpro, and Dynbegin fields of the structure.
The screen identifier record is followed by a separate BDCDATA record for each value, to be entered into a field. These records use the FNAM and FVAL fields of the BDCDATA structure. Values to be entered in a field can be any of the following:
? Data that is entered into screen fields.
? Function codes that are entered into the command field. Such function codes execute functions in a transaction, such as Save or Enter.
The BDCDATA structure contains the following fields:
? PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
? DYNPRO: Screen Number. Set this field only in the first record for the screen.
? DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to ? ? (blank) for all other records.)
? FNAM: Field Name. The FNAM field is not case-sensitive.
? FVAL: Value for the field named in FNAM. The FVAL field is case-sensitive. Values assigned to this field are always padded on the right, if they are less than 132 characters. Values must be in character format.
Transferring data from local file to internal table
Data is uploaded to internal table by UPLOAD of WS_UPLOAD function.
Population of BDCDATA
For each record of internal table, you need to populate Internal table, which is similar to BDCDATA structure.
All these five initial steps are necessary for any type of BDC interface.
DATA TRANSFER program can call SESSION METHOD or CALL TRANSACTION. The initial steps for both the methods are same.
First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.
SESSION METHOD
About Session method
In this method you transfer data from internal table to database table through sessions.
In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.
Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.
When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.
Unless session is processed, the data is not transferred to database table.
BDC_OPEN_GROUP
You create the session through program by BDC_OPEN_GROUP function.
Parameters to this function are:
? User Name: User name
? Group: Name of the session
? Lock Date: The date on which you want to process the session.
? Keep: This parameter is passed as ?X? when you want to retain session after
processing it or ? ? to delete it after processing.
BDC_INSERT
This function creates the session & data is transferred to Session.
Parameters to this function are:
? Tcode: Transaction Name
? Dynprotab: BDC Data
BDC_CLOSE_GROUP
This function closes the BDC Group. No Parameters.
Some additional information for session processing
When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.
However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.
If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.
CALL TRANSACTION
About CALL TRANSACTION
A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program by
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>
Messages into <MSGTAB>.
Parameter ? 1 is transaction code.
Parameter ? 2 is name of BDCTAB table.
Parameter ? 3 here you are specifying mode in which you execute transaction
A is all screen mode. All the screen of transaction are displayed.
N is no screen mode. No screen is displayed when you execute the transaction.
E is error screen. Only those screens are displayed wherein you have error record.
Parameter ? 4 here you are specifying update type by which database table is updated.
S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.
A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).
Parameter ? 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:
1. Tcode: Transaction code
2. Dyname: Batch point module name
3. Dynumb: Batch input Dyn number
4. Msgtyp: Batch input message type (A/E/W/I/S)
5. Msgspra: Batch input Lang, id of message
6. Msgid: Message id
7. MsgvN: Message variables (N = 1 - 4)
For each entry, which is updated in database, table message is available in BDCMSGCOLL. As BDCMSGCOLL is structure, you need to declare a internal table which can contain multiple records (unlike structure).
Steps for CALL TRANSACTION method
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. UPLOAD or WS_UPLOAD function to upload the data from local file to itab. (Considering file is local file)
4. Loop at itab.
Populate BDCTAB table.
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>.
Refresh BDCTAB.
Endloop.
(To populate BDCTAB, You need to transfer each and every field)
The major differences between Session method and Call transaction are as follows:
SESSION METHOD CALL TRANSACTION
1. Data is not updated in database table unless Session is processed. Immediate updation in database table.
2. No sy-subrc is returned. Sy-subrc is returned.
3. Error log is created for error records. Errors need to be handled explicitly
4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.
Error Handling in CALL TRANSACTION
When Session Method updates the records in database table, error records are stored in the log file. In Call transaction there is no such log file available and error record is lost unless handled. Usually you need to give report of all the error records i.e., records which are not inserted or updated in the database table. This can be done by the following method:
Steps for the error handling in CALL TRANSACTION
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. Internal table BDCMSG like BDCMSGCOLL
4. Internal table similar to Ist internal table
(Third and fourth steps are for error handling)
5. UPLOAD or WS_UPLOAD function to upload the data from the local file to itab. (Considering file is local file)
6. Loop at itab.
Populate BDCTAB table.
Call transaction <tr.code> using <Bdctab>
Mode <A/N/E>
Update <S/A>
Messages <BDCMSG>.
Perform check.
Refresh BDCTAB.
Endloop.
7 Form check.
IF sy-subrc <> 0. (Call transaction returns the sy-subrc if updating is not successful).
Call function Format_message.
(This function is called to store the message given by system and to display it along with record)
Append itab2.
Display the record and message.
DIRECT INPUT
Thanks &regards,
Sravani

Error in Call Adapter step

Hello,
We have RFC --> HTTPS scenario.
The RFC Destination of type G is created in XI and the connection test is working fine.
When I run this scenario, sometimes I get following error:
com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapter:ATTRIBUTE_CLIENT:.
Error in sxmb_moni in Call Adapter Step:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
<SAP:P1>400</SAP:P1>
<SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP client code 400 reason ICM_HTTP_CONNECTION_FAILED</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
However sometimes it works fine.
Please help to resolve this.
Thanks in advance,
Hetal

Hello Hetal,
Can you please elaborate more on the scenario. if it is a RFC -> PI -> SOAP scenario please check if you are using the correct target URL in your Receiver Comm. Channel. Also check if the backend service could be unstable due to network load.
Thanks.
Kiran

Why do I get error -17500 when calling a batch file using the call executable step type?

I am calling a batch file using the call executable step type. If the path to the batch file contains a space I get error -17500 and a message stating there was an error in "Post". For example the path to the batch file is "c:\TestWin\Test Files\...\Program.bat" When I run this I get the above mentioned error, however if I change my directory structure so the path is now "c:\TestWin\TestFiles\...\Program.bat" it runs fine. I use the browse feature to find my batch file so it is not me typing in a path incorrectly. I have removed the batch file and I get a different error stating that it couldn't find the file so it appears that for my error it can find the file but can't run it. I am
sure that this has something to do with the fact that batch files are written in DOS but really don't want to resort to changing my directory structure on all my test stations. Is there any way to fix this problem so I can leave a space in my path?

It appears I have figured it out. This was on another computer so I was unaware of how they used their computer. I like you got it to work in the temp directory and in fact got the program.bat file to work as long as I put it under the temp directory, but when I switched out to my TestWin directory it wouldn't work, so I removed everything from the directory except the batch file it self and it work. What I found out after adding files in one at a time is that the person had a file called "Test" with no file extension in there "c:\TestWin\" directory. Removing this file made it work. Putting the file back broke it. So it appeares that when teststand was running it followed the path saw a space and attempted to grab the "Test" file instead of bro
wsing into the "Test Files" directory. If you create a file in your temp directory called "temp" with no file extension you will see the same problem. Thank you for your help.

Two "Call Adapter" step in SXMB_MONI

Hello Experts,
I have developed Sync interface WebService - PI - BAPI.
However when message is failing due to error in mapping at response side, there are 2 "Call Adapter" steps in sxmb_moni got that message.
First Call Adapter step is not in error status, however 2nd Call Adapter is in Error status (System Error- Restart not possible).
Could you please explain me why there are 2 "Call Adapter" steps? Actually there has to be only one step.
Best Regards,
Manisha

First Call Adapter step, there is no error
but in 2nd call adapter error is
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_Z_BAPI_VL10_DLVY_CREATE_resp_2_~</SAP:P1>
<SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
<SAP:P3>on: Cannot create target element /ns1:Order/OrderD</SAP:P3>
<SAP:P4>etail/ListOfItemDetail/ItemDetail. Values missing~</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_Z_BAPI_VL10_DLVY_CREATE_resp_2_; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns1:Order/OrderDetail/ListOfItemDetail/ItemDetail. Values missing</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
both call adapter steps are under "Central client" step. why 2 call adapter in one?

Call hold vs. media bypass in CUCM-Lync infrastructure

Dear Colleagues,
We have built a heterogeneous UC infrastructure based on Lync Server 2013 and CUCM 9.1.2.11900-12 and we experienced, that with media bypass, we cant hold the calls on Lync side. I checked the SIP logs on both sides and I saw, when Lync sends a re-invite, CUCM responds with 200 OK and in this there is a parameter "b=CT:64" and unfortunately the Lync could not handle it.
After some investigation I found this link: http://johnacook.wordpress.com/2014/03/27/the-case-of-the-curious-sdp-with-lync-call-manager-media-bypass-and-call-hold-and-resume/
In the post, the author mentioned a LUA script:
M = {} function M.outbound_ANY(msg) local sdp = msg:getSdp() if sdp then local b_CT_line = sdp:getLine(“b=CT”,”64″) if b_CT_line then b_CT_line = b_CT_line:gsub(“64″, “1000”) sdp = sdp:modifyLine(“b=CT”, “64”, b_CT_line) msg:setSdp(sdp) end end end function M.outbound_ANY_ANY(msg) local sdp = msg:getSdp() if sdp then local b_CT_line = sdp:getLine(“b=CT”,”64″) if b_CT_line then b_CT_line = b_CT_line:gsub(“64″, “1000”) sdp = sdp:modifyLine(“b=CT”, “64”, b_CT_line) msg:setSdp(sdp) end end end
return M
I have created a SIP normalization script and afterwards I have assigned it to the SIP trunk but unfortunately the problem still exists.
Do I have to do anything else? Did I miss something?
Thanks,
Laci

Hello Laci, did you fix this issue?
We have similar setup and while testing the media bypass, we faced the issue with call hold and hence decided to upgrade the lync client for all the users.
Wanted to check if you have any other solution for this call hold issue.

Calling second step of transaction of r3 through web dynpro

Hi all
We are calling a particular transaction and passing paramter to it through web dynpro.We have successfully implemented it.but we are facing problem in calling second step of transaction and passing parameter required at second step.
pls tell me if any one has any ideas how to do it ???
regards
zaid

Does the second step involve a new function module or does it make use of the same one? Regardless the second call shouldn't be any different than the subsequent calls. Maybe you could provide more details.
/Greg

Problem with Call Redirect step

Hi
I am trying to use Call Redirect step to forward the calls to receptionit's voice mail box after office hours.
My script is very simple.
Start
Accept
Call Redirect (destination: voice mail pilot number, Called address reset to receptionist extension)
End
Haven't included the date and time checking.
But it just doesn't go to receptionist's voice mail box.
The strange thing is, when I call the number (CIT route point for reception), it goes to helpdesk's voice mail box...
I have another script (not done by me) for helpdesk with IVR, where you can press 2 to leave voice mail. It works fine. And its using the same script.
But I didn't copy the script.
Where did I possibly make a mistake?
I have been struggling it for 3 days
Regards,
Raymond

Your configuration looks fine, and I'm sure you can see that it's nearly identical to the working script.
So there's something else at play here.
First thing I can see is, you sent a screenshot of a script off your PC, and not from the repository of the server. So, it is possible that the script loaded into memory is different than the script you are showing us. Do this: log into AppAdmin, and click on the application, note the script file name, then in your Editor go to File > Open, and select the script repository icon (purple icon) then open the default folder, then open the script from there. This will be the actual script in use.
Second, refresh your application. You could be working off the script in the repo, but forgetting to refresh the application.
Third, you said your script, which was created from scratch, goes to 650666, which just happens to be the mailbox from the help desk script. I think that's a little too convenient, and would like to see a screenshot of a route plan report for 4000 and for 650666.
Last, are you using the same CCG on your trigger as the working helpdesk script?
Anthony Holloway
Please use the star ratings to help drive great content to the top of searches.

Setting Enterprise Call Info Step Within An HTTP Triggered CRS Script

IPCC Enterprise 7.5(6)
CAD 7.5(6)
IPIVR 7.0(1)sr05_build504
We had a vendor develop some IVR & ICM scripts a few years back to take a website triggered request and pass along it’s value from the header, store it into Call Peripheral Variable 1 and place a call to a queue with agents (using CAD). It then sets off a work flow group macro to populate this value (from PV1) into another application along with a repeating message to the agent that says they have a new request. Since we recently upgraded our IVR to 7.0(1)sr05, I had to change the scripting some to make it work. They were using a freaky way of getting the value into PV1 using a pre-connect application triggered from the initial application. Anyway, their method would not work with the new version any longer so I needed to alter the scripts some.
The problem I’m having is that PV1 is being set after the Place Call step. This actually needs to be set before it reaches an agent in order to pass the value into CAD. Currently, I’ve been using some delay statements in the ICM script to give it time to get the value into PV1 but it’s not 100%. I get sporadic results.
Current script in test.
I’m looking to see if anyone can tell me a way to setup the Set Enterprise Call Info step before the Place Call step? Since this is HTTP triggered, I can’t use (Triggering Contact) and I haven’t been able to set a pseudo contact because debug tells me that the contact is null or because it’s not a call contact.

Hi Gabriel. Thanks for the reply.
The current method that's in place seems to work fine for me in test but when in production, I'm getting about a 60-70% success rate. As it comes into my ICM queuing script, I'm using another Run Ext Script node to execute a delay to give the Set Enterprise Call Info step from the first VRU script extra time to set it's value before reaching the ICM Queue To Skill Group node. I definitely notice better results when I did this but still not a 100%.
The reason I'm doing this is because of the notation that the help file discusses about the Set Enterprise Call Info step:
"Note In a Cisco Unified CCX system:
Beginning with CRS 4.0, this step should be placed script before the call gets connected to an agent. This means the step in the script should be placed before the Select Resource Step or in the Selected/Queued branch of the Select Resource step.
If call data is set after the call gets connected to the agent, it will not be displayed in Cisco Agent Desktop (CAD)."
So this is why I've been looking to see if this step can somehow be set before the Place Call step. I'm not that familiar with altering Sessions or Contacts but was hoping someone might know how to manipulate these in order to let me do this.
Thanks again.

When running labview's test executive I recieve runtime error: Call to step "PRE-RUN" failed. Could someone explain this error?

I have a set of vi's that work when run under labview. However, when calling these vi's from labview's test executive I recieve runtime error: Call to step "PRE-RUN" failed. in Assign Connector Pane.vi->Call Test.vi->Execute Pre-Run.vi->Test Executive. Could someone explain this error to me? (or ideally tell me how to fix it?) Thanks.

Hello,
There are any number of possible causes to this problem. Which version of Test Executive are you using? Have you upgraded your Test Executive recently? The latest version is 5.1.1. If you have changed anything about Test Executive on your computer recently, I recommend you perform a mass compile of all your VI libraries, as having different versions of the VIs on your system could often result in the "Call to Step XYZ Failed" errors. Also, are you using any DAQ or Analysis VIs in your steps? We have seen problems where the use of DAQ or Analysis VIs in the sequence can cause intermittent "Call to Step...Failed" errors. There are some KnowledgeBase entries on our website that discuss this problem. Are you using the Test Executive in the VI environment, or
as an executable? Again, there are some problems with using Test Executive as an executable that result in these errors, and there are also KnowledgeBase entries that discuss these problems.
If you have a pared-down application that demonstrates the problem, feel free to send me your VIs and your .seq file and I will try to reproduce the problem.
Alternatively, I would suggest you visit www.ni.com/teststand to learn about TestStand, our state-of-the-art Test Sequencing software that completely outperforms Test Executive. It is very easy to use and much more powerful, and we have a top-notch support team available dedicated exclusively to supporting TestStand. As you are probably aware, we are no longer developing Test Executive, and instead are concentrating our efforts on making TestStand the penultimate solution for all our customers' test sequencing needs.
I appreciate your patience on this issue. Please let me know if I can offer further assistance.
Have a pleasant weeken
d.
Sincerely,
Darren Nattinger
Applications Engineer
National Instruments
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

1.call information such as call waiting,call forwarding, call holding is not working when caller the call me or im wait for my call i cant see any title by iphon , and also holding is the same.2. there is not any option for call baring.

Hi. please solve my problem.
.call information such as call waiting,call forwarding, call holding is not working when caller the call me or im wait for my call i cant see any title by iphon , and also holding is the same.2. there is not any option for call baring.3.playback music is not hearing by second partner during the call.4.i cant select ringing ton from saving tons.
thank you in advance.

Hi Ersin,
Exception 1 would seem to be FORMATTING_ERROR, which suggests something in the design of the Smartform. However, that doesn't fit with the form being generated from a report, but only erroring when called from a function module. I can think of no reason why the different calling method would be a factor.
When FORMATTING_ERROR is raise it should also set a message ID and number, are you able to determine what they are?
Regards,
Nick

How to use "Set Enterprise Call Info" step in the script ?

Hi all
Can anyone please suggest how to use "Set Enterprise Call Info" step in the script.
Does anyone has any example script with the same (a complete example script) ?

Hi
go to this guide
http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/crs/express_7_0/user/guide/uccx70edgs.pdf
and see the chapter
"Designing Scripts for use with the Cisco Application Gateway"

Cannot pick up calls on wait, Cannot make a second call holding the first call

I have a really weird problem with my iPhone 5S. (iOS 7.1)
1. When I am on a call, I am not able to pick up a second call that is on wait. I can see the second call, I can hear the beep sounds but as soon as I pick up, the call freezes in 00.00 time, and My first caller is still active, not on hold.
2. When I am on a call, I am not able to make a second call placing the first call on hold. The second call disconnects immediately with 3 beeps.
3. I am able to see the incoming calls on wait, when I am already on a call. I am able to hear the beeps coming in. SO it means the call waiting is on (Tried turning it on/off/on too.) But when I pick up the call, the above problem comes in.
What have I tried to solve this: (None of them helped)
1. I tried a hard reset of my iPhone (Holding Power and Home button)
2. I tried toggling the Call waiting button
3. I tried resetting network settings.
4. I called my Operator for assistance. I am using Airtel, India. They told me to dial this code - *43# . I tried it and it gave me this screen. But the problem is not solved yet.
Is there anybody here who is facing the same issue with your iPhone? I never had this problem with my iPhone 4.

Make sure you do not have "Do Not Disturb" turned on. This feature will block the first call, but is someone calls right back it will be put through.
On the iPhone, go to Settings/Do Not Disturb
Make sure you do not have Do Not Disturb turned on manual or scheduled.

Why is timing different when subvi is called vs. stepped into?

I have a subvi that is called from within a larger vi. This subvi uses a sequence of wait(ms) vis and custom white-noise generator vis to create a sequence of sounds outputted to headphones. The timing of the sequence is very reliable when the subvi is either run directly or if I step-into it from the calling vi. However, when labview calls the subvi as part of the larger routine, the sequence is off.
It's confusing because I'd expect the same behavior regardless of step-into or running it from the calling vi. Any help will be much apprecitated.

What do you mean by step into? Is that during the debug phase?
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies

How to run from the caller's step in teststand

Hi,
When an error occurs in a step during a sequence, I can use the SequenceFilePostStepRuntimeError call back to catch the error. But how can I go back to the step which is the one just raised the error for a retry run again? I do not want to make all test fail straightway, but want to go back to the caller step to have retry a few times 1st.
Many thanks,
WeiL
Solved!
Go to Solution.

There is an example which shows how to do exactly what you are asking located at:
<TestStand Public>\Examples\Callbacks\PostStepRuntimeErrorCallback\ErrorHandlerExample.seq
Hope this helps,
-Doug

CUE 8.6.4 Call Hold Step

Similar Messages

Maybe you are looking for