Re: [OpenSIPS-Users] Mediaproxy Relay start error - 'MediaRelayBase' is not defined

[Mark Allen]

Yep - the software loaded successfully, integrated with OpenSIPS and I can
see in the log file that it is trying to handle RTP traffic. Just need to
work out the correct configuration now! :)

Thanks for the help Adrian
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Mediaproxy Relay start error - 'MediaRelayBase' is not defined

[Mark Allen]

Hi Adrian - thanks for getting back to me

I'm getting an unexpected error on apt-get update using the following in
sources.list...

# AG Projects software
deb http://ag-projects.com/debian unstable main
deb-src http://ag-projects.com/debian unstable main

...I get...

Err:10 https://ag-projects.com/debian unstable Release
 404  Not Found [IP: 85.17.186.10 443]
E: The repository 'http://ag-projects.com/debian unstable Release' no
longer has a Release file.

...I've checked with nmap and I can see port 443 on 85.17.186.10

I've set it to use 'buster' instead of 'unstable' ('buster' was previously
giving me a similar error)...

# AG Projects software
deb http://ag-projects.com/debian buster main
deb-src http://ag-projects.com/debian buster  main

...and that seems to now be working as I get...

Hit:5 https://ag-projects.com/debian buster InRelease

...and when I install packages I'm seeing...

Get:1 https://ag-projects.com/debian buster/main amd64
mediaproxy-common amd64 4.0.5buster [63.1 kB]
Get:2 https://ag-projects.com/debian buster/main amd64
mediaproxy-dispatcher all 4.0.5buster [18.1 kB]
Get:3 https://ag-projects.com/debian buster/main amd64 mediaproxy-relay
all 4.0.5buster [18.6 kB]
Fetched 99.8 kB in 0s (535 kB/s)

...so hopefully I'm good to go now.

Thanks for your help. I'll post a follow-up once I've got it up and running








On Wed, 6 Jan 2021 at 21:59, Adrian Georgescu  wrote:

> This was a bug.
>
> You must update to the latest mediaproxy version:
>
> sudo apt update
> sudo apt install mediaproxy-relay mediaproxy-common mediaproxy-dispatcher
>
> Regards,
> Adrian
>
> On 6 Jan 2021, at 12:59, Mark Allen  wrote:
>
> Hi all - not sure what I'm missing here...
>
> I'm installing Mediaproxy onto our Debian Buster box which is also running
> OpenSIPS 3.1 but when I start the relay I'm getting an error in syslog...
>
> 15:40:07 opensipsx media-relay[4983]: INFO Starting MediaProxy Relay
> 4.0.4
> 15:40:07 opensipsx media-relay[4983]: INFO Set resource limit for
> maximum open file descriptors to 11000
> 15:40:07 opensipsx media-relay[4983]: CRITICAL Failed to create MediaProxy
> Relay: name 'MediaRelayBase' is not defined
> 15:40:07 opensipsx media-relay[4983]: ERRORTraceback (most recent call
> last):#012ERROR  File "/usr/bin/media-relay", line 100, in
> #012ERRORfrom mediaproxy.relay import MediaRelay#012ERROR
>File "/usr/lib/python3/dist-packages/mediaproxy/relay.py", line 290, in
> #012ERRORclass MediaRelay(MediaRelayBase):#012ERROR
>  NameError: name 'MediaRelayBase' is not defined
> 15:40:07 opensipsx systemd[1]: mediaproxy-relay.service: Main process
> exited, code=exited, status=1/FAILURE
> 15:40:07 opensipsx systemd[1]: mediaproxy-relay.service: Failed with
> result 'exit-code'.
>
> I'm starting the relay with the command...
>
> systemctl start mediaproxy-relay
>
> ...I installed Mediaproxy using the Debian package using the instructions
> at http://mediaproxy.ag-projects.com/installation-guide/ and
> https://github.com/AGProjects/mediaproxy. mediaproxy-dispatcher is
> starting successfully.
>
> In the /etc/mediaproxy/config.ini file - everything is left at the default
> setting except for...
>
> dispatchers = xxx.xxx.xxx.xxx
> advertised_ip = xxx.xxx.xxx.xxx
>
> Certificates are in place in /etc/mediaproxy/tls
>
>
> Anybody got any ideas about where I've gone wrong
>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Mediaproxy Relay start error - 'MediaRelayBase' is not defined

[Adrian Georgescu]

This was a bug.

You must update to the latest mediaproxy version:

sudo apt update 
sudo apt install mediaproxy-relay mediaproxy-common mediaproxy-dispatcher

Regards,
Adrian

> On 6 Jan 2021, at 12:59, Mark Allen  wrote:
> 
> Hi all - not sure what I'm missing here... 
> 
> I'm installing Mediaproxy onto our Debian Buster box which is also running 
> OpenSIPS 3.1 but when I start the relay I'm getting an error in syslog...
> 
> 15:40:07 opensipsx media-relay[4983]: INFO Starting MediaProxy Relay 4.0.4
> 15:40:07 opensipsx media-relay[4983]: INFO Set resource limit for maximum 
> open file descriptors to 11000
> 15:40:07 opensipsx media-relay[4983]: CRITICAL Failed to create MediaProxy 
> Relay: name 'MediaRelayBase' is not defined
> 15:40:07 opensipsx media-relay[4983]: ERRORTraceback (most recent call 
> last):#012ERROR  File "/usr/bin/media-relay", line 100, in 
> #012ERRORfrom mediaproxy.relay import MediaRelay#012ERROR 
>  File "/usr/lib/python3/dist-packages/mediaproxy/relay.py", line 290, in 
> #012ERRORclass MediaRelay(MediaRelayBase):#012ERROR
> NameError: name 'MediaRelayBase' is not defined
> 15:40:07 opensipsx systemd[1]: mediaproxy-relay.service: Main process exited, 
> code=exited, status=1/FAILURE
> 15:40:07 opensipsx systemd[1]: mediaproxy-relay.service: Failed with result 
> 'exit-code'.
> 
> I'm starting the relay with the command...
> 
> systemctl start mediaproxy-relay
> 
> ...I installed Mediaproxy using the Debian package using the instructions at 
> http://mediaproxy.ag-projects.com/installation-guide/ 
>  and 
> https://github.com/AGProjects/mediaproxy 
> . mediaproxy-dispatcher is starting 
> successfully.
> 
> In the /etc/mediaproxy/config.ini file - everything is left at the default 
> setting except for...
> 
> dispatchers = xxx.xxx.xxx.xxx
> advertised_ip = xxx.xxx.xxx.xxx
> 
> Certificates are in place in /etc/mediaproxy/tls
> 
> 
> Anybody got any ideas about where I've gone wrong
> 
> 
> 
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Mediaproxy Relay start error - 'MediaRelayBase' is not defined

[Mark Allen]

Hi all - not sure what I'm missing here...

I'm installing Mediaproxy onto our Debian Buster box which is also running
OpenSIPS 3.1 but when I start the relay I'm getting an error in syslog...

15:40:07 opensipsx media-relay[4983]: INFO Starting MediaProxy Relay
4.0.4
15:40:07 opensipsx media-relay[4983]: INFO Set resource limit for
maximum open file descriptors to 11000
15:40:07 opensipsx media-relay[4983]: CRITICAL Failed to create MediaProxy
Relay: name 'MediaRelayBase' is not defined
15:40:07 opensipsx media-relay[4983]: ERRORTraceback (most recent call
last):#012ERROR  File "/usr/bin/media-relay", line 100, in
#012ERRORfrom mediaproxy.relay import MediaRelay#012ERROR
   File "/usr/lib/python3/dist-packages/mediaproxy/relay.py", line 290, in
#012ERRORclass MediaRelay(MediaRelayBase):#012ERROR
 NameError: name 'MediaRelayBase' is not defined
15:40:07 opensipsx systemd[1]: mediaproxy-relay.service: Main process
exited, code=exited, status=1/FAILURE
15:40:07 opensipsx systemd[1]: mediaproxy-relay.service: Failed with result
'exit-code'.

I'm starting the relay with the command...

systemctl start mediaproxy-relay

...I installed Mediaproxy using the Debian package using the instructions
at http://mediaproxy.ag-projects.com/installation-guide/ and
https://github.com/AGProjects/mediaproxy. mediaproxy-dispatcher is starting
successfully.

In the /etc/mediaproxy/config.ini file - everything is left at the default
setting except for...

dispatchers = xxx.xxx.xxx.xxx
advertised_ip = xxx.xxx.xxx.xxx

Certificates are in place in /etc/mediaproxy/tls


Anybody got any ideas about where I've gone wrong
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] mediaproxy relay stuck on source port 1024

[Jeff Pyle]

Hello,

I have Mediaproxy 2.6.1 and OpenSIPS 1.10 on Debian wheezy with a bit of an
unusual configuration.

The box has a LAN-facing interface ('lan') and a WAN-facing interface
('wan').  The lan has a private IP and the wan has a public IP.  Each
interface has a separate OpenSIPS instance bound to it for communication
with SIP entities on its respective network.  The two OpenSIPS instances
exchange SIP traffic with each other across localhost.

I had rtpproxy bridging media across the interfaces but it has a problem I
can't work around at the moment.  So, I'm attempting to creatively
configure an RTP bridge with Mediaproxy.  I've done this by running a
separate relay/dispatcher pair on each OpenSIPS instance.  Each pair has
its own config with the correct lan or wan IP address.  Since two
interfaces on a single linux system can send traffic directly to each other
without concern for subnets and traditional routing rules, I figure if I
can get each relay to send traffic to the other one and then out thenI've
created a bridge.

The cool thing is it (almost) works.  On the relays I've configured
different port ranges to make it more obvious which relay I'm observing,
with 16384:24572 on the wan instance and 24576:32768 on the lan instance.
All the SDPs look good through the system with proper port selection.  The
relay debugs and dispatcher stats agree with the SDPs.  RTP flows look just
about right, with the exception that traffic leaving the relay always has
source port 1024.

Any thoughts on what might cause a relay's traffic always to source from
1024 rather than the port it has chosen?  This is the case for both the lan
and wan relays sending traffic to its respective host on its own network.



Regards,
Jeff
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] MediaProxy Relay 2.3.8 -Centos 6.5 default_host_ip error

[Tijmen de Mes]

Hi,

You should check which python-application this version need and install it, 
1.1.5 is too new for the is really old relay (2009).

Also you should be able to run the latest version of mediaproxy on centos 6.5 
without problems.

-- 
Tijmen de Mes
AG-Projects

From: Jonathan Hunter 
Reply: OpenSIPS users mailling list >
Date: 22 september 2014 at 21:55:23
To: users@lists.opensips.org >
Subject:  Re: [OpenSIPS-Users] MediaProxy Relay 2.3.8 -Centos 6.5 
default_host_ip error  

Hi Laszlo,

Thanks for the response, sorry missed it!

I have  python_application-1.1.5-py2.6.egg-info installed currently.

Jon



From: hunter...@hotmail.com
To: users@lists.opensips.org
Subject: MediaProxy Relay 2.3.8 -Centos 6.5 default_host_ip error
Date: Fri, 19 Sep 2014 16:45:24 +

Hi All,

I have opensips version 1.5.3 running fine on Centos 6.5, as well as 
media-dispatcher, however when it comes to starting media-relay I get the 
following error;



Sep 19 17:41:07 sgw media-relay[30835]: Starting MediaProxy Relay 2.3.8
Sep 19 17:41:07 sgw media-relay[30835]: fatal error: failed to create 
MediaProxy Relay: cannot import name default_host_ip
Sep 19 17:41:07 sgw media-relay[30835]: Traceback (most recent call last):
Sep 19 17:41:07 sgw media-relay[30835]:   File "/usr/bin/media-relay", line 61, 
in 
Sep 19 17:41:07 sgw media-relay[30835]:     from mediaproxy.relay import 
MediaRelay
Sep 19 17:41:07 sgw media-relay[30835]:   File 
"/usr/lib64/python2.6/site-packages/mediaproxy/relay.py", line 33, in 
Sep 19 17:41:07 sgw media-relay[30835]:     from application.system import 
default_host_ip
Sep 19 17:41:07 sgw media-relay[30835]: ImportError: cannot import name 
default_host_ip

Any tips/idea's appreciated.

Thanks

Jon


___  
Users mailing list  
Users@lists.opensips.org  
http://lists.opensips.org/cgi-bin/mailman/listinfo/users  
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] MediaProxy Relay 2.3.8 -Centos 6.5 default_host_ip error

[Jonathan Hunter]

Hi Laszlo,
Thanks for the response, sorry missed it!
I have  python_application-1.1.5-py2.6.egg-info installed currently.
Jon


From: hunter...@hotmail.com
To: users@lists.opensips.org
Subject: MediaProxy Relay 2.3.8 -Centos 6.5 default_host_ip error
Date: Fri, 19 Sep 2014 16:45:24 +




Hi All,
I have opensips version 1.5.3 running fine on Centos 6.5, as well as 
media-dispatcher, however when it comes to starting media-relay I get the 
following error;


Sep 19 17:41:07 sgw media-relay[30835]: Starting MediaProxy Relay 2.3.8Sep 19 
17:41:07 sgw media-relay[30835]: fatal error: failed to create MediaProxy 
Relay: cannot import name default_host_ipSep 19 17:41:07 sgw 
media-relay[30835]: Traceback (most recent call last):Sep 19 17:41:07 sgw 
media-relay[30835]:   File "/usr/bin/media-relay", line 61, in Sep 19 
17:41:07 sgw media-relay[30835]: from mediaproxy.relay import MediaRelaySep 
19 17:41:07 sgw media-relay[30835]:   File 
"/usr/lib64/python2.6/site-packages/mediaproxy/relay.py", line 33, in 
Sep 19 17:41:07 sgw media-relay[30835]: from application.system 
import default_host_ipSep 19 17:41:07 sgw media-relay[30835]: ImportError: 
cannot import name default_host_ip
Any tips/idea's appreciated.
Thanks
Jon


  ___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] MediaProxy Relay 2.3.8 -Centos 6.5 default_host_ip error

[Laszlo]

On Fri, Sep 19, 2014 at 6:45 PM, Jonathan Hunter 
wrote:

