RE: [reSIProcate] problem with In-Dialog SUBSCRIBE(Re-posting )

[<basavaraj.puttagangaiah@xxxxxxxxx>]

Thank you very much Hong.

+Basu

 

---

From: Hong Yu [mailto:hyu@xxxxxxxxxxx]
Sent: Tuesday, April 04, 2006 12:49 AM
To: Basavaraj Puttagangaiah (WT01 - Product Engineering Solutions); resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [reSIProcate] problem with In-Dialog SUBSCRIBE(Re-posting )

 

SUBSCRIBE/NOTIFY supported is not complete in the stack. I”ve been modifying the stack to get it work for me. Once I’m satisfied with my modification, I will post the change back to repository.

 

Hong

 

---

From: basavaraj.puttagangaiah@xxxxxxxxx [mailto:basavaraj.puttagangaiah@xxxxxxxxx]
Sent: Sunday, April 02, 2006 11:05 PM
To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: [reSIProcate] problem with In-Dialog SUBSCRIBE(Re-posting )

 

Hi All

 I am reposting my old question…any help will be appreciated

I am using SUBSCRIBE/NOTIFY support provided by resiprocate.

It works fine for fresh subscriptions which will create new Dialog.

In this case if SUBSCRIBE is sent with an Event-package which is not

existing it clearly sends "489 Event Package Not Supported".

 

But if Dialog already exists and SUBSCRIBE is sent within the Dialog

assertion fails in ServerSubscription.cxx as follows.

 

ServerSubscription.cxx:198:

virtual void   resip::ServerSubscription::dispatch(const

resip::SipMessage&): Assertion `handler' failed.

 

Checking for supported Event Package is not made.

 

Why is the check not there like how it is for Out-of-Dialog SUBSCRIBE?

why assertion is provided instead of that?

 

 

Thank you

+Basu