[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sip] Preventing unanticipated respondent syndrome when retargeting
ETSI and TISPAN use it for their Communication Diversion service, that
means that people are using it.
They stick in the History-Info header containing an entry for the
diverting party and an entry for the diverted-to party. In fact they use
History-Info here to say something about the future of the request;-)
/Hans Erik
-----Original Message-----
From: Dean Willis [mailto:dean.willis at softarmor.com]
Sent: Friday, April 04, 2008 10:55 AM
To: Hans Erik van Elburg
Cc: sip at ietf.org
Subject: Re: [Sip] Preventing unanticipated respondent syndrome when
retargeting
On Apr 4, 2008, at 2:45 AM, Hans Erik van Elburg wrote:
> Dean mumbled:
>> I therefore propose a provisional response from Proxy to Alice, which
>> I'll provisionally call "121 (Retargeting)"
> Is this any different then 181 Call Is Being Forwarded from RFC3261?
Well, 181 is rather totally unspecified, AFAIK.
Th main difference is that the proposed 121 has a Contact that tells you
where the call is being forwarded. It also specifically means that the
call was "retargeted" meaning that the anticipated respondent has
changed.
It might be reasonable to "further specify" 181 to mean the same thing,
since, AFAIK, nobody ever actually used 181 for anything.
John Elwell made a try at it in draft-elwell-sipping-redirection-
reason-01, but this lacked the whole "Contact" parameter bit that tells
the recipient where the call is being forwarded to.
--
Dean
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip