[reSIProcate] REFER without Expire
FrankYuan
frankyuan at emergent-netsolutions.com
Thu Jul 13 12:00:58 CDT 2006
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 at list.sipfoundry.org
>> [mailto:resiprocate-devel-bounces at list.sipfoundry.org] On Behalf Of
>> Niraj Roy
>> Sent: Thursday, July 13, 2006 8:28 AM
>> To: resiprocate-devel at list.sipfoundry.org
>> 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 at list.sipfoundry.org
>> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
>>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at list.sipfoundry.org
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20060713/c1588632/attachment.htm>
More information about the resiprocate-devel
mailing list