Age | Commit message (Collapse) | Author | Files | Lines |
|
Reported by: ramonpeek
Pass through the return value from macro_exec through the MacroIf application.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@77767 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@75748 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@75657 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
What triggered this investigation was an IRC chat where some people's quiet flags were
set while others' weren't even though none of them had specified the q option.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@75066 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
Between the time recalc_holdtime and update_queue was called, it was possible that the call could have been hungup.
Move both additions to the same place, so this won't happen.
Issue 10158, initial patch by makoto, modified by me.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@74427 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
Issue 10170, patch by casper.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@74316 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@73349 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
|
|
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
|
|
reported by netoguy)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@72378 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
mtryfoss)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@72327 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
|
|
in memory corruption
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@71750 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
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@70444 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@69894 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
cleanly using '#'
(closes issue #9577, patch from Thomas Andrews)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@68526 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
accept/save.
Issue 9904, patch by me.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@68204 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
reported by gasparz)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@68070 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
unfixed for pbx_realtime, but only because we lack core API to do it.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@66744 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
On most device state changes, it would leak roughly 8 to 64 bytes (the length of
the name of the device).
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@65389 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
when several targets are specified for a dial, if any one them reports FAIL, the whole call gets FAIL, even though others were ringing OK. I rearranged the priorities, so that a new disposition, NULL, is at the lowest level, and the disposition get init'd to NULL. Then, next up is FAIL, and next up is BUSY, then NOANSWER, then ANSWERED. All the related set routines will only do so if the disposition value to be set to is greater than what's already there. This gives the intended effect. So, if all the targets are busy, you'd get BUSY for the call disposition. If all get BUSY, but one, and that one rings is not answered, you get NOANSWER. If by some freak of nature, the NULL value doesn't get overridden, then the disp2str routine will report NOANSWER as before.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@65172 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
Issue 9727.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@64758 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@63565 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@63477 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
so deleting causes memory corruption (beyond bounds)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@63359 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
list of the channels. That was bad, mmmk? (issue #7497 reported by sabbathbh)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@61804 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
valid exit key.
If it was enabled, this statement would've never been checked in the first place.
Issue #9552
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@61692 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
OUTBOUND_GROUP except it will get unset after use so it won't get accidentally inherited. (issue #BE-140)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@61655 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
This also fixes the case where somebody wants to match on less then 3 chars.
Issue 9071
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@60935 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
channels compatible if it is the only channel being dialed. (issue #9445 reported by marcelbarbulescu)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@60797 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
general weirdness. (Issue 8329)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@60711 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
mean that the module failed to load. The user could be using realtime.
Issue #9473
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@60267 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
reported by rtucker)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@59723 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
are in use. This ensures that two people going into a new dynamic conference when the 'e' option is set don't go into the same conference room. (issue #8835 reported by eliel)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@59360 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@59283 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@59280 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
this one.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@59277 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@59187 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
hangups (et al.), as per 9337
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@59186 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
success. (issue #9205 reported by ballares)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@57869 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@57648 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
fails on a channel in meetme it will tell you the channel name instead of spitting out the wrong error message.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@55956 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
handling to use the linked list macros and most importantly, implements
reference counting on the ast_conference objects. The reference counting was
first backported from 1.4. However, that code has some problems that caused
the reference count to never hit zero. Those problems are fixed in this patch
and will be resolved in 1.4 and trunk next, with a different patch.
(issues #7647, #9073, #9106, BE-115).
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@55750 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
aligned.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@55588 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
already exists
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@55434 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@55277 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
reported by lmamane)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@55153 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
and trunk. I decided that once a conference is created from meetme.conf,
it is acceptable behavior that the pin can not be changed until the
conference goes away. I also added a note in meetme.conf to describe this
behavior.
We still have another issue in 1.4 and trunk where some conferences with no
users don't go away. That is the real bug that needs to be addressed here.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@55005 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
file every time someone joins the conference instead of only when the
conference is first created. This is to ensure that changes to the pin
numbers in the config file are always honored. (issue #9073)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@54955 f38db490-d61c-443f-a65b-d21fe96a405b
|