[asterisk-bugs] [JIRA] (ASTERISK-22908) CLONE - SIP INFO DTMF Relay locking on DTMF tones in G100 gateway

[Jean Galarneau (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-22908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=212245#comment-212245 ] 

Jean Galarneau commented on ASTERISK-22908:
-------------------------------------------

We are actually using 1.8.15-cert2
                
> CLONE - SIP INFO DTMF Relay locking on DTMF tones in G100 gateway
> -----------------------------------------------------------------
>
>                 Key: ASTERISK-22908
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22908
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>            Reporter: Justin Hester
>            Assignee: Doug Bailey
>
> I am moving a site to use reinvite internally upon its extensions and in doing so, have moved to using dtmfmode=info for the extensions.  All internal RTP works fine.
> However, when a call is switched via the Asterisk PBX, and the G100 to the ISDN service, and a DTMF digit is sent by the Extension, the receiving device on the ISDN side is left with a hanging on DTMF digit.  This appears to be a bug in the g100.
> I need to resolve this asap as the PBX has analog FXS extensions (xorcom) and we are having issues with DTMF digit transfer.  I need to sort the SIP extensions working with correct dtmfmode=info first.... 
> Called from SIP ext 302 to 0490038089.
> Upon answer, dialled digit 3 for about 1/2 a second
> The called party continues to hear the hung DTMF digit continuously, cannot talk over it and has to hang up.
> Just tried shortinfo too, and same problem.
> Asterisk PBX trunk config:
> username=ISDN-GW
> type=peer
> secret=ISDN-StUTuR7p
> qualify=100
> host=10.10.206.5
> nat=no
> insecure=invite,port
> canreinvite=no
> dtmfmode=shortinfo
> disallow=all
> context=from-trunk-isdn-gw-custom
> allow=alaw

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira