RE: [reSIProcate] DUM version 2 work session
Can you post an ethereal trace + log file of the offending dialog?
> -----Original Message-----
> From: Hong Yu [mailto:hyu@xxxxxxxxxxx]
> Sent: Tuesday, April 25, 2006 7:04 AM
> To: Derek MacDonald; Jason Fischl
> Cc: resiprocate-devel
> Subject: RE: [reSIProcate] DUM version 2 work session
>
> I have both the event handler and mime type registered. Initial
> subscription worked, But Dialog::dispatch didn't handle the first notify
> request from Cisco CallManager.
>
> Hong
>
> -----Original Message-----
> From: Derek MacDonald [mailto:derek@xxxxxxxxxxxxxxx]
> Sent: Monday, April 24, 2006 7:34 PM
> To: Hong Yu; 'Jason Fischl'
> Cc: 'resiprocate-devel'
> Subject: RE: [reSIProcate] DUM version 2 work session
>
> Did you have an event handler for the KPML event package installed in
> DUM?
> Another possibility is that you haven't registered the KPML mime type in
> DUM.
>
> You shouldn't need to customize DUM to handle KPML>
>
> > -----Original Message-----
> > From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:resiprocate-
> > devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Hong Yu
> > Sent: Wednesday, April 19, 2006 11:41 AM
> > To: Jason Fischl
> > Cc: resiprocate-devel
> > Subject: RE: [reSIProcate] DUM version 2 work session
> >
> > I ran into problems when implementing support for KPML for Cisco's
> > CallManager. After a UA subscribes for KPML event notification,
> > CallManager replies with 200 OK. Then it sends the initial NOTIFY
> > request. Dialog::Dispatch always returns 406 response. I added
> support
> > to check for KPML event, similar to the existing check for REFER
> event,
> > to make it work for me.
> >
> > Hong
> >
> > -----Original Message-----
> > From: jason.fischl@xxxxxxxxx [mailto:jason.fischl@xxxxxxxxx] On Behalf
> > Of Jason Fischl
> > Sent: Tuesday, April 18, 2006 7:03 PM
> > To: Hong Yu
> > Cc: david Butcher; resiprocate-devel
> > Subject: Re: [reSIProcate] DUM version 2 work session
> >
> > On 4/19/06, Hong Yu <hyu@xxxxxxxxxxx> wrote:
> > > One thing I'd like to see addressed is a better way of managing
> > > Transports, for example, removing of a transport at runtime. Also,
> > > fuller support of SUBSCRIBE/NOTIFY is definitely needed.
> > >
> > Can you be more explicit on what you mean by fuller support of
> > SUB/NOTIFY?
> > _______________________________________________
> > resiprocate-devel mailing list
> > resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> > https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
>