asterisk/asterisk.git
3 years agochan_sip: Support auth username for callbackextension feature
Timo Teräs [Fri, 3 Jun 2016 06:33:08 +0000 (09:33 +0300)]
chan_sip: Support auth username for callbackextension feature

ASTERISK-20527 #close

Change-Id: I659cf7f00836a09d09d146ad226a40477d731239

3 years agoMerge "pjsip_distributor.c: Use correct rdata info access method (Part 2)."
Joshua Colp [Wed, 1 Jun 2016 23:15:53 +0000 (18:15 -0500)]
Merge "pjsip_distributor.c: Use correct rdata info access method (Part 2)."

3 years agoMerge "logging,cdr,cel: Fix stringfield memory leak."
Joshua Colp [Wed, 1 Jun 2016 21:51:55 +0000 (16:51 -0500)]
Merge "logging,cdr,cel: Fix stringfield memory leak."

3 years agoMerge "pjproject_bundled: Move to pjproject 2.5"
Joshua Colp [Wed, 1 Jun 2016 20:13:48 +0000 (15:13 -0500)]
Merge "pjproject_bundled:  Move to pjproject 2.5"

3 years agologging,cdr,cel: Fix stringfield memory leak.
Richard Mudgett [Wed, 1 Jun 2016 18:57:53 +0000 (13:57 -0500)]
logging,cdr,cel: Fix stringfield memory leak.

The stringfields refactor to allow adding stringfields to the end of a
structure (f6f4cf459f43f072604927209b39646f84aaa2e2) exposed some
incomplete cleanup code by some stringfield users.

The most noticeable leaker is the logging system where there is a leak for
every log message generated.

