[SR-Users] TM clarifications Re: CANCEL before INVITE + loose_route()

[Alex Balashov]

On 06/21/2010 04:07 AM, Iñaki Baz Castillo wrote:

> Also note that CANCEL is hop-by-hop (in stateful mode), this is: a
> CANCEL is not relayed/forwarded by a proxy, but consumed/accepted by
> the proxy (so it immediately replies 200) and then the proxy must
> terminate *its* pending outgoing transactions (which would involve
> *generating* CANCEL requests for those transactions which already
> replied a 1xx).

Sure, but from a conceptual point of view this sounds like more like a 
UAS and less like a proxy, because the proxy is in this case is (a) 
the logical target of the CANCEL request from the UAC and (b) provides 
an encapsulating layer of abstraction in which the management of one 
or more branches is contained.

-- 
Alex Balashov - Principal
Evariste Systems LLC
1170 Peachtree Street
12th Floor, Suite 1200
Atlanta, GA 30309
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/