[asterisk-bugs] [JIRA] (ASTERISK-28960) bridge: System gets into state where bridge is terminated after joining
Joshua C. Colp (JIRA)
noreply at issues.asterisk.org
Mon Jun 29 05:11:25 CDT 2020
[ https://issues.asterisk.org/jira/browse/ASTERISK-28960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=251265#comment-251265 ]
Joshua C. Colp edited comment on ASTERISK-28960 at 6/29/20 5:11 AM:
--------------------------------------------------------------------
I would suggest adding some additional logging to the dialplan[1] to state who hung up in the situation. This will narrow down the potential area. As it is I'm not seeing anything standing out, except a lot of BYE requests coming in with a non-normal reason (Recovery on timer expiry) suddenly. You can see it by filtering using "sip.reason_cause_q850 == 102". There's a few at the start, but about 7000 packets in there is a lot. If this is what your trunk is - then I'd expect that channel to be hung up and things to terminate. That may be what is happening. In fact, in some cases Asterisk has already bridged things enough that the cause code is getting passed through to the remote side (not in all cases mind you, but some).
[1] https://wiki.asterisk.org/wiki/pages/viewpage.action?pageId=20185363
was (Author: jcolp):
I would suggest adding some additional logging to the dialplan[1] to state who hung up in the situation. This will narrow down the potential area. As it is I'm not seeing anything standing out, except a lot of BYE requests coming in with a non-normal reason (Recovery on timer expiry) suddenly. You can see it by filtering using "sip.reason_cause_q850 == 102". There's a few at the start, but about 7000 packets in there is a lot. If this is what you trunk is - then I'd expect that channel to be hung up and things to terminate. That may be what is happening. In fact, in some cases Asterisk has already bridged things enough that the cause code is getting passed through to the remote side (not in all cases mind you, but some).
[1] https://wiki.asterisk.org/wiki/pages/viewpage.action?pageId=20185363
> bridge: System gets into state where bridge is terminated after joining
> -----------------------------------------------------------------------
>
> Key: ASTERISK-28960
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-28960
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Bridges/bridge_simple
> Affects Versions: 16.10.0
> Environment: ubunut 18.04, docker asterisk 16.10
> Reporter: Robert Sutton
> Assignee: Robert Sutton
> Severity: Minor
> Labels: fax, webrtc
>
> system gets into state where bridges collapse within a few seconds
> calls kept flowing into the system, but bridges would collapse without error within a few seconds of starting.
> Seems to be happening about once a week.
> This particular system has only ever run 16.10
> I have a core dump from the running system and full logs including a period with debug set to 4
> below is a typical call flow while the system was in this state.
> {noformat}
> Jun 24 10:53:29 -- Executing [555555555 at routesv2-inbound:1] Set("PJSIP/trunk-00000fa4", "AGIEXITONHANGUP=yes") in new stack
> Jun 24 10:53:29 -- Executing [555555555 at routesv2-inbound:2] Set("PJSIP/trunk-00000fa4", "recovery-did=555555555") in new stack
> Jun 24 10:53:29 -- Executing [555555555 at routesv2-inbound:3] AGI("PJSIP/trunk-00000fa4", "agi://127.0.0.1/route?targ=555555555&ctx=Pre-Inbound") in new stack
> Jun 24 10:53:34 -- AGI Script Executing Application: (mixmonitor) Options: (/var/spool/asterisk/monitor/1592960009.5408-4444444444-3333333333-I-1.wav,,curl 'http://127.0.0.1:8080/rest/recordingMigration/migrate?guid=1592960014936-35584&apiKey=xxxxxxxxxxxx')
> Jun 24 10:53:34 == Begin MixMonitor Recording PJSIP/trunk-00000fa4
> Jun 24 10:53:34 -- Started music on hold, class 'queue17', on channel 'PJSIP/trunk-00000fa4'
> Jun 24 10:53:35 -- PJSIP/417-00000faa is ringing
> Jun 24 10:53:35 -- PJSIP/417-00000faa is ringing
> Jun 24 10:53:40 -- PJSIP/417-00000faa answered
> Jun 24 10:53:40 -- Executing [activity-agi at activity:1] Set("PJSIP/417-00000faa", "AGIEXITONHANGUP=yes") in new stack
> Jun 24 10:53:40 -- Executing [activity-agi at activity:2] AGI("PJSIP/417-00000faa", "agi://127.0.0.1/activityAgi") in new stack
> Jun 24 10:53:40 == Begin MixMonitor Recording PJSIP/trunk-00000fa4
> Jun 24 10:53:40 -- AGI Script Executing Application: (bridge) Options: (PJSIP/trunk-00000fa4,x)
> Jun 24 10:53:40 -- Stopped music on hold on PJSIP/trunk-00000fa4
> Jun 24 10:53:40 == Spawn extension (routesv2-inbound, 555555555, 3) exited non-zero on 'Surrogate/PJSIP/trunk-00000fa4'
> Jun 24 10:53:40 -- Channel PJSIP/trunk-00000fa4 joined 'simple_bridge' basic-bridge <67256011-e289-430d-bc1c-08b96c97811e>
> Jun 24 10:53:40 -- Channel PJSIP/417-00000faa joined 'simple_bridge' basic-bridge <67256011-e289-430d-bc1c-08b96c97811e>
> Jun 24 10:53:40 == Begin MixMonitor Recording PJSIP/trunk-00000fa4
> Jun 24 10:53:40 OK == End MixMonitor Recording PJSIP/trunk-00000fa4
> Jun 24 10:53:40 OK == End MixMonitor Recording PJSIP/trunk-00000fa4
> Jun 24 10:53:41 -- Channel PJSIP/trunk-00000fa4 left 'simple_bridge' basic-bridge <67256011-e289-430d-bc1c-08b96c97811e>
> Jun 24 10:53:41 -- Channel PJSIP/417-00000faa left 'simple_bridge' basic-bridge <67256011-e289-430d-bc1c-08b96c97811e>
> Jun 24 10:53:41 -- Manager 'njcontact' from 127.0.0.1, hanging up channel: PJSIP/417-00000faa
> Jun 24 10:53:41 == Spawn extension (activity, activity-agi, 2) exited non-zero on 'PJSIP/417-00000faa'
> Jun 24 10:53:42 OK == End MixMonitor Recording PJSIP/trunk-00000fa4
> {noformat}
> for future reference:
> {noformat}
> the issue started somewhere between 10:38 and 10:46
> debug set to level 4 at 10:56:08
> core dump triggered at 10:55:32
> system restart at 10:57:30 approx
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list