[OpenSER-Devel] [ openser-Bugs-1876667 ] carrierroute: ERROR logs during successful call routing

SourceForge.net noreply at sourceforge.net
Thu Jan 24 15:24:12 UTC 2008


Bugs item #1876667, was opened at 2008-01-21 18:36
Message generated for change (Settings changed) made by henningw
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1876667&group_id=139143

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
Group: ver 1.3.x
>Status: Closed
Resolution: None
Priority: 5
Private: No
Submitted By: Ovidiu Sas (osas)
Assigned to: Nobody/Anonymous (nobody)
Summary: carrierroute: ERROR logs during successful call routing

Initial Comment:
During a successful routing of a call, the following logs are showing up:

NOTICE:carrierroute:tree_route_uri: tree blah has id 2 
INFO:carrierroute:get_route_tree_by_id: searching in carrier blah
ERROR:carrierroute:rewrite_uri_recursor: URI or route tree nodes empty, empty rule list
ERROR:carrierroute:rewrite_uri_recursor: empty rule list
INFO:carrierroute:carrier_rewrite_msg: uri <DEST> was rewritten to sip:<DEST>@<IP>

And the call completes normally ...


Regards,
Ovidiu Sas

Note:
# openser -V
version: openser 1.3.0-notls (i386/linux)
flags: STATS: Off, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
svnrevision: 2:3551M
@(#) $Id: main.c 3383 2007-12-14 12:03:24Z jerocu $
main.c compiled on 05:21:50 Jan 18 2008 with gcc 4.1.2

----------------------------------------------------------------------

>Comment By: Henning Westerholt (henningw)
Date: 2008-01-24 15:24

Message:
Logged In: YES 
user_id=337916
Originator: NO

Ok, log level changed to INFO in rev 3575. The log messages in this case
were produced because of the recursive calling of the rewrite_uri_recursor
function. The last function in the recursion chain was able to successful
route the call.

Cheers,

Henning

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1876667&group_id=139143



More information about the Devel mailing list