> Hi All,
>
> I have opensips version 1.5.3 running fine on Centos 6.5, as well as
> media-dispatcher, however when it comes to starting media-relay I get the
> following error;
>
>
>
> Sep 19 17:41:07 sgw media-relay[30835]: Starting MediaProxy Relay 2.3.8
> Sep 19 17:41:07 sgw media-relay[30835]: fatal error: failed to create
> MediaProxy Relay: cannot import name default_host_ip
> Sep 19 17:41:07 sgw media-relay[30835]: Traceback (most recent call last):
> Sep 19 17:41:07 sgw media-relay[30835]:   File "/usr/bin/media-relay",
> line 61, in 
> Sep 19 17:41:07 sgw media-relay[30835]: from mediaproxy.relay import
> MediaRelay
> Sep 19 17:41:07 sgw media-relay[30835]:   File
> "/usr/lib64/python2.6/site-packages/mediaproxy/relay.py", line 33, in
> 
> Sep 19 17:41:07 sgw media-relay[30835]: from application.system import
> default_host_ip
> Sep 19 17:41:07 sgw media-relay[30835]: ImportError: cannot import name
> default_host_ip
>
> Any tips/idea's appreciated.
>
> Thanks
>
> Jon
>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
Which version of  python-application you using?


-- 

--
Kind regards,
Laszlo Bekesi
http://voipfreak.net
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] MediaProxy Relay 2.3.8 -Centos 6.5 default_host_ip error

[Jonathan Hunter]

Hi All,
I have opensips version 1.5.3 running fine on Centos 6.5, as well as 
media-dispatcher, however when it comes to starting media-relay I get the 
following error;


Sep 19 17:41:07 sgw media-relay[30835]: Starting MediaProxy Relay 2.3.8Sep 19 
17:41:07 sgw media-relay[30835]: fatal error: failed to create MediaProxy 
Relay: cannot import name default_host_ipSep 19 17:41:07 sgw 
media-relay[30835]: Traceback (most recent call last):Sep 19 17:41:07 sgw 
media-relay[30835]:   File "/usr/bin/media-relay", line 61, in Sep 19 
17:41:07 sgw media-relay[30835]: from mediaproxy.relay import MediaRelaySep 
19 17:41:07 sgw media-relay[30835]:   File 
"/usr/lib64/python2.6/site-packages/mediaproxy/relay.py", line 33, in 
Sep 19 17:41:07 sgw media-relay[30835]: from application.system 
import default_host_ipSep 19 17:41:07 sgw media-relay[30835]: ImportError: 
cannot import name default_host_ip
Any tips/idea's appreciated.
Thanks
Jon


  ___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Mediaproxy relay oddness

[Dan Pascu]

On 23 Jul 2014, at 15:38, Jeff Pyle wrote:

> The ports in use are 16384-32768.  That provides for ~8000 session, yes?

Only ~4000. There are 4 ports allocated per session.

>  We were nowhere near that many calls.  So, it's much more likely that ports 
> were not being released for some reason.

--
Dan





___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Mediaproxy relay oddness

[Saúl Ibarra Corretgé]

On 23 Jul 2014, at 14:38, Jeff Pyle  wrote:

> HI Saul,
> 
> The ports in use are 16384-32768.  That provides for ~8000 session, yes?  We 
> were nowhere near that many calls.  So, it's much more likely that ports were 
> not being released for some reason.
> 
> There is a limited amount of T.38 traffic through these relays.  The majority 
> of the T.38-speaking devices are Adtran TA900-series, which, in general, 
> behave quite well.  That's on our side.  On the partner side, usually Sonus 
> GSX 9000-series.  I bet it's the unusual client that is the problem.
> 
> A SIP capture isn't practical here.  :(   I'll try to correlate the 
> exceptions with CDR records to determine if there is a particular trunk group 
> on my network that needs its attitude adjusted.
> 
> Until we can update the entire call flow (Opensips, Mediaproxy, all deps, 
> ...), or find a definitive misbehaving client, I'll restart the relays on a 
> schedule.  If I am able to reproduce the exceptions I'll provide debug data.
> 

Ok, thanks! If you manage to get some SIP captures feel free to email them to 
me privately.

--
Saúl Ibarra Corretgé
AG Projects





signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Mediaproxy relay oddness

[Jeff Pyle]

HI Saul,

The ports in use are 16384-32768.  That provides for ~8000 session, yes?
 We were nowhere near that many calls.  So, it's much more likely that
ports were not being released for some reason.

There is a limited amount of T.38 traffic through these relays.  The
majority of the T.38-speaking devices are Adtran TA900-series, which, in
general, behave quite well.  That's on our side.  On the partner side,
usually Sonus GSX 9000-series.  I bet it's the unusual client that is the
problem.

A SIP capture isn't practical here.  :(   I'll try to correlate the
exceptions with CDR records to determine if there is a particular trunk
group on my network that needs its attitude adjusted.

Until we can update the entire call flow (Opensips, Mediaproxy, all deps,
...), or find a definitive misbehaving client, I'll restart the relays on a
schedule.  If I am able to reproduce the exceptions I'll provide debug data.


- Jeff



On Wed, Jul 23, 2014 at 4:01 AM, Saúl Ibarra Corretgé 
wrote:

> Hi Jeff,
>
> On 21 Jul 2014, at 21:55, Jeff Pyle  wrote:
>
> > Hello,
> >
> > This is on Opensips 1.6 with Mediaproxy 2.4.4.  Yeah, they're old.  I
> know.
> >
> > We see this from time to time:
> >
> > media-relay[10719]: Traceback (most recent call last):
> > media-relay[10719]:   File
> "/usr/lib/python2.5/site-packages/twisted/internet/udp.py", line 126, in
> doRead
> > media-relay[10719]: self.protocol.datagramReceived(data, addr)
> > media-relay[10719]:   File
> "/usr/lib/pymodules/python2.5/mediaproxy/mediacontrol.py", line 130, in
> datagramReceived
> > media-relay[10719]: self.cb_func(host, port, data)
> > media-relay[10719]:   File
> "/usr/lib/pymodules/python2.5/mediaproxy/mediacontrol.py", line 226, in
> got_data
> > media-relay[10719]: self.substream.send_data(self, data, is_stun)
> > media-relay[10719]:   File
> "/usr/lib/pymodules/python2.5/mediaproxy/mediacontrol.py", line 311, in
> send_data
> > media-relay[10719]: dest.listener.protocol.send(data, is_stun)
> > media-relay[10719]:   File
> "/usr/lib/pymodules/python2.5/mediaproxy/mediacontrol.py", line 159, in send
> > media-relay[10719]: self.transport.write(data, (ip, port))
> > media-relay[10719]:   File
> "/usr/lib/python2.5/site-packages/twisted/internet/udp.py", line 155, in
> write
> > media-relay[10719]: return self.socket.sendto(datagram, addr)
> > media-relay[10719]: error: (1, 'Operation not permitted')
> >
> > There doesn't seem to be any pattern.  Nor do there seem to be any
> complaints.
> >
> > Today we had it happen about 10 times, far more than the logs indicate
> is normal.  Then we had many lines of this:
> >
> > media-relay[10719]: error: Could not reserve relay ports for session,
> all allocated ports are being used
> >
>
> What port range are you using? Any chance they were all exhausted?
>
> > Then a few instances of:
> >
> > media-relay[10719]:   File
> "/usr/lib/pymodules/python2.5/mediaproxy/relay.py", line 175, in
> lineReceived
> > media-relay[10719]: response =
> self.factory.parent.got_command(self.factory.host, self.command,
> self.headers)
> > media-relay[10719]:   File
> "/usr/lib/pymodules/python2.5/mediaproxy/relay.py", line 387, in got_command
> > media-relay[10719]: local_media =
> self.session_manager.update_session(dispatcher, **headers)
> > media-relay[10719]:   File
> "/usr/lib/pymodules/python2.5/mediaproxy/mediacontrol.py", line 754, in
> update_session
> > media-relay[10719]: session.update_media(cseq, to_tag, user_agent,
> media, is_downstream, is_caller_cseq)
> > media-relay[10719]:   File
> "/usr/lib/pymodules/python2.5/mediaproxy/mediacontrol.py", line 566, in
> update_media
> > media-relay[10719]: raise ValueError('Media types do not match: "%s"
> and "%s"' % (stream.media_type, media_type))
> > media-relay[10719]: ValueError: Media types do not match: "audio" and
> “image”
> >
>
> Hum, this could be a bug. Maybe some weird fax device? A SIP trace of such
> calls would be nice.
>
> > Followed by lots (and LOTS) of these with various port combinations:
> >
> > media-relay[10719]: warning: Cannot use port pair 28836/28837
> >
>
> It’s possible that due to the previous exception ports are not deallocated
> so they kept piling up until the range was exhausted.
>
> > This happened on two relays at the same time.  The dispatchers lost
> connectivity with the relays, and I had to kill -9 the relays to shake them
> loose.  Upon a relay restart all seems normal.
> >
> > Even though old, this media relay configuration has been rock solid for
> years.  Today, not so much.  I'm wondering if this is a known bug that
> hasn't bitten us until today?  Or, something else?
> >
> > They are scheduled for replacement with more current software, but until
> then, I'd like to learn what I can.
> >
>
> I browsed through the MediaProxy changelogs just in case memory was not
> serving well, and I don’t see anything related to this problem. At a first
> glance it looks like an issue potentially caus

Re: [OpenSIPS-Users] Mediaproxy relay oddness

[Saúl Ibarra Corretgé]

Hi Jeff,

On 21 Jul 2014, at 21:55, Jeff Pyle  wrote:

> Hello,
> 
> This is on Opensips 1.6 with Mediaproxy 2.4.4.  Yeah, they're old.  I know.
> 
> We see this from time to time:
> 
> media-relay[10719]: Traceback (most recent call last):
> media-relay[10719]:   File 
> "/usr/lib/python2.5/site-packages/twisted/internet/udp.py", line 126, in 
> doRead
> media-relay[10719]: self.protocol.datagramReceived(data, addr)
> media-relay[10719]:   File 
> "/usr/lib/pymodules/python2.5/mediaproxy/mediacontrol.py", line 130, in 
> datagramReceived
> media-relay[10719]: self.cb_func(host, port, data)
> media-relay[10719]:   File 
> "/usr/lib/pymodules/python2.5/mediaproxy/mediacontrol.py", line 226, in 
> got_data
> media-relay[10719]: self.substream.send_data(self, data, is_stun)
> media-relay[10719]:   File 
> "/usr/lib/pymodules/python2.5/mediaproxy/mediacontrol.py", line 311, in 
> send_data
> media-relay[10719]: dest.listener.protocol.send(data, is_stun)
> media-relay[10719]:   File 
> "/usr/lib/pymodules/python2.5/mediaproxy/mediacontrol.py", line 159, in send
> media-relay[10719]: self.transport.write(data, (ip, port))
> media-relay[10719]:   File 
> "/usr/lib/python2.5/site-packages/twisted/internet/udp.py", line 155, in write
> media-relay[10719]: return self.socket.sendto(datagram, addr)
> media-relay[10719]: error: (1, 'Operation not permitted')
> 
> There doesn't seem to be any pattern.  Nor do there seem to be any complaints.
> 
> Today we had it happen about 10 times, far more than the logs indicate is 
> normal.  Then we had many lines of this:
> 
> media-relay[10719]: error: Could not reserve relay ports for session, all 
> allocated ports are being used
> 

What port range are you using? Any chance they were all exhausted?

> Then a few instances of:
> 
> media-relay[10719]:   File 
> "/usr/lib/pymodules/python2.5/mediaproxy/relay.py", line 175, in lineReceived
> media-relay[10719]: response = 
> self.factory.parent.got_command(self.factory.host, self.command, self.headers)
> media-relay[10719]:   File 
> "/usr/lib/pymodules/python2.5/mediaproxy/relay.py", line 387, in got_command
> media-relay[10719]: local_media = 
> self.session_manager.update_session(dispatcher, **headers)
> media-relay[10719]:   File 
> "/usr/lib/pymodules/python2.5/mediaproxy/mediacontrol.py", line 754, in 
> update_session
> media-relay[10719]: session.update_media(cseq, to_tag, user_agent, media, 
> is_downstream, is_caller_cseq)
> media-relay[10719]:   File 
> "/usr/lib/pymodules/python2.5/mediaproxy/mediacontrol.py", line 566, in 
> update_media
> media-relay[10719]: raise ValueError('Media types do not match: "%s" and 
> "%s"' % (stream.media_type, media_type))
> media-relay[10719]: ValueError: Media types do not match: "audio" and “image”
> 

Hum, this could be a bug. Maybe some weird fax device? A SIP trace of such 
calls would be nice.

> Followed by lots (and LOTS) of these with various port combinations:
> 
> media-relay[10719]: warning: Cannot use port pair 28836/28837
> 

It’s possible that due to the previous exception ports are not deallocated so 
they kept piling up until the range was exhausted.

> This happened on two relays at the same time.  The dispatchers lost 
> connectivity with the relays, and I had to kill -9 the relays to shake them 
> loose.  Upon a relay restart all seems normal.
> 
> Even though old, this media relay configuration has been rock solid for 
> years.  Today, not so much.  I'm wondering if this is a known bug that hasn't 
> bitten us until today?  Or, something else?
> 
> They are scheduled for replacement with more current software, but until 
> then, I'd like to learn what I can.
> 

I browsed through the MediaProxy changelogs just in case memory was not serving 
well, and I don’t see anything related to this problem. At a first glance it 
looks like an issue potentially caused by a device that can do a=image, usually 
a fax. We do have some workarounds inplace for misbehaving fax devices, maybe 
there is one case we miss.


Regards,

--
Saúl Ibarra Corretgé
AG Projects





signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Mediaproxy relay oddness

[Jeff Pyle]

Hello,

This is on Opensips 1.6 with Mediaproxy 2.4.4.  Yeah, they're old.  I know.

We see this from time to time:

media-relay[10719]: Traceback (most recent call last):
media-relay[10719]:   File
"/usr/lib/python2.5/site-packages/twisted/internet/udp.py", line 126, in
doRead
media-relay[10719]: self.protocol.datagramReceived(data, addr)
media-relay[10719]:   File
"/usr/lib/pymodules/python2.5/mediaproxy/mediacontrol.py", line 130, in
datagramReceived
media-relay[10719]: self.cb_func(host, port, data)
media-relay[10719]:   File
"/usr/lib/pymodules/python2.5/mediaproxy/mediacontrol.py", line 226, in
got_data
media-relay[10719]: self.substream.send_data(self, data, is_stun)
media-relay[10719]:   File
"/usr/lib/pymodules/python2.5/mediaproxy/mediacontrol.py", line 311, in
send_data
media-relay[10719]: dest.listener.protocol.send(data, is_stun)
media-relay[10719]:   File
"/usr/lib/pymodules/python2.5/mediaproxy/mediacontrol.py", line 159, in send
media-relay[10719]: self.transport.write(data, (ip, port))
media-relay[10719]:   File
"/usr/lib/python2.5/site-packages/twisted/internet/udp.py", line 155, in
write
media-relay[10719]: return self.socket.sendto(datagram, addr)
media-relay[10719]: error: (1, 'Operation not permitted')


There doesn't seem to be any pattern.  Nor do there seem to be any
complaints.

Today we had it happen about 10 times, far more than the logs indicate is
normal.  Then we had many lines of this:

media-relay[10719]: error: Could not reserve relay ports for session, all
allocated ports are being used


Then a few instances of:

media-relay[10719]:   File
"/usr/lib/pymodules/python2.5/mediaproxy/relay.py", line 175, in
lineReceived
media-relay[10719]: response =
self.factory.parent.got_command(self.factory.host, self.command,
self.headers)
media-relay[10719]:   File
"/usr/lib/pymodules/python2.5/mediaproxy/relay.py", line 387, in got_command
media-relay[10719]: local_media =
self.session_manager.update_session(dispatcher, **headers)
media-relay[10719]:   File
"/usr/lib/pymodules/python2.5/mediaproxy/mediacontrol.py", line 754, in
update_session
media-relay[10719]: session.update_media(cseq, to_tag, user_agent,
media, is_downstream, is_caller_cseq)
media-relay[10719]:   File
"/usr/lib/pymodules/python2.5/mediaproxy/mediacontrol.py", line 566, in
update_media
media-relay[10719]: raise ValueError('Media types do not match: "%s"
and "%s"' % (stream.media_type, media_type))
media-relay[10719]: ValueError: Media types do not match: "audio" and
"image"


Followed by lots (and LOTS) of these with various port combinations:

media-relay[10719]: warning: Cannot use port pair 28836/28837


This happened on two relays at the same time.  The dispatchers lost
connectivity with the relays, and I had to kill -9 the relays to shake them
loose.  Upon a relay restart all seems normal.

Even though old, this media relay configuration has been rock solid for
years.  Today, not so much.  I'm wondering if this is a known bug that
hasn't bitten us until today?  Or, something else?

They are scheduled for replacement with more current software, but until
then, I'd like to learn what I can.



- Jeff
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] mediaproxy-relay: kernel version problem

[Dan Pascu]

On 6 Nov 2013, at 1:17, steph...@shimaore.net wrote:

> Hello,
> 
> I've been using mediaproxy for years without issues, but recently
> encountered a problem when upgrading kernel version on Debian.
> 
> In recent Debian versions, /proc/sys/kernel/osrelease
> (KERNEL_VERSION_FILE in media-relay) looks for example this way:
> 
>$ cat /proc/sys/kernel/osrelease 
>3.10-3-amd64

This is how it was forever. I have older machines with 2.6.x and they show up 
the same:

$ cat /proc/sys/kernel/osrelease
2.6.32-3-686

> which doesn't match the format expected by the script (and causes
> media-relay to fail at startup).

Actually this is the format the script expected since I remember it. Mediaproxy 
detects the kernel version fine both on older and newer debian systems as I do 
not see any difference in the format.

> 
> It seems odd that we would rely on the various distributions to gather
> the kernel version, when we could use /proc/sys/kernel/version
> 
>$ cat /proc/sys/kernel/version 
>#1 SMP Debian 3.10.11-1 (2013-09-10)

Unfortunately that is not the kernel version and the fact that in your case the 
kernel version is tucked in there is a matter of coincidence. I have 2 
machines, one with 2.6.x and one with 3.x that don't have it in there (both 
Debian BTW, so it seems that it is not present in there even if you use the 
same distribution):

