Age | Commit message (Collapse) | Author | Files | Lines |
|
f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/tags/1.4.10@78492 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/tags/1.4.10@78491 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/tags/1.4.10@78490 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@78488 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/tags/1.4.10@78458 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/tags/1.4.10@78457 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/tags/1.4.10@78456 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
message_count.
(closes issue #10401, reported by st1710, patched by me)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@78450 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
connections might be depending upon it
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@78437 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@78416 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
#9389)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@78415 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
(ASA-2007-019)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@78375 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
https://origsvn.digium.com/svn/asterisk/branches/1.2
........
r78370 | russell | 2007-08-07 12:44:04 -0500 (Tue, 07 Aug 2007) | 4 lines
Revert patch committed for issue #9660. It broke E&M trunks.
(closes issue #10360)
(closes issue #10364)
........
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@78371 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@78275 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
dynamic thread list.
(closes issue #10392, patch from Mihai, with credit to his colleague, Pete)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@78242 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
problems, though, because the only code that uses the return value only checks
to see if it is NULL.
(closes issue #10390, pointed out by mihai)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@78184 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
in which case they send none in the transfer. In this case we need to not fail the transfer dialog lookup.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@78182 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
in a config would be converted to just semicolons (\; to ;)
Issue 9938
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@78180 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
Reported by: wdecarne
Now that we pass through RTP timestamp information we need to make the allowed timestamp skew considerably less. There are situations where a source may change and due to the timestamp difference the receiver will experience an audio gap since we did not indicate by setting the marker bit that the source changed.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@78172 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
Reported by: rizzo
Include stdlib.h so NULL gets defined for gethostbyname_r checks.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@78166 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
time.
Thanks to Jon Fealy for emailing me the correction.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@78164 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@78146 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@78143 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
found, not ACL failure)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@78139 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
corresponding way of matching for non-realtime peers.
Now matches are made on both the IP address and port number, or if the insecure setting is set to "port" then just match on the
IP address.
In order to accomplish this, I also added a new API call, ast_category_root, which returns the first variable of an ast_category struct
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@78103 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
Reported by: blitzrage
Patches:
bug0010194 uploaded by vovochka
Tested by: blitzrage
Fix a problem when you call Voicemail() with multiple mailboxes specified and
ODBC_STORAGE is in use. The audio part of the message was only given to the
first mailbox specified.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@78101 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
with DEBUG_THREADS enabled and provide the following:
* This will keep track of which locks are held by which thread as well as
which lock a thread is waiting for in a thread-local data structure. A
reference to this structure is available on the stack in the dummy_start()
function, which is the common entry point for all threads. This information
can be easily retrieved using gdb if you switch to the dummy_start() stack
frame of any thread and print the contents of the lock_info variable.
* All of the thread-local structures for keeping track of this lock information
are also stored in a list so that the information can be dumped to the CLI
using the "core show locks" CLI command. This introduces a little bit of a
performance hit as it requires additional underlying locking operations
inside of every lock/unlock on an ast_mutex. However, the benefits of
having this information available at the CLI is huge, especially considering
this is only done in DEBUG_THREADS mode. It means that in most cases where
we debug deadlocks, we no longer have to request access to the machine to
analyze the contents of ast_mutex_t structures. We can now just ask them
to get the output of "core show locks", which gives us all of the information
we needed in most cases.
I also had to make some additional changes to astmm.c to make this work when
both MALLOC_DEBUG and DEBUG_THREADS are enabled. I disabled tracking of one
of the locks in astmm.c because it gets used inside the replacement memory
allocation routines, and the lock tracking code allocates memory. This caused
infinite recursion.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@78095 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
is set to "passthrough". This was pointed out by Kevin in the middle of a
training session.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@78063 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
will just return immediately. Also, fix some logic so the thread's lock
isn't unlocked twice in the weird case of dynamic threads getting acquired
right after a timeout.
(pointed out by SteveK)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@78028 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
Also make note of the "A" option of date format.
Issue 9779, modifications by DEA, wedhorn, and myself.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@77996 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
If this happens during call setup, we need to give up.
Issue 10325.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@77993 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
during the first time it runs. This shouldn't ever happen, but we should
account for it anyway.
(pointed out by pete, who works with mihai)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@77949 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
Also rearrange messages to better fit with what a wireshark trace shows it should be.
Issue 10299, initial patch and solution by sbisker, modified by me to fit with wireshark trace.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@77947 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
https://origsvn.digium.com/svn/asterisk/branches/1.2
........
r77942 | murf | 2007-08-02 11:56:37 -0600 (Thu, 02 Aug 2007) | 1 line
This patch hopefully solves 10141; The user is running with it, and it doesn't appear to harm asterisk's operation, and may prevent a crash. I'll store it in 1.2, as we have shut down support on 1.2, but since I developed the patch before support finished, and it might affect 1.4 and trunk, I'm going ahead with it.
........
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@77945 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
thread timed out waiting for something to do, but was acquired to perform an
action immediately afterwords, then wait on the condition again to give the
other thread a chance to finish setting up the data for what action this thread
should perform. Otherwise, if it immediately continues, it will perform the
wrong action.
(reported on IRC by mihai, patch by me)
(related to issue #10289)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@77943 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
that have already been marked for deletion don't get retransmitted.
(closes issue #10361, patch from mihai)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@77939 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
"From: 5555" rather than "From: s"
Issue 10358, initial patch by DEA, reworked by me to use S_OR, tested by sbisker
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@77894 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
Issue 10291, patch by DEA.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@77890 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
The most notable problem is that people have been seeing storms of VNAK frames
being sent due to really old frames mysteriously being in the retransmission
queue and never getting removed.
It was possible that a dynamic thread got created, but did not acquire its lock
before the thread that created it signals it to perform an action. When this
happens, the thread will sleep until it hits a timeout, and then get destroyed.
So, the action never gets performed and in some cases, means a frame doesn't
get transmitted and never gets freed since the scheduler never gets a chance
to reschedule transmission.
Another less severe race condition is in the handling of a timeout for a dynamic
thread. It was possible for it to be acquired to perform at action at the same
time that it hit a timeout. When this occurs, whatever action it was acquired
for would never get performed.
(patch contributed by Mihai and SteveK)
(closes issue #10289)
(closes issue #10248)
(closes issue #10232)
(possibly related to issue #10359)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@77887 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@77886 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
the 7921),
due to sending packets in the wrong order during hangup.
Also make sure we clear tones/messages on the correct line/instance.
Issue 10291, patch by DEA, tested by sbisker and myself.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@77883 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
Reported by: ftarz
Some platforms don't like it when you pass NULL to vsnprintf so pass "" instead.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@77871 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@77869 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@77867 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
library that it is used.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@77865 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
the system.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@77863 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
would kick people out of the queue because of erroneously
thinking the 'n' option was in use.
(closes issue #10320, reported by jfitzgibbon, patched by me, tested by blitzrage and me)
Thank you blitzrage for all the testing you've done lately with queues! It's much appreciated!
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@77854 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
updated after each attempt to call the queue.
This fixes an issue where if a caller calls into a queue where no one is logged in, they would wait forever even if a member
logged in at some point.
(closes issue #10346, reported by and tested by blitzrage, patched by me)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@77852 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@77846 f38db490-d61c-443f-a65b-d21fe96a405b
|