Adtran
Help
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Anonymous
Not applicable
‎01-29-2015 11:30 AM

Debugging DTMF Sip -> PRI -> SIP

Jump to solution

Edited Title to better reflect question.

Hello, I'm relatively new to the Adtran products.  I'm using a TA904 as a SIP to PRI Gateway.  My Setup is Handset ->SIP -> Asterisk -> PRI -> Adtran - > SIP -> Carrier.  I'm having DTMF Issues when calling from the asterisk box out to the carrier.  Calls Inbound, from the carrier to the Asterisk box can navigate my IVR Properly.  This is a test setup, that is why the Sip Carrier does not connect directly to the Asterisk box.  I'm testing this to be able to provide Voip Termination via PRI to legacy PBX Products.

I'm running the DTMF Debug options on both the Asterisk box and the Adtran, but I'm having some issues deciphering what the Adtran Output is telling me.  I used the command 'debug voice dsp voip 0/1 channel verbose rfc2833'

Below is the example when Entering my zip code into an IVR out on the PSTN (60505)  It looks like the Adtran is seeing the DTMF Event over the PRI correctly, but I'm not sure exactly what it's telling me.  It's acting like the remote end is getting multiple Keypresses for each digit.

Thank you,

Nate

Asterisk DTMF Logging output:

[2015-01-29 11:18:54] DTMF[4823][C-00000020]: channel.c:4214 __ast_read: DTMF begin '6' received on SIP/1011-00000020

[2015-01-29 11:18:54] DTMF[4823][C-00000020]: channel.c:4225 __ast_read: DTMF begin passthrough '6' on SIP/1011-00000020

[2015-01-29 11:18:54] DTMF[4823][C-00000020]: channel.c:4128 __ast_read: DTMF end '6' received on SIP/1011-00000020, duration 120 ms

[2015-01-29 11:18:54] DTMF[4823][C-00000020]: channel.c:4169 __ast_read: DTMF end accepted with begin '6' on SIP/1011-00000020

[2015-01-29 11:18:54] DTMF[4823][C-00000020]: channel.c:4198 __ast_read: DTMF end passthrough '6' on SIP/1011-00000020

[2015-01-29 11:18:54] DTMF[4823][C-00000020]: channel.c:4214 __ast_read: DTMF begin '0' received on SIP/1011-00000020

[2015-01-29 11:18:54] DTMF[4823][C-00000020]: channel.c:4225 __ast_read: DTMF begin passthrough '0' on SIP/1011-00000020

[2015-01-29 11:18:54] DTMF[4823][C-00000020]: channel.c:4128 __ast_read: DTMF end '0' received on SIP/1011-00000020, duration 120 ms

[2015-01-29 11:18:54] DTMF[4823][C-00000020]: channel.c:4169 __ast_read: DTMF end accepted with begin '0' on SIP/1011-00000020

[2015-01-29 11:18:54] DTMF[4823][C-00000020]: channel.c:4198 __ast_read: DTMF end passthrough '0' on SIP/1011-00000020

[2015-01-29 11:18:55] DTMF[4823][C-00000020]: channel.c:4214 __ast_read: DTMF begin '5' received on SIP/1011-00000020

[2015-01-29 11:18:55] DTMF[4823][C-00000020]: channel.c:4225 __ast_read: DTMF begin passthrough '5' on SIP/1011-00000020

[2015-01-29 11:18:55] DTMF[4823][C-00000020]: channel.c:4128 __ast_read: DTMF end '5' received on SIP/1011-00000020, duration 120 ms

[2015-01-29 11:18:55] DTMF[4823][C-00000020]: channel.c:4169 __ast_read: DTMF end accepted with begin '5' on SIP/1011-00000020

[2015-01-29 11:18:55] DTMF[4823][C-00000020]: channel.c:4198 __ast_read: DTMF end passthrough '5' on SIP/1011-00000020

[2015-01-29 11:18:55] DTMF[4823][C-00000020]: channel.c:4214 __ast_read: DTMF begin '0' received on SIP/1011-00000020

[2015-01-29 11:18:55] DTMF[4823][C-00000020]: channel.c:4225 __ast_read: DTMF begin passthrough '0' on SIP/1011-00000020

[2015-01-29 11:18:55] DTMF[4823][C-00000020]: channel.c:4128 __ast_read: DTMF end '0' received on SIP/1011-00000020, duration 120 ms

[2015-01-29 11:18:55] DTMF[4823][C-00000020]: channel.c:4169 __ast_read: DTMF end accepted with begin '0' on SIP/1011-00000020

[2015-01-29 11:18:55] DTMF[4823][C-00000020]: channel.c:4198 __ast_read: DTMF end passthrough '0' on SIP/1011-00000020

