[Serusers] Unable to complete calls with 0.8.13
Nils Ohlmeier
nils at iptel.org
Fri Jan 30 04:50:05 CET 2004
Now you moved the bracket to much to the end and thus the ACKs are probably
not transported because they do not hit any forward or t_ call.
BTW why dont you simply use a new fresh working default ser config (i dont see
too much changes to our defautl script)
Nils
On Friday 30 January 2004 04:45, Andres wrote:
> Ok...I removed it and added it at the bottom (or else SER says there is
> an error). But still the same problem. Here is the new config:
>
> 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;
> };
>
> # 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;
> };
> # if the request is for other domain use UsrLoc
> # (in case, it does not work, use the following command
> # with proper names and addresses in it)
> if (uri==myself) {
> if (method=="REGISTER") {
> save("location");
> break;
> };
> # native SIP destinations are handled using our USRLOC DB
> if (!lookup("location")) {
> sl_send_reply("404", "Not Found");
> break;
> };
>
>
insert here };
> # forward to current uri now; use stateful forwarding; that
> # works reliably even if we forward from TCP to UDP
> if (!t_relay()) {
> sl_reply_error();
> };
> }
> }
^^^
remove
More information about the sr-users
mailing list