[asterisk-bugs] [JIRA] (ASTERISK-24996) chan_pjsip: Creating Channel Causes Asterisk to Crash When Duplicate AOR Sections Exist in pjsip.conf

[Ashley Sanders (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-24996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ashley Sanders closed ASTERISK-24996.
-------------------------------------

    Resolution: Fixed

Modified the current loading strategy of the pjsip configuration. If
duplicate sections (e.g. sections containing the same [id/type]) are defined in
[pjsip.conf], the loader will consider the configuration for the given type as
invalid when the duplicate section is encountered. The entire configuration
(including what was previously loaded) for the duplicate [id/type] sections
will be rejected and destroyed, an error message is logged and the load
processing for the given stops.

> chan_pjsip: Creating Channel Causes Asterisk to Crash When Duplicate AOR Sections Exist in pjsip.conf
> -----------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-24996
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24996
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip, Core/Sorcery
>            Reporter: Ashley Sanders
>            Assignee: Ashley Sanders
>         Attachments: pjsip.a.conf, pjsip.b.conf
>
>
> *This seems to only be relevant for outbound registrations.*
> # On Asterisk instance \[A\]: The 'pjsip.conf' file contains definitions for an endpoint, aor, auth, and registration type, all named 'siptrunk'. The aor and registration sections are configured to point to address of  Asterisk instance \[B\].
> # On Asterisk instance \[B\]: The 'pjsip.conf' file contains definitions for an endpoint, aor, auth, and registration type, all named 'siptrunk'. The aor and registration sections are configured to point to address of Asterisk instance \[A\].
> # On Asterisk instance \[A\]: duplicate the siptrunk sections in pjsip.conf, so now there are two identical sections for each type (even though I am fairly certain it is the AOR section that is causing the grief.)
> # Define an extension '5000' in the dialplan of both Asterisk instances to play hello-world:
> {quote}
> {{exten => 5000,1,NoOp()}}
> {{same => n,Ringing()}}
> {{same => n,Answer(5000)}}
> {{same => n,Playback(hello-world)}}
> {{same => n,Hangup()}}
> {quote}
> # After both instances of Asterisk are up and running, on the Asterisk instance \[A\], originate a channel using the Asterisk CLI:
> {quote}{{originate pjsip/5000 at siptrunk application echo}}{quote}
> # Observe a crash.
> *The peer asterisk system, Asterisk instance \[B\], can run above command successfully.*
> I have attached a sample config for Asterisk instances A and B for the above scenario.



--
This message was sent by Atlassian JIRA
(v6.2#6252)