Re: C8000v DTMF debug issue

Maxim Denisov · ‎11-08-2021

Hello,

I'm running CUBE on C8000v 17.06.1a and found that it not shows DTMF events with debug voip rtp session named-event 101. The same debug works with older CSR 1000v. Is there a workaround except using monitor capture?

Regards,
Maxim

Maren Mahoney · ‎11-08-2021

Certainly debug voip rtp works on the C8000V. When you do "debug voip rtp ?", what are your options?

Maren

Maxim Denisov · ‎11-08-2021

Thank you for your reply. I can see that DTMF events are generated with debug voip rtp but don't see the details. Here is a debug after pressing 4 and 5:

Nov  9 04:26:25.461: //110/2F8D5A000000/VOIPRTP:():voip_rtp_xmit:
Nov  9 04:26:25.461: //110/2F8D5A000000/VOIPRTP:():voip_rtp_send_pak:
Nov  9 04:26:25.481: //110/2F8D5A000000/VOIPRTP:():voip_rtp_xmit:
Nov  9 04:26:25.481: //110/2F8D5A000000/VOIPRTP:():voip_rtp_send_pak:
Nov  9 04:26:25.501: //110/2F8D5A000000/VOIPRTP:():voip_rtp_xmit:
Nov  9 04:26:25.501: //110/2F8D5A000000/VOIPRTP:():voip_rtp_send_pak:
Nov  9 04:26:25.522: //110/2F8D5A000000/VOIPRTP:():voip_rtp_xmit:
Nov  9 04:26:25.522: //110/2F8D5A000000/VOIPRTP:():voip_rtp_send_pak:
Nov  9 04:26:25.541: //110/2F8D5A000000/VOIPRTP:():voip_rtp_xmit:
Nov  9 04:26:25.541: //110/2F8D5A000000/VOIPRTP:():voip_rtp_send_pak:
Nov  9 04:26:25.561: //110/2F8D5A000000/VOIPRTP:():voip_rtp_xmit:
Nov  9 04:26:25.561: //110/2F8D5A000000/VOIPRTP:():voip_rtp_send_pak:
Nov  9 04:26:25.581: //110/2F8D5A000000/VOIPRTP:():voip_rtp_xmit:
Nov  9 04:26:25.581: //110/2F8D5A000000/VOIPRTP:():voip_rtp_send_pak:
Nov  9 04:26:25.591: //110/2F8D5A000000/VOIPRTP:():voip_rtp_xmit:
Nov  9 04:26:25.591: //110/2F8D5A000000/VOIPRTP:():voip_rtp_send_pak:
Nov  9 04:26:25.591: //110/2F8D5A000000/VOIPRTP:():voip_rtp_xmit:
Nov  9 04:26:25.591: //110/2F8D5A000000/VOIPRTP:():voip_rtp_send_pak:
Nov  9 04:26:25.591: //110/2F8D5A000000/VOIPRTP:():voip_rtp_xmit:
Nov  9 04:26:25.591: //110/2F8D5A000000/VOIPRTP:():voip_rtp_send_pak:
Nov  9 04:26:25.821: //110/2F8D5A000000/VOIPRTP:():voip_rtp_xmit:
Nov  9 04:26:25.821: //110/2F8D5A000000/VOIPRTP:():voip_rtp_send_pak:
Nov  9 04:26:25.841: //110/2F8D5A000000/VOIPRTP:():voip_rtp_xmit:
Nov  9 04:26:25.841: //110/2F8D5A000000/VOIPRTP:():voip_rtp_send_pak:
Nov  9 04:26:25.861: //110/2F8D5A000000/VOIPRTP:():voip_rtp_xmit:
Nov  9 04:26:25.861: //110/2F8D5A000000/VOIPRTP:():voip_rtp_send_pak:
Nov  9 04:26:25.881: //110/2F8D5A000000/VOIPRTP:():voip_rtp_xmit:
Nov  9 04:26:25.881: //110/2F8D5A000000/VOIPRTP:():voip_rtp_send_pak:
Nov  9 04:26:25.901: //110/2F8D5A000000/VOIPRTP:():voip_rtp_xmit:
Nov  9 04:26:25.901: //110/2F8D5A000000/VOIPRTP:():voip_rtp_send_pak:
Nov  9 04:26:25.921: //110/2F8D5A000000/VOIPRTP:():voip_rtp_xmit:
Nov  9 04:26:25.921: //110/2F8D5A000000/VOIPRTP:():voip_rtp_send_pak:
Nov  9 04:26:25.931: //110/2F8D5A000000/VOIPRTP:():voip_rtp_xmit:
Nov  9 04:26:25.931: //110/2F8D5A000000/VOIPRTP:():voip_rtp_send_pak:
Nov  9 04:26:25.931: //110/2F8D5A000000/VOIPRTP:():voip_rtp_xmit:
Nov  9 04:26:25.931: //110/2F8D5A000000/VOIPRTP:():voip_rtp_send_pak:
Nov  9 04:26:25.931: //110/2F8D5A000000/VOIPRTP:():voip_rtp_xmit:
Nov  9 04:26:25.931: //110/2F8D5A000000/VOIPRTP:():voip_rtp_send_pak:
Nov  9 04:26:29.013: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

DTMF method is negotiated, here is SDP fom OK message:

v=0
o=CiscoSystemsSIP-GW-UserAgent 4509 9863 IN IP4 100.123.15.1
s=SIP Call
c=IN IP4 100.123.10.18
t=0 0
m=audio 8208 RTP/AVP 8 101
c=IN IP4 100.123.10.18
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20

I see correct debug if I route a call to CSR 1000v with the same config so it is a bug or debug syntax has changed.

Maren Mahoney · ‎11-09-2021

That's why I was asking what you see in your C8000V if you type in "debug voip rtp ?" What are the additional syntax options? If "debug voip rtp session named-event 101" is there as an available command, I would guess you are running into a bug. If it is not there as an available command, what are the other commands that are available? We may be able to find a different command that gives you the information you need.

Maren

Maxim Denisov · ‎11-09-2021

I misunderstood you, debug command is correct but not working.

COBALT-RTR#debug voip rtp ?
  all                Enable All VOIP RTP debugging
  default            Activates inout, error, and function debugs
  error              Enable VOIP RTP Error debugging trace
  function           Procedure tracing
  high-availability  VOIPRTP high-availability debugs
  individual         Activation of individual VOIP RTP debugs
  inout              Subsystem inout debugging
  packet             Enable VOIP RTP Packet debugging trace
  recvfail           simulating rtp recv failure
  sendfail           simulating rtp send failure
  session            Enable VOIP RTP Session debugging trace
  statistics         Enable VOIP RTP Statistics debugging trace
  <cr>               <cr>

COBALT-RTR#debug voip rtp session named-event ?
  <98-117>  payload value
  <cr>      <cr>

Maren Mahoney · ‎11-10-2021

Hmmm... I don't know the answer. As you suggested, if the command is there but showing no useful output you are probably running into a bug...which makes your next step contacting TAC. I wish I could have been more help.

Maren