Getting channel 'SIP/192.168.1.69-00000000' refused to negotiate T.38

Report
Question

Hi, I recently configured T.38 on Asterisk 10.4.2. When I send the fax to
Asterisk, it gives the errors as listed below; WARNING[25986]: app_fax.c:442 transmit_audio: channel
'SIP/192.168.1.69-00000000' refused to negotiate T.38
WARNING[25986]: app_fax.c:174 span_message: WARNING T.30 ECM carrier not
found As in sip.conf the configuration is listed below; t38pt_udptl = yes,fec,maxdatagram=400
faxdetect = t38 And the rest are the standard configuration. Please advise to resolve this issue.

Asterisk Users 3.1 years ago 4 Answers

asterisk-users Digest, Vol 95, Issue 20

Report
Question

Anybody, can you please share your thoughts to overcome this issue?
> Hi,
>
> I'm getting error: ' FAX session '9' is complete, result: 'FAILED'
> (FAX_FAILURE_PARTIAL), error: '3RD_T2_TIMEOUT', pages: 1, resolution:
> '204x196', transfer rate: '9600', remoteSID: '' ' when I tried send fax
> more than 2 pages to Asterisk using T.38.
>
> First I set speed rate to 14400 which I was getting same error message
> while sending 2 fax pages document. Later I set the speed rate for sending
> fax machine…

Asterisk Users 3.1 years ago 0 Answers

destroying time

Report
Question

Hello, Please forgive me if I'm repeating this post.
I have searched and looked for similar question but have not seen a similar
one. When I do call from client to Asterisk 1.8, I do follows. 1. REGISTER
2. INVITE
3. call established
4. Bye
5. call ended After the call ended, my client receive the message like this. "Really destroying SIP dialog '54c09c884a61e39140a2358a5adb7d96@192.168.1.2'
Method: REGISTER"
And at least after 30sec, my client disconnect from Asterisk.
I have to do REGISTER again. I think this message means that "Asterisk will…

Asterisk Users 3.1 years ago 2 Answers

Skinny Channel Driver Remote Crash Vulnerability

Report
Question

A previously developed patch dealt with a denial of service attack exploitable in the Skinny channel driver that occurred when certain messages are sent after a previously registered station sends an Off Hook message. Unresolved in that patch is an issue in the Asterisk 10 releases, wherein, if a Station Key Pad Button Message is processed after an Off Hook message, the channel driver will inappropriately dereference a Null pointer. Similar to the problem solved with the previous patch, a remote attacker with a valid SCCP ID can use this vulnerability by closing a connection to the Asterisk server when a station is in the "Off Hook" call state and…

VoIP News 3.1 years ago 0 Answers

Asterisk 10.5.1 Now Available (Security Release)

Report
Question

The Asterisk Development Team has announced a security release for Asterisk 10.
This security release is released as version 10.5.1. The release is available for immediate download at
http://downloads.asterisk.org/pub/telephony/asterisk/releases The release of Asterisk 10.5.1 resolves the following issue: * A remotely exploitable crash vulnerability was found in the Skinny (SCCP)
Channel driver. When an SCCP client sends an Off Hook message, followed by
a Key Pad Button Message, a structure that was previously set to NULL is
dereferenced. This allows remote authenticated connections the ability to
cause a crash in the server,…

Asterisk Users 3.1 years ago 0 Answers