6 Oct
2010
6 Oct
'10
7:18 p.m.
You post reminded me that I should update the examples on the repo
(which I just did).
It is better to use the new rtpproxy_offer/rtpproxy_answer functions.
For a quick example, please check:
http://git.sip-router.org/cgi-bin/gitweb.cgi?p=sip-router;a=blob_plain;f=mo…
Regards,
Ovidiu Sas
On Wed, Oct 6, 2010 at 6:41 PM, Stagg Shelton <stagg(a)vocalcloud.com> wrote:
I'm working on a setup where we have rtpproxy on a
machine with eth0 IP
10.10.5.141/19 and eth1 IP 10.10.10.78/24. When using
force_rtp_proxy("","10.10.5.141"); the connection information (c)
field in
the SDP is not being set to the ip 10.10.5.141 It is instead being set to
10.10.10.78
We are starting to run out of ideas on getting the proper contact address
into the sdp based on call source signaling ip. Does anyone have any ideas
what the problem could be?
Thanks
Stagg
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users