[asterisk-bugs] [JIRA] (ASTERISK-28386) res_pjsip does not follow DNS SRV priority values

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-28386:
------------------------------------------

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

> res_pjsip does not follow DNS SRV priority values
> -------------------------------------------------
>
>                 Key: ASTERISK-28386
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28386
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 13.25.0, 13.26.0, 16.3.0
>         Environment: Sangoma Linux release 7.5.1805 (Core)
>            Reporter: Andy Chi
>            Assignee: Andy Chi
>              Labels: pjsip
>
> Using a provider that supports DNS SRV with the following output:
> _sip._udp.testing.st.sip.global. 299 IN   SRV     20 100 6000 dllstx37-access-sbc2.sip.global.
> _sip._udp.testing.st.sip.global. 299 IN   SRV     10 100 6000 plmomn-access-sbc2.sip.global.
> My expectation would be for registration and calls to always use the priority 10 server, however when running a simple channel originate script, I see calls round robin between the two entries.



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