[asterisk-bugs] [JIRA] (ASTERISK-29111) res_pjsip_outbound_registration: Documentation for TCP/TLS transports.

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-29111:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].

> res_pjsip_outbound_registration: Documentation for TCP/TLS transports.
> ----------------------------------------------------------------------
>
>                 Key: ASTERISK-29111
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29111
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip_outbound_registration
>    Affects Versions: 16.13.0
>            Reporter: Alexander Traud
>            Severity: Minor
>
> The general documentation [states|https://wiki.asterisk.org/wiki/display/AST/Asterisk+16+Configuration_res_pjsip#Asterisk16Configuration_res_pjsip-endpoint_transport]:
> bq. Not specifying a transport will select the first configured transport in pjsip.conf which is compatible with the URI we are trying to contact.
> The specific documentation of registrations [states|https://wiki.asterisk.org/wiki/display/AST/Asterisk+16+Configuration_res_pjsip_outbound_registration#Asterisk16Configuration_res_pjsip_outbound_registration-registration_transport]:
> bq. A transport configured in pjsip.conf. As with other res_pjsip modules, this will use the first available transport of the appropriate type if unconfigured.
> The terms ‘appropriate’ and ‘compatible’ are not explained.
> I created (just) a TCP transport and a SIP registration. The registration did not specify the transport. This created the error:
> bq. Could not create an object of type 'registration' with id '…' from configuration file 'pjsip.conf'
> No additional information was printed what caused this error.
> The call stack is:
> sorcery_config_internal_load
> ⤷ ast_sorcery_objectset_apply
>   ⤷ sip_outbound_registration_apply
>     ⤷ sip_outbound_registration_regc_alloc
>       ⤷ sip_dialog_create_contact
> There, the state is:
> {code}
> selector = { type = PJSIP_TPSELECTOR_NONE, disable_connection_reuse = 0, u = {transport = 0x0, listener = 0x0, ptr = 0x0}}){code}
> which sets:
> {code}type = PJSIP_TRANSPORT_UNSPECIFIED{code}which then simply returns a {{-1}}. The current source code expects UDP and TLS transports only. This is not explained in the documentation. Currently, to use a TCP transport, that must be specified within a registration. Consequently, as a follow-up issue, the IP version gets fixed and the TCP client is not automatically dual-stack capable anymore.
> However, a similar issue exists with TLS transports: I have to use the URI scheme SIPs in the {{server_uri}} otherwise just UDP transports are matched. Again, this is not explained in the documentation. And if there is no UDP transport at all, the same error above, again without any further explanation is printed.
> Consequently:
> # The source code has to be updated to print a reason where/why it failed. I am a long-term contributor. To follow that call-stack five layers deeper compared to where the error message was created, took even me some time.
> # The documentation has to be updated to explain ‘appropriate’ and ‘compatible’.
> There is another issue: PJSIP supports DNS-NAPTR. That should be leveraged to select the transport (UDP, TCP, and TLS) automatically.



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