Jump to content

viatalk inband dtmf issue


gotvoip
 Share

Recommended Posts

I have a customer who can't get inband dtmf's working with viatalk. I have it set to yes and still nothing. Outbound work fine. The invite shows no out of band. Here is the logfile. Any ideas? I tried changing media settings on the trunk and it is using 711.

 

 

Logfile

Clear or Reload the log.

 

[7] 2008/05/16 15:56:45: SIP Rx udp:216.246.73.186:5060:

INVITE sip:xxxxxxxxx@192.168.30.15:5060;transport=udp;line=c4ca4238 SIP/2.0

Via: SIP/2.0/UDP 216.246.73.186:5060;branch=z9hG4bK3711432b;rport

From: "xxxxxxxxxxxxxxxx@216.246.73.186>;tag=as6002f06d

To: <sip:xxxxxxx@192.168.30.15:5060;transport=udp;line=c4ca4238>

Contact: <sip:xxxxxx@216.246.73.186>

Call-ID: 625703bd2e99896065d3113d0f5f4327@216.246.73.186

CSeq: 102 INVITE

User-Agent: Viatalk SIP

Max-Forwards: 70

Remote-Party-ID: "xxxxxxxxxxxx@216.246.73.186>;privacy=off;screen=no

Date: Fri, 16 May 2008 20:03:56 GMT

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY

Supported: replaces

Content-Type: application/sdp

Content-Length: 210

 

v=0

o=root 1086 1086 IN IP4 216.246.73.186

s=session

c=IN IP4 216.246.73.186

t=0 0

m=audio 16312 RTP/AVP 0 8

a=rtpmap:0 PCMU/8000

a=rtpmap:8 PCMA/8000

a=silenceSupp:off - - - -

a=ptime:20

a=sendrecv

[7] 2008/05/16 15:56:45: UDP: Opening socket on port 52378

[7] 2008/05/16 15:56:45: UDP: Opening socket on port 52379

[5] 2008/05/16 15:56:45: Identify trunk (line match) 1

[9] 2008/05/16 15:56:45: Resolve 28: aaaa udp 216.246.73.186 5060

[9] 2008/05/16 15:56:45: Resolve 28: a udp 216.246.73.186 5060

[9] 2008/05/16 15:56:45: Resolve 28: udp 216.246.73.186 5060

[7] 2008/05/16 15:56:45: SIP Tx udp:216.246.73.186:5060:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 216.246.73.186:5060;branch=z9hG4bK3711432b;rport=5060

From: "xxxxxxxxx@216.246.73.186>;tag=as6002f06d

To: <sip:xxxxxxx@192.168.30.15:5060;transport=udp;line=c4ca4238>;tag=dcc2ade9bb

Call-ID: 625703bd2e99896065d3113d0f5f4327@216.246.73.186

CSeq: 102 INVITE

Content-Length: 0

[7] 2008/05/16 15:56:45: Set packet length to 20

[6] 2008/05/16 15:56:45: Sending RTP for 625703bd2e99896065d3113d0f5f4327@216.246.73.186#dcc2ade9bb to 216.246.73.186:16312

[5] 2008/05/16 15:56:45: Trunk Via Talk sends call to 100

[8] 2008/05/16 15:56:45: Play recordings/att1.wav space20

[7] 2008/05/16 15:56:45: Set packet length to 20

[9] 2008/05/16 15:56:45: Resolve 29: aaaa udp 216.246.73.186 5060

[9] 2008/05/16 15:56:45: Resolve 29: a udp 216.246.73.186 5060

[9] 2008/05/16 15:56:45: Resolve 29: udp 216.246.73.186 5060

[7] 2008/05/16 15:56:45: SIP Tx udp:216.246.73.186:5060:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 216.246.73.186:5060;branch=z9hG4bK3711432b;rport=5060

From: "xxxxxxxxxx@216.246.73.186>;tag=as6002f06d

To: <sip:xxxxxxx@192.168.30.15:5060;transport=udp;line=c4ca4238>;tag=dcc2ade9bb

Call-ID: 625703bd2e99896065d3113d0f5f4327@216.246.73.186

CSeq: 102 INVITE

Contact: <sip:1xxxxxxx@192.168.30.15:5060;transport=udp>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: pbxnsip-PBX/2.1.10.2474

Content-Type: application/sdp

Content-Length: 172

 

v=0

o=- 7333 7333 IN IP4 192.168.30.15

s=-

c=IN IP4 192.168.30.15

t=0 0

m=audio 52378 RTP/AVP 0 8

a=rtpmap:0 pcmu/8000

a=rtpmap:8 pcma/8000

a=ptime:20

a=sendrecv

[9] 2008/05/16 15:56:45: Resolve 30: aaaa udp 216.246.73.186 5060

[9] 2008/05/16 15:56:45: Resolve 30: a udp 216.246.73.186 5060

[9] 2008/05/16 15:56:45: Resolve 30: udp 216.246.73.186 5060

[7] 2008/05/16 15:56:45: SIP Tx udp:216.246.73.186:5060:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 216.246.73.186:5060;branch=z9hG4bK3711432b;rport=5060

From: "xxxxxxx@216.246.73.186>;tag=as6002f06d

To: <sip:xxxxxxxxx@192.168.30.15:5060;transport=udp;line=c4ca4238>;tag=dcc2ade9bb

Call-ID: 625703bd2e99896065d3113d0f5f4327@216.246.73.186

CSeq: 102 INVITE

Contact: <sip:xxxxxxx@192.168.30.15:5060;transport=udp>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: pbxnsip-PBX/2.1.10.2474

Content-Type: application/sdp

Content-Length: 172

 

v=0

o=- 7333 7333 IN IP4 192.168.30.15

s=-

c=IN IP4 192.168.30.15

t=0 0

m=audio 52378 RTP/AVP 0 8

a=rtpmap:0 pcmu/8000

a=rtpmap:8 pcma/8000

a=ptime:20

a=sendrecv

[7] 2008/05/16 15:56:45: SIP Rx udp:216.246.73.186:5060:

ACK sip:xxxxxx2@192.168.30.15:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 216.246.73.186:5060;branch=z9hG4bK6ec74547;rport

From: "xxxxxxx@216.246.73.186>;tag=as6002f06d

To: <sip:xxxxxx@192.168.30.15:5060;transport=udp;line=c4ca4238>;tag=dcc2ade9bb

Contact: <sip:xxxxxxx@216.246.73.186>

Call-ID: 625703bd2e99896065d3113d0f5f4327@216.246.73.186

CSeq: 102 ACK

User-Agent: Viatalk SIP

Max-Forwards: 70

Remote-Party-ID: "xxxxxxxx@216.246.73.186>;privacy=off;screen=no

Content-Length: 0

[7] 2008/05/16 15:56:45: SIP Rx udp:216.246.73.186:5060:

ACK sip:xxxxxx2@192.168.30.15:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 216.246.73.186:5060;branch=z9hG4bK075c8ace;rport

From: "xxxxxx@216.246.73.186>;tag=as6002f06d

To: <sip:xxxxxx@192.168.30.15:5060;transport=udp;line=c4ca4238>;tag=dcc2ade9bb

Contact: <sipxxxxx@216.246.73.186>

Call-ID: 625703bd2e99896065d3113d0f5f4327@216.246.73.186

CSeq: 102 ACK

User-Agent: Viatalk SIP

Max-Forwards: 70

Remote-Party-ID: "xxxxxxxx@216.246.73.186>;privacy=off;screen=no

Content-Length: 0

[9] 2008/05/16 15:56:45: Message repetition, packet dropped

[9] 2008/05/16 15:56:45: DTMF: Power: 0 0 0 0 0 0 0 0 0

[9] 2008/05/16 15:56:45: Last message repeated 2 times

[9] 2008/05/16 15:56:45: DTMF: Power: 0 0 2 0 0 0 0 0 1

[9] 2008/05/16 15:56:45: DTMF: Power: 0 0 0 0 2 0 0 0 0

[9] 2008/05/16 15:56:45: DTMF: Power: 2 0 2 0 0 0 0 0 0

[9] 2008/05/16 15:56:45: DTMF: Power: 2 0 0 0 0 0 0 0 0

[9] 2008/05/16 15:56:46: DTMF: Power: 0 0 2 0 0 0 0 1 0

[9] 2008/05/16 15:56:49: Resolve 31: aaaa udp 192.168.30.105 12052

[9] 2008/05/16 15:56:49: Resolve 31: a udp 192.168.30.105 12052

[9] 2008/05/16 15:56:49: Resolve 31: udp 192.168.30.105 12052

