Re: [Enum] Response codes and multiple paths to a destination

[Dale.Worley at comcast.net]

   From: Paul Kyzivat <pkyzivat at cisco.com>

   I'm sympathetic to the general issue you are raising. But I think some 
   of the codes you have issue with can be explained away as non-issues:

   402: does it really matter who needs to be paid? If the UAC is willing
   and able to pay, then go ahead and try that. If not, then go ahead and 
   try the pstn. (Maybe you will get lucky and its free on the pstn and 
   only charged via sip. (NOT))

Or we could just say that since the implementation of 402 is reserved
for future standardization, handling this problem for the 402 response
is reserved for that same standardization.

   420: again - does it really matter? Either way you can't talk via sip, 
   but still have a chance via the pstn.

That's true if one path is SIP and the other path is PSTN.  But there
is also the case where both paths are SIP.  If one SIP path rejects
you based on the failure of a Proxy-Require, you want to try the other
path.  But there's no point in retrying if the failure is due to
Require.

OTOH, as long as the Require and the Proxy-Require options do not
duplicate names, the Unsupported header in the response will
distinguish the two cases

   422: There is no reason for a UAC to ever *request* a session timer.

OK, I was not aware of that.

Dale

_______________________________________________
enum mailing list
enum at ietf.org
https://www1.ietf.org/mailman/listinfo/enum