[Serusers] mediaproxy + ser0.8.14 problem

[Arne Scheffer]

Dave,
 
Are you not using nathelper/rtpproxy mixed with mediaproxy ?
 
This will not work as the 2 are not compatible (see docs).
 
I am using only mediaproxy and never see any log info with ..... NAT: .......
 
Arne.

-----Original Message-----
From: serusers-bounces at iptel.org [mailto:serusers-bounces at lists.iptel.org]On Behalf Of Dave Bath
Sent: dinsdag 10 augustus 2004 17:41
To: serusers at lists.iptel.org
Subject: [Serusers] mediaproxy + ser0.8.14 problem



Hey guys... please, does anyone have an thoughts on this?  I have been around and around the houses trying to figure out why as soon as use_media_proxy() is called, ser crashes out.  I have checked permissions (I think!) for the mediaproxy sockets from ser... if I use the util script to generate media sessions all is fine, and they can be seen on the web interface, so I know that bit is working...

 

It just seems that as soon as I call it from within ser, all goes wrong...

 

*A very confused Dave*

 

 

Hi all,

 

Have been trying to get media proxy to work with 0.8.14 and am not having a huge amount of joy.  Basically the route processing seems to be fine, but as soon as ser attempts to actually pass traffic through media proxy it crashes out! 

 

 

Aug  5 15:30:13 sip /sbin/ser[3066]: NAT: Request from RFC Private IP Detected --> mediaproxy flagged

Aug  5 15:30:13 sip /sbin/ser[3066]: VOICEMAIL: VM user detected --> activating VM Flag

Aug  5 15:30:13 sip /sbin/ser[3066]: NAT: Caller is NAT'd (destination offline) --> enable reply processing

Aug  5 15:30:13 sip /sbin/ser[3066]: NAT: Invite received --> enabling media proxy

Aug  5 15:30:13 sip /sbin/ser[3052]: child process 3066 exited by a signal 11

Aug  5 15:30:13 sip /sbin/ser[3052]: core was not generated

Aug  5 15:30:13 sip /sbin/ser[3052]: INFO: terminating due to SIGCHLD

Aug  5 15:30:13 sip /sbin/ser[3186]: INFO: signal 15 received

Aug  5 15:30:13 sip /sbin/ser[3193]: INFO: signal 15 received 

 

(the same is true if the destination is online as well).  

 

I may have a problem with symmetric/asymmetric clients, but I don't think ser should actually crash like that... does anyone have any ideas? 

 

Dave

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20040810/9202843f/attachment.htm>