similar to: Asterisks RTP source address binding

Does anyone know how to change the source IP address/Source Interface of RTP packets? Changing the SIP source IP address in sip.conf has no apparent impact on RTP. RTP traffic still uses the address assigned to the outbound interface.

Is there anyway to change the RTP binding address? I've changed the SIP binding address successfully but the setting doesn't seem to effect the RTP binding. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20040629/85ed8291/attachment.htm

C:\>net view \\mummy System error 64 has occurred. The specified network name is no longer available. C:\>ping mummy Pinging mummy [192.168.2.2] with 32 bytes of data: Reply from 192.168.2.2: bytes=3D32 time=3D63ms TTL=3D126 Reply from 192.168.2.2: bytes=3D32 time=3D63ms TTL=3D126 Any ideas? Thanks. ------=_NextPart_000_004B_01C281B0.68A07A90 Content-Type: text/html;

Hello, please excuse the length of my question, and I hope that this is an appropriate place to ask. I have a workstation that has two interfaces connected to two private networks, 192.168.0.0/24 and 192.168.1.0/24, each of which has a separate masquerading gateway to the internet, something like as follows: +-----------> to internet | router0

-----BEGIN PGP SIGNED MESSAGE----- The FreeSWAN project uses rsync to keep our FTP repository up-to-date. The FTP server is at xs4all.nl, and we rsync to one of their FreeBSD boxes (xs1.xs4all.nl) over SSH. We have been experiencing core dumps from the remote rsync. Initially this was with the XS4ALL provided rsync in /usr/local/bin/rsync. Since I didn't have access to the source code for

I am new to Shorewall and FreeSwan, please excuse my ignorance I was wondering if someone could help me. I had help getting my FreeSwan running with the following iptables commands: iptables -I FORWARD -s 0/0 -d 192.168.1.0/24 -i ipsec0 -o eth1 -j ACCEPT iptables -I FORWARD -s 192.168.1.0/24 -d 0/0 -i eth1 -o ipsec0 -j ACCEPT If I manually run this FreeSwan works, however I am not sure

Hi all! I have got a vpn connection set up using FreeSwan and shorewall. Everything works fine but I want to add another subnet to the whole. This means that 1 box will get two net-to-net connections. I want to limit the services on one subnet however. Cuurently I have defined a vpn zone for the current connection and allow all vpn<->loc traffic. How would I go about in tightening the

Hello, I seem to have the Freeswan IPSEC tunnel working between my two sites, but I am still having a problem that looks to be because of something I have configured wrong in my shorewall setup.. I have a LEAF Oxygen < 1.9 heavily modifed firewall setup.. Using FreeSwan 1.91, and Kernel 2.4.8. Modified to use IPTables and standard Debian network/interfaces. I am also using Shorewall

This is an idea from FreeSWAN, which was implemented in the recently released version 1.0. Basically the idea is that FreeSWAN sites automatically encrypt traffic between them when possible, without having to set up the link ahead of time. How this works is: The sites publish some info in DNS. FreeSWAN gets some traffic destined for that site. - looks up the info in DNS - if the info is there:

I have a plan to make freeswan and shorewall talk to each other. Shorewall doesn''t currently have proper handles to make ipsec and firewall work properly together and I''m planning on building a custom _updown script for freeswan to make it communicate with shorewall. How can I make shorewall work properly with different road warriors with different dynamic ip-addresses and

>sample setups of freeswan working with shorewall? I just implemented this a few days ago. In my case it was the simple scenario of two private subnets (with different private network numbers!) already equipped with Shorewall firewalls on which I added Freeswan. The hardest part was being patient enough for the other end''s firewall (a 486= ) to compile the patched kernel. I basically

I''m getting insane here. I''m running shorewall 1.3.11 with iptables 1.2.5 and freeswan 1.97 on a 2.4.18-8 kernel aka MNF. The setup is a followed: Lan (192.168.1.x) - FW (eth1 192.168.1.254 - eth0 64.x.y.71) - router 64.x.y.65 (which is default GW on eth0) -internet - 161.a.b.c (FW-1) So a windows client with checkpoint tries to connect to a vpn-1 server on the internet. The

-----BEGIN PGP SIGNED MESSAGE----- I added the following code to log_exit(): void log_exit(int code, const char *file, int line) { static int error_count=0; if(error_count++ > 10) { abort(); } To force it to bail earlier instead of overflowing the stack. As you can see at frame #50, it is trying to log that the connection went away unexpectantly.

Hi list, I am trying to create a VPN between two different locations. On the first location we have a cisco pix 525 Natting the internal 192.168.100.x network, while on the second location we have a Centos3 box Natting via iptables the internal 192.168.10.x netowrk. My goal is to connect this 2 over the internet via IPsec. I created the IPsec Net2Net via the network configuration graphic

Tuomo Soini wrote: > You don''t happen to read shorewall-devel mailinglist ? I read it -- I just didn''t know what to make of your post and it arrived while I was on vacation. What exactly are you trying to accomplish that Shorewall isn''t doing for you now? e.g. /etc/shorewall/zones rw Roadwarriors Road Warriors /etc/shorewall/interfraces rw ipsec+

Hello, We have a system that interoperates with an external service, so that the basic call flow is: PSTN origination -> Asterisk A -> External service -> Asterisk B Initially the SDP from the external service tells the two Asterisks to send RTP directly to each other. Part way through the call the external service sends re-INVITEs both Asterisks to change the address for audio to

Hi. I am trying to force some traffic that goes to address 203.7.93.94 through a VPN tunnel. I use freeswan 1.98b and Shorewall 1.4.6c in one machine. The 203.7.93.94 is in the DMZ on the other end. (Both ends use the same shorewall and freeswan). I have successfully set up a tunnel between the two network (using a point to point topology, not hub). I added a static routing that redirect

Hi everyone, I'd like to set up the RSA keys for the IAX registration, but have a couple of Q's. I have the manual and can follow the instructions, but I want to understand the limitations. First, understand there will be a central Asterisk (which has the private key?) and several remote Asterisks (which are as automated as possible, and each have the same public key?). We

Hello all, I am configuring a vpn between freeswan and windows 2000. I am following the steps at http://www.jacco2.dds.nl/networking/win2000xp-freeswan.html, to get the VPN up and running. using this I have a ppp tunnel between windows and linux, which is inside a l2tp tunnel which is again encrypted by IPSec. (the url gives the configuration in detail and I have followed it exactly) Now the

Hello, I''ve finally managed to setup a firewall with freeswan 2.04 using the kernel crypto api (backported from kernel 2.6). (Almost) everything seems to work fine if I disable shorewall, but packets are filtered whe shorewall is active. I''ve already read a past thread on the subject and I followed all the hints and it actually partially works: my lan I can access the remote