On Wed, 2008-01-16 at 16:11 +0000, Stephen Paterson wrote: > Hi Srini, > > It is also present in the Contact, Via and Request-Line and as I > understand it, these are necessary requirements (well, if future > communication is to be over TCP) but that's not the question. > > The question is, is it valid to have transport=tcp as a URI parameter in > the To and From headers? Calls are being rejected on this basis. I can't > find anything forbidding it although I will concede that it is rather > unnecessary.
Unless the From header cannot be parsed as syntactically valid, I cannot imagine any reason to reject a call based on the presence or absence of any url parameter it might have. Other than the tag, the From header has no real semantics in SIP - it's essentially decoration. -- Scott Lawrence tel:+1.781.229.0533;ext=162 or sip:[EMAIL PROTECTED] sipXecs project coordinator - SIPfoundry http://www.sipfoundry.org/sipXecs CTO, Voice Solutions - Bluesocket Inc. http://www.bluesocket.com/ http://www.pingtel.com/ _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
