<div dir="ltr">On 1 May 2013 02:14, Aldo Antignano <span dir="ltr"><<a href="mailto:aldo@antignano.it" target="_blank">aldo@antignano.it</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
>> In the REGFWD route you send all the registrations to ALL the Asterisks?<br>
>> If so, why?<br>
<br>
> By sending the registration to all the available Asterisk servers then they<br>
> all know where each SIP client can be located. If a call comes in from the<br>
> PSTN or from a SIP client Kamailio can just be sent it to any of the *<br>
> servers and it will find the registered client. This will work even with<br>
> multiple load balancers/dispatchers using DNS SRV.<br>
<br>
In this way should be an option to keep registration in Kamailio only,<br>
let Asterisk do its specific job, and configure Asterisk to accept all calls<br>
coming from Kamailio as authorized calls by its IP?<br>
<br></blockquote><div><br></div><div style>Yes, that would be as simple as commenting out the route(REGFWD) on Kamailio and putting a peer entry in Asterisk sip.conf for the Kamailio server. However, this then requires that Asterisk be set up to send any calls not known locally to your single Kamailio IP address, which also makes it more difficult to have multiple kamailio as Asterisk will need to know on which kamailio instance a particular client is registered. You could probably do this in Asterisk by querying the kamailio location table but things get needlessly complicated then.</div>
<div style><br></div><div style>If Asterisk is simply functioning as a PSTN gateway this would be fine. In this case you probably want to use the WITH_PSTN rather than WITH_ASTERISK setting in kamailio.cfg. </div><div style>
<br></div><div style><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
> In this scenario Kamailio is mainly acting as a load balancer, topology<br>
> hider and security/anti-flood front-end to create a scalable and redundant<br>
> Asterisk PBX system. Really depends what you are after.<br>
<br>
These are exactly my goals and was trying to understand which is the best way to achieve this.<br>
Any suggestion is welcome, thanks.<br>
<br></blockquote><div><br></div><div><br></div><div><div>As I said, my aim was using Asterisk as a PBX (supporting call queues, BLF, Device State etc) so I needed the clients registered to Asterisk. Total registrations for my use case would not exceed 1,000 so having the registers sent to all asterisk servers made sense. For a large scale system I would keep registrations off Asterisk completely.</div>
</div><div><br></div><div style>Regards,</div><div style><br></div><div style>-Barry Flanagan</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Anty<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Tue, 30 Apr 2013 23:02:20 +0100<br>
From: Barry Flanagan <<a href="mailto:barry@flanagan.ie">barry@flanagan.ie</a>><br>
To: "Kamailio (SER) - Users Mailing List"<br>
<<a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a>><br>
Subject: Re: [SR-Users] Kamailio 3.x and Asterisk Realtime Integration<br>
plus<br>
Message-ID:<br>
<<a href="mailto:CALJb54_1FGmGV4HfmR1zHgcAGqMsSPu6kriTv72W3adyHF3dQw@mail.gmail.com">CALJb54_1FGmGV4HfmR1zHgcAGqMsSPu6kriTv72W3adyHF3dQw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
<br>
<br>
<br>
> _______________________________________________<br>
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
> <a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
> <a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.sip-router.org/pipermail/sr-users/attachments/20130430/95b9dbb4/attachment.html" target="_blank">http://lists.sip-router.org/pipermail/sr-users/attachments/20130430/95b9dbb4/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
sr-users mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<br>
<br>
End of sr-users Digest, Vol 96, Issue 1<br>
***************************************<br>
<br>
<br>
<br>
_______________________________________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
</blockquote></div><br></div></div>