machine1:~$ cat /proc/sys/kernel/osrelease
2.6.32-3-686
machine1:~$ cat /proc/sys/kernel/version
#1 SMP Thu Feb 25 06:14:20 UTC 2010

machine2:~$ cat /proc/sys/kernel/osrelease
3.2.0-0.bpo.2-686-pae
machine2:~$ cat /proc/sys/kernel/version
#1 SMP Sun Jun 3 22:21:19 UTC 2012

Also, while something resembling the kernel version seems to be there, it 
doesn't match the actual kernel version (this is from another Debian system):

machine3:~$ cat /proc/sys/kernel/osrelease
3.10-3-686-pae
machine3:~$ cat /proc/sys/kernel/version
#1 SMP Debian 3.10.11-1 (2013-09-10)
machine3:~$ uname -r
3.10-3-686-pae

As you can see, the file has 3.10.11-1 tucked in there, but the actual kernel 
version is 3.10-3 (as reported by both the osrelease file and uname -r). 

So we can conclude that /proc/sys/kernel/version is pretty much useless in 
determining the kernel version.

> which I assume contains the proper value

Not even (see the last example above).

> (although maybe in a
> not-so-stable format).
> 
> I'm proposing the changes described here
>  https://gist.github.com/shimaore/7328080
> (which first try to use the current method, then fallback to using
> kernel/version) for consideration & integration by AG Projects.

By looking at your patch, I believe I have an idea why it doesn't work for you. 
Are you using stock mediaproxy version 2.5.2? Because your patch suggests 
otherwise. This change, proposed by the patch:

 try:
-major, minor, revision = [int(num) for num in 
open(KERNEL_VERSION_FILE).read().split(" ", 1)[3].split(".")[:3]]
+major, minor, revision = [int(num) for num in 
open(OS_RELEASE_FILE).read().split("-", 1)[0].split(".")[:3]]
 except:

indicates that you try to replace this line from the original version:

major, minor, revision = [int(num) for num in 
open(KERNEL_VERSION_FILE).read().split(" ", 1)[3].split(".")[:3]]

however that line is not present in that form in stock mediaproxy-2.5.2. The 
actual line in our version is:

major, minor, revision = [int(num) for num in 
open(KERNEL_VERSION_FILE).read().split("-", 1)[0].split(".")[:3]]

which is exactly what you try to change it to.

So if the source you try to change looks like in your patch, there is no wonder 
it doesn't work as that form cannot parse the output from osrelease.

So I suggest you try out stock mediaproxy 2.5.2 without any alterations or use 
the latest version from the darcs repository and see if the problem persists. 
If it does, please post the output from the osrelease file and the backtrace so 
we can take a look at what's different. Currently I'm running the latest kernel 
from debian unstable and nothing has changed in the format of that file.

--
Dan





___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] mediaproxy-relay: kernel version problem

[Saúl Ibarra Corretgé]

Changes look ok, I'm traveling right now, but I'll have a look soon.

On Nov 6, 2013, at 12:17 AM, steph...@shimaore.net wrote:

> Hello,
> 
> I've been using mediaproxy for years without issues, but recently
> encountered a problem when upgrading kernel version on Debian.
> 
> In recent Debian versions, /proc/sys/kernel/osrelease
> (KERNEL_VERSION_FILE in media-relay) looks for example this way:
> 
>$ cat /proc/sys/kernel/osrelease 
>3.10-3-amd64
> 
> which doesn't match the format expected by the script (and causes
> media-relay to fail at startup).
> 
> It seems odd that we would rely on the various distributions to gather
> the kernel version, when we could use /proc/sys/kernel/version
> 
>$ cat /proc/sys/kernel/version 
>#1 SMP Debian 3.10.11-1 (2013-09-10)
> 
> which I assume contains the proper value (although maybe in a
> not-so-stable format).
> 
> I'm proposing the changes described here
>  https://gist.github.com/shimaore/7328080
> (which first try to use the current method, then fallback to using
> kernel/version) for consideration & integration by AG Projects.
> 
> S.
> 
> -- 
> Stéphane Alnet -- Telecom Artisan. OpenSource Advocate.
> Development and integration for FreeSwitch, OpenSIPS, CouchDB, Node.js.
> Mobile: +33643482771 - http://shimaore.net/ - https://github.com/shimaore/
> 
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

--
Saúl Ibarra Corretgé
AG Projects




___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] mediaproxy-relay: kernel version problem

[stephane]

Hello,

I've been using mediaproxy for years without issues, but recently
encountered a problem when upgrading kernel version on Debian.

In recent Debian versions, /proc/sys/kernel/osrelease
(KERNEL_VERSION_FILE in media-relay) looks for example this way:

$ cat /proc/sys/kernel/osrelease 
3.10-3-amd64

which doesn't match the format expected by the script (and causes
media-relay to fail at startup).

It seems odd that we would rely on the various distributions to gather
the kernel version, when we could use /proc/sys/kernel/version

$ cat /proc/sys/kernel/version 
#1 SMP Debian 3.10.11-1 (2013-09-10)

which I assume contains the proper value (although maybe in a
not-so-stable format).

I'm proposing the changes described here
  https://gist.github.com/shimaore/7328080
(which first try to use the current method, then fallback to using
kernel/version) for consideration & integration by AG Projects.

S.

-- 
Stéphane Alnet -- Telecom Artisan. OpenSource Advocate.
Development and integration for FreeSwitch, OpenSIPS, CouchDB, Node.js.
Mobile: +33643482771 - http://shimaore.net/ - https://github.com/shimaore/

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Mediaproxy relay on CentOS 6 VPS

[Saúl Ibarra Corretgé]

You are missing some iptables kernel module. Sometimes VPS providers use a 
monolithic kernel and disable things. You should be able to install a standard 
kernel from your distro's repositories.

On May 22, 2013, at 11:14 AM, John Quick wrote:

> Hi Muhammad,
> 
> The (edited) results for those commands you suggested running are as follows:
> processor   : 0
> vendor_id   : AuthenticAMD
> cpu family  : 16
> model   : 2
> model name  : Quad-Core AMD Opteron(tm) Processor 2352
> stepping: 3
> cpu MHz : 1050.000
> etc.
>  
> CentOS release 6.4 (Final)
> Kernel \r on an \m
>  
> Linux s123456.onlinehome-server.info 2.6.32-042stab076.8 #1 SMP Tue May 14 
> 20:38:14 MSK 2013 x86_64 x86_64 x86_64 GNU/Linux
>  
> Also, just to confirm about iptables, here is the edited output from “yum 
> info iptables iptables-devel”:
> Installed Packages
> Name: iptables
> Arch: x86_64
> Version : 1.4.7
> Release : 9.el6
>  
> Name: iptables-devel
> Arch: x86_64
> Version : 1.4.7
> Release : 9.el6
>  
> John
>  
> From: Muhammad Shahzad [mailto:shaherya...@gmail.com] 
> Sent: 20 May 2013 17:49
> To: John Q
> Cc: OpenSIPS users mailling list
> Subject: Re: [OpenSIPS-Users] Mediaproxy relay on CentOS 6 VPS
>  
> Humm, strange i never had to do that. If you can check which VMS you have, 
> may be i can get it tested in local data center. Following three commands may 
> give you some idea,
>  
> cat /proc/cpuinfo
> cat /etc/issue
> uname -a
>  
> OR you can always fallback to Debian. :-)
>  
> Thank you.
>  
>  
>  
> 
> On Mon, May 20, 2013 at 6:45 PM, John Quick  wrote:
> Muhammed,
> 
> Thanks for responding so quickly. I already have iptables-devel package 
> installed, but I used yum to install it.
> I did some research the last time it happened and think it concerns Linux 
> loadable modules and options that may require a re-build of the kernel.
> On that occasion, I chickened out and changed to Ubuntu.
> 
> John
>  
> From: Muhammad Shahzad [mailto:shaherya...@gmail.com] 
> Sent: 20 May 2013 17:37
> To: John Q; OpenSIPS users mailling list
> Subject: Re: [OpenSIPS-Users] Mediaproxy relay on CentOS 6 VPS
>  
> I think you need to install iptables-devel package.
>  
> http://rpm.pbone.net/index.php3?stat=3&search=iptables-devel&srodzaj=3
>  
> Thank you.
>  
>  
> 
> On Mon, May 20, 2013 at 5:56 PM, John Quick  wrote:
> On two different Virtual Private Servers running CentOS 6 I have hit the
> same problem.
> It is that when I try to start mediaproxy relay, it errors with:
> FATAL: Module ip_tables not found.
> 
> Unfortunately, as it is a third party VPS, I do not know what virtualization
> environment is being used.
> Does anyone know how to debug this problem (before I re-image it with
> Debian/Ubuntu)?
> 
> Mediaproxy version is 2.5.2 and I used my own instructions as outlined at
> http://kb.smartvox.co.uk/opensips/install-mediaproxy-centos-6/
> The same procedure has worked fine on many other servers running CentOS 6.
> 
> John Quick
> Smartvox Limited
> Web: www.smartvox.co.uk
> 
> 
> 
> 
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> 
> 
>  
> --
> Mit freundlichen Grüßen
> Muhammad Shahzad
> ---
> CISCO Rich Media Communication Specialist (CRMCS)
> CISCO Certified Network Associate (CCNA)
> Cell: +49 176 99 83 10 85
> MSN: shari_78...@hotmail.com
> Email: shaherya...@googlemail.com
> 
> 
>  
> --
> Mit freundlichen Grüßen
> Muhammad Shahzad
> ---
> CISCO Rich Media Communication Specialist (CRMCS)
> CISCO Certified Network Associate (CCNA)
> Cell: +49 176 99 83 10 85
> MSN: shari_78...@hotmail.com
> Email: shaherya...@googlemail.com
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

--
Saúl Ibarra Corretgé
AG Projects




___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Mediaproxy relay on CentOS 6 VPS

[John Quick]

Hi Muhammad,


The (edited) results for those commands you suggested running are as follows:

processor   : 0

vendor_id   : AuthenticAMD

cpu family  : 16

model   : 2

model name  : Quad-Core AMD Opteron(tm) Processor 2352

stepping: 3

cpu MHz : 1050.000

etc.

 

CentOS release 6.4 (Final)

Kernel \r on an \m

 

Linux s123456.onlinehome-server.info 2.6.32-042stab076.8 #1 SMP Tue May 14 
20:38:14 MSK 2013 x86_64 x86_64 x86_64 GNU/Linux

 

Also, just to confirm about iptables, here is the edited output from “yum info 
iptables iptables-devel”:

Installed Packages

Name: iptables

Arch: x86_64

Version : 1.4.7

Release : 9.el6

 

Name: iptables-devel

Arch: x86_64

Version : 1.4.7

Release : 9.el6

 

John

 

From: Muhammad Shahzad [mailto:shaherya...@gmail.com] 
Sent: 20 May 2013 17:49
To: John Q
Cc: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Mediaproxy relay on CentOS 6 VPS

 

Humm, strange i never had to do that. If you can check which VMS you have, may 
be i can get it tested in local data center. Following three commands may give 
you some idea,

 

cat /proc/cpuinfo

cat /etc/issue

uname -a

 

OR you can always fallback to Debian. :-)

 

Thank you.

 

 

 

On Mon, May 20, 2013 at 6:45 PM, John Quick  wrote:

Muhammed,


Thanks for responding so quickly. I already have iptables-devel package 
installed, but I used yum to install it.

I did some research the last time it happened and think it concerns Linux 
loadable modules and options that may require a re-build of the kernel.

On that occasion, I chickened out and changed to Ubuntu.

John

 

From: Muhammad Shahzad [mailto:shaherya...@gmail.com] 
Sent: 20 May 2013 17:37
To: John Q; OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Mediaproxy relay on CentOS 6 VPS

 

I think you need to install iptables-devel package.

 

http://rpm.pbone.net/index.php3?stat=3 
<http://rpm.pbone.net/index.php3?stat=3&search=iptables-devel&srodzaj=3> 
&search=iptables-devel&srodzaj=3

 

Thank you.

 

 

On Mon, May 20, 2013 at 5:56 PM, John Quick  wrote:

On two different Virtual Private Servers running CentOS 6 I have hit the
same problem.
It is that when I try to start mediaproxy relay, it errors with:
FATAL: Module ip_tables not found.

Unfortunately, as it is a third party VPS, I do not know what virtualization
environment is being used.
Does anyone know how to debug this problem (before I re-image it with
Debian/Ubuntu)?

Mediaproxy version is 2.5.2 and I used my own instructions as outlined at
http://kb.smartvox.co.uk/opensips/install-mediaproxy-centos-6/
The same procedure has worked fine on many other servers running CentOS 6.

John Quick
Smartvox Limited
Web: www.smartvox.co.uk




___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users





 

-- 

Mit freundlichen Grüßen

Muhammad Shahzad
---
CISCO Rich Media Communication Specialist (CRMCS)
CISCO Certified Network Associate (CCNA)
Cell: +49 176 99 83 10 85
MSN:  <mailto:shari_78...@hotmail.com> shari_78...@hotmail.com
Email:  <mailto:shaherya...@googlemail.com> shaherya...@googlemail.com 





 

-- 

Mit freundlichen Grüßen

Muhammad Shahzad
---
CISCO Rich Media Communication Specialist (CRMCS)
CISCO Certified Network Associate (CCNA)
Cell: +49 176 99 83 10 85
MSN:  <mailto:shari_78...@hotmail.com> shari_78...@hotmail.com
Email:  <mailto:shaherya...@googlemail.com> shaherya...@googlemail.com 

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Mediaproxy relay on CentOS 6 VPS

[Muhammad Shahzad]

Humm, strange i never had to do that. If you can check which VMS you have,
may be i can get it tested in local data center. Following three commands
may give you some idea,

cat /proc/cpuinfo
cat /etc/issue
uname -a

OR you can always fallback to Debian. :-)

Thank you.




On Mon, May 20, 2013 at 6:45 PM, John Quick wrote:

> Muhammed,
>
>
> Thanks for responding so quickly. I already have iptables-devel package
> installed, but I used yum to install it.
>
> I did some research the last time it happened and think it concerns Linux
> loadable modules and options that may require a re-build of the kernel.***
> *
>
> On that occasion, I chickened out and changed to Ubuntu.
>
> 
>
> John
>
> ** **
>
> *From:* Muhammad Shahzad [mailto:shaherya...@gmail.com]
> *Sent:* 20 May 2013 17:37
> *To:* John Q; OpenSIPS users mailling list
> *Subject:* Re: [OpenSIPS-Users] Mediaproxy relay on CentOS 6 VPS
>
> ** **
>
> I think you need to install iptables-devel package.
>
> ** **
>
> http://rpm.pbone.net/index.php3?stat=3&search=iptables-devel&srodzaj=3
>
> ** **
>
> Thank you.
>
> ** **
>
> ** **
>
> On Mon, May 20, 2013 at 5:56 PM, John Quick 
> wrote:
>
> On two different Virtual Private Servers running CentOS 6 I have hit the
> same problem.
> It is that when I try to start mediaproxy relay, it errors with:
> FATAL: Module ip_tables not found.
>
> Unfortunately, as it is a third party VPS, I do not know what
> virtualization
> environment is being used.
> Does anyone know how to debug this problem (before I re-image it with
> Debian/Ubuntu)?
>
> Mediaproxy version is 2.5.2 and I used my own instructions as outlined at
> http://kb.smartvox.co.uk/opensips/install-mediaproxy-centos-6/
> The same procedure has worked fine on many other servers running CentOS 6.
>
> John Quick
> Smartvox Limited
> Web: www.smartvox.co.uk
>
>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
> 
>
> ** **
>
> -- 
>
> Mit freundlichen Grüßen
>
> Muhammad Shahzad
> ---
> CISCO Rich Media Communication Specialist (CRMCS)
> CISCO Certified Network Associate (CCNA)
> Cell: +49 176 99 83 10 85
> MSN: shari_78...@hotmail.com
> Email: shaherya...@googlemail.com 
>



-- 
Mit freundlichen Grüßen
Muhammad Shahzad
---
CISCO Rich Media Communication Specialist (CRMCS)
CISCO Certified Network Associate (CCNA)
Cell: +49 176 99 83 10 85
MSN: shari_78...@hotmail.com
Email: shaherya...@googlemail.com
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Mediaproxy relay on CentOS 6 VPS

[John Quick]

Muhammed,


Thanks for responding so quickly. I already have iptables-devel package 
installed, but I used yum to install it.

I did some research the last time it happened and think it concerns Linux 
loadable modules and options that may require a re-build of the kernel.

On that occasion, I chickened out and changed to Ubuntu.



John

 

From: Muhammad Shahzad [mailto:shaherya...@gmail.com] 
Sent: 20 May 2013 17:37
To: John Q; OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Mediaproxy relay on CentOS 6 VPS

 

I think you need to install iptables-devel package.

 

http://rpm.pbone.net/index.php3?stat=3 
<http://rpm.pbone.net/index.php3?stat=3&search=iptables-devel&srodzaj=3> 
&search=iptables-devel&srodzaj=3

 

Thank you.

 

 

On Mon, May 20, 2013 at 5:56 PM, John Quick  wrote:

On two different Virtual Private Servers running CentOS 6 I have hit the
same problem.
It is that when I try to start mediaproxy relay, it errors with:
FATAL: Module ip_tables not found.

Unfortunately, as it is a third party VPS, I do not know what virtualization
environment is being used.
Does anyone know how to debug this problem (before I re-image it with
Debian/Ubuntu)?

Mediaproxy version is 2.5.2 and I used my own instructions as outlined at
http://kb.smartvox.co.uk/opensips/install-mediaproxy-centos-6/
The same procedure has worked fine on many other servers running CentOS 6.

John Quick
Smartvox Limited
Web: www.smartvox.co.uk




___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users





 

-- 

Mit freundlichen Grüßen

Muhammad Shahzad
---
CISCO Rich Media Communication Specialist (CRMCS)
CISCO Certified Network Associate (CCNA)
Cell: +49 176 99 83 10 85
MSN:  <mailto:shari_78...@hotmail.com> shari_78...@hotmail.com
Email:  <mailto:shaherya...@googlemail.com> shaherya...@googlemail.com 

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Mediaproxy relay on CentOS 6 VPS

[Muhammad Shahzad]

I think you need to install iptables-devel package.

http://rpm.pbone.net/index.php3?stat=3&search=iptables-devel&srodzaj=3

Thank you.



On Mon, May 20, 2013 at 5:56 PM, John Quick wrote:

> On two different Virtual Private Servers running CentOS 6 I have hit the
> same problem.
> It is that when I try to start mediaproxy relay, it errors with:
> FATAL: Module ip_tables not found.
>
> Unfortunately, as it is a third party VPS, I do not know what
> virtualization
> environment is being used.
> Does anyone know how to debug this problem (before I re-image it with
> Debian/Ubuntu)?
>
> Mediaproxy version is 2.5.2 and I used my own instructions as outlined at
> http://kb.smartvox.co.uk/opensips/install-mediaproxy-centos-6/
> The same procedure has worked fine on many other servers running CentOS 6.
>
> John Quick
> Smartvox Limited
> Web: www.smartvox.co.uk
>
>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>



-- 
Mit freundlichen Grüßen
Muhammad Shahzad
---
CISCO Rich Media Communication Specialist (CRMCS)
CISCO Certified Network Associate (CCNA)
Cell: +49 176 99 83 10 85
MSN: shari_78...@hotmail.com
Email: shaherya...@googlemail.com
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Mediaproxy relay on CentOS 6 VPS

[John Quick]

On two different Virtual Private Servers running CentOS 6 I have hit the
same problem.
It is that when I try to start mediaproxy relay, it errors with:
FATAL: Module ip_tables not found.

Unfortunately, as it is a third party VPS, I do not know what virtualization
environment is being used.
Does anyone know how to debug this problem (before I re-image it with
Debian/Ubuntu)?

Mediaproxy version is 2.5.2 and I used my own instructions as outlined at 
http://kb.smartvox.co.uk/opensips/install-mediaproxy-centos-6/
The same procedure has worked fine on many other servers running CentOS 6.

John Quick
Smartvox Limited
Web: www.smartvox.co.uk




___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Mediaproxy relay error

[Saúl Ibarra Corretgé]

Hi,

On 16/12/09 2:47 PM, Darshak Modi wrote:
> #
> ./media-relay --no-fork
> Starting MediaProxy Relay 2.3.8
> fatal error: failed to create MediaProxy Relay: cannot import name
> _conntrack
> Traceback (most recent call last):
> ---  ---
>File "./media-relay", line 61, in ?
>  from mediaproxy.relay import MediaRelay
>File "/usr/local/src/mediaproxy/mediaproxy-2.3.8/mediaproxy/relay.py",
> line 37, in ?
>  from mediaproxy.mediacontrol import SessionManager,
> RelayPortsExhaustedError
>File
> "/usr/local/src/mediaproxy/mediaproxy-2.3.8/mediaproxy/mediacontrol.py",
> line 23, in ?
>  from mediaproxy.interfaces.system import _conntrack
> exceptions.ImportError: cannot import name _conntrack
>
>
> I DID THIS
> #locate conntrack.so
> /home/darshak/Sources/mediaproxy-2.3.8/build/lib.linux-i686-2.4/mediaproxy/i
> nterfaces/system/_conntrack.so
> /lib/iptables/libipt_conntrack.so
> /usr/lib/libnetfilter_conntrack.so
> /usr/lib/libnetfilter_conntrack.so.1
> /usr/lib/libnetfilter_conntrack.so.1.2.0
> /usr/lib/python2.4/site-packages/mediaproxy/interfaces/system/_conntrack.so
> /usr/local/src/mediaproxy/mediaproxy-2.3.8/build/lib.linux-i686-2.4/mediapro
> xy/interfaces/system/_conntrack.so
>
>
> The so is there.
>
> python -c "import sys; print sys.path"
> ['', '/usr/lib/python24.zip', '/usr/lib/python2.4',
> '/usr/lib/python2.4/plat-linux2', '/usr/lib/python2.4/lib-tk',
> '/usr/lib/python2.4/lib-dynload', '/usr/lib/python2.4/site-packages',
> '/usr/lib/python2.4/site-packages/Numeric',
> '/usr/lib/python2.4/site-packages/gtk-2.0']
>
> Please guide what to do next
>

Where are you running MediaProxy from? I assume you are running it from 
the directory you downloaded it, so did you build it with ./build_inplace?


Regards,


-- 
Saúl Ibarra Corretgé
AG Projects

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Mediaproxy relay error

[Darshak Modi]

#
./media-relay --no-fork
Starting MediaProxy Relay 2.3.8
fatal error: failed to create MediaProxy Relay: cannot import name
_conntrack
Traceback (most recent call last):
---  ---
  File "./media-relay", line 61, in ?
from mediaproxy.relay import MediaRelay
  File "/usr/local/src/mediaproxy/mediaproxy-2.3.8/mediaproxy/relay.py",
line 37, in ?
from mediaproxy.mediacontrol import SessionManager,
RelayPortsExhaustedError
  File
"/usr/local/src/mediaproxy/mediaproxy-2.3.8/mediaproxy/mediacontrol.py",
line 23, in ?
from mediaproxy.interfaces.system import _conntrack
exceptions.ImportError: cannot import name _conntrack


I DID THIS
#locate conntrack.so
/home/darshak/Sources/mediaproxy-2.3.8/build/lib.linux-i686-2.4/mediaproxy/i
nterfaces/system/_conntrack.so
/lib/iptables/libipt_conntrack.so
/usr/lib/libnetfilter_conntrack.so
/usr/lib/libnetfilter_conntrack.so.1
/usr/lib/libnetfilter_conntrack.so.1.2.0
/usr/lib/python2.4/site-packages/mediaproxy/interfaces/system/_conntrack.so
/usr/local/src/mediaproxy/mediaproxy-2.3.8/build/lib.linux-i686-2.4/mediapro
xy/interfaces/system/_conntrack.so


The so is there.

