Project

General

Profile

Bug #4352

Need to handle 401 Unauthorized

Added by keith 19 days ago. Updated 19 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
01/09/2020
Due date:
% Done:

0%

Resolution:

Description

It was noticed through a misconfiguration of upstream PBX at congress that osmo-sip-connector does not handle a 401 response from upstream.

In this case the upstream was responding with a 401 to our BYE.

osmo-sip-connector just terminates it's own leg anyway, leaving the other leg hanging.
granted, there's not a lot to be done from our side if upstream SIP stubbornly refuses to hang up, but we should probably handle this (what do RFCs say?) and indeed have some kind of credential system in osmo-sip-connector.

History

#1 Updated by laforge 19 days ago

On Thu, Jan 09, 2020 at 09:36:24AM +0000, keith [REDMINE] wrote:

osmo-sip-connector just terminates it's own leg anyway, leaving the other leg hanging.

that sounds like a bug.

granted, there's not a lot to be done from our side if upstream SIP stubbornly refuses to hang up, but we should probably handle this (what do RFCs say?) and indeed have some kind of credential system in osmo-sip-connector.

The assumption so far was that osmo-sip-connectors is not used directly with user-agents
on the remote side, but that it's always some SIP trunk. It was my understanding that
user/password based authentication is only used for UAs? If it's also commonly used with
sip trunks, then we should implement at least the most common authentication method[s].

#2 Updated by laforge 19 days ago

random notes...

  • digest authentication should be used these days, no basic authentication
  • SOFIA-SIP supports digest authentication, see auth_digest.h

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)