As in most undefined error situations you can do what you like as long as it's reasonably sensible. Since the behaviour is purely confusing, you could just drop the packet. Eventually the erroneous SIP component will get fixed or removed - I doubt it would last long in usage - it would get found out pretty quickly. If send a 400 request, you are just guessing at UDP or TCP. It's hard to know which one would work. Or send both TCP and UDP responses? That's just confusing!! Or you could just pretend it's a TCP message and process it normally - things could eventually work by the time the responses are due to be sent back. Or it might all totally fail ! As I said, it's upto you. It's in the realms of undefined behaviour so do what you like. Personally, I might go for dropping the packet - then the downstream element would have to investigate why no responses are coming back. Regards, Attila
________________________________ From: [EMAIL PROTECTED] on behalf of Iñaki Baz Castillo Sent: Sun 28/09/2008 00:03 To: [email protected] Subject: [Sip-implementors] Incoming UDP request with a top Via indicatingTCP, what to do? Hi, what should do a UAS if it receives an incoming UDP request indicating TCP in the top most Via header? - Should the UAS drop the request (no reply)? - Should it rejects it with a 400? but then: how to send the response (UDP or TCP)? -- Iñaki Baz Castillo _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
