20 Aug
2018
20 Aug
'18
9:17 p.m.
On Mon, Aug 20, 2018 at 1:04 PM Alex Balashov <abalashov(a)evaristesys.com>
wrote:
On Mon, Aug 20, 2018 at 09:01:08PM +0300, Dmitri
Savolainen wrote:
in
This is fine, and you can make your outbound calls in that fashion. You do
need to have Asterisk present enough information that Kamailio is aware of
how to route that outbound INVITE request, but if you have sufficient
information in the request URI, it can certainly make that decision.
If, however, you wanted to dial PJSIP/1000 - which no other information and
where 1000 is some registered device - Asterisk will need the registered
contact that the device has presented to the registrar. In which case, you
have to have some mechanism for Asterisk to get at that information.
If Kamailio is going to act as your registrar, then you will need to
find some way to expose the registered contacts to Asterisk -
Matthew, could you explain why Asterisk have to know about reg contacts you approch? Asterisk just may sends all to
Kamailio (second call leg)
and let Kamailio route this call to appropriate contact.
The historical problem with this "dial endpoints over a trunk peer"
approach is that such endpoints are not as privileged by Asterisk as
local AstDB bindings for various Class 5 / application purposes, e.g.
hints, voicemail, MWI, etc.
But as I understand it, PJSIP is supposed to fix this problem and make
use of an outboard registrar a lot more transparent.
Yup - it all depends on how you configure / use things.
--
Matthew Jordan
Digium, Inc. | CTO
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: http://digium.com & http://asterisk.org