Age | Commit message (Collapse) | Author | Files | Lines |
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@86372 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@86371 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
and modify channel data that may change elsewhere. I went through every timer
callback in the source tree to make sure that none of them did any additional
locking that could introduce deadlocks, and all is well.
(closes issue #10765)
Reported by: Ivan
Patches:
ast_1_4_11_svn_patch_channel_rc.diff uploaded by Ivan (license 229)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@86330 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
announcement
or as a hold/position announcement, the caller would be kicked out of the queue.
No longer does this happen.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@86328 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
(patch from jsloan)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@86296 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
me in issue #11018, doesn't really make sense. There is no reason to have
the base64 decode function force a '\0' terminated buffer, when the result is
almost always binary, anyway. In fact, this caused some breakage, as some code
in res_crypto passed in a buffer exactly the right size to get its binary
result, which got stomped on by this patch.
(closes issue #11018, reported by dimas)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@86237 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
unsigned,
since the code attempts to set the strategy to -1 if you specify a bogus strategy.
While this isn't a huge issue in 1.4, it could be a problem for someone who, say, tries
to use the roundrobin strategy in trunk (despite all the deprecation warnings in 1.4).
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@86202 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
with 503 Unavailable.
(closes issue #10994)
Reported by: eserra
Patches:
sip-options-503.patch uploaded by eserra (license 45)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@86149 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
(closes issue #11010)
Reported by: vadim
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@86117 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
by root
(Closes issue #9999)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@86066 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
dialog.
(closes issue #11010)
Reported by: vadim
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@86063 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
queues.conf file
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@86032 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
queue option
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@86031 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
no longer support this in favor of monitor-type = mixmonitor
(related to issue #10885)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@86028 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85997 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
not thread safe. How ironic! Anyway, these changes ensure that the code that
is accessing the lock debugging data is thread-safe.
Many thanks to Ivan for finding and fixing the core issue here, and also
thanks to those that tested the patch and provided test results.
(closes issue #10571)
(closes issue #10886)
(closes issue #10875)
(might close some others, as well ...)
Patches: (from issue #10571)
ivan_ast_1_4_12_rel_patch_lock.h.diff uploaded by Ivan (license 229)
- a few small changes by me
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85994 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
interesting (read nasty) situations. This patch clears up the issue by making
only dynamic queue members removable via dynamic methods.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85958 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
Reported and fixed by jcmoore
Closes issue #11002
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85921 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85896 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
(closes issue #10987, reported by andrew)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85852 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
(closes issue #10996)
Reported by: marsosa
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85850 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
(closes issue #10995)
Reported by: snuffy
Patches:
new-patch.diff uploaded by snuffy (license 35)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85818 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85800 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
thread gets stopped on module unload.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85720 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
change. I changed this a while ago in trunk for performance reasons. However,
bug 8407 points out that it is actually a race condition, causing device state
changes to get processed in random order. So, I backported my changes from
trunk to 1.4.
(closes issue #8407, patch provided by tim_ringenbach, committed patch by me)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85717 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
Reported by davevg
Fixed by me
Closes issue #10985
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85687 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
(closes issue #7827)
Reported by: sharkey
Patches:
say.nits.patch uploaded by sharkey (license 172)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85686 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
Do not try to run chkconfig or similar if using DESTDIR.
Issue 10938, patch by cabal95.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85684 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85649 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
some amount of time. Be a little bit more careful and prepare all of the
output in an intermediary buffer while holding a global resource. Then, after
releasing it, send the output to ast_cli().
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85647 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
sense for it to default to off. The default configuration file has it on, and
proper RFC behavior, as indicated by a comment in the code, is for it to be on.
So, let's have it on by default to make lives easier.
(closes issue #10954, suggested by jtodd)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85604 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
together.
(closes issue #10773)
Reported by: pbayley
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85571 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
character set don't get stripped when reading configuration.
(closes issue #10982, dandre)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85561 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
handling.
(closes issue #10826)
Reported by: dimas
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85559 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
that it is null terminated.
(issue #10977)
Reported by: dimas
Patches:
pbxdundi.patch uploaded by dimas (license 88)
- small mods by me
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85556 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
channel back to the generic bridging core so the monitor or spy operations work.
(closes issue #10943)
Reported by: julianjm
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85552 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
(closes issue #10980)
Reported by: casper
Patches:
db.c.84633.diff uploaded by casper (license 55)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85548 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
(closes issue #10847)
Reported by: atis
Patches:
console_unmute_on_reconnect.patch uploaded by atis (license 242)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85545 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
(closes issue #10979)
Reported by: ys
Patches:
util.c.diff uploaded by ys (license 281)
- small mods by me
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85543 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
user exists.
(closes issue #10971)
Reported by: dimas
Patches:
pbxconfig.patch uploaded by dimas (license 88)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85540 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
Reported and patched by: dimas
Closes issue #10967
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85536 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
command
and retrieve its output. The issue was that there was no way for the main Asterisk
process to know that the remote console was connecting in the -rx mode. The way that
James has fixed this is to have all remote consoles muted by default. Then, regular
remote consoles automatically execute a CLI command to unmute themselves when they
first start up.
(closes issue #10847)
Reported by: atis
Patches:
asterisk-consolemute.diff.txt uploaded by jamesgolovich (license 176)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85533 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
CLI command at once for a remote console.
(closes issue #10888)
Reported by: jamesgolovich
Patches:
asterisk-climultiple.diff.txt uploaded by jamesgolovich (license 176)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85532 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85523 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
(closes issue #10959)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85517 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
(closes issue #10958)
Reported by: dimas
Patches:
realtime.patch uploaded by dimas (license 88)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85515 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
just allocated/created so it's impossible for it to have already been scheduled.
(closes issue #10945)
Reported by: flefoll
Patches:
chan_sip.c.br14.85280.xmit_reliable-patch uploaded by flefoll (license 244)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85397 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
prematurely ends substitution (closes issue #10939)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85356 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
in the middle of the struct, instead of at the end. One of the Debian folks,
paravoid, pointed out that this breaks binary compatability with modules
compiled against older headers. So, I'm moving the new member to the end
of the struct to resolve the situation.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85316 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@85315 f38db490-d61c-443f-a65b-d21fe96a405b
|