[asterisk-dev] T.38 Fax issues on 1.6.1.14
Bryant Zimmerman
BryantZ at zktech.com
Wed Feb 10 11:54:23 CST 2010
I moved to the 1.6.1.14 version due to the concernes with T.38 security
issues. I was on version 1.6.1.10
Now I am having issues sending faxes. From audiocodes mp-202 units. They
can receive faxes via t.38 but can not send. When sending a fax I get
== Using SIP RTP CoS mark 5
== Using SIP VRTP CoS mark 6
== Using UDPTL CoS mark 5
-- Called zkt_wmis_gr44_gw2001/13125873146
-- SIP/zkt_wmis_gr44_gw2001-00000800 is ringing
-- SIP/zkt_wmis_gr44_gw2001-00000800 answered
SIP/gr2006lksw0001-fax-000007f
f
-- Native bridging SIP/gr2006lksw0001-fax-000007ff and
SIP/zkt_wmis_gr44_gw2
001-00000800
[Feb 10 12:40:48] NOTICE[23901]: rtp.c:1796 ast_rtp_read: Unknown RTP codec
102
received from '75.12.95.xxx'
[Feb 10 12:40:48] NOTICE[23901]: rtp.c:1796 ast_rtp_read: Unknown RTP codec
102
received from '75.12.95.xxx'
[Feb 10 12:40:48] NOTICE[23901]: rtp.c:1796 ast_rtp_read: Unknown RTP codec
102
received from '75.12.95.xxx'
[Feb 10 12:40:48] NOTICE[23901]: rtp.c:1796 ast_rtp_read: Unknown RTP codec
102
received from '75.12.95.xxx'
[Feb 10 12:40:48] NOTICE[23901]: rtp.c:1796 ast_rtp_read: Unknown RTP codec
102
I then get a report response from the fax machine that there was too much
line nose.
It looks to me like the devices are now not getting the conversion to T.38
on outbound now.
Any ideas?
Thanks
Bryant
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-dev/attachments/20100210/9e4ef177/attachment-0001.htm
More information about the asterisk-dev
mailing list