Though I don't understand the problem you experienced -- HTTP runs over a bidirectional TCP connection, if they got your request, then packets for that session were already flowing in both directions (the TCP session wouldn't set up otherwise). The only way I could see what you described would be if they had a proxy or some sort of deep inspection firewall in the middle that was blocking the return response.
Sure thing, do exactly what you're told.
That doesn't preclude you from firing back a message to say "Hey, this request is unusual and almost certainly wrong, are you sure this is what you wanted?"
When a nurse sees an order for 10000 mg of a drug that's never normally administered above 200mg, it's not their job to correct anything, but it is their job to ask the doctor "Hey, did you mean to write 100.00mg? Is this actually correct?"
We're seeing this a lot - doing projects directly with marketing department, largely so they can completely circumvent internal IT department's and their apparent stonewalling on seemingly simple requests.
(Of course it also means we're seeing things like completely outlandish requests that indicate fundamental security/privacy misunderstandings ("What do you mean you can't import our entire customer database into the WordPress site you're building and hosting cheaply for us?"), as well as last minute compliance intrusions ("Oh, you need this to live on a big-corp.com subdomain? That requires a security audit and risk assessment and mitigation document! How on earth have you got this far without knowing that?")
They were incredibly dependent on their filter rules, and their process assumed the filter rules were always correct and accurate.
One night I got confused about which window I was in and ssh'd into my desktop machine (on the internal 9/8 network) from one of the ibm.com backend servers (on the open internet). A "routine update" caused routes for 9.0.0.0/8 to be advertised on the open internet. Although I had a short escalation path it still took an hour from when I discovered the hole to get anyone in Global Services to accept it as a problem.
Question sounds reasonable - could be a fire & forget scenario.
Problem isn't the question but that it takes a week between iterations. If you had to order lunch and it was a week between asking for your steak and being asked if you want it medium or well done then the question isn't the problem
Now I avoid dealing with outsourcers as much as possible unless I have 100% understanding of the issue and can describe it precisely.
I doubt there are many companies who are 100% on top of things, but I get the sense that's more down to the department or the individuals you're dealing with. There are people who don't think things through everywhere. I certainly wouldn't bear a grudge against IBM for too long!
Maybe it's a language barrier?
I'm not sure why you're being down voted if other big enterprises didn't have this issue they would not put up with IBM having this issue. It is all about minimal work, CYA, and minimal thinking. It is why I always tell people that anyone who can really do IT (probably most on this site), will always have a job.
If you're outsourcing your operations, that's what you have to expect. They're not going to be as invested in your success as your own employees would be.
http://www.wsj.com/articles/SB100014240527487035155045761420...
http://www.theatlantic.com/international/archive/2013/10/beh...
http://www.rozinskiy.com/why-india-outsourcing-is-doomed/
Those are from the top of the fold of the Google search "quality of Indian tech workers."
Our client gave IBM the IP addresses to be white listed. They filled in a lengthy time consuming form that got sent through layers of IBM management till some ops team in India finally implemented the change one week later.
We started testing. It didn't work. We went back and forth for weeks. Finally we put a conference call together with all parties. Live on the phone we sent a series of SOAP requests over the wire. "Yes, we can see the requests", came the answer. We saw no response.
Finally whilst on the phone call, one of the IBM Tech's piped up.
"Did you want this traffic to go in AND out?", he asked.
"Well, HTTP traffic isn't going to be of much use if we don't get a response to our request you idiots", was the answer I wanted to give.
They pulled out the initial firewall request form. The request was to "allow traffic from our IP addresses in through the firewall to reach the client".
They took that absolutely literally, and nobody thought to question it. They also absolved themselves of any blame.
I detested IBM from that day on.