[asterisk-bugs] [Asterisk 0018993]: issue with Asterisk 1.4.30 and T38 passthrough
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Apr 1 12:58:48 CDT 2011
The following issue has been UPDATED.
======================================================================
https://issues.asterisk.org/view.php?id=18993
======================================================================
Reported By: michel
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 18993
Category: Channels/chan_sip/T.38
Reproducibility: always
Severity: major
Priority: normal
Status: feedback
Asterisk Version: Older 1.4 - please test a newer version
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2011-03-18 07:37 CDT
Last Modified: 2011-04-01 12:58 CDT
======================================================================
Summary: issue with Asterisk 1.4.30 and T38 passthrough
Description:
This is my set up:
analog fax machine (fax #:224176701) <> Avaya IP office 500 PBX <>
Asterisk <> VOIP provider (netia).
We are trying to set up fax pass-through for Asterisk. There is an analog
fax machine attached to the Avaya PBX (192.168.10.242) which in turn is
communicating with Asterisk. All the in/out communication goes through the
Asterisk (192.168.10.231). Avaya is et up to support G.711 (ulaw,alaw) and
G.729 if this matters in any way.
extensions.conf is correctly configured.
This is sip.conf for Avaya:
-----------------------------------
[avaya]
type = friend
host = 192.168.10.242
qualify = no
context = from-avaya
canreinvite = no
disallow = all
allow = alaw
; added
allow = g729
t38udptlsupport = yes
t38pt_udptl = yes
t38pt_rtp = no
t38pt_tcp = no
-----------------------------------
This is udptl.conf:
-----------------------------------
; UDPTL Configuration (UDPTL is one of the transports for T.38)
;
[general]
;
; UDPTL start and UDPTL end configure start and end addresses
;
udptlstart=4000
udptlend=4999
;
; Whether to enable or disable UDP checksums on UDPTL traffic
;
;udptlchecksums=no
;
; The error correction type to be sent
;
; T38FaxUdpEC = t38UDPFEC
T38FaxUdpEC = t38UDPRedundancy
;
; The maximum length of a UDPTL packet
;
T38FaxMaxDatagram = 400
;
; The number of error correction entries in a UDPTL packet
;
;udptlfecentries = 3
udptlfecentries = 1
;
; The span over which parity is calculated for FEC in a UDPTL packet
;
udptlfecspan = 3
;
; Some VoIP providers will only accept an offer with an even-numbered
; UDPTL port. Set this option so that Asterisk will only attempt to use
; even-numbered ports when negotiating T.38. Default is no.
use_even_ports = yes
-----------------------------------
When we try to send a fax (fax number 224176701), we hear the typical "fax
beeping", but then we get a "communication error".
I have gathered few logs, here they are:
- tshark on asterisk (192.168.10.231):
1: 264.945761 192.168.10.231 -> 192.168.10.242 SIP/SDP Request: INVITE
sip:224176701 at 192.168.10.242, with session description
2: 264.951583 192.168.10.242 -> 192.168.10.231 SIP Status: 100 Trying
3: 264.962531 192.168.10.242 -> 192.168.10.231 SIP Status: 180 Ringing
4: 266.119080 192.168.10.242 -> 192.168.10.231 SIP/SDP Status: 200 Ok,
with session description
5: 266.119326 192.168.10.231 -> 192.168.10.242 SIP Request: ACK
sip:224176701 at 192.168.10.242:5060;transport=udp
6: 272.880566 192.168.10.242 -> 192.168.10.231 SIP Request: OPTIONS
sip:Unknown at 192.168.10.231
7: 272.880830 192.168.10.231 -> 192.168.10.242 SIP Status: 404 Not Found
8: 273.640571 192.168.10.242 -> 192.168.10.231 SIP/SDP Request: INVITE
sip:225401522 at 192.168.10.231, with session description
9: 273.640996 192.168.10.231 -> 192.168.10.242 SIP Status: 488 Not
acceptable here
10: 273.644819 192.168.10.242 -> 192.168.10.231 SIP Request: ACK
sip:225401522 at 192.168.10.231
11: 273.647558 192.168.10.242 -> 192.168.10.231 SIP Request: BYE
sip:225401522 at 192.168.10.231
12: 273.647716 192.168.10.231 -> 192.168.10.242 SIP Status: 200 OK
Request from asterisk to Avaya seems fine, but then in line 9, it looks
like asterisk is not accepting the Request from Avaya (FYI: 225401522 is
the callee).
Line 6 and 7 I think are irrelevant for our case.
- Asterisk in command line shows when trying to send a fax to the fax
machine (https://issues.asterisk.org/view.php?id=224176701):
Asterisk*CLI>
-- Executing [224176701 at from-pstn:1] NoOp("SIP/netia-00000d74",
"Inbound DDI 224176701 - Forwarding to avaya") in new stack
-- Executing [224176701 at from-pstn:2] Dial("SIP/netia-00000d74",
"SIP/avaya/224176701") in new stack
-- Called avaya/224176701
-- SIP/avaya-00000d75 is ringing
-- SIP/avaya-00000d75 answered SIP/netia-00000d74
-- Packet2Packet bridging SIP/netia-00000d74 and SIP/avaya-00000d75
[Mar 15 11:41:45] NOTICE[591]: chan_sip.c:5632 process_sdp: No compatible
codecs, not accepting this offer!
== Spawn extension (from-pstn, 224176701, 2) exited non-zero on
'SIP/netia-00000d74'
Looking at the last two lines, It seems like Avaya and Asterisk do not
agree on which codec to use!
Thanks for any help on this subject.
Michel.
======================================================================
----------------------------------------------------------------------
(0133282) lmadsen (administrator) - 2011-04-01 12:58
https://issues.asterisk.org/view.php?id=18993#c133282
----------------------------------------------------------------------
We'll need to see a SIP trace from the Asterisk console along with DEBUG
level logging. Please provide this information so we can move the issue
forward.
Thanks!
Issue History
Date Modified Username Field Change
======================================================================
2011-04-01 12:58 lmadsen Note Added: 0133282
======================================================================
More information about the asterisk-bugs
mailing list