python -c "import sys; print sys.path"
['', '/usr/lib/python24.zip', '/usr/lib/python2.4',
'/usr/lib/python2.4/plat-linux2', '/usr/lib/python2.4/lib-tk',
'/usr/lib/python2.4/lib-dynload', '/usr/lib/python2.4/site-packages',
'/usr/lib/python2.4/site-packages/Numeric',
'/usr/lib/python2.4/site-packages/gtk-2.0']

Please guide what to do next


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] mediaproxy relay on none default route interface failed

[Iñaki Baz Castillo]

El Jueves, 10 de Septiembre de 2009, Dan Pascu escribió:
> > That's not true, you could run as many Realys as you want on the  
> > same server,
> > only have to patch mediaproxy-relay to be able to call it with a
> > diferent .cfg as the default one, have diferent listen ports and no  
> > more.
> 
> You don't need to patch anything. Just unpack mediaproxy in as many  
> different directories as you need, run ./build_inplace and modify each  
> config.ini in those directories as needed. Then run mediaproxy from  
> those directories and each of them will use the local config.ini from  
> its own directory.

Is this really preferable to a single and so common "-c CONFIG_FILE" 
commandline option?

A "-c" option would break nothing since the absence of it means "default 
config file". Also a "-c" option allows deb usual installation and upgrade 
(the only requeriment would be create N init scripts having each one a 
different "-c" config file and PID file).

Perhaps you suggest the above solution as a feasible workaround without 
patching the code. I expect it because I cannot imagine how managing N full 
installations of N mediaproxies can be better than a simple "-c" option 
involving a single installation of the software.

Of course this is just my opinion. Take is as a suggestion and not as a 
demand.

Regards.

-- 
Iñaki Baz Castillo 

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] mediaproxy relay on none default route interface failed

[Raúl Alexis Betancor Santana]

On Thursday 10 September 2009 22:25:39 Dan Pascu wrote:
> On 10 Sep 2009, at 18:00, Raúl Alexis Betancor Santana wrote:
> > So ... "killing flies with bazookas" ...
> > So ... when having to update, need to update n instances, instead of
> > only
> > one ..
> > So ... wasting hard disk (I know it's cheap ... but wasting
> > anyway) ...
>
> I'm pretty sure you felt smart and clever while wording your indignant
> reply. Indeed, you absolutely had to put me into my rightful place and
> I deserved every dot and comma in it. What was in my mind trying to
> suggest some alternatives that work with the software as it is and do
> not require patching or a new version? But for a strange reason I
> cannot pinpoint, I do not feel motivated by your rhetoric. No sir.
> Shamefully I must admit that it made me think that I can spend my time
> better elsewhere. Imagine that good sir. I'm so ashamed. It also made
> me have unclean thoughts about you. It made me think that maybe you
> have a size problem and you're compensating. Can you imagine that? So,
> good sir, maybe you should fire more of your aggressive indignation
> towards me to break this unclean thinking in my mind and finally make
> me see the light. Forget about asking nicely or, God forbid,
> contributing back. That's for pussies and it only weakens one's
> character.

Every time we have "talked" about this ... you always react the same ... as If 
I was fighting against you ... I don't know from where you get that feeling 
from my words.

I'm only expressing my opinion, your are free to ignore it if you don't like 
it.

Yes you gave a solucion and I arge that a better solucion (and from a desing 
point of view and from the KISS principles, easier) it's so simple add a -c 
config param.
Do you want the patch? ... they are just 4 lines, I did it for 2.3.4 version 
of mediaproxy, also for callcontrol and other very good software you have 
developed but that lacks THAT SIMPLE option, to be able to set the config 
file to use from the command line ... as 99% of other software allow you.

> > I still think that a simple param like -c configfile is better.
>
> That may be, but I made a principle of not helping people that hate me
> or abuse me verbally. 

I don't think I have abused you ... if you think soo it's your problem. I only 
express my opinion and comment other possible solutions.

> Besides, free in "free software" doesn't stand 
> for let's use that software that is free of charge and then feel free
> to abuse the developer. It stands for fell free to improve it and
> contribute back. Wait, scratch that. From you I wouldn't even want
> patches. The contribution you made is already more than enough...

Dan, sincerily .. you don't like to hear opinions that are agains yours ... 
and that's not good.
If you don't want my patches, you are free to ignore them. Not always a patch 
is needed to improve a software or to contribute to it, most of time another 
point of view about a problem it's enought.

-- 
Raúl Alexis Betancor Santana
Dimensión Virtual

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] mediaproxy relay on none default route interface failed

[Dan Pascu]

On 10 Sep 2009, at 18:00, Raúl Alexis Betancor Santana wrote:

> So ... "killing flies with bazookas" ...
> So ... when having to update, need to update n instances, instead of  
> only
> one ..
> So ... wasting hard disk (I know it's cheap ... but wasting  
> anyway) ...

I'm pretty sure you felt smart and clever while wording your indignant  
reply. Indeed, you absolutely had to put me into my rightful place and  
I deserved every dot and comma in it. What was in my mind trying to  
suggest some alternatives that work with the software as it is and do  
not require patching or a new version? But for a strange reason I  
cannot pinpoint, I do not feel motivated by your rhetoric. No sir.  
Shamefully I must admit that it made me think that I can spend my time  
better elsewhere. Imagine that good sir. I'm so ashamed. It also made  
me have unclean thoughts about you. It made me think that maybe you  
have a size problem and you're compensating. Can you imagine that? So,  
good sir, maybe you should fire more of your aggressive indignation  
towards me to break this unclean thinking in my mind and finally make  
me see the light. Forget about asking nicely or, God forbid,  
contributing back. That's for pussies and it only weakens one's  
character.

> I still think that a simple param like -c configfile is better.

That may be, but I made a principle of not helping people that hate me  
or abuse me verbally. Besides, free in "free software" doesn't stand  
for let's use that software that is free of charge and then feel free  
to abuse the developer. It stands for fell free to improve it and  
contribute back. Wait, scratch that. From you I wouldn't even want  
patches. The contribution you made is already more than enough...

--
Dan




___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] mediaproxy relay on none default route interface failed

[Ghaith ALKAYYEM]

Does the dispatcher work on the same machine also?
Could you provide me with more details about running these two
instances?

Regards.

On Thu, 2009-09-10 at 23:39 +0800, Jiang Jinke wrote:
> Thanks for the detail instruction.
> I just use a symlink into the directory, it's working properly now.
> 
> Just like below:
> /usr/local/relay1/media-relay   -> /usr/bin/media-relay
> /usr/local/relay2/media-relay   -> /usr/bin/media-relay
> 
> Regards,
> Jinke Jiang
> 
> On Thu, Sep 10, 2009 at 10:02 PM, Dan Pascu  wrote:
> >
> > On 10 Sep 2009, at 15:47, Raúl Alexis Betancor Santana wrote:
> >
> >> On Thursday 10 September 2009 11:56:00 Ghaith ALKAYYEM wrote:
> >>> Hello,
> >>>
> >>> I think it's not possible to use two separate relays on the same
> >>> server,
> >>> I tried that a lot then I switched to RTPproxy.
> >>
> >> That's not true, you could run as many Realys as you want on the
> >> same server,
> >> only have to patch mediaproxy-relay to be able to call it with a
> >> diferent .cfg as the default one, have diferent listen ports and no
> >> more.
> >
> > You don't need to patch anything. Just unpack mediaproxy in as many
> > different directories as you need, run ./build_inplace and modify each
> > config.ini in those directories as needed. Then run mediaproxy from
> > those directories and each of them will use the local config.ini from
> > its own directory.
> >
> > Alternatively, if you want to use a system wide installation, you can
> > copy the binaries from /usr/bin to a number of different directories
> > and add a config.ini in each directory. Then run those binaries from
> > those directories instead of /usr/bin/ and each binary will use the
> > config.ini file in its own directory to overwrite settings from the
> > global /etc/mediaproxy/config.ini.
> >
> > Mediaproxy uses 2 configuration files. The global one resides in /etc/
> > mediaproxy/config.ini. On top of that if a config.ini is present in
> > the same directory as the binary (media-relay & media-dispatcher) that
> > one will be used to overwrite the settings from the global one having
> > priority over it.
> >
> > --
> > Dan
> >
> >
> >
> >
> > ___
> > Users mailing list
> > Users@lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
> 
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] mediaproxy relay on none default route interface failed

[Jiang Jinke]

Thanks for the detail instruction.
I just use a symlink into the directory, it's working properly now.

Just like below:
/usr/local/relay1/media-relay   -> /usr/bin/media-relay
/usr/local/relay2/media-relay   -> /usr/bin/media-relay

Regards,
Jinke Jiang

On Thu, Sep 10, 2009 at 10:02 PM, Dan Pascu  wrote:
>
> On 10 Sep 2009, at 15:47, Raúl Alexis Betancor Santana wrote:
>
>> On Thursday 10 September 2009 11:56:00 Ghaith ALKAYYEM wrote:
>>> Hello,
>>>
>>> I think it's not possible to use two separate relays on the same
>>> server,
>>> I tried that a lot then I switched to RTPproxy.
>>
>> That's not true, you could run as many Realys as you want on the
>> same server,
>> only have to patch mediaproxy-relay to be able to call it with a
>> diferent .cfg as the default one, have diferent listen ports and no
>> more.
>
> You don't need to patch anything. Just unpack mediaproxy in as many
> different directories as you need, run ./build_inplace and modify each
> config.ini in those directories as needed. Then run mediaproxy from
> those directories and each of them will use the local config.ini from
> its own directory.
>
> Alternatively, if you want to use a system wide installation, you can
> copy the binaries from /usr/bin to a number of different directories
> and add a config.ini in each directory. Then run those binaries from
> those directories instead of /usr/bin/ and each binary will use the
> config.ini file in its own directory to overwrite settings from the
> global /etc/mediaproxy/config.ini.
>
> Mediaproxy uses 2 configuration files. The global one resides in /etc/
> mediaproxy/config.ini. On top of that if a config.ini is present in
> the same directory as the binary (media-relay & media-dispatcher) that
> one will be used to overwrite the settings from the global one having
> priority over it.
>
> --
> Dan
>
>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] mediaproxy relay on none default route interface failed

[Raúl Alexis Betancor Santana]

On Thursday 10 September 2009 15:02:21 Dan Pascu wrote:
> You don't need to patch anything. Just unpack mediaproxy in as many
> different directories as you need, run ./build_inplace and modify each
> config.ini in those directories as needed. Then run mediaproxy from
> those directories and each of them will use the local config.ini from
> its own directory.

So ... "killing flies with bazookas" ...
So ... when having to update, need to update n instances, instead of only 
one ..
So ... wasting hard disk (I know it's cheap ... but wasting anyway) ...

I think it's easier to patch media-relay to be able to pass the config file as 
a param, as on many other programs around the world ..
 
> Alternatively, if you want to use a system wide installation, you can
> copy the binaries from /usr/bin to a number of different directories
> and add a config.ini in each directory. Then run those binaries from
> those directories instead of /usr/bin/ and each binary will use the
> config.ini file in its own directory to overwrite settings from the
> global /etc/mediaproxy/config.ini.

... no coments

> Mediaproxy uses 2 configuration files. The global one resides in /etc/
> mediaproxy/config.ini. On top of that if a config.ini is present in
> the same directory as the binary (media-relay & media-dispatcher) that
> one will be used to overwrite the settings from the global one having
> priority over it.

I have no tested that ... but anyway it requires me to been duplicating 
installations  ... I still think that a simple param like -c configfile is 
better.

-- 
Raúl Alexis Betancor Santana
Dimensión Virtual

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] mediaproxy relay on none default route interface failed

[Dan Pascu]

On 10 Sep 2009, at 15:47, Raúl Alexis Betancor Santana wrote:

> On Thursday 10 September 2009 11:56:00 Ghaith ALKAYYEM wrote:
>> Hello,
>>
>> I think it's not possible to use two separate relays on the same  
>> server,
>> I tried that a lot then I switched to RTPproxy.
>
> That's not true, you could run as many Realys as you want on the  
> same server,
> only have to patch mediaproxy-relay to be able to call it with a
> diferent .cfg as the default one, have diferent listen ports and no  
> more.

You don't need to patch anything. Just unpack mediaproxy in as many  
different directories as you need, run ./build_inplace and modify each  
config.ini in those directories as needed. Then run mediaproxy from  
those directories and each of them will use the local config.ini from  
its own directory.

Alternatively, if you want to use a system wide installation, you can  
copy the binaries from /usr/bin to a number of different directories  
and add a config.ini in each directory. Then run those binaries from  
those directories instead of /usr/bin/ and each binary will use the  
config.ini file in its own directory to overwrite settings from the  
global /etc/mediaproxy/config.ini.

Mediaproxy uses 2 configuration files. The global one resides in /etc/ 
mediaproxy/config.ini. On top of that if a config.ini is present in  
the same directory as the binary (media-relay & media-dispatcher) that  
one will be used to overwrite the settings from the global one having  
priority over it.

--
Dan




___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] mediaproxy relay on none default route interface failed

[Jiang Jinke]

Dear Raúl,

Thanks for the idea. But I'm wondering if there is another way to do
this easily.

Regards,
Jinke Jiang

2009/9/10 Raúl Alexis Betancor Santana :
> On Thursday 10 September 2009 11:56:00 Ghaith ALKAYYEM wrote:
>> Hello,
>>
>> I think it's not possible to use two separate relays on the same server,
>> I tried that a lot then I switched to RTPproxy.
>
> That's not true, you could run as many Realys as you want on the same server,
> only have to patch mediaproxy-relay to be able to call it with a
> diferent .cfg as the default one, have diferent listen ports and no more.
>
>
> --
> Raúl Alexis Betancor Santana
> Dimensión Virtual
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] mediaproxy relay on none default route interface failed

[Raúl Alexis Betancor Santana]

On Thursday 10 September 2009 11:56:00 Ghaith ALKAYYEM wrote:
> Hello,
>
> I think it's not possible to use two separate relays on the same server,
> I tried that a lot then I switched to RTPproxy.

That's not true, you could run as many Realys as you want on the same server, 
only have to patch mediaproxy-relay to be able to call it with a 
diferent .cfg as the default one, have diferent listen ports and no more.


-- 
Raúl Alexis Betancor Santana
Dimensión Virtual

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] mediaproxy relay on none default route interface failed

[Ghaith ALKAYYEM]

Hello,

I think it's not possible to use two separate relays on the same server,
I tried that a lot then I switched to RTPproxy.

Regards.


On Thu, 2009-09-10 at 18:22 +0800, Jiang Jinke wrote:
> Dear All,
> 
> I tried to make the relay to listen to the none default route
> interface, but failed.
> 
> Below is my configuration info and my env.
> 
> Using the latest mediaproxy-2.3.8 on CentOS 5.3.
> 
> I had media-dispatcher and media-relay running on my server which has
> multiple NIC interface,
> two public ips which are belong to two different provider.
> 
> for example:
> eth0: 192.168.88.12
> eth1: 203.xx.xx.xx
> eth2: 63.xx.xx.xx
> eth3: 10.11.12.21
> 
> route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric RefUse Iface
> 63.xx.xx.320.0.0.0 255.255.255.240 U 0  00 eth2
> 203.xx.xx.128  0.0.0.0 255.255.255.192 U 0  00 eth1
> 10.11.12.0  0.0.0.0 255.255.255.0   U 0  00 eth3
> 192.168.88.00.0.0.0 255.255.255.0   U 0  00 eth0
> 169.254.0.0 0.0.0.0 255.255.0.0 U 0  00 eth3
> 0.0.0.0 203.xx.xx.129  0.0.0.0 UG0  00 eth1
> 
> But I notice that the relay are always binding to the one that has
> default route
> as said in the document.
> I can use two machine of course, but is it possible to have two
> separate relay that will
> only sent out packet from the interface it's listening to.
> 
> my config file is:
> [Relay]
> dispatchers = 63.xx.xx.xx 203.xx.xx.xx
> port_range = 3:4
> log_level = DEBUG
> [Dispatcher]
> socket_path = dispatcher.sock
> listen_management = 127.0.0.1
> log_level = DEBUG
> relay_timeout = 5
> [TLS]
> certs_path = tls
> [Database]
> [Radius]
> [OpenSIPS]
> socket_path = '/var/run/opensips.sock'
> max_connections = 20
> 
> I tried to use the media_relay_avp before calling use_media_proxy();
> but it seems the relay still listening to the other interface which
> has the default route.
> 
> The script of opensips is below:
> $avp(s:media_relay) = "63.xx.xx.xx";
> use_media_proxy();
> 
> Regards,
> --
> Jinke Jiang
> 
> 
> 
> the debug log of mediaproxy:
> Sep 10 18:16:54 ssw1 media-dispatcher[21925]: debug: Issuing "update"
> command to relay at 63.xx.xx.xx
> Sep 10 18:16:54 ssw1 media-relay[21930]: debug: Received new SDP offer
> Sep 10 18:16:54 ssw1 media-relay[21930]:
> mediaproxy.mediacontrol.StreamListenerProtocol starting on 30028
> Sep 10 18:16:54 ssw1 media-relay[21930]:
> mediaproxy.mediacontrol.StreamListenerProtocol starting on 30029
> Sep 10 18:16:54 ssw1 media-relay[21930]:
> mediaproxy.mediacontrol.StreamListenerProtocol starting on 30030
> Sep 10 18:16:54 ssw1 media-relay[21930]:
> mediaproxy.mediacontrol.StreamListenerProtocol starting on 30031
> Sep 10 18:16:54 ssw1 media-relay[21930]: debug: Added new stream:
> (audio) 10.10.101.147:20562 (RTP: Unknown, RTCP: Unknown) <->
> 203.xx.xx.xx:30028 <->
> 
> 203.xx.xx.xx:30030 <-> Unknown (RTP: Unknown, RTCP: Unknown)
> Sep 10 18:16:54 ssw1 media-relay[21930]: debug: created new session
> 4022675...@10.10.101.147: 8...@test.com (3297793466) -->
> 0086135x...@test.com
> Sep 10 18:16:55 ssw1 media-dispatcher[21925]: debug: Issuing "update"
> command to relay at 63.xx.xx.xx
> Sep 10 18:16:55 ssw1 media-relay[21930]: debug: updating existing
> session 4022675...@10.10.101.147: 8...@test.com (3297793466) -->
> 0086135x...@test.com
> Sep 10 18:16:55 ssw1 media-relay[21930]: debug: Received updated SDP answer
> Sep 10 18:16:55 ssw1 media-relay[21930]: debug: Got initial answer
> from callee for stream: (audio) 10.10.101.147:20562 (RTP: Unknown,
> RTCP: Unknown) <->
> 
> 203.xx.xx.xx:30028 <-> 203.xx.xx.xx:30030 <-> 203.xx.xx.15x:18550
> (RTP: Unknown, RTCP: Unknown)
> Sep 10 18:16:56 ssw1 media-relay[21930]: debug: Got traffic
> information for stream: (audio) 10.10.101.147:20562 (RTP:
> 119.145.xx.xx:20562, RTCP: Unknown) <->
> 
> 203.xx.xx.xx:30028 <-> 203.xx.xx.xx:30030 <-> 203.xx.xx.15x:18550
> (RTP: Unknown, RTCP: Unknown)
> Sep 10 18:16:56 ssw1 media-relay[21930]: debug: Got traffic
> information for stream: (audio) 10.10.101.147:20562 (RTP:
> 119.145.xx.xx:20562, RTCP: Unknown) <->
> 
> 203.xx.xx.xx:30028 <-> 203.xx.xx.xx:30030 <-> 203.xx.xx.15x:18550
> (RTP: 203.xx.xx.15x:18550, RTCP: Unknown)
> Sep 10 18:16:58 ssw1 media-relay[21930]: debug: Got traffic
> information for stream: (audio) 10.10.101.147:20562 (RTP:
> 119.145.xx.xx:20562, RTCP: Unknown) <->
> 
> 203.xx.xx.xx:30028 <-> 203.xx.xx.xx:30030 <-> 203.xx.xx.15x:18550
> (RTP: 203.xx.xx.15x:18550, RTCP: 203.xx.xx.15x:18551)
> Sep 10 18:17:03 ssw1 media-dispatcher[21925]: debug: Issuing "update"
> command to relay at 63.xx.xx.xx
> Sep 10 18:17:03 ssw1 media-relay[21930]: debug: updating existing
> session 4022675...@10.10.101.147: 8...@test.com (3297793466) -->
> 0086135x...@test.com
> Sep 10 18:17:03 ssw1 media-relay[21930]: debug: Recei

[OpenSIPS-Users] mediaproxy relay on none default route interface failed

[Jiang Jinke]

Dear All,

I tried to make the relay to listen to the none default route
interface, but failed.

Below is my configuration info and my env.

Using the latest mediaproxy-2.3.8 on CentOS 5.3.

I had media-dispatcher and media-relay running on my server which has
multiple NIC interface,
two public ips which are belong to two different provider.

for example:
eth0: 192.168.88.12
eth1: 203.xx.xx.xx
eth2: 63.xx.xx.xx
eth3: 10.11.12.21

route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
63.xx.xx.320.0.0.0 255.255.255.240 U 0  00 eth2
203.xx.xx.128  0.0.0.0 255.255.255.192 U 0  00 eth1
10.11.12.0  0.0.0.0 255.255.255.0   U 0  00 eth3
192.168.88.00.0.0.0 255.255.255.0   U 0  00 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0  00 eth3
0.0.0.0 203.xx.xx.129  0.0.0.0 UG0  00 eth1

But I notice that the relay are always binding to the one that has
default route
as said in the document.
I can use two machine of course, but is it possible to have two
separate relay that will
only sent out packet from the interface it's listening to.

my config file is:
[Relay]
dispatchers = 63.xx.xx.xx 203.xx.xx.xx
port_range = 3:4
log_level = DEBUG
[Dispatcher]
socket_path = dispatcher.sock
listen_management = 127.0.0.1
log_level = DEBUG
relay_timeout = 5
[TLS]
certs_path = tls
[Database]
[Radius]
[OpenSIPS]
socket_path = '/var/run/opensips.sock'
max_connections = 20

I tried to use the media_relay_avp before calling use_media_proxy();
but it seems the relay still listening to the other interface which
has the default route.

The script of opensips is below:
$avp(s:media_relay) = "63.xx.xx.xx";
use_media_proxy();

Regards,
--
Jinke Jiang



the debug log of mediaproxy:
Sep 10 18:16:54 ssw1 media-dispatcher[21925]: debug: Issuing "update"
command to relay at 63.xx.xx.xx
Sep 10 18:16:54 ssw1 media-relay[21930]: debug: Received new SDP offer
Sep 10 18:16:54 ssw1 media-relay[21930]:
mediaproxy.mediacontrol.StreamListenerProtocol starting on 30028
Sep 10 18:16:54 ssw1 media-relay[21930]:
mediaproxy.mediacontrol.StreamListenerProtocol starting on 30029
Sep 10 18:16:54 ssw1 media-relay[21930]:
mediaproxy.mediacontrol.StreamListenerProtocol starting on 30030
Sep 10 18:16:54 ssw1 media-relay[21930]:
mediaproxy.mediacontrol.StreamListenerProtocol starting on 30031
Sep 10 18:16:54 ssw1 media-relay[21930]: debug: Added new stream:
(audio) 10.10.101.147:20562 (RTP: Unknown, RTCP: Unknown) <->
203.xx.xx.xx:30028 <->

203.xx.xx.xx:30030 <-> Unknown (RTP: Unknown, RTCP: Unknown)
Sep 10 18:16:54 ssw1 media-relay[21930]: debug: created new session
4022675...@10.10.101.147: 8...@test.com (3297793466) -->
0086135x...@test.com
Sep 10 18:16:55 ssw1 media-dispatcher[21925]: debug: Issuing "update"
command to relay at 63.xx.xx.xx
Sep 10 18:16:55 ssw1 media-relay[21930]: debug: updating existing
session 4022675...@10.10.101.147: 8...@test.com (3297793466) -->
0086135x...@test.com
Sep 10 18:16:55 ssw1 media-relay[21930]: debug: Received updated SDP answer
Sep 10 18:16:55 ssw1 media-relay[21930]: debug: Got initial answer
from callee for stream: (audio) 10.10.101.147:20562 (RTP: Unknown,
RTCP: Unknown) <->

203.xx.xx.xx:30028 <-> 203.xx.xx.xx:30030 <-> 203.xx.xx.15x:18550
(RTP: Unknown, RTCP: Unknown)
Sep 10 18:16:56 ssw1 media-relay[21930]: debug: Got traffic
information for stream: (audio) 10.10.101.147:20562 (RTP:
119.145.xx.xx:20562, RTCP: Unknown) <->

203.xx.xx.xx:30028 <-> 203.xx.xx.xx:30030 <-> 203.xx.xx.15x:18550
(RTP: Unknown, RTCP: Unknown)
Sep 10 18:16:56 ssw1 media-relay[21930]: debug: Got traffic
information for stream: (audio) 10.10.101.147:20562 (RTP:
119.145.xx.xx:20562, RTCP: Unknown) <->

203.xx.xx.xx:30028 <-> 203.xx.xx.xx:30030 <-> 203.xx.xx.15x:18550
(RTP: 203.xx.xx.15x:18550, RTCP: Unknown)
Sep 10 18:16:58 ssw1 media-relay[21930]: debug: Got traffic
information for stream: (audio) 10.10.101.147:20562 (RTP:
119.145.xx.xx:20562, RTCP: Unknown) <->

203.xx.xx.xx:30028 <-> 203.xx.xx.xx:30030 <-> 203.xx.xx.15x:18550
(RTP: 203.xx.xx.15x:18550, RTCP: 203.xx.xx.15x:18551)
Sep 10 18:17:03 ssw1 media-dispatcher[21925]: debug: Issuing "update"
command to relay at 63.xx.xx.xx
Sep 10 18:17:03 ssw1 media-relay[21930]: debug: updating existing
session 4022675...@10.10.101.147: 8...@test.com (3297793466) -->
0086135x...@test.com
Sep 10 18:17:03 ssw1 media-relay[21930]: debug: Received updated SDP answer
Sep 10 18:17:03 ssw1 media-relay[21930]: debug: Unchanged stream:
(audio) 10.10.101.147:20562 (RTP: 119.145.xx.xx:20562, RTCP: Unknown)
<->

203.xx.xx.xx:30028 <-> 203.xx.xx.xx:30030 <-> 203.xx.xx.15x:18550
(RTP: 203.xx.xx.15x:18550, RTCP: 203.xx.xx.15x:18551)
Sep 10 18:17:04 ssw1 media-dispatcher[21925]: debug: Issuing "remove"
command to relay at 63.xx.xx.xx
Sep 10 18:17:04 ssw1 media-relay[21930]: debug: removing 

Re: [OpenSIPS-Users] mediaproxy relay

[Dan Pascu]

On 12 Aug 2009, at 17:23, Ghaith ALKAYYEM wrote:

> Hi,
> Could you tell me what is happening to mediaproxy relay when I'm  
> trying
> to run it?
> The relay is not starting and this message appears:
>
> Set resource limit for maximum open file descriptors to 11000
> debug: Adding new dispatcher at
> O j: operation is not possible without initialized secure  
> memory
> Aborted

That message is not generated by mediaproxy. It seems that it's a  
gnutls bug, as per this thread:

http://bugs.gentoo.org/235098

I'd recommend you upgrade to gnutls-2.6.x and rebuild python-gnutls.

--
Dan




___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] mediaproxy relay

[Ghaith ALKAYYEM]

Hi,
Could you tell me what is happening to mediaproxy relay when I'm trying
to run it?
The relay is not starting and this message appears:

Set resource limit for maximum open file descriptors to 11000
debug: Adding new dispatcher at 
O j: operation is not possible without initialized secure memory
Aborted



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Mediaproxy relay error: 'module' object has no attribute 'Interface'

[Ruud Klaver]

Hi,
On 26 May 2009, at 22:18, CSB wrote:
>>
>> Perhaps you do not have the zope.interface module installed?
>>
>> I'm not sure which linux distribution you are using, but I'm guessing
>> from the rpm command that it is some RedHat derivative. You can save
>> yourself from these sort of dependency problem by using Debian and
>> installing MediaProxy2 directly from our repository.
>>
> Unfortunately we have a number of servers all running CentOS so to  
> change is
> not so easy. zope.interface looks like it's installed - see my other  
> post.
>
> Regards
>
> Cameron

The traceback shows the problem is in twisted.names, so I would  
probably suspect there is something wrong with that version. I don't  
understand the version number you quote of that anyway, 0.3.0 seems to  
be very different from the rest. Please try to upgrade anything  
related to twisted to use the latest version and see if you still have  
problems.

Ruud Klaver
AG Projects

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Mediaproxy relay error: 'module' object has no attribute 'Interface'

[CSB]

> Hi,
> 
> On 26 May 2009, at 10:24, CSB wrote:
> 
> > When attempting to start the MediaProxy relay I get the following:
> >
> > May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: Starting
> > MediaProxy
> > Relay 2.3.4
> > May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: fatal error:
> > failed to
> > create MediaProxy Relay: 'module' object has no attribute 'Interface'
> > May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: Traceback (most
> > recent
> > call last):
> > May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: ---  > caught
> > here> ---
> > May 26 16:45:00 ip-10-250-54-212 media-relay[18032]:   File "./media-
> > relay",
> > line 55, in ?
> > May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: from
> > mediaproxy.relay import MediaRelay
> > May 26 16:45:00 ip-10-250-54-212 media-relay[18032]:   File
> > "/usr/lib/python2.4/site-packages/mediaproxy/relay.py", line 30, in ?
> > May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: from
> > twisted.names
> > import dns
> > May 26 16:45:00 ip-10-250-54-212 media-relay[18032]:   File
> > "/usr/lib/python2.4/site-packages/twisted/names/dns.py", line 116,
> > in ?
> > May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: class
> > IRecord(components.Interface):
> > May 26 16:45:00 ip-10-250-54-212 media-relay[18032]:
> > exceptions.AttributeError: 'module' object has no attribute
> > 'Interface'
> >
> > rpm -q python-twisted-core
> > python-twisted-core-2.5.0-4.el5
> > rpm -q python-twisted-names
> > python-twisted-names-0.3.0-3.el5
> > rpm -q python-twisted-web2
> > python-twisted-web2-8.1.0-1.el5.rf
> >
> > Any assistance appreciated.
> >
> > Cameron
> 
> Perhaps you do not have the zope.interface module installed?
> 
> I'm not sure which linux distribution you are using, but I'm guessing
> from the rpm command that it is some RedHat derivative. You can save
> yourself from these sort of dependency problem by using Debian and
> installing MediaProxy2 directly from our repository.
> 
Unfortunately we have a number of servers all running CentOS so to change is
not so easy. zope.interface looks like it's installed - see my other post.

Regards

Cameron


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Mediaproxy relay error: 'module' object has no attribute 'Interface'

[CSB]

> It appears that you do not have the zope-interface package installed.
> 
According to rpm that is installed:

rpm -q python-zope-interface
python-zope-interface-3.0.1-10.el5

I do have /usr/lib/python2.4/site-packages/zope/interface with various
python scripts in there.

Regards

Cameron

> On Tuesday 26 May 2009, CSB wrote:
> > When attempting to start the MediaProxy relay I get the following:
> >
> > May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: Starting
> MediaProxy
> > Relay 2.3.4
> > May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: fatal error:
> failed to
> > create MediaProxy Relay: 'module' object has no attribute 'Interface'
> > May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: Traceback (most
> recent
> > call last):
> > May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: ---  caught
> > here> ---
> > May 26 16:45:00 ip-10-250-54-212 media-relay[18032]:   File "./media-
> relay",
> > line 55, in ?
> > May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: from
> > mediaproxy.relay import MediaRelay
> > May 26 16:45:00 ip-10-250-54-212 media-relay[18032]:   File
> > "/usr/lib/python2.4/site-packages/mediaproxy/relay.py", line 30, in ?
> > May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: from
> twisted.names
> > import dns
> > May 26 16:45:00 ip-10-250-54-212 media-relay[18032]:   File
> > "/usr/lib/python2.4/site-packages/twisted/names/dns.py", line 116, in
> ?
> > May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: class
> > IRecord(components.Interface):
> > May 26 16:45:00 ip-10-250-54-212 media-relay[18032]:
> > exceptions.AttributeError: 'module' object has no attribute
> 'Interface'
> >
> > rpm -q python-twisted-core
> > python-twisted-core-2.5.0-4.el5
> > rpm -q python-twisted-names
> > python-twisted-names-0.3.0-3.el5
> > rpm -q python-twisted-web2
> > python-twisted-web2-8.1.0-1.el5.rf
> >
> > Any assistance appreciated.
> >
> > Cameron
> >
> >
> > ___
> > Users mailing list
> > Users@lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
> >
> 
> 
> --
> Dan


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Mediaproxy relay error: 'module' object has no attribute 'Interface'

[Ruud Klaver]

Hi,

On 26 May 2009, at 10:24, CSB wrote:

> When attempting to start the MediaProxy relay I get the following:
>
> May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: Starting  
> MediaProxy
> Relay 2.3.4
> May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: fatal error:  
> failed to
> create MediaProxy Relay: 'module' object has no attribute 'Interface'
> May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: Traceback (most  
> recent
> call last):
> May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: ---  caught
> here> ---
> May 26 16:45:00 ip-10-250-54-212 media-relay[18032]:   File "./media- 
> relay",
> line 55, in ?
> May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: from
> mediaproxy.relay import MediaRelay
> May 26 16:45:00 ip-10-250-54-212 media-relay[18032]:   File
> "/usr/lib/python2.4/site-packages/mediaproxy/relay.py", line 30, in ?
> May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: from  
> twisted.names
> import dns
> May 26 16:45:00 ip-10-250-54-212 media-relay[18032]:   File
> "/usr/lib/python2.4/site-packages/twisted/names/dns.py", line 116,  
> in ?
> May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: class
> IRecord(components.Interface):
> May 26 16:45:00 ip-10-250-54-212 media-relay[18032]:
> exceptions.AttributeError: 'module' object has no attribute  
> 'Interface'
>
> rpm -q python-twisted-core
> python-twisted-core-2.5.0-4.el5
> rpm -q python-twisted-names
> python-twisted-names-0.3.0-3.el5
> rpm -q python-twisted-web2
> python-twisted-web2-8.1.0-1.el5.rf
>
> Any assistance appreciated.
>
> Cameron

Perhaps you do not have the zope.interface module installed?

I'm not sure which linux distribution you are using, but I'm guessing  
from the rpm command that it is some RedHat derivative. You can save  
yourself from these sort of dependency problem by using Debian and  
installing MediaProxy2 directly from our repository.

Ruud Klaver
AG Projects

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Mediaproxy relay error: 'module' object has no attribute 'Interface'

[Dan Pascu]

It appears that you do not have the zope-interface package installed.

On Tuesday 26 May 2009, CSB wrote:
> When attempting to start the MediaProxy relay I get the following:
> 
> May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: Starting MediaProxy
> Relay 2.3.4
> May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: fatal error: failed to
> create MediaProxy Relay: 'module' object has no attribute 'Interface'
> May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: Traceback (most recent
> call last):
> May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: ---  here> ---
> May 26 16:45:00 ip-10-250-54-212 media-relay[18032]:   File "./media-relay",
> line 55, in ?
> May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: from
> mediaproxy.relay import MediaRelay
> May 26 16:45:00 ip-10-250-54-212 media-relay[18032]:   File
> "/usr/lib/python2.4/site-packages/mediaproxy/relay.py", line 30, in ?
> May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: from twisted.names
> import dns
> May 26 16:45:00 ip-10-250-54-212 media-relay[18032]:   File
> "/usr/lib/python2.4/site-packages/twisted/names/dns.py", line 116, in ?
> May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: class
> IRecord(components.Interface):
> May 26 16:45:00 ip-10-250-54-212 media-relay[18032]:
> exceptions.AttributeError: 'module' object has no attribute 'Interface'
> 
> rpm -q python-twisted-core
> python-twisted-core-2.5.0-4.el5
> rpm -q python-twisted-names
> python-twisted-names-0.3.0-3.el5
> rpm -q python-twisted-web2
> python-twisted-web2-8.1.0-1.el5.rf
> 
> Any assistance appreciated.
> 
> Cameron
> 
> 
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> 
> 


-- 
Dan

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Mediaproxy relay error: 'module' object has no attribute 'Interface'

[CSB]

When attempting to start the MediaProxy relay I get the following:

May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: Starting MediaProxy
Relay 2.3.4
May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: fatal error: failed to
create MediaProxy Relay: 'module' object has no attribute 'Interface'
May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: Traceback (most recent
call last):
May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: ---  ---
May 26 16:45:00 ip-10-250-54-212 media-relay[18032]:   File "./media-relay",
line 55, in ?
May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: from
mediaproxy.relay import MediaRelay
May 26 16:45:00 ip-10-250-54-212 media-relay[18032]:   File
"/usr/lib/python2.4/site-packages/mediaproxy/relay.py", line 30, in ?
May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: from twisted.names
import dns
May 26 16:45:00 ip-10-250-54-212 media-relay[18032]:   File
"/usr/lib/python2.4/site-packages/twisted/names/dns.py", line 116, in ?
May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: class
IRecord(components.Interface):
May 26 16:45:00 ip-10-250-54-212 media-relay[18032]:
exceptions.AttributeError: 'module' object has no attribute 'Interface'

rpm -q python-twisted-core
python-twisted-core-2.5.0-4.el5
rpm -q python-twisted-names
python-twisted-names-0.3.0-3.el5
rpm -q python-twisted-web2
python-twisted-web2-8.1.0-1.el5.rf

Any assistance appreciated.

Cameron


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Mediaproxy relay exception for video call

[Carlo Dimaggio]

Il giorno 05/mag/09, alle ore 12:28, Ruud Klaver ha scritto:

> Hi Carlo,
>
> This seems to be exactly the same exception you posted before. It  
> means no relaying UDP ports are available at the relay. Could you  
> check your configuration for the amount of ports you allocated?

Hi Ruud,

I'm sorry!!!
I have forgot that I've changed the config.ini in media relay... :-(
There was no problem in voice call because the stream used only 4  
ports...


Many, many thanks




___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Mediaproxy relay exception for video call

[Ruud Klaver]

Hi Carlo,

On 05 May 2009, at 11:25, Carlo Dimaggio wrote:

> Hi all,
>
> I have an exception in media-relay when I try to perform a video call
> (h.263/264 or 261). A voice call works fine.
> The two endpoints are Ekiga 3.0 and Xmeeting 0.3.4a (or Xlite 3) while
> the other versions are: opensips 1.5.1, media dispatcher and relay
> 2.3.4.
>
> Is this problem related to mediaproxy 2.3.4?
>
>
> Thanks and regards,
> Carlo Dimaggio
>
>
>
> --- Log Media-dispatcher
>
> May  5 10:38:07 sip media-dispatcher[4623]: debug: Issuing "update"
> command to relay at 
> May  5 10:38:07 sip media-dispatcher[4623]: warning: Relay at
>  returned error: Received error from relay at  in
> response to "update" command
> May  5 10:38:07 sip media-dispatcher[4623]: error: Error processing
> request: No suitable relay found
>
>
> --- Log Media-relay
>
> May  5 10:38:07 media media-relay[14342]: Traceback (most recent call
> last):
> May  5 10:38:07 media media-relay[14342]:   File "/usr/lib/python2.5/
> site-packages/twisted/internet/epollreactor.py", line 197, in
> _doReadOrWrite
> May  5 10:38:07 media media-relay[14342]: why =  
> selectable.doRead()
> May  5 10:38:07 media media-relay[14342]:   File "/var/lib/python-
> support/python2.5/gnutls/interfaces/twisted/__init__.py", line 82, in
> doRead
> May  5 10:38:07 media media-relay[14342]: return
> tcp.Connection.doRead(self)
> May  5 10:38:07 media media-relay[14342]:   File "/usr/lib/python2.5/
> site-packages/twisted/internet/tcp.py", line 362, in doRead
> May  5 10:38:07 media media-relay[14342]: return
> self.protocol.dataReceived(data)
> May  5 10:38:07 media media-relay[14342]:   File "/usr/lib/python2.5/
> site-packages/twisted/protocols/basic.py", line 149, in dataReceived
> May  5 10:38:07 media media-relay[14342]: self.lineReceived(line)
> May  5 10:38:07 media media-relay[14342]: --- 
> ---
> May  5 10:38:07 media media-relay[14342]:   File "/usr/lib/python2.5/
> site-packages/mediaproxy/relay.py", line 180, in lineReceived
> May  5 10:38:07 media media-relay[14342]: response =
> self.factory.parent.got_command(self.factory.host, self.command,
> self.headers)
> May  5 10:38:07 media media-relay[14342]:   File "/usr/lib/python2.5/
> site-packages/mediaproxy/relay.py", line 391, in got_command
> May  5 10:38:07 media media-relay[14342]: local_media =
> self.session_manager.update_session(dispatcher, **headers)
> May  5 10:38:07 media media-relay[14342]:   File "/usr/lib/python2.5/
> site-packages/mediaproxy/mediacontrol.py", line 673, in update_session
> May  5 10:38:07 media media-relay[14342]: session = Session(self,
> dispatcher, call_id, from_tag, from_uri, to_tag, to_uri, cseq,
> user_agent, media, is_downstream, is_caller_cseq)
> May  5 10:38:07 media media-relay[14342]:   File "/usr/lib/python2.5/
> site-packages/mediaproxy/mediacontrol.py", line 422, in __init__
> May  5 10:38:07 media media-relay[14342]: self.update_media(cseq,
> to_tag, user_agent, media_list, is_downstream, is_caller_cseq)
> May  5 10:38:07 media media-relay[14342]:   File "/usr/lib/python2.5/
> site-packages/mediaproxy/mediacontrol.py", line 463, in update_media
> May  5 10:38:07 media media-relay[14342]: stream =
> MediaStream(self, media_type, media_ip, media_port, party,
> media_direction)
> May  5 10:38:07 media media-relay[14342]:   File "/usr/lib/python2.5/
> site-packages/mediaproxy/mediacontrol.py", line 317, in __init__
> May  5 10:38:07 media media-relay[14342]: self.caller =
> MediaParty(self)
> May  5 10:38:07 media media-relay[14342]:   File "/usr/lib/python2.5/
> site-packages/mediaproxy/mediacontrol.py", line 285, in __init__
> May  5 10:38:07 media media-relay[14342]: self.ports = port_rtp,
> port_rtcp = self.manager.get_ports()
> May  5 10:38:07 media media-relay[14342]:   File "/usr/lib/python2.5/
> site-packages/mediaproxy/mediacontrol.py", line 640, in get_ports
> May  5 10:38:07 media media-relay[14342]: return
> self.ports.popleft()
> May  5 10:38:07 media media-relay[14342]: exceptions.IndexError: pop
> from an empty deque

This seems to be exactly the same exception you posted before. It  
means no relaying UDP ports are available at the relay. Could you  
check your configuration for the amount of ports you allocated?

This exception should be fixed in the next version, although it would  
still mean there are no more ports to allocate.

Ruud Klaver
AG Projects

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Mediaproxy relay exception for video call

[Carlo Dimaggio]

Hi all,

I have an exception in media-relay when I try to perform a video call  
(h.263/264 or 261). A voice call works fine.
The two endpoints are Ekiga 3.0 and Xmeeting 0.3.4a (or Xlite 3) while  
the other versions are: opensips 1.5.1, media dispatcher and relay  
2.3.4.

Is this problem related to mediaproxy 2.3.4?


Thanks and regards,
Carlo Dimaggio



--- Log Media-dispatcher

May  5 10:38:07 sip media-dispatcher[4623]: debug: Issuing "update"  
command to relay at 
May  5 10:38:07 sip media-dispatcher[4623]: warning: Relay at  
 returned error: Received error from relay at  in  
response to "update" command
May  5 10:38:07 sip media-dispatcher[4623]: error: Error processing  
request: No suitable relay found


--- Log Media-relay

May  5 10:38:07 media media-relay[14342]: Traceback (most recent call  
last):
May  5 10:38:07 media media-relay[14342]:   File "/usr/lib/python2.5/ 
site-packages/twisted/internet/epollreactor.py", line 197, in  
_doReadOrWrite
May  5 10:38:07 media media-relay[14342]: why = selectable.doRead()
May  5 10:38:07 media media-relay[14342]:   File "/var/lib/python- 
support/python2.5/gnutls/interfaces/twisted/__init__.py", line 82, in  
doRead
May  5 10:38:07 media media-relay[14342]: return  
tcp.Connection.doRead(self)
May  5 10:38:07 media media-relay[14342]:   File "/usr/lib/python2.5/ 
site-packages/twisted/internet/tcp.py", line 362, in doRead
May  5 10:38:07 media media-relay[14342]: return  
self.protocol.dataReceived(data)
May  5 10:38:07 media media-relay[14342]:   File "/usr/lib/python2.5/ 
site-packages/twisted/protocols/basic.py", line 149, in dataReceived
May  5 10:38:07 media media-relay[14342]: self.lineReceived(line)
May  5 10:38:07 media media-relay[14342]: ---   
---
May  5 10:38:07 media media-relay[14342]:   File "/usr/lib/python2.5/ 
site-packages/mediaproxy/relay.py", line 180, in lineReceived
May  5 10:38:07 media media-relay[14342]: response =  
self.factory.parent.got_command(self.factory.host, self.command,  
self.headers)
May  5 10:38:07 media media-relay[14342]:   File "/usr/lib/python2.5/ 
site-packages/mediaproxy/relay.py", line 391, in got_command
May  5 10:38:07 media media-relay[14342]: local_media =  
self.session_manager.update_session(dispatcher, **headers)
May  5 10:38:07 media media-relay[14342]:   File "/usr/lib/python2.5/ 
site-packages/mediaproxy/mediacontrol.py", line 673, in update_session
May  5 10:38:07 media media-relay[14342]: session = Session(self,  
dispatcher, call_id, from_tag, from_uri, to_tag, to_uri, cseq,  
user_agent, media, is_downstream, is_caller_cseq)
May  5 10:38:07 media media-relay[14342]:   File "/usr/lib/python2.5/ 
site-packages/mediaproxy/mediacontrol.py", line 422, in __init__
May  5 10:38:07 media media-relay[14342]: self.update_media(cseq,  
to_tag, user_agent, media_list, is_downstream, is_caller_cseq)
May  5 10:38:07 media media-relay[14342]:   File "/usr/lib/python2.5/ 
site-packages/mediaproxy/mediacontrol.py", line 463, in update_media
May  5 10:38:07 media media-relay[14342]: stream =  
MediaStream(self, media_type, media_ip, media_port, party,  
media_direction)
May  5 10:38:07 media media-relay[14342]:   File "/usr/lib/python2.5/ 
site-packages/mediaproxy/mediacontrol.py", line 317, in __init__
May  5 10:38:07 media media-relay[14342]: self.caller =  
MediaParty(self)
May  5 10:38:07 media media-relay[14342]:   File "/usr/lib/python2.5/ 
site-packages/mediaproxy/mediacontrol.py", line 285, in __init__
May  5 10:38:07 media media-relay[14342]: self.ports = port_rtp,  
port_rtcp = self.manager.get_ports()
May  5 10:38:07 media media-relay[14342]:   File "/usr/lib/python2.5/ 
site-packages/mediaproxy/mediacontrol.py", line 640, in get_ports
May  5 10:38:07 media media-relay[14342]: return  
self.ports.popleft()
May  5 10:38:07 media media-relay[14342]: exceptions.IndexError: pop  
from an empty deque

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Mediaproxy relay exception when all the ports are in use

[Ruud Klaver]

Hi Carlo,

On 16 Apr 2009, at 11:05, Carlo Dimaggio wrote:

> HI all,
>
> I made a test with mediaproxy 2.3.4 in order to check what happens
> when the ports in the relay are not available (all in use).
> I saw that there is an exception in the media-relay.
>
> Can you see if it is an expected behaviour?
>
>
> Thanks,
> Carlo
>
> 

The relay doesn't seem to handle it too well, but the dispatcher  
doesn't freak out at least. Thanks for the report, I'll look into  
handling this more gracefully.

Ruud Klaver
AG Projects

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Mediaproxy relay exception when all the ports are in use

[Carlo Dimaggio]

HI all,

I made a test with mediaproxy 2.3.4 in order to check what happens  
when the ports in the relay are not available (all in use).
I saw that there is an exception in the media-relay.

Can you see if it is an expected behaviour?


Thanks,
Carlo


-

Log DISPATCHER:

Apr 16 10:56:18 sip media-dispatcher[4623]: debug: Issuing "update"  
command to relay at 
Apr 16 10:56:18 sip media-dispatcher[4623]: warning: Relay at  
 returned error: Received error from relay at  in  
response to "update" command
Apr 16 10:56:18 sip media-dispatcher[4623]: error: Error processing  
request: No suitable relay found
Apr 16 10:56:21 sip media-dispatcher[4623]: debug: Issuing "update"  
command to relay at 
Apr 16 10:56:21 sip media-dispatcher[4623]: warning: Relay at  
 returned error: Received error from relay at  in  
response to "update" command
Apr 16 10:56:21 sip media-dispatcher[4623]: error: Error processing  
request: No suitable relay found


Log RELAY:

Apr 16 10:56:17 proxy media-relay[14342]: debug: Received new SDP offer
Apr 16 10:56:17 proxy media-relay[14342]: Traceback (most recent call  
last):
Apr 16 10:56:17 proxy media-relay[14342]:   File "/usr/lib/python2.5/ 
site-packages/twisted/internet/epollreactor.py", line 197, in  
_doReadOrWrite
Apr 16 10:56:17 proxy media-relay[14342]: why = selectable.doRead()
Apr 16 10:56:17 proxy media-relay[14342]:   File "/var/lib/python- 
support/python2.5/gnutls/interfaces/twisted/__init__.py", line 82, in  
doRead
Apr 16 10:56:17 proxy media-relay[14342]: return  
tcp.Connection.doRead(self)
Apr 16 10:56:17 proxy media-relay[14342]:   File "/usr/lib/python2.5/ 
site-packages/twisted/internet/tcp.py", line 362, in doRead
Apr 16 10:56:17 proxy media-relay[14342]: return  
self.protocol.dataReceived(data)
Apr 16 10:56:17 proxy media-relay[14342]:   File "/usr/lib/python2.5/ 
site-packages/twisted/protocols/basic.py", line 149, in dataReceived
Apr 16 10:56:17 proxy media-relay[14342]: self.lineReceived(line)
Apr 16 10:56:17 proxy media-relay[14342]: ---   
---
Apr 16 10:56:17 proxy media-relay[14342]:   File "/usr/lib/python2.5/ 
site-packages/mediaproxy/relay.py", line 180, in lineReceived
Apr 16 10:56:17 proxy media-relay[14342]: response =  
self.factory.parent.got_command(self.factory.host, self.command,  
self.headers)
Apr 16 10:56:17 proxy media-relay[14342]:   File "/usr/lib/python2.5/ 
site-packages/mediaproxy/relay.py", line 391, in got_command
Apr 16 10:56:17 proxy media-relay[14342]: local_media =  
self.session_manager.update_session(dispatcher, **headers)
Apr 16 10:56:17 proxy media-relay[14342]:   File "/usr/lib/python2.5/ 
site-packages/mediaproxy/mediacontrol.py", line 673, in update_session
Apr 16 10:56:17 proxy media-relay[14342]: session = Session(self,  
dispatcher, call_id, from_tag, from_uri, to_tag, to_uri, cseq,  
user_agent, media, is_downstream, is_caller_cseq)
Apr 16 10:56:17 proxy media-relay[14342]:   File "/usr/lib/python2.5/ 
site-packages/mediaproxy/mediacontrol.py", line 422, in __init__
Apr 16 10:56:17 proxy media-relay[14342]: self.update_media(cseq,  
to_tag, user_agent, media_list, is_downstream, is_caller_cseq)
Apr 16 10:56:17 proxy media-relay[14342]:   File "/usr/lib/python2.5/ 
site-packages/mediaproxy/mediacontrol.py", line 463, in update_media
Apr 16 10:56:17 proxy media-relay[14342]: stream =  
MediaStream(self, media_type, media_ip, media_port, party,  
media_direction)
Apr 16 10:56:17 proxy media-relay[14342]:   File "/usr/lib/python2.5/ 
site-packages/mediaproxy/mediacontrol.py", line 317, in __init__
Apr 16 10:56:17 proxy media-relay[14342]: self.caller =  
MediaParty(self)
Apr 16 10:56:17 proxy media-relay[14342]:   File "/usr/lib/python2.5/ 
site-packages/mediaproxy/mediacontrol.py", line 285, in __init__
Apr 16 10:56:17 proxy media-relay[14342]: self.ports = port_rtp,  
port_rtcp = self.manager.get_ports()
Apr 16 10:56:17 proxy media-relay[14342]:   File "/usr/lib/python2.5/ 
site-packages/mediaproxy/mediacontrol.py", line 640, in get_ports
Apr 16 10:56:17 proxy media-relay[14342]: return  
self.ports.popleft()
Apr 16 10:56:17 proxy media-relay[14342]: exceptions.IndexError: pop  
from an empty deque
Apr 16 10:56:20 proxy media-relay[14342]: debug: Received new SDP offer
Apr 16 10:56:20 proxy media-relay[14342]: Traceback (most recent call  
last):
Apr 16 10:56:20 proxy media-relay[14342]:   File "/usr/lib/python2.5/ 
site-packages/twisted/internet/epollreactor.py", line 197, in  
_doReadOrWrite
Apr 16 10:56:20 proxy media-relay[14342]: why = selectable.doRead()
Apr 16 10:56:20 proxy media-relay[14342]:   File "/var/lib/python- 
support/python2.5/gnutls/interfaces/twisted/__init__.py", line 82, in  
doRead
Apr 16 10:56:20 proxy media-relay[14342]: return  
tcp.Connection.doRead(self)
Apr 16 10:56:20 proxy media-relay[14342]:   File "/usr/lib/python2.5/ 
site-packages/twisted/internet/tcp.py", line 362, in doRead
Apr 16 10:56:20 proxy media-relay[1434

Re: [OpenSIPS-Users] Mediaproxy relay avp question

[Giuseppe Roberti]

Dan Pascu wrote:
> On Friday 16 January 2009, Giuseppe Roberti wrote:
>> Dan Pascu wrote:
>>> On Thursday 15 January 2009, Giuseppe Roberti wrote:
 Hi,
 can media_relay_avp be used with engage_media_proxy() or only for
 use_media_proxy() ?
>>> It works with both.
>> Anyone is sure that it really works ?
> 
> I can't speak for anyone, but if you use the latest mediaproxy version 
> (2.3.2) you may become a believer yourself ;)
> 
:D

I say that because i have tried and it doesnt work for me, so maybe i
have an error somewhere in my configuration.
I will check it next week.

Thanks.

-- 
Giuseppe Roberti


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Mediaproxy relay avp question

[Dan Pascu]

On Friday 16 January 2009, Giuseppe Roberti wrote:
> Dan Pascu wrote:
> > On Thursday 15 January 2009, Giuseppe Roberti wrote:
> >> Hi,
> >> can media_relay_avp be used with engage_media_proxy() or only for
> >> use_media_proxy() ?
> >
> > It works with both.
>
> Anyone is sure that it really works ?

I can't speak for anyone, but if you use the latest mediaproxy version 
(2.3.2) you may become a believer yourself ;)

-- 
Dan

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Mediaproxy relay avp question

[Giuseppe Roberti]

Dan Pascu wrote:
> On Thursday 15 January 2009, Giuseppe Roberti wrote:
>> Hi,
>> can media_relay_avp be used with engage_media_proxy() or only for
>> use_media_proxy() ?
> 
> It works with both.
> 
Anyone is sure that it really works ?

Thanks.

-- 
Giuseppe Roberti


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Mediaproxy relay avp question

[Dan Pascu]

On Thursday 15 January 2009, Giuseppe Roberti wrote:
> Hi,
> can media_relay_avp be used with engage_media_proxy() or only for
> use_media_proxy() ?

It works with both.

-- 
Dan

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Mediaproxy relay avp question

[Giuseppe Roberti]

Hi,
can media_relay_avp be used with engage_media_proxy() or only for
use_media_proxy() ?
Thanks.

-- 
Giuseppe Roberti


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users