Handling 423 Registration Too Brief in PJSUA

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

 



Adrian,
I do not say it is a bug. PJSIP is a great stack and really nothing 
stops me from reading headers from responses.
I just want to ask how. I would like to get the value and not to 
interfere with PJSUA. Any ideas?
Thanks
- Vali


Dne 13.1.2010 18:16, Adrian Georgescu napsal(a):
> Nobody stops you to make your application read a header in the response
> and then register again with the expected expires value. Pjsip gives you
> all the control, you must do some work on your application side to
> achieve what you want.
>
> So this is not a bug in PJSIP, it is logic you must build explicitly
> into your client.
>
> Adrian
>
> On Jan 13, 2010, at 5:46 PM, Tom?? Valenta wrote:
>
>> Hi Adrian,
>> thanks for the brief answer. Unfortunately I am not allowed to alter
>> the server's configuration. I am using PJSUA-lib in an IVR application
>> which must work in any environment without reconfiguring the servers.
>> Thus it should be as robust as possible.
>> Cheers
>> - Vali
>>
>>
>> Dne 13.1.2010 17:27, Adrian Georgescu napsal(a):
>>> If the server would simply return another Expire value in the 200OK the
>>> client will obey to it. Can the server do this?
>>>
>>> Adrian
>>>
>>> On Jan 13, 2010, at 5:17 PM, Tom?? Valenta wrote:
>>>
>>>> Hi,
>>>>
>>>> I came across an issue with Alcatel gateway. It was discussed in
>>>> thread "RX msg 423 Interval Too Brief":
>>>> http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/2008-January/001198.html
>>>>
>>>>
>>>>
>>>> Shortly: Client (PJSUA) sends REGISTER request with Expires header,
>>>> but the server answers 423 Registration Too Brief with Min-Expires
>>>> header. As a consequence client should send new REGISTER request with
>>>> new value of Expires, but PJSUA neither does so itself nor exposes the
>>>> Min-Expires value to the user. I am writing about version 1.0.x and do
>>>> not know how it works in 1.x branch.
>>>>
>>>> Can you suggest a clean solution of the situation while going deep as
>>>> little as possible? Utilizing pjsua_internal.h is okay for me.
>>>>
>>>> Thanks
>>>> - Vali
>>>>
>>>> _______________________________________________
>>>> 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
>
>



[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