[asterisk-bugs] [JIRA] (ASTERISK-25688) Problem calling to a pjsip trunk

Asterisk Team (JIRA) noreply at issues.asterisk.org
Tue Jan 12 05:32:33 CST 2016


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

Asterisk Team commented on ASTERISK-25688:
------------------------------------------

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

> Problem calling to a pjsip trunk
> --------------------------------
>
>                 Key: ASTERISK-25688
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25688
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 13.6.0
>         Environment: Asterisk 13.6.0 (tested in Asterisk 13.7.0 rc2 too), Ubuntu 14.04.3 LTS, Linux rtc 4.1.5-x86_64-linode61 #7 SMP Mon Aug 24 13:46:31 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux
>            Reporter: Marcelo Terres
>
> When I try to call to another Asterisk via pjsip trunk, Asterisk crashs:
>     -- Executing [407 at ramais:2] Progress("PJSIP/10-00000000", "") in new stack
>     -- Executing [407 at ramais:3] Answer("PJSIP/10-00000000", "") in new stack
>     -- Executing [407 at ramais:4] Dial("PJSIP/10-00000000", "PJSIP/407 at asterisk,30") in new stack
>     -- Called PJSIP/407 at asterisk
>        > 0x7f166001e6b0 -- Probation passed - setting RTP source address to 177.27.46.125:4000
>     -- PJSIP/10-00000000 requested media update control 26, passing it to PJSIP/asterisk-00000001
>        > 0x7f166001e6b0 -- Probation passed - setting RTP source address to 177.27.46.125:4000
>     -- PJSIP/asterisk-00000001 answered PJSIP/10-00000000
>     -- Channel PJSIP/asterisk-00000001 joined 'simple_bridge' basic-bridge <ee50b922-2431-4571-9627-33a3a6d43921>
>     -- Channel PJSIP/10-00000000 joined 'simple_bridge' basic-bridge <ee50b922-2431-4571-9627-33a3a6d43921>
>        > Bridge ee50b922-2431-4571-9627-33a3a6d43921: switching from simple_bridge technology to native_rtp
>        > Remotely bridged 'PJSIP/10-00000000' and 'PJSIP/asterisk-00000001' - media will flow directly between them
>        > Remotely bridged 'PJSIP/10-00000000' and 'PJSIP/asterisk-00000001' - media will flow directly between them
> asterisk: symbol lookup error: /usr/lib/asterisk/modules/res_pjsip_session.so: undefined symbol: pj_timer_entry_running
> It is the same problem reported in this URL: http://stackoverflow.com/questions/34287633/asterisk-symbol-lookup-error-res-pjsip-session-so-undefined-symbol-pj-timer-ent



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



More information about the asterisk-bugs mailing list