11.5.0: Blindxfer Problems

Home » Asterisk Users » 11.5.0: Blindxfer Problems
Asterisk Users 7 Comments

I’ve got a confbridge set up which works if dialed locally:

— Executing [266@internal:1] Answer(“DAHDI/1-1”, “”) in new stack
— Executing [266@internal:2] SendDTMF(“DAHDI/1-1”, “1”) in new stack
— Executing [266@internal:3] ConfBridge(“DAHDI/1-1”, “1”) in new stack
— Playing ‘conf-onlyperson.ulaw’ (language ‘en’)
…….

extensions.conf:

[globals]
……. GOTO_ON_BLINDXFR=”internal,266,1″

features.conf:

[featuremap]
blindxfer => #1

But:

— Executing [s@DialOut:14] Dial(“DAHDI/1-1”,
“motif/xxxx/+1234567890a@voice.google.com,,rTt”) in new stack
— Called motif/xxxx/+1234567890a@voice.google.com
— Motif/+1234567890a@voice.google.com-688c is proceeding passing it to DAHDI/1-1
— Motif/+1234567890a@voice.google.com-688c answered DAHDI/1-1
— Started music on hold, class ‘default’, on Motif/+123456789a@voice.google.com-688c
— Playing ‘pbx-transfer.ulaw’ (language ‘en’)
[Dec 17 09:46:59] WARNING[19083][C-000000be]: features.c:2550
builtin_blindtransfer: No digits dialed.
— Playing ‘pbx-invalid.ulaw’ (language ‘en’)

I’m expecting the blind transfer to GOTO internal,266,1.

If I input 266 at the transfer dial tone, the blind transfer occurs.

Do I have this set up incorrectly?

sean

7 thoughts on - 11.5.0: Blindxfer Problems

  • Thanks for the response, but no joy:

    == Setting global variable ‘GOTO_ON_BLINDXFER’ to ‘internal^266^1’

    Playing ‘pbx-transfer.ulaw’ (language ‘en’)
    [Dec 20 15:12:03] WARNING[12336][C-00000012]: features.c:2550
    builtin_blindtransfer: No digits dialed.

    sean

  • I also tried setting up a transfer as an applicationmap.

    conference => *7,peer/both,ConfBridge,1

    Seems to load:

    features reload
    == Parsing ‘/etc/asterisk/features.conf’: Found
    == Registered Feature ‘conference’
    == Mapping Feature ‘conference’ to app ‘ConfBridge(1)’ with code ‘*7’

    but when the caller dials *7, there’s no action, Nothing in the cli. The dtmf is just sent to the callee.

    Also tried having the callee dial *7, same result.

    Any help appreciated.

  • OK. I’ll figure out DTMF logging, but notice asterisk does recognize both #1 (blindxfer) and *2 (atxfer), so it recognizes DTMF tones.

    sean

    —

  • How do I enable DTMF logging?

    logger set level DEBUG
    No such command ‘logger set level DEBUG’ (type ‘core show help logger set level’ for other possible commands)

    didn’t work, even though:

    help logger
    logger mute Toggle logging output to a console
    logger reload Reopens the log files
    logger rotate Rotates and reopens the log files logger set level {DEBUG|NOTICE Enables/Disables a specific logging level for this console

    I tried core set debug 10 , but that captured no DTMF.

    sean

    —

  • The help syntax string is truncated because of the number of options and the column length. The command is:
    logger set level DTMF

    The full help syntax string is:
    logger set level {DEBUG|NOTICE|WARNING|ERROR|VERBOSE|DTMF} {on|off}

    Richard

  • Thanks.

    cli logger shows _no_ dtmf events, yet recognizes *2 !!

    logger set level dtmf on Logger status for ‘DTMF’ has been set to ‘on’.

    << here I first hit *7, then hit *2 >>>

    — Started music on hold, class ‘default’, on Motif/+12036258013@voice.google.com-8bf9
    — Playing ‘pbx-transfer.ulaw’ (language ‘en’)
    …..

    sean