[asterisk-dev] res_pjsip: sending to arbitrary URI

Matthew Jordan mjordan at digium.com
Fri Nov 22 13:28:06 CST 2013


On Fri, Nov 22, 2013 at 11:45 AM, Kevin Harwell <kharwell at digium.com> wrote:

> On Tue, 2013-11-12 at 11:38 -0600, Kevin Harwell wrote:
>
>
<snip>


> > 1) Use a specially-named endpoint (maybe called "default_outbound").
> > This endpoint can be automatically created when res_pjsip is loaded and
> > contain nothing but the default values for the endpoint. If people want
> > to tweak default behavior, then they can create an endpoint called
> > "default_outbound" in their pjsip.conf file and set appropriate values
> > on it. This approach has the advantage of "just working" out of the box
> > and allowing for overriding of the default behavior if desired.
> > 2) Create a new option for PJSIP global configuration (maybe called
> > "default_outbound_endpoint") that indicates an endpoint to be used when
> > sending an outbound request to a URI. This approach has the advantage of
> > not creating any "secret" endpoints that the user did not explicitly
> > place in the configuration file.
> >
> > I kind of like #2 as there is nothing hidden and it allows the end user
> > to name the default outbound endpoint.  Thoughts? Other ideas?
> >
> > Thanks,
> >
>
> I am planning on moving forward with #2 soonish unless I hear of some
> major reason why not to.
>
>
I'd say my vote is for #2. That way it is still up to the user to define
the endpoint characteristics they want when sending to an arbitrary SIP
URI, and they simply say in the global system config which characteristics
should apply to that scenario.

That also alleviates users from having to specify said 'endpoint' when
dialing an arbitrary SIP URI, which is very nice.

-- 
Matthew Jordan
Digium, Inc. | Engineering Manager
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: http://digium.com & http://asterisk.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20131122/10746228/attachment.html>


More information about the asterisk-dev mailing list