Re: [Users] Mediaproxy running with Openser

2007-05-18 Thread Lesley Liu

Hi Arun,

I can't get my configure files now.
Here is a general configure:
(ser.cfg)
point mediaproxy to mediaproxy.sock

(mediaproxy.ini SIP site)
[Dispatcher]
start = yes
defaultProxy = Media Proxy server IP
[MediaProxy]
start = yes

(mediaproxy.ini on media proxy)
[Dispatcher]
start = no
[MediaProxy]
start = yes
listen = media server ip
allow = ser server ip
proxyIP = media server ip

Regards,
Lesley
___
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users


Re: [Users] Mediaproxy running with Openser

2007-05-18 Thread Arun Kumar

Hi

My ser.cfg:
modparam("nathelper", "rtpproxy_disable", 1)
modparam("nathelper", "natping_interval", 0)

modparam("mediaproxy", "natping_interval", 20)

and on my ser box Im running proxydispatcher.py: python
/usr/local/mediaproxy/proxydispatcher.py

mediaproxy.ini (on ser box)
[Dispatcher]
;
defaultProxy = Media Proxy server IP

[MediaProxy]
start = no
accounting = off

mediaproxy.ini (on my mediaproxy server)
[Dispatcher]
;
start = no

[MediaProxy]
;
listen = media server ip
allow = ser server ip
proxyIP = media server ip
accounting = off

and its running : python /usr/local/mediaproxy/mediaproxy.py

thanks
arun

On 5/18/07, Sergio Gutierrez <[EMAIL PROTECTED]> wrote:


Hi Arun.

Could you send a snippet of the log of both services.

Regards.

Sergio G.

On 5/18/07, Arun Kumar < [EMAIL PROTECTED]> wrote:
>
> Hi,
>
> can you please post your mediaproxy config for two server config. Im
> trying to setup the same thing but some problem and what I've to write in my
> ser.cfg that line also. Sorry to take your thread.
>
> thanks
> arun
>
> On 5/18/07, Lesley Liu < [EMAIL PROTECTED]> wrote:
>
> > Hi Sergio,
> >
> > Thanks for your kindly help.
> > SIP proxy and MEDIA proxy on different PC worked well now.
> >
> >
> > Regards,
> > Lesley
> >
> >
> > 2007/5/18, Sergio Gutierrez <[EMAIL PROTECTED]>:
> > >
> > > Hi Lesley.
> > >
> > > It is good to know it worked.
> > >
> > > Yes, you could configure the mediaproxy on another computer.
> > >
> > > You still load the mediaproxy module, and configure the socket to
> > > your proxydispatcher (which must be running).
> > >
> > > In the config file of it, you define that the mediaproxy is
> > > reachable at some IP address:
> > >
> > > This is an snippet of my mediaproxy.ini file:
> > >
> > > start = yes
> > > ;socket = /var/run/proxydispatcher.sock
> > > listen= X.Y.Z.W
> > > defaultProxy = A.B.C.D
> > > accounting = off
> > >
> > > Where A.B.C.D is the machine where mediaproxy is running; it listens
> > > on 25060 TCP port.
> > >
> > > Kind regards.
> > >
> > >
> > > On 5/18/07, Lesley Liu <[EMAIL PROTECTED] > wrote:
> > > >
> > > > Hi Sergio,
> > > >
> > > > You are correct, it works after modified the parameter.
> > > > Here comes another question: what if setup mediaproxy on another
> > > > PC? how to configure the openser.cfg? Should it load dispatcher?
> > > >
> > > > Thank you.
> > > >
> > > > Regards,
> > > > Lesley
> > > >
> > >
> > >
> >
> > ___
> > Users mailing list
> > [email protected]
> > http://openser.org/cgi-bin/mailman/listinfo/users
> >
> >
>

___
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users


Re: [Users] Mediaproxy running with Openser

2007-05-18 Thread Sergio Gutierrez

Hi Arun.

Could you send a snippet of the log of both services.

Regards.

Sergio G.

On 5/18/07, Arun Kumar <[EMAIL PROTECTED]> wrote:


Hi,

can you please post your mediaproxy config for two server config. Im
trying to setup the same thing but some problem and what I've to write in my
ser.cfg that line also. Sorry to take your thread.

thanks
arun

On 5/18/07, Lesley Liu <[EMAIL PROTECTED]> wrote:

> Hi Sergio,
>
> Thanks for your kindly help.
> SIP proxy and MEDIA proxy on different PC worked well now.
>
>
> Regards,
> Lesley
>
>
> 2007/5/18, Sergio Gutierrez <[EMAIL PROTECTED]>:
> >
> > Hi Lesley.
> >
> > It is good to know it worked.
> >
> > Yes, you could configure the mediaproxy on another computer.
> >
> > You still load the mediaproxy module, and configure the socket to your
> > proxydispatcher (which must be running).
> >
> > In the config file of it, you define that the mediaproxy is reachable
> > at some IP address:
> >
> > This is an snippet of my mediaproxy.ini file:
> >
> > start = yes
> > ;socket = /var/run/proxydispatcher.sock
> > listen= X.Y.Z.W
> > defaultProxy = A.B.C.D
> > accounting = off
> >
> > Where A.B.C.D is the machine where mediaproxy is running; it listens
> > on 25060 TCP port.
> >
> > Kind regards.
> >
> >
> > On 5/18/07, Lesley Liu <[EMAIL PROTECTED] > wrote:
> > >
> > > Hi Sergio,
> > >
> > > You are correct, it works after modified the parameter.
> > > Here comes another question: what if setup mediaproxy on another PC?
> > > how to configure the openser.cfg? Should it load dispatcher?
> > >
> > > Thank you.
> > >
> > > Regards,
> > > Lesley
> > >
> >
> >
>
> ___
> Users mailing list
> [email protected]
> http://openser.org/cgi-bin/mailman/listinfo/users
>
>

___
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users


Re: [Users] Mediaproxy running with Openser

2007-05-18 Thread Arun Kumar

Hi,

can you please post your mediaproxy config for two server config. Im trying
to setup the same thing but some problem and what I've to write in my
ser.cfg that line also. Sorry to take your thread.

thanks
arun

On 5/18/07, Lesley Liu <[EMAIL PROTECTED]> wrote:


Hi Sergio,

Thanks for your kindly help.
SIP proxy and MEDIA proxy on different PC worked well now.


Regards,
Lesley


2007/5/18, Sergio Gutierrez <[EMAIL PROTECTED]>:
>
> Hi Lesley.
>
> It is good to know it worked.
>
> Yes, you could configure the mediaproxy on another computer.
>
> You still load the mediaproxy module, and configure the socket to your
> proxydispatcher (which must be running).
>
> In the config file of it, you define that the mediaproxy is reachable at
> some IP address:
>
> This is an snippet of my mediaproxy.ini file:
>
> start = yes
> ;socket = /var/run/proxydispatcher.sock
> listen= X.Y.Z.W
> defaultProxy = A.B.C.D
> accounting = off
>
> Where A.B.C.D is the machine where mediaproxy is running; it listens on
> 25060 TCP port.
>
> Kind regards.
>
>
> On 5/18/07, Lesley Liu <[EMAIL PROTECTED] > wrote:
> >
> > Hi Sergio,
> >
> > You are correct, it works after modified the parameter.
> > Here comes another question: what if setup mediaproxy on another PC?
> > how to configure the openser.cfg? Should it load dispatcher?
> >
> > Thank you.
> >
> > Regards,
> > Lesley
> >
>
>

___
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users


Re: [Users] Mediaproxy running with Openser

2007-05-18 Thread Lesley Liu

Hi Sergio,

Thanks for your kindly help.
SIP proxy and MEDIA proxy on different PC worked well now.


Regards,
Lesley


2007/5/18, Sergio Gutierrez <[EMAIL PROTECTED]>:


Hi Lesley.

It is good to know it worked.

Yes, you could configure the mediaproxy on another computer.

You still load the mediaproxy module, and configure the socket to your
proxydispatcher (which must be running).

In the config file of it, you define that the mediaproxy is reachable at
some IP address:

This is an snippet of my mediaproxy.ini file:

start = yes
;socket = /var/run/proxydispatcher.sock
listen= X.Y.Z.W
defaultProxy = A.B.C.D
accounting = off

Where A.B.C.D is the machine where mediaproxy is running; it listens on
25060 TCP port.

Kind regards.


On 5/18/07, Lesley Liu <[EMAIL PROTECTED]> wrote:
>
> Hi Sergio,
>
> You are correct, it works after modified the parameter.
> Here comes another question: what if setup mediaproxy on another PC? how
> to configure the openser.cfg? Should it load dispatcher?
>
> Thank you.
>
> Regards,
> Lesley
>


___
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users


Re: [Users] Mediaproxy running with Openser

2007-05-17 Thread Sergio Gutierrez

Hi Lesley.

It is good to know it worked.

Yes, you could configure the mediaproxy on another computer.

You still load the mediaproxy module, and configure the socket to your
proxydispatcher (which must be running).

In the config file of it, you define that the mediaproxy is reachable at
some IP address:

This is an snippet of my mediaproxy.ini file:

start = yes
;socket = /var/run/proxydispatcher.sock
listen=X.Y.Z.W
defaultProxy = A.B.C.D
accounting = off

Where A.B.C.D is the machine where mediaproxy is running; it listens on
25060 TCP port.

Kind regards.


On 5/18/07, Lesley Liu <[EMAIL PROTECTED]> wrote:


Hi Sergio,

You are correct, it works after modified the parameter.
Here comes another question: what if setup mediaproxy on another PC? how
to configure the openser.cfg? Should it load dispatcher?

Thank you.

Regards,
Lesley

___
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users


Re: [Users] Mediaproxy running with Openser

2007-05-17 Thread Lesley Liu

Hi Sergio,

You are correct, it works after modified the parameter.
Here comes another question: what if setup mediaproxy on another PC? how to
configure the openser.cfg? Should it load dispatcher?

Thank you.

Regards,
Lesley
___
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users


Re: [Users] Mediaproxy running with Openser

2007-05-17 Thread Sergio Gutierrez

Hi Lesley.

In the log I can see that your mediaproxy is creating the socket at
/var/run/mediaproxy.sock and you have this configured in openser as

/var/run/proxydispather.sock

I think the error could be that. Try changing the mediaproxy_socket param.

Kind regards.

Sergio G.


On 5/17/07, Lesley Liu <[EMAIL PROTECTED]> wrote:


Hi Sergio,

I restart both mediaproxy and openser, please help to check the log:
May 18 12:22:00 localhost proxydispatcher[2774]: received signal 15
May 18 12:22:01 localhost mediaproxy[2762]: received signal 15
May 18 12:22:01 localhost proxydispatcher[2774]: exiting.
May 18 12:22:01 localhost mediaproxy[2762]: exiting.
May 18 12:22:02 localhost mediaproxy[4858]: Listening for commands on
local socket `/var/run/mediaproxy.sock'
May 18 12:22:02 localhost mediaproxy[4858]: Listening for remote commands
is disabled
May 18 12:22:02 localhost mediaproxy[4858]: Using IP address `172.25.0.71'
for the RTP/RTCP proxy
May 18 12:22:03 localhost proxydispatcher[4861]: Listening for commands on
local socket `/var/run/proxydispatcher.sock'
May 18 12:22:03 localhost proxydispatcher[4861]: Listening for mediaproxy
media timeout requests on 0.0.0.0:25061
May 18 12:22:03 localhost proxydispatcher[4861]: Default mediaproxy server
is on `172.25.0.71:25060'
May 18 12:22:12 localhost openser: WARNING: fix_socket_list: could not
rev. resolve 172.25.0.71
May 18 12:22:12 localhost openser: WARNING: fix_socket_list: could not
rev. resolve 172.25.0.71
May 18 12:22:12 localhost openser: init_tcp: using epoll_lt as the io
watch method (auto detected)
May 18 12:22:12 localhost openser[4867]: INFO: statistics manager
successfully initialized
May 18 12:22:12 localhost openser[4867]: StateLess module - initializing
May 18 12:22:12 localhost openser[4867]: TM - initializing...
May 18 12:22:12 localhost openser[4867]: Maxfwd module- initializing
May 18 12:22:12 localhost openser[4867]: INFO:ul_init_locks: locks array
size 512
May 18 12:22:12 localhost openser[4867]: TextOPS - initializing
May 18 12:22:12 localhost openser[4867]: AUTH module - initializing
May 18 12:22:12 localhost openser[4867]: AUTH_DB module - initializing
May 18 12:22:12 localhost openser[4867]: INFO:textops:hname_fixup: using
hdr type (9) instead of 
May 18 12:22:12 localhost openser[4867]: INFO: udp_init: SO_RCVBUF is
initially 110592
May 18 12:22:12 localhost openser[4867]: INFO: udp_init: SO_RCVBUF is
finally 221184
May 18 12:22:12 localhost openser[4867]: INFO: udp_init: SO_RCVBUF is
initially 110592
May 18 12:22:12 localhost openser[4867]: INFO: udp_init: SO_RCVBUF is
finally 221184
May 18 12:22:12 localhost openser[4867]: ERROR: tcp_init: bind(7,
0x81777ac, 16) on 127.0.0.1:5060 : Address already in use
May 18 12:22:12 localhost openser[4867]: INFO:mi_fifo:mi_destroy: process
hasn't been created -> nothing to kill
May 18 12:22:33 localhost monit[2661]: 'proxydispatcher' process PID
changed to 4861
May 18 12:22:42 localhost /sbin/openser[2816]: Register Incoming
May 18 12:22:42 localhost /sbin/openser[2811]: Register Incoming
May 18 12:22:42 localhost /sbin/openser[2808]: Register Incoming
May 18 12:22:42 localhost /sbin/openser[2814]: Register Incoming
May 18 12:24:30 localhost /sbin/openser[2811]: use media proxy
May 18 12:24:30 localhost /sbin/openser[2811]: error:
mediaproxy/sendMediaproxyCommand(): can't connect to MediaProxy
May 18 12:24:33 localhost monit[2661]: 'proxydispatcher' PID has not
changed
May 18 12:24:36 localhost /sbin/openser[2811]: error:
mediaproxy/sendMediaproxyCommand(): can't connect to MediaProxy


