Re: [reSIProcate] Multiple REFER handling in resiprocate
Hi Robert,
Makes sense to me. I would be great if you could submit a patch for
this. Thanks!
Regards,
Scott
On Thu, Aug 19, 2010 at 6:03 AM, Robert Szokovacs
<rszokovacs@xxxxxxxxxxxxxxx> wrote:
> Hi,
>
> we're developing a server application where the client can send multiple REFER
> requests in the same dialog. According to RFC3515, section 2.4.6, each REFER
> creates a subscription and they are identified by an Event header in the
> NOTIFYs. The RFC states that this Event header must include an id parameter,
> equal to the CSeq header of the REFER request that created the subscription.
> Currently the DUM code doesn't do this (see BaseSubscription::BaseSubscription
> in resip/dum/BaseSubscription.cxx), it just puts "refer" in the Event header
> (or if the request had an Event header, it is kept and used in the NOTIFY
> too).
> I think this is not the correct behaviour and it can be easily fixed.
> Should I send a patch here?
>
> br
>
> Szo
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxx
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
>