[9] 2008/05/16 15:56:54: Resolve 32: aaaa udp 192.168.30.105 12052

[9] 2008/05/16 15:56:54: Resolve 32: a udp 192.168.30.105 12052

[9] 2008/05/16 15:56:54: Resolve 32: udp 192.168.30.105 12052

[8] 2008/05/16 15:57:02: Play audio_en/aa_enter_extension_number.wav space10 audio_en/aa_dial_name_prompt.wav audio_en/bi_4.wav space20

[9] 2008/05/16 15:57:06: Resolve 33: url sip:richmond-3.vtnoc.net:5060

[9] 2008/05/16 15:57:06: Resolve 33: a udp richmond-3.vtnoc.net 5060

[9] 2008/05/16 15:57:06: Resolve 33: udp 216.246.73.186 5060

[8] 2008/05/16 15:57:06: Trunk 1 (Via Talk) has outbound proxy udp:216.246.73.186:5060

[9] 2008/05/16 15:57:06: Resolve 34: udp 216.246.73.186 5060

[8] 2008/05/16 15:57:06: Answer challenge with username 17326064002

[9] 2008/05/16 15:57:06: Resolve 35: udp 216.246.73.186 5060 udp:1

[9] 2008/05/16 15:57:06: Message repetition, packet dropped

[5] 2008/05/16 15:57:06: SMTP: Timeout

[8] 2008/05/16 15:57:10: Play audio_en/aa_enter_extension_number.wav space10 audio_en/aa_dial_name_prompt.wav audio_en/bi_4.wav space20

[8] 2008/05/16 15:57:11: DNS: Add dns_cname mail.friedomtech.com mail.friedomtech.com.netsolmail.net (ttl=60)

[8] 2008/05/16 15:57:12: SMTP: Connect to 205.178.146.50:25

[9] 2008/05/16 15:57:12: Resolve 36: aaaa udp 216.246.73.186 5060

[9] 2008/05/16 15:57:12: Resolve 36: a udp 216.246.73.186 5060

[9] 2008/05/16 15:57:12: Resolve 36: udp 216.246.73.186 5060

[9] 2008/05/16 15:57:13: Resolve 37: aaaa udp 192.168.30.105 12052

[9] 2008/05/16 15:57:13: Resolve 37: a udp 192.168.30.105 12052

[9] 2008/05/16 15:57:13: Resolve 37: udp 192.168.30.105 12052

[8] 2008/05/16 15:57:19: Play audio_en/aa_enter_extension_number.wav space10 audio_en/aa_dial_name_prompt.wav audio_en/bi_4.wav space20

[7] 2008/05/16 15:57:24: SIP Rx udp:216.246.73.186:5060:

BYE sip:xxxxxxx192.168.30.15:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 216.246.73.186:5060;branch=z9hG4bK60615544;rport

From: "xxxxxxx@216.246.73.186>;tag=as6002f06d

To: <sip:xxxxx@192.168.30.15:5060;transport=udp;line=c4ca4238>;tag=dcc2ade9bb

Call-ID: 625703bd2e99896065d3113d0f5f4327@216.246.73.186

CSeq: 103 BYE

User-Agent: Viatalk SIP

Max-Forwards: 70

Remote-Party-ID: "xxxxxx@216.246.73.186>;privacy=off;screen=no

Content-Length: 0

[9] 2008/05/16 15:57:24: Resolve 38: aaaa udp 216.246.73.186 5060

[9] 2008/05/16 15:57:24: Resolve 38: a udp 216.246.73.186 5060

[9] 2008/05/16 15:57:24: Resolve 38: udp 216.246.73.186 5060

[7] 2008/05/16 15:57:24: SIP Tx udp:216.246.73.186:5060:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 216.246.73.186:5060;branch=z9hG4bK60615544;rport=5060

From: "xxxx@216.246.73.186>;tag=as6002f06d

To: <sipx@192.168.30.15:5060;transport=udp;line=c4ca4238>;tag=dcc2ade9bb

Call-ID: 625703bd2e99896065d3113d0f5f4327@216.246.73.186

CSeq: 103 BYE

Contact: <sip:1x@192.168.30.15:5060;transport=udp>

User-Agent: pbxnsip-PBX/2.1.10.2474

RTP-RxStat: Dur=38,Pkt=7,Oct=1204,Underun=0

