Cisco outbound Dialer MRPG test calls command

Hi Dear,
Can you please tell me someone about this command.
What is the cisco sccp dialer test call command on the cmd.
It should be  smilar command on the cmd 
c:\ test x 01545051
I could not remember correctly.
Thanks and Regards

The utility is dialogictest
This is for SCCP only though so wouldn't work in a recent install. Details are in the Cisco Outbound Option guide:
From the \icm\bin directory on the Dialer, type the following to run the DialogicTest utility, type Dialogictest softphone <number of ports in the Dialer port map> <CallManager name or IP address> <dialer ID> <starting channelID> <custname>
where:
The CallManager name or IP address indicates the Unified CM TFTP server machine.
The dialer ID is the numeric identifier obtained above from the Dialer table.
The starting channel ID indicates the first port ID in the Dialer (usually 0). This creates simulated Dialer ports based on the port map configuration.
The custname is the ICM customer name.
Choose a phone station on the ACD that has a "caller ID" display and note its phone number. This phone station is called to validate connectivity between the Dialer and the station. Using DialogicTest, dial this station using the following syntax: >d 0 <station #> 30
where d is the abbreviation for "Dial," 0 is the first channel in the port map, station # is the actual number to reach the phone station, and 30 represents the amount of time DialogicTest attempts to ring the phone station. For example, to dial station 51001, the command is >d 0 51001 30.

