[Spce-user] upgrade to 3.1 problem

[Miguel Rios]

Hi Andrew,

Thanks for your help, as always.


Indeed issuing the start command seems to have fixed the problem.

The relevant rtp.log after issuing the restart command is:

Nov 22 16:40:33 fortknox mediaproxy-ng[4054]: Version 2.3.3 shutting down
Nov 22 16:40:34 fortknox mediaproxy-ng[22075]: Startup complete, version 2.3.3

Seems all is OK as there are no errors now but I'll do some more testing.


Thanks again






On Friday, November 22, 2013 4:28 PM, Andrew Pogrebennyk <apogrebennyk at sipwise.com> wrote:
 
Hi Miguel,
looks like mediaproxy is not running. Please try:

/etc/init.d/ngcp-mediaproxy-ng-daemon start
tail -50 /var/log/ngcp/rtp.log

then post us the output and check if the problem is gone?
Andrew


On 11/22/2013 05:19 PM, Miguel Rios wrote:
> Hi,
> 
> After upgrading to 3.1 just now, I see that there's a problem with
> mediaproxy. I believe the network.yml hasn't changed as I see my public
> IP there as before, so I'm assuming something broke with the upgrade.
> 
> Nov 22 15:56:54 host proxy[3926]: ERROR: rtpproxy-ng [rtpproxy.c:1515]: send_rtpp_command(): can't send command to a RTP proxy
> Nov 22 15:56:54 host proxy[3926]: ERROR: rtpproxy-ng [rtpproxy.c:1551]: send_rtpp_command(): proxy <udp:127.0.0.1:2223> does not respond, disable it
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20131122/309bc256/attachment-0001.html>