[Spce-user] Issue with RTP proxy on dual interface host
Andrew Yager
andrew at rwts.com.au
Mon Aug 17 09:30:15 EDT 2015
Yes; definitely got errors!
Aug 17 22:33:41 sip proxy[1694]: NOTICE: <script>: NAT-Reply - S=100 -
Connecting M=INVITE IP=XXX.XXX.XXX.XXX:53091 (192.168.2.2:5080)
ID=76590ZGMzYTk0ODE3MDY3MzdjMWYzYzQ2MjFiYWMwMWRmYjc
Aug 17 22:33:46 sip proxy[1688]: NOTICE: <script>: NAT-Reply - S=183 -
Session Progress M=INVITE IP=124.189.159.174:53091 (192.168.2.2:5080)
ID=76590ZGMzYTk0ODE3MDY3MzdjMWYzYzQ2MjFiYWMwMWRmYjc
Aug 17 22:33:46 sip proxy[1688]: ERROR: rtpengine [rtpengine.c:1683]:
select_rtpp_set(): no rtp_proxy configured
Aug 17 22:33:46 sip proxy[1688]: ERROR: rtpengine [rtpengine.c:1895]:
set_rtpengine_set_n(): could not locate rtpengine set 50
Aug 17 22:33:46 sip proxy[1688]: ERROR: rtpengine [rtpengine.c:1709]:
select_rtpp_node(): script error -no valid set selected
Aug 17 22:33:46 sip proxy[1688]: ERROR: rtpengine [rtpengine.c:1442]:
rtpp_function_call(): no available proxies
Aug 17 22:33:48 sip proxy[1692]: NOTICE: <script>: NAT-Reply - S=200 - OK
M=INVITE IP=XXX.XXX.XXX.XXX:53091 (192.168.2.2:5080)
ID=76590ZGMzYTk0ODE3MDY3MzdjMWYzYzQ2MjFiYWMwMWRmYjc
Aug 17 22:33:48 sip proxy[1692]: ERROR: rtpengine [rtpengine.c:1683]:
select_rtpp_set(): no rtp_proxy configured
Aug 17 22:33:48 sip proxy[1692]: ERROR: rtpengine [rtpengine.c:1895]:
set_rtpengine_set_n(): could not locate rtpengine set 50
Aug 17 22:33:48 sip proxy[1692]: ERROR: rtpengine [rtpengine.c:1709]:
select_rtpp_node(): script error -no valid set selected
Aug 17 22:33:48 sip proxy[1692]: ERROR: rtpengine [rtpengine.c:1442]:
rtpp_function_call(): no available proxies
Aug 17 22:33:48 sip proxy[1695]: NOTICE: <script>: New request on proxy -
M=ACK R=sip:192.168.2.2:5080;prxroute=1 F=sip:XXX at XXX.XXX.XXX.XXX
T=sip:XXX at XXX.XXX.XXX.XXX IP=XXX.XXX.XXX.XXX:53091 (192.168.2.2:5060)
ID=76590ZGMzYTk0ODE3MDY3MzdjMWYzYzQ2MjFiYWMwMWRmYjc
Aug 17 22:33:56 sip proxy[1693]: NOTICE: <script>: New request on proxy -
M=BYE R=sip:192.168.2.2:5080;prxroute=1 F=sip:XXX at XXX.XXX.XXX.XXX
T=sip:XXX at XXX.XXX.XXX.XXX IP=XXX.XXX.XXX.XXX:53091 (192.168.2.2:5060)
ID=76590ZGMzYTk0ODE3MDY3MzdjMWYzYzQ2MjFiYWMwMWRmYjc
Aug 17 22:33:56 sip proxy[1693]: ERROR: rtpengine [rtpengine.c:1683]:
select_rtpp_set(): no rtp_proxy configured
Aug 17 22:33:56 sip proxy[1693]: ERROR: rtpengine [rtpengine.c:1895]:
set_rtpengine_set_n(): could not locate rtpengine set 50
Aug 17 22:33:56 sip proxy[1693]: ERROR: rtpengine [rtpengine.c:1709]:
select_rtpp_node(): script error -no valid set selected
Aug 17 22:33:56 sip proxy[1693]: ERROR: rtpengine [rtpengine.c:1442]:
rtpp_function_call(): no available proxies
So obviously something hasn't come up correctly, but
root at sip:~# ps aux | grep rtpengine
root 18098 0.0 0.0 7780 1340 pts/2 S+ 23:29 0:00 grep rtp
root 31088 0.2 0.0 206048 3004 pts/2 Sl 22:14 0:12
/usr/sbin/rtpengine --interface=ext/XXX.XXX.XXX.XXX --interface=proxy/
10.237.217.254 --listen-ng=192.168.2.2:2223 --timeout=60
--silent-timeout=3600 --pidfile=/var/run/ngcp-rtpengine-daemon.pid
--tos=184 --port-min=30000 --port-max=40000 --b2b-url=http://%%:8090/
--table=0 --log-level=6
TIA,
Andrew
On 17 August 2015 at 23:13, Andrew Pogrebennyk <apogrebennyk at sipwise.com>
wrote:
> On 08/17/2015 02:37 PM, Andrew Yager wrote:
> > Have just done as you suggested (which was similar to a version of
> > config we had already tried) and am still seeing the same behaviour.
> >
> > The outbound_socket and rtp_socket are both using the "mypeer" RTP
> > socket, but the SDP still includes the endpoint IP.
> >
> > What should we look at next?
>
> Do you have any errors in kamailio-proxy.log like if kamailio can't
> connect to rtpengine? If the logs are clear the next step is to get a
> network trace as well as kamailio-proxy.log (with debug=2: execute
> "ngcp-kamctl proxy fifo debug 2").
>
> Andrew
>
--
*Andrew Yager, Managing Director* *(BCompSc, JNCIS-SP, MACS (Snr) CP)*
Real World Technology Solutions - IT People you can trust
Voice | Data | IT Procurement | Managed IT
rwts.com.au | 1300 798 718
*Real World is a Dell Premier Partner*
This document should be read only by those persons to whom it is addressed
and its content is not intended for use by any other persons. If you have
received this message in error, please notify us immediately. Please also
destroy and delete the message from your computer. Any unauthorised form of
reproduction of this message is strictly prohibited. We are not liable for
the proper and complete transmission of the information contained in this
communication, nor for any delay in its receipt. Please consider the
environment before printing this e-mail.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20150817/ae58048c/attachment-0001.html>
More information about the Spce-user
mailing list