[Home]

Summary:ASTERISK-06173: * has lots of warnings when get rfc2833 dtmf from HuaweiSoftX3000 softswitch
Reporter:adomjan (adomjan)Labels:
Date Opened:2006-01-23 14:17:09.000-0600Date Closed:2006-02-14 14:27:12.000-0600
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Channels/chan_sip/CodecHandling
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) rtpdebug
( 1) sipdebug
Description:I think this related with the ASTERISK-5300576 closed bug.
I enabled only alaw, ulaw codecs.

Jan 23 22:15:00 WARNING[13841]: codec_ilbc.c:175 ilbctolin_framein: Huh?  An ilbc frame that isn't a multiple of 50 bytes long from RTP (4)?
Jan 23 22:15:00 WARNING[13841]: codec_ilbc.c:175 ilbctolin_framein: Huh?  An ilbc frame that isn't a multiple of 50 bytes long from RTP (4)?
Jan 23 22:15:00 WARNING[13841]: codec_ilbc.c:175 ilbctolin_framein: Huh?  An ilbc frame that isn't a multiple of 50 bytes long from RTP (4)?
Jan 23 22:15:00 WARNING[13841]: codec_ilbc.c:175 ilbctolin_framein: Huh?  An ilbc frame that isn't a multiple of 50 bytes long from RTP (4)?
Jan 23 22:15:00 WARNING[13841]: codec_ilbc.c:175 ilbctolin_framein: Huh?  An ilbc frame that isn't a multiple of 50 bytes long from RTP (4)?
Jan 23 22:15:00 WARNING[13841]: codec_ilbc.c:175 ilbctolin_framein: Huh?  An ilbc frame that isn't a multiple of 50 bytes long from RTP (4)?
Jan 23 22:15:00 WARNING[13841]: codec_ilbc.c:175 ilbctolin_framein: Huh?  An ilbc frame that isn't a multiple of 50 bytes long from RTP (4)?
Jan 23 22:15:00 WARNING[13841]: codec_ilbc.c:175 ilbctolin_framein: Huh?  An ilbc frame that isn't a multiple of 50 bytes long from RTP (4)?
Jan 23 22:15:00 WARNING[13841]: codec_ilbc.c:175 ilbctolin_framein: Huh?  An ilbc frame that isn't a multiple of 50 bytes long from RTP (4)?
Comments:By: Serge Vecher (serge-v) 2006-01-23 15:06:05.000-0600

adomjan: you need to attach the appropriate trace for the channel you are using, as well as RTP debug.
By: adomjan (adomjan) 2006-01-23 15:25:14.000-0600

ok I uploaded the output of the sip debug and interesting part of rtp debug.
By: Olle Johansson (oej) 2006-01-24 03:33:33.000-0600

For some reason, the device is sending type 97 (iLBC) packets when it's supposed to send only aLAW. Oops. It redefines RFC2833 dtmf events as type 97. Interesting. We still treat them as iLBX when we should treat them as dtmf. Clearly a bug.
By: Olle Johansson (oej) 2006-01-24 03:35:35.000-0600

m=audio 9104 RTP/AVP 8 97
a=rtpmap:8 PCMA/8000
a=rtpmap:97 telephone-event/8000

If you can move the DTMF/RFC2833 to 101 instead of 97, it will work. (That's a workaround, not a fix.)
By: Olle Johansson (oej) 2006-01-24 04:00:57.000-0600

Could not repeat this with trunk.
By: Olle Johansson (oej) 2006-01-24 04:09:38.000-0600

Notes from test with trunk:

Got RTP packet from 127.0.0.1:8000 (type 97, seq 139, ts 19200, len 4)
Got rfc2833 RTP packet from 127.0.0.1:8000 (type 97, seq 139, ts 19200, len 4, mark 0, event 00000001, end 1, duration 2880)
Jan 24 12:07:31 DEBUG[8632]: rtp.c:274 process_rfc2833: - RTP 2833 Event: 00000001 (len = 4)


Side not, xlite sends this when configuring RFC2833 as 97:

m=audio 8000 RTP/AVP 0 8 3 98 97 97
a=rtpmap:0 pcmu/8000
a=rtpmap:8 pcma/8000
a=rtpmap:3 gsm/8000
a=rtpmap:98 iLBC/8000
a=rtpmap:97 speex/8000
a=rtpmap:97 telephone-event/8000


Obviously a bug - they need to redefine speex in that case :-)


By: Olle Johansson (oej) 2006-01-24 04:19:41.000-0600

Could not repeat this with 1.2 svn either.
By: Olle Johansson (oej) 2006-01-24 04:20:52.000-0600

See the difference now, I was calling *to* asterisk and you are calling *from* asterisk. Will try again.
By: Olle Johansson (oej) 2006-01-24 04:38:44.000-0600

Tried with asterisk calling to Xlite, asterisk using 101 for dtmf and Xlite responding with 97 for dtmf. Sending DTMF from Xlite was parsed as DTMF in asterisk.

Can not repeat the problem.

Check which version of Asterisk you are running, please.
By: adomjan (adomjan) 2006-01-24 05:10:03.000-0600

pbx0*CLI> show version
Asterisk SVN-branch-1.2-r8437M built by root @ pbx0 on a x86_64 running Linux on 2006-01-22 18:17:14 UTC

it's the same when I call the asterisk and I call from tha asterisk. Bye the way asterisk understand the rfc2833 dtmf with these warnings.

the other side operated by my provider, so I can't change anything on other side.
By: Olle Johansson (oej) 2006-01-30 12:18:18.000-0600

Weird that I can't see it in 1.2, but you can.
By: Kevin P. Fleming (kpfleming) 2006-02-14 14:27:11.000-0600

This is not an Asterisk bug. Asterisk clearly told the other end that it wanted to receive RFC2833 as format number 101, but the other end sent it as format number 97 anyway.