How Can We Help?

Authentication to the carrier failed

Description of the problem:
When using a VoIP operator (carrier) who authenticates through registration credentials (username and password), the UCloud server behaves like a SIP client, sending REGISTER packets to the operator:

REGISTER sip: SIP / 2.0
Via: SIP / 2.0 / UDP;rport;branch=z9hG4bK147B044C2
From: <sip:>; tag = 73EB1459
To: <sip:>
Expires: 60

The provider usually refuses the first registration with a 401 or 407, “challenging” the client (UCloud) to repeat the request by authenticating, using a different nonce key each time:

SIP / 2.0 401 Unauthorized
WWW-Authenticate: Digest realm = “”, nonce = “WbJX11my”
Server: SIP Proxy
Content-Length: 0

Received the temporary rejection, the client (UCloud) sends a new REGISTER with the response field calculated with the as soon as received, the realm, username and password fields saved in the VoIP gateway configuration.

REGISTER sip: SIP / 2.0
Via: SIP / 2.0 / UDP;rport;branch=z9hG4bKF530AB52
From: <sip:>; tag = 73EB1459
Authorization: Digest uri = “sip:”, username = “0234567890 ″, realm =” “, nonce =” WbJX11my “, response =” 78b39157fab32d14e3cf4ce4a0bdb383 ″
Expires: 60

Possible causes:
In the event that there is a discrepancy in one or more of the 3 parameters set on the PBX configurator (username, password or realm) compared to those used by the provider, the response field will be calculated incorrectly and the request will be rejected by the provider with a negative 4xx response, usually 401, 403, 404 or 407.

Possible solutions:

  1. Check that the username entered in the “User ID Authentication” field is correct
  2. Check that the “Realm” entered in the configuration coincides with the one that the provider provides in the 401 or 407 response
  3. Re-enter the password provided by the provider