Hi again, <div><br></div><div>I've talked to my provider and they require that media and signalling come from my servers vpn-interface ip address. (Not the eaddress). Can I set the media IP address to the extra_socket IP instead of the eaddress IP somehow? (As happens with signalling)</div>
<div><br></div><div>Thanks in advanced.</div><div><br></div><div>--<div><div>Joel Smith</div><div><div><div><div>Cell: +34 639 03 13 53</div><div>E-Mail: <a href="mailto:joel@vozelia.com" target="_blank">joel@vozelia.com</a></div>
<div><a href="mailto:joel@vozelia.com" target="_blank"></a><br><div><a href="http://www.vozelia.com" target="_blank"><img src="http://images.joelserrano.com/social/vozelia.gif" width="96" height="27"></a> <a href="http://twitter.com/vozelia" target="_blank"><img src="http://images.joelserrano.com/social/twitter.png"></a> <a href="http://www.facebook.com/pages/Vozelia-Operador-de-telefonia-IP-para-empresas/165574849908?v=info" target="_blank"><img src="http://images.joelserrano.com/social/facebook.png"></a> </div>
</div></div></div></div></div><br>
<br><br><div class="gmail_quote">On Thu, Nov 8, 2012 at 11:05 PM, Joel Smith | VOZELIA <span dir="ltr"><<a href="mailto:joel@vozelia.com" target="_blank">joel@vozelia.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Ok, that explains everything!<div><br></div><div>Can I set the media IP address to the extra_socket IP instead of the eaddress IP? My provider does in deed require the media and signalling to be the same IP.</div><div><br>
</div><div>Regards, <br clear="all">--<div><div>Joel Smith</div><div><div><div><div class="im"><div>Cell: <a href="tel:%2B34%20639%2003%2013%2053" value="+34639031353" target="_blank">+34 639 03 13 53</a></div><div>E-Mail: <a href="mailto:joel@vozelia.com" target="_blank">joel@vozelia.com</a></div>
</div><div><a href="mailto:joel@vozelia.com" target="_blank"></a><br>
<div><a href="http://www.vozelia.com" target="_blank"><img src="http://images.joelserrano.com/social/vozelia.gif" width="96" height="27"></a> <a href="http://twitter.com/vozelia" target="_blank"><img src="http://images.joelserrano.com/social/twitter.png"></a> <a href="http://www.facebook.com/pages/Vozelia-Operador-de-telefonia-IP-para-empresas/165574849908?v=info" target="_blank"><img src="http://images.joelserrano.com/social/facebook.png"></a> </div>
</div></div></div></div></div><div><div class="h5"><br>
<br><br><div class="gmail_quote">On Thu, Nov 8, 2012 at 8:20 PM, Andreas Granig <span dir="ltr"><<a href="mailto:agranig@sipwise.com" target="_blank">agranig@sipwise.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Joel,<br>
<br>
Probably your provider requires to receive the audio from the same IP<br>
as the signalling? The signalling (especially the extra_socket option)<br>
doesn't influence the media flow beside the fact that at your provider1,<br>
the SIP message is received from the external_socket IP, whereas the<br>
media is received from the eaddress IP.<br>
<span><font color="#888888"><br>
Andreas<br>
</font></span><div><div><br>
On 11/08/2012 07:04 PM, Joel Smith | VOZELIA wrote:<br>
> Hi,<br>
><br>
> I've done a little further testing...<br>
><br>
><br>
> Scenario A (2 IPs):<br>
><br>
> [Softphone] <-> [provider1] <-vpn-> [my sip:provider ce] <-> [pstn]<br>
><br>
> extra_socket is the vpn interface (eth1)<br>
> eaddress is the other (outside) interface (eth3)<br>
><br>
> --> NO audio at all.<br>
><br>
><br>
> Scenario B (2 IPs):<br>
><br>
> [Softphone] <-> [provider1] <-vpn-> [my sip:provider ce] <-> [pstn]<br>
><br>
> eaddress is the vpn interface (eth1)<br>
> extra_socket is the other (outside) interface (eth3)<br>
><br>
> --> NO audio at all.<br>
><br>
><br>
> Scenario C (2 IPs):<br>
><br>
> [Softphone] <-> [provider1] <-vpn-> [my sip:provider ce] <-> [pstn]<br>
><br>
> eaddress is the vpn interface (eth1)<br>
> extra_socket is the other (outside) interface (eth3)<br>
> in the pstn-peer settings the "vpn_udp" extra socket is selected.<br>
><br>
> --> One-way audio.<br>
><br>
><br>
> Scenario D (1 IP):<br>
><br>
> [Softphone] <-> [provider1] <-vpn-> [my sip:provider ce] <-vpn-> [pstn]<br>
><br>
> eaddress is the vpn interface (eth1)<br>
> no extra_socket is configured.<br>
><br>
> --> Audio works perfect.<br>
><br>
><br>
> My desired scenario is A, but I need to handle the call correctly and<br>
> obviously I'm not. The problem is that calls always enter the<br>
> sipwise-server from vpn-interface and then leave the sipwise-server<br>
> through the outside-interface.<br>
><br>
> Thank you in advanced.<br>
><br>
><br>
> Best regards,<br>
> --<br>
> Joel Smith<br>
> Cell: <a href="tel:%2B34%20639%2003%2013%2053" value="+34639031353" target="_blank">+34 639 03 13 53</a><br>
> E-Mail: <a href="mailto:joel@vozelia.com" target="_blank">joel@vozelia.com</a><br>
><br>
><br>
><br>
><br>
> On Thu, Nov 8, 2012 at 5:16 PM, Joel Smith | VOZELIA <<a href="mailto:joel@vozelia.com" target="_blank">joel@vozelia.com</a>> wrote:<br>
>> Hi Andrew<br>
>><br>
>> I've deleted the customtt file and added the extra_socket.<br>
>><br>
>> My config.yml has this:<br>
>><br>
>> [...]<br>
>> eaddress: 37.139.120.59<br>
>> iaddress: 127.0.0.1<br>
>> [...]<br>
>> extra_sockets:<br>
>> vpn_udp: udp:<a href="http://80.91.82.252:5060" target="_blank">80.91.82.252:5060</a><br>
>> [...]<br>
>><br>
>> My scenario is this:<br>
>><br>
>> [Softphone] <-> [provider1] <-vpn-> [my sip:provider ce] <-> [pstn]<br>
>><br>
>> extra_socket is the vpn interface (eth1)<br>
>> eaddress is the outside interface (eth3)<br>
>><br>
>> In peer "provider1" I'd have to select "vpn_udp" as my outgoing socket, correct?<br>
>><br>
>><br>
>> Regards,<br>
>> --<br>
>> Joel Smith<br>
>> Cell: <a href="tel:%2B34%20639%2003%2013%2053" value="+34639031353" target="_blank">+34 639 03 13 53</a><br>
>> E-Mail: <a href="mailto:joel@vozelia.com" target="_blank">joel@vozelia.com</a><br>
>><br>
>><br>
>><br>
>><br>
>> On Thu, Nov 8, 2012 at 2:25 PM, Joel Smith | VOZELIA <<a href="mailto:joel@vozelia.com" target="_blank">joel@vozelia.com</a>> wrote:<br>
>>> Thanks Andrew!<br>
>>><br>
>>> The hack was just for testing purposes, I'm undoing it right away :-)<br>
>>><br>
>>> I'll get back to you if anything fails...<br>
>>><br>
>>> Regards,<br>
>>> --<br>
>>> Joel Smith<br>
>>> Cell: <a href="tel:%2B34%20639%2003%2013%2053" value="+34639031353" target="_blank">+34 639 03 13 53</a><br>
>>> E-Mail: <a href="mailto:joel@vozelia.com" target="_blank">joel@vozelia.com</a><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> On Thu, Nov 8, 2012 at 1:55 PM, Andrew Pogrebennyk<br>
>>> <<a href="mailto:apogrebennyk@sipwise.com" target="_blank">apogrebennyk@sipwise.com</a>> wrote:<br>
>>>> Joel,<br>
>>>> the correct format consists of a label and value like this:<br>
>>>> extra_sockets:<br>
>>>> test: udp:<a href="http://10.15.20.108:6060" target="_blank">10.15.20.108:6060</a><br>
>>>> The label is shown in outbound_socket peer preference (you can route<br>
>>>> calls to specific peer out via specific socket).<br>
>>>> I would not recommend to hack this using customtt because in that case<br>
>>>> sip routing will be probably broken.<br>
>>>><br>
>>>> On 11/08/2012 01:49 PM, Joel Smith | VOZELIA wrote:<br>
>>>>> Hi everybody,<br>
>>>>><br>
>>>>> I have a system with multiple IP addresses. What is the correct format<br>
>>>>> of the "extra_sockets" parameter inside config.yml?<br>
>>>>><br>
>>>>> I've tried several different combinations and none make kamailio-lb<br>
>>>>> listen on the secondary ips, so, to solve this I've created a custom<br>
>>>>> tt2 for kamailio-lb but I still need to know what is the correct way<br>
>>>>> to setup extra_sockets in config.yml (otherwise I'll end up with<br>
>>>>> incorrect headers inside sip packets caused by using the wrong IP.)<br>
>>>>><br>
>>>>> Thanks in advanced.<br>
>>>>><br>
>>>>> Best regards.<br>
>>>>> --<br>
>>>>> Joel Smith<br>
>>>>> Cell: <a href="tel:%2B34%20639%2003%2013%2053" value="+34639031353" target="_blank">+34 639 03 13 53</a><br>
>>>>> E-Mail: <a href="mailto:joel@vozelia.com" target="_blank">joel@vozelia.com</a><br>
>>>>><br>
>>>>> _______________________________________________<br>
>>>>> Spce-user mailing list<br>
>>>>> <a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br>
>>>>> <a href="http://lists.sipwise.com/listinfo/spce-user" target="_blank">http://lists.sipwise.com/listinfo/spce-user</a><br>
>>>>><br>
>>>><br>
><br>
> _______________________________________________<br>
> Spce-user mailing list<br>
> <a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br>
> <a href="http://lists.sipwise.com/listinfo/spce-user" target="_blank">http://lists.sipwise.com/listinfo/spce-user</a><br>
><br>
<br>
</div></div><br>_______________________________________________<br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br>
<a href="http://lists.sipwise.com/listinfo/spce-user" target="_blank">http://lists.sipwise.com/listinfo/spce-user</a><br>
<br></blockquote></div><br></div></div></div>
</blockquote></div><br></div>