[asterisk-bugs] [JIRA] (ASTERISK-22379) Strange dialplan lookups happening when dial()ing sip peers

[Rusty Newton (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-22379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210093#comment-210093 ] 

Rusty Newton commented on ASTERISK-22379:
-----------------------------------------

Mark Michelson and I both looked into the debug and configs so far. It is not clear to us how the call to SIP/digidev&SIP/digidevs is triggering the dialplan execution at their assigned contexts.

1. Did this start after an update to your trunk version? Do you know when it was previously working different?

bq. The question is why something tries to use the dialplan at all.

Yes this is what we would like to find out.

2. Please provide steps for reproduction so that we can easily reproduce the behavior. I think that is easiest if you minimize your configuration to only what is needed to reproduce the issue. Often in doing that for other issues I find that seemingly unrelated aspects of configuration are sometimes related. 

Thanks!
                
> Strange dialplan lookups happening when dial()ing sip peers
> -----------------------------------------------------------
>
>                 Key: ASTERISK-22379
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22379
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: SVN
>            Reporter: Birger "WIMPy" Harzenetter
>            Assignee: Birger "WIMPy" Harzenetter
>            Severity: Minor
>         Attachments: astdebug, dial-contexts.txt, sip-conf-info
>
>
> I'm experiencing very noticeable delays on delivering calls do to an unexplained dialplan lookup. This probably wouldn't be any issue at all if it wouldn't happen in a context that contains loopback switches to a dundi switch that, off course, takes some time to fail.

--
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