CUBE / IP-IP gateway: slow (4 seconds) translation from H.245 DTMF to RTP NTE

Unanswered Question
Mar 30th, 2010

I just opened a TAC case on it too, but I'm wondering if anyone here run into this before. I am having a problem with a CUBE gateway. It's a 2811 running latest 12.4(24)T3.

Incoming call leg is from H.323 Avaya gateway that is sending DTMF using out of band H.245 signalling. I can see those in "debug h245 asn1". The outgoing call leg is to an Oracle CCA call center that is expecting RFC2833 RTP NTE DTMF. I can see those messages sent from CUBE with "debug voip rtp session event". So CUBE is doing translation just fine, the only problem is that it takes 4 seconds to do the translation. There's a 4 second gap between the H.245 debug message and the RTP NTE debug message. Users are reporting similar behavior, they press a digit and it takes 4 seconds before IVR responds to input.

The inbound dial-peer is configured for h.245-alphanumeric for dtmf-relay. Here's the outbound dial-peer:

dial-peer voice 100 voip
destination-pattern ^8[0,6,7,8]........$
voice-class sip asymmetric payload dtmf
session protocol sipv2
session target ipv4:10.0.0.1

dtmf-relay rtp-nte digit-drop
codec g711ulaw
ip qos dscp cs5 signaling
no vad

here's the debug

Mar 30 22:23:06.229: h323chan_chn_process_read_socket: fd=5 of type CONNECTED has data

Mar 30 22:23:06.229: H245 MSC INCOMING ENCODE BUFFER::= 6D810426200064
Mar 30 22:23:06.229:
Mar 30 22:23:06.229: H245 MSC INCOMING PDU ::=

value MultimediaSystemControlMessage ::= indication : userInput : signal :
    {
      signalType "1"
      rtp
      {
        logicalChannelNumber 101
      }
    }

Mar 30 22:23:06.229: h245_decode_remote_message: received Indication PDU
Mar 30 22:23:06.229: h245_decode_remote_indication: received User Input message

<<< 4 SECOND GAP !!!!! >>>

Mar 30 22:23:10.029:          s=DSP d=VoIP payload 0x65 ssrc 0x47D8AE71 sequence 0x1C9 timestamp 0x12160
Mar 30 22:23:10.029:          Pt:101    Evt:1       Pkt:04 00 00  <Snd>>>
Mar 30 22:23:10.029:          s=DSP d=VoIP payload 0x65 ssrc 0x47D8AE71 sequence 0x1CA timestamp 0x12160
Mar 30 22:23:10.029:          Pt:101    Evt:1       Pkt:04 00 00  <Snd>>>
Mar 30 22:23:10.029:          s=DSP d=VoIP payload 0x65 ssrc 0x47D8AE71 sequence 0x1CB timestamp 0x12160
Mar 30 22:23:10.029:          Pt:101    Evt:1       Pkt:04 00 00  <Snd>>>
Mar 30 22:23:10.029:          s=DSP d=VoIP payload 0x65 ssrc 0x47D8AE71 sequence 0x1CC timestamp 0x12160
Mar 30 22:23:10.029:          Pt:101    Evt:1       Pkt:04 01 90  <Snd>>>
Mar 30 22:23:10.029:          s=DSP d=VoIP payload 0x65 ssrc 0x47D8AE71 sequence 0x1CD timestamp 0x12160
Mar 30 22:23:10.029:          Pt:101    Evt:1       Pkt:84 03 20  <Snd>>>
Mar 30 22:23:10.029:          s=DSP d=VoIP payload 0x65 ssrc 0x47D8AE71 sequence 0x1CE timestamp 0x12160
Mar 30 22:23:10.029:          Pt:101    Evt:1       Pkt:84 03 20  <Snd>>>
Mar 30 22:23:10.029:          s=DSP d=VoIP payload 0x65 ssrc 0x47D8AE71 sequence 0x1CF timestamp 0x12160
Mar 30 22:23:10.029:          Pt:101    Evt:1       Pkt:84 03 20  <Snd>>>


Has anyone seen this before?

Thanks

Roman

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
goranpilat Mon, 11/19/2012 - 05:33

Hi,

I am facing exactly the same issue, did you maybe manage to resolve it?

Best regards

Goran

Actions

This Discussion