Versions Compared

Old Version 1

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

 

This article describes the steps necessary to configure the 

Spacevars
0series
or 
Spacevars
0series2
product
with a SIP peer or with an Internet Telephony Service Provider (ITSP) that requires digest authentication with 401 Unauthorized challenge.

On this Page

Panel

In this section:

Section
Column
width400px
Table of Contents
maxLevel3

column
Panel

Related Articles:

Prerequisites

General

This document assumes that you have already created a Signaling Group and a SIP Server table for the ITSP.

Software Version

Verify that your your

Spacevars
0product
is loaded with the correct boot image version and that your SBC Edge base software version is at least version 2.0.0, build 108.

System Licenses

TheThe 

Spacevars
0product
system must have the necessary licenses to make calls.

...

  • Creating a Remote Authorization Table
  • Assigning the Remote Authorization Table to the SIP Server Table
  • Assigning the SIP Server Table to the Signaling Group for the ITSP

Pagebreak

  1. Add a Remote Authorization Table

    Image Removed

    .

  2. Add a Remote Authorization entry.

    Image Removed

  3. Assign the Remote Authorization Table to the SIP Server Table

    Image Removed

    .

Additional Information

Call Flow

The call flow below depicts an outbound call from Lync to ITSP via Sonus

Spacevars
0company
SBC 1000/2000.

  • After the initial INVITE from the Mediation server, 
    Spacevars
    0product
    (UA) sends an INVITE request to the ITSP proxy server (UAS).
  • Spacevars
    0product
     then receives 100 Trying and then 401 Unauthorized request from the ITSP proxy server.
  • Spacevars
    0product
    , acting as a UA, then re-sends the request and authenticates itself by including an Authorization header field with the request.
  • The Authorization field value consists of credentials containing the authentication information of the UA for the realm of the resource being requested as well as parameters required in support of authentication and replay protection.
  • The Realm, Username and Password information are taken from the Remote Authorization Table entry based on the username that is provided by the realm provided by the UAS.
Panel
borderStylenone

Caption
0Figure
1Call Flow

Image Modified

Call Debugging Trace

The 

Spacevars
0product
debug log produced at Trace level will show the information that is used to compute the MD5 string used in the Authorization header:

Code Block
none
none
[2012-04-12 16:17:40,303] 5688 0001 com.net.ux.sip TRACE (Credentials.cpp:451) - computeResponse: creating credentials:
   algorithm : "MD5"
   userName  : "d8Er27ScWIQ"
   passWord  : "uw83i29BeY3x"
   realm     : "ITSPRealm"
   nonce     : "ITSPRealmDe98wSj8euJdU8SHs8"
   cNonce    : "baea32a3"
   nonceCount: "00000001"
   qop       : "auth"
   method    : "INVITE"
   uri       : "sip:15105742474@10.0.0.10:5070;user=phone"

Pagebreak