[asterisk-bugs] [JIRA] (ASTERISK-22390) client_uri and server_uri config documentation lacks useful detail

[Rusty Newton (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-22390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rusty Newton updated ASTERISK-22390:
------------------------------------

    Description: 
{noformat}
                                <configOption name="client_uri">
                                        <synopsis>Client SIP URI used when attemping outbound registration</synopsis>
                                </configOption>

{noformat}

*Proposed change for synopsis:*

"A SIP URI to be used in both the From and To headers for our outbound registration attempts."

*Add a description:*

"For registration with an ITSP, the Client SIP URI may need to consist of your account name or number and the providers hostname for their registrar. e.g. client_uri=1234567890 at example.com. This will often differ between providers. 

For registration against any server in general; what value you need to set will be determined by networking specifics and the configuration of the remote server." 


{noformat}
                                <configOption name="server_uri">
                                        <synopsis>SIP URI of the server to register against</synopsis>
                                </configOption>
{noformat}

*Proposed change for synopsis:*

"A SIP URI to be used for the Request-URI in our outbound registration attempts."

*Add a description:*

"The info in this SIP URI will pertain to the server you are registering against. What exactly is needed in the URI will be determined by networking specifics and the remote servers configuration.

For registration with an ITSP, the setting may often be just the domain of the registrar. e.g. sip.example.com"


* I may not be considering some advanced scenarios.
* I'm not a source dev, so I need someone to verify accuracy. This text comes from my limited use of these settings so far.

  was:
{noformat}
                                <configOption name="client_uri">
                                        <synopsis>Client SIP URI used when attemping outbound registration</synopsis>
                                </configOption>

{noformat}

*Proposed change for synopsis:*

"A SIP URI to be used in both the From and To headers for our outbound registration attempts."

*Add a description:*

"For registration with an ITSP, the Client SIP URI may need to consist of your account name or number and the providers hostname for their registrar. e.g. client_uri=1234567890 at example.com. This can differ between providers. 

For registration against any server in general; what value you need to set will be determined by networking specifics and the configuration of the remote server." 


{noformat}
                                <configOption name="server_uri">
                                        <synopsis>SIP URI of the server to register against</synopsis>
                                </configOption>
{noformat}

*Proposed change for synopsis:*

"A SIP URI to be used for the Request-URI in our outbound registration attempts."

*Add a description:*

"The info in this SIP URI will pertain to the server you are registering against. What exactly is needed in the URI will be determined by networking specifics and the remote servers configuration.

For registration with an ITSP, the setting may often be just the domain of the registrar. e.g. sip.example.com"


* I may not be considering some advanced scenarios.
* I'm not a source dev, so I need someone to verify accuracy. This text comes from my limited use of these settings so far.

    
> client_uri and server_uri config documentation lacks useful detail
> ------------------------------------------------------------------
>
>                 Key: ASTERISK-22390
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22390
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Resources/res_pjsip_outbound_registration
>    Affects Versions: SVN, 12
>         Environment: SVN-branch-12-r397614M
>            Reporter: Rusty Newton
>            Severity: Minor
>
> {noformat}
>                                 <configOption name="client_uri">
>                                         <synopsis>Client SIP URI used when attemping outbound registration</synopsis>
>                                 </configOption>
> {noformat}
> *Proposed change for synopsis:*
> "A SIP URI to be used in both the From and To headers for our outbound registration attempts."
> *Add a description:*
> "For registration with an ITSP, the Client SIP URI may need to consist of your account name or number and the providers hostname for their registrar. e.g. client_uri=1234567890 at example.com. This will often differ between providers. 
> For registration against any server in general; what value you need to set will be determined by networking specifics and the configuration of the remote server." 
> {noformat}
>                                 <configOption name="server_uri">
>                                         <synopsis>SIP URI of the server to register against</synopsis>
>                                 </configOption>
> {noformat}
> *Proposed change for synopsis:*
> "A SIP URI to be used for the Request-URI in our outbound registration attempts."
> *Add a description:*
> "The info in this SIP URI will pertain to the server you are registering against. What exactly is needed in the URI will be determined by networking specifics and the remote servers configuration.
> For registration with an ITSP, the setting may often be just the domain of the registrar. e.g. sip.example.com"
> * I may not be considering some advanced scenarios.
> * I'm not a source dev, so I need someone to verify accuracy. This text comes from my limited use of these settings so far.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira