[asterisk-bugs] [JIRA] (ASTERISK-26685) SEGFAULT PJSIP using IPv6 and Transport ws, wss

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-26685:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

> SEGFAULT PJSIP using IPv6 and Transport ws,wss
> ----------------------------------------------
>
>                 Key: ASTERISK-26685
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26685
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 13.9.0, 13.13.1
>         Environment: WSS over IPv6 or IPv6 via WS through Stunnel
> Qualify is set to 30sec for endpoint
>            Reporter: Michael Balen
>
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  0xb765ca3d in pjsip_transport_get_flag_from_type (type=139) at ../src/pjsip/sip_transport.c:337
> 337<--->    return get_tpname(type)->flag;
> #1  0xb7619124 in pjsip_tpmgr_acquire_transport2 (mgr=0x9e2508c, type=139, remote=0xb682c7a4, addr_len=28, sel=0xb682c954, tdata=0xb682c694, tp=0xb682d014) at ../src/pjsip/sip_transport.c:1992
>         flag = 16
>         remote_addr = 0xb6800040
>         key = {type = 139, rem_addr = {addr = {sa_family = 10}, ipv4 = {sin_family = 10, sin_port = 31686, sin_addr = {s_addr = 0}, sin_zero = " \002^r\203h", <incomplete sequence \374>}, ipv6 =
>         key_len = 32
>         transport = 0x0
>         factory = 0xb6e1a106 <__GI_inet_pton+182>
>         status = 2816
> #2  0xb7612377 in pjsip_endpt_acquire_transport2 (endpt=0x940fa4c, type=139, remote=0xb682c7a4, addr_len=28, sel=0xb682c954, tdata=0xb682c694, transport=0xb682d014) at ../src/pjsip/sip_endpoint.
> When register via ws or wss @asterisk with jssip-0.3 segfault occurs. 
> After that asterisk crash aprox 30 sec after next start with the same segfault in line 337 (without connecting anymore or anything). 
> I think it want to test the reachablity of the astdb entries because of qualify. 
> To make asterisk run again, I had to delete the astdb.sqlite file manually.



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