[FREEPBX-19618] When Alert Info exists, device is CHANUNAVAIL - Sangoma Issue Tracker

XML

Word

Printable

Details

Type: Bug
Status: Closed
Priority: Minor
Resolution: Works For Me
Affects Version/s: 14
Fix Version/s: None
Component/s: Inbound Routes
Labels:
None

ToDo:

Asterisk Version:
13.21.1
Distro Version:
14.0.7.3
Distro:
FreePBX Distro

Description

Since the last update, any inbound route that contains alert info results in the extension / device reporting as CHANUNAVAIL. Removing the alert info, resolves the issue and calls flow normally.

Alert Into value has always been: ;info=ring1 (or ;info=ring2)

SINCE LAST UPDATE:


[2019-03-09 11:29:53] VERBOSE[4113][C-00054751] app_stack.c: SIP/123456789-0007748b Internal Gosub(func-apply-sipheaders,s,1) start
[2019-03-09 11:29:53] VERBOSE[4113][C-00054751] pbx.c: Executing [s@func-apply-sipheaders:1] NoOp("SIP/123456789-0007748b", "Applying SIP Headers to channel SIP/123456789-0007748b") in new stack
[2019-03-09 11:29:53] VERBOSE[4113][C-00054751] pbx.c: Executing [s@func-apply-sipheaders:2] Set("SIP/123456789-0007748b", "TECH=SIP") in new stack
[2019-03-09 11:29:53] VERBOSE[4113][C-00054751] pbx.c: Executing [s@func-apply-sipheaders:3] Set("SIP/123456789-0007748b", "SIPHEADERKEYS=Alert-Info") in new stack
[2019-03-09 11:29:53] VERBOSE[4113][C-00054751] pbx.c: Executing [s@func-apply-sipheaders:4] While("SIP/123456789-0007748b", "1") in new stack
[2019-03-09 11:29:53] VERBOSE[4113][C-00054751] pbx.c: Executing [s@func-apply-sipheaders:5] Set("SIP/123456789-0007748b", "sipheader=;info=ring2") in new stack
[2019-03-09 11:29:53] VERBOSE[4113][C-00054751] pbx.c: Executing [s@func-apply-sipheaders:6] ExecIf("SIP/123456789-0007748b", "0?SIPRemoveHeader(Alert-Info:)") in new stack
[2019-03-09 11:29:53] VERBOSE[4113][C-00054751] pbx.c: Executing [s@func-apply-sipheaders:7] ExecIf("SIP/123456789-0007748b", "1?Set(sipheader=<http://127.0.0.1>;info=;info=ring2)") in new stack
[2019-03-09 11:29:53] VERBOSE[4113][C-00054751] pbx.c: Executing [s@func-apply-sipheaders:8] ExecIf("SIP/123456789-0007748b", "1?SIPAddHeader(Alert-Info:<http://127.0.0.1>;info=;info=ring2)") in new stack
[2019-03-09 11:29:53] VERBOSE[4113][C-00054751] pbx.c: Executing [s@func-apply-sipheaders:9] EndWhile("SIP/123456789-0007748b", "") in new stack
[2019-03-09 11:29:53] VERBOSE[4113][C-00054751] pbx.c: Executing [s@func-apply-sipheaders:4] While("SIP/123456789-0007748b", "0") in new stack
[2019-03-09 11:29:53] VERBOSE[4113][C-00054751] pbx.c: Executing [s@func-apply-sipheaders:10] Return("SIP/123456789-0007748b", "") in new stack
[2019-03-09 11:29:53] VERBOSE[4113][C-00054751] app_stack.c: Spawn extension (from-internal, 9055551212, 1) exited non-zero on 'SIP/123456789-0007748b'
[2019-03-09 11:29:53] VERBOSE[4113][C-00054751] app_stack.c: SIP/123456789-0007748b Internal Gosub(func-apply-sipheaders,s,1) complete GOSUB_RETVAL=
[2019-03-09 11:29:53] VERBOSE[4113][C-00054751] app_dial.c: Called SIP/123456789
[2019-03-09 11:29:53] VERBOSE[4113][C-00054751] app_dial.c: Connected line update to SIP/InboundCall_1_121-0007748a prevented.
[2019-03-09 11:30:00] VERBOSE[4113][C-00054751] app_dial.c: Everyone is busy/congested at this time (1:0/0/1)

