28147 Commits (be36bd7ca565531c09ca444e59b6d057131a9ab0)

 

All Branches   

Search

Author	SHA1	Message	Date
zuul	de29888904	Merge "app_voicemail: fix bugs, imap mm_status log change to debug"	9 years ago
Alexei Gradinari	31f17abe44	res_pjsip: add "via_addr", "via_port", "call_id" to contact ... As res_pjsip_nat rewrites contact's address, only the last Via header can contain the source address of registered endpoint. Also Call-Id header may contain the source address of registered endpoint. Added "via_addr", "via_port", "call_id" to contact. Added new fields ViaAddress, CallID to AMI event ContactStatus. ASTERISK-26011 Change-Id: I36bcc0bf422b3e0623680152d80486aeafe4c576	9 years ago
Alexei Gradinari	574c9e77eb	res_pjsip: chatty verbose messages ... There are a lot of verbose messages about Endpoint and Contact status changes if there are many dynamic endpoints. The patch sets verbose level 2 for Endpoint status changes and verbose level 3 for Contact status changes. ASTERISK-26055 #close Change-Id: Ie64e261ddbbc41bfff0f0190241152cc123fe6d7	9 years ago
Alexei Gradinari	b3142e99e4	app_voicemail: fix bugs, imap mm_status log change to debug ... Fixed some bugs: - create dirpath when save downloading message from IMAP storage. - create IMAP folder if not exists when saving to IMAP storage - check if file successfully opened before write to it - some IMAP checks - remove non-standard flag 'Unseen' etc Change to debug IMAP mm_status log instead of verbose. Remove unused X-Asterisk-VM-Caller-channel message header for security reason. The clients should not know name of peer/endpoint. ASTERISK-26045 #close Change-Id: I7f83d88b69b36934e2539c114b9fb612deed971b	9 years ago
Richard Mudgett	7d44d12816	pjsip_distributor.c: Use correct rdata info access method. ... The pjproject doxygen for rdata->msg_info.info says to call pjsip_rx_data_get_info() instead of accessing the struct member directly. You need to call the function mostly because the function will generate the struct member value if it is not already setup. Change-Id: Iafe8b01242b7deb0ebfdc36685e21374a43936d2	9 years ago
Tzafrir Cohen	1d60bfcdf1	followme: allow disabling callee prompt ... Add the option 'enable_callee_prompt' to followme.conf. Enabled by default. If disabled, a callee is not prompted to accept or reject the forwarded call. ASTERISK-26064 #close Change-Id: I0a8b19d4cf95c86a07c992813babb9e4a4acfff5 Signed-off-by: Tzafrir Cohen <tzafrir.cohen@xorcom.com>	9 years ago
zuul	a6b16d7029	Merge "res_pjsip_outbound_publish: Ensure publish is valid when explicitly destroying."	9 years ago
Joshua Colp	b0e4ea96de	Merge "Bridging: introduce "invisible" bridges."	9 years ago
zuul	d1ab0936ab	Merge "res_pjsip: Only check transaction on transaction state events."	9 years ago
Corey Farrell	80ff2c2540	threadpool: Fix potential data race. ... worker_start checked for ZOMBIE status without holding a lock. All other read/write of worker status are performed with a lock, so this check should do the same. ASTERISK-25777 #close Change-Id: I5e33685a5c26fdb300851989a3b82be8c4e03781	9 years ago
Joshua Colp	56f24345f7	Merge "func_odbc: single database connection should be optional"	9 years ago
Joshua Colp	070eab6ed2	res_pjsip_outbound_publish: Ensure publish is valid when explicitly destroying. ... Recent changes to res_pjsip_outbound_publish have introduced a race condition at shutdown where an outbound publish may be shutdown twice. In this case the first succeeds as a result of the unpublish. In the second invocation since it's been unpublished a task is queued to just destroy the client. This task holds no ref to the publish and as a result the publish may be destroyed before the task is run, causing a crash. This explicit destruction task now holds a reference to the publish to ensure it remains valid. ASTERISK-26053 #close Change-Id: I10789b98add3e50292ee3b33a55a1d9061cec94b	9 years ago
Joshua Colp	cab97fd905	Merge "ARI: Add the ability to download the media associated with a stored recording"	9 years ago
Joshua Colp	c20e560516	Merge "chan_rtp.c: Cleanup ast_request() parameter parsing."	9 years ago
zuul	c7320aea6e	Merge "Makefile: remove OSARCH check for init install"	9 years ago
Mark Michelson	f6c33771f6	Bridging: introduce "invisible" bridges. ... Invisible bridges function the same as normal bridges, but they have the following restrictions: * They never show up in CLI, AMI, or ARI queries. * They do not have Stasis messages published about them. Invisible bridges' main use is for when use of the bridging system is desired, but the bridge should not be known to users of the Asterisk system. ASTERISK-25925 Change-Id: I804a209d3181d7c54e3d61a60eb462e7ce0e3670	9 years ago
Joshua Colp	56d5af4584	Merge "func_curl: Don't trim response text on non-ASCII characters"	9 years ago
Joshua Colp	0eb293d2c4	Merge "parking.h: Update ast_parking_park_call() doxygen to reality."	9 years ago
Joshua Colp	85d0272e76	res_pjsip: Only check transaction on transaction state events. ... The send request callback function currently assumes that it will only ever be called on transaction state changes. This is not always true. If our own timer callback occurs we will call the callback with a timer event instead of a transaction state change event. In this case the transaction on the event is invalid and accessing it will result in a crash. ASTERISK-26049 #close Change-Id: I623211c8533eb73056b0250b4580b49ad4174dfc	9 years ago
Ivan Poddubny	31897d2d99	func_curl: Don't trim response text on non-ASCII characters ... The characters 0x80-0xFF were trimmed as well as 0x00-0x20 because of a signed comparison. ASTERISK-25669 #close Reported by: Jesper patches: strings.curl.trim.patch submitted by Jesper (License 5518) Change-Id: Ia51e169f24e3252a7ebbaab3728630138ec6f60a	9 years ago
Richard Mudgett	2a77af9ed0	chan_rtp.c: Cleanup ast_request() parameter parsing. ... * Fixed NULL crash potential if parameters are missing. * Reordered some operations so further diagnostic messages can be more helpful. Change-Id: Ibbdc67a2496508cbfbfef0cf19c35177ae2fbd70	9 years ago
Richard Mudgett	ade5275a3e	parking.h: Update ast_parking_park_call() doxygen to reality. ... ASTERISK-26029 Change-Id: I2db14d102a48d3224010e6d1c69e856373cc1260	9 years ago
Alexei Gradinari	c378b00a83	func_odbc: single database connection should be optional ... func_odbc was changed in Asterisk 13.9.0 to make func_odbc use a single database connection per DSN because of reported bug ASTERISK-25938 with MySQL/MariaDB LAST_INSERT_ID(). This is drawback in performance when func_odbc is used very often in dialplan. Single database connection should be optional. ASTERISK-26010 Change-Id: I7091783a7150252de8eeb455115bd00514dfe843	9 years ago
Mark Michelson	1c02b19b79	res_pjsip: Match dialogs on responses better. ... When receiving an incoming response to a dialog-starting INVITE, we were not matching the response to the INVITE dialog. Since we had not recorded the to-tag to the dialog structure, the PJSIP-provided method to find the dialog did not match. Most of the time, this was not a problem, because there is a fall-back that makes the response get routed to the same serializer that the request was sent on. However, in cases where an asynchronous DNS lookup occurs in the PJSIP core, the thread that sends the INVITE is not actually a threadpool serializer thread. This means we are unable to record a serializer to handle the incoming response. Now, imagine what happens when an INVITE is sent on a non-serialized thread, and an error response (such as a 486) arrives. The 486 ends up getting put on some random threadpool thread. Eventually, a hangup task gets queued on the INVITE dialog serializer. Since the 486 is being handled on a different thread, the hangup task can execute at the same time that the 486 is being handled. The hangup task assumes that it is the sole owner of the INVITE session and channel, so it ends up potentially freeing the channel and NULLing the session's channel pointer. The thread handling the 486 can crash as a result. This change has the incoming response match the INVITE transaction, and then get the dialog from that transaction. It's the same method we had been using for matching incoming CANCEL requests. By doing this, we get the INVITE dialog and can ensure that the 486 response ends up being handled by the same thread as the hangup, ensuring that the hangup runs after the 486 has been completely handled. ASTERISK-25941 #close Reported by Javier Riveros Change-Id: I0d4cc5d07e2a8d03e9db704d34bdef2ba60794a0	9 years ago
Matt Jordan	e773e3a9bb	ARI: Add the ability to download the media associated with a stored recording ... This patch adds a new feature to ARI that allows a client to download the media associated with a stored recording. The new route is /recordings/stored/{name}/file, and transmits the underlying binary file using Asterisk's HTTP server's underlying file transfer facilities. Because this REST route returns non-JSON, a few small enhancements had to be made to the Python Swagger generation code, as well as the mustache templates that generate the ARI bindings. ASTERISK-26042 #close Change-Id: I49ec5c4afdec30bb665d9c977ab423b5387e0181	9 years ago
Joshua Colp	40cb032009	res_sorcery_astdb: Filter fields to only the registered ones. ... This change introduces the same filtering that is done in res_sorcery_realtime to the res_sorcery_astdb module. This allows persisted sorcery objects that may contain unknown fields to still be read in from the AstDB and used. This is particularly useful when switching between different versions of Asterisk that may have introduced additional fields. ASTERISK-26014 #close Change-Id: Ib655130485a3ccfd635b7ed5546010ca14690fb2	9 years ago
Joshua Colp	ff3cbc0046	Merge "res_pjsip_empty_info: Respond to empty SIP INFO packets"	9 years ago
Joshua Colp	e205eb55a4	Merge "res_pjsip: Endpoint IP Access Controls"	9 years ago
snuffy	9766a12b4c	res_pjsip_empty_info: Respond to empty SIP INFO packets ... Some SBCs require responses to empty SIP INFO packets after establishing call via INVITE, if not responded to they may drop your call after unspecified timeout of X minutes. They are identified by having no Content-Type, check for this and respond with 200 - OK message. ASTERISK-24986 #close Reported-by: Ilya Trikoz, Federico Santulli Change-Id: Ib27e4f07151e5aef28fa587e4ead36c5b87c43e0	9 years ago
Joshua Colp	acbaa1b0cf	Merge "udptl: Don't eat sequence numbers until OK is received"	9 years ago
Joshua Colp	5acb25722c	Merge "logger: Support JSON logging with Verbose messages"	9 years ago
Joshua Colp	b57032c364	Merge "res_hep: Provide an option to pick the UUID type"	9 years ago
Joshua Colp	1f36270b21	Merge "res/res_hep_pjsip: Fix reported local IP address when bound to 'any'"	9 years ago
Tzafrir Cohen	111c4b0324	Makefile: remove OSARCH check for init install ... There are more specific checks for the platform. Specifically this allows installing OS/X init scripts. ASTERISK-26038 #close Change-Id: If08933621145b10362a0cfe73c079301d9c13f50 Signed-off-by: Tzafrir Cohen <tzafrir.cohen@xorcom.com>	9 years ago
Joshua Colp	d4b77dad1b	res_pjsip_exten_state: Use the extension for publishing to. ... This change uses the newly added multi-user support for outbound publish to publish to the specific user that an extension state change is for. This also extends the res_pjsip_outbound_publish support to include the user specific From and To URI information in the outbound publishing of extension state. Since the URI is used when constructing the body it is important to ensure that the correct local and remote URIs are used. Finally the max string growths for the dialog-info+xml body generator has been increased as through testing it has proven to be too conservative. ASTERISK-25965 Change-Id: I668fdf697b1e171d4c7e6f282b2e1590f8356ca1	9 years ago
Kevin Harwell	3905997bae	res_pjsip_outbound_publish: Add multi-user support per configuration ... Added a new multi_user option that when specified allows a particular configuration to be used for multiple users. It does this by replacing the user portion of the server uri with a dynamically created one. Two new API calls have been added in order to make use of the new functionality: ast_sip_publish_user_send - Sends an outgoing publish message based on the given user. If state for the user already exists it uses that, otherwise it dynamically creates new outbound publishing state for the user at that time. ast_sip_publish_user_remove - Removes all outbound publish state objects associated with the user. This essentially stops outbound publishing for the user. ASTERISK-25965 #close Change-Id: Ib88dde024cc83c916424645d4f5bb84a0fa936cc	9 years ago
Joshua Colp	fc68291d13	Merge "CHANGES: Update formatting of items"	9 years ago
Joshua Colp	e2fc83af50	Merge "ARI: Add the ability to play multiple media URIs in a single operation"	9 years ago
Joshua Colp	4e7a1b4193	Merge "chan_sip: Prevent extra Session-Expires headers from being added"	9 years ago
George Joseph	6e5e84458f	udptl: Don't eat sequence numbers until OK is received ... Scenario: Local fax -> Asterisk w/ firewall -> Provider -> Remote fax * Local fax starts rtp call to remote fax * Remote fax starts t38 call back to local fax. * Local fax sends t38 no-signal to Asterisk before sending an OK. * udptl processes the frame and increments the expected sequence number. * chan_sip drops the frame because the call isn't up so nothing goes out the external interface to open the port for incoming packets. * Local fax sends OK and Asterisk sends OK to the remote fax. * Remote fax sends t38 packets which are dropped by the firewall. * Local fax re-sends t38 no-signal with the same sequence number. * udptl drops the frame because it thinks it's a dup. * Still no outgoing packets to open the firewall. * t38 negotiation fails. The patch drops frames t38 received before udptl sequence processing when the call hasn't been answered yet. The second no-signal frame is then seen as new and is relayed out the external interface which opens the port and allows negotiation to continue. ASTERISK-26034 #close Change-Id: I11744b39748bd2ecbbe8ea84cdb4f3c5943c5af9	9 years ago
Matt Jordan	52148d93f4	CHANGES: Update formatting of items ... * Provide consistent indenting of lines in bulleted paragraphs * Respect the 80 character column width * Group all like items together, e.g., all dialplan applications under "Applications", etc. * Use a single blank line to break up functionality changes within a larger section * Use two blanks lines to delineate larger sections Change-Id: I0488554f5cb7c51da70003d69288a21c9aab9647	9 years ago
Matt Jordan	03d88b5656	ARI: Add the ability to play multiple media URIs in a single operation ... Many ARI applications will want to play multiple media files in a row to a resource. The most common use case is when building long-ish IVR prompts made up of multiple, smaller sound files. Today, that requires building a small state machine, listening for each PlaybackFinished event, and triggering the next sound file to play. While not especially challenging, it is tedious work. Since requiring developers to write tedious code to do normal activities stinks, this patch adds the ability to play back a list of media files to a resource. Each of the 'play' operations on supported resources (channels and bridges) now accepts a comma delineated list of media URIs to play. A single Playback resource is created as a handle to the entire list. The operation of playing a list is identical to playing a single media URI, save that a new event, PlaybackContinuing, is raised instead of a PlaybackFinished for each non-final media URI. When the entire list is finished being played, a PlaybackFinished event is raised. In order to help inform applications where they are in the list playback, the Playback resource now includes a new, optional attribute, 'next_media_uri', that contains the next URI in the list to be played. It's important to note the following: - If an offset is provided to the 'play' operations, it only applies to the first media URI, as it would be weird to skip n seconds forward in every media resource. - Operations that control the position of the media only affect the current media being played. For example, once a media resource in the list completes, a 'reverse' operation on a subsequent media resource will not start a previously completed media resource at the appropiate offset. - This patch does not add any new operations to control the list. Hopefully, user feedback and/or future patches would add that if people want it. ASTERISK-26022 #close Change-Id: Ie1ea5356573447b8f51f2e7964915ea01792f16f	9 years ago
George Joseph	5bd1bf2816	chan_sip: Prevent extra Session-Expires headers from being added ... When chan_sip does a re-INVITE to refresh a session and authentication is required, the INVITE with the Authorization header containes a second Session-Expires header without the ";refersher=" parameter. This is causing some proxies to return a 400. Also, when Asterisk is the uas and the refresher, it is including the Session-Expires and Min-SE headers in OPTIONS messages which is not allowed per RFC4028. This patch (based on the reporter's) Checks to see if a Session-Expires header is already in the message before adding another one. It also checks that the method is INVITE or UPDATE. ASTERISK-26030 #close Change-Id: I58a7b07bab5a3177748d8a7034fb8ad8e11ce1d9	9 years ago
George Joseph	ae81b55361	res_pjsip_outbound_registration: Clean up state when registration is deleted ... Nothing was cleaning up the registration state object when ast_sorcery_delete was called on a registration. So, the registration was deleted from sorcery but the state object went right on refreshing the registration (or failing to refresh the registration) with the peer. * Added a 'deleted' observer on registration that removes the state object. ASTERISK-25964 #close Reported-by Matt Jordan Change-Id: I2db792145cdb1f72ebbf57dd9099596dbbf12c23	9 years ago
zuul	040522100b	Merge "configs/samples/pjsip.conf.sample: Fix typo"	9 years ago
George Joseph	8b5cee4a4f	res_pjsip: Set TCP_NODELAY on TCP transports ... Although it's perfectly legal to place multiple SIP messages in the same packet, it can cause problems because the Linux default is to enable Path MTU Discovery which sets the Don't Fragment bit on the packets. If adding a second message to the packet causes the MTU to be exceeded, and the destination isn't equipped to send a FRAGMENTATION NEEDED response to a large packet, the packet will just be dropped. We can't specifically tell the stack to send only 1 message per packet, but we can turn on TCP_NODELAY when we create the transport. This will at least tell the stack to send packets as soon as possible. ASTERISK-26005 #close Reported-by: Ross Beer Change-Id: I820f23227183f2416ca5e393bec510e8fe1c8fbd	9 years ago
Matt Jordan	3522376512	logger: Support JSON logging with Verbose messages ... When 2d7a4a3357 was merged, it missed the fact that Verbose log messages are formatted and handled by 'verbosers'. Verbosers are registered functions that handle verbose messages only; they exist as a separate class of callbacks. This was done to handle the 'magic' that must be inserted into Verbose messages sent to remote consoles, so that the consoles can format the messages correctly, i.e., the leading tabs/characters. In reality, verbosers are a weird appendage: they're a separate class of formatters/message handlers outside of what handles all other log messages in Asterisk. After some code inspection, it became clear that simply passing a Verbose message along with its 'sublevel' importance through the normal logging mechanisms removes the need for verbosers altogether. This patch removes the verbosers, and makes the default log formatter aware that, if the log channel is a console log, it should simply insert the 'verbose magic' into the log messages itself. This allows the console handlers to interpret and format the verbose message themselves. This simplifies the code quite a lot, and should improve the performance of printing verbose messages by a reasonable factor: (1) It removes a number of memory allocations that were done on each verobse message (2) It removes the need to strip the verbose magic out of the verbose log messages before passing them to non-console log channels (3) It now performs fewer iterations over lists when handling verbose messages Since verbose messages are now handled like other log messages (for the most part), the JSON formatting of the messages works as well. ASTERISK-25425 Change-Id: I21bf23f0a1e489b5102f8a035fe8871552ce4f96	9 years ago
Matt Jordan	a1803cb5f4	configs/samples/pjsip.conf.sample: Fix typo ... A ':' is not a valid token for starting a comment. Change-Id: I123592d93a83d1bdde3e352822881eb9da85e5ad	9 years ago
Matt Jordan	d29c17834c	res/res_hep_pjsip: Fix reported local IP address when bound to 'any' ... When bound to an 'any' address, e.g., 0.0.0.0, PJSIP reports as its local address the 'any' address, as opposed to the IP address we actually received the packet on. This can cause some confusion in Homer, as it will dutifully report what we send it. This patch uses the PJSIP inspection routines to determine which IP address we probably received the packet on based on the remote party's IP address. In the event that this fails, it falls back to the IP address natively reported by the transport. Change-Id: I076f835d2aef489e1ee1d01595b211eb2ce62da3	9 years ago
Joshua Colp	acdd0ae993	Merge "logger: Add PID to syslog messages."	9 years ago