Age | Commit message (Collapse) | Author | Files | Lines |
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@78416 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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@77869 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
W9SH), and oversight in logic in TONE_VERIFY/RELAX mode in chan_zap.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@77845 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
of re-invites. This makes it so that if there are two or more Asterisk
servers between endpoints, the Asterisk servers will not keep retransmitting the re-invites.
(closes issue #10274, reported by cstadlmann, patched by me with approval from file)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@77824 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
queue. In the network_thread() loop, it traverses the list using the
AST_LIST_TRAVERSE_SAFE macro. However, to remove an element of the list within
this loop, it used AST_LIST_REMOVE, instead of AST_LIST_REMOVE_CURRENT, which I
believe could leave some of the internal variables of the SAFE macro invalid.
Mihai says that he already made this change in his local copy and it didn't help
his VNAK storm issues, but I still think it's wrong. :)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@77794 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
Reported by: julianjm
Patches:
chan_sip_device_state_hold_fix.v1.diff.txt uploaded by julianjm (license 99)
Clear ONHOLD flag when decrementing the onHold peer count. If we did not do this the count may keep decreasing.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@77536 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@77490 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
https://origsvn.digium.com/svn/asterisk/branches/1.2
........
r76978 | murf | 2007-07-24 18:07:24 -0600 (Tue, 24 Jul 2007) | 1 line
this fixes bug 10293, where the error message because defaultzone or loadzone was not defined was confusing
........
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@76983 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
(ASA-2007-018)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@76803 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
Don't try to play dialtone in some unimplemented features.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@76656 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
https://origsvn.digium.com/svn/asterisk/branches/1.2
........
r76653 | file | 2007-07-23 15:28:13 -0300 (Mon, 23 Jul 2007) | 4 lines
(closes issue #5866)
Reported by: tyler
Do not force channel format changes when a generator is present. The generator may have changed the formats itself and changing them back would cause issues.
........
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@76654 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
Issue 10276.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@76620 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
https://origsvn.digium.com/svn/asterisk/branches/1.2
........
r76560 | file | 2007-07-23 11:32:07 -0300 (Mon, 23 Jul 2007) | 6 lines
(closes issue #10236)
Reported by: homesick
Patches:
rpid_1.4_75840.patch uploaded by homesick (license 91)
Accept Remote Party ID on guest calls.
........
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@76561 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
Reported by: mvanbaak
Patches:
chan_skinny_openbsd.diff uploaded by mvanbaak (license 7)
Add another OS that has to use the Macros for byte ordering.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@76519 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
the network. Using an unsigned value here made it impossible to handle an
error returned from recvfrom(). Furthermore, in the case that recvfrom()
did return an error, this would cause a crash due to a heap overflow.
(closes issue #10265, reported by and fix suggested by timrobbins)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@76485 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
https://origsvn.digium.com/svn/asterisk/branches/1.2
........
r76226 | russell | 2007-07-20 21:01:46 -0500 (Fri, 20 Jul 2007) | 4 lines
Backport a fix for a memory leak that was fixed in trunk in reivision 76221
by rizzo. The memory used for the localaddr list was not freed during a
configuration reload.
........
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@76227 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
Cancel ringing if endpoint hangs up before answering.
Fixes were backported from trunk (there was apparently a bit of confusion during merge of a previous patch).
(closes issue #10241)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@76178 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
immediately after/during sending a digit.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@76174 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
https://origsvn.digium.com/svn/asterisk/branches/1.2
........
r76080 | file | 2007-07-20 14:16:48 -0300 (Fri, 20 Jul 2007) | 6 lines
(closes issue #10247)
Reported by: fkasumovic
Patches:
chan_sip.patch uploaded by fkasumovic (license #101)
Drop any peer realm authentication entries when reloading so multiple entries do not get added to the peer.
........
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@76087 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@75980 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
https://origsvn.digium.com/svn/asterisk/branches/1.2
........
r75927 | russell | 2007-07-19 10:49:42 -0500 (Thu, 19 Jul 2007) | 6 lines
When processing full frames, take sequence number wraparound into account when
deciding whether or not we need to request retransmissions by sending a VNAK.
This code could cause VNAKs to be sent erroneously in some cases, and to not
be sent in other cases when it should have been.
(closes issue #10237, reported and patched by mihai)
........
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@75928 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
recent ast_ time stuff from Tilghman
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@75807 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
https://origsvn.digium.com/svn/asterisk/branches/1.2
........
r75757 | russell | 2007-07-18 16:09:13 -0500 (Wed, 18 Jul 2007) | 5 lines
When traversing the queue of frames for possible retransmission after
receiving a VNAK, handle sequence number wraparound so that all frames that
should be retransmitted actually do get retransmitted.
(issue #10227, reported and patched by mihai)
........
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@75759 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@75732 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
using GCC 4.2.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@75712 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
Issue 9245, patch by slimey.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@75711 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
Issue 9887, patches by DEA
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@75707 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@75623 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
Reported by: elandivar
It is possible for hold status to exist without call limits set, so we need to ensure update_call_counter is executed regardless.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@75621 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
first place. This would otherwise cause a crash.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@75619 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
https://origsvn.digium.com/svn/asterisk/branches/1.2
........
r75449 | russell | 2007-07-17 15:57:09 -0500 (Tue, 17 Jul 2007) | 3 lines
Properly check for the length in the skinny packet to prevent an invalid memcpy.
(ASA-2007-016)
........
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@75450 f38db490-d61c-443f-a65b-d21fe96a405b
|