Session Timer Too Small

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dear Nanang
I tested Session timer fix with revision svn 2961 but still having same as
before. Wireshark trace attached.(forget to attach file now with this one)
Thanks and regards
Bharat Yadav

-----Original Message-----
From: pjsip-bounces@xxxxxxxxxxxxxxx [mailto:pjsip-bounces at lists.pjsip.org]
On Behalf Of Nanang Izzuddin
Sent: Thursday, October 15, 2009 10:15 AM
To: pjsip list
Subject: Re: Session Timer Too Small

Hi Bharat,

Just want to update you regarding this issue. There was update on
ticket #954, i.e: rev 2933-2934, to handle this case.

Please drop in any feedback once you've got a chance to test it, thanks.

BR,
nanang


On Fri, Aug 21, 2009 at 10:28 PM, Nanang Izzuddin <nanang at pjsip.org> wrote:
> Hi Bharat,
>
> The log does help. The UAS said in its 422/INVITE response that Min-SE
> is 5400, but then UAS sent SE 3600 in its 200/INVITE response. The
> symbian_ua/PJSIP doesn't like it when the 200/INVITE response contains
> Session-expires header with value less than Min-SE header in INVITE
> request, so BYE was sent.
>
> The faulty UA here is the UAS, take a look at RFC 4028 Section 9:
> ===
> If the UAS wishes to accept the request, it copies the value of the
> Session-Expires header field from the request into the 2xx response.
> The UAS response MAY reduce its value but MUST NOT set it to a
> duration lower than the value in the Min-SE header field in the
> request, if it is present;
> ===
>
> However, I've just created ticket #954 (Session Timer issues) and
> considered to put this case in.
>
> Thanks for the report,
> nanang
>
>
> On Fri, Aug 21, 2009 at 7:04 PM, Bharat
> Yadav<bharat.yadav at axisconvergence.com> wrote:
>> Dear Nanang
>> Here is trace logs of symbian_ua and Wireshark.
>> Thanks and regards
>> Bharat
>>
>> -----Original Message-----
>> From: pjsip-bounces@xxxxxxxxxxxxxxx
[mailto:pjsip-bounces at lists.pjsip.org]
>> On Behalf Of Bharat Yadav
>> Sent: Friday, August 21, 2009 5:10 PM
>> To: 'pjsip list'
>> Subject: Re: Session Timer Too Small
>>
>> Dear Nanang
>> Thanks for quick reply. First of all when I want to make call with G711
it
>> will ok and call get connected and I hangup the call gracefully, but if I
>> only use G729 for that case when call made at the stage of Ringing if
>> recipient accept the call it shows "Session Timer Too small" and get
hanged
>> with "normal call clearing" message. From the log end with will send the
log
>> file within as while.
>> Thanks
>> Bharat
>>
>> -----Original Message-----
>> From: pjsip-bounces@xxxxxxxxxxxxxxx
[mailto:pjsip-bounces at lists.pjsip.org]
>> On Behalf Of Nanang Izzuddin
>> Sent: Friday, August 21, 2009 4:52 PM
>> To: pjsip list
>> Subject: Re: Session Timer Too Small
>>
>> Hi Bharat,
>>
>> I don't think I get this right. There shouldn't be a problem when a
>> caller gets 422 response (session timer too small), it will just
>> re-try to send INVITE with acceptable session interval as specified by
>> the 422 response automatically (no config setting to be set/modified
>> here).
>>
>> So, did you experience other than the above scenario? Log file or
>> clear reproducing steps could be helpful.
>>
>> Regards,
>> nanang
>>
>>
>> On Fri, Aug 21, 2009 at 5:24 PM, Bharat
>> Yadav<bharat.yadav at axisconvergence.com> wrote:
>>> Hi all
>>>
>>> I am using 1.4 trunk and trying to implement VAS for FP1 using
symbian_ua
>>> all are fine for Ringing stage when call connect to GSM phone using G729
>> it
>>> show "Session Timer Too Small", how should and where I define session
time
>>> into ua.cpp, I checked into pjsua_app.c but failed to follow steps for
>>> session timer expression. Please help.
>>>
>>> Thanks
>>>
>>> Bharat
>>>
>>> _______________________________________________
>>> Visit our blog: http://blog.pjsip.org
>>>
>>> pjsip mailing list
>>> pjsip at lists.pjsip.org
>>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>>>
>>>
>>
>> _______________________________________________
>> Visit our blog: http://blog.pjsip.org
>>
>> pjsip mailing list
>> pjsip at lists.pjsip.org
>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>>
>>
>>
>>
>>
>> _______________________________________________
>> Visit our blog: http://blog.pjsip.org
>>
>> pjsip mailing list
>> pjsip at lists.pjsip.org
>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>>
>>
>> _______________________________________________
>> Visit our blog: http://blog.pjsip.org
>>
>> pjsip mailing list
>> pjsip at lists.pjsip.org
>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>>
>>
>

_______________________________________________
Visit our blog: http://blog.pjsip.org

pjsip mailing list
pjsip at lists.pjsip.org
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 23Oct09-at-11.30am.pcap
Type: application/octet-stream
Size: 38310 bytes
Desc: not available
URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20091023/66f59eee/attachment-0001.pcap>


[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux