<div dir="ltr">So, I can use Kamailio as SBC/Load balancer/registrar, Asterisk as IVR and application server, and rtpproxy as media relay and recorder ?<br></div><div class="gmail_extra"><br><div class="gmail_quote">2017-03-14 7:44 GMT+01:00 Alex Balashov <span dir="ltr"><<a href="mailto:abalashov@evaristesys.com" target="_blank">abalashov@evaristesys.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">It can record, as can a number of other media relays.<br>
<div class="HOEnZb"><div class="h5"><br>
On March 14, 2017 2:43:15 AM EDT, przeqpiciel <<a href="mailto:przeqpiciel@gmail.com">przeqpiciel@gmail.com</a>> wrote:<br>
>>> WHy not installing rtpproxy and proxying all<br>
>Because I would like to record some calls and I dont know RTPProxy's<br>
>features, maybe it could record ?<br>
><br>
>2017-03-14 5:14 GMT+01:00 anfecora <<a href="mailto:anfecora@gmail.com">anfecora@gmail.com</a>>:<br>
><br>
>> WHy not installing rtpproxy and proxying all rtp to the inside uase<br>
>> kamailio to load balance them, it will be transparent on the inside<br>
>perhaps<br>
>> a cleaner solution?<br>
>><br>
>> On Mon, Mar 13, 2017 at 3:21 PM, Kjeld Flarup <<a href="mailto:kfc@viptel.dk">kfc@viptel.dk</a>> wrote:<br>
>><br>
>>> As I recall it is sequential, but not from the start everytime, it<br>
>is<br>
>>> incrementing all the time.<br>
>>><br>
>>> If You are running three servers, then with a 100% identical load,<br>
>one<br>
>>> would expect an average of 2 failing attempts per call.<br>
>>><br>
>>> The reality I see is however often very different RTP ports, most<br>
>likely<br>
>>> because load isn't 100% identical.<br>
>>><br>
>>><br>
>>> Med venlig hilsen / Best regards<br>
>>> Kjeld Flarup (Christensen) M.Sc E.E, Teknisk chef<br>
>>> Viptel ApS, Hammershusvej 16C, DK-7400 Herning<br>
>>> Telefon: <a href="tel:%2B45%2046949949" value="+4546949949">+45 46949949</a>, Telefax: <a href="tel:%2B45%2046949950" value="+4546949950">+45 46949950</a>, <a href="http://viptel.dk" rel="noreferrer" target="_blank">http://viptel.dk</a><br>
>>><br>
>>> On 03/13/2017 11:05 PM, Alex Balashov wrote:<br>
>>><br>
>>>> Well, indeed, but a sequential scan of many consecutive ports like<br>
>this<br>
>>>> from the bottom of the same range can be quite a latent operation.<br>
>So at<br>
>>>> the very least the allocation strategy would benefit from being<br>
>random.<br>
>>>> Does Asterisk take that approach?<br>
>>>><br>
>>>> On March 13, 2017 6:04:06 PM EDT, Kjeld Flarup <<a href="mailto:kfc@viptel.dk">kfc@viptel.dk</a>><br>
>wrote:<br>
>>>><br>
>>>>> No there is no such thing as magic.<br>
>>>>><br>
>>>>> The most obvious way to implement the RTP port handling, is to<br>
>first<br>
>>>>> open the next UDP port in the OS, and then report that back in the<br>
>>>>> Invite/200Ok. If the port cannot be opened, then simply try the<br>
>next in<br>
>>>>><br>
>>>>> line.<br>
>>>>><br>
>>>>><br>
>>>>> Med venlig hilsen / Best regards<br>
>>>>> Kjeld Flarup (Christensen) M.Sc E.E, Teknisk chef<br>
>>>>> Viptel ApS, Hammershusvej 16C, DK-7400 Herning<br>
>>>>> Telefon: <a href="tel:%2B45%2046949949" value="+4546949949">+45 46949949</a>, Telefax: <a href="tel:%2B45%2046949950" value="+4546949950">+45 46949950</a>, <a href="http://viptel.dk" rel="noreferrer" target="_blank">http://viptel.dk</a><br>
>>>>><br>
>>>>> On 03/13/2017 01:52 PM, przeqpiciel wrote:<br>
>>>>><br>
>>>>>> Maybe there is an magic device? I know that if we have an<br>
>asterisk,<br>
>>>>>> that become to us with default configuration of rtp ports sets to<br>
>>>>>> 10000_20000. And each call choose the one port fron that range.<br>
>So if<br>
>>>>>> we have several asterisks with default configuratiin of rtp,<br>
>there is<br>
>>>>>> possibilities to have 2 concurent calls each through another<br>
>asterisk<br>
>>>>>> instance with this same rtp port. Am i right?<br>
>>>>>><br>
>>>>>> So mqybe this magic device could see source IP address and route<br>
>rtp<br>
>>>>>> to correct adterisk?<br>
>>>>>><br>
>>>>>> <a href="tel:13.03.2017%207" value="+48130320177">13.03.2017 7</a>:15 AM "Alex Balashov" <<a href="mailto:abalashov@evaristesys.com">abalashov@evaristesys.com</a><br>
>>>>>> <mailto:<a href="mailto:abalashov@evaristesys.com">abalashov@evaristesys.<wbr>com</a>>> napisał(a):<br>
>>>>>><br>
>>>>>> On Mon, Mar 13, 2017 at 07:08:09AM +0100, Kjeld Flarup<br>
>wrote:<br>
>>>>>><br>
>>>>>> > We run multiple Asterisk instances since 1.4 and never<br>
>>>>>> configured RTP ports.<br>
>>>>>> ><br>
>>>>>> > More challenging issues are the Asterisk DB, and the<br>
>Asteisk<br>
>>>>>><br>
>>>>> home.<br>
>>>>><br>
>>>>>> You may not have enough calls for RTP port collisions to<br>
>become<br>
>>>>>><br>
>>>>> an<br>
>>>>><br>
>>>>>> issue. Otherwise, I'm not sure how you're avoiding it, since<br>
>>>>>><br>
>>>>> Asterisk<br>
>>>>><br>
>>>>>> isn't aware of which ports from within the range are in use.<br>
>>>>>><br>
>>>>>> --<br>
>>>>>> Alex Balashov | Principal | Evariste Systems LLC<br>
>>>>>><br>
>>>>>> Tel: <a href="tel:%2B1-706-510-6800" value="+17065106800">+1-706-510-6800</a> <tel:%2B1-706-510-6800> /<br>
>+1-800-250-5920<br>
>>>>>> <tel:%2B1-800-250-5920> (toll-free)<br>
>>>>>> Web: <a href="http://www.evaristesys.com/" rel="noreferrer" target="_blank">http://www.evaristesys.com/</a>, <a href="http://www.csrpswitch.com/" rel="noreferrer" target="_blank">http://www.csrpswitch.com/</a><br>
>>>>>><br>
>>>>>> ______________________________<wbr>_________________<br>
>>>>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users<br>
>>>>>><br>
>>>>> mailing<br>
>>>>><br>
>>>>>> list<br>
>>>>>> <a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
>>>>>><br>
>>>>> <mailto:<a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-<wbr>router.org</a>><br>
>>>>><br>
>>>>>><br>
><a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">http://lists.sip-router.org/<wbr>cgi-bin/mailman/listinfo/sr-<wbr>users</a><br>
>>>>>><br>
><<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">http://lists.sip-router.org/<wbr>cgi-bin/mailman/listinfo/sr-<wbr>users</a>><br>
>>>>>><br>
>>>>>><br>
>>>>>><br>
>>>>>> ______________________________<wbr>_________________<br>
>>>>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users<br>
>mailing<br>
>>>>>><br>
>>>>> list<br>
>>>>><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" rel="noreferrer" target="_blank">http://lists.sip-router.org/<wbr>cgi-bin/mailman/listinfo/sr-<wbr>users</a><br>
>>>>>><br>
>>>>><br>
>>>> -- Alex<br>
>>>><br>
>>>> --<br>
>>>> Principal, Evariste Systems LLC (<a href="http://www.evaristesys.com" rel="noreferrer" target="_blank">www.evaristesys.com</a>)<br>
>>>><br>
>>>> Sent from my Google Nexus.<br>
>>>><br>
>>>> ______________________________<wbr>_________________<br>
>>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing<br>
>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" rel="noreferrer" target="_blank">http://lists.sip-router.org/<wbr>cgi-bin/mailman/listinfo/sr-<wbr>users</a><br>
>>>><br>
>>><br>
>>><br>
>>> ______________________________<wbr>_________________<br>
>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing<br>
>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" rel="noreferrer" target="_blank">http://lists.sip-router.org/<wbr>cgi-bin/mailman/listinfo/sr-<wbr>users</a><br>
>>><br>
>><br>
>><br>
>> ______________________________<wbr>_________________<br>
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing<br>
>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" rel="noreferrer" target="_blank">http://lists.sip-router.org/<wbr>cgi-bin/mailman/listinfo/sr-<wbr>users</a><br>
>><br>
>><br>
<br>
<br>
-- Alex<br>
<br>
--<br>
Principal, Evariste Systems LLC (<a href="http://www.evaristesys.com" rel="noreferrer" target="_blank">www.evaristesys.com</a>)<br>
<br>
Sent from my Google Nexus.<br>
<br>
______________________________<wbr>_________________<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" rel="noreferrer" target="_blank">http://lists.sip-router.org/<wbr>cgi-bin/mailman/listinfo/sr-<wbr>users</a><br>
</div></div></blockquote></div><br></div>