Uploaded image for project: 'FreePBX'
  1. FreePBX
  2. FREEPBX-11246

Class of service fails on caller id with * in it

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Out of Date
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Asterisk Version:
      13.6.0
    • Distro Version:
      10.13.66-6
    • Distro:
      FreePBX Distro

      Description

      Have a module (based on wake-up calls) that was working fine up until a couple of days ago. I checked /var/logs/asterisk/full and see that the failure is being caused by the COS module failing to parse the caller ID value set by the AGI script which contains an asterisk (always has... *67). Temporarily changing the caller ID value to eliminate the asterisk allows the call to go through as normal.

      Cheers,
      Mike

      [2016-01-06 20:22:00] VERBOSE[16786][C-000012ed] pbx.c: Goto (macro-user-callerid,s,29)[2016-01-06 20:22:00] VERBOSE[16786][C-000012ed] pbx.c: Executing [s@macro-user-callerid:29] Set("Local/310@from-internal-0000002e;2", "CALLERID(number)=*67") in new stack[2016-01-06 20:22:00] VERBOSE[16786][C-000012ed] pbx.c: Executing [s@macro-user-callerid:30] Set("Local/310@from-internal-0000002e;2", "CALLERID(name)=Announcement") in new stack[2016-01-06 20:22:00] VERBOSE[16786][C-000012ed] pbx.c: Executing [s@macro-user-callerid:31] Set("Local/310@from-internal-0000002e;2", "CDR(cnum)=*67") in new stack[2016-01-06 20:22:00] VERBOSE[16786][C-000012ed] pbx.c: Executing [s@macro-user-callerid:32] Set("Local/310@from-internal-0000002e;2", "CDR(cnam)=Announcement") in new stack[2016-01-06 20:22:00] VERBOSE[16786][C-000012ed] pbx.c: Executing [s@macro-user-callerid:33] Set("Local/310@from-internal-0000002e;2", "CHANNEL(language)=en") in new stack[2016-01-06 20:22:00] VERBOSE[16786][C-000012ed] pbx.c: Executing [s@macro-user-callerid:34] GosubIf("Local/310@from-internal-0000002e;2", "1?app-check-classofservce,s,1()") in new stack[2016-01-06 20:22:00] VERBOSE[16786][C-000012ed] pbx.c: Executing [s@app-check-classofservce:1] NoOp("Local/310@from-internal-0000002e;2", "Starting COS Check") in new stack[2016-01-06 20:22:00] VERBOSE[16786][C-000012ed] pbx.c: Executing [s@app-check-classofservce:2] AGI("Local/310@from-internal-0000002e;2", "cos.agi") in new stack[2016-01-06 20:22:00] VERBOSE[16786][C-000012ed] res_agi.c: Launched AGI Script /var/lib/asterisk/agi-bin/cos.agi[2016-01-06 20:22:00] VERBOSE[16786][C-000012ed] res_agi.c: cos.agi: Starting Class Of Service checks[2016-01-06 20:22:00] VERBOSE[16786][C-000012ed] res_agi.c: cos.agi: CallerID not Parseable - received *67 - exiting with DENY[2016-01-06 20:22:00] VERBOSE[16786][C-000012ed] res_agi.c: AGI Script Executing Application: (Goto) Options: (macro-trunk-dial,barred,1)[2016-01-06 20:22:00] VERBOSE[16786][C-000012ed] pbx.c: Goto (macro-trunk-dial,barred,1)[2016-01-06 20:22:00] VERBOSE[16786][C-000012ed] res_agi.c: <Local/310@from-internal-0000002e;2>AGI Script cos.agi completed, returning 0[2016-01-06 20:22:00] WARNING[16786][C-000012ed] pbx.c: Channel 'Local/310@from-internal-0000002e;2' sent to invalid extension but no invalid handler: context,exten,priority=macro-trunk-dial,barred,2[2016-01-06 20:22:00] NOTICE[16784] pbx_spool.c: Call failed to go through, reason (0) Call Failure (not BUSY, and not NO_ANSWER, maybe Circuit busy or down?)[2016-01-06 20:22:00] NOTICE[16784] pbx_spool.c: Queued call to Local/310@from-internal expired without completion after 3 attempts

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                mcisar mcisar
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  NextupJiraPlusStatus

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