Outbound Failed issue

[medalibarhoumi]

Hello,
So i try to configure my asterisk to connect with cube (cisco Gateway) to allow making external calls,
I have a problem with outgoing calls using a pjsip trunk while incoming calls are working correctly.
Incoming and outgoing authentication are well configured but on an outgoing call I get the following error message.
“ERROR[452122]: res_pjsip_outbound_authenticator_digest.c:450 digest_create_request_with_auth: Endpoint: ‘cube’: There was no authentication ids available”

[david551]

Did you forget to include your configuration?

[medalibarhoumi]

I already include the cube file .conf in the pjsip.conf like that
#include pjsip/trunks/cube.conf
and i still try until now

[ashleymike]

The error message you’re encountering in Asterisk indicates that there’s an issue with the authentication configuration for outgoing calls via the PJSIP trunk. Specifically, it’s stating that there were no authentication IDs available when creating a request.

Here are some steps you can take to troubleshoot and potentially resolve this issue:

1. Verify Outgoing Authentication Configuration:

• Double-check the configuration of the PJSIP trunk for outgoing calls in your pjsip.conf or related configuration files.
• Ensure that the authentication credentials (username, password, realm, etc.) are correctly set for the outgoing section of the trunk.

2. Ensure Correct Endpoint Configuration:

• Verify that the endpoint configuration for the outbound trunk (e.g., cube) includes the correct information, especially the auth parameter, which should reference the authentication configuration.

3. Check Authentication Section:

• In your PJSIP configuration, check for the section where you define the authentication credentials for the cube endpoint.
• Ensure that you have set the correct type and username for the authentication.

4. Recheck for Typos and Case Sensitivity:

• Ensure that there are no typos in your configuration files, and pay attention to case sensitivity.
• For example, make sure that the endpoint name (cube) is consistently referenced with the correct case throughout your configuration.

5. Review Asterisk Logs:

• Examine the Asterisk logs (/var/log/asterisk/full or a similar path) for additional details on the error.
• The logs might provide more insight into the specific point of failure or any additional issues with the authentication process.

6. Packet Capture (Wireshark):

• Use a packet capture tool like Wireshark to capture the SIP traffic between Asterisk and the Cisco Gateway.
• Analyze the SIP messages to see if there are any clues about why the authentication IDs might not be available.

7. Update Asterisk and PJSIP:

• Ensure that you are using a reasonably recent version of Asterisk and the PJSIP module.
• Consider updating to the latest versions if you are not already using them, as newer releases may include bug fixes and improvements.

8. Check Cisco Gateway Configuration:

• Review the configuration on the Cisco Gateway (Cube) to ensure that it is expecting and configured to accept SIP traffic from your Asterisk server.

After making adjustments based on these steps, restart Asterisk to apply the changes. If the issue persists, carefully review your configuration files, focusing on the authentication setup for outgoing calls. Additionally, consult the Asterisk documentation and community forums for any specific considerations related to your Asterisk version and the PJSIP module.