From a2aa8bf438440d89c04ad89f45353bfd7f3c5ac0 Mon Sep 17 00:00:00 2001 From: Mark Michelson Date: Thu, 5 Sep 2013 14:09:48 +0000 Subject: [PATCH] Clarify server_uri and client_uri registration settings. Used some of Rusty's suggested language plus also included more SIPesque descriptions of where the URIs are actually used in an outgoing REGISTER. (closes issue ASTERISK-22390) reported by Rusty Newton git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/12@398368 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- res/res_pjsip_outbound_registration.c | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/res/res_pjsip_outbound_registration.c b/res/res_pjsip_outbound_registration.c index be72081b4c..9c3ae1fcea 100644 --- a/res/res_pjsip_outbound_registration.c +++ b/res/res_pjsip_outbound_registration.c @@ -57,6 +57,15 @@ Client SIP URI used when attemping outbound registration + + This is the address-of-record for the outbound registration (i.e. the URI in + the To header of the REGISTER). + For registration with an ITSP, the client SIP URI may need to consist of + an account name or number and the provider's hostname for their registrar, e.g. + client_uri=1234567890@example.com. This may differ between providers. + For registration to generic registrars, the client SIP URI will depend + on networking specifics and configuration of the registrar. + Contact User to use in request @@ -78,6 +87,12 @@ SIP URI of the server to register against + + This is the URI at which to find the registrar to send the outbound REGISTER. This URI + is used as the request URI of the outbound REGISTER request from Asterisk. + For registration with an ITSP, the setting may often be just the domain of + the registrar, e.g. sip:sip.example.com. + Transport used for outbound authentication -- 2.47.2