SMSc 3.5: GetSMSCustomisationIndicator not returning appropriate responses

Please verify that CustomizationInfoService getSMSCustomizationIndicator is
returning correct responses, both when a valid customer BPID is provided and in
the invalid case.

dev wsdl:
http://centos52-64-yell-dev-mms1:8080/CustomizationInfoService/CustomizationInfoService?wsdl

Reported by Graham French at Yell:

> >>>>> Dave,
> >>>>>
> >>>>> I've done a little investigation and it looks like in a
> >>>>> 'normal request' we send you a customBpId with an incorrect
> >>>>> namespace (http://yell.com/esb/tsa/services instead of the
> >>>>> correct namespace http://yell.com/esb/tsa/icommon). By
> >>>>> webservice design this should result in a soap fault coming
> >>>>> back to us saying 'rubbish data in request' or 'schema
> >>>>> validation failure'. Instead you send an incorrect response,
> >>>>> which we fail, so it makes it look like the error is with
> >>>>> you, when it was our poor data we sent. I can fix our
> >>>>> request, but you should be sending a soap fault back to us
> >>>>> when we send rubbish data
> >>>>>
> >>>>> Secondly if we send a customBpId that is not in your system,
> >>>>> then you send a invalid response with no CustomerBpId in it.
> >>>>>
> >>>>> And lastly as mentioned before the header is not reflected
> >>>>> back.
> >>>>>
> >>>>> The most pressing issue here is to fix the first instance,
> >>>>> which is for us to do (I shall put a request in for a new
> >>>>> deploy to our systems now), but it would be very helpful if
> >>>>> we could have soap faults returned where our data does not
> >>>>> match the service definition. The last two are less pressing
> >>>>> issues, but would preferably be required to go live.
> >>>>>