[asterisk-bugs] [JIRA] (ASTERISK-22580) Asterisk 12 crashes

[Rusty Newton (JIRA)]

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

Rusty Newton updated ASTERISK-22580:
------------------------------------

    Assignee: Private Name
      Status: Waiting for Feedback  (was: Triage)

Please read through the guidelines here: https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

Please attach a backtrace to this issue (More Actions > Attach Files>
Follow these instructions very closely: https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace

Please attach the full DEBUG log, being sure that res_pjsip__logger.so is loaded to the issue using "Attach Files" as well. https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information






                
> Asterisk 12 crashes
> -------------------
>
>                 Key: ASTERISK-22580
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22580
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip
>    Affects Versions: 12.0.0-alpha1
>         Environment: debian 64
>            Reporter: Private Name
>            Assignee: Private Name
>
> Please read, it crashes at the last line
> [Sep 24 03:21:56] DEBUG[18280]: pjsip:0 <?>:       tsx0xf9d388 ...State changed from Trying to Proceeding, event=TX_MSG
> [Sep 24 03:21:56] DEBUG[18280]: pjsip:0 <?>:       dlg0xf9e1f8 ....Transaction tsx0xf9d388 state changed to Proceeding
> [Sep 24 03:21:56] DEBUG[18280]: res_pjsip_session.c:1664 __print_debug_details: Function session_inv_on_state_changed called on event TSX_STATE
> [Sep 24 03:21:56] DEBUG[18280]: res_pjsip_session.c:1675 __print_debug_details: The state change pertains to the session with afe8e926-9ceb-4f3c-a93e-ce848e1a8256
> [Sep 24 03:21:56] DEBUG[18280]: res_pjsip_session.c:1678 __print_debug_details: The inv session still has an invite_tsx (0xf9d388)
> [Sep 24 03:21:56] DEBUG[18280]: res_pjsip_session.c:1687 __print_debug_details: There is no transaction involved in this state change
> [Sep 24 03:21:56] DEBUG[18280]: res_pjsip_session.c:1689 __print_debug_details: The current inv state is INCOMING
> [Sep 24 03:21:56] DEBUG[18280]: res_pjsip_session.c:1815 session_inv_on_state_changed: Source of transaction state change is TX_MSG
> [Sep 24 03:21:56] DEBUG[18280]: res_pjsip_session.c:1770 handle_outgoing: Sending response
> [Sep 24 03:21:56] DEBUG[18280]: res_pjsip_session.c:1758 handle_outgoing_response: Method is INVITE, Response is 100 Trying
> [Sep 24 03:21:56] DEBUG[18280]: res_pjsip_session.c:1664 __print_debug_details: Function session_inv_on_tsx_state_changed called on event TSX_STATE
> [Sep 24 03:21:56] DEBUG[18280]: res_pjsip_session.c:1675 __print_debug_details: The state change pertains to the session with afe8e926-9ceb-4f3c-a93e-ce848e1a8256
> [Sep 24 03:21:56] DEBUG[18280]: res_pjsip_session.c:1678 __print_debug_details: The inv session still has an invite_tsx (0xf9d388)
> [Sep 24 03:21:56] DEBUG[18280]: res_pjsip_session.c:1683 __print_debug_details: The transaction involved in this state change is 0xf9d388
> [Sep 24 03:21:56] DEBUG[18280]: res_pjsip_session.c:1684 __print_debug_details: The current transaction state is Proceeding
> [Sep 24 03:21:56] DEBUG[18280]: res_pjsip_session.c:1685 __print_debug_details: The transaction state change event is TX_MSG
> [Sep 24 03:21:56] DEBUG[18280]: res_pjsip_session.c:1689 __print_debug_details: The current inv state is INCOMING
> [Sep 24 03:21:56] DEBUG[18280]: res_pjsip_session.c:1699 handle_incoming_request: Method is INVITE
> [Sep 24 03:21:56] DEBUG[18280]: format_pref.c:339 ast_codec_choose: Could not find preferred codec - Going for the best codec
> [Sep 24 03:21:56] WARNING[18280]: channel.c:830 ast_best_codec: Don't know any of (nothing) formats
> [Sep 24 03:21:56] ERROR[18280]: astobj2.c:156 INTERNAL_OBJ: user_data is NULL

--
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