Similar Messages

  • Cisco Outbound Dialer issue

    Dear All,
    Request your advise on below,
    We have ucce 8.5.4 deplyed in cvp comprehensive model.
    we are facing issue with dialer, out bound option is not working.
    i could see below error from dialer and pim logs.
    08:09:52:607 dialer-baDialer Trace: (DD)          **** Media Routing PIM is not Connected ****
    08:09:52:607 dialer-baDialer Trace: (DD)          **** CTI Server indicated that peripheral is off-line, or peripheral online message not received yet****
    08:09:52:607 dialer-baDialer Trace: (DD)          **** Media Routing PIM is not Connected ****
    08:09:52:607 dialer-baDialer Trace: (DD)          **** CTI Server indicated that peripheral is off-line, or peripheral online message not received yet****
    08:09:53:608 dialer-baDialer Trace: (DD)          **** Media Routing PIM is not Connected ****
    08:09:53:608 dialer-baDialer Trace: (DD)          **** CTI Server indicated that peripheral is off-line, or peripheral online message not received yet****
    08:09:53:608 dialer-baDialer Trace: (DD)          **** Media Routing PIM is not Connected ****
    08:09:53:608 dialer-baDialer Trace: (DD)          **** CTI Server indicated that peripheral is off-line, or peripheral online message not received yet****
    08:09:54:607 dialer-baDialer Trace: (DD)          **** Media Routing PIM is not Connected ****
    08:09:54:607 dialer-baDialer Trace: (DD)          **** CTI Server indicated that peripheral is off-line, or peripheral online message not received yet****
    08:09:54:607 dialer-baDialer Trace: (DD)          **** Media Routing PIM is not Connected ****
    08:09:54:607 dialer-baDialer Trace: (DD)          **** CTI Server indicated that peripheral is off-line, or peripheral online message not received yet****
    08:09:55:607 dialer-baDialer Trace: (DD)          **** Media Routing PIM is not Connected ****
    08:09:55:607 dialer-baDialer Trace: (DD)          **** CTI Server indicated that peripheral is off-line, or peripheral online message not received yet****
    08:09:55:607 dialer-baDialer Trace: (FAILOVER)          SENT:HeartBeatRequest to CTI Server; InvokeId[1]
    08:09:55:607 dialer-baDialer Trace: (DD)          **** Media Routing PIM is not Connected ****
    08:09:55:607 dialer-baDialer Trace: (DD)          **** CTI Server indicated that peripheral is off-line, or peripheral online message not received yet****
    08:09:55:615 dialer-baDialer Trace: CallListener creating mutex - Global\CCallListener9744
    08:09:55:615 dialer-baDialer Trace: (FAILOVER)          Received:HeartBeatConf from CTI Server; InvokeId[1]
    08:09:55:735 dialer-baDialer Trace: CSipUATelephonyServer::HandleKeepAliveTimer
    08:09:55:765 dialer-baDialer Trace: SipISH-onSuccess:
    SipResp: 200 cid=56159138-9f5c4318-1d6e1f1d-245bf074 tid=181f8a389042be27 cseq=OPTIONS / 1 from(wire)
    could you any one please shed some light on it.
    Regards,
    Shalid K.C

    Dear Senthil,
    1. imported the file and could see the ba  table is update with the list.
    4:52:57:531 la-baImport Trace: Updating 500000 NULL GMT records for phone 10.  0 remaining. SQL: update DL_5000_5000 set GMTPhone10 = 180, DSTPhone10 = 'N' from ( select top 500000 DialingListID, GMTPhone10, Phone10 from DL_5000_5000 where GMTPhone10 is null) as t1 where DL_5000_5000.DialingListID = t1.DialingListID
    14:52:57:531 la-baImport Trace: Build done for Campaign: Sales, Query Rule: Sales, 1 Records Inserted into DL_5000_5000  table  [Begin: 0 End: 1]
    14:52:57:532 la-baImport Trace: Updating sm_used column in table [Sales] to value: 1
    14:52:57:533 la-baImport Trace: 1 records left to be updated
    14:52:57:645 la-baImport Trace: Update for sm_used column in table [Sales] to value: 1 has been completed
    14:52:57:645 la-baImport Trace: Imported [1] good records into table [Sales] out of [1] total records. [0] records were bad.
    14:52:57:645 la-baImport Trace: Closing the Database
    14:52:57:679 la-baImport Trace: Renamed import file: [\\10.200.128.100\c$\ba\ba.txt] to [\\10.200.128.100\c$\ba\ba.txt.bak] for import rule id [5000]
    14:52:57:679 la-baImport Trace: CImport::ImportFile - Released ImportMutex
    2., from the campaign manager logswe  could see that  the records has been successfuly send to router.
    4:52:57:531 la-baImport Trace: Updating 500000 NULL GMT records for phone 10.  0 remaining. SQL: update DL_5000_5000 set GMTPhone10 = 180, DSTPhone10 = 'N' from ( select top 500000 DialingListID, GMTPhone10, Phone10 from DL_5000_5000 where GMTPhone10 is null) as t1 where DL_5000_5000.DialingListID = t1.DialingListID
    14:52:57:531 la-baImport Trace: Build done for Campaign: Sales, Query Rule: Sales, 1 Records Inserted into DL_5000_5000  table  [Begin: 0 End: 1]
    14:52:57:532 la-baImport Trace: Updating sm_used column in table [Sales] to value: 1
    14:52:57:533 la-baImport Trace: 1 records left to be updated
    14:52:57:645 la-baImport Trace: Update for sm_used column in table [Sales] to value: 1 has been completed
    14:52:57:645 la-baImport Trace: Imported [1] good records into table [Sales] out of [1] total records. [0] records were bad.
    14:52:57:645 la-baImport Trace: Closing the Database
    14:52:57:679 la-baImport Trace: Renamed import file: [\\10.200.128.100\c$\ba\ba.txt] to [\\10.200.128.100\c$\ba\ba.txt.bak] for import rule id [5000]
    14:52:57:679 la-baImport Trace: CImport::ImportFile - Released ImportMutex
    3. but the dialer is not working. and further from the dialer logs we found the above mentioned peripheral offline message.
    4. couldnt find any thing in the mr pim logs.
    how can we troubleshoot it further..
    regards,
    Shalid K.C

  • ICM 7.5-how to get individual outbound dialer calls talktime and respective ECC values

    Hello,
    I'm looking for following two items
    1. Outbound dialer calls talktime in each call.
    2. Each calls respective ECC values.
    I have tried to get talktime from TCD table it’s shows zero value.
    Please advice how to get above values, it would be much appreciated.
    Thanks
    Regards,
    Param

    Hey Param,
    You can use the PeripheralCallType in the TCD table to find dialer calls. Look for calls with:
    PeripheralCallType IN ('27','28','29','30','31') for reservation calls and
    PeripheralCallType IN ('32','33','34','35') for the customer calls
    For duration of reservation calls look at the HoldTime value
    For duration of the customer call you can look at the HoldTime + TalkTime + WorkTime for a total handle time for the customer leg of the dialer call
    If you want to look at the ECC variables that were associated with that call you will have to lookup the Termination_Call_Variable table matching:
    Termination_Call_Variable.TCDRecoveryKey = Termination_Call_Detail.RecoveryKey
    Cheers,
    Nathan

  • ICM MR PG and Outbound Dialer

    Hi,
    I am trying to install Outbound option for IPCC Enterprise 7.5.1 and I am having some problems with it. My setup is as follows
    Server 1 : RouterA, LoggerA, PG1A(CCM PG), CG1A, CTIOS1, DialerA, PG2A(MR PG with two PIMs for the two dialers);
    Server 2 : RouterB, LoggerB, PG1B(CCM PG), CG1B, CTIOS1, DIalerB, PG2B(MR PG with two PIMs for the two dialers);
    Server 3 : AW/HDS, WebView
    CCM -6.1.2
    This is my first try with IPCCE and I did my best to install everything following the installation guides but I have the following problems:
    - on the dialer window I am seeing:
    [client.Dialer.BADialer][CM-A][CTI-U][Ports-X][MR-X]
    Trace: Registering with Campain Manager
    Trace: Registering with Campain Manager
    Trace: Registering with Campain Manager
    - the MR PG is probably Down. I am seeing the following messages in the trace window:
    Attempting to connect to MR application at IP address 10.40.40.11 port 38001.
    Attempting to connect to MR application at IP address 10.40.40.11 port 38001.
    Attempting to connect to MR application at IP address 10.40.40.12 port 38001.
    Attempting to connect to MR application at IP address 10.40.40.12 port 38001.
    where 10.40.40.11(12) are sideA, sideB visible IP addresses(Dialers addresses and ports);
    ,in "opc" proccess I am seeing:
    11:12:42 Peripheral 5001 failed 2 startup request. Delaying startup for 60 seconds.
    11:13:43 Trace: ProcessPIMReportingConfigInd: Unknown ConfigType -1 specified from Peripheral 5001 on Side SideA.
    11:13:43 Trace: ProcessPIMReportingConfigInd: Unknown ConfigType -1 specified from Peripheral 5001 on Side SideB.
    11:14:14 Trace: ProcessPIMReportingConfigInd: Unknown ConfigType -1 specified from Peripheral 5001 on Side SideB.
    11:14:16 Trace: ProcessPIMReportingConfigInd: Unknown ConfigType -1 specified from Peripheral 5001 on Side SideA.
    - the Dialer ports are not getting registered in CCM. I added these dialer ports in Call Manager as Standard 30 VIP phones. I added these phones to PGUser as well. CCM PG is operational
    Any help would be appreciated.
    Thanks,
    Cristian

    Hi Geoff,
    This was a very good observation.
    Thank you very much!
    Now I have on dialer window:
    [CM-A][CTI-A][Ports: C5,R5,B0][MR-X].
    The Cisco 30 VIP are now registered to CCM but I have the following error messages in Dialer proccess:
    19:57:30 Trace: (FAILOVER) SENT:HeartBeatRequest to CTI Server; InvokeId[119]
    19:57:30 Trace: (DD) **** Media Routing PIM is not Connected ****
    19:57:30 Trace: (FAILOVER) Received:HeartBeatConf from CTI Server; InvokeId[119]
    19:57:31 Trace: (DD) **** Media Routing PIM is not Connected ****
    19:57:31 Trace: (DD) **** Media Routing PIM is not Connected ****
    19:57:32 Trace: (DD) **** Media Routing PIM is not Connected ****
    19:57:32 Trace: (DD) **** Media Routing PIM is not Connected ****
    19:57:33 Trace: (DD) **** Media Routing PIM is not Connected ****
    19:57:33 Trace: (DD) **** Media Routing PIM is not Connected ****
    In the "MR_PIM - pim1" and "MR_PIM -pim2" proccesses I have the following messages:
    19:55:45 Peripheral 5001 sending OPC PIM_OK_ACK acknowledgment for command PIM_CONFIGURE_REQ (TransID=0).
    19:55:45 Attempting to connect to MR application at IP address 10.40.40.11 port 38001.
    19:55:46 Attempting to connect to MR application at IP address 10.40.40.11 port 38001.
    19:55:57 Attempting to connect to MR application at IP address 10.40.40.11 port 38001.
    19:55:58 Attempting to connect to MR application at IP address 10.40.40.11 port 38001.
    19:56:09 Attempting to connect to MR application at IP address 10.40.40.11 port 38001.
    19:56:10 Attempting to connect to MR application at IP address 10.40.40.11 port 38001.
    19:56:16 ProcessPIMSetIdleReq: Peripheral 5001 going idle.
    19:56:21 Peripheral 5001 sending OPC PIM_OK_ACK acknowledgment for command PIM_SET_IDLE_REQ (TransID=-1).
    What do you think about this?
    Thanks once again,
    Cristian

  • UCCX 7 outbound dialing, problem with area codes

    Hello all,
    I'm just testing the outbound dialing feature in a lab, and have run into the following problem:
    I have following:
    outbound configuration:
    general:
    Customer dialing time: start (9:00) end (21:00)
    dialing prefix - 9
    international prefix - 00
    Local Area Code: 44
    Area Codes:
    44 -> Europe/London
    34 -> Europe/Madrid
    86 -> GMT-10 (for testing purposes, does not correspond to real China time).
    Then, I upload a .CSV file into a campaign with the following information:
    Jane,Smith,00447111113007
    Jacky,Chan,0086611115002
    Juan,Pablo,0034611114001
    The dialing works, the agent receives the call, accepts it, and then the call is made.
    if anyone is interested, although it has nothing to do with the question itself, the calls are translated to other extension on CUCM to be able to make a call.
    The problem is that, they are all treated as in the same AREA CODE, although I have clearly defined area codes for each of those countries.
    when the call appears it shows on the CAD as BAAreaCode: +00060
    Therefore the calls are made through to China even when it's midnight there!!!???
    I know I must be doing something wrong, but I don't know what?
    Many thanks for your help,
    Cheers,

    Hi Aaron,
    Sorry for being so late to answer you. But I've done quite a few tests last weekend and have couple traces as well.
    Apparently, the first time I added area codes, I did something incorrect, although I do not know what exactly, because now I've added area codes and it partially worked.
    Area code: 4420 - Europe/London with Daylight saving
    Area code: 3498 - Europe/Madrid with Daylight saving
    Area code: 8661 - GMT/+7 NO Daylight saving
    The first two Area codes (Spain and London) were correctly identified, In traces I could even see:
    this one is for Spain:
    type=com.cisco.executor.QueuedExecutor,Thread=MIVR_CFG_MGR_INVOKE_NOTIFICATION-33-189,Thread priority=7,Original Thread=null,Original thread priority=5,Time=null,Exception=null 358035:
    Jul 03 10:56:40.390 BST %MIVR-CFG_MGR-7-UNK:configStubImpl-replace() notified with DialingListConfig,time=2010-07-03 10:56:40.373,recordId=0,impl=class com.cisco.crs.outbound.DialingListConfig,desc=,key[137],columns[137,1,,Jacky,Chan,0086611115002,,,377,0,424,1,424,1,,1278150825843,6,0,0,0,0,0,0,0,0] 358036:
    Jul 03 10:56:40.390 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getPhoneNumber: callStatus=2callResult=0lastNumDialed=0 358037:
    Jul 03 10:56:40.390 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getUnformattedPhoneNumber: dlcID:138 358038:
    Jul 03 10:56:40.390 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getFormattedPhoneNumber: phoneNum=0034981114001 0034981114001 358039:
    Jul 03 10:56:40.390 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getFormattedPhoneNumber: intPrefix=00 localAreaCode=004420 lenAreaCode=6 include lac=true 358040:
    Jul 03 10:56:40.390 BST %MIVR-SS_OB-7-UNK:numToDial=0034981114001 0034981114001 358041:
    Jul 03 10:56:40.390 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getUnformattedPhoneNumber: dlcID:138 358042:
    Jul 03 10:56:40.390 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: timezone=sun.util.calendar.ZoneInfo[id="Europe/Madrid",offset=3600000,dstSavings=3600000,useDaylight=true,transitions=165,lastRule=java.util.SimpleTimeZone[id=Europe/Madrid,offset=3600000,dstSavings=3600000,useDaylight=true,startYear=0,startMode=2,startMonth=2,startDay=-1,startDayOfWeek=1,startTime=3600000,startTimeMode=2,endMode=2,endMonth=9,endDay=-1,endDayOfWeek=1,endTime=3600000,endTimeMode=2]] 358043:
    Jul 03 10:56:40.390 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: DST observed=true 358044:
    Jul 03 10:56:40.390 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: localTimeMins=716 globalStartTime=480 globalEndTime=1410 358045:
    Jul 03 10:56:40.390 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: isValidTime=true 358046:
    Jul 03 10:56:40.390 BST %MIVR-SS_OB-7-UNK:CampaignMgr.getContactsFromMemory: no more in-memory contacts left for campaignID 1 358047:
    As we can see, localTimeMins is 716 which is: 11:56AM.  That was correct time, and in between min/max globalstart times.
    And this one is for London:
    getPhoneNumber: callStatus=2callResult=0lastNumDialed=0 276065:
    Jul 03 10:27:41.687 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getUnformattedPhoneNumber: dlcID:130 276066:
    Jul 03 10:27:41.687 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getFormattedPhoneNumber: phoneNum=00442081114002 276067:
    Jul 03 10:27:41.687 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getFormattedPhoneNumber: intPrefix=00 localAreaCode=004420 lenAreaCode=6 include lac=true 276068:
    Jul 03 10:27:41.687 BST %MIVR-SS_OB-7-UNK:numToDial=00442081114002 276069:
    Jul 03 10:27:41.687 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getUnformattedPhoneNumber: dlcID:130 276070:
    Jul 03 10:27:41.687 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: timezone=sun.util.calendar.ZoneInfo[id="Europe/London",offset=0,dstSavings=3600000,useDaylight=true,transitions=242,lastRule=java.util.SimpleTimeZone[id=Europe/London,offset=0,dstSavings=3600000,useDaylight=true,startYear=0,startMode=2,startMonth=2,startDay=-1,startDayOfWeek=1,startTime=3600000,startTimeMode=2,endMode=2,endMonth=9,endDay=-1,endDayOfWeek=1,endTime=3600000,endTimeMode=2]] 276071:
    Jul 03 10:27:41.687 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: DST observed=true 276072:
    Jul 03 10:27:41.687 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: localTimeMins=627 globalStartTime=480 globalEndTime=1410 276073:
    Jul 03 10:27:41.687 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: isValidTime=true 276074:
    As we see, localTimeMins is 627 which is: 10:27AM which is correctly between min/max globalstart times too.
    But the problem started with GMT+7.
    Jul 03 10:28:41.859 BST %MIVR-SS_OB-7-UNK:CampaignMgr.getContactsFromMemory: for campaignID=1 280255:
    Jul 03 10:28:41.859 BST %MIVR-SS_OB-7-UNK:CampaignMgr.getContactsFromMemory: campaignID=1;#of DLC=2 280256:
    Jul 03 10:28:41.859 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getPhoneNumber: callStatus=2callResult=0lastNumDialed=0 280257:
    Jul 03 10:28:41.859 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getUnformattedPhoneNumber: dlcID:131 280258:
    Jul 03 10:28:41.859 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getFormattedPhoneNumber: phoneNum=0086611115002 280259:
    Jul 03 10:28:41.859 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getFormattedPhoneNumber: intPrefix=00 localAreaCode=004420 lenAreaCode=6 include lac=true 280260:
    Jul 03 10:28:41.859 BST %MIVR-SS_OB-7-UNK:numToDial=0086611115002 280261:
    Jul 03 10:28:41.859 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getUnformattedPhoneNumber: dlcID:131 280262:
    Jul 03 10:28:41.859 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: timezone=sun.util.calendar.ZoneInfo[id="Etc/GMT+7",offset=-25200000,dstSavings=0,useDaylight=false,transitions=0,lastRule=null] 280263:
    Jul 03 10:28:41.859 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: DST observed=false 280264:
    Jul 03 10:28:41.859 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: localTimeMins=148 globalStartTime=480 globalEndTime=1410 280265:
    Jul 03 10:28:41.859 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: isValidTime=false 280266:
    Jul 03 10:28:41.859 BST %MIVR-SS_OB-7-UNK:CampaignMgr.getContactsFromMemory: cannot dial at this time, will be marked RETRY
    It correctly identifies Etc/GMT+7 but then it calculates the localtime wrongly... It came up with 148 which is 2:28AM... and the time I was making a call GMT+0 time was around 9:28AM so GMT+7 should've been 4:28PM...
    Then I tried GMT-7 too:
    Jul 03 11:25:40.843 BST %MIVR-SS_OB-7-UNK:CampaignMgr.getContactsFromMemory: for campaignID=1 433346:
    Jul 03 11:25:40.843 BST %MIVR-SS_OB-7-UNK:CampaignMgr.getContactsFromMemory: campaignID=1;#of DLC=2 433347:
    Jul 03 11:25:40.843 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getPhoneNumber: callStatus=2callResult=0lastNumDialed=0 433348:
    Jul 03 11:25:40.843 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getUnformattedPhoneNumber: dlcID:140 433349:
    Jul 03 11:25:40.843 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getFormattedPhoneNumber: phoneNum=0086611115002 433350:
    Jul 03 11:25:40.843 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getFormattedPhoneNumber: intPrefix=00 localAreaCode=004420 lenAreaCode=6 include lac=true 433351:
    Jul 03 11:25:40.843 BST %MIVR-SS_OB-7-UNK:numToDial=0086611115002 433352:
    Jul 03 11:25:40.843 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getUnformattedPhoneNumber: dlcID:140 433353:
    Jul 03 11:25:40.843 BST %MIVR-SS_OB-7-UNK:OutboundContactInfo:isRequestingContacts() for CSQ 2 returns true 433354:
    Jul 03 11:25:40.843 BST %MIVR-SS_OB-7-UNK:OutboundContactInfo:setNrGetContactsReqSent() for CSQ 2 to 1 433355:
    Jul 03 11:25:40.859 BST %MIVR-SS_OB-7-UNK:OutboundContactsRequestor before sleep 433356:
    Jul 03 11:25:40.859 BST %MIVR-SS_OB-7-UNK:Dialer:printLicenses() working_resources for CSQ:2 is 0 433357:
    Jul 03 11:25:40.859 BST %MIVR-SS_OB-7-UNK:Dialer:printLicenses() total_working_resources:0, OB_contacts_in_progress:0 433358:
    Jul 03 11:25:40.859 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: timezone=sun.util.calendar.ZoneInfo[id="Etc/GMT-7",offset=25200000,dstSavings=0,useDaylight=false,transitions=0,lastRule=null] 433359:
    Jul 03 11:25:40.859 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: DST observed=false 433360:
    Jul 03 11:25:40.859 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: localTimeMins=1045 globalStartTime=480 globalEndTime=1410 433361:
    Jul 03 11:25:40.859 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: isValidTime=true 433362:
    Jul 03 11:25:40.859 BST %MIVR-SS_OB-7-UNK:CampaignMgr.getContactsFromMemory: remaining # of in-memory contacts for campaignID 1:1 433363:
    and this time it did all the way around, instead of early morning, it was 1045: 5:25PM...
    I do not understand what am I doing bad... but I'm starting to think it's some kind of a bug...
    and the other problem is: outbound dialer does not even take contacts out of the campaign for calling if the server's local time is not between global start time and global end time. which should not be the case, as I understand campaign times should be applied to area code local time not to server local time.
    Many thanks to all,
    Cheers,
    George

  • CCME test call FXO without line

    hi All,
    We have an ISR2911 CCME10 with 2x FXO port.
    We are currently staging it, however we do not have FXO lines to test in house if our dial-peer plans is actually routed correct to our voice port 0/0/0 and voice port 0/0/1.
    Is there a way,cmd i can test call from my ip phone and see if the call is routed out to the intended voice FXO port
    please advise

    Hi.
    You have different ways to test it.
    debugging ccapi inout it will show you the matched outgoing dialpeer .
    With debug vpm signal the output should show the port status progress.
    Without a phone, from telnet or console session (not ssh) you can use the hidden command csim start followed by the number to dial.
    HTH
    Regards
    Carlo
    Sent from Cisco Technical Support iPhone App

  • Outbound Dialer 7.0 problems

    Hi,
    We are trying to install Outbound option for IPCC Enterprise 7.0 and we are having some problems with it. Our setup is as follows
    Server 1 : Rogger 7.0 with SR4
    Server 2 : CCM PG, VRU PG, CTI Server, CTI OS with SR4
    Server 3 : AW/HDS SR4
    Server 4 - Dialer, MR PG Sr4
    CCM -5.0
    We have installed everything as specified in the installation document, but when we start the Dialer, we see the followig in the command window
    [lab1.Dialer.BADialer][CM-A][CTI-A][Ports C:4,R:0,B:0][MR-A]
    As you can see, the Dialer ports are not getting registered. We added these dialer ports in Call Manager as Standard 30 VIP phones and they also show up as registered in the Call Manager. We added these phones to PGUser as well.
    Yet we don't see these ports registered in the dialer window and so we are not able to get the Outbound working. Any clues as to what we are doing wrong here?
    We are getting the following error in the Dialer as well as the CTI Server
    Trace: (CLMGR) CTI Query Device Information Request, invoke: 4423, port: 003, instrument: [1004]
    Trace: (CPORT) SetState, port: 003, state: PORT_WAIT_FOR_QUERY_DEVICE
    Trace: (CLMGR_IP) Control failure event, port: 003, id: 1000004423, failure code: 13 [CF_INVALID_CSTA_CONNECTION_IDENTIFIER], peripheral error code: 10137 [C_??CAUSE??]
    1004 is one of the Dialer ports and when the Dialer communicated with the CTI for this port, the above mentioned error occurs.
    Any help would be appreciated.
    Thanks
    Gokul

    Hi All,
    We finally figured out the problem. There were a couple of issues basically.
    1) When we added the dialer ports in config manager->dialer, I believe the device targets for these ports need to be added manually. This did not happen.
    2) So we went ahead and added the device targets manually. Still it did not work. We were suggested by TAC to add the following line in the configuration parameters in the Device target for each of these ports
    Configuration Parameters: /devtype monitorphone /dn 1004 /monitor Periph# i.e in our case one of the dialer ports was 1004 and our CCM PG id was 5000. So our config parameters looked like this
    /devtype monitorphone /dn 1004 /monitor 5000.
    Once we did this, the ports got registered and it worked like a charam :)
    Gokul

  • CDR by Outbound Dialed Number

    Hello,
    Is it possible to run a report on an outbound dialed number? I have been tasked to find how many times a number has been called. I normally did this with query analyzer with an if statement in older versions of CM but this is on UCM 8.
    Any help is greatly appreciated. 
    Thank you to all in advance.

    What version are you on?
    Mine shows "By User/Phone Number/SIP URL" for the first option.
    You can try using the "By User Extension" option but it may not work.
    You can use the CDR->Export CDR function to just export that date range to an Excel sheet and do your filtering there.
    The SQL queries would be another option as well.
    Brian

  • Trying to change Inbound IDOC to Outbound IDOC for testing....

    Hi Friends,
    I am trying to do the following
    1) In our legacy system SAP R/3 3.1H we have received an IDOC from our partner. This has been stored correctly.
    2) We now need the same functionality in our SAP R/3 4.6C system so I have created the IDOC type + segments accordingly. I have also set up the partner profiles
    3) We need test data but our partner can not send yet so the only other way is to send this INBOUND IDOC from 3.1H to 4.6C.
    4) HOWEVER, i have tried everything to do this like using WE19 to edit the idoc, but I can not process it for OUTBOUND processing.... You can in 4.6C but there is no option in 3.1H.
    HELP!! Rewards

    Hi Friend,
            The test programs allow you to skip certain sections of the processing chain between applications to localize errors. However, they can also be used to simulate an entire business process (for example, purchase order on the customer side with posting of the purchase order on the vendor side) in an SAP System (without any other systems). For this reason, the test programs are an important tool for configuring the IDoc Interface and defining new IDoc types.
    Use
    You can use the test tool to generate an IDoc manually and send the IDoc for either inbound or outbound processing. You are not restricted to a specific port type. You can start with an IDoc type (an “empty” IDoc) or use an old IDoc as a template and edit the IDoc, that is, add segments or change data. This is a good way to test new IDoc types, in particular.
    You can forward your new IDoc for standard inbound processing (checking partner profiles and so on). You can also call a function module directly. You can therefore test new function modules for new IDoc types.
    Activities
    ·        Start the test tool with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Test Tool (WE19). You can use a template for your test IDoc.
    You can choose IDoc types as a template, either directly or according to a specific message type. You can use the F4 Help for IDocs used as a template, which searches for IDocs by selection criteria, in the same way, for example, to IDoc Display. When an IDoc file is used as a template, the IDocs are read from this file and are available to you for selection. A default value for the IDoc file gives you the system using your test port which you can enter in IDoc Administration . This test port must therefore be of the “file“ type. The default file is the inbound file entered there.
    ·        You generate the IDoc using .
    The IDoc is displayed as a tree structure. If you do not use a template to create the IDoc type, at least one more segment must be added.
    ·        To create segments in the form of tree nodes (colored fields) place the cursor on an existing node (for example a control record at the top) and choose .
    You can cut, paste or copy individual segments or entire segment groups by positioning the cursor on the relevant segment and selecting the required action from the Edit menu.
    ·        Click on the white fields to change data in the segments.
    In the case of the control record, only the fields which are relevant for standard inbound processing are displayed. Do not forget the required entries in the partner profiles if you want to send the IDoc for standard inbound processing! You can also change all of the control record data by choosing All fields in the edit screen.
    In the All fields editor screen you must enter the non-language specific partner function (for example AG for vendor). This is the only screen in the IDoc Interface in which the partner function is not translated into your language (in English AG becomes vendor VD) - in the partner profiles or in the IDoc display the field is always translated. Thus, you see the partner functions here in the way they are saved in the database. This is a unique value in the SAP System and therefore protected against mistakes.
    ·        The additional procedure depends on whether you want to test inbound or outbound processing.
    Test: Outbound Processing from MC
    Use
    Use this test program if you have chosen the Message Control module and want to test generation of an outbound IDoc from an existing message status record (table NAST).
    Prerequisites
    You must be able to post the application documents which are to be converted into IDocs by the Message Control module correctly so that a message status record can be generated. In the case of the Materials Management (MM) and Sales and Distribution (SD) components, the following entries are required:
    ·        Customer or vendor records
    ·        Material records
    ·        Info records
    ·        MC condition record: The output medium 6 (for EDI) must be entered here. The condition records are maintained as “messages” from the respective application.
    The appropriate file ports and partner profiles must exist in the IDoc Interface.
    Outbound processing must be stopped when the message status record has been generated to allow the test program to intervene. To do so, you must set the Message Control dispatch time to “1” (output with selection run) in the corresponding condition record in the application. This test program, therefore, is simply used to start a selection run which retrieves the Message Control records and sends them for further outbound processing. The program is report RSNAST00, which is also generally scheduled with dispatch time 1 in live operation.
    Activities
    Once the application document has been posted, outbound processing stops after the message status record has been generated and is triggered again by the test program. Choose SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Outbound ® Outbound from MC.
    Errors are stored in the Message Control processing log (document header) and in the status records of the IDocs. The status records, however, are only available if the IDoc was successfully generated.
    Use
    This test program selects one or more outbound IDocs and forwards them to the external system. You can choose the IDocs according to various criteria (for example, recipient or business message).
    Prerequisites
    You require outbound IDocs which were generated without errors (no error status). The partner profiles, therefore, must be maintained completely.
    Outbound processing must stop when the outbound IDocs have been generated to allow the test program to intervene. You can check this by setting the output mode to “Collect IDocs” in the partner profile for the IDoc Interface. If you now generate an outbound IDoc for the partner (for example, using the application or the test tool), the IDoc is only generated in the SAP System and is not forwarded to the external system. This test program, therefore, is simply used to start a selection run which retrieves your IDoc(s) and sends them to the external system. The program is report RSEOUT00, which is also generally scheduled with the output mode “Collect IDocs” in live operation.
    Activities
    You start the test program by choosing SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Outbound ® Outbound from IDoc (WE14).
    You can decide whether the output mode is set to “Start subsystem” or “Do not start subsystem” in the partner profile. This defines whether the external (sub) system processes the IDocs further.
    Use
    This program is used to test whether status confirmations for an outbound IDoc are sent correctly from the external system to the SAP System. The port type here must be set to “File”.
    Prerequisites
    A correct status file which can be generated by an EDI subsystem, for example, is required. The status file must refer to an existing outbound IDoc in the SAP System. You can also generate such a status file yourself.
    The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type “File” in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
    Features
    The SAP System reads the status file. The IDoc number contained in the file refers to the outbound IDoc, to which the status confirmation relates. The confirmed statuses are “credited” to the relevant IDoc in the form of status records in the SAP System.
    Activities
    Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Status ® Edit Status File (WE17) and pass the inbound port, name and directory of the file. These entries overwrite the standard values which you have stored in IDoc administration using the test port.
    Test: Inbound Processing: Modified Outbound File
    Use
    This program converts an outbound file with IDocs to a correct inbound file and sends the new file for inbound processing. The outbound file is not modified and can therefore be used more than once. The port type here must be set to “File”.
    Prerequisites
    You need a correct outbound file, for example, a file which is generated by the test tool or using a standard outbound processing. In this case, a port of the type “File” must be specified in the partner profile for the IDoc Interface, so that the IDoc(s) can be written to a file.
    The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type “File” in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
    Features
    The program imports sender and recipient data as input parameters from the user. The program reads the IDoc file and changes the corresponding entries in the IDoc control record. The changed data is written to a second IDoc file at the operating system level.
    Standard inbound processing is then triggered;
    ·        Reading the modified file
    ·        Generating the IDoc(s) in the SAP System
    ·        Processing in the application
    Activities
    Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Inbound ® Inb. Mod. Outb. File (WE12).
    Set the sender and recipient data, as well as the outbound file and the inbound file to be generated (path and name). Your entries for the inbound file overwrite the standard values which you have stored in IDoc administration.
    The recipient in this case is the SAP System. The port is used for identification purposes:
    ·        SAP (for example RSMITH
    Test: Inbound Processing: Original Inbound File
    Use
    This program reads an inbound file and sends the file for inbound processing. If all data has been successfully read, the file is deleted.
    Prerequisites
    You require a correct inbound file. In this case, correct means that the:
    ·        Sender and recipient in the control record are correct
    ·        Direction in the control record is set to 2 (inbound)
    ·        Client in the control record and data records are correct or empty
    The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type “File” in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
    Features
    The program reads the IDoc(s) from the inbound file and sends them for standard inbound processing (with processing within the application).
    The file is deleted after being read successfully!
    Activities
    Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Inbound ® Inb. Orig. Inb.File (WE16) and pass the following data:
    ·        Inbound port
    ·        Name and directory of the file
    These entries overwrite the standard values, which you have stored in IDoc Administration using the test port.
    Thanks

  • CHAP Dialing and Receiving Call

    Hi,
    I'm implementing a solution, where few sites will be dialing and accepting calls.
    For example, A will dial tp B when their primary is down, but when the B primary is down, it will dial to A, and vice-versa.
    Trying to make this work using backuo interface, but in backup interface cannot accept calls.
    Any idea how can this be perform??

    hi
    In this scenario you can have 2 dialer interfaces on both the sides binded to ur physical BRI interface in which you can use one dialer interface for dial out and one for dial in.
    You need to take care of the dialer string and other authetication details on both the dialers.
    Also the floating static routes thru both the dialer interfaces for your access as well as for the remote locations access.
    do find the link which deals the same but with PRI its similar to the bri only the physical interface config changes.
    http://cisco.com/en/US/tech/tk801/tk133/technologies_configuration_example09186a0080094559.shtml
    for more info in dial technology do check this out ...
    http://cisco.com/en/US/tech/tk801/tk133/tech_configuration_examples_list.html
    regds

  • Is there oversea roaming detection for telemarket outbound dialer?

    Hi All,
    Is there any ovesea roaming detection for telemarket outbound dialer that UCM will drop call before connection?
    Lawrence

    In preview mode, isn't it the responsibility of the agent to tag / wrap up the call?
    Thanks!
    -JT-

  • Test call of TP ended with return  0212

    while releasing a transport request, getting the following error message-
    test call of TP ended with return  0212
    your transport request cannot be exported , since all the requirements are not fulfilled
    calling transport control (tp) program "TP EXE CHK DEVK908291  pf=usr/sap/trans/bin/tp_domain_PRD.pfl -Dtransdir=usr/sap/tr"
    which checks the export requirement , returned the following information
    returned code from tp :0212
    further processing is terminated
    Please help if anyone has any clue
    Regards
    Al Mamun

    Hi Eric,
    Thanks for your reply,
    I have checked the configuration, looks ok. The path is ok, I missed the / before usr while typing this message.
    one thing I checked that there is no cofile or datafile corresponding to that transport. Same thing is happening while releasing  other transports.
    Is it mount problem?
    Al Mamun

  • Test call of transport control program (tp) ended with return code 0200 Message no. TK094

    Hello Expert,
    My SAP System environment as follow
    SAP Product : SAP NetWeaver 04
    Operating System : Windows 2003 32 bit
    SAP Database : MS SQL 2005 32 bit
    I have installed SAP NetWeaver 04 system with system copy option. I have installed Application server & Database server on different physical server. App server : SSC2PAS3SFWBW and Database Server : SSC2PAS3SFSQW1.
    After SAP NetWeaver 04 installation with system copy I have done TMS configuration with virtual system for a test, It is working fine but while releasing request form SFD system (Development system) it get error  “Test call of transport control program (tp) ended with return code 0200. Message no. TK094”
    I have reconfigured the TMS and check but it can’t help. TR gets release and import with OS level but at SAP level it gets error.
    Trans --> Log
    1 ETP199 ######################################
    1 ETP199X######################################
    1 ETP182 CHECK WRITEABILITY OF BUFFERS
    1 ETP101 transport order     : "SFDK905838"
    1 ETP102 system              : "SFD"
    1 ETP108 tp path             : "tp"
    1 ETP109 version and release : "340.16.72" "640"
    1 ETP198
    2EETP128 No target system defined. "SFDK905838" is not a transport request.
    1 ETP182 CHECK WRITEABILITY OF BUFFERS
    1 ETP110 end date and time   : "20140602150208"
    1 ETP111 exit code           : "12"
    1 ETP199 ######################################
    Steps for Reconstruction                                            
    # Upgraded latest SAP Kernel Non-Unicode 640_Rel Patch level 404
    # Reconfigured the TMS
    # Full User Permission has been set to all SAP Directory.        
    Rgds,
    Ashok      

    Hi Ashish,
    I have removed virtual system form TMS and configured with Development & Production system, but the same error. Not able to release TR.
    SLOG as below.
    ERROR SFDK905832           SFD f 0012 20140602090930 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602093923 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602094059 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602102854 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602103633 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602104142 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602111140 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602112723 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602113109 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602113704 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602113722 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602113753 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602113809 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905834           SFD f 0012 20140602125959 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905834           SFD f 0012 20140602130035 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    START EXPORT PREPARATION   SFD e      20140602132917              sfdadm       SSC2PAS3SFWBW 20140602132916001358
    START tp_getprots          SFD E      20140602132917              sfdadm       SSC2PAS3SFWBW 20140602132916001358
    STOP  tp_getprots          SFD E      20140602132920              sfdadm       SSC2PAS3SFWBW 20140602132916001358
    STOP  EXPORT PREPARATION   SFD e      20140602132920              sfdadm       SSC2PAS3SFWBW 20140602132916001358
    ERROR SFDK905836           SFD f 0012 20140602133526 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905836           SFD f 0012 20140602133540 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905838           SFD f 0012 20140602144313 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905838           SFD f 0012 20140602144350 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905838           SFD f 0012 20140602144430 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905838           SFD f 0012 20140602150202 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905838           SFD f 0012 20140602150208 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905838           SFD f 0012 20140603080634 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905838           SFD f 0012 20140603081006 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905838           SFD f 0012 20140603083952 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905838           SFD f 0012 20140603084005 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603091608 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603091617 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905842           SFD f 0012 20140603091826 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603093805 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603101944 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603102709 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603114753 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603121948 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603122039 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603123438 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603135937 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603140114 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603140233 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603140339 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603141743 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603150924 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905844           SFD f 0012 20140603152403 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905844           SFD f 0012 20140603152753 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905844           SFD f 0012 20140603153518 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905844           SFD f 0012 20140603162013 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905844           SFD f 0012 20140603162544 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905844           SFD f 0012 20140603162639 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905844           SFD f 0012 20140603162755 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905844           SFD f 0012 20140603163347 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905844           SFD f 0012 20140603163740 default_user A559420      SSC2PAS3SFWBW                    
    Rgds,
    Ashok

  • Error:        Test call of transport control program (tp) ended with return

    Hi Experts,
    When we are trying to transport Request.
    Error:        Test call of transport control program (tp) ended with return code 0208
    in STMS what are the steps to fallow to just back up the code.
    Any Solutions is Greatly Appreciable...
    Thanks in Advance,
    Ram,

    RAM,
    check these links
    http://www.sapfans.com/forums/viewtopic.php?f=12&t=326264
    Re: tp ended with error code 0208
    Please post the question in relevant forums
    Thanks
    Bala Duvvuri

  • Error: Test call of transport control program (tp) ended with return code 0

    Hi Experts,
    When we are trying to transport Request.
    Error: Test call of transport control program (tp) ended with return code 0208
    in STMS what are the steps to fallow to just back up the code.
    Any Solutions is Greatly Appreciable...
    Thanks in Advance,
    Ram,

    Hi,
    a)If your system is UNIX check /usr/sap/trans is mounted or not?
    b)After configuring TMS did you save and activate?that can be one reason.
    c)tp might be corrupted.u need to upgrade your tp. (or you can upgrade to the latest kernel)
    Please check the below link
    could not start transport control program tp
    However as suggested by NIbu, you should restart the server once before doing any other checks
    Thanks
    Debdeep
    Edited by: Debdeep  Ray on Jul 13, 2009 4:28 PM

Maybe you are looking for