RTP-TxStat: Dur=38,Pkt=1893,Oct=325596

Content-Length: 0

[9] 2008/05/16 15:57:31: Resolve 39: aaaa udp 216.246.73.186 5060

[9] 2008/05/16 15:57:31: Resolve 39: a udp 216.246.73.186 5060

[9] 2008/05/16 15:57:31: Resolve 39: udp 216.246.73.186 5060

[9] 2008/05/16 15:57:39: Resolve 40: aaaa udp 192.168.30.105 12052

[9] 2008/05/16 15:57:39: Resolve 40: a udp 192.168.30.105 12052

[9] 2008/05/16 15:57:39: Resolve 40: udp 192.168.30.105 12052

[9] 2008/05/16 15:58:04: Resolve 41: aaaa udp 192.168.30.105 12052

[9] 2008/05/16 15:58:04: Resolve 41: a udp 192.168.30.105 12052

[9] 2008/05/16 15:58:04: Resolve 41: udp 192.168.30.105 12052

[9] 2008/05/16 15:58:06: Resolve 42: url sip:richmond-3.vtnoc.net:5060

[9] 2008/05/16 15:58:06: Resolve 42: a udp richmond-3.vtnoc.net 5060

[9] 2008/05/16 15:58:06: Resolve 42: udp 216.246.73.186 5060

[8] 2008/05/16 15:58:06: Trunk 1 (Via Talk) has outbound proxy udp:216.246.73.186:5060

[9] 2008/05/16 15:58:06: Resolve 43: udp 216.246.73.186 5060

[8] 2008/05/16 15:58:06: Answer challenge with username 17326064002

[9] 2008/05/16 15:58:06: Resolve 44: udp 216.246.73.186 5060 udp:1

[9] 2008/05/16 15:58:06: Message repetition, packet dropped

[9] 2008/05/16 15:58:08: Resolve 45: aaaa udp 216.246.73.186 5060

[9] 2008/05/16 15:58:08: Resolve 45: a udp 216.246.73.186 5060

[9] 2008/05/16 15:58:08: Resolve 45: udp 216.246.73.186 5060

 

[9] 2008/05/16 15:58:31: Resolve 46: aaaa udp 192.168.30.105 12052

[9] 2008/05/16 15:58:31: Resolve 46: a udp 192.168.30.105 12052

[9] 2008/05/16 15:58:31: Resolve 46: udp 192.168.30.105 12052

[9] 2008/05/16 15:58:31: Resolve 47: aaaa udp 216.246.73.186 5060

[9] 2008/05/16 15:58:31: Resolve 47: a udp 216.246.73.186 5060

[9] 2008/05/16 15:58:31: Resolve 47: udp 216.246.73.186 5060

[9] 2008/05/16 15:58:32: Message repetition, packet dropped

[9] 2008/05/16 15:58:56: Resolve 48: aaaa udp 192.168.30.105 12052

[9] 2008/05/16 15:58:56: Resolve 48: a udp 192.168.30.105 12052

[9] 2008/05/16 15:58:56: Resolve 48: udp 192.168.30.105 12052

[9] 2008/05/16 15:59:06: Resolve 49: url sip:richmond-3.vtnoc.net:5060

[9] 2008/05/16 15:59:06: Resolve 49: a udp richmond-3.vtnoc.net 5060

[9] 2008/05/16 15:59:06: Resolve 49: udp 216.246.73.186 5060

[8] 2008/05/16 15:59:06: Trunk 1 (Via Talk) has outbound proxy udp:216.246.73.186:5060

[9] 2008/05/16 15:59:06: Resolve 50: udp 216.246.73.186 5060

[8] 2008/05/16 15:59:06: Answer challenge with username

[9] 2008/05/16 15:59:06: Resolve 51: udp 216.246.73.186 5060 udp:1

[9] 2008/05/16 15:59:06: Message repetition, packet dropped

[5] 2008/05/16 15:59:12: SMTP: Timeout

[9] 2008/05/16 15:59:13: Resolve 52: aaaa udp 216.246.73.186 5060

[9] 2008/05/16 15:59:13: Resolve 52: a udp 216.246.73.186 5060

[9] 2008/05/16 15:59:13: Resolve 52: udp 216.246.73.186 5060

)

[8] 2008/05/16 15:59:17: SMTP: Connect to 205.178.146.50:25

