[SR-Users] sip_trace unable to capture after next_branches()

[Alexandr Dubovikov]

Hi,

 

can you please start ngrep -W byline -l -t port 9060 and check if you really
don't have outgoing messages.

 

Wbr,

Alexandr

 

From: sr-users-bounces at lists.sip-router.org
[mailto:sr-users-bounces at lists.sip-router.org] On Behalf Of Ramaseshi reddy
kolli
Sent: Saturday, April 06, 2013 11:01 PM
To: sr-users at lists.sip-router.org
Subject: Re: [SR-Users] sip_trace unable to capture after next_branches()

 

Hi,

I have tried by setting flag only but still no luck,Here is the
configuration i am using.


# sip trace
modparam("siptrace", "trace_to_database", 0)
modparam("siptrace", "db_url", "")
modparam("siptrace", "duplicate_uri", "sip:homer.com:9060")
modparam("siptrace", "duplicate_with_hep", 1)
modparam("siptrace", "trace_flag", 22)
modparam("siptrace", "trace_on", 1)
#HEPv2 == timestamp will be included to HEP header
modparam("siptrace", "hep_version", 2)


       setflag(22);
        if (!t_relay()) {
            xlog("L_ERR", "CALL $ci - Relay error\n");
            sl_reply_error();
            exit;
        }

Thanks
Ram

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20130406/52ae606c/attachment.htm>