Hi Patrick,
First, you can control the timeout in a per-request fashion, by setting
from script some TM variables:
- in 1.11 -
http://www.opensips.org/html/docs/modules/1.11.x/tm.html#id295747
- in 1.10 -
http://www.opensips.org/html/docs/modules/1.10.x/tm.html#id294137
And no, 4320 is not supported, I will look into it.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 16.09.2014 20:45, Patrick Wakano wrote:
Hello list,
I have a scenario with mobile user - Opensips - Asterisk and I was
having some trouble with Options requests sent from Asterisk to mobile
user.
Due to a high value of the qualify timeout on Asterisk a and low value
of the fr_timeout from tm module, Options requests sent to unreachable
users were being answered with a 408 by Opensips and so Asterisk was
considering the user reachable when in fact they weren't.
After some debug I discovered that the low fr_timeout was inducing a
fast 408 reply back to Asterisk, and since its qualify mechanism
accepts *any* reply as valid, then the user remained reachable until
the registration expired.
Problem was solved but during my research I found the RFC4320
(http://www.ietf.org/rfc/rfc4320.txt) that deals with this situation.
According to it, I think that Opensips should not send this 408 for
non-invites. Not sure if Opensips should implement anything related
but I thought it was worth the advice!
Regards,
Patrick
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
