[asterisk-bugs] [JIRA] (ASTERISK-28233) pbx_dundi: PJSIP is not a supported technology

Michael Newton (JIRA) noreply at issues.asterisk.org
Wed Apr 12 18:13:03 CDT 2023


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

Michael Newton commented on ASTERISK-28233:
-------------------------------------------

Looking over the recent commits, I am having trouble understanding how a single fixed endpoint is in any way useful? The idea of dundi is to send out a request to many peers, any of which might respond with an offer to complete the call. Am I misunderstanding what an "endpoint" is in pjsip terminology?

In our network, we have incoming calls from our PSTN carrier sent to a single server. That server does a dundi query of 100 hosted PBXs, one of which responds with, e.g. "SIP/12345678 at foobar_pbx" where "foobar_pbx" is configured as a dundi peer and a SIP peer with an IP address on the local network. How could this be replicated with this patch using a single fixed endpoint?

Also I am not a C programmer, but are both these things meant to be checking for an empty string? There are two opposite uses of {{ast_strlen_zero}} here.

{noformat}
if (!ast_strlen_zero(pjsip_outgoing_endpoint)) {
	ast_log(LOG_WARNING, "PJSIP calls require an endpoint to be specified explicitly (use the pjsip_outgoing_endpoint option in dundi.conf)\n");
	return -1;
}
/* Take IP/number and turn it into sip:number at IP */
if (ast_strlen_zero(ip)) {
	ast_log(LOG_WARNING, "PJSIP destination is empty?\n");
	return -1;
}
{noformat}

> pbx_dundi: PJSIP is not a supported technology
> ----------------------------------------------
>
>                 Key: ASTERISK-28233
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28233
>             Project: Asterisk
>          Issue Type: New Feature
>      Security Level: None
>          Components: PBX/pbx_dundi
>    Affects Versions: 15.3.0
>            Reporter: Kirsty Tyerman
>            Assignee: Kirsty Tyerman
>              Labels: pjsip
>
> PJSIP is not supported as a technology for a DUNDILOOKUP, it is reported as UNKNOWN.
> I want to configure "dundi.conf" with a mapping that uses PJSIP.
> {noformat}
> [mappings]
> test => test,0,PJSIP,${NUMBER}@192.168.1.1,nopartial
> {noformat}
> When I query the mappings on the CLI it displays as an unknown technology.
> {noformat}
> *CLI> dundi show mappings
> DUNDi Cntxt  Weight  Local Cntxt  Options    Tech  Destination              
> test         0       test         NONE       Unkno ${NUMBER}@192.168.1.1
> {noformat}
> PJSIP should be a valid technology and should be able to be called via a returned DUNDILOOKUP.



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list