It's a rather advanced configuration you are trying to set up. In theory, yes, this can work, but I don't know what you run into. You may need to turn off mhomed and manually control how you record route. You also need to be careful to make each rtpproxy instance listen and announce the right interfaces etc. All this requires good insight in SIP protocol, SDP, and ser.cfg and is beyond what I can possibly guide you through. I assume your routing table is perfectly set up, of course ;-)

To running several ser instances: create symlinks to ser in sbin (ser2, ser3 or something), create a separate mysql database and ser.cfg for each and make sure to modify dburls, fifo/sock, listening ports etc to avoid conflicts. Also, if you start ser using an init.d script, remember to change pid and /var/run files. g-)

Gerardo Amaya wrote:

Hello Greger. Thank you so much for your answer. Right now I'm trying to layer SER in multiple instances as you recommend.

Now the approach for this will be to install multiple and different SER Servers in a different path on the machine and started each SER individually for each network to be bridged with it's own configuration file?

Can I run multiple SER servers with one installation and just add -f /new_conf_file/ to each instance?

Right now the only way to make SER work between multiple interfaces is to enable the mhomed=1 option. Since I have 6-8 network interfaces(2 for each network) can I expect problems if all ser instances will have the mhomed=1 parameter?

I have seen that the use of multiple instances is considered for SER, but there is no documentation for that, can someone please help me pointing out which is the best way to run ser on this environment?

Thanks in advanced

Gerardo Amaya

Greger V. Teigre wrote:

...

Inline.

Gerardo Amaya wrote:

...

Hello All. After investigating quite a while about this issue I'm kind of desperate now, I will appreciate your help on this.

I have a SER Server with multiple interfaces, I'm able to handle all the SIP packets with the multi homed enabled. Now the part that I'm having real trouble with is the RTP audio streams. After struggling with MediaProxy I finally started using RTPProxy for this, since it has bridge mode available. Now the problem is that I have more than one network to connect audio from, so the internal and external configuration is not enough for me. So my questions are:

1.-Can I have RTPProxy Bridge mode working for all the interfaces in my server?

No, but you can "layer" ser where each instance is bridging it's own network.

...

2.-Can I have more than one RTPProxy socket available for each of the multiple interfaces I'm connecting in order to have the audio working, so each route will use the proxy of their own network?

The issue is to make sure that SDP is correctly replaced for INVITE and 200 OK dependent on the network origin and destination of the message. rtpproxy will only handle an internal and an external network. You also have the problem of nat_uac_test() testing for private addresses to detect NAT, so you need to replace those tests with IP-based tests to make sure you detect which network is src and dst. g-)

...

3.-If #2 is true, is this where the force_socket and force_rtp_proxy functions play a role in my configuration?

Please help!!

Thanks you so much in advance

Gerardo Amaya

---

Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers