> You are missing the point. The issue is simply that a > downstream entity wants to communicate that it can not accept > the call because it is congested. This is not an RFC 3263 > issue. This a Layer-5 (SIP) issue. We need an L5 mechanism to > communicate back to the proxy/UAC that an alternate route > should be attempted.
The 503 is currently the only SIP response which triggers rfc3263 advancing (see rfc3263 section 4.3 and rfc3261 28.1) instead of only other types resulting from other failure responses and/or 3xx. However overload within SIP is currently being enhanced; see http://tools.ietf.org/wg/sipping/draft-ietf-sipping-overload-reqs/ and http://www.ietf.org/proceedings/08mar/slides/tsvarea-3.ppt. _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
