This article describes the steps necessary to configure the SBC Edge with a SIP peer or with an Internet Telephony Service Provider (ITSP) that requires digest authentication with 401 Unauthorized challenge.
In this section:
This document assumes that you have already created a Signaling Group and a SIP Server table for the ITSP.
Verify that yourSBC Edge 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.
TheSBC Edge system must have the necessary licenses to make calls.
The configuration is comprised of three overall steps:
The call flow below depicts an outbound call from Lync to ITSP via Ribbon SBC 1000/2000.
The SBC Edge debug log produced at Trace level will show the information that is used to compute the MD5 string used in the Authorization header:
[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"