[asterisk-bugs] [JIRA] (ASTERISK-28233) pbx_dundi: PJSIP is not a supported technology
Joshua C. Colp (JIRA)
noreply at issues.asterisk.org
Thu Apr 13 03:58:03 CDT 2023
[ https://issues.asterisk.org/jira/browse/ASTERISK-28233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=261767#comment-261767 ]
Joshua C. Colp commented on ASTERISK-28233:
-------------------------------------------
An endpoint in PJSIP defines the configuration to use when initiating a call to a destination. I don't believe your usage is covered currently for PJSIP, because you're using the SIP one in a way it wasn't originally made for and kind of just happens to work based on how things work in chan_sip (passing SIP peer names in returned DUNDi dial strings). Further work would need to be done to cover your specific use case.
[~InterLinked] Will you be fixing the string issue above?
> 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