Regards,
Lesley

2007/5/18, Sergio Gutierrez <[EMAIL PROTECTED]>:
>
> Hi again Lesley.
>
> Could you check that starting up the mediaproxy process indeed is
> creating the socket which is referred in openser config.
>
> Kind regards.
>
> Sergio G.
>
>  On 5/17/07, Lesley Liu < [EMAIL PROTECTED]> wrote:
>
> >  Hi Users,
> >
> > I'm trying to setup a mediaproxy 1.7.2 running with operser 1.2.0 on
> > Fedora 6. I can see all service running up. But when I make a call, the SDP
> > does not change the owner address in the INVITE to callee. Openser only
> > report following error:
> > May 18 09:25:51 localhost /sbin/openser[2808]: error:
> > mediaproxy/sendMediaproxyCommand(): can't connect to MediaProxy
> >
> > Configure as attachment, can anyone help?
> > Thanks in advance.
> >
> >
> > Regards,
> > Lesley
> >
> > ___
> > Users mailing list
> > [email protected]
> > http://openser.org/cgi-bin/mailman/listinfo/users
> >
> >
> >
>

___
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users


Re: [Users] Mediaproxy running with Openser

2007-05-17 Thread Lesley Liu

Hi Sergio,

I restart both mediaproxy and openser, please help to check the log:
May 18 12:22:00 localhost proxydispatcher[2774]: received signal 15
May 18 12:22:01 localhost mediaproxy[2762]: received signal 15
May 18 12:22:01 localhost proxydispatcher[2774]: exiting.
May 18 12:22:01 localhost mediaproxy[2762]: exiting.
May 18 12:22:02 localhost mediaproxy[4858]: Listening for commands on local
socket `/var/run/mediaproxy.sock'
May 18 12:22:02 localhost mediaproxy[4858]: Listening for remote commands is
disabled
May 18 12:22:02 localhost mediaproxy[4858]: Using IP address `172.25.0.71'
for the RTP/RTCP proxy
May 18 12:22:03 localhost proxydispatcher[4861]: Listening for commands on
local socket `/var/run/proxydispatcher.sock'
May 18 12:22:03 localhost proxydispatcher[4861]: Listening for mediaproxy
media timeout requests on 0.0.0.0:25061
May 18 12:22:03 localhost proxydispatcher[4861]: Default mediaproxy server
is on `172.25.0.71:25060'
May 18 12:22:12 localhost openser: WARNING: fix_socket_list: could not rev.
resolve 172.25.0.71
May 18 12:22:12 localhost openser: WARNING: fix_socket_list: could not rev.
resolve 172.25.0.71
May 18 12:22:12 localhost openser: init_tcp: using epoll_lt as the io watch
method (auto detected)
May 18 12:22:12 localhost openser[4867]: INFO: statistics manager
successfully initialized
May 18 12:22:12 localhost openser[4867]: StateLess module - initializing
May 18 12:22:12 localhost openser[4867]: TM - initializing...
May 18 12:22:12 localhost openser[4867]: Maxfwd module- initializing
May 18 12:22:12 localhost openser[4867]: INFO:ul_init_locks: locks array
size 512
May 18 12:22:12 localhost openser[4867]: TextOPS - initializing
May 18 12:22:12 localhost openser[4867]: AUTH module - initializing
May 18 12:22:12 localhost openser[4867]: AUTH_DB module - initializing
May 18 12:22:12 localhost openser[4867]: INFO:textops:hname_fixup: using hdr
type (9) instead of 
May 18 12:22:12 localhost openser[4867]: INFO: udp_init: SO_RCVBUF is
initially 110592
May 18 12:22:12 localhost openser[4867]: INFO: udp_init: SO_RCVBUF is
finally 221184
May 18 12:22:12 localhost openser[4867]: INFO: udp_init: SO_RCVBUF is
initially 110592
May 18 12:22:12 localhost openser[4867]: INFO: udp_init: SO_RCVBUF is
finally 221184
May 18 12:22:12 localhost openser[4867]: ERROR: tcp_init: bind(7, 0x81777ac,
16) on 127.0.0.1:5060 : Address already in use
May 18 12:22:12 localhost openser[4867]: INFO:mi_fifo:mi_destroy: process
hasn't been created -> nothing to kill
May 18 12:22:33 localhost monit[2661]: 'proxydispatcher' process PID changed
to 4861
May 18 12:22:42 localhost /sbin/openser[2816]: Register Incoming
May 18 12:22:42 localhost /sbin/openser[2811]: Register Incoming
May 18 12:22:42 localhost /sbin/openser[2808]: Register Incoming
May 18 12:22:42 localhost /sbin/openser[2814]: Register Incoming
May 18 12:24:30 localhost /sbin/openser[2811]: use media proxy
May 18 12:24:30 localhost /sbin/openser[2811]: error:
mediaproxy/sendMediaproxyCommand(): can't connect to MediaProxy
May 18 12:24:33 localhost monit[2661]: 'proxydispatcher' PID has not changed

May 18 12:24:36 localhost /sbin/openser[2811]: error:
mediaproxy/sendMediaproxyCommand(): can't connect to MediaProxy


Regards,
Lesley

2007/5/18, Sergio Gutierrez <[EMAIL PROTECTED]>:


Hi again Lesley.

Could you check that starting up the mediaproxy process indeed is creating
the socket which is referred in openser config.

Kind regards.

Sergio G.

 On 5/17/07, Lesley Liu <[EMAIL PROTECTED]> wrote:

>  Hi Users,
>
> I'm trying to setup a mediaproxy 1.7.2 running with operser 1.2.0 on
> Fedora 6. I can see all service running up. But when I make a call, the SDP
> does not change the owner address in the INVITE to callee. Openser only
> report following error:
> May 18 09:25:51 localhost /sbin/openser[2808]: error:
> mediaproxy/sendMediaproxyCommand(): can't connect to MediaProxy
>
> Configure as attachment, can anyone help?
> Thanks in advance.
>
>
> Regards,
> Lesley
>
> ___
> Users mailing list
> [email protected]
> http://openser.org/cgi-bin/mailman/listinfo/users
>
>
>

___
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users


Re: [Users] Mediaproxy running with Openser

2007-05-17 Thread Sergio Gutierrez

Hi again Lesley.

Could you check that starting up the mediaproxy process indeed is creating
the socket which is referred in openser config.

Kind regards.

Sergio G.

On 5/17/07, Lesley Liu <[EMAIL PROTECTED]> wrote:


Hi Users,

I'm trying to setup a mediaproxy 1.7.2 running with operser 1.2.0 on
Fedora 6. I can see all service running up. But when I make a call, the SDP
does not change the owner address in the INVITE to callee. Openser only
report following error:
May 18 09:25:51 localhost /sbin/openser[2808]: error:
mediaproxy/sendMediaproxyCommand(): can't connect to MediaProxy

Configure as attachment, can anyone help?
Thanks in advance.


Regards,
Lesley

___
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users



___
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users