[2015-01-29 11:18:56] DTMF[4823][C-00000020]: channel.c:4214 __ast_read: DTMF begin '5' received on SIP/1011-00000020

[2015-01-29 11:18:56] DTMF[4823][C-00000020]: channel.c:4225 __ast_read: DTMF begin passthrough '5' on SIP/1011-00000020

[2015-01-29 11:18:56] DTMF[4823][C-00000020]: channel.c:4128 __ast_read: DTMF end '5' received on SIP/1011-00000020, duration 120 ms

[2015-01-29 11:18:56] DTMF[4823][C-00000020]: channel.c:4169 __ast_read: DTMF end accepted with begin '5' on SIP/1011-00000020

[2015-01-29 11:18:56] DTMF[4823][C-00000020]: channel.c:4198 __ast_read: DTMF end passthrough '5' on SIP/1011-00000020

Adtran logging output

TA904#

2015.01.29 11:18:54 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (6) - Seq Num (48260) - Timestamp (2526622193) - Duration (320) - M

2015.01.29 11:18:54 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (6) - Seq Num (48261) - Timestamp (2526622193) - Duration (480) -

2015.01.29 11:18:54 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (6) - Seq Num (48262) - Timestamp (2526622193) - Duration (640) -

2015.01.29 11:18:54 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (6) - Seq Num (48263) - Timestamp (2526622193) - Duration (800) -

2015.01.29 11:18:54 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (6) - Seq Num (48264) - Timestamp (2526622193) - Duration (960) -

2015.01.29 11:18:54 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (6) - Seq Num (48265) - Timestamp (2526622193) - Duration (1040) -

2015.01.29 11:18:54 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (6) - Seq Num (48266) - Timestamp (2526622193) - Duration (1040) - E

2015.01.29 11:18:54 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (6) - Seq Num (48267) - Timestamp (2526622193) - Duration (1040) - E

2015.01.29 11:18:54 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (6) - Seq Num (48268) - Timestamp (2526622193) - Duration (1040) - E

2015.01.29 11:18:54 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (0) - Seq Num (48280) - Timestamp (2526625233) - Duration (320) - M

2015.01.29 11:18:54 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (0) - Seq Num (48281) - Timestamp (2526625233) - Duration (480) -

2015.01.29 11:18:54 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (0) - Seq Num (48282) - Timestamp (2526625233) - Duration (640) -

2015.01.29 11:18:54 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (0) - Seq Num (48283) - Timestamp (2526625233) - Duration (800) -

2015.01.29 11:18:54 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (0) - Seq Num (48284) - Timestamp (2526625233) - Duration (960) -

2015.01.29 11:18:54 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (0) - Seq Num (48285) - Timestamp (2526625233) - Duration (1040) -

2015.01.29 11:18:54 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (0) - Seq Num (48286) - Timestamp (2526625233) - Duration (1040) - E

2015.01.29 11:18:54 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (0) - Seq Num (48287) - Timestamp (2526625233) - Duration (1040) - E

2015.01.29 11:18:55 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (0) - Seq Num (48288) - Timestamp (2526625233) - Duration (1040) - E

2015.01.29 11:18:55 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (5) - Seq Num (48298) - Timestamp (2526627953) - Duration (320) - M

2015.01.29 11:18:55 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (5) - Seq Num (48299) - Timestamp (2526627953) - Duration (480) -

2015.01.29 11:18:55 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (5) - Seq Num (48300) - Timestamp (2526627953) - Duration (640) -

2015.01.29 11:18:55 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (5) - Seq Num (48301) - Timestamp (2526627953) - Duration (800) -

2015.01.29 11:18:55 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (5) - Seq Num (48302) - Timestamp (2526627953) - Duration (960) -

2015.01.29 11:18:55 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (5) - Seq Num (48303) - Timestamp (2526627953) - Duration (1040) -

2015.01.29 11:18:55 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (5) - Seq Num (48304) - Timestamp (2526627953) - Duration (1040) - E

2015.01.29 11:18:55 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (5) - Seq Num (48305) - Timestamp (2526627953) - Duration (1040) - E

2015.01.29 11:18:55 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (5) - Seq Num (48306) - Timestamp (2526627953) - Duration (1040) - E

2015.01.29 11:18:55 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (0) - Seq Num (48317) - Timestamp (2526630913) - Duration (320) - M

2015.01.29 11:18:55 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (0) - Seq Num (48318) - Timestamp (2526630913) - Duration (480) -

2015.01.29 11:18:55 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (0) - Seq Num (48319) - Timestamp (2526630913) - Duration (640) -

