On Wed, 2010-02-24 at 21:16 +0000, Aaron Clauson wrote: > Since that would take extra work on the server and the client I'll be a > heretic and stick to my 184 info response approach for the time being. It's > not much of a contravention of the standard. A UAS can send back as many > info responses as it likes and the standard doesn't forbid a UAC from doing > some arbitrary processing when it receives an info response, in this case > forking a new call.
As long as you don't mind requiring the UAC to support the non-standard feature. But generally in SIP, even the largest vendors discover that their business benefits if they can use strictly standard UAs. Dale _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
