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

[Michael Newton (JIRA)]

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

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

BTW my thinking on endpoints is somewhat different, but that may be based on my use of dundi. We use it internally to route incoming calls to one of many PBXs, so having a single endpoint specified by a `use_endpoint` directive would not be helpful. The dundi response includes the PBX name or IP address, and that should be used. A better solution in my mind would be to have a `default_endpoint` directive in the config file. If the name/IP address provided by the peer can be mapped to a known endpoint, then it should be given priority but fall back to the default otherwise. So I would modify Rhys' list to look like this:


 *   User doing the lookup adds "default_endpoint=SIP-SYD-01" to the DUNDi peer
 *   A user does a lookup against a peer for the number "61299998888"
 *   A DUNDi peer is advertising a mapping returns a dial string similar to: SIP/100.1.1.1/61299998888
 *   Nothing changes on the DUNDi peer advertising it's mapping, but on the lookup side we take the response "SIP/100.1.1.1/61299998888" and extract the number from the end.
 *   The lookup side then transparently converts the dial string before returning it, to: PJSIP/61299998888 at 100.1.1.1
 *   The side doing the lookup now has a dial string that contains the PJSIP endpoint they specified and can use this to dial out without any messing around with the lookup result, or coordinating with the DUNDi peer on the other side.
 *   If the dial string cannot be resolved, use the "default_endpoint" value to try a different endpoint: PJSIP/61299998888 at SIP-SYD-01
 *   Probably modify dundi lookup command output to show the returned string both before and after translation, if "use_endpoint" is configured, to help with debugging.


Maybe a mix of both approaches would be most flexible, so having a `force_endpoint` that's always used (if desired) or a `default_endpoint` that's a fallback.

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