Age | Commit message (Collapse) | Author | Files | Lines |
|
f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/tags/1.2.13@45413 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/tags/1.2.13@45412 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
create one. Instead use a temporary pvt and fill it with enough information so we can send a reply.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@45380 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@45332 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@45326 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
time was doing the right thing, even though the change optimized a bit
and removed a lot of potential risks.
Conclusion: No need for a configuration option at all.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@45306 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@45265 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
response but instead basically drop it.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@45260 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
pattern extension needed to resolved the wildcards to an appropriate digit for extension matching to work
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@45134 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
invalid entry (BE-92)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@45119 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@45090 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
mnicholson)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@45060 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
bindings (reported on asterisk-dev)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@45048 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
refresh item back into the scheduler if enabled since it is deleted during reload. (issue #8142 reported by p_lindheimer)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@45030 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
sometimes..also some minor formatting fixes
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@45020 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@44993 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
Linux (thanks to Brian Candler on the asterisk-dev list for the tip)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@44955 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@44785 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@44757 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
reported by eldadran)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@44580 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
reported by eldadran)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@44501 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@44460 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@44432 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
add workaround for new Polycom firmware SUBSCRIBE requests (bug is known to exist in 2.0.1 firmware)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@44392 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
limitations
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@44343 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
just use the keypad as called party number.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@44335 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
RELEASE_COMPLETE - cause on the 3. incoming PMP channel, which is automatically rejected because chan_misdn does not support that kind of callwaiting. Therefore chan_misdn supports now 3 incoming channels on a PMP BRI Port. misdn_lib_get_free_bc now gets the info if the requested channel is incoming or outgoing to make the 3. channel possible
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@44334 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@44296 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
is indeed possible. (issue #7943 reported by eclubb)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@44213 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
message (issue #7942 reported by eclubb)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@44198 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
(issue #7941 reported by eclubb)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@44168 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
setting of frame.delivery fields, some minor code cleanups
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@44149 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
(issue #8065, adamg)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@44110 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@43977 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@43924 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
static member list updating
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@43916 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
statuses. It's internal list of interfaces includes the dial string, while the argument passed to this function does not have the dial string (/n for a local channel). This causes it to ignore the device state changes because it thinks it belongs to none of its members. (#8040 reported and patch by tim_ringenbach)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@43897 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@43895 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
(issue #7370 reported by kryptolus)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@43891 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
reported and patched)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@43871 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
ahead of time. (Issue 7631)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@43815 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
Playback() returns -1 on missing args - so should Background()
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@43800 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
feature that was configured using multiple digits, and the digit that was
pressed timed out in the feature digit timeout period. For example, if blind
transfer is configured as '##', and a user presses just '#'. In this situation,
the call would lock up and no longer pass any frames.
(issue #7977 reported by festr, and issue #7982 reported by michaels and
valuable input provided by mneuhauser and kuj. Fixed by me, with testing help
and peer review from Joshua Colp).
There are a couple of issues involved in this fix:
1) When ast_generic_bridge determines that there has been a timeout, it returned
AST_BRIDGE_RETRY. Then, when ast_channel_bridge gets this result, it calls
ast_generic_bridge over again with the same timestamp for the next event.
This results in an endless loop of nothing until the call is terminated.
This is resolved by simply changing ast_generic_bridge to return
AST_BRIDGE_COMPLETE when it sees a timeout.
2) I also changed ast_channel_bridge such that if in the process of calculating
the time until the next event, it knows a timeout has already occured, to
immediately return AST_BRIDGE_COMPLETE instead of attempting to bridge the
channels anyway.
3) In the process of testing the previous two changes, I ran into a problem in
res_features where ast_channel_bridge would return because it determined
that there was a timeout. However, ast_bridge_call in res_features would
then determine by its own calculation that there was still 1 ms before the
timeout really occurs. It would then proceed, and since the bridge broke
out and did *not* return a frame, it interpreted this as the call was over
and hung up the channels.
The reason for this was because ast_bridge_call in res_features and
ast_channel_bridge in channel.c were using different times for their
calculations. channel.c uses the start_time on the bridge config, which
is the time that the feature digit was recieved. However, res_features
had another time, 'start', which was set right before calling
ast_channel_bridge. 'start' will always be slightly after start_time in the
bridge config, and sometimes enough to round up to one ms.
This is fixed by making ast_bridge_call use the same time as
ast_channel_bridge for the timeout calculation.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@43778 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
properly established in misdn_call. also removed the ACK_HDLC stuff which is not really needed.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@43764 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
calling write(). During this change, checking if this was a remote console was
removed. This caused this message about using "exit" or "quit" to exit an
Asterisk console to come up in times where it did not make sense. This change
restores the check to see if this is a remote console before printing the
message. (fixes BE-4)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@43708 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@43706 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@43705 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
don't introduce a length limit on the definition by using a 256 byte temporary
storage buffer. Instead, make the temporary buffer just as big as it needs
to be to hold the entire mailbox definition.
(fixes BE-68)
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@43699 f38db490-d61c-443f-a65b-d21fe96a405b
|
|
1) delete=yes was ignored
2) maxmessages was ignored
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@43634 f38db490-d61c-443f-a65b-d21fe96a405b
|