ASTERISK-26078 #close
Reported by:  Etienne Lessard
Patches:
      jira_asterisk_26078_v13.patch (license #5621) patch uploaded
      by Richard Mudgett

Change-Id: If6a08b31336b492c3de6f9dfd07c447f8d5a8782

3 years agoMerge "Expand the scope of Dial Events"
Joshua Colp [Tue, 31 May 2016 21:36:35 +0000 (16:36 -0500)]
Merge "Expand the scope of Dial Events"

3 years agopjsip_distributor.c: Use correct rdata info access method (Part 2).
Richard Mudgett [Tue, 31 May 2016 18:02:15 +0000 (13:02 -0500)]
pjsip_distributor.c: Use correct rdata info access method (Part 2).

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: I4d519385a577f3e9d9193a88125e493cf17fa799

3 years agoMerge "followme: allow disabling callee prompt"
Joshua Colp [Tue, 31 May 2016 18:20:49 +0000 (13:20 -0500)]
Merge "followme: allow disabling callee prompt"

3 years agoMerge "ARI: Re-implement the ARI dial command, allowing for early bridging."
zuul [Tue, 31 May 2016 17:39:53 +0000 (12:39 -0500)]
Merge "ARI: Re-implement the ARI dial command, allowing for early bridging."

3 years agoMerge "res_pjsip_mwi_body_generator: Re-order the body items"
zuul [Tue, 31 May 2016 17:39:51 +0000 (12:39 -0500)]
Merge "res_pjsip_mwi_body_generator:  Re-order the body items"

3 years agoExpand the scope of Dial Events
Mark Michelson [Mon, 9 May 2016 20:00:56 +0000 (15:00 -0500)]
Expand the scope of Dial Events

Dial events up to this point have come in two flavors
* A Dial event with no status to indicate that dialing has begun
* A Dial event with a status to indicate that dialing has ended

With this change, Dial events have been expanded to also give
intermediate events, such as "RINGING", "PROCEEDING", and "PROGRESS".
This is especially useful for ARI dialing, as it gives the application
writer the opportunity to place a channel into an early bridge when
early media is detected.

AMI handles these in-progress dial events by sending a new event called
"DialState" that simply indicates that dial state has changed but has
not ended. ARI never distinguished between DialBegin and DialEnd, so no
change was made to the event itself.

Another change here relates to dial forwards. A forward-related event
was previously only sent when a channel was successfully able to forward
a call to a new channel. With this set of changes, if forwarding is
blocked, we send a Dial event with a forwarding destination but no
forwarding channel, since we were prevented from creating one. This is
again useful for ARI since application writers can now handle call
forward attempts from within their own application.

ASTERISK-25925 #close
Reported by Mark Michelson

Change-Id: I42cbec7730d84640a434d143a0d172a740995543

3 years agoMerge "res_pjsip: add "via_addr", "via_port", "call_id" to contact"
Joshua Colp [Tue, 31 May 2016 13:23:12 +0000 (08:23 -0500)]
Merge "res_pjsip: add "via_addr", "via_port", "call_id" to contact"

3 years agoMerge "res_pjsip: Add clarifying documentation to PJSIP_HEADER help text"
zuul [Tue, 31 May 2016 11:59:58 +0000 (06:59 -0500)]
Merge "res_pjsip: Add clarifying documentation to PJSIP_HEADER help text"

3 years agoMerge "multicast RTP: Add dialing options"
zuul [Tue, 31 May 2016 11:53:38 +0000 (06:53 -0500)]
Merge "multicast RTP: Add dialing options"

3 years agoMerge "res_pjsip: chatty verbose messages"
zuul [Tue, 31 May 2016 11:52:15 +0000 (06:52 -0500)]
Merge "res_pjsip: chatty verbose messages"

3 years agores_pjsip_mwi_body_generator: Re-order the body items
George Joseph [Tue, 31 May 2016 00:27:35 +0000 (18:27 -0600)]
res_pjsip_mwi_body_generator:  Re-order the body items

Re-ordered the body items so Message-Account is second.

Messages-Waiting: no
Message-Account: sip:1571@<IP Removed>:5060
Voice-Message: 0/0 (0/0)

ASTERISK-26065 #close
Reported-by: Ross Beer

Change-Id: If5d35a64656eac98c2dd5e490cc0b2807bed80c3

3 years agopjproject_bundled: Move to pjproject 2.5
George Joseph [Mon, 30 May 2016 15:58:35 +0000 (09:58 -0600)]
pjproject_bundled:  Move to pjproject 2.5

Although all the patches we had against 2.4.5 were applied by Teluu,
a new bug was introduced preventing re-use of tcp and tls transports
This patch removes all the previous patches against 2.4.5, updates
the version to 2.5, and adds a new patch to correct the transport
re-use problem.

Change-Id: I0dc6c438c3910f7887418a5832ca186aea23d068

3 years agores_pjsip: Add clarifying documentation to PJSIP_HEADER help text
Rusty Newton [Fri, 27 May 2016 17:25:55 +0000 (12:25 -0500)]
res_pjsip: Add clarifying documentation to PJSIP_HEADER help text

Added notes about when you can read or write headers. Specifically
about being able to read on the inbound channel and write on an
outbound channel.

ASTERISK-26063 #close
Reported by: Private Name
Tested by: Rusty Newton

Change-Id: Ibeb64af17d1f6451028b3c29855a3f151a01d8c5

3 years agomulticast RTP: Add dialing options
Mark Michelson [Thu, 26 May 2016 20:14:50 +0000 (15:14 -0500)]
multicast RTP: Add dialing options

This adds a new parameter to the end of a multicast RTP dialing string.
This parameter defines the following options:

* i: Set the interface from which multicast RTP is sent
* l: Set whether multicast packets are looped back to the sender
* t: Set the TTL for multicast packets
* c: Set the codec to use for RTP

ASTERISK-26068 #close
Reported by Mark Michelson

Change-Id: I033b706b533f0aa635c342eb738e0bcefa07e219

3 years agoARI: Re-implement the ARI dial command, allowing for early bridging.
Mark Michelson [Mon, 9 May 2016 19:48:51 +0000 (14:48 -0500)]
ARI: Re-implement the ARI dial command, allowing for early bridging.

ARI dial had been implemented using the Dial API. This made great sense
when dialing was 100% separate from bridging. However, if a channel were
to be added to a bridge during the dial attempt, there would be a
conflict between the dialing thread and the bridging thread. Each would
be attempting to read frames from the dialed channel and act on them.

The initial attempt to make the two play nice was to have the Dial API
suspend the channel in the bridge and stay in charge of the channel
until the dial was complete. The problem with this was that it was
riddled with potential race conditions. It also was not well-suited for
the case where the channel changed which bridge it was in during the
dial.

This new approach removes the use of the Dial API altogether. Instead,
the channel we are dialing is placed into an invisible ARI dialing
bridge. The bridge channel thread handles incoming frames from the
channel. If the channel is added to a real bridge, it is departed from
the invisible bridge and then added to the real bridge. Similarly, if
the channel is removed from the real bridge, it is automatically added
back to the invisible bridge if the dial attempt is still active.

This approach keeps the threading simple by always having the channel
being handled by bridge channel threads.

ASTERISK-25925

Change-Id: I7750359ddf45fcd45eaec749c5b3822de4a8ddbb

3 years agoMerge "app_voicemail: fix bugs, imap mm_status log change to debug"
zuul [Thu, 26 May 2016 22:46:01 +0000 (17:46 -0500)]
Merge "app_voicemail: fix bugs, imap mm_status log change to debug"

3 years agores_pjsip: add "via_addr", "via_port", "call_id" to contact
Alexei Gradinari [Thu, 19 May 2016 19:56:26 +0000 (15:56 -0400)]
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

3 years agores_pjsip: chatty verbose messages
Alexei Gradinari [Tue, 24 May 2016 21:56:49 +0000 (17:56 -0400)]
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

3 years agoapp_voicemail: fix bugs, imap mm_status log change to debug
Alexei Gradinari [Fri, 20 May 2016 18:56:30 +0000 (14:56 -0400)]
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

3 years agopjsip_distributor.c: Use correct rdata info access method.
Richard Mudgett [Wed, 25 May 2016 23:30:07 +0000 (18:30 -0500)]
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

3 years agofollowme: allow disabling callee prompt
Tzafrir Cohen [Tue, 3 May 2016 16:11:20 +0000 (19:11 +0300)]
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>

3 years agoMerge "res_pjsip_outbound_publish: Ensure publish is valid when explicitly destroying."
zuul [Wed, 25 May 2016 13:38:22 +0000 (08:38 -0500)]
Merge "res_pjsip_outbound_publish: Ensure publish is valid when explicitly destroying."

3 years agoMerge "Bridging: introduce "invisible" bridges."
Joshua Colp [Wed, 25 May 2016 10:32:55 +0000 (05:32 -0500)]
Merge "Bridging: introduce "invisible" bridges."

3 years agoMerge "res_pjsip: Only check transaction on transaction state events."
zuul [Wed, 25 May 2016 00:09:13 +0000 (19:09 -0500)]
Merge "res_pjsip: Only check transaction on transaction state events."

3 years agothreadpool: Fix potential data race.
Corey Farrell [Fri, 12 Feb 2016 15:59:44 +0000 (10:59 -0500)]
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

3 years agoMerge "func_odbc: single database connection should be optional"
Joshua Colp [Tue, 24 May 2016 14:28:03 +0000 (09:28 -0500)]
Merge "func_odbc: single database connection should be optional"

3 years agores_pjsip_outbound_publish: Ensure publish is valid when explicitly destroying.
Joshua Colp [Tue, 24 May 2016 10:28:17 +0000 (07:28 -0300)]
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

3 years agoMerge "ARI: Add the ability to download the media associated with a stored recording"
Joshua Colp [Mon, 23 May 2016 23:04:07 +0000 (18:04 -0500)]
Merge "ARI: Add the ability to download the media associated with a stored recording"

3 years agoMerge "chan_rtp.c: Cleanup ast_request() parameter parsing."
Joshua Colp [Mon, 23 May 2016 21:17:57 +0000 (16:17 -0500)]
Merge "chan_rtp.c: Cleanup ast_request() parameter parsing."

3 years agoMerge "Makefile: remove OSARCH check for init install"
zuul [Mon, 23 May 2016 21:16:04 +0000 (16:16 -0500)]
Merge "Makefile: remove OSARCH check for init install"

3 years agoBridging: introduce "invisible" bridges.
Mark Michelson [Mon, 9 May 2016 19:27:53 +0000 (14:27 -0500)]
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

3 years agoMerge "func_curl: Don't trim response text on non-ASCII characters"
Joshua Colp [Mon, 23 May 2016 14:43:20 +0000 (09:43 -0500)]
Merge "func_curl: Don't trim response text on non-ASCII characters"

3 years agoMerge "parking.h: Update ast_parking_park_call() doxygen to reality."
Joshua Colp [Mon, 23 May 2016 11:15:59 +0000 (06:15 -0500)]
Merge "parking.h: Update ast_parking_park_call() doxygen to reality."

3 years agores_pjsip: Only check transaction on transaction state events.
Joshua Colp [Sun, 22 May 2016 16:03:20 +0000 (13:03 -0300)]
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

3 years agofunc_curl: Don't trim response text on non-ASCII characters
Ivan Poddubny [Sat, 21 May 2016 10:42:45 +0000 (13:42 +0300)]
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

3 years agochan_rtp.c: Cleanup ast_request() parameter parsing.
Richard Mudgett [Sat, 21 May 2016 00:03:53 +0000 (19:03 -0500)]
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

3 years agoparking.h: Update ast_parking_park_call() doxygen to reality.
Richard Mudgett [Fri, 20 May 2016 21:59:52 +0000 (16:59 -0500)]
parking.h: Update ast_parking_park_call() doxygen to reality.

ASTERISK-26029

Change-Id: I2db14d102a48d3224010e6d1c69e856373cc1260

3 years agofunc_odbc: single database connection should be optional
Alexei Gradinari [Thu, 12 May 2016 20:18:22 +0000 (16:18 -0400)]
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

3 years agores_pjsip: Match dialogs on responses better.
Mark Michelson [Fri, 20 May 2016 14:39:10 +0000 (09:39 -0500)]
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

3 years agoARI: Add the ability to download the media associated with a stored recording
Matt Jordan [Wed, 18 May 2016 11:19:58 +0000 (06:19 -0500)]
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

3 years agores_sorcery_astdb: Filter fields to only the registered ones.
Joshua Colp [Thu, 19 May 2016 16:41:45 +0000 (13:41 -0300)]
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

3 years agoMerge "res_pjsip_empty_info: Respond to empty SIP INFO packets"
Joshua Colp [Thu, 19 May 2016 19:46:11 +0000 (14:46 -0500)]
Merge "res_pjsip_empty_info: Respond to empty SIP INFO packets"

3 years agoMerge "res_pjsip: Endpoint IP Access Controls"
Joshua Colp [Thu, 19 May 2016 15:39:58 +0000 (10:39 -0500)]
Merge "res_pjsip: Endpoint IP Access Controls"

3 years agores_pjsip_empty_info: Respond to empty SIP INFO packets
snuffy [Tue, 10 May 2016 02:40:08 +0000 (12:40 +1000)]
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

3 years agoMerge "udptl: Don't eat sequence numbers until OK is received"
Joshua Colp [Thu, 19 May 2016 10:33:13 +0000 (05:33 -0500)]
Merge "udptl:  Don't eat sequence numbers until OK is received"

3 years agoMerge "logger: Support JSON logging with Verbose messages"
Joshua Colp [Thu, 19 May 2016 10:31:19 +0000 (05:31 -0500)]
Merge "logger: Support JSON logging with Verbose messages"

3 years agoMerge "res_hep: Provide an option to pick the UUID type"
Joshua Colp [Thu, 19 May 2016 10:26:57 +0000 (05:26 -0500)]
Merge "res_hep: Provide an option to pick the UUID type"

3 years agoMerge "res/res_hep_pjsip: Fix reported local IP address when bound to 'any'"
Joshua Colp [Thu, 19 May 2016 10:23:21 +0000 (05:23 -0500)]
Merge "res/res_hep_pjsip: Fix reported local IP address when bound to 'any'"

3 years agoMakefile: remove OSARCH check for init install
Tzafrir Cohen [Wed, 18 May 2016 15:58:20 +0000 (18:58 +0300)]
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>

3 years agores_pjsip_exten_state: Use the extension for publishing to.
Joshua Colp [Tue, 10 May 2016 16:28:04 +0000 (13:28 -0300)]
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

3 years agores_pjsip_outbound_publish: Add multi-user support per configuration
Kevin Harwell [Tue, 3 May 2016 21:07:23 +0000 (16:07 -0500)]
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

3 years agoMerge "CHANGES: Update formatting of items"
Joshua Colp [Wed, 18 May 2016 23:35:32 +0000 (18:35 -0500)]
Merge "CHANGES: Update formatting of items"

3 years agoMerge "ARI: Add the ability to play multiple media URIs in a single operation"
Joshua Colp [Wed, 18 May 2016 23:35:20 +0000 (18:35 -0500)]
Merge "ARI: Add the ability to play multiple media URIs in a single operation"

3 years agoMerge "chan_sip: Prevent extra Session-Expires headers from being added"
Joshua Colp [Wed, 18 May 2016 23:27:28 +0000 (18:27 -0500)]
Merge "chan_sip:  Prevent extra Session-Expires headers from being added"

3 years agoudptl: Don't eat sequence numbers until OK is received
George Joseph [Wed, 18 May 2016 12:54:14 +0000 (06:54 -0600)]
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

3 years agoCHANGES: Update formatting of items
Matt Jordan [Sun, 15 May 2016 17:22:42 +0000 (12:22 -0500)]
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

3 years agoARI: Add the ability to play multiple media URIs in a single operation
Matt Jordan [Mon, 18 Apr 2016 23:17:08 +0000 (18:17 -0500)]
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

3 years agochan_sip: Prevent extra Session-Expires headers from being added
George Joseph [Tue, 17 May 2016 16:14:51 +0000 (10:14 -0600)]
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

3 years agores_pjsip_outbound_registration: Clean up state when registration is deleted
George Joseph [Mon, 16 May 2016 20:29:38 +0000 (14:29 -0600)]
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

3 years agoMerge "configs/samples/pjsip.conf.sample: Fix typo"
zuul [Mon, 16 May 2016 18:53:00 +0000 (13:53 -0500)]
Merge "configs/samples/pjsip.conf.sample: Fix typo"

3 years agores_pjsip: Set TCP_NODELAY on TCP transports
George Joseph [Mon, 16 May 2016 00:05:34 +0000 (18:05 -0600)]
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

3 years agologger: Support JSON logging with Verbose messages
Matt Jordan [Sat, 14 May 2016 12:24:07 +0000 (07:24 -0500)]
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

3 years agoconfigs/samples/pjsip.conf.sample: Fix typo
Matt Jordan [Sun, 15 May 2016 02:48:56 +0000 (21:48 -0500)]
configs/samples/pjsip.conf.sample: Fix typo

A ':' is not a valid token for starting a comment.

Change-Id: I123592d93a83d1bdde3e352822881eb9da85e5ad

3 years agores/res_hep_pjsip: Fix reported local IP address when bound to 'any'
Matt Jordan [Thu, 12 May 2016 12:08:08 +0000 (07:08 -0500)]
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

3 years agoMerge "logger: Add PID to syslog messages."
Joshua Colp [Sun, 15 May 2016 01:37:43 +0000 (20:37 -0500)]
Merge "logger: Add PID to syslog messages."

3 years agores_ari: Correct Location headers returned by some ARI resources
Sean Bright [Sat, 14 May 2016 17:29:09 +0000 (13:29 -0400)]
res_ari: Correct Location headers returned by some ARI resources

The Location headers returned by:

 * /bridges/{bridgeId}/play
 * /bridges/{bridgeId}/record
 * /channels/{channelId}/play
 * /channels/{channelId}/record

Did not have the '/ari' prefix, and in the case of the 'play' resources, were
using 'playback' instead of 'playbacks.'

Change-Id: I957c58a3a1471bf477dae7c67faa1b74fcd9241c

3 years agores_hep: Provide an option to pick the UUID type
Matt Jordan [Thu, 12 May 2016 01:17:15 +0000 (20:17 -0500)]
res_hep: Provide an option to pick the UUID type

At one point in time, it seemed like a good idea to use the Asterisk
channel name as the HEP correlation UUID. In particular, it felt like
this would be a useful identifier to tie PJSIP messages and RTCP
messages together, along with whatever other data we may eventually send
to Homer. This also had the benefit of keeping the correlation UUID
channel technology agnostic.

In practice, it isn't as useful as hoped, for two reasons:
1) The first INVITE request received doesn't have a channel. As a
   result, there is always an 'odd message out', leading it to be
   potentially uncorrelated in Homer.
2) Other systems sending capture packets (Kamailio) use the SIP Call-ID.
   This causes RTCP information to be uncorrelated to the SIP message
   traffic seen by those capture nodes.

In order to support both (in case someone is trying to use res_hep_rtcp
with a non-PJSIP channel), this patch adds a new option, uuid_type, with
two valid values - 'call-id' and 'channel'. The uuid_type option is used
by a module to determine the preferred UUID type. When available, that
source of a correlation UUID is used; when not, the more readily available
source is used.

For res_hep_pjsip:
 - uuid_type = call-id: the module uses the SIP Call-ID header value
 - uuid_type = channel: the module uses the channel name if available,
                        falling back to SIP Call-ID if not
For res_hep_rtcp:
 - uuid_type = call-id: the module uses the SIP Call-ID header if the
                        channel type is PJSIP and we have a channel,
                        falling back to the Stasis event provided
                        channel name if not
 - uuid_type = channel: the module uses the channel name

ASTERISK-25352 #close

Change-Id: Ide67e59a52d9c806e3cc0a797ea1a4b88a00122c

3 years agoMerge "config_transport: Tell pjproject to allow all SSL/TLS protocols"
zuul [Fri, 13 May 2016 22:57:55 +0000 (17:57 -0500)]
Merge "config_transport:  Tell pjproject to allow all SSL/TLS protocols"

3 years agores_pjsip: Endpoint IP Access Controls
Alexei Gradinari [Fri, 13 May 2016 16:46:52 +0000 (12:46 -0400)]
res_pjsip: Endpoint IP Access Controls

With the old SIP module we can use IP access controls per peer.
PJSIP module missing this feature.

This patch added next configuration Endpoint options:
    "acl" - list of IP ACL section names in acl.conf
    "deny" - List of IP addresses to deny access from
    "permit" - List of IP addresses to permit access from
    "contact_acl" - List of Contact ACL section names in acl.conf
    "contact_deny" - List of Contact header addresses to deny
    "contact_permit" - List of Contact header addresses to permit

This patch also better logging failed request:
    add custom message instead of "No matching endpoint found"
    add SIP method to logging

ASTERISK-25900

Change-Id: I456dea3909d929d413864fb347d28578415ebf02

3 years agoMerge "pjsip_distributor: Add missing newline to NOTICE"
zuul [Fri, 13 May 2016 11:21:23 +0000 (06:21 -0500)]
Merge "pjsip_distributor:  Add missing newline to NOTICE"

3 years agoMerge "basic-cfg: asterisk.conf: don't set languages"
Joshua Colp [Fri, 13 May 2016 09:53:39 +0000 (04:53 -0500)]
Merge "basic-cfg: asterisk.conf: don't set languages"

3 years agoMerge "basic-cfg: asterisk.conf: debug level 5 spams"
Joshua Colp [Fri, 13 May 2016 09:53:27 +0000 (04:53 -0500)]
Merge "basic-cfg: asterisk.conf: debug level 5 spams"

3 years agoMerge "basic-cfg: asterisk.conf: defaults of options"
Joshua Colp [Fri, 13 May 2016 09:53:13 +0000 (04:53 -0500)]
Merge "basic-cfg: asterisk.conf: defaults of options"

3 years agoMerge "followme: delete the right recorded name file"
zuul [Fri, 13 May 2016 02:44:11 +0000 (21:44 -0500)]
Merge "followme: delete the right recorded name file"

3 years agoMerge "basic-cfg: asterisk.conf: remove [directories]"
zuul [Fri, 13 May 2016 00:52:13 +0000 (19:52 -0500)]
Merge "basic-cfg: asterisk.conf: remove [directories]"

3 years agoUse doubles instead of floats for conversions when comparing strings.
Mark Michelson [Thu, 12 May 2016 19:36:25 +0000 (14:36 -0500)]
Use doubles instead of floats for conversions when comparing strings.

In 13.9.0, there was an issue where PJSIP contacts added to an AOR would
be deleted at seemingly random times.

One reason this was happening was because of an operation to retrieve
the contacts whose expiration time was less than or equal to the current
time. When retrieving existing contacts, the contact's expiration time
and the current time were converted from a string to a float, and those
two floats were compared.

On some systems, including mine, this conversion was horribly off. For
instance, I could regularly see the string "1463079214" get converted
into 1463079168.000000. When switching from using a float to using a
double, the conversion was as expected.

Why was the conversion to float off? My best guess is that the
conversion to float was attempting to store the entire value in the 23
bit significand of the IEEE-754 floating point number. In particular, if
you take only the 23 most significant bits of 1463079214, you get the
messed up 1463079168 that we were seeing in the conversion. It likely
was possible to get a more precise value by composing the number using
an exponent, but the conversion did not work that way. With a double,
you have a 52 bit significand, allowing the entire value to fit there,
and thereby allowing an accurate conversion.

ASTERISK-26007 #close
Reported by Greg Siemon

Change-Id: I83ca7944aae8b7cd994b254c78ec02411d321070

3 years agoMerge "res_pjsip_outbound_registration: generate correct Contact URI for TLS"
zuul [Thu, 12 May 2016 19:25:43 +0000 (14:25 -0500)]
Merge "res_pjsip_outbound_registration: generate correct Contact URI for TLS"

3 years agopjsip_distributor: Add missing newline to NOTICE
George Joseph [Thu, 12 May 2016 14:13:55 +0000 (08:13 -0600)]
pjsip_distributor:  Add missing newline to NOTICE

There was a newline missing from the end of the "no matching endpoint" notice.

Change-Id: Idc11fe5bc0354072291663dbffe648c471e39181

3 years agores_pjsip_outbound_registration: generate correct Contact URI for TLS
Sebastian Damm [Tue, 10 May 2016 15:19:48 +0000 (17:19 +0200)]
res_pjsip_outbound_registration: generate correct Contact URI for TLS

There are two types of SIP URIs indicating a secure transport:
* sips:user@example.org
* sip:user@example.org;transport=tls

When using a sips URI, Asterisk checks incoming INVITEs and answers from
the other side for sips URIs, and rejects the packet if there are only
sip URIs. So Asterisk should only generate a sips Contact URI if the
other side supports it.

This patch makes Asterisk generate either a sip or sips Contact URI
depending on the format of the server URI.

If you want a sip URI, use:
server_uri=sip:example.org\;transport=tls

If you want a sips URI, use:
server_uri=sips:example.org

ASTERISK-25990 #close
Reported-by: Sebastian Damm

Change-Id: I5ae57d6531ce940b5fc64d5cd2673e60db0f9ba2

3 years agologger: Add PID to syslog messages.
Alexei Gradinari [Thu, 5 May 2016 21:41:21 +0000 (17:41 -0400)]
logger: Add PID to syslog messages.

During refactoring of this support the addition of
the PID to messages was removed. This change adds it
back in.

ASTERISK-25538 #close

Change-Id: Ie2d43b0652e59b7ac319a7dba94501540d70ba36

3 years agoconfigure: Fix errors with AST_UNDEFINED_SANITIZER/AST_LEAK_SANITIZER
Matt Jordan [Wed, 11 May 2016 19:07:17 +0000 (14:07 -0500)]
configure: Fix errors with AST_UNDEFINED_SANITIZER/AST_LEAK_SANITIZER

When running on a system that does not support or use AST_UNDEFINED_SANITIZER
or AST_LEAK_SANITIZER, the configure script would incorrectly set those
constants to a blank value, e.g., 'AST_UNDEFINED_SANITIZER='. This would
cause menuselect to error out, complaining that a blank value is not a
valid option. This patch corrects the issue by setting the value to 0 if
the options that those constants enable/disable is not found.

Change-Id: Ib39814aaf940f308d500c1e026edb3d70de47fba

3 years agoMerge "res_pjsip_outbound_publish: state potential dropped on reloads/realtime fetches"
Joshua Colp [Wed, 11 May 2016 17:57:34 +0000 (12:57 -0500)]
Merge "res_pjsip_outbound_publish: state potential dropped on reloads/realtime fetches"

3 years agoMerge "res_pjsip_outbound_publishing: After unloading the library won't load again"
Joshua Colp [Wed, 11 May 2016 17:57:24 +0000 (12:57 -0500)]
Merge "res_pjsip_outbound_publishing: After unloading the library won't load again"

3 years agoMerge "res_pjsip_outbound_publish: Won't unload if condition wait times out"
Joshua Colp [Wed, 11 May 2016 17:57:13 +0000 (12:57 -0500)]
Merge "res_pjsip_outbound_publish: Won't unload if condition wait times out"

3 years agoMerge "res_pjsip_outbound_publish: Ref leak in off nominal callback paths"
Joshua Colp [Wed, 11 May 2016 17:57:04 +0000 (12:57 -0500)]
Merge "res_pjsip_outbound_publish: Ref leak in off nominal callback paths"

3 years agoMerge "res_pjsip_outbound_publish: Potential crash due to off nominal path"
Joshua Colp [Wed, 11 May 2016 17:56:52 +0000 (12:56 -0500)]
Merge "res_pjsip_outbound_publish: Potential crash due to off nominal path"

3 years agoMerge "res_pjsip: improve realtime performance"
Joshua Colp [Wed, 11 May 2016 15:58:54 +0000 (10:58 -0500)]
Merge "res_pjsip: improve realtime performance"

3 years agoMerge "res_fax/t38_gateway: Peer V.21 session is created on wrong channel"
zuul [Wed, 11 May 2016 15:36:34 +0000 (10:36 -0500)]
Merge "res_fax/t38_gateway: Peer V.21 session is created on wrong channel"

3 years agofollowme: delete the right recorded name file
Tzafrir Cohen [Tue, 10 May 2016 13:17:29 +0000 (16:17 +0300)]
followme: delete the right recorded name file

FollowMe with the option a records the name of the caller and plays it
to the callee. However it has failed to clean up that recorded file
as it tried to delete the file name without the '.sln' extension.

ASTERISK-26008 #close

Change-Id: I79d7b1be7d5cde57bf076d9389e2a8a4422776ec
Signed-off-by: Tzafrir Cohen <tzafrir.cohen@xorcom.com>

3 years agoMerge "app_confbridge: Add a regcontext option for confbridge bridge profiles."
Joshua Colp [Tue, 10 May 2016 09:48:35 +0000 (04:48 -0500)]
Merge "app_confbridge: Add a regcontext option for confbridge bridge profiles."

3 years agobasic-cfg: asterisk.conf: don't set languages
Tzafrir Cohen [Tue, 10 May 2016 08:10:55 +0000 (11:10 +0300)]
basic-cfg: asterisk.conf: don't set languages

* No need to set language in a miniml configuration. 'en' will do just
  fine.
* It would be useful to have an example of setting it to a different
  language.
* Setting the documentation language explicitly is likewise not
  required. Setting it to a different value is not common. At least
  until there is a set of translated documentation.

Change-Id: I94d91ea34e129925f25af81ef8dc0906fb568cb7
Signed-off-by: Tzafrir Cohen <tzafrir.cohen@xorcom.com>

3 years agobasic-cfg: asterisk.conf: debug level 5 spams
Tzafrir Cohen [Tue, 10 May 2016 08:08:33 +0000 (11:08 +0300)]
basic-cfg: asterisk.conf: debug level 5 spams

Don't suggest users to use debug level 5, which spews (usually
non-useful) debug information. Reduce the suggestion to (an
arbitrarily-selected) level 2.

Change-Id: Ib53195f78945970956ff59ef13fa89b90e0fcd60
Signed-off-by: Tzafrir Cohen <tzafrir.cohen@xorcom.com>

3 years agobasic-cfg: asterisk.conf: defaults of options
Tzafrir Cohen [Tue, 10 May 2016 08:06:10 +0000 (11:06 +0300)]
basic-cfg: asterisk.conf: defaults of options

Note the default of remmed-out options. To clarify that those values are
not the defaults.

Change-Id: I849c29b7a710f0abc37355fcb5bfee335ae30738
Signed-off-by: Tzafrir Cohen <tzafrir.cohen@xorcom.com>

3 years agobasic-cfg: asterisk.conf: remove [directories]
Tzafrir Cohen [Tue, 10 May 2016 07:56:40 +0000 (10:56 +0300)]
basic-cfg: asterisk.conf: remove [directories]

A minimal configuration does not need to explicitly spell out the
directories. The built-in defaults will do just fine. In many cases
they are wrong.

Change-Id: Id1a671e5c5e9923765a4156b57f9f7e263fdd26c
Signed-off-by: Tzafrir Cohen <tzafrir.cohen@xorcom.com>

3 years agoMerge "res_pjsip_authenticator_digest: Don't use source port in nonce verification"
zuul [Tue, 10 May 2016 03:56:53 +0000 (22:56 -0500)]
Merge "res_pjsip_authenticator_digest: Don't use source port in nonce verification"