[9] 2008/05/16 15:59:20: Resolve 53: aaaa udp 192.168.30.105 12052

[9] 2008/05/16 15:59:20: Resolve 53: a udp 192.168.30.105 12052

[9] 2008/05/16 15:59:20: Resolve 53: udp 192.168.30.105 12052

[9] 2008/05/16 15:59:32: Resolve 54: aaaa udp 216.246.73.186 5060

[9] 2008/05/16 15:59:32: Resolve 54: a udp 216.246.73.186 5060

[9] 2008/05/16 15:59:32: Resolve 54: udp 216.246.73.186 5060

[9] 2008/05/16 15:59:48: Resolve 55: aaaa udp 192.168.30.105 12052

[9] 2008/05/16 15:59:48: Resolve 55: a udp 192.168.30.105 12052

[9] 2008/05/16 15:59:48: Resolve 55: udp 192.168.30.105 12052

[9] 2008/05/16 16:00:06: Resolve 56: url sip:richmond-3.vtnoc.net:5060

[9] 2008/05/16 16:00:06: Resolve 56: a udp richmond-3.vtnoc.net 5060

[9] 2008/05/16 16:00:06: Resolve 56: udp 216.246.73.186 5060

[8] 2008/05/16 16:00:06: Trunk 1 (Via Talk) has outbound proxy udp:216.246.73.186:5060

[9] 2008/05/16 16:00:06: Resolve 57: udp 216.246.73.186 5060

[8] 2008/05/16 16:00:06: Answer challenge with username 17326064002

[9] 2008/05/16 16:00:06: Resolve 58: udp 216.246.73.186 5060 udp:1

[9] 2008/05/16 16:00:06: Message repetition, packet dropped

[9] 2008/05/16 16:00:09: Resolve 59: aaaa udp 216.246.73.186 5060

[9] 2008/05/16 16:00:09: Resolve 59: a udp 216.246.73.186 5060

[9] 2008/05/16 16:00:09: Resolve 59: udp 216.246.73.186 5060

[9] 2008/05/16 16:00:09: Message repetition, packet dropped

[9] 2008/05/16 16:00:13: Resolve 60: aaaa udp 192.168.30.105 12052

[9] 2008/05/16 16:00:13: Resolve 60: a udp 192.168.30.105 12052

[9] 2008/05/16 16:00:13: Resolve 60: udp 192.168.30.105 12052

 

[9] 2008/05/16 16:00:32: Resolve 61: aaaa udp 216.246.73.186 5060

[9] 2008/05/16 16:00:32: Resolve 61: a udp 216.246.73.186 5060

[9] 2008/05/16 16:00:32: Resolve 61: udp 216.246.73.186 5060

[9] 2008/05/16 16:00:36: Resolve 62: aaaa udp 192.168.30.105 12052

[9] 2008/05/16 16:00:36: Resolve 62: a udp 192.168.30.105 12052

[9] 2008/05/16 16:00:36: Resolve 62: udp 192.168.30.105 12052

[9] 2008/05/16 16:00:59: Resolve 63: aaaa udp 192.168.30.105 12052

[9] 2008/05/16 16:00:59: Resolve 63: a udp 192.168.30.105 12052

[9] 2008/05/16 16:00:59: Resolve 63: udp 192.168.30.105 12052

 

 

Copyright © 2005-2008 pbxnsip Inc. All rights reserved. See the license agreement for more information.

Link to comment
Share on other sites

[9] 2008/05/16 15:56:45: DTMF: Power: 0 0 0 0 0 0 0 0 0

[9] 2008/05/16 15:56:45: Last message repeated 2 times

[9] 2008/05/16 15:56:45: DTMF: Power: 0 0 2 0 0 0 0 0 1

[9] 2008/05/16 15:56:45: DTMF: Power: 0 0 0 0 2 0 0 0 0

[9] 2008/05/16 15:56:45: DTMF: Power: 2 0 2 0 0 0 0 0 0

[9] 2008/05/16 15:56:45: DTMF: Power: 2 0 0 0 0 0 0 0 0

[9] 2008/05/16 15:56:46: DTMF: Power: 0 0 2 0 0 0 0 1 0

 

Well obviously there is inband DTMF detection going on, but it seems the volume is too low to have a reliable DTMF detection ("Whisper DTMF"). Maybe whoever is sending the DTMF should increase the volume.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...