El Tuesday 03 June 2008 10:22:19 Attila Sipos escribió: > >>6XX behaviour is really painful. > >>I realy wonder why they break serail forking: > > To me, 6xx means the user you're trying to reach doesn't exist anywhere > or won't accept your call anywhere or can't accept your call anywhere. > So, it doesn't matter if you try another fork because it won't work > anyway.
But how could a UAS know that its proxy will want to forward the request to a voicemail system when receiving a negative reply? Why should a 6XX destroy still not generated branches? (ok, because RC 3261 says it but...) > Now, it could be that an endpoint is sending a 6xx response when it > should only be a 4xx (but that's another issue). The problem is that many UA's reply a 6XX instead of a 4XX :( Thanks. -- Iñaki Baz Castillo [EMAIL PROTECTED] _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
