[Spce-user] Understanding extra_sockets format in config.yml

[Joel Smith | VOZELIA]

Hi,

I've done a little further testing...


Scenario A (2 IPs):

[Softphone] <-> [provider1] <-vpn-> [my sip:provider ce] <-> [pstn]

extra_socket is the vpn interface (eth1)
eaddress is the other (outside) interface (eth3)

--> NO audio at all.


Scenario B (2 IPs):

[Softphone] <-> [provider1] <-vpn-> [my sip:provider ce] <-> [pstn]

eaddress is the vpn interface (eth1)
extra_socket is the other (outside) interface (eth3)

--> NO audio at all.


Scenario C (2 IPs):

[Softphone] <-> [provider1] <-vpn-> [my sip:provider ce] <-> [pstn]

eaddress is the vpn interface (eth1)
extra_socket is the other (outside) interface (eth3)
in the pstn-peer settings the "vpn_udp" extra socket is selected.

--> One-way audio.


Scenario D (1 IP):

[Softphone] <-> [provider1] <-vpn-> [my sip:provider ce] <-vpn-> [pstn]

eaddress is the vpn interface (eth1)
no extra_socket is configured.

--> Audio works perfect.


My desired scenario is A, but I need to handle the call correctly and
obviously I'm not. The problem is that calls always enter the
sipwise-server from vpn-interface and then leave the sipwise-server
through the outside-interface.

Thank you in advanced.


Best regards,
--
Joel Smith
Cell: +34 639 03 13 53
E-Mail: joel at vozelia.com




On Thu, Nov 8, 2012 at 5:16 PM, Joel Smith | VOZELIA <joel at vozelia.com> wrote:
> Hi Andrew
>
> I've deleted the customtt file and added the extra_socket.
>
> My config.yml has this:
>
> [...]
>   eaddress: 37.139.120.59
>   iaddress: 127.0.0.1
> [...]
>     extra_sockets:
>       vpn_udp: udp:80.91.82.252:5060
> [...]
>
> My scenario is this:
>
> [Softphone] <-> [provider1] <-vpn-> [my sip:provider ce] <-> [pstn]
>
> extra_socket is the vpn interface (eth1)
> eaddress is the outside interface (eth3)
>
> In peer "provider1" I'd have to select "vpn_udp" as my outgoing socket, correct?
>
>
> Regards,
> --
> Joel Smith
> Cell: +34 639 03 13 53
> E-Mail: joel at vozelia.com
>
>
>
>
> On Thu, Nov 8, 2012 at 2:25 PM, Joel Smith | VOZELIA <joel at vozelia.com> wrote:
>> Thanks Andrew!
>>
>> The hack was just for testing purposes, I'm undoing it right away :-)
>>
>> I'll get back to you if anything fails...
>>
>> Regards,
>> --
>> Joel Smith
>> Cell: +34 639 03 13 53
>> E-Mail: joel at vozelia.com
>>
>>
>>
>>
>> On Thu, Nov 8, 2012 at 1:55 PM, Andrew Pogrebennyk
>> <apogrebennyk at sipwise.com> wrote:
>>> Joel,
>>> the correct format consists of a label and value like this:
>>>     extra_sockets:
>>>       test: udp:10.15.20.108:6060
>>> The label is shown in outbound_socket peer preference (you can route
>>> calls to specific peer out via specific socket).
>>> I would not recommend to hack this using customtt because in that case
>>> sip routing will be probably broken.
>>>
>>> On 11/08/2012 01:49 PM, Joel Smith | VOZELIA wrote:
>>>> Hi everybody,
>>>>
>>>> I have a system with multiple IP addresses. What is the correct format
>>>> of the "extra_sockets" parameter inside config.yml?
>>>>
>>>> I've tried several different combinations and none make kamailio-lb
>>>> listen on the secondary ips, so, to solve this I've created a custom
>>>> tt2 for kamailio-lb but I still need to know what is the correct way
>>>> to setup extra_sockets in config.yml (otherwise I'll end up with
>>>> incorrect headers inside sip packets caused by using the wrong IP.)
>>>>
>>>> Thanks in advanced.
>>>>
>>>> Best regards.
>>>> --
>>>> Joel Smith
>>>> Cell: +34 639 03 13 53
>>>> E-Mail: joel at vozelia.com
>>>>
>>>> _______________________________________________
>>>> Spce-user mailing list
>>>> Spce-user at lists.sipwise.com
>>>> http://lists.sipwise.com/listinfo/spce-user
>>>>
>>>