Re: [SR-Users] rtpengine and serial forking with multiple network interfaces

2015-12-15 Thread Andreas Granig
Hi, On 12/10/2015 01:33 PM, Alex Balashov wrote: > I tested an approach in which all initial rtpengine_manage() calls (in > support of a new SDP offer) were made in a branch_route[], and this > appeared to work. > > Is this the 'orthodox' way to do it? That's the way we're using it also. Andrea

Re: [SR-Users] rtpengine and serial forking with multiple network interfaces

2015-12-10 Thread Alex Balashov
I tested an approach in which all initial rtpengine_manage() calls (in support of a new SDP offer) were made in a branch_route[], and this appeared to work. Is this the 'orthodox' way to do it? -- Alex Balashov | Principal | Evariste Systems LLC 303 Perimeter Center North, Suite 300 Atlanta, G

[SR-Users] rtpengine and serial forking with multiple network interfaces

2015-12-10 Thread Alex Balashov
Hi, It is not very clear to me how to handle serial forking scenarios with rtpengine where there are multiple RTP listeners attached to multiple network interfaces. That is to say, given: rtpengine ... -i net1/xxx.xxx.xxx.xxx -i net2/yyy.yyy.yyy.yyy 1. I attempt to reach SIP gateway 1 vi