RE: [reSIProcate] REFER without Expire

["Matthias Moetje - TERASENS GmbH" <moetje@xxxxxxxxxxxx>]

Why not completely remove the tar ball? It seems this is

continuously confusing people...

Best regards,

Matthias Moetje

 

---

From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of FrankYuan
Sent: Thursday, July 13, 2006 7:01 PM
To: Scott Godin
Cc: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [reSIProcate] REFER without Expire

The last  resiprocate tar ball had been released more than a year ago, and when will the latest tar ball be released to prevent these kinds of problem?

Thanks

F Yuan

Scott Godin wrote:

Have you tried using the SVN head version?  Does this problem still
exist?

  

-----Original Message-----
From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
Niraj Roy
Sent: Thursday, July 13, 2006 8:28 AM
To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: [reSIProcate] REFER without Expire


 Hi,
	I have a sip client uses resiprocate-0.9.0-5019.
	When REFER message is sent to my application without Expire
header, resiprocate stack sends 400 BAD request.
	While I am also getting onRefer Call back.
	As per the RFC 3515 Expires in the REFER message is an optional.

	Can anybody shade some light on it how can I come out of this
    

and
  

have proper behavior?

Regards,
Niraj









_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
    

_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel