Option to accept call replace when in early state and as UAS

[nanang]

A user likes to have same transfer behaviour as he is used to his old analogue PABX. The user have an active call and wants to transfer it to another extension, but only when the extension is free. So first, the user put the 1st call in hold and invoke a new call, once the alert tone comes up (receiving 180), the user press transfer.

Currently, we will reject such transfer request, in line to ​RFC 3891 section 3:

If the Replaces header field matches an early dialog that was not
initiated by this UA, it returns a 481 (Call/Transaction Does Not
Exist) response to the new INVITE, and leaves the matched dialog
unchanged. Note that since Replaces matches only a single dialog,
the replacement dialog will not be retargeted according to the same
forking logic as the original request which created the early dialog.

Thanks Peter Koletzki for the feedback and the patch.

[nanang]

In r4267:

• Added settings to accept call replace when in early state and as UAS:
  • accept_replace_in_early_state in pjsip_cfg_t for run time setting, and
  • PJSIP_ACCEPT_REPLACE_IN_EARLY_STATE for initial value and compile time setting.

[nanang]

In 4268:

Re #1587:

• Don't answer call replace request with 200 if the replaced call hasn't reach confirmed state and has UAS role.
• Only apply accept_replace_in_early_state when call is in early state.

[nanang]

In 4269:

Re #1587: Respond to call replace request with the last provisional response sent in the replaced call.