[asterisk-bugs] [Asterisk 0016485]: after udp error sip phones get kicked
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Jan 11 21:12:15 CST 2010
The following issue requires your FEEDBACK.
======================================================================
https://issues.asterisk.org/view.php?id=16485
======================================================================
Reported By: elsto
Assigned To: dvossel
======================================================================
Project: Asterisk
Issue ID: 16485
Category: Channels/chan_sip/T.38
Reproducibility: always
Severity: crash
Priority: normal
Status: feedback
Target Version: 1.6.1.14
Asterisk Version: 1.6.1.12
JIRA: SWP-574
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-12-21 06:28 CST
Last Modified: 2010-01-11 21:12 CST
======================================================================
Summary: after udp error sip phones get kicked
Description:
I get the following error message;
udptl.c:766 calculate_far_max_ifp: (no tag): Cannot calculate far_max_ifp
before far_max_datagram has been set.
udptl.c:725 calculate_local_max_datagram: (SIP/0887865299): Cannot
calculate local_max_datagram before local_max_ifp has been set
astobj2.c:116 INTERNAL_OBJ: bad magic number 0x0 for 0x227bfb8
The fax does arrive at the destination, but strangely all my sip phones
get kicked and unregister.
I have to restart asterisk do get the sip phones back to register
I've set in sip.conf under global;
t38pt_udptl = yes,fec,maxdatagram=400
======================================================================
----------------------------------------------------------------------
(0116488) dvossel (administrator) - 2010-01-11 21:12
https://issues.asterisk.org/view.php?id=16485#c116488
----------------------------------------------------------------------
geokill, thanks for the backtrace. It looks like you may have not compiled
with don't optimize enabled. Please run make menuselect and enable don't
optimize, this is an option under compile flags I believe. After compiling
with don't optimize please update the issue with a new gdb output of the
crash.
Without this it is difficult to tell anything from the gdb output because
all the values are missing. Thanks!
Issue History
Date Modified Username Field Change
======================================================================
2010-01-11 21:12 dvossel Note Added: 0116488
2010-01-11 21:12 dvossel Status assigned => feedback
======================================================================
More information about the asterisk-bugs
mailing list