Age | Commit message (Collapse) | Author | Files | Lines |
|
instead of blindly assuming it was. (issue #10112 reported by makoto)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@73318 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
each time... otherwise we will get previous values. (issue #10117 reported by noriyuki)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@73315 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
setuped on inbound calls too.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@73252 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
state wasn't changed..
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@73207 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
distinguish between 0 and error (closes issue #10106)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@73052 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
channels.. #9449
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@73004 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
time format.
Issue 10101
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@72924 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
newline just in case the original call file did not have a newline at the end.
This fix is in response to a problem I saw reported on the asterisk-users
mailing list.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@72805 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
until the three-way call setup is completed. These changes are already in 1.4
and trunk.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@72629 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
time. Also added a release_chan lock, so that the same chan_list object cannot be freed twice. chan_misdn does not crash anymore on heavy load with these changes.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@72585 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
reported by netoguy)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@72378 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
development branch without it and mistakenly thought it wasn't fixed.
Fixes issue #10010, and #9654: 100% CPU usage caused by an asterisk console losing it's controlling terminal.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@72373 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@72333 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
mtryfoss)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@72327 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
whitespace as you want around a numeric priority, but you couldn't have any
whitespace around a special priority like "n" or "hint".
(issue #10039, reported by mitheloc, fixed by me)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@72267 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
Issue #9654, #10010
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@72259 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
after the channel has been dealt with. This should eliminate all of the issues with channels going funky (SIP/PRI) when you are posting CDRs to a database that is either slow or unavailable and do not want to enable batching.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@72256 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
Issue 10074, patch by kryptolus, extended to include #if 0'd blocks (just in case)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@72184 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
they are not used later as real-bchannels, optimized the RESTART mechanisms, we block a channel now on cause:44, and send out a RESTART automatically, then on reception of RESTART_ACKNOWLEDGE we unblock the channel again.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@72099 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
areas.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@72087 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@72041 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
CONNECT_ACKNOWLEDGE, to make sure mISDN has everything ready. removed some #if 0 areas which weren't used anymore.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@72040 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
Reported to me on #asterisk on Freenode IRC.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@71847 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
in memory corruption
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@71750 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
other AGI commands
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@71656 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
#10041 reported by homesick)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@71414 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@71358 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
empty string.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@71288 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@71124 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
Issue 10035
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@71065 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
and return value of input function wasn't checked for
errors. This would cause 100% cpu to be taken up.
(closes issue #9654, issue #10010)
Reported by: mnicholson, and eserra
Idea for the patch from mnicholson, patched by me
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@71064 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
is wrong, clearly. In a situation where you set the CDR's amaflags, and then ForkCDR, and then set the new CDR's amaflags to some other value, you will see that all CDRs have had their amaflags changed. This is not good. So I fixed it.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@70948 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
reported by mfarver)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@70898 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
under certain circumstances, would never release it. I also noted that the situation where more than one mapping spec was warned about, but did not ignore further mappings as it had promised. I think I have fixed both situations.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@70804 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
connect the call.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@70672 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
#8565 reported by jsmith)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@70551 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@70444 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
when a PRI disconnect is received depending on which cause code was received.
(issue #9588, original patch by softins, updated patch from jtexter3, and some
additional feedback from mhardeman)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@70396 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@70342 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
..bchannels weren't cleaned properly.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@70341 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
about the situation, we need to test the RESTART stuff then. Also shuffled the empty_chan_in_stack function after the bchannel cleaning functions, to avoid race conditions.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@70311 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
on a 'ZOMBIE' channel. The fix is to consolidate the channel variables during a masquerade, and then copy the merged variables back onto the clone, so the zombie has the same vars that the 'original' has.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@70053 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@69992 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
Fix a crash that could occur when handing device state changes.
When the state of a device changes, the device state thread tells the extension
state handling code that it changed. Then, the extension state code calls the
callback in chan_sip so that it can update subscriptions to that extension.
A pointer to a sip_pvt structure is passed to this function as the call which
needs a NOTIFY sent. However, there was no locking done to ensure that the pvt
struct didn't disappear during this process.
(issue #9946, reported by tdonahue, patch by me, patch updated to trunk to use
the sip_pvt lock wrappers by eliel)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@69990 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
happens. (issue #9699 reported by dimas)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@69986 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@69894 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
after reception of a hangup.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@69887 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
otherwise two threads will try to handle the same channel and it will go kaboom. (issue #9191 reported by japple)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@69846 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
the username to be used for authentication attempts. (issue #9967 reported by achauvin)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@69765 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@69743 f38db490-d61c-443f-a65b-d21fe96a405b
|