Response code: 504

Please help on this. Getting below error while communicating with remote domain

1046; reason="Failed to connect to a federated peer server"; fqdn="abc.com:5061"; ip-address="x.x.x.x"; peer-type="FederatedPartner"; winsock-code="10060"; winsock-info="The peer did not respond to the connection attempt"; source="sip.xyz.com"


  • Edited by xavmit Friday, July 24, 2015 10:58 PM
July 24th, 2015 10:57pm

Yes Eric,

I am able to telnet to the federated partners Edge server via port 5061.

But still same issue.

Free Windows Admin Tool Kit Click here and download it now
July 28th, 2015 3:55pm

Please help on this. Getting below error while communicating with remote domain

1046; reason="Failed to connect to a federated peer server"; fqdn="abc.com:5061"; ip-address="x.x.x.x"; peer-type="FederatedPartner"; winsock-code="10060"; winsock-info="The peer did not respond to the connection attempt"; source="sip.xyz.com"




July 28th, 2015 4:05pm

Please help on this. Getting below error while communicating with remote domain

1046; reason="Failed to connect to a federated peer server"; fqdn="abc.com:5061"; ip-address="x.x.x.x"; peer-type="FederatedPartner"; winsock-code="10060"; winsock-info="The peer did not respond to the connection attempt"; source="sip.xyz.com"

Free Windows Admin Tool Kit Click here and download it now
July 28th, 2015 4:05pm

SIP federation happens over 443. From the edge server can you telnet to the peer IP on 443? I still believe this issue to be at the peer end.

thanks

July 28th, 2015 4:56pm

yes i am able to telnet 443. checked with my local machine.
Free Windows Admin Tool Kit Click here and download it now
July 28th, 2015 5:25pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics