Wenpeng Song authored 8 months ago and Yalu Zhang committed 8 months ago

cherry-pick the following changes from devel
- When SIP response 408/503/500 is received for SIP Register requests
  to all server addresses, the failover retry will be scheduled
  with certain time interval.
- If number of continuous failed retries reached 'failover_max_retries',
  the SIP registraion will be given up. By default, the number is '-1',
  i.e. unlimited.
- 'failover_interval1' is used between normal failover retries, which
  is 10 seconds by default.
- 'failover_interval2' is used once after every 3 continuous retries,
  which is 60 seconds by default.

More timer (T1,T2,T4,TD/TB) configuration added from asterisk to pjsip.

Priority after this changes:
* retry_after (if received, as above diagram)
* failover_max_retries (if have non-zero values, -1 as infinitive)
* retry_interval (if set, default 1 if not set)
* above diagram base on RFC

Wenpeng Song authored 9 months ago and Yalu Zhang committed 9 months ago

According to asterisk doc:

* prefer: \< pending | configured \>\
  pending - The codec list in the received SDP answer.\
  configured - The codec list from the endpoint.
* operation : \< union | intersect | only_preferred | only_nonpreferred \>\
  `union` - Merge the lists with the preferred codecs first.\
  intersect - Only common codecs with the preferred codecs first.\
  only_preferred - Use only the preferred codecs.\
  only_nonpreferred - Use only the non-preferred codecs.
* keep : \< all | first \> - all - After the operation, keep all codecs.\
  first - After the operation, keep only the first codec.

But in current Asterisk implementation, the `remote_first` which we currently used for incoming
preference has been interrupted wrongly with option "`union`"(merge).

This leading to the issue that unsupported codec could also got an valid joint cap during
ast_sip_session_create_joint_call_cap even if there has no common codec(local codec will be
used), but then failure in the later stage which given the `500 SDP negotiation failed`
response and hangup.

After this correction, unsupported codec will not receiving an valid joint cap during ast_sip_session_create_joint_call_cap if there has no common codec, then a `488 Not Acceptable
Here` response will be send as expected.

This also improve the behavior when an incoming call has no common codec at all: INVITE-
100(Trying)-488(Not Acceptable Here)-ACK, will not have 180(Ringing) in this case.

Grzegorz Sluja authored 9 months ago and Yalu Zhang committed 9 months ago

According to RFC6228 Chapter 4, when UAC sends an initial dialog initiation request
and is willing to receive 199 responses, it must insert '199' option-tag' in the
Supported header field.

Grzegorz Sluja authored 9 months ago and Yalu Zhang committed 9 months ago

Before this change, the next registration happens 10 (defined by REREGISTER_BUFFER_TIME) seconds
before expiration.

This reverts merge request !172

This is to avoid memory corruption issue that happens when more than one thread calls ubus_free() which frees the global buffer which is defined in libubus.

Wenpeng Song authored 1 year ago and Yalu Zhang committed 1 year ago

When SIP un-registration request got an 200 OK with expiration value which is not 0 (due to the
server setting and network), it is treated as registration success based on the non zero expiration value. This made the other procedures following and it went into an uncontrollable
stage, i.e. unstoppable loop of the un-registration requests until crash.

Solution
Retrieve the requested expiration if possible, and check it together with the received expiration
in response to identify if the 200 OK is to register or unregister.

This reverts commit 3c8116c8. It has
been a merge that has been acidentally squashed into one commit with the
consequence that all history has been lost. The next commit will be a
proper merge commit rectifying this.

Grzegorz Sluja authored 1 year ago and Yalu Zhang committed 1 year ago

There was no audio for 3-way conference when sRTP is used.
For 2-way calls frame->seqno is taken from DSP and is used by asterisk for the sequence number
in RTP headers. However for 3-way conference the sequence number is generated by asterisk and
it has to be greater than the previous value, otherwise libsrtp refuses to forward 'too old'
RTP packets.

George Joseph authored 1 year ago and Wenpeng Song committed 1 year ago

Commit f66f77fa last year prevents the res_pjsip_exten_state and
res_pjsip_mwi modules from unloading due to possible pjproject
asserts if the modules are reloaded. A side effect of the
implementation is that the taskprocessors these modules use aren't
being released. When asterisk is doing a graceful shutdown, it
waits AST_TASKPROCESSOR_SHUTDOWN_MAX_WAIT seconds for all
taskprocessors to stop but since those 2 modules don't release
theirs, the shutdown hangs for that amount of time.

This change allows the modules to be unloaded and their resources to
be released when ast_shutdown_final is true.

Resolves: #379

Wenpeng Song authored 1 year ago and Yalu Zhang committed 1 year ago

This hook function is supposed to return PJ_SUCCESS in order to let a SIP request be
transmitted.

This reverts commit 0f97e870.

Wenpeng Song authored 1 year ago and Yalu Zhang committed 1 year ago

The purpose is to avoid crash during closing.
Also enhance the pointer validation check in sipaddress_on_outgoing_inv_request().

Lukasz Kotasa authored 1 year ago and Yalu Zhang committed 1 year ago

The ast_sip_dialog_get_session function returns the session with reference count
increased. This was not taken into account and was causing sessions to remain
around when they should not be.

Wenpeng Song authored 1 year ago and Yalu Zhang committed 1 year ago

Session invitation is not ready (NULL) on "session_on_tx_request" (before sending the request)
when the function for setting SIPIPAdress is called in the current version.
Call the function under "session_inv_on_tsx_state_changed" (just after the request be sent) 
instead.

Grzegorz Sluja authored 1 year ago and Yalu Zhang committed 1 year ago

Our commits to the previous version have been rebased.

In ast_sip_session_terminate(), reset both active and pending media to prevent
non-freed resources after a call. Otherwise RTP/RTCP ports won't be closed after
the call in some call scenarios, e.g. a non-answered incoming call. In that case,
there are no active media sessions before the swapping.

Wenpeng Song authored 1 year ago and Yalu Zhang committed 1 year ago

- Disable the trans-coding steps from set_cap which has been only used for outgoing call
  negotiation. Ignore trans-coding path failure
- Add codec sync for early media with AST_CONTROL_PROGRES

Lukasz Kotasa authored 1 year ago and Yalu Zhang committed 1 year ago

Reduce the retry-timer from 60s to 1s.

The SUBSCRIBE request for MWI is sent in the following conditions:
* mwi is enabled in asterisk configuration: option mwi_enable '1'
* SUBSCRIBE is sent after registration succeeds with expiration set to the same value as REGISTER.

We should also return all codecs on an re-INVITE without SDP for a
call that used late offer (e.g. no SDP in the initial INVITE, SDP
in the ACK). Bugfix for feature introduced in ASTERISK-30193
(https://issues.asterisk.org/jira/browse/ASTERISK-30193)

Migration from previous gerrit change that was not merged.

(cherry picked from commit 37a41a2a20688a0c0c84d0d3a888f0b598e12060)

When using mediasec, requests sent after a 401 must still contain the
Security-Client header according to
draft-dawes-sipcore-mediasec-parameter.

Resolves: #48
(cherry picked from commit f3cc1e7fbd08b1dc90bc7a1c13afae42a7210bf1)

The current STIR/SHAKEN signing process is inconsistent with the
RFCs in a couple ways that can cause interoperability issues.

RFC8225 specifies that the keys must be ordered lexicographically, but
currently the fields are simply ordered according to the order
in which they were added to the JSON object, which is not
compliant with the RFC and can cause issues with some carriers.

To fix this, we now leverage libjansson's ability to dump a JSON
object sorted by key value, yielding the correct field ordering.

Additionally, telephone numbers must have any leading + prefix removed
and must not contain characters outside of 0-9, *, and # in order
to comply with the RFCs. Numbers are now properly formatted as such.

ASTERISK-30407 #close

Change-Id: Iab76d39447c4b8cf133de85657dba02fda07f9a2
(cherry picked from commit 66a7cff57ecc4514c28071981037afa72ef0d4b9)