[asterisk-bugs] [JIRA] (ASTERISK-27061) sigseg during t.38 reinvite / negotiation
Asterisk Team (JIRA)
noreply at issues.asterisk.org
Sun Jun 18 10:31:58 CDT 2017
[ https://issues.asterisk.org/jira/browse/ASTERISK-27061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237469#comment-237469 ]
Asterisk Team commented on ASTERISK-27061:
------------------------------------------
Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.
A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.
Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].
> sigseg during t.38 reinvite / negotiation
> -----------------------------------------
>
> Key: ASTERISK-27061
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-27061
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Affects Versions: 13.16.0
> Environment: Centos 6, 64 bit
> Reporter: Michael Maier
>
> sigseg happens during sending of a fax / t.38 the following way:
> fax client -> asterisk -> telekom -> easybell -> asterisk -> fax server
> Fax server sends t.38 reinvite via asterisk to easybell.
> Session Description Protocol Version (v): 0
> Owner/Creator, Session Id (o): - 2447581897 4 IN IP4 46.17.15.23
> Session Name (s): Asterisk
> Connection Information (c): IN IP4 46.17.15.23
> Time Description, active time (t): 0 0
> Media Description, name and address (m): image 4573 udptl t38
> Media Attribute (a): T38FaxVersion:0
> Media Attribute (a): T38MaxBitRate:14400
> Media Attribute (a): T38FaxRateManagement:transferredTCF
> Media Attribute (a): T38FaxMaxDatagram:397
> Media Attribute (a): T38FaxUdpEC:t38UDPRedundancy
> This reinvite is received by asterisk via telekom:
> Session Description Protocol Version (v): 0
> Owner/Creator, Session Id (o): - 1811299599 2925027276 IN IP4 0.0.0.0
> Session Name (s): -
> Time Description, active time (t): 0 0
> Media Description, name and address (m): image 0 udptl t38
> Media Attribute (a): sendrecv
> Media Attribute (a): T38FaxVersion:0
> Media Attribute (a): T38MaxBitRate:14400
> Media Attribute (a): T38FaxRateManagement:transferredTCF
> Media Attribute (a): T38FaxMaxDatagram:397
> Media Attribute (a): T38FaxUdpEC:t38UDPRedundancy
> And asterisk gives it to the fax client:
> Session Description Protocol Version (v): 0
> Owner/Creator, Session Id (o): - 1497774025 5 IN IP4 192.168.12.13
> Session Name (s): Asterisk
> Connection Information (c): IN IP4 192.168.12.13
> Time Description, active time (t): 0 0
> Media Description, name and address (m): image 4284 udptl t38
> Media Attribute (a): T38FaxVersion:0
> Media Attribute (a): T38MaxBitRate:14400
> Media Attribute (a): T38FaxRateManagement:transferredTCF
> Media Attribute (a): T38FaxMaxDatagram:393
> Media Attribute (a): T38FaxUdpEC:t38UDPRedundancy
> Completely ignoring, that telekom doesn't support it (port and ip
> addresses are set to 0).
> On completing the negotiation after 200 ok SDP and ACK from fax client,
> asterisk crashes. Stack trace and asterisk log is attached!
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list