HI
Not able to send message to http://test2messaging.easylink.com/soap/sync.
returns bad gateway error.
I havebeen using this for quite sometime and never faced issue. There is no change from configuration perspective.
Domain being used is flusme
I don't see any issues with accessing this URL right now.
Can you access it from your browser? You'll get an error, but you should be able to verify connectivity. I suggest doing this with Chrome or Firefox, rather than IE.
Hi,
i got a pretty similar problem here. I cannot reach the URL http://test2messaging.easylink.com/soap/syncThe connection always times out, no difference whether trying to reach it by browser sending a soap request.
It worked for about half a year now without problems, also in my case there were no changes in the configuration.
Regards
I am having similar issue.
Not able to connect to
1. Easylink Test portal - https://test2.myportal.easylink.com/welcome.do
2. Not able to send Fax via Test System - http://test2messaging.easylink.com/soap/sync
from Saturday Oct 6th,2012.
The test2 system is currently not available. The below was sent out earlier today. Apologies if you were not on the email list. I will update the forum when test2 is available.
Dear Valued EasyLink Customer,
Please be advised that our XDDS TEST2 and FLUSME Test systems are still unavailable. You will be notified once the issue has been resolved.
Please do not reply to this e-mail. It is for notification purposes only. If you have further questions regarding this, or any other issue, please contact Customer Support at 1-866-323-9707 or 1-732-460-5707.
Thank you.
EasyLink Customer Support
I can connect to the test2 portal however on trying to get the job list programmatically I'm getting an error. ([pt] Domain not available for this request) This is in code that has been functioning in the field for a couple months. I'm wondering if this is still a symptom of the test2 maintenance from last week.
Is the test2 system functional again?
This is not specifically related to the test2 system, but rather to another test system that is being brought online.
What I would expect you to be seeing with your API requests is that the result should indicate a warning, because the pt system is unavailable, but you should still get back correct results for your job list from test2.
Is that what you are seeing?
Actually it isn't what we are seeing. In executing the request to get the job list we are receiving a result that indicates the following with no faxes coming through:
Status Code: 2
Status Message: 'Result may be incomplete'
Error Code: 2801
Error Message: [pt] Domain not available for this request
Can you let me know your user ID and the Processing ID for the transaction, so I can investigate?
The Group ID is: 597578
The User ID is: T2/F2M/INTEGRA
The result being returned that contains the error information returns a submit ID of blank. Is this the processing ID you were requesting?
Have you been able to find anything with this that would indicate where the problem is coming from?
Sorry for the delayed reply.
This is more or less what I expected.
First of all, your request is asking for faxes in a 5 minute window on May 10, 2012. I'm pretty sure there aren't any faxes processed still on the test switch within that window. See the XML below:
<Interval><StartDateTime>2012-05-10T18:27:00Z</StartDateTime><EndDateTime>2012-05-10T18:42:00Z</EndDateTime></Interval>
Then the second question is why you're getting the warnings you're seeing. As indicated earlier, there is another test system that is in the process of being set up, and it doesn't have the back end set up to retrieve the data you're looking for.
As a result, you're getting back XML indicating a warning, to tell you that one of the possible domains for your request could not be processed. However, if there had been results from the test2 system, you would have received those as well. Here's what the result XML looks like:
<StatusCode>2</StatusCode><StatusMessage>Result may be incomplete</StatusMessage>
This is an unusual situation, but it is something that could happen in production, if one of the domains where your jobs process in production is in some way impaired.
In general, we recommend that you update your software to recognize this warning status for what it is and not consider it an error in the system.
However, I have made a configuration change that should prevent this error from occurring in the test2 system for right now.
If you want us to put it back so you can test the handling of the warning, please let us know.
