[asterisk-bugs] [JIRA] (ASTERISK-22096) chan_pjsip - when dialing an endpoint that is misconfigured, debug could be more helpful in regards to whether Asterisk found a matching AOR or not

[Rusty Newton (JIRA)]

Rusty Newton created ASTERISK-22096:
---------------------------------------

             Summary: chan_pjsip - when dialing an endpoint that is misconfigured, debug could be more helpful in regards to whether Asterisk found a matching AOR or not
                 Key: ASTERISK-22096
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22096
             Project: Asterisk
          Issue Type: Improvement
      Security Level: None
          Components: Channels/chan_gulp
    Affects Versions: SVN, 12
         Environment: Trunk
            Reporter: Rusty Newton
            Severity: Minor


{noformat}
[Jul  5 14:34:54] DEBUG[9021][C-00000000]: pbx.c:4649 pbx_extension_helper: Launching 'Dial'
    -- Executing [6001 at otherinternal:1] Dial("Gulp/6002-00000000", "GULP/6001") in new stack
[Jul  5 14:34:54] ERROR[9007]: chan_gulp.c:1536 request: Unable to create Gulp channel - endpoint '6001' was not found
[Jul  5 14:34:54] WARNING[9021][C-00000000]: app_dial.c:2420 dial_exec_full: Unable to create channel of type 'GULP' (cause 3 - No route to destination)
{noformat}

The above debug occurs when you have an endpoint and AOR configured correctly, *except* for the aors option on the endpoint. In this case I had "aor=" instead of "aors=".

We need debug to indicate that Asterisk is looking for an AOR associated with 6001 and that it wasn't found. Without knowledge of the source that is my understanding of what is happening from various conversations with devs.

It does currently point you to a problem with an endpoint and for someone like me that means I'll scrutinize the endpoint configuration letter by letter, but if there is a way we can have it point towards the issue with finer detail that is always better.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira