Re: [sipcore] SBC-friendliness of 4244bis

It is worth pointing out that for the ISDN information to the caller that the call has been forwarded is not subject to privacy, only the identity where the call has been forwarded to. So in this case, it would be reasonable to expect that part of the H-I entry survices the SBC.

There are sound service reasons for doing this, i.e. the users complain when they end up talking to a different party to the one they expected - with a normal tendency to hang up immediately (possibly with an intervening "Oh wrong number sorry".

Keith

> -----Original Message-----
> From: sipcore-bounces@ietf.org 
> [mailto:sipcore-bounces@ietf.org] On Behalf Of Worley, Dale R (Dale)
> Sent: Tuesday, September 07, 2010 6:57 PM
> To: Hadriel Kaplan
> Cc: sipcore@ietf.org
> Subject: Re: [sipcore] SBC-friendliness of 4244bis
> 
> ________________________________________
> From: Hadriel Kaplan [HKaplan@acmepacket.com]
> 
> And I see them being removed from responses all-together, 
> especially in call centers where they don't want the caller 
> to know the specific agent it was sent to.
> ________________________________________
> 
> That would be unfortunate -- the handling of H-I in responses 
> is as important as handling of H-I in requests, and in 
> principle, the H-I in an outgoing response can be edited to 
> show precisely what the service provider wishes to show about 
> the call's handling.  In any case, the service provider 
> shouldn't edit the H-I entries concerning routing in any 
> other service provider's network (unless there is some sort 
> of joint operating agreement).
> 
> Dale
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
> 