Dnia 2012-03-14, śro o godzinie 15:26 +, Michael Humphries-Dolnick
pisze:
> Yes, I thought of that, but IIRC after a connection is initiated, the
> daemon does a dialback validation;
Exactly. s2s connections are uni-directional.
Even if the s2s connection is initiated locally it creates outbou
On 3/14/12 9:26 AM, Michael Humphries-Dolnick wrote:
> Peter, thanks for the quick reply.
>
>> If you want to do something like whitelist connections to port 5269 (or
>> whatever you decide to use for s2s), you might need to do that at the
>> firewall
>> level, not the application level.
>
> Yes
Peter, thanks for the quick reply.
> If you want to do something like whitelist connections to port 5269 (or
> whatever you decide to use for s2s), you might need to do that at the firewall
> level, not the application level.
Yes, I thought of that, but IIRC after a connection is initiated, the d
On 3/14/12 9:14 AM, Michael Humphries-Dolnick wrote:
> Hello,
>
> I have two questions, which I have researched and checked the list archive
> and don't see any mention of.
>
> First, I want to confirm: the s2s daemon provides both inbound and outbound
> server-to-server connections, correct?
Hello,
I have two questions, which I have researched and checked the list archive and
don't see any mention of.
First, I want to confirm: the s2s daemon provides both inbound and outbound
server-to-server connections, correct? I believe this is correct, I just want
to confirm.
Second, is the
