Just because your routers permit ICMP packets (PING) does not mean that they will permit traffic on all other TCP ports. Layer 3 switches can perform actions like a firewall these days. Perhaps your network team needs to be brought in to evaluate the network connectivity.
A sniffer like Wireshark could be placed on another computer next to your CallPilot reporter and you could sniff the wire for traffic to make sure that the connection attempt is responded to by the CallPilot servers. If they are being responded to (or if they are not being sent) then the problem is local. If the communication from your CPRPT server is being sent but not getting a response, your problem
may be the network. (I hate this answer because I don't like to throw the network guys under the bus for something that might be a mis-configuration or installation issue on the server itself.)
I found the reference in the manual that your vendor referred you to, but I think the definition of "network segment" becomes the key.
Port requirements
The following ports must be enabled when using a firewall:
• TCP port 20 (FTP)
• TCP port 21 (FTP)
• TCP port 135 (DCOM)
• UDP port 135 (DCOM)
• TCP port 143 (IMAP)
• TCP port 389 (LDAP)
• TCP port 636 (LDAP)
• TCP port 993 (IMAP)
• TCP ports 1024 to 65535 (DCOM)
• UDP ports 1024 to 65535 (DCOM)
I found nothing in either the Planning and Engineering guide nor the Software Administration and Maintenance (installation of CallPilot reporter) that says that they must be in the same
subnet.
Within the same network segment, in the scope of this documentation, I believe means within your network and not connected via network address translation or other means that would place CPRPT outside of your network.
I've had lots of problems with CallPilot reporter server where the customer did not adhere to the server requirements that we delivered to them in writing. I've rarely had network issues (but I have had them). Sometimes I occasionnaly get CPRPT mismatch with the CallPilot server (someone downloaded an earlier version of CPRPT than was compatible with the server.)
Regardless, if it were me I would at least insist that the latest CPMGR/CPRPT for your CallPilot version (4.0) is installed. These updates are done by Nortel to resolve known issues.
Perhaps after updating to the latest CPMGR your CPRPT issue will go away (remember, I've had a MWI issue that was apparently resolved by installing the latest CPMGR... no explanation why that was the case...)