However, it has been pointed out recently that RFC 3725 does not work
with dynamic payloads in the SDP. With many current and all future
codecs using dynamic payloads, this could be a much greater
interoperability issue than support of REFER.
As an aside, a number of us plan a new effort to get this draft on
remote call control using REFER adopted as a working group item so it
can progress to RFC.
http://www.ietf.org/internet-drafts/draft-mahy-sip-remote-cc-04.txt
Thanks,
Alan
Paul Kyzivat wrote:
> Ramesh wrote:
>
>> Hi,
>> I have come across a Draft that uses REFER to accomplish the 33PCC calls
>> instead of the INVITE method as stated by the RFC 3725. Can somebody
>> substantiate the reasoning behind not taking the REFER path. I am pretty
>> sure there is some very valid reason I just want to get educated on the
>> reason as I could not find too many threads on this subject.
>>
>
> Not all UAs support REFER. If you want your 3pcc implementation to work
> with as many UAs as possible the way using INVITE may be better.
>
> Paul
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
>
>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
