PJSIP – Sessions-timers Support Not Working On 13.X
Hi guys i was trying to get working sessions-timer over PJSIP channel i was trying to see what is supported or not about this features on the new pjsip channel since chan_sip was kind of flexible on this , at the moment since wiki says pjsip support 4 modes of operation (forced, no, required, yes) but if i try to change any of the timers parameters (timers, timers_min_se or timers_sess_expiries) the pjsip channel doesn’t load the endpoint or even not load the well the channel this happens on 13.1, 13.2 and 13.3.
should i enable something different of normal variables on pjsip.conf ?
Thanks Javier Riveros.
—
4 thoughts on - PJSIP – Sessions-timers Support Not Working On 13.X
Gosmac wrote:
What is the exact configuration of the endpoint, and what is output on the CLI? As well – you have one of the parameters incorrect above. It’s timers_sess_expires, not timers_sess_expiries. If that is incorrect in your configuration this would be considered invalid and thus it would not load.
Cheers,
—
Joshua Colp Digium, Inc. | Senior Software Developer
445 Jan Davis Drive NW – Huntsville, AL 35806 – US
Check us out at: http://www.digium.com & http://www.asterisk.org
—
Hi Josua, Sorry for writing wrong the parameter but i just copy paste the examples on pjsip.conf it wasn’t a “typo” error of timers parameters, i have an error on global tag and can’t load the timers I was getting this :
[Apr 29 17:21:49] WARNING[16144]: config.c:1796 process_text_line: parse error: No category context for line 631 of /etc/asterisk/pjsip.conf
after fix global issue
[105]
type=aor max_contacts=1
remove_existing=yes
[105]
type=auth auth_type=userpass password=XXXXXXXX
username=105
[105]
type=endpoint disallow=all allow=ulaw allow=alaw context=video-test auth=105
aors=105
direct_media=no force_rport=yes rewrite_contact=yes transport=transport-udp-nat media_encryption=no ice_support=no timers_min_se=90 ; Minimum session timers expiration period (default:; “90”)
timers=required ; Session timers for SIP packets (default: “yes”)
timers_sess_expires=3600 ; Maximum session timer expiration period
now get things working and i could see how this behave.
Thanks Regards
—
Ok , digging more into this i could see that (timers=no) and (timers=forced) not work asterisk not pay attention to this options when is reloaded cli not say anything and when the pjsip show endpoint it show always timers=yes when (timers=no) and (timers=forced) to that endpoint.
I wonder to force asterisk to refresh the session in some cases when is needed .
pjsip is able to refresh the session ?
Cheers
—
Gosmac wrote:
There was an issue[1] where stuff did not work/was inconsistent. This has been resolved in git and will be in the next release.
Cheers,
[1] https://issues.asterisk.org/jira/browse/ASTERISK-24910