We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dtmf not recognized by pinset while dialing out
Reproduction Steps:
Skinny Client Control Protocol (SCCP). Release: 4.3.5 develop - c1533a6 (built by 'root' on '2022-11-25 18:40:52 UTC')
freepbx 16 Asterisk 18.14.0
-- Goto (macro-pinsets,s,7) -- Executing [s@macro-pinsets:7] Set("SCCP/8499-00000087", "try=3") in new stack -- Executing [s@macro-pinsets:8] GotoIf("SCCP/8499-00000087", "0?hangup") in new stack -- Executing [s@macro-pinsets:9] Read("SCCP/8499-00000087", "dtmf,auth-incorrect,0,n,1,10") in new stack -- <SCCP/8499-00000087> Playing 'auth-incorrect.ulaw' (language 'pt_BR') -- SEPECE1A9AA63E2: SCCP (handle_keypad) digit:00000006, callid:135, lineInstance:1 -- SEPECE1A9AA63E2: SCCP (handle_keypad) BOTH callid and lineinstance -- SEPECE1A9AA63E2: SCCP Digit: 00000006 (6) on line 8499, channel 135 with state: 24 (Using: RFC2833) -- SEPECE1A9AA63E2: SCCP (handle_keypad) digit:00000005, callid:135, lineInstance:1 -- SEPECE1A9AA63E2: SCCP (handle_keypad) BOTH callid and lineinstance -- SEPECE1A9AA63E2: SCCP Digit: 00000005 (5) on line 8499, channel 135 with state: 24 (Using: RFC2833) -- SEPECE1A9AA63E2: SCCP (handle_keypad) digit:00000004, callid:135, lineInstance:1 -- SEPECE1A9AA63E2: SCCP (handle_keypad) BOTH callid and lineinstance -- SEPECE1A9AA63E2: SCCP Digit: 00000004 (4) on line 8499, channel 135 with state: 24 (Using: RFC2833) -- SEPECE1A9AA63E2: SCCP (handle_keypad) digit:00000003, callid:135, lineInstance:1 -- SEPECE1A9AA63E2: SCCP (handle_keypad) BOTH callid and lineinstance -- SEPECE1A9AA63E2: SCCP Digit: 00000003 (3) on line 8499, channel 135 with state: 24 (Using: RFC2833) -- SEPECE1A9AA63E2: SCCP (handle_keypad) digit:00000009, callid:135, lineInstance:1 -- SEPECE1A9AA63E2: SCCP (handle_keypad) BOTH callid and lineinstance -- SEPECE1A9AA63E2: SCCP Digit: 00000009 (9) on line 8499, channel 135 with state: 24 (Using: RFC2833) -- User entered nothing. -- Executing [s@macro-pinsets:10] GotoIf("SCCP/8499-00000087", "0?return:askpin") in new stack -- Goto (macro-pinsets,s,7) -- Executing [s@macro-pinsets:7] Set("SCCP/8499-00000087", "try=4") in new stack -- Executing [s@macro-pinsets:8] GotoIf("SCCP/8499-00000087", "0?hangup") in new stack -- Executing [s@macro-pinsets:9] Read("SCCP/8499-00000087", "dtmf,auth-incorrect,0,n,1,10") in new stack -- <SCCP/8499-00000087> Playing 'auth-incorrect.ulaw' (language 'pt_BR')
The text was updated successfully, but these errors were encountered:
If I override pinset macro to answer instead of Progress, pinsets works fine.
[macro-pinsets] ;include => macro-pinsets-custom exten => s,1,Set(try=1) exten => s,n,GotoIf($[${ARG2} = 1]?cdr,1) exten => s,n,GotoIf($["${DB(AMPUSER/${AMPUSER}/pinless)}" != "NOPASSWD"]?auth:return) ;exten => s,n(auth),Progress exten => s,n(auth),Answer exten => s,n,Read(dtmf,agent-pass,0,n,1,10)
Sorry, something went wrong.
No branches or pull requests
dtmf not recognized by pinset while dialing out
Reproduction Steps:
Skinny Client Control Protocol (SCCP). Release: 4.3.5 develop - c1533a6 (built by 'root' on '2022-11-25 18:40:52 UTC')
freepbx 16 Asterisk 18.14.0
-- Goto (macro-pinsets,s,7)
-- Executing [s@macro-pinsets:7] Set("SCCP/8499-00000087", "try=3") in new stack
-- Executing [s@macro-pinsets:8] GotoIf("SCCP/8499-00000087", "0?hangup") in new stack
-- Executing [s@macro-pinsets:9] Read("SCCP/8499-00000087", "dtmf,auth-incorrect,0,n,1,10") in new stack
-- <SCCP/8499-00000087> Playing 'auth-incorrect.ulaw' (language 'pt_BR')
-- SEPECE1A9AA63E2: SCCP (handle_keypad) digit:00000006, callid:135, lineInstance:1
-- SEPECE1A9AA63E2: SCCP (handle_keypad) BOTH callid and lineinstance
-- SEPECE1A9AA63E2: SCCP Digit: 00000006 (6) on line 8499, channel 135 with state: 24 (Using: RFC2833)
-- SEPECE1A9AA63E2: SCCP (handle_keypad) digit:00000005, callid:135, lineInstance:1
-- SEPECE1A9AA63E2: SCCP (handle_keypad) BOTH callid and lineinstance
-- SEPECE1A9AA63E2: SCCP Digit: 00000005 (5) on line 8499, channel 135 with state: 24 (Using: RFC2833)
-- SEPECE1A9AA63E2: SCCP (handle_keypad) digit:00000004, callid:135, lineInstance:1
-- SEPECE1A9AA63E2: SCCP (handle_keypad) BOTH callid and lineinstance
-- SEPECE1A9AA63E2: SCCP Digit: 00000004 (4) on line 8499, channel 135 with state: 24 (Using: RFC2833)
-- SEPECE1A9AA63E2: SCCP (handle_keypad) digit:00000003, callid:135, lineInstance:1
-- SEPECE1A9AA63E2: SCCP (handle_keypad) BOTH callid and lineinstance
-- SEPECE1A9AA63E2: SCCP Digit: 00000003 (3) on line 8499, channel 135 with state: 24 (Using: RFC2833)
-- SEPECE1A9AA63E2: SCCP (handle_keypad) digit:00000009, callid:135, lineInstance:1
-- SEPECE1A9AA63E2: SCCP (handle_keypad) BOTH callid and lineinstance
-- SEPECE1A9AA63E2: SCCP Digit: 00000009 (9) on line 8499, channel 135 with state: 24 (Using: RFC2833)
-- User entered nothing.
-- Executing [s@macro-pinsets:10] GotoIf("SCCP/8499-00000087", "0?return:askpin") in new stack
-- Goto (macro-pinsets,s,7)
-- Executing [s@macro-pinsets:7] Set("SCCP/8499-00000087", "try=4") in new stack
-- Executing [s@macro-pinsets:8] GotoIf("SCCP/8499-00000087", "0?hangup") in new stack
-- Executing [s@macro-pinsets:9] Read("SCCP/8499-00000087", "dtmf,auth-incorrect,0,n,1,10") in new stack
-- <SCCP/8499-00000087> Playing 'auth-incorrect.ulaw' (language 'pt_BR')
The text was updated successfully, but these errors were encountered: