Re: [reSIProcate] RES: ClientSubscriptionHandler
- From: Ryan Kereliuk <ryker@xxxxxxxxx>
- Date: Fri, 25 May 2007 14:08:52 -0600
onUpdateExtension is called when you get a NOTIFY with an Event header
field with a value of 'refer' and a sipfrag message body, where this
sipfrag contains the status line for a 1xx response. This callback is
only invoked when the NOTIFY is missing a Subscription-State header,
which is technically a violation of RFC 3515. So you should only worry
about onUpdateExtension if you need to solve an interop problem for a
customer who is having problems getting help from the vendor at fault.
Thanks,
-Ryan
On 2007-05-25 at 14h54, Gustavo Honorato wrote:
>
> OnUpdateExtension, I don?t know.
>
> _____
>
> De: Matthias Moetje [mailto:moetje@xxxxxxxxxxxx]
> Enviada em: sexta-feira, 25 de maio de 2007 12:56
> Para: resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
> Assunto: [reSIProcate] ClientSubscriptionHandler
>
> could someone please shed some light on the callback functions of the
> ClientSubscriptionHandler? Some are easy to understand but when are:
>
> onUpdatePending, onUpdateActive and onUpdateExtension actually called?