Re: [SR-Users] sip_capture columns
Hello, Thank you. It's clear now. Regards, Grant ___ Van: sr-users-boun...@lists.sip-router.org [sr-users-boun...@lists.sip-router.org] namens Alexandr Dubovikov [aduv...@googlemail.com] Verzonden: vrijdag 5 april 2013 19:43 Aan: 'Kamailio (SER) - Users Mailing List' Onderwerp: Re: [SR-Users] sip_capture columns Hi, PID_user = P-Asserted-Identity, user part Proto = type of protocol (UDP, TCP) Family = protocol family (IPv6, IPv4) RTP_stat = X-Rtp-Stat / P-Rtp-stat header Node = capture node ID Wbr, Alexandr From: sr-users-boun...@lists.sip-router.org [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Grant Bagdasarian Sent: Thursday, April 04, 2013 4:58 PM To: sr-users@lists.sip-router.org Subject: [SR-Users] sip_capture columns Hello, I couldn’t find any documentation on what the table columns of the sip_capture module are used for. Most of them are straightforward, but I still don’t know what the following columns mean and what values to expect: - PID_user - Proto - Family - Rtp_stat - Type - Node Type has for example values 1 and 2. Im guessing 1 is for requests and 2 is for responses. I hope someone could clear this out for me. Thanks, Grant ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] forward to pseudo var destination
looks like forward core function does not accept pseudo var argument. then i found this: I just committed a patch that allow using send() without any parameter: * http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=8e4db808bf9f94d3ccf0f14ed22e75586afd0f23 if that commit is still valid, it is not reflected by core cookbook: send Send the original SIP message to a specific destination in stateless mode. No changes are applied to received message, no Via header is added. Host can be an IP or hostname. Used protocol: UDP Parameter is mandatory and has string format. Example of usage: send(10.10.10.10:5070); so which way this is? -- juha ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] sip_trace unable to capture after next_branches()
Hi,
try just set the flag without call sip_trace() function.
Wbr,
Alexandr
From: sr-users-boun...@lists.sip-router.org
[mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Ramaseshi reddy
kolli
Sent: Saturday, April 06, 2013 7:29 PM
To: mico...@gmail.com; sr-users@lists.sip-router.org
Subject: Re: [SR-Users] sip_trace unable to capture after next_branches()
hi,
i have set the following flag it is still not capturing outbound SIP
messages.
{
setflag(22)
sip_trace();
}
http://www.mail-archive.com/search?l=sr-users@lists.sip-router.orgq=from:%
22Daniel-Constantin+Mierla%22 Daniel-Constantin Mierla
http://www.mail-archive.com/search?l=sr-users@lists.sip-router.orgq=date:2
0130405 Fri, 05 Apr 2013 00:45:16 -0700
Hello,
On 3/31/13 4:27 PM, Ramaseshi reddy kolli wrote:
Hi,
I am using sip_trace function after next_branches(), it is not capturing
outbound SIP INVITE request can anyone please help me.
iirc, you have to set a flag to trace outgoing messages. the
sip_trace()function just takes the snapshot of processed messages.
Cheers,
Daniel
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Changing Domain in To URI
Hello, On 4/6/13 1:29 AM, qm...@polarismail.com wrote: Mersi mult Daniel! It worked but unfortunately it didn't fix the issue. As I mentioned previously the original setup is like this: Asterisk - Kamailio gateway - carrier. All calls go through just fine The new setup we are trying is: Asterisk - Kamailio load balancer ( dispatch module ) - Kamailio gateway - carrier With this setup the calls come back from the carrier with 500 - Internal error maybe if you paste the ngrep output for such messages we can spot if something is wrong. I've looked at the SIP packets in both cases and they look similar. The only difference is that when going through the load balancer the To is different ( fixed now ) and it has 3 more VIA lines in the header. Where can I start looking at what's causing this ? Three more via headers, added by the load balancer? That means the request is looping back two times? Have you watched the loopback interface? Sound like broken routing logic in the config. Cheers, Daniel Thank you! Quoting Daniel-Constantin Mierla mico...@gmail.com: Changes are not immediately visible, this is the internal design from the time of SER back in 2001 -- I made a FAQ entry with more details: - http://www.kamailio.org/wiki/tutorials/faq/main#why_changes_made_to_headers_or In short, you have to use msg_apply_changes() function after changing headers. Cheers, Daniel On 4/5/13 10:35 PM, Vitaliy Aleksandrov wrote: http://kamailio.org/docs/modules/3.2.x/modules_k/textops.html#id2495808 I use this subst(/^To:.*$/To: $var(new_to)\r/i) where $var(new_to) is a new value of the To header and it works fine on kamailio-3.2.4 Sorry if I repeat myself - I just subscribed properly to the list: if you don't need to change it back for replies and next requests, try: $td = xyz.com; IIRC, that is available on 3.2.x. If not, either you upgrade or use replace functions from textops. Cheers, Daniel Thank you for replying. We tried the direct assignment of $td=xyz.com but the variable doesn't change. We are doing an xlog print right after and an ngrep and we confirmed that the domain part of the URI doesn't change. I also tried a subst() and it's the same problem. I read on the online documentation that the variable is read-only and I figured it can't be changed through these methods. That's why I tried uac_replace_to(). To sum it up, is that variable read-only or not ? ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, April 16-17, 2013, Berlin - http://conference.kamailio.com - ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, April 16-17, 2013, Berlin - http://conference.kamailio.com - ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] sip_trace unable to capture after next_branches()
Hi, Once in a while it captures outbound SIP Invite but it captures always 100 trying, 180 and 200 OK and some times it captures inbound SIP INVITE as well. Thanks Ram ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
