[asterisk-bugs] [JIRA] (ASTERISK-22384) modifying transport configuration names results in non-functional transport after 'core reload'

Rusty Newton (JIRA) noreply at issues.asterisk.org
Sat Aug 24 19:39:03 CDT 2013


    [ https://issues.asterisk.org/jira/browse/ASTERISK-22384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209568#comment-209568 ] 

Rusty Newton commented on ASTERISK-22384:
-----------------------------------------

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}
                
> modifying transport configuration names results in non-functional transport after 'core reload'
> -----------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-22384
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22384
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 12
>         Environment: SVN-branch-12-r397614
>            Reporter: Rusty Newton
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list