I think there are a few ways of doing this. This is what I did before:

   If message.Context.Addressing.Action.Value =
"http://soapaction.softwaremaker.net/ProcessThisMessage" Then
     Console.WriteLine("I am a SOAP Receiver. The BUCK stops here !")
   Else
     Console.WriteLine("I am a SOAP Router...Forwarding...")

     Dim viaUri As New Uri("soap.tcp://" + System.Net.Dns.GetHostName() +
":2088/soapreceiver")
     Dim toUri As New Uri("soap://softwaremaker.net/soapreceiver")

     message.Context.Addressing.Destination = New EndpointReference(toUri,
viaUri)

     Dim channel As ISoapOutputChannel
     channel =
SoapTransport.StaticGetOutputChannel(message.Context.Addressing.Destination)
     channel.Send(message)
     channel.Close()

As you can see from the above, I route the message based on the SOAPAction.
You can use your own method as preferred. Since this is a SOAP Receiver, the
routed endpoint can also respond with another SOAP Response
real-asynchronous duplex-style.

HTH.

Cam,

    Implementing a TCP based router is pretty tricky and unfortunately
there needs to be a lot of thought when you build a router of this sort. If
you're still interested, I can share some insight into how you may go about
doing this. Basically you would have to go one level below
SoapClient/SoapService and deal with the raw channels themselves.

Let me know if you're still interested

Sidd [MSFT]