Hi, What I think Iñaki tries to underline is the fact that the UAS has the knowledge about the destination user from the current branch. But a mid proxy may decide to serial fork the call to a new destination that points to a totally different user - and is this case the 6xx is not relevant as it is a different user.
Imagine something like this: I have user BOSS and user SECRETARY. I want my proxy to serial fork all the un-answered calls for BOSS. So, in the first step, the call will go to the UAS of BOSS and this may reply with 6xx if BOSS is totally gone. But this should not prevent my proxy to hunt the user SECRETARY for this call. Regards, Bogdan Attila Sipos wrote: >>> But how could a UAS know that its proxy will want to forward the >>> request to a voicemail system when receiving a negative reply? >>> > > More accurately, the UAS doesn't know if the destined user > is available on another fork so it shouldn't send a 6xx response. > > >>> Why should a 6XX destroy still not generated branches? (ok, because RC 3261 >>> says it but...) >>> > > Because 6xx means you cannot be successful so don't bother trying. > It stops time being wasted on other forks. > > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
