Ok, maybe I’ve been misunderstanding things a little… with the mediaproxy module do you need to specify an outbound proxy? I was under the impression that if you were registered against SER, and ser has provision for detecting NAT’d clients and forwarding them off to mediaproxy… is this correct? Or is it necessary to specify the ser IP again as an outbound proxy?

Many thanks,

Dave

---

From: Dave Bath
Sent: 05 August 2004 15:39
To: serusers@lists.iptel.org
Subject: mediaproxy + ser0.8.14 problem

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