----- Original Message -----
Sent: Tuesday, October 14, 2003 1:29
PM
Subject: [Sip-implementors] Must Proxy
forward or drop a 4xx, when 2xx is got from other leg?
Hi All,
I have a query in Forking Proxy behaviour.
(Incase this
query has already been discussed, please give a pointer to that
mail
thread)
The scenario is as below:
The Proxy gets a 4xx from the
other branch,after it has got a 2xx from the
first branch.
Now should
the Proxy forward this 4xx (or) drop this?
As per RFC Clause:16.7
Item9
----------------------------------
If the server transaction is no
longer available to handle the transmission,
the element MUST forward the
response statelessly by sending it to the
server transport.
=>This means that 4xx has to be FORWARDED statelessly as the
Server
Transaction(ST) would have been deleted,as soon as forwarding the
2xx.
As per RFC Clause:16.7
Item5
----------------------------------
After a final response has been
sent on the server transaction,
the following responses MUST be forwarded
immediately:
- Any 2xx response to an INVITE request
A stateful
proxy MUST NOT ***immediately*** forward any other
responses.
=>
This means that 4xx has to be DROPPED(?).
=>Here,***immediately***
refers to till some timer value or indefinitely?
These 2 clauses creates an
ambiguity as to what is the expected
behaviour...........
Can someone
please clarify?
[ABN] here
the 4xx must not be forwarded back UAC, it must be DROPPED
......
here ,***immediately*** means no need wait for
response staus on other clients (If there are any)
#
[UAC] [PROXY]
[UAS_A]
[UAS_B]
# |
INV
|
|
|
# |---------->
|
|
|
# |
100
|
|
|
# |<-----------|
INV
|
|
#
|
|--------->|
|
#
|
|
INV
|
#
|
|----------------------->|
now there are 2 CT and 1
ST.
#
|
| 200
|
|
# |
200
|<---------|
|
#
|<-----------|
|
|
now there will be only 1 CT and NO STs.
#
|
|
486
|
#
|
|<------------------------|
# |
486(?)
|
|
|
# |
forward?|
|
|
#
|<---------|
|
|
#
|
|
ACK(?)
|
#
|
|
drop?
|
#
|
|------------------------>|
#
|
|
|
|
#
|
|
|
|
#
Thanks,
Prakash.
_______________________________________________
Sip-implementors
mailing list
[EMAIL PROTECTED]http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
