Skip to contentSkip to navigationSkip to topbar
Page toolsOn this pageProducts used
Looking for more inspiration?Visit the

80902: No Active Session


ERROR: 80902

error-80902 page anchor
PROXY
ERROR

This error occurs when Proxy receives a call to a Proxy Number from a caller who is not a Participant in an open Session. Proxy Sessions map two Participants for a temporary conversation, so a call that arrives after a Session is closed, expired, or never created is treated as out-of-session traffic.

Possible causes

possible-causes page anchor
  • The caller's phone number was never added to the Session as a Participant identifier.
  • There is no open Session for the caller because the Session was closed, failed, or expired based on ttl or dateExpiry.
  • The caller dialed a different masked number than the proxyIdentifier assigned to that Participant. Proxy expects the participant to call the assigned Proxy Number to reach the other party.
  • The Service was not configured with outOfSessionCallbackUrl to handle calls that reach a closed or non-existent Session.
  • Create the Session before either party places the call. Add the caller and the other party as Participants in that Session.
  • Verify that the caller's real phone number matches the Participant identifier stored in the intended Session and that the caller is dialing the assigned proxyIdentifier.
  • Review the Session status and expiration settings. Increase the Service defaultTtl or set the Session ttl or dateExpiry so the Session stays open for the full lifetime of the conversation.
  • Configure outOfSessionCallbackUrl if you need to handle calls that arrive after a Session ends or before one exists. Return valid TwiML to play a message or redirect the call, or return auto-create Session JSON to create the Session and Participants when appropriate.

Additional resources

additional-resources page anchor