Your config calls fix_contact twice, this is why is crashing. Until this is fixed please follow the guidelines in ser.cfg example from
http://cvs.berlios.de/cgi-bin/viewcvs.cgi/*checkout*/ser/sip_router/ modules/mediaproxy/config/ser.cfg?rev=HEAD&content-type=text/plain
Adrian
here is my config any help at all work be great
route{
# initial sanity checks -- messages with # max_forwards==0, or excessively long requests if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); break; }; if (msg:len >= max_len ) { sl_send_reply("513", "Message too big"); break; };
if (method == "REGISTER" || ! search("^Record-Route:")) { if (is_from_local()) { log("LOG: Someone trying to register from private IP, rewriting\n"); if (client_nat_test("3")) { setflag(2); force_rport(); fix_contact(); };
}; };
if (method == "REGISTER") { save("location"); break; };
#if (method == "INVITE") #{ # if("!(is_from_local() || is_uri_host_local())) # { # sl_send_reply("403", "Relaying is forbidden"); # break; # }; # t_on_failure("1"); #} #else if (method == "BYE" || method == "CANCEL") #{ # end_media_session(); #};
if (loose_route()) { if (method == "INVITE" || method == "ACK") { use_media_proxy(); };
t_relay(); break; };
# Force subsequent messages to pass through this proxy if (method == "INVITE") { record_route(); };
if (client_nat_test("3") && !search("^Record-Route:")) { # Mark as NAT'ED force_rport(); fix_contact(); };
if (method == "INVITE") { t_on_reply("1"); };
#if (is_uri_host_local()) #{ # if(!lookup("location")) # { # sl_send_reply("404", "User not found"); # break; # }; #};
if (method == "INVITE" || method == "ACK") { use_media_proxy(); };
if (uri=~"^sip:7[0-9]{3}@.*") { if (is_user_in("from", "pbx")) { # if (isflagset(6)) #{ rewritehostport("*.*.*.*"); forward(uri:host, uri:port); xlog("L_ERR", "LOG - method<%rm> uri<%ru> from<%fu> to<%tu>\n"); log (1,"PSTN Call\n"); setflag(2); break; #}; }; };
if (!t_relay()) { if (method == "INVITE" || method == "ACK") { end_media_session(); }; sl_reply_error(); }; }
failure_route[1] { end_media_session(); }
onreply_route[1] { if (status=~"(183)|(2[0-9][0-9])") { if (client_nat_test("1")) { fix_contact(); }; use_media_proxy(); }; }
-----Original Message----- From: Adrian Georgescu [SMTP:ag@ag-projects.com] Sent: 06 August 2004 12:11 To: Sean Lowry Cc: serusers@lists.iptel.org Subject: Re: [Serusers] mediaproxy + ser0.8.14 problem
That sample configuration is OK. Your problem must be searched elsewhere.
On Aug 6, 2004, at 12:51 PM, Sean Lowry wrote:
Umm very strange i used the example.cfg and inside there it has the fix_contact in the registration, and in the client_nat_test and also in te onreply_route.
so what is the correct format if this is wrong.
Sean
-----Original Message----- From: Adrian Georgescu [SMTP:ag@ag-projects.com] Sent: 06 August 2004 11:55 To: dave@fuuz.com Cc: serusers@lists.iptel.org Subject: [Serusers] mediaproxy + ser0.8.14 problem
See http://lists.iptel.org/pipermail/serusers/2004-August/010420.html
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 << File: ATT13254.txt >>