KB Article #177630
PESIT error Gateway to CFT: prot.diag="301, Called party identification not known"
Problem
The error on Gateway side while transferring a file from Gateway to Transfer CFT using PESIT protocol:
SUP006W 07.01.2016 17:27:46 MYCFTPARTNER(33554433) connection in requester mode refused: reason="166, Connection failure" / prot.diag="301, Called party identification not known".
is due to mistaken configuration.
Please find below the correct setup.
Resolution
In order to transfer files form Gateway to Transfer CFT, one has to make the following configuration.
On Gateway side:
Activate the PESIT E protocol from Configuration. The port can be 6330.
Create a local site from Partner Management < Sites < Local Site. For exemple, MYGATEWAY.
Create a remote site from Partner Management < Sites < Remote Site. For exemple, MYCFTPARTNER. Indicate also the following: protocol (PESIT E), protocol identifier (for exemple, PROTID), network address (select TCP/IP and put the IP of the CFT machine and the port, in the exemple it is 1761).
On Transfer CFT side:
Make sure that PESIT transfer protocol is working. The SAP might be 1761.
When declaring the Gateway Partner, go to Configuration > Ongoing configuration > Partner and create a partner with the following characteristics:
ID: any identifier you want
NSPART: Gateway’s protocol identifier, which in our case is PROTID
NRPART: Gateway’s local site, which is our case is MYGATEWAY
Addressing: the protocol is PESIT, the SAP is the Gateway PESIT E port which in our case is 6330. The host is the IP machine address of the Gateway.
How to transfer a file from Gateway to CFT:
When you make the transfer request, use the Originator Alias your local site (MYGATEWAY) and Destination Alias, the remote site (MYCFTPARTNER).
Attention!
In order to work, the NSPART from Transfer CFT should be the Protocol Identifier from Gateway.
The NRPART from Transfer CFT should be Gateway’s local site.
If the Gateway local site is missing, on Gateway log it appears the following message: “connection in requester mode refused: reason="166, Connection failure" / prot.diag="301, Called party identification not known".”