PRIOR TO LAST UPDATE:


[2019-03-04 17:36:59] VERBOSE[12746][C-0002c736] app_stack.c: SIP/123456789-0004b7ae Internal Gosub(func-apply-sipheaders,s,1) start
[2019-03-04 17:36:59] VERBOSE[12746][C-0002c736] pbx.c: Executing [s@func-apply-sipheaders:1] NoOp("SIP/123456789-0004b7ae", "Applying SIP Headers to channel ") in new stack
[2019-03-04 17:36:59] VERBOSE[12746][C-0002c736] pbx.c: Executing [s@func-apply-sipheaders:2] Set("SIP/123456789-0004b7ae", "SIPHEADERKEYS=Alert-Info") in new stack
[2019-03-04 17:36:59] VERBOSE[12746][C-0002c736] pbx.c: Executing [s@func-apply-sipheaders:3] ExecIf("SIP/123456789-0004b7ae", "0?Set(Rheader=1)") in new stack
[2019-03-04 17:36:59] VERBOSE[12746][C-0002c736] pbx.c: Executing [s@func-apply-sipheaders:4] While("SIP/123456789-0004b7ae", "1") in new stack
[2019-03-04 17:36:59] VERBOSE[12746][C-0002c736] pbx.c: Executing [s@func-apply-sipheaders:5] Set("SIP/123456789-0004b7ae", "sipheader=;info=ring2") in new stack
[2019-03-04 17:36:59] VERBOSE[12746][C-0002c736] pbx.c: Executing [s@func-apply-sipheaders:6] SIPAddHeader("SIP/123456789-0004b7ae", "Alert-Info: ;info=ring2") in new stack
[2019-03-04 17:36:59] VERBOSE[12746][C-0002c736] pbx.c: Executing [s@func-apply-sipheaders:7] EndWhile("SIP/123456789-0004b7ae", "") in new stack
[2019-03-04 17:36:59] VERBOSE[12746][C-0002c736] pbx.c: Executing [s@func-apply-sipheaders:4] While("SIP/123456789-0004b7ae", "0") in new stack
[2019-03-04 17:36:59] VERBOSE[12746][C-0002c736] pbx.c: Executing [s@func-apply-sipheaders:8] ExecIf("SIP/123456789-0004b7ae", "0?SIPRemoveHeader(Alert-Info:)") in new stack
[2019-03-04 17:36:59] VERBOSE[12746][C-0002c736] pbx.c: Executing [s@func-apply-sipheaders:9] Return("SIP/123456789-0004b7ae", "") in new stack
[2019-03-04 17:36:59] VERBOSE[12746][C-0002c736] app_stack.c: Spawn extension (from-internal, 9055551212, 1) exited non-zero on 'SIP/123456789-0004b7ae'
[2019-03-04 17:36:59] VERBOSE[12746][C-0002c736] app_stack.c: SIP/123456789-0004b7ae Internal Gosub(func-apply-sipheaders,s,1) complete GOSUB_RETVAL=
[2019-03-04 17:36:59] VERBOSE[12746][C-0002c736] app_dial.c: Called SIP/123456789
[2019-03-04 17:36:59] VERBOSE[12746][C-0002c736] app_dial.c: Connected line update to SIP/InboundCall_2_38-0004b7ad prevented.
[2019-03-04 17:36:59] VERBOSE[12746][C-0002c736] app_dial.c: SIP/123456789-0004b7ae is ringing
[2019-03-04 17:37:08] VERBOSE[12746][C-0002c736] app_dial.c: Connected line update to SIP/InboundCall_2_38-0004b7ad prevented.
[2019-03-04 17:37:08] VERBOSE[12746][C-0002c736] app_dial.c: SIP/123456789-0004b7ae answered SIP/InboundCall_2_38-0004b7ad

Gliffy Diagrams

Attachments

Activity

People

Assignee:

Unassigned

Reporter:

D Hunter

Votes:

0 Vote for this issue

Watchers:

3 Start watching this issue

Dates

Created:

09/Mar/19 4:51 PM

Updated:

12/Mar/19 9:36 PM

Resolved:

11/Mar/19 8:26 PM

NextupJiraPlusStatus

Error rendering 'slack.nextup.jira:nextup-jira-plus-status'. Please contact your Jira administrators.