Re: [Siproxd-users] Need for help, siproxd does not work well....@@...

[Thomas R. <tr...@gm...>]

Just saw something else:

Please don't use a rtp_port range from 5 to 65000. Siproxd will try to
use also the "low port range" that usually is used for "well known
services" and the port range above ~30000 which (depending of you Linux)
is used for masquerading). It *might* work, but I'd not be surprised if
funny things start to happen.
Stay with the port range as provided in the sample configuration file
(7070-7089).

/Thomas




On 26 Aug, Samlee wrote:
> Dear all:
> 
>            Sorry, I am a newbie of siproxd, and have some problem when using
> siproxd...
> 
> The architecture is following:
> 
> private IP address range             :          Internet public IP address
> range
> 
>    192.168.2.1                          :          10.90.8.40
> 
>                                         :
> 
>    192.168.2.91                         :  foo.bar.org          10.90.8.185
> 
>    +-------------+             +--------------+              +-------------+
> 
>    !             !          .1 ! masquerading ! publicIP     !             !
> 
>    ! IntHost     !-------------! Firewall     !------------>>! externalHost!
> 
>    !             !         eth2!              !eth1          !             !
> 
>    +-------------+             +--------------+              +-------------+
> 
>    user: 1111                                                user: 2222
> 
> Both of user 1111 and user 2222 are registered to siproxd, and 
> 
> I want to make a call from "1111" to "2222" and make a call from "2222" to
> "1111".
> 
>  
> 
>        I installed siproxd into a machine with two network interfaces: eth1
> (public IP address, but we use 10.90.8.40 for simulation), eth2 (private IP
> address, 192.168.2.1). 
> 
> To enable NAT, I executed following commands:
> 
> 1. iptables -A INPUT -i eth2 -j ACCEPT
> 
> 2. echo "1" > /proc/sys/net/ipv4/ip_forward
> 
> 3. iptables -t nat -A POSTROUTING -s 192.168.2.0/24 -o eth1 -j MASQUERADE
> 
> Then execute 
> 
> 1. iptables -A INPUT -i eth1 -p udp -m udp --dport 5060 -j ACCEPT
> 
> 2. iptables -A INPUT -i eth1 -p udp -m udp --dport 2:65000 -j ACCEPT
> 
> to receive SIP and RTP message from eth1.
> 
> Finally execute "siproxd".
> 
> My configuration is following:
> 
> # The interface names of INBOUND and OUTBOUND interface.####
> 
> if_inbound  = eth2
> 
> if_outbound = eth1
> 
> host_outbound = 10.90.8.40
> 
>  
> 
> # Access control.#
> 
> hosts_allow_reg = 192.168.2.0/24,10.90.8.0/24
> 
> hosts_allow_sip = 192.168.2.0/24,10.90.8.0/24
> 
>  
> 
> # Port to listen for incoming SIP messages.#
> 
> sip_listen_port = 5060
> 
>  
> 
> # Shall we daemonize?#
> 
> daemonize = 0
> 
>  
> 
> # What shall I log to syslog?#
> 
> silence_log = 0
> 
>  
> 
> # Shall I log call establishment to syslog?#
> 
> log_calls = 1
> 
>  
> 
> # Secure Enviroment settings:#
> 
> user = root
> 
>  
> 
> # Registration file:#
> 
> registration_file = /usr/local/sipproxd/etc/siproxd_registrations
> 
>  
> 
> # Automatically save current registrations every 'n' seconds#
> 
> autosave_registrations = 300
> 
>  
> 
> # PID file:#
> 
> pid_file = /usr/local/sipproxd/etc/siproxd.pid
> 
>  
> 
> # global switch to control the RTP proxy behaviour#
> 
> rtp_proxy_enable = 0
> 
>  
> 
> # Port range to allocate listen ports from for incoming RTP traffic
> 
> rtp_port_low  = 2
> 
> rtp_port_high = 65000
> 
>  
> 
> # Timeout for RTP streams#
> 
> rtp_timeout = 300
> 
>  
> 
> # Default Expiration timeout for Registrations#
> 
> default_expires = 600
> 
>  
> 
> # Proxy authentication#
> 
> proxy_auth_pwfile = usr/local/sipproxd/etc/siproxd_passwd.cfg
> 
>  
> 
> # Debug level... (setting to -1 will enable everything)#
> 
> debug_level =      0x00000000
> 
>  
> 
> But when 1111 makes a call to 2222 , the call is failed. 2222 is ringing,
> but when taking the call, 1111 will send CANCEL message..@@
> 
> When 2222 makes a call to 1111, the signaling is OK , but there is only one
> way RTP from 1111 to 2222.@@
> 
>  
> 
> Is it something wrong of the configuration file? Or the NAT setting ? .. @@
> , please help, Thank you 
> 
>  
> 
> Best Regards,
> 
> sam
> 
>  
> 

-- 
GnuPG: pub  1024D/87BCDC94 2000-03-19 Thomas Ries <tr...@gm...>
-      Fingerprint = 13D1 19F5 77D0 4CEC 8D3F  A24E 09FC C18A 87BC DC94
-      Key via pgp.openpkg.org / http://www.ries.ch.vu/87BCDC94.pub
VoIP:  sip:174...@pr... | sip:43...@fw...