[Home]

Summary:ASTERISK-22384: modifying transport configuration names results in non-functional transport after 'core reload'
Reporter:Rusty Newton (rnewton)Labels:
Date Opened:2013-08-24 19:18:03Date Closed:2013-08-30 14:52:15
Priority:MajorRegression?
Status:Closed/CompleteComponents:Resources/res_pjsip
Versions:12 Frequency of
Occurrence		Constant
Related
Issues:
is related toASTERISK-22382 modifying transport configuration results in a crash a few seconds after a 'core reload' (security_event_get_transport at res_pjsip/security_events.c)
Environment:SVN-branch-12-r397614Attachments:( 0) backtrace-threads9.txt
Description:This is another failure mode for ASTERISK-22382 and is likely related.

If it doesn't crash, then Asterisk just ignores all incoming SIP traffic.

Something bad happened to the transports!

Shutting down asterisk and restarting it results in the transport functioning fine.
Comments:By: Rusty Newton (rnewton) 2013-08-24 19:38:15.385-0500

Looks like instead of just leaving the transport config alone we try to reconfigure it but fail:
{noformat}
[Aug 24 19:36:43] VERBOSE[6775] config.c:   == Parsing '/etc/asterisk/pjsip.conf': Found
[Aug 24 19:36:43] DEBUG[6775] config.c: extract int from [0] in [0, 65535] gives [0](0)
[Aug 24 19:36:43] DEBUG[6775] config.c: extract int from [0] in [-2147483648, 2147483647] gives [0](0)
[Aug 24 19:36:43] DEBUG[6775] config.c: extract int from [1] in [-2147483648, 2147483647] gives [1](0)
[Aug 24 19:36:43] DEBUG[6775] config.c: extract int from [0] in [-2147483648, 2147483647] gives [0](0)
[Aug 24 19:36:43] ERROR[6775] res_pjsip/config_transport.c: Transport 'transport-udp1' could not be started: Unknown pjsip error 120098
[Aug 24 19:36:43] DEBUG[6775] res_sorcery_config.c: Could not create an object of type 'transport' with id 'transport-udp1' from configuration file 'pjsip.conf'
[Aug 24 19:36:43] DEBUG[6775] config.c: Parsing /etc/asterisk/pjsip.conf
[Aug 24 19:36:43] VERBOSE[6775] config.c:   == Parsing '/etc/asterisk/pjsip.conf': Found
[Aug 24 19:36:43] DEBUG[6775] config.c: extract int from [0] in [-2147483648, 2147483647] gives [0](0)
[Aug 24 19:36:43] DEBUG[6775] config.c: extract int from [1800] in [-2147483648, 2147483647] gives [1800](0)
[Aug 24 19:36:43] DEBUG[6775] config.c: extract int from [0] in [-2147483648, 2147483647] gives [0](0)
[Aug 24 19:36:43] DEBUG[6775] config.c: extract int from [0] in [-2147483648, 2147483647] gives [0](0)
[Aug 24 19:36:43] DEBUG[6775] config.c: extract int from [90] in [-2147483648, 2147483647] gives [90](0)
{noformat}