Help needed understanding why call could not be made

I am having trouble understanding the reason this outbound call to AAABBBCCCC could not be made - the users are complaining that the system is generating a busy signal. The number is known to be working, so am I missing the cause of the call failure from the (partial) logs below:

... (First lines dropped for brevity)
[2020-03-23 11:49:58] VERBOSE[26534][C-00000786] pbx.c: Executing [[email protected]:22] ExecIf("SIP/23-00001066", "1?Set(CONNECTEDLINE(name,i)=CID:XXXYYYZZZZ)") in new stack
[2020-03-23 11:49:58] VERBOSE[26534][C-00000786] pbx.c: Executing [[email protected]:23] ExecIf("SIP/23-00001066", "0?Set(CONNECTEDLINE(name,i)=CID:(Hidden)XXXYYYZZZZ)") in new stack
[2020-03-23 11:49:58] VERBOSE[26534][C-00000786] pbx.c: Executing [[email protected]:24] GotoIf("SIP/23-00001066", "0?customtrunk") in new stack
[2020-03-23 11:49:58] VERBOSE[26534][C-00000786] pbx.c: Executing [[email protected]:25] ExecIf("SIP/23-00001066", "0?Set(DIAL_TRUNK_OPTIONS=)") in new stack
[2020-03-23 11:49:58] VERBOSE[26534][C-00000786] pbx.c: Executing [[email protected]:26] Dial("SIP/23-00001066", "SIP/thinktel/1AAABBBCCCC,300,Tb(func-apply-sipheaders^s^1,(2))") in new stack
[2020-03-23 11:49:58] VERBOSE[26534][C-00000786] netsock2.c: Using SIP RTP TOS bits 184
[2020-03-23 11:49:58] VERBOSE[26534][C-00000786] netsock2.c: Using SIP RTP CoS mark 5
[2020-03-23 11:49:58] VERBOSE[26534][C-00000786] app_stack.c: SIP/thinktel-00001067 Internal Gosub(func-apply-sipheaders,s,1(2)) start
[2020-03-23 11:49:58] VERBOSE[26534][C-00000786] pbx.c: Executing [[email protected]:1] NoOp("SIP/thinktel-00001067", "Applying SIP Headers to channel SIP/thinktel-00001067") in new stack
[2020-03-23 11:49:58] VERBOSE[26534][C-00000786] pbx.c: Executing [[email protected]:2] Set("SIP/thinktel-00001067", "TECH=SIP") in new stack
[2020-03-23 11:49:58] VERBOSE[26534][C-00000786] pbx.c: Executing [[email protected]:3] Set("SIP/thinktel-00001067", "SIPHEADERKEYS=") in new stack
[2020-03-23 11:49:58] VERBOSE[26534][C-00000786] pbx.c: Executing [[email protected]:4] While("SIP/thinktel-00001067", "0") in new stack
[2020-03-23 11:49:58] VERBOSE[26534][C-00000786] app_while.c: Jumping to priority 12
[2020-03-23 11:49:58] VERBOSE[26534][C-00000786] pbx.c: Executing [[email protected]:13] Return("SIP/thinktel-00001067", "") in new stack
[2020-03-23 11:49:58] VERBOSE[26534][C-00000786] app_stack.c: Spawn extension (from-trunk, 5AAABBBCCCC, 1) exited non-zero on 'SIP/thinktel-00001067'
[2020-03-23 11:49:58] VERBOSE[26534][C-00000786] app_stack.c: SIP/thinktel-00001067 Internal Gosub(func-apply-sipheaders,s,1(2)) complete GOSUB_RETVAL=
[2020-03-23 11:49:58] VERBOSE[26534][C-00000786] app_dial.c: Called SIP/thinktel/1AAABBBCCCC
[2020-03-23 11:50:04] VERBOSE[26534][C-00000786] app_dial.c: SIP/thinktel-00001067 is making progress passing it to SIP/23-00001066
[2020-03-23 11:50:16] VERBOSE[26534][C-00000786] app_macro.c: Spawn extension (macro-dialout-trunk, s, 26) exited non-zero on 'SIP/23-00001066' in macro 'dialout-trunk'
[2020-03-23 11:50:16] VERBOSE[26534][C-00000786] pbx.c: Spawn extension (from-internal, 5AAABBBCCCC, 6) exited non-zero on 'SIP/23-00001066'
[2020-03-23 11:50:16] VERBOSE[26534][C-00000786] pbx.c: Executing [[email protected]:1] Macro("SIP/23-00001066", "hangupcall") in new stack
[2020-03-23 11:50:16] VERBOSE[26534][C-00000786] pbx.c: Executing [[email protected]:1] GotoIf("SIP/23-00001066", "1?theend") in new stack
[2020-03-23 11:50:16] VERBOSE[26534][C-00000786] pbx_builtins.c: Goto (macro-hangupcall,s,3)
[2020-03-23 11:50:16] VERBOSE[26534][C-00000786] pbx.c: Executing [[email protected]:3] ExecIf("SIP/23-00001066", "0?Set(CDR(recordingfile)=)") in new stack
[2020-03-23 11:50:16] VERBOSE[26534][C-00000786] pbx.c: Executing [[email protected]:4] NoOp("SIP/23-00001066", "SIP/thinktel-00001067 montior file= /var/spool/asterisk/monitor/2020/03/23/out-5AAABBBCCCC-23-20200323-114958-1584982198.6067.wav") in new stack
[2020-03-23 11:50:16] VERBOSE[26534][C-00000786] pbx.c: Executing [[email protected]:5] GotoIf("SIP/23-00001066", "0?skipagi") in new stack
[2020-03-23 11:50:16] VERBOSE[26534][C-00000786] pbx.c: Executing [[email protected]:6] AGI("SIP/23-00001066", "attendedtransfer-rec-restart.php,SIP/thinktel-00001067,/var/spool/asterisk/monitor/2020/03/23/out-5AAABBBCCCC-23-20200323-114958-1584982198.6067.wav") in new stack
[2020-03-23 11:50:16] VERBOSE[26534][C-00000786] res_agi.c: Launched AGI Script /var/lib/asterisk/agi-bin/attendedtransfer-rec-restart.php
[2020-03-23 11:50:16] VERBOSE[26534][C-00000786] res_agi.c: <SIP/23-00001066>AGI Script attendedtransfer-rec-restart.php completed, returning 0
[2020-03-23 11:50:16] VERBOSE[26534][C-00000786] pbx.c: Executing [[email protected]:7] Hangup("SIP/23-00001066", "") in new stack
[2020-03-23 11:50:16] VERBOSE[26534][C-00000786] app_macro.c: Spawn extension (macro-hangupcall, s, 7) exited non-zero on 'SIP/23-00001066' in macro 'hangupcall'
[2020-03-23 11:50:16] VERBOSE[26534][C-00000786] pbx.c: Spawn extension (from-internal, h, 1) exited non-zero on 'SIP/23-00001066'

I think you need to increase your “verbosity” to fill in the bits around

[ 2020-03-23 11:50:16] VERBOSE[26534][C-00000786] app_macro.c: Spawn extension (macro-dialout-trunk, s, 26) exited non-zero on ‘SIP/23-00001066’ in macro ‘dialout-trunk’

I presume there is no way to change verbosity level after the fact as these are from the actual log file?

That is correct.

core set verbose 3

will a) set it to 3, b) report what it was.

The fact that the phone number goes into your outbound route with a leading ‘1’ and leaves unhandled with a leading ‘5’ seem pretty hinky to me.

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.