2015.01.29 11:18:55 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (0) - Seq Num (48320) - Timestamp (2526630913) - Duration (800) -

2015.01.29 11:18:55 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (0) - Seq Num (48321) - Timestamp (2526630913) - Duration (960) -

2015.01.29 11:18:55 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (0) - Seq Num (48322) - Timestamp (2526630913) - Duration (960) - E

2015.01.29 11:18:55 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (0) - Seq Num (48323) - Timestamp (2526630913) - Duration (960) - E

2015.01.29 11:18:55 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (0) - Seq Num (48324) - Timestamp (2526630913) - Duration (960) - E

2015.01.29 11:18:56 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (5) - Seq Num (48347) - Timestamp (2526635633) - Duration (320) - M

2015.01.29 11:18:56 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (5) - Seq Num (48348) - Timestamp (2526635633) - Duration (480) -

2015.01.29 11:18:56 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (5) - Seq Num (48349) - Timestamp (2526635633) - Duration (640) -

2015.01.29 11:18:56 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (5) - Seq Num (48350) - Timestamp (2526635633) - Duration (800) -

2015.01.29 11:18:56 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (5) - Seq Num (48351) - Timestamp (2526635633) - Duration (960) -

2015.01.29 11:18:56 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (5) - Seq Num (48352) - Timestamp (2526635633) - Duration (960) - E

2015.01.29 11:18:56 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (5) - Seq Num (48353) - Timestamp (2526635633) - Duration (960) - E

2015.01.29 11:18:56 VOIPGATEWAY.VOIP 0/1 0 RFC2833 Sent - Event (5) - Seq Num (48354) - Timestamp (2526635633) - Duration (960) - E

TA904#

Labels (2)
Labels
0 Kudos
Reply
2 Solutions

Accepted Solutions
jayh
Honored Contributor
Honored Contributor
‎01-29-2015 12:55 PM

Re: Debugging DTMF Sip -> PRI -> SIP

Jump to solution

This looks OK. What is happening on the carrier side? Do they not react to DTMF at all, or does it appear as multiple digits?

Is the carrier side set up for DTMF inband or RFC2833?  Are you using G.711 codec to the carrier? 

View solution in original post

0 Kudos
Reply
jayh
Honored Contributor
Honored Contributor
‎01-29-2015 02:12 PM

Re: Debugging DTMF Sip -> PRI -> SIP

Jump to solution

blastcomm wrote:



I believe that it's receiving multiple digits, but I don't have a way to


confirm this. 


When you dial an IVR and send a single digit, does it interrupt the greeting? This will tell.


I am using Gx711, the Carrier is expecting RFC2833, is


there a way to confirm that in the Adtran?  I don't see any DTMF


Settings under the voice trunk settings.


You set it on the codec group for the ISDN voice trunk.

If you always use G.711 and get double digits it's possible that there is some early detection of the inband tone as well as the RFC2833 relay. You might set to inband if G-711 only but this will fail with G.729.

View solution in original post

0 Kudos
Reply
3 Replies
jayh
Honored Contributor
Honored Contributor
‎01-29-2015 12:55 PM

Re: Debugging DTMF Sip -> PRI -> SIP

Jump to solution

This looks OK. What is happening on the carrier side? Do they not react to DTMF at all, or does it appear as multiple digits?

Is the carrier side set up for DTMF inband or RFC2833?  Are you using G.711 codec to the carrier? 

0 Kudos
Reply
Anonymous
Not applicable
‎01-29-2015 01:17 PM

Re: Debugging DTMF Sip -> PRI -> SIP

Jump to solution

I believe that it's receiving multiple digits, but I don't have a way to

confirm this. I am using Gx711, the Carrier is expecting RFC2833, is

there a way to confirm that in the Adtran? I don't see any DTMF

Settings under the voice trunk settings.

Nate

0 Kudos
Accept as Solution Reply
jayh
Honored Contributor
Honored Contributor
‎01-29-2015 02:12 PM

Re: Debugging DTMF Sip -> PRI -> SIP

Jump to solution

blastcomm wrote:



I believe that it's receiving multiple digits, but I don't have a way to


confirm this. 


When you dial an IVR and send a single digit, does it interrupt the greeting? This will tell.


I am using Gx711, the Carrier is expecting RFC2833, is


there a way to confirm that in the Adtran?  I don't see any DTMF


Settings under the voice trunk settings.


You set it on the codec group for the ISDN voice trunk.

If you always use G.711 and get double digits it's possible that there is some early detection of the inband tone as well as the RFC2833 relay. You might set to inband if G-711 only but this will fail with G.729.

0 Kudos
Reply