Dale,

Notwithstanding what I stated below, the design team also recognised
that in certain environments the proxy simply would not authorise a 6xx
to literally apply to all branches, and would instead override this,
particularly in a call centre, for example. So basically what it means
is "I would like to rejection to be "everywhere", although in practice
this might not be allowed and the proxy might permit some exceptions,
e.g., forwarding outside the domain, forwarding to email.

John

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
> On Behalf Of [EMAIL PROTECTED]
> Sent: 25 April 2008 03:50
> To: [email protected]
> Subject: Re: [BLISS] Rejection conditions for ACH
> 
> 
>    From: "Elwell, John" <[EMAIL PROTECTED]>
> 
>    The BLISS ACH design team feels that, on balance, 6xx response
>    codes should be strictly "everywhere", to be consistent 
> with RFC 3261.
>    Also, the design team had seen "global rejection" as being a 6xx
>    response code and applying "everywhere". I think there is 
> a need for
>    such a global response, e.g., for handling unwanted traffic.
> 
> To clarify -- The difficulty as I see it is that the 3261 semantics
> for 6xx responses is unusable in practice.  In the sipX proxy, we've
> had to treat 6xx responses as 4xx responses because a popular brand of
> phone generates a 603 response when the user pushes the Decline
> soft-button in response to an incoming call.  If the proxy treated 603
> per 3261, the call wouldn't go to voicemail.
> 
> I can see the motivation to define a "global rejection" function for
> ACH, but I fear that it will be impossible to use, that very quickly
> it will run into the problem we've seen, or one like it.  I don't
> think that a workable global rejection function can be defined without
> dealing with the "rejection scoping" problem.
> 
> Dale
> _______________________________________________
> BLISS mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/bliss
> 
_______________________________________________
BLISS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/bliss

Reply via email to