| Summary: | ASTERISK-24336: PJSIP timer_min_se value under 90 causes crash | ||
| Reporter: | Leon Rowland (zogot) | Labels: | |
| Date Opened: | 2014-09-17 07:43:44 | Date Closed: | 2014-11-15 12:29:17.000-0600 |
| Priority: | Critical | Regression? | |
| Status: | Closed/Complete | Components: | pjproject/pjsip Resources/res_pjsip |
| Versions: | 12.5.0 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | CentOS 6.5 Asterisk 12 from the Digium Repository | Attachments: | |
| Description: | Following the PJSIP Realtime Configuration page (https://wiki.asterisk.org/wiki/display/AST/Setting+up+PJSIP+Realtime) I came across a crash that happens when in the ps_endpoints table the column timer_min_se was below 90.
The crash showed the following message when I attempted to call between 101 and 102 When changing the value to 91 the call happened correctly. Asterisk Ready. *CLI> -- Removed contact 'sip:101@172.17.2.60:51177;ob' from AOR '101' due to request -- Added contact 'sip:101@172.17.2.60:51177;ob' to AOR '101' with expiration of 300 seconds -- Removed contact 'sip:102@172.17.2.60:51177;ob' from AOR '102' due to request -- Added contact 'sip:102@172.17.2.60:51177;ob' to AOR '102' with expiration of 300 seconds asterisk: ../src/pjsip-ua/sip_timer.c:587: pjsip_timer_init_session: Assertion `setting->min_se >= 90' failed. | ||
| Comments: | By: Rusty Newton (rnewton) 2014-09-18 09:49:15.485-0500 [~zogot] Please follow the instructions for [Getting a Backtrace|https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace] on the wiki. Specifically the part about getting a backtrace for a crash. Make sure to use the compiler flags mentioned in the article. | ||