ran into errors while configuration to enable accounting, my xten client recieved "500 I'm terribly sorry, server error occured (1/SL)"
the server logs as follow, Sep 19 15:33:16 dv1 /usr/sbin/ser[2003]: record_route(): Double attempt to record-route Sep 19 15:33:16 dv1 /usr/sbin/ser[2006]: ERROR: t_newtran: transaction already in process 0x422b9c70 Sep 19 15:33:16 dv1 /usr/sbin/ser[1996]: ERROR: t_newtran: transaction already in process 0x422ca290 Sep 19 15:33:16 dv1 /usr/sbin/ser[2000]: ERROR: t_newtran: transaction already in process 0x422c7f70 Sep 19 15:33:17 dv1 /usr/sbin/ser[2003]: ERROR: t_newtran: transaction already in process 0x422ca290 Sep 19 15:33:17 dv1 /usr/sbin/ser[2006]: Warning: sl_send_reply: I won't send a reply for ACK!!
***** ser.cfg
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 (len_gt( max_len )) { sl_send_reply("513", "Message too big"); break; };
# Process record-routing
if (loose_route()) { t_relay(); break; }; # labeled all transaction for accounting setflag(1);
# record-route INVITES to make sure BYEs will visit our server too if (method=="INVITE") record_route();
# forward the request statefuly now; (we need *stateful* forwarding, # because the stateful mode correlates requests with replies and # drops retranmissions; otherwise, we would have to report on # every single message received)
if (!t_relay()) { sl_reply_error(); break; };
# we record-route all messages -- to make sure that # subsequent messages will go through our proxy; that's # particularly good if upstream and downstream entities # use different transport protocol record_route(); # loose-route processing if (loose_route()) { t_relay(); break; };
will someone post a sample ser.cfg with setting of all the HOWTOs section from the Admin guide?
tim
__________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com
What is exactly the problem? The logs tells you what is gone wrong. You try record-route and t_relay twice in your script which makes no sense.
-jiri
At 01:13 AM 9/20/2003, t d wrote:
ran into errors while configuration to enable accounting, my xten client recieved "500 I'm terribly sorry, server error occured (1/SL)"
the server logs as follow, Sep 19 15:33:16 dv1 /usr/sbin/ser[2003]: record_route(): Double attempt to record-route Sep 19 15:33:16 dv1 /usr/sbin/ser[2006]: ERROR: t_newtran: transaction already in process 0x422b9c70 Sep 19 15:33:16 dv1 /usr/sbin/ser[1996]: ERROR: t_newtran: transaction already in process 0x422ca290 Sep 19 15:33:16 dv1 /usr/sbin/ser[2000]: ERROR: t_newtran: transaction already in process 0x422c7f70 Sep 19 15:33:17 dv1 /usr/sbin/ser[2003]: ERROR: t_newtran: transaction already in process 0x422ca290 Sep 19 15:33:17 dv1 /usr/sbin/ser[2006]: Warning: sl_send_reply: I won't send a reply for ACK!!
***** ser.cfg
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 (len_gt( max_len )) { sl_send_reply("513", "Message too big"); break; };
# Process record-routing
if (loose_route()) { t_relay(); break; }; # labeled all transaction for accounting setflag(1); # record-route INVITES to make sure BYEs will visit
our server too if (method=="INVITE") record_route();
# forward the request statefuly now; (we need
*stateful* forwarding, # because the stateful mode correlates requests with replies and # drops retranmissions; otherwise, we would have to report on # every single message received)
if (!t_relay()) { sl_reply_error(); break; }; # we record-route all messages -- to make sure
that # subsequent messages will go through our proxy; that's # particularly good if upstream and downstream entities # use different transport protocol record_route(); # loose-route processing if (loose_route()) { t_relay(); break; };
will someone post a sample ser.cfg with setting of all the HOWTOs section from the Admin guide?
tim
Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-- Jiri Kuthan http://iptel.org/~jiri/
Hi Jiri,
thanks for pointing that out, i took off the second t_relay and record-route but recieve a different error
/usr/sbin/ser[1574]: ERROR: t_newtran: transaction already in process 0x422c2f18 Sep 19 18:07:48 dv1 /usr/sbin/ser[1572]: Warning: sl_send_reply: I won't send a reply for ACK!!
appreciate your help!
tim --- Jiri Kuthan jiri@iptel.org wrote:
What is exactly the problem? The logs tells you what is gone wrong. You try record-route and t_relay twice in your script which makes no sense.
-jiri
At 01:13 AM 9/20/2003, t d wrote:
ran into errors while configuration to enable accounting, my xten client recieved "500 I'm
terribly
sorry, server error occured (1/SL)"
the server logs as follow, Sep 19 15:33:16 dv1 /usr/sbin/ser[2003]: record_route(): Double attempt to record-route Sep 19 15:33:16 dv1 /usr/sbin/ser[2006]: ERROR: t_newtran: transaction already in process
0x422b9c70
Sep 19 15:33:16 dv1 /usr/sbin/ser[1996]: ERROR: t_newtran: transaction already in process
0x422ca290
Sep 19 15:33:16 dv1 /usr/sbin/ser[2000]: ERROR: t_newtran: transaction already in process
0x422c7f70
Sep 19 15:33:17 dv1 /usr/sbin/ser[2003]: ERROR: t_newtran: transaction already in process
0x422ca290
Sep 19 15:33:17 dv1 /usr/sbin/ser[2006]: Warning: sl_send_reply: I won't send a reply for ACK!!
***** ser.cfg
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 (len_gt( max_len )) { sl_send_reply("513", "Message too
big"); break; };
# Process record-routing
if (loose_route()) { t_relay(); break; }; # labeled all transaction for accounting setflag(1); # record-route INVITES to make sure BYEs
will visit
our server too if (method=="INVITE") record_route();
# forward the request statefuly now; (we
need
*stateful* forwarding, # because the stateful mode correlates requests with replies and # drops retranmissions; otherwise, we would have to report on # every single message received)
if (!t_relay()) { sl_reply_error(); break; }; # we record-route all messages -- to make
sure
that # subsequent messages will go through our proxy; that's # particularly good if upstream and
downstream
entities # use different transport protocol record_route(); # loose-route processing if (loose_route()) { t_relay(); break; };
will someone post a sample ser.cfg with setting of
all
the HOWTOs section from the Admin guide?
tim
Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site
design software
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-- Jiri Kuthan http://iptel.org/~jiri/
__________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com