Opened 8 years ago

Closed 8 years ago

#1455 closed defect (fixed)

Incoming re-INVITE is unhandled if it comes in CONNECTING state (thanks Olle Frimanson for the report)

Reported by: bennylp Owned by: bennylp
Priority: normal Milestone: release-1.14
Component: pjsip Version: common
Keywords: Cc:
Backport to 1.x milestone: Backported:

Description (last modified by bennylp)

An incoming re-INVITE request will be ignored/unhandled if it is received while the invite session is in CONNECTING state (i.e. waiting for ACK from peer).

The correct behavior according to RFC 5407 (section 3.1.4) is as follows:

  • if the current offer-answer has completed, the re-INVITE should be accepted with 200/OK.
  • if the current offer-answer is still pending (i.e. we're waiting for an answer in the ACK), the re-INVITE must be answered with 491/Request Pending.

Unfortunately if we answer the re-INVITE with 200/OK, we will have two pending invite transactions, and we don't support that. Hence the solution that this ticket implements is to always answer with 491 for such re-INVITE.

Change History (2)

comment:1 Changed 8 years ago by bennylp

  • Description modified (diff)

comment:2 Changed 8 years ago by bennylp

  • Resolution set to fixed
  • Status changed from new to closed

(In [3959]) Fixed #1455: Incoming re-INVITE is unhandled if it comes in CONNECTING state (thanks Olle Frimanson for the report)

Note: See TracTickets for help on using tickets.