[Spce-user] rtpengine usage in serial forking
john.nash778 at gmail.com
Fri Jan 23 09:22:35 EST 2015
Thank you once again for explaining Richard. I also tried with
"--sip-source" but it changed port in that also. Any setting which can
enable rtpengine to "lookup" the same port and ignore change in "source IP"
Does it look for source IP and port only or "orgin" and other information
On Fri, Jan 23, 2015 at 7:45 PM, Richard Fuchs <rfuchs at sipwise.com> wrote:
> On 01/23/15 03:54, John Nash wrote:
> > OK I get it now. There is one more scenario I am confused about. If
> > rtpengine_answer() is called in case of session progress and 200 OK, In
> > my setup I receive two session progress messages (one from some IVR and
> > another from gateway) and a 200 OK.
> > I received ports from engine as 1111 for first session progress, 2222
> > from second session progress and 2222 for 200 OK. I was hoping to get
> > same port for both session progress as call-id, from tag and to tag are
> > all same.
> In this case, the called client (or what appears to be the same client)
> is changing media endpoints from the first answer to the second,
> different port and different address. So rtpengine goes along and also
> changes the endpoint between the two answers. Rtpengine always tries to
> mimic what the client is doing.
> Spce-user mailing list
> Spce-user at lists.sipwise.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Spce-user