Opened 5 years ago

Closed 5 years ago

#2164 closed defect (fixed)

Subscription may get terminated when NOTIFY is challenged

Reported by: ming Owned by: bennylp
Priority: normal Milestone: release-2.9
Component: pjsip Version: trunk
Keywords: Cc:
Backport to 1.x milestone: Backported: no

Description

Based on the ​RFC 3265:

A NOTIFY request is considered failed if the response times out, or a
non-200 class response code is received which has no "Retry-After"
header and no implied further action which can be taken to retry the
request (e.g., "401 Authorization Required".)

However, our current implementation terminates the subscription for ALL non-200 with no retry-after, even for 401/407, which shouldn't be the case.

Change History (1)

comment:1 Changed 5 years ago by ming

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

In 5917:

Fixed #2164: Subscription may get terminated when NOTIFY is challenged

Note: See TracTickets for help on using tickets.