Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enabling message forwarding in sip_trace #201

Closed
Shyamtechm opened this issue Jun 10, 2015 · 12 comments
Closed

Enabling message forwarding in sip_trace #201

Shyamtechm opened this issue Jun 10, 2015 · 12 comments

Comments

@Shyamtechm
Copy link

Hi all,

I am able to log the SIP messages to database using sip_trace module of kamailio.
But when i tried to forward the SIP messages to duplicate uri ..I am not getting any log file have SIP messages.

Basically i am not able to dump the messages to a log file using duplicate url.

Please suggest.

Thank you,
Shyam

@adubovikov
Copy link
Member

Hi,

do you use Homer project and duplicate messages in HEP ?

Wbr,
Alexandr

@Shyamtechm
Copy link
Author

no...I am using only sip_trace module in kamailio and enabling hep mode in kamailio config.

Please elaborate more on ur suggestions..

Thanks,
Shyam

@adubovikov
Copy link
Member

you have to use Homer project and configure the destination kamailo to be a capture server.

more info is here:

http://www.sipcapture.org
http://github.com/sipcapture/homer

@Shyamtechm
Copy link
Author

Ok...One more question...

If I give the CAPTURE_NODE as 127.0.0.1:9060,
the sip_trace module is still forwarding SIP messages to 127.0.0.1:4060.
But as per my knowledge, it should forward it to 9060.

I will be having both source and destination kamailio on same machine,
in that case, which ports will be used?

All above ports mentioned are UDP ports.

Thanks,
Shyam

@adubovikov
Copy link
Member

can you pastebin your kamailio's config somethere ?

@Shyamtechm
Copy link
Author

I am copying below kamailio cfg contents related to sip_trace.

# Destination, where to send the traffic
modparam("siptrace", "duplicate_uri", sip:127.0.0.1:9060)
# Trace all traffic
modparam("siptrace", "trace_on", 1)
modparam("siptrace", "trace_to_database", 1)
modparam("siptrace", "trace_flag", 22)
modparam("siptrace", "hep_mode_on", 1)
modparam("siptrace", "hep_version", 2)
modparam("siptrace", "traced_user_avp", "$avp(i:2)")
modparam("siptrace", "traced_user_avp", "$avp(s:root)")

The sip_trace module is still forwarding SIP messages to 127.0.0.1:4060.
But as per my knowledge, it should forward it to 9060, then another Kamailio can listen on 9060.

Please suggest.

Thanks,
Shyam

@adubovikov
Copy link
Member

you didn't escape url:

have to be something like this:

modparam("siptrace", "duplicate_uri", "udp:127.0.0.1:9060")

On 11 June 2015 at 13:25, Shyamtechm notifications@github.com wrote:

I am copying below kamailio cfg contents related to sip_trace.
Destination, where to send the traffic

modparam("siptrace", "duplicate_uri", sip:127.0.0.1:9060)
Trace all traffic

modparam("siptrace", "trace_on", 1)
modparam("siptrace", "trace_to_database", 1)
modparam("siptrace", "trace_flag", 22)
modparam("siptrace", "hep_mode_on", 1)
modparam("siptrace", "hep_version", 2)
modparam("siptrace", "traced_user_avp", "$avp(i:2)")
modparam("siptrace", "traced_user_avp", "$avp(s:root)")

The sip_trace module is still forwarding SIP messages to 127.0.0.1:4060.
But as per my knowledge, it should forward it to 9060, then another
Kamailio can listen on 9060.

Please suggest.

Thanks,
Shyam


Reply to this email directly or view it on GitHub
#201 (comment).

@Shyamtechm
Copy link
Author

Actually, I am using

modparam("siptrace", "duplicate_uri", CAPTURE_NODE)

where CAPTURE_NODE is set to "sip:127.0.0.1:9060"

@Shyamtechm
Copy link
Author

Can u please reply on this?...

@Shyamtechm
Copy link
Author

r u there?

@adubovikov
Copy link
Member

@linuxmaniac
Copy link
Member

Not a code issue here. Move this to sr-users@lists.sip-router.org please

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants