top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Can we use sip client with stateless proxy?

0 votes
441 views

My configuration is following

SIP client <--> stateless proxy <--> SIP server

My doubt is that if SIP can work with stateless proxy though it will always work statefull proxy.

posted Jun 25, 2014 by anonymous

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

0 votes

its implementation/requirement specific thing, if in your network there is no need of state-full proxies, no need to use the same.
can go ahead with the stateless proxies as well.
SIP will work with stateless proxies as well, only thing is you will miss the advantages and extra feature of statefull proxies if thinking about pure VOIP network.

answer Apr 28, 2016 by Bhushan Patil
Similar Questions
+1 vote

I am working with a stateless firewall to help keep up with DoS and a state flood. I have a few doubts about my setup:

a.) When allowing web traffic, is it necessary to allow port range 1000:65535 ? i saw that due to this rule sending packets to those ports directly respond with a REJECT instead of a DROP which is preferred. Any
work around and still have a stateless setup?

b.) What is needed to safely have a default OUTPUT DROP, apparently as soon as i change it to that iam unable to access it via ssh, even if I add a rule like this: /sbin/iptables -A OUTPUT -p tcp --dport 22 -j ACCEPT

#!/bin/bash

/sbin/iptables -F
/sbin/iptables -X

/sbin/iptables -P INPUT DROP
/sbin/iptables -P FORWARD DROP
/sbin/iptables -P OUTPUT ACCEPT

#ICMP IN
/sbin/iptables -A INPUT -p icmp -s 178.174.50.29/24 -j ACCEPT

#ICMP IN (TRACEROUTE)
/sbin/iptables -A INPUT -p icmp --icmp-type 0 -j ACCEPT
/sbin/iptables -A INPUT -p icmp --icmp-type 11 -j ACCEPT

#ICMP OUT
/sbin/iptables -A OUTPUT -p icmp --icmp-type 8 -j ACCEPT

#DNS RESOLVERS
/sbin/iptables -A INPUT -s 63.15.64.91 -j ACCEPT
/sbin/iptables -A INPUT -s 63.15.64.92 -j ACCEPT

#SSH
/sbin/iptables -A INPUT -p tcp --dport 22 -j ACCEPT

#WEB
/sbin/iptables -A INPUT -p tcp --dport 1000:65535 -j ACCEPT
/sbin/iptables -A INPUT -p tcp --dport 80 -j ACCEPT
+2 votes

Im trying to configure the proxy_balancer, but still having problems. Here is my configuration:

BalancerMember http://172.16.14.81:80 
retry=120 
timeout=10 

BalancerMember http://172.16.14.82:80 
retry=1 
timeout=10 
status=+H

But when The first worker fails, request are not redirected to the failover worker. For this I have to wait for more than 7 minutes. Is this behavior normal?

+1 vote

I have two virtual web server and only one IP for the host. So the need of some kind of proxy server.
Whitch one should I use? (apache, nginx, varnish, squid)

I need also the same for smtp (two postfix), if possible the same one :-) basic config?

I have one host , one IP and two domain, one for each virtual machine and the result I want:
abc.org[188.165.211.22]--->abc.org[192.168.50.2]
xyz.org[188.165.211.22]--->xyz.org[192.168.50.3]

0 votes

While going through rfc 3665 , I stopped where proxy server was sending 407 to originator of INVITE request message.
I want to know in what cases/scenarios, proxy server does this.

...