11.5.1.1. ast_rtp_read: Unknown RTP codec X received
1) Unknown RTP codec 96 received:
2) Unknown RTP codec 57 received:
3) Unknown RTP codec 72 received:
4) Unknown RTP codec 19 received:
5) Unknown RTP codec 85 received:
6) Unknown RTP codec 100 received:
You probably connected some fax to some ATA, and then try to send faxes over t.30 to asterisk, this is not good, this fails in almost all cases.
The real solution is to use a t.38 enabled ATA and patch asterisk to use t.38.
references:
7) Lots of lines with different unknown codecs received:
Same as the problem above, you probably tried to connect some fax to an ATA, this is what might happen during the fax training.
ATA's are not made to be connected to faxes unless they are t.38 capable.
If it doesn't work, give up now, its not meant to be used like that.
------------------
If you know of any other unknown codec errors, please post them here. (and if you find the solution later, come back and post the solution please!!!!).
If you are getting messages such as the one below, chances are big you are trying to connect to a Cirpack/v4.39a (gw_sip) sip gateway or to a Mediatrix 1124 gateway
This is because those 2 devices for some reason decide to send DTMF as a dynamic payload type 96, and asterisk expects the DTMF to have number 101 or 121.
We can easily fix this with a one line patch to rtp.c
Look for:
and change this to:
now recompile asterisk, and everything should work fine.
References:
Dec 24 10:57:40 NOTICE[5570]: rtp.c:564 ast_rtp_read: Unknown RTP codec 96 received
This is because those 2 devices for some reason decide to send DTMF as a dynamic payload type 96, and asterisk expects the DTMF to have number 101 or 121.
We can easily fix this with a one line patch to rtp.c
Look for:
[34] = {1, AST_FORMAT_H263},
[103] = {1, AST_FORMAT_H263_PLUS},
[97] = {1, AST_FORMAT_ILBC},
[101] = {0, AST_RTP_DTMF},
[110] = {1, AST_FORMAT_SPEEX},
[103] = {1, AST_FORMAT_H263_PLUS},
[97] = {1, AST_FORMAT_ILBC},
[101] = {0, AST_RTP_DTMF},
[110] = {1, AST_FORMAT_SPEEX},
and change this to:
[34] = {1, AST_FORMAT_H263},
[103] = {1, AST_FORMAT_H263_PLUS},
[96] = {0, AST_RTP_DTMF},
[97] = {1, AST_FORMAT_ILBC},
[101] = {0, AST_RTP_DTMF},
[110] = {1, AST_FORMAT_SPEEX},
[103] = {1, AST_FORMAT_H263_PLUS},
[96] = {0, AST_RTP_DTMF},
[97] = {1, AST_FORMAT_ILBC},
[101] = {0, AST_RTP_DTMF},
[110] = {1, AST_FORMAT_SPEEX},
now recompile asterisk, and everything should work fine.
References:
http://www.asteriskguru.com/archives/asterisk-users-asterisk-devel-mediatrix-dtmf-bug-solved-vt13784.html
http://www.ethereal.com/lists/ethereal-users/200408/msg00043.html
http://www.freesoft.org/CIE/RFC/1890/29.htm
http://www.iana.org/assignments/rtp-parameters
http://www.ethereal.com/lists/ethereal-users/200408/msg00043.html
http://www.freesoft.org/CIE/RFC/1890/29.htm
http://www.iana.org/assignments/rtp-parameters
2) Unknown RTP codec 57 received:
seems to happen on SPA
http://www.asterisknerds.com/logs/irclogger_log/asterisk?date=2005-05-05,Thu&text=on
http://www.asterisknerds.com/logs/irclogger_log/asterisk?date=2005-05-05,Thu&text=on
3) Unknown RTP codec 72 received:
I've never seen this one myself, but by googling around this is probably:
1) you are using info for DTMF with xlite. (unconfirmed)
2) you are using an asterisk version older than 12-06-04 and have allow=all (which means you should upgrade)
3) Most probable: something is sending RTCP packets in the RTP datastream to asterisk and asterisk doesn't know what to do with it.
references:
http://bugs.digium.com/bug_view_advanced_page.php?bug_id=2945
http://www.asteriskguru.com/archives/asterisk-users-unknown-rtp-codec-72-received-vt21186.html
http://www.asteriskguru.com/archives/asterisk-users-error-unknown-rtp-codec-72-received-vt27771.html
http://www.ietf.org/rfc/rfc3550.txt
http://voxilla.com/forum-viewtopic-t-4475.html
1) you are using info for DTMF with xlite. (unconfirmed)
2) you are using an asterisk version older than 12-06-04 and have allow=all (which means you should upgrade)
3) Most probable: something is sending RTCP packets in the RTP datastream to asterisk and asterisk doesn't know what to do with it.
To get rid of this, turn of symmetric RTP. (turn NAT to no, but still use externip if you are using the sip client behind a nat).
If you are using xlite, you can also try to turn it off in the phone settings,
the setting is in Main Menu > Advanced System Settings > RTP Settings > Obey Reverse UDP Mapping Rules = NO.
and
Xten menu > Advanced Settings > RTP Settings > Send RTCP messages = NO
You might need to use stun to make it work without symmetric RTP.
If you are using xlite, you can also try to turn it off in the phone settings,
the setting is in Main Menu > Advanced System Settings > RTP Settings > Obey Reverse UDP Mapping Rules = NO.
and
Xten menu > Advanced Settings > RTP Settings > Send RTCP messages = NO
You might need to use stun to make it work without symmetric RTP.
references:
http://bugs.digium.com/bug_view_advanced_page.php?bug_id=2945
http://www.asteriskguru.com/archives/asterisk-users-unknown-rtp-codec-72-received-vt21186.html
http://www.asteriskguru.com/archives/asterisk-users-error-unknown-rtp-codec-72-received-vt27771.html
http://www.ietf.org/rfc/rfc3550.txt
http://voxilla.com/forum-viewtopic-t-4475.html
4) Unknown RTP codec 19 received:
This one seems to be a problem similar to unknown codec 96 received (see above).
It appears when DTMF is being sent on the PSTN phone connected to a cisco as5350, and sent to asterisk over RTP Named Telephone Event (RFC 2833).
The solution is probably a patch as in the unknown codec 96, or reconfiguring the cisco gateway.
(please let us know how you fixed this, if you encounter this problem)
references:
It appears when DTMF is being sent on the PSTN phone connected to a cisco as5350, and sent to asterisk over RTP Named Telephone Event (RFC 2833).
The solution is probably a patch as in the unknown codec 96, or reconfiguring the cisco gateway.
(please let us know how you fixed this, if you encounter this problem)
references:
5) Unknown RTP codec 85 received:
I only found one reference to this problem, possibly a problem where allow=all is used. (don't use that)
If that doesn't fix it, try upgrading your asterisk, chances are big the problem is already fixed.
If you experience this problem and can or cannot fix it, please let us know!!!!
references:
If that doesn't fix it, try upgrading your asterisk, chances are big the problem is already fixed.
If you experience this problem and can or cannot fix it, please let us know!!!!
references:
6) Unknown RTP codec 100 received:
You probably connected some fax to some ATA, and then try to send faxes over t.30 to asterisk, this is not good, this fails in almost all cases.
The real solution is to use a t.38 enabled ATA and patch asterisk to use t.38.
references:
7) Lots of lines with different unknown codecs received:
Same as the problem above, you probably tried to connect some fax to an ATA, this is what might happen during the fax training.
ATA's are not made to be connected to faxes unless they are t.38 capable.
If it doesn't work, give up now, its not meant to be used like that.
------------------
If you know of any other unknown codec errors, please post them here. (and if you find the solution later, come back and post the solution please!!!!).