Below is the example in java to retrieve fault message and return code:

catch (SaveContactToListFault f)
{
Log("GOT SaveContactToListFault!");
Log(f.getFaultMessage().getFaultMsg());
Log(f.getFaultMessage().getRetCode())
}

Thanks,
Prashant

Hi David

I've looked into logs, retrieving the custom attributes values from tables is slow, since you've around 25-30 attributes per contact it is taking in seconds to fetch complete contact record.
The regular DB maintainance could improve overall system performance. I'm assuming that postgres is being used. If so- please try the steps below during maintainance window:

stop POM & vpms services.
restart postgresql service on remote DB server.
Goto SQl prompt of configured POM database & Run VACUUM FULL ANALYZE VERBOSE query. This might take in minutes depending on size of database.
Login to primary POM command, cd to $POM_HOME/bin directory and run ./reindexPOMPGDB.sh script.
start POM & vpms services.

If issue persists, other workaround could be to retrieve specific required attribute values (using Get contact attribute) instead of complete contact record.

Thanks,
Prashant

Which campaign pacing type is being used? If it is preview type of pacing :
The campaign manager clean up thread check for stuck attempts in “in –progress” state & if found in same state for more than time configured on the system, campaign manager will reset stuck calls to release the blocked licenses. This parameter (Maximum preview time) is configurable on global configuration page under “Campaign settings” section

Please share logs of campaign manager (PIM_CmpMgr.log) and MPP (CXI logs) for further investigation.

David,

Could you please confirm POM & POM PDC version? If issue persists please share OD applications' trace.log file(from appserver) & $POM_HOME/logs/PIM_WebService.log file from EP machine.

Thanks,
Prashant

David,

Could you please confirm POM & POM PDC version? If issue persists please share OD applications' trace.log file(from appserver) & $POM_HOME/logs/PIM_WebService.log file from EP machine.

Thanks,
Prashant

Please follow steps in section "Changing the hostname or IP address on a dedicated primary EPM server" page 117 from EP document
https://downloads.avaya.com/css/P8/documents/100146867
Then follow instructions in section "Editing POM server" page 257 from POM document http://downloads.avaya.com/css/P8/documents/100176701

Thanks,
Prashant

The TextID & ContactGroupID are populated by POM for other POM applications. They are used internally to play text using AvayaPOMNotifier app. As you've requested we might consider this request for future releases.

Thanks,
Prashant

Frank,

Please note that this will work only for POM3.0 release. In POM2.5 you have to rely on multiple apps or CAV approach you've explained above.

Yes, the TextID & ContactGroupID are passed by POM server to OD. However they are not prepulated internally within POM PDC.

Frank,

The completion code is by default populated by system. It is not required to invoke GetContactData in callflow. Please try accessing pominfo:CompletionCode before using other PDC nodes. IN appl. trace.log it should show completion code as below:

com.avaya.sce.pdc.pim.DataConnector.GetContactAttributeImpl:getVariableValue(pomInfo, SessionID): 569665

com.avaya.sce.pdc.pim.DataConnector.GetContactAttributeImpl:getVariableValue(pomInfo, CompletionCode): Answer_Human

The PomPDCInstallerSite_3.0.0.148.jar release along with POM 3.0 GA version supports this functionality.

Thanks,
Prashant

Could you please add entry of POM server in hosts file? If OD is on windows, goto windows run option. enter drivers, navigate to hosts file in etc folder. Add entry like below

1.1.1.1 HOSTNAME

This should be same as entry /etc/hosts file from EP/POM machine.

Thanks,
Prashant

The contactID & campaign JobID are populated by system. Other fields in pomInfo requires user input. This is documented in deverloper's guide .pdf
You can use GetCampaignDetails webservice to get all campaign names created on POM server.

Thanks,
Prashant

The SDK for POM 3.0 GA is attached, please refer readme.txt for more details.

The contents of the zip package are:
1.POMDesktopAPI.dll : The API will be available through this DLL.
2.Avaya.POM.Agent.ObjectModel.dll : The data structures used for the API will be available through this DLL.
3.log4net.dll : This is a helper DLL for the API.

Please share trace.log from OD appl & PIM_WebService.log from $POM_HOME/logs location for further investigation.

Thanks,
Prashant

Please check mpp logs, the SM / SES configuration used could be an issue.

Thanks,
Prashant