from:"Alexandr Dubovikov"

Re: [SR-Users] [sr-dev] FOSDEM 2017

2017-01-20 Thread Alexandr Dubovikov

Hi Daniel,

IMHO we can do like last year. It was good organized.

Wbr,
Alexandr

On 20 January 2017 at 11:00, Daniel-Constantin Mierla 
wrote:

> Hello,
>
> another edition of FOSDEM is approaching, about 2 weeks left:
>
>   - https://fosdem.org/2017/
>
> Couple of devs and many Kamailio friends will be around.
>
> Like past year, there is a Realtime Communications devroom, this edition
> on Sunday. Very interesting presentation for our ecosystem: Olle giving
> a presentation about IPv4/IPv6, Inaki introducing its SFU media server
> project, Jose talking about JsSIP, Daniel debating about fundraising
> FreeRTC, Lorenzo with Janus SIP-WebRTC gateway, the other Lorenzo with
> Homer Sipcature, Saul with Jitsi, Dan with cgrates, Matt with Asterisk,
> Giovanni with FreeSwitch... Schedule at:
>
>   - https://fosdem.org/2017/schedule/track/real_time_communications/
>
> On Sunday morning, part of Lua devroom, I will present about using Lua
> for building RTC services with Kamailio:
>
>   - https://fosdem.org/2017/schedule/track/lua/
>   - https://fosdem.org/2017/schedule/event/luartcserviceskamailio/
>
> During the past editions we organized a dinner on Saturday evening.
> Shall we attempt to do it again in advance this year? Or should we do it
> on spot based on the weather and mood at the end of Saturday?
>
> Cheers,
> Daniel
>
> --
> Daniel-Constantin Mierla
> www.twitter.com/miconda -- www.linkedin.com/in/miconda
> Kamailio Advanced Training - Mar 6-8 (Europe) and Mar 20-22 (USA) -
> www.asipto.com
> Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com
>
>
> ___
> sr-dev mailing list
> sr-...@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
>
___
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] Fosdem 2015

2015-01-27 Thread Alexandr Dubovikov

yep, Emil is waiting for us :-)

Regards,
Alexandr

2015-01-26 14:53 GMT+01:00 Daniel-Constantin Mierla mico...@gmail.com:

  Very likely I will be around at Fosdem as well this year and going for
 the event in the evening, if it takes place. Have you discussed with Jitsi
 guys?

 Cheers,
 Daniel


 On 17/01/15 16:47, Alexandr Dubovikov wrote:

 so, same event like last year at Beer Mania. Enjoy!

 2015-01-16 21:12 GMT+01:00 Alexandr Dubovikov aduv...@googlemail.com:

  ok, Torsten Schweizer, Heino Klier and I will be at Fosdem. We can make
 same beer event like last year, together with Emil and Jitsi Co.




 2015-01-15 12:47 GMT+01:00 DanB danb.li...@gmail.com:

 I will be there this year also, if someone prepares an event.

 DanB.


 ___
 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 
 listsr-us...@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


 --
 Daniel-Constantin Mierlahttp://twitter.com/#!/miconda - 
 http://www.linkedin.com/in/miconda


___
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] Fosdem 2015

2015-01-17 Thread Alexandr Dubovikov

so, same event like last year at Beer Mania. Enjoy!

2015-01-16 21:12 GMT+01:00 Alexandr Dubovikov aduv...@googlemail.com:

 ok, Torsten Schweizer, Heino Klier and I will be at Fosdem. We can make
 same beer event like last year, together with Emil and Jitsi Co.




 2015-01-15 12:47 GMT+01:00 DanB danb.li...@gmail.com:

 I will be there this year also, if someone prepares an event.

 DanB.


 ___
 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

Re: [SR-Users] Fosdem 2015

2015-01-16 Thread Alexandr Dubovikov

ok, Torsten Schweizer, Heino Klier and I will be at Fosdem. We can make
same beer event like last year, together with Emil and Jitsi Co.




2015-01-15 12:47 GMT+01:00 DanB danb.li...@gmail.com:

 I will be there this year also, if someone prepares an event.

 DanB.


 ___
 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

[SR-Users] Fosdem 2015

2015-01-14 Thread Alexandr Dubovikov

Hello everybody,

what is about Fosdem this year ? Who is going there ?

Wbr,
Alexandr
___
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] Montoring/Reporting Solution - Commercial/Open Source

2013-04-26 Thread Alexandr Dubovikov


4/25/2013 8:52 AM, Ali Jawad wrote:
Homer is a great product, I can wait for version 4 to come out. But 
currently it lacks the advanced reporting I need.  I will check in the 
business mailing list.


you can check Homer 3.5.  We have implemented there advanced statistics 
and alarms.


branch webhomer_3.5

Wbr,
Alexandr



On Wed, Apr 24, 2013 at 5:39 PM, Henning Westerholt h...@kamailio.org 
mailto:h...@kamailio.org wrote:


Am Mittwoch, 24. April 2013, 17:36:46 schrieb Ali Jawad:
 Any input please ?

 On Tue, Apr 23, 2013 at 2:31 PM, Ali Jawad
ali.ja...@splendor.net mailto:ali.ja...@splendor.net wrote:
  Hi
  I am in need of a solution that does provide me with advanced
graphing and
  report for Kamailio, I.e. ASR/ACD over day/month/destination
etc. with
  tresholds and alerts. Does anyone know about a solution that
is compatible
  with Kamailio and does this ?

Hello,

maybe you'd like to ask at the business list about a commercial
offering, if
the available open source software like homer or siremis does not
fulfil your
needs.

http://lists.kamailio.org/cgi-bin/mailman/listinfo/business

Best regards,

Henning Westerholt




--
*Ali Jawad
*
*Information Systems Manager
CISSP - PMP - ITIL V3 - RHCE - VCP - C|EH - CCNA - MCSA
*
*Splendor Telecom (www.splendor.net http://www.splendor.net/)
Beirut, Lebanon
Phone: +9611373725/ext 116
FAX: +9611375554

*


___
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

Re: [SR-Users] siptrace source ip causes martians

2013-04-23 Thread Alexandr Dubovikov


4/23/2013 11:41 AM, Thilo Bangert wrote:

On Monday, April 22, 2013 10:53:42 PM Alexandr Dubovikov wrote:

Hi Thilio,

no, siptrace doesn't support this, but I think you can do it as ip route

i.e: http://lartc.org/howto/lartc.rpdb.multiple-links.html

thanks, but i think i'll go for a dedicated captagent instead, if that
works...


yes, it can works with a separate captagent.

Wbr,
Alexandr



Wbr,
Alexandr

4/22/2013 10:14 AM, Thilo Bangert wrote:

Hi,

i have a kamailio instance, which is connected to two subnets (A and B)
and
exchanges sip messages between them. I have setup the siptrace module to
send hep tracing messages of all sip messages to a host in subnet B.

This works really well for sip messages arriving on the IP of subnet B -
for those arriving on subnet A however it doesnt work. The hep messages
have the interface address of subnet A set as source address.
Since the machine receiving the HEP messages also is connected to both
subnet A and B, these messages are (correctly) rejected as martians and
never reach the sipcapture module on that host.

this is on kamailio 3.3.4.

Is there a way to force the source IP of outgoing HEP messages in the
siptrace module?

thanks
kind regards
Thilo

___
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

___
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

Re: [SR-Users] siptrace source ip causes martians

2013-04-22 Thread Alexandr Dubovikov


Hi Thilio,

no, siptrace doesn't support this, but I think you can do it as ip route

i.e: http://lartc.org/howto/lartc.rpdb.multiple-links.html

Wbr,
Alexandr

4/22/2013 10:14 AM, Thilo Bangert wrote:

Hi,

i have a kamailio instance, which is connected to two subnets (A and B) and
exchanges sip messages between them. I have setup the siptrace module to send
hep tracing messages of all sip messages to a host in subnet B.

This works really well for sip messages arriving on the IP of subnet B - for
those arriving on subnet A however it doesnt work. The hep messages have the
interface address of subnet A set as source address.
Since the machine receiving the HEP messages also is connected to both subnet
A and B, these messages are (correctly) rejected as martians and never reach
the sipcapture module on that host.

this is on kamailio 3.3.4.

Is there a way to force the source IP of outgoing HEP messages in the siptrace
module?

thanks
kind regards
Thilo

___
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

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

2013-04-06 Thread Alexandr Dubovikov

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] sip_capture columns

2013-04-05 Thread Alexandr Dubovikov

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

Re: [SR-Users] Homer / Kamailio / Freeswitch

2013-03-28 Thread Alexandr Dubovikov

Hi,

can you show your sofia's config ?

btw, better send this question to homer's list.

Wbr,
Alexandr

-Original Message-
From: sr-users-boun...@lists.sip-router.org
[mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Antonio Teixeira
Sent: Thursday, March 28, 2013 6:37 PM
To: sr-users@lists.sip-router.org
Subject: [SR-Users] Homer / Kamailio / Freeswitch

Hello.

First of all i just did a fresh install of Homer and this thing is perfect
only really missing the RTP analysis.
Anyway I have a Freeswitch PBX with several internal profiles and also
external profiles binded into external Ips ( Public not Private).

Capture on the private network profiles works flawlessly when i try to track
public interface , calls going into the VOIP Operators , there are no
entries 

So :

Public call data inside the DB , No

Freeswitch sending data into Kamailio , Yes

TCPDUMP on Kamailio Shows SIP Data from the PBX  Interface , Yes ,

Kamailio complains with
Mar 28 08:30:27 debian /usr/local/sbin/kamailio[23709]: ERROR: core
[parser/msg_parser.c:705]: ERROR: parse_msg: message=#015#012 Mar 28
08:30:27 debian /usr/local/sbin/kamailio[23709]: ERROR: core
[receive.c:146]: ERROR: receive_msg: parse_msg failed

Problem Scenario :

A call from a phone inside the network 1.1.1.0 Into the PBX 1.1.1.1 is
tracked by Homer a call from the external IP Binded into the PBX lets say
something like 80.0.80.8(External Public IP) , Call not tracked and Kamailio
complains with parse_msg_error.

Helper Data :

Uname
Linux debian 2.6.32-5-amd64 #1 SMP Mon Feb 25 00:26:11 UTC 2013 x86_64
GNU/Linux

LSB
Distributor ID: Debian
Description:Debian GNU/Linux 6.0.7 (squeeze)
Release:6.0.7
Codename:   squeeze

Kamailio as of TODAY  from GIT
Homer as of TODAY from GIT
WebHomer 3.3.1 From GIT Also

Using the SOFIA SIPTRACE , problem shows both using the global sip trace or
individual profile siptrace.

Thanks for your time
Antonio

___
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

Re: [SR-Users] siptrace/sipcapture and MSRP

2013-02-15 Thread Alexandr Dubovikov

Peter, before need to implement HEPv3 into siptrace module. Currently it has
only HEPv1/v2 support.

Can you please contact me in gtalk, we can do it together step by step.


Wbr,
Alexandr

-Original Message-
From: sr-users-boun...@lists.sip-router.org
[mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Peter Dunkley
Sent: Friday, February 15, 2013 5:02 PM
To: sr-users@lists.sip-router.org
Subject: Re: [SR-Users] siptrace/sipcapture and MSRP

Actually, the sipcapture module does use the Kamailio message parsing.  
It looks like only a few small changes will be required to make it recognise
and handle HTTP and MSRP.

I will look into doing this.

Regards,

Peter

On 15/02/13 15:56, Peter Dunkley wrote:
 OK.  So sipcapture parses the messages itself instead of using the 
 Kamailio's message parsing (which does handle HTTP and MSRP)?

 Regards,

 Peter

 On 15/02/13 15:47, Dragos Dinu wrote:
 Sipcapture can't handle it, because it parses the data as SIP message.

 If sipcapture would be able to handle it and get it into the DB, 
 Webhomer will be able to show it, because it shows all the entries 
 that you write into the DB.
 You can, for example, write the MSRP message into the 'msg' column of 
 the table and leave all the other sip-related columns blank. Webhomer 
 will display the data just like that. Think of Webhomer as a 
 user-interface to see everything that is in there (and to search data).

 Hope it helps,

 Dragos

 On 02/15/2013 05:30 PM, Peter Dunkley wrote:
 I know that the HEP3 protocol is designed to handle different 
 message types, so I am curious as to whether the implementation of 
 the capture node can handle it.

 Also, if the capture node can handle it and it does go into the DB 
 will it cause problems for webhomer, or will webhomer simply ignore 
 non-SIP entries (which would be absolutely fine for my use-case)?

 Regards,

 Peter


 On 15/02/13 15:22, Dragos Dinu wrote:
 Hi,

 As far as I know, although making siptrace encapsulate different 
 types of messages is not something very difficult, the sipcapture 
 module is developed to write SIP messages into database.

 Webhomer 3 reads SIP-related data from DB, so it displays only SIP.

 Regards,
 Dragos

 On 02/15/2013 04:45 PM, Peter Dunkley wrote:
 Hello,

 Is there any reason why I couldn't use the existing siptrace() 
 function in event_route[msrp:frame-in] to relay all MSRP messages 
 to a SIP Capture node?

 Will the SIP Capture node handle receiving these messages?

 What will end up in the WebHomer display in these cases?

 Regards,

 Peter

 ___
 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

 ___
 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


 ___
 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


___
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] Segmentation fault in sip-capture

2012-12-05 Thread Alexandr Dubovikov

something in tcp stack, maybe need initialize some modules before. But who
cares ? :-)

 

regards,

Alexandr

 

From: sr-users-boun...@lists.sip-router.org
[mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Owen Lynch
Sent: Tuesday, December 04, 2012 9:21 PM
To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users
Mailing List
Subject: Re: [SR-Users] Segmentation fault in sip-capture

 

Hi Alexandr,

 

thanks, that seems to have fixed it. But I am curious, why should having TLS
enabled cause kamailio to crash in this configuration?

 

Owen

 

On 3 December 2012 22:27, Alexandr Dubovikov aduv...@googlemail.com wrote:

Hi Owen,

 

you don't need TLS for sip capturing, please undef WITH_TLS and try again,

 

Wbr,

Alexandr

 

2012/12/3 Owen Lynch owen.ly...@paragon.co.nz

 

 

On 3 December 2012 10:20, Alexandr Dubovikov aduv...@googlemail.com wrote:

Hi Olwen,

 

siptrace use UDP to send HEP packets, but here is a problem in tcp stack.

Can you please provide your config for the capture node and config for
remote kamailio.

 

Wbr,

Alexandr

 

 

From: sr-users-boun...@lists.sip-router.org
[mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Owen Lynch
Sent: Sunday, December 02, 2012 9:43 PM
To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users
Mailing List
Subject: [SR-Users] Segmentation fault in sip-capture

 

Hi,

 

I am running Kamailio 3.3 as a Homer capture agent, the sip-capture module
receives HEP packets from a sip-trace module in a remote kamailio instance.
Periodically the capture agent dies. The log and core dump suggest the
initial problem is an invalid HEP msg received, but kamailio crashes when
trying to send an error reply. Can anyone shed any light on this?

 

Thanks,

Owen Lynch

 

Back  trace:

Program terminated with signal 11, Segmentation fault.

#0  0x0813c916 in send2child (tcpconn=0xb55c1c60) at tcp_main.c:3967

3967tcp_main.c: No such file or directory.

in tcp_main.c

Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.80.el6.i686
keyutils-libs-1.4-4.el6.i686 krb5-libs-1.9-33.el6.i686
libcom_err-1.41.12-12.el6.i686 libselinux-2.0.94-5.3.el6.i686
mysql-libs-5.1.61-4.el6.i686 nss-softokn-freebl-3.12.9-11.el6.i686
openssl-1.0.0-20.el6_2.5.i686 zlib-1.2.3-27.el6.i686

(gdb) bt

#0  0x0813c916 in send2child (tcpconn=0xb55c1c60) at tcp_main.c:3967

#1  0x08136e78 in handle_tcpconn_ev (fm=value optimized out, ev=value
optimized out,

idx=value optimized out) at tcp_main.c:4310

#2  handle_io (fm=value optimized out, ev=value optimized out,
idx=value optimized out)

at tcp_main.c:4362

#3  0x0813ea3c in io_wait_loop_epoll () at io_wait.h:1092

#4  tcp_main_loop () at tcp_main.c:4656

#5  0x080a502b in main_loop () at main.c:1727

#6  0x080a6c00 in main (argc=11, argv=0xbfeafd14) at main.c:2546

 

Log:

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: : core
[pass_fd.c:288]: ERROR: receive_fd: recvmsg on 10 failed: Connection reset
by peer

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: ERROR: core
[tcp_main.c:2347]: BUG: tcp_send: failed to get fd(receive_fd): Connection
reset by peer (104)

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: ERROR: sl
[../../forward.h:193]: msg_send: ERROR: tcp_send failed

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: ERROR: ***
cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=704 a=3 n=exit

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
[usr_avp.c:644]: DEBUG:destroy_avp_list: destroying list (nil)

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
[usr_avp.c:644]: DEBUG:destroy_avp_list: destroying list (nil)

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
[usr_avp.c:644]: DEBUG:destroy_avp_list: destroying list (nil)

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
[usr_avp.c:644]: DEBUG:destroy_avp_list: destroying list (nil)

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
[usr_avp.c:644]: DEBUG:destroy_avp_list: destroying list (nil)

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
[usr_avp.c:644]: DEBUG:destroy_avp_list: destroying list (nil)

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
[xavp.c:365]: destroying xavp list (nil)

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
[receive.c:293]: receive_msg: cleaning up

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: ERROR: sipcapture
[sipcapture.c:682]: ERROR: sipcapture:hep_msg_received: not supported
version or bad length: v:[10] l:[10] vs [40]

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
[parser/msg_parser.c:634]: SIP Reply  (status):

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
[parser/msg_parser.c:636]:  version: SIP/2.0

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core

Re: [SR-Users] Segmentation fault in sip-capture

2012-12-03 Thread Alexandr Dubovikov

Hi Owen,

you don't need TLS for sip capturing, please undef WITH_TLS and try again,

Wbr,
Alexandr

2012/12/3 Owen Lynch owen.ly...@paragon.co.nz




 On 3 December 2012 10:20, Alexandr Dubovikov aduv...@googlemail.comwrote:

 Hi Olwen,

 ** **

 siptrace use UDP to send HEP packets, but here is a problem in tcp stack.
 

 Can you please provide your config for the capture node and config for
 remote kamailio.

 ** **

 Wbr,

 Alexandr

 ** **

 ** **

 *From:* sr-users-boun...@lists.sip-router.org [mailto:
 sr-users-boun...@lists.sip-router.org] *On Behalf Of *Owen Lynch
 *Sent:* Sunday, December 02, 2012 9:43 PM
 *To:* SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -
 Users Mailing List
 *Subject:* [SR-Users] Segmentation fault in sip-capture

 ** **

 Hi,

 ** **

 I am running Kamailio 3.3 as a Homer capture agent, the sip-capture
 module receives HEP packets from a sip-trace module in a remote kamailio
 instance. Periodically the capture agent dies. The log and core dump
 suggest the initial problem is an invalid HEP msg received, but kamailio
 crashes when trying to send an error reply. Can anyone shed any light on
 this?

 ** **

 Thanks,

 Owen Lynch

 ** **

 Back  trace:

 Program terminated with signal 11, Segmentation fault.

 #0  0x0813c916 in send2child (tcpconn=0xb55c1c60) at tcp_main.c:3967

 3967tcp_main.c: No such file or directory.

 in tcp_main.c

 Missing separate debuginfos, use: debuginfo-install
 glibc-2.12-1.80.el6.i686 keyutils-libs-1.4-4.el6.i686
 krb5-libs-1.9-33.el6.i686 libcom_err-1.41.12-12.el6.i686
 libselinux-2.0.94-5.3.el6.i686 mysql-libs-5.1.61-4.el6.i686
 nss-softokn-freebl-3.12.9-11.el6.i686 openssl-1.0.0-20.el6_2.5.i686
 zlib-1.2.3-27.el6.i686

 (gdb) bt

 #0  0x0813c916 in send2child (tcpconn=0xb55c1c60) at tcp_main.c:3967

 #1  0x08136e78 in handle_tcpconn_ev (fm=value optimized out, ev=value
 optimized out,

 idx=value optimized out) at tcp_main.c:4310

 #2  handle_io (fm=value optimized out, ev=value optimized out,
 idx=value optimized out)

 at tcp_main.c:4362

 #3  0x0813ea3c in io_wait_loop_epoll () at io_wait.h:1092

 #4  tcp_main_loop () at tcp_main.c:4656

 #5  0x080a502b in main_loop () at main.c:1727

 #6  0x080a6c00 in main (argc=11, argv=0xbfeafd14) at main.c:2546

 ** **

 Log:

 Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: : core
 [pass_fd.c:288]: ERROR: receive_fd: recvmsg on 10 failed: Connection reset
 by peer

 Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: ERROR: core
 [tcp_main.c:2347]: BUG: tcp_send: failed to get fd(receive_fd): Connection
 reset by peer (104)

 Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: ERROR: sl
 [../../forward.h:193]: msg_send: ERROR: tcp_send failed

 Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: ERROR: ***
 cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=704 a=3 n=exit

 Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
 [usr_avp.c:644]: DEBUG:destroy_avp_list: destroying list (nil)

 Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
 [usr_avp.c:644]: DEBUG:destroy_avp_list: destroying list (nil)

 Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
 [usr_avp.c:644]: DEBUG:destroy_avp_list: destroying list (nil)

 Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
 [usr_avp.c:644]: DEBUG:destroy_avp_list: destroying list (nil)

 Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
 [usr_avp.c:644]: DEBUG:destroy_avp_list: destroying list (nil)

 Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
 [usr_avp.c:644]: DEBUG:destroy_avp_list: destroying list (nil)

 Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
 [xavp.c:365]: destroying xavp list (nil)

 Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
 [receive.c:293]: receive_msg: cleaning up

 Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: ERROR:
 sipcapture [sipcapture.c:682]: ERROR: sipcapture:hep_msg_received: not
 supported version or bad length: v:[10] l:[10] vs [40]

 Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
 [parser/msg_parser.c:634]: SIP Reply  (status):

 Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
 [parser/msg_parser.c:636]:  version: SIP/2.0

 Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
 [parser/msg_parser.c:638]:  status:  500

 Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
 [parser/msg_parser.c:640]:  reason:  Invalid CSeq

 Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
 [parser/parse_via.c:1286]: Found param type 234, received =
 yadayadayada; state=6

 Nov 28 12:24:24 flowadmin /usr

Re: [SR-Users] Segmentation fault in sip-capture

2012-12-02 Thread Alexandr Dubovikov

Hi Olwen,

 

siptrace use UDP to send HEP packets, but here is a problem in tcp stack.

Can you please provide your config for the capture node and config for
remote kamailio.

 

Wbr,

Alexandr

 

 

From: sr-users-boun...@lists.sip-router.org
[mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Owen Lynch
Sent: Sunday, December 02, 2012 9:43 PM
To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users
Mailing List
Subject: [SR-Users] Segmentation fault in sip-capture

 

Hi,

 

I am running Kamailio 3.3 as a Homer capture agent, the sip-capture module
receives HEP packets from a sip-trace module in a remote kamailio instance.
Periodically the capture agent dies. The log and core dump suggest the
initial problem is an invalid HEP msg received, but kamailio crashes when
trying to send an error reply. Can anyone shed any light on this?

 

Thanks,

Owen Lynch

 

Back  trace:

Program terminated with signal 11, Segmentation fault.

#0  0x0813c916 in send2child (tcpconn=0xb55c1c60) at tcp_main.c:3967

3967tcp_main.c: No such file or directory.

in tcp_main.c

Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.80.el6.i686
keyutils-libs-1.4-4.el6.i686 krb5-libs-1.9-33.el6.i686
libcom_err-1.41.12-12.el6.i686 libselinux-2.0.94-5.3.el6.i686
mysql-libs-5.1.61-4.el6.i686 nss-softokn-freebl-3.12.9-11.el6.i686
openssl-1.0.0-20.el6_2.5.i686 zlib-1.2.3-27.el6.i686

(gdb) bt

#0  0x0813c916 in send2child (tcpconn=0xb55c1c60) at tcp_main.c:3967

#1  0x08136e78 in handle_tcpconn_ev (fm=value optimized out, ev=value
optimized out,

idx=value optimized out) at tcp_main.c:4310

#2  handle_io (fm=value optimized out, ev=value optimized out,
idx=value optimized out)

at tcp_main.c:4362

#3  0x0813ea3c in io_wait_loop_epoll () at io_wait.h:1092

#4  tcp_main_loop () at tcp_main.c:4656

#5  0x080a502b in main_loop () at main.c:1727

#6  0x080a6c00 in main (argc=11, argv=0xbfeafd14) at main.c:2546

 

Log:

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: : core
[pass_fd.c:288]: ERROR: receive_fd: recvmsg on 10 failed: Connection reset
by peer

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: ERROR: core
[tcp_main.c:2347]: BUG: tcp_send: failed to get fd(receive_fd): Connection
reset by peer (104)

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: ERROR: sl
[../../forward.h:193]: msg_send: ERROR: tcp_send failed

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: ERROR: ***
cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=704 a=3 n=exit

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
[usr_avp.c:644]: DEBUG:destroy_avp_list: destroying list (nil)

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
[usr_avp.c:644]: DEBUG:destroy_avp_list: destroying list (nil)

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
[usr_avp.c:644]: DEBUG:destroy_avp_list: destroying list (nil)

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
[usr_avp.c:644]: DEBUG:destroy_avp_list: destroying list (nil)

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
[usr_avp.c:644]: DEBUG:destroy_avp_list: destroying list (nil)

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
[usr_avp.c:644]: DEBUG:destroy_avp_list: destroying list (nil)

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
[xavp.c:365]: destroying xavp list (nil)

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
[receive.c:293]: receive_msg: cleaning up

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: ERROR: sipcapture
[sipcapture.c:682]: ERROR: sipcapture:hep_msg_received: not supported
version or bad length: v:[10] l:[10] vs [40]

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
[parser/msg_parser.c:634]: SIP Reply  (status):

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
[parser/msg_parser.c:636]:  version: SIP/2.0

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
[parser/msg_parser.c:638]:  status:  500

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
[parser/msg_parser.c:640]:  reason:  Invalid CSeq

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
[parser/parse_via.c:1286]: Found param type 234, received =
yadayadayada; state=6

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
[parser/parse_via.c:1286]: Found param type 232, branch =
z9hG4bK2348.d1620f62.0; state=16

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
[parser/parse_via.c:2561]: end of header reached, state=5

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
[parser/msg_parser.c:511]: parse_headers: Via found, flags=2

Nov 28 12:24:24 flowadmin /usr/local/sbin/kamailio[19568]: DEBUG: core
[parser/msg_parser.c:513]: parse_headers: this is the first via

Nov 28 12:24:24

Re: [SR-Users] siptrace vs. sipcapture

2012-10-29 Thread Alexandr Dubovikov

Hello Mino,

if you would like to have advanced search possibility, long time archiving,
pcap export, X-Rtp stats etc, you can use sipcapture module and Homer UI,
but if you just have a couple of SIP messages, siptrace will be absolute
enough :-) 

Wbr,
Alexandr


-Original Message-
From: sr-users-boun...@lists.sip-router.org
[mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Mino Haluz
Sent: Monday, October 29, 2012 2:48 PM
To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users
Mailing List
Subject: [SR-Users] siptrace vs. sipcapture

Hi,

we are thinking about switching from siptrace to sipcapture + HEP
encapsulation. Do you know some reasons why we should switch to sipcapture
or why we should not ? ;) We have multiple SIP proxies and Cisco gateways.
In earlier versions of kamailio was siptrace blocking, that's why we started
to looking for some other capturing mechanism. I think now siptrace is
buffered, so we are hesitating ..

Mino

___
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

Re: [SR-Users] web homer not displaying data

2012-10-26 Thread Alexandr Dubovikov


Hi Christopher,

at first please check your apache errors.log. Seems you have problem 
with PDO driver. If you want get support for Webhomer, please contact us 
by email: supp...@sipcapture.org


Wbr,
Alexandr


10/26/2012 7:17 PM, Christopher Holland wrote:
I have  sipcapture and siptrace setup on the same server using 
kamailio 3.4.0-dev4 and webhomer 3.3.0 setup to capture sip traffic 
from a mirriored port on the LAN. Interface ETH1 is to capture and 
ETH0 is for managment.


The sipcapture database is getting data put into it. I can log into 
webhomer, but see no data in the graphes nor can I search. I have 
double checked my database permissions and they seem to be set up 
correctly.


webserver is set up with:

Apache/2.2.16 (Debian)
PHP5
MYSQL
Json
phpmyadmin

Here is a copy of my kamailio.cfg and configuration.php

rev_dns=no
auto_aliases=no

debug=1
log_stderror=no

memdbg=5
memlog=5

log_facility=LOG_LOCAL0

fork=yes
children=5

/* uncomment the next line to disable TCP (default on) */
disable_tcp=yes

/* IP and port for HEP capturing) */
listen=udp:127.0.0.1:9060

mpath=/usr/local/lib/kamailio/modules_k/:/usr/local/lib/kamailio/modules/ 



loadmodule pv.so
loadmodule db_mysql.so
loadmodule sipcapture.so
loadmodule textops.so
loadmodule siptrace.so

# - mi_fifo params -

### Routing Logic 
modparam(sipcapture, db_url, 
mysql://openser:**@localhost/homerdb)

modparam(sipcapture, capture_on, 1)
/* activate HEP capturing */
modparam(sipcapture, hep_capture_on, 1)
/* IP to listen. Port/Portrange apply only on mirroring port capturing */
modparam(sipcapture, raw_socket_listen, 10.0.0.0:5060-5080)
/* Name of interface to bind on raw socket */
modparam(sipcapture, raw_interface, eth1)
/* activate IPIP capturing */
#modparam(sipcapture, raw_ipip_capture_on, 1)
/* My table name*/
modparam(sipcapture, table_name, sip_capture)
/* children for raw socket */
modparam(sipcapture, raw_sock_children, 4)
/* insert delayed */
#modparam(sipcapture, db_insert_mode, 1)
/* activate monitoring/mirroring port capturing. Linux only */
modparam(sipcapture, raw_moni_capture_on, 1)
/* Promiscious mode RAW socket. Mirroring port. Linux only */
modparam(sipcapture, promiscious_on, 1)
/* activate Linux Socket Filter (LSF/BPF) on mirroring interface. 
Linux only */

#modparam(sipcapture, raw_moni_bpf_on, 1)
/* sipcapture node */
modparam(sipcapture, capture_node, homer01)

# check IP and port of your capture node
modparam(siptrace, duplicate_uri,sip:127.0.0.1:9060)
modparam(siptrace, hep_mode_on, 1)
modparam(siptrace, trace_to_database, 0)
modparam(siptrace, trace_flag,22)
modparam(siptrace, trace_on, 1)

# Main SIP request routing logic
# - processing of any incoming SIP request starts with this route
route {
   sip_capture();
   drop;
}
onreply_route {
   sip_capture();
   drop;
}

##

configuration.php

?php

/*/ 


/* Access db of homer */
define('HOST', localhost);
define('PORT', 3306);
define('USER', webhomer);
define('PW', **);
define('DB', web_homer);

/* Homer connection
*  this user must have the same password for all Homer nodes
*  please define all your nodes in homer_nodes table
*/
define('HOMER_HOST', localhost); /* DEFAULT. Don't forget insert 
this host to your DB nodes table */

define('HOMER_PORT', 3306);
define('HOMER_USER', openser);
define('HOMER_PW', **);
define('HOMER_DB', homerdb);
define('HOMER_TABLE', sip_capture);

/*/ 



/* webHomer Settings
*  Adjust to reflect your system preferences
*/

define('PCAPDIR',/var/www/webhomer/tmp/);
define('WEBPCAPLOC',/webhomer/tmp/);
define('APIURL',http://localhost;);
define('APILOC',/webhomer/api/);

/* INCLUDE preferences */

include(preferences.php);

?



___
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

Re: [SR-Users] kamailio 3.3 sipcapture and Homer Capture Agent 4

2012-10-05 Thread Alexandr Dubovikov

Hello Juha,

yes, it's compatible with version 1 or 2. Your captagent config must looks
like this:

configuration name=core_hep.conf description=HEP Socket

  settings
param name=version value=2/
param name=capture-host value=10.0.0.1/
param name=capture-port value=9060/
param name=capture-proto value=udp/
param name=capture-id value=2001/
param name=capture-password value=myHep/
  /settings
/configuration

can you show your kamailio config ? I think there are some issues...

Wbr,

Alexandr


2012/10/5 Juha Heinanen j...@tutpro.com

 is Homer Capture Agent 4 hep protocol incompatible with Kamalio 3.3
 sipcapture module?  in captagent.xml i set core_hep.conf version to 2,
 but looks like kamailio is not able to parse the messages:

 Oct  5 12:40:18 siika sip-proxy[6779]: INFO: core
 [parser/parse_fline.c:145]: ERROR:parse_first_line: method not followed by
 SP
 Oct  5 12:40:18 siika sip-proxy[6779]: INFO: core
 [parser/parse_fline.c:242]: ERROR:parse_first_line: bad message
 Oct  5 12:40:18 siika sip-proxy[6779]: ERROR: core
 [parser/msg_parser.c:705]: ERROR: parse_msg:
 message=#002#020#002#006#023ĳ��bg#012�bg#012#002�nP#037#035#010
 Oct  5 12:40:18 siika sip-proxy[6779]: ERROR: core [receive.c:146]:
 ERROR: receive_msg: parse_msg failed

 in kamailio config i have

 modparam(sipcapture, capture_on, 1)
 modparam(sipcapture, hep_capture_on, 1)

 -- 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

___
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_capture schema?

2012-10-04 Thread Alexandr Dubovikov


10/4/2012 8:49 AM, Juha Heinanen wrote:

Juha Heinanen writes:


also, looks like sipcapture module README is missing many of module's
params.  is this module still supported or has it become obsolete?

perhaps obsolete, because my sip proxy crashed at start when in added
loading of sipcapture module.


no, it's not obsolete. I will add HEPv3 support soon and update the 
README file too.


please show your kamailio.conf

Wbr,
Alexandr


-- juha

Program terminated with signal 11, Segmentation fault.
#0  0x7fbec39ebcb9 in strtok () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) where
#0  0x7fbec39ebcb9 in strtok () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7fbebebca46e in mt_init () at sipcapture.c:343
#2  0x7fbebebcb389 in mod_init () at sipcapture.c:470
#3  0x004f2339 in init_mod (m=0x7fbec2b9d4a0) at sr_module.c:936
#4  0x004f220d in init_mod (m=0x7fbec2b9d7c8) at sr_module.c:933
#5  0x004f220d in init_mod (m=0x7fbec2b9dcb8) at sr_module.c:933
#6  0x004f220d in init_mod (m=0x7fbec2b9e130) at sr_module.c:933
#7  0x004f220d in init_mod (m=0x7fbec2ba0900) at sr_module.c:933
#8  0x004f220d in init_mod (m=0x7fbec2ba0c60) at sr_module.c:933
#9  0x004f220d in init_mod (m=0x7fbec2ba0fc0) at sr_module.c:933
#10 0x004f220d in init_mod (m=0x7fbec2ba13d8) at sr_module.c:933
#11 0x004f220d in init_mod (m=0x7fbec2ba17e8) at sr_module.c:933
#12 0x004f220d in init_mod (m=0x7fbec2ba1b10) at sr_module.c:933
#13 0x004f220d in init_mod (m=0x7fbec2ba2450) at sr_module.c:933
#14 0x004f220d in init_mod (m=0x7fbec2ba2c70) at sr_module.c:933
#15 0x004f220d in init_mod (m=0x7fbec2ba3550) at sr_module.c:933
#16 0x004f220d in init_mod (m=0x7fbec2ba8ea8) at sr_module.c:933
#17 0x004f220d in init_mod (m=0x7fbec2ba9480) at sr_module.c:933
#18 0x004f220d in init_mod (m=0x7fbec2ba98c0) at sr_module.c:933
#19 0x004f220d in init_mod (m=0x7fbec2ba9c58) at sr_module.c:933
#20 0x004f220d in init_mod (m=0x7fbec2ba9f88) at sr_module.c:933
#21 0x004f220d in init_mod (m=0x7fbec2baa608) at sr_module.c:933
#22 0x004f220d in init_mod (m=0x7fbec2baa9a0) at sr_module.c:933
#23 0x004f220d in init_mod (m=0x7fbec2baade8) at sr_module.c:933
#24 0x004f220d in init_mod (m=0x7fbec2bab658) at sr_module.c:933
#25 0x004f220d in init_mod (m=0x7fbec2babc28) at sr_module.c:933
#26 0x004f220d in init_mod (m=0x7fbec2bac000) at sr_module.c:933
#27 0x004f220d in init_mod (m=0x7fbec2bac6c8) at sr_module.c:933
#28 0x004f220d in init_mod (m=0x7fbec2bacc30) at sr_module.c:933
#29 0x004f220d in init_mod (m=0x7fbec2bacf58) at sr_module.c:933
#30 0x004f220d in init_mod (m=0x7fbec2bad360) at sr_module.c:933
#31 0x004f220d in init_mod (m=0x7fbec2badb80) at sr_module.c:933
#32 0x004f220d in init_mod (m=0x7fbec2bae2e0) at sr_module.c:933
#33 0x004f220d in init_mod (m=0x7fbec2bae738) at sr_module.c:933
#34 0x004f220d in init_mod (m=0x7fbec2baf2e8) at sr_module.c:933
#35 0x004f220d in init_mod (m=0x7fbec2baf540) at sr_module.c:933
#36 0x004f249b in init_modules () at sr_module.c:963
#37 0x00468e6b in main (argc=17, argv=0x7fffceacf4c8) at main.c:2504


___
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

Re: [SR-Users] sip_capture schema?

2012-10-04 Thread Alexandr Dubovikov


10/4/2012 4:05 PM, Juha Heinanen wrote:

Alexandr Dubovikov writes:


no, it's not obsolete. I will add HEPv3 support soon and update the
README file too.

that is very good.  please also include db schema in lib/srdb1/schema.


please show your kamailio.conf

i don't yet have any sipcapture params set in the config.  i just added
line

loadmodule sipcapture

and restarted my proxy, which resulted in the crash.



without any additional modules ? anyway I will check it too.

Wbr,
Alexandr


-- 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



___
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_capture schema?

2012-10-04 Thread Alexandr Dubovikov


10/4/2012 4:31 PM, Juha Heinanen wrote:

Alexandr Dubovikov writes:


without any additional modules ? anyway I will check it too.

no, with lots of other modules.  below is list up to sipcapture, but i
don't think it matters.

-- juha


ok. i will check.

Wbr,
Alexandr


loadpath /usr/lib/sip-proxy/modules
loadmodule app_lua
loadmodule auth
loadmodule avpops
loadmodule db_mysql
loadmodule tm
loadmodule lcr
loadmodule cfg_rpc
loadmodule ctl
loadmodule dialplan
loadmodule enum
loadmodule geoip
loadmodule ipops
loadmodule mediaproxy
loadmodule mi_rpc
loadmodule mtree
loadmodule sanity
loadmodule sdpops
loadmodule sipcapture

___
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

Re: [SR-Users] sipcapture unsupported family

2012-10-04 Thread Alexandr Dubovikov


10/4/2012 5:11 PM, Juha Heinanen wrote:

after adding a few module params

modparam(sipcapture, db_url, MYSQL_SIP_PROXY_USAGE_URL)
modparam(sipcapture, table_name, sip_capture)
modparam(sipcapture, hep_capture_on, 1)
modparam(sipcapture, capture_node, EXTERNAL_HOSTNAME)

i restarted my sip proxy and started to get these kind of errors to
syslog:

Oct  4 18:09:02 siika /usr/sbin/sip-proxy[22914]: ERROR: sipcapture 
[sipcapture.c:733]: ERROR: sipcapture:hep_msg_received:  unsupported family [71]

why they appear and how to turn them off?


probably you are recieving normal SIP messages, not HEP.  Can you change 
capture port to 9060 and duplicate all SIP messages to this port.


or follow these instructions:

http://code.google.com/p/homer/wiki/Kamailio
http://code.google.com/p/homer/wiki/HOWTO

Wbr,
Alexandr



-- 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



___
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] sipcapture unsupported family

2012-10-04 Thread Alexandr Dubovikov


10/4/2012 5:23 PM, Juha Heinanen wrote:

Alexandr Dubovikov writes:


http://code.google.com/p/homer/wiki/Kamailio

kamailio example includes calls of sip_capture() function, which is not
documented in README.  based on README i got the impression that once i
give 'sip_capture on' mi command, all packets are captured
automatically.


ok, but the issue in your last mail has nothing to do how you are 
calling the sip_capture function: directly in kamailio config or through 
mi command.


just change the capture port to 9060 and send HEP traffic there.

Wbr,
Alexandr



-- 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



___
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] Sipcapture and Siptrace Compile Error

2012-06-18 Thread Alexandr Dubovikov


Hallo Akan,

oops, sorry :-(

please add  new typedef after u_int16_t;

#ifdef __OS_solaris
typedef uint8_t u_int8_t;
typedef uint16_t u_int16_t;
*typedef uint16_t u_int32_t;*
#define IPPROTO_IPIP IPPROTO_ENCAP /* Solaris IPIP protocol has name 
ENCAP */

#endif

Wbr,
Alexandr

6/15/2012 9:11 PM, Akan wrote:
I added the define and recompiled. still got the same error. Here is 
the change that I've made:


#define __OS_solaris 1   //* this is the line that i've added

#ifdef __OS_solaris
typedef uint8_t u_int8_t;
typedef uint16_t u_int16_t;
#define IPPROTO_IPIP IPPROTO_ENCAP /* Solaris IPIP protocol has name 
ENCAP */

#endif


Thanks

Nathaniel


On 6/15/2012 9:15 AM, Alexandr Dubovikov wrote:

Hi Akan,

looks like in your system has not defined __OS_solaris

open sipcapture.h and add this string on top:

#define __OS_solaris 1

and recompile modules again.

Wbr,
Alexandr

On 06/15/2012 06:53 AM, Akan wrote:
When compiling kamailio v3.3, I am getting this error from 
sipcapture and siptrace. I am compiling on solaris 10, 64bit  Sun 
server with gnu tools.


CC (gcc) [M sipcapture.so]  sipcapture.o
In file included from sipcapture.c:76:0:
sipcapture.h:48:4: error: unknown type name 'u_int32_t'
sipcapture.h:49:4: error: unknown type name 'u_int32_t'
gmake[1]: *** [sipcapture.o] Error 1

In file included from siptrace.c:54:0:
../../modules/sipcapture/sipcapture.h:48:4: error: unknown type name 
'u_int32_t'
../../modules/sipcapture/sipcapture.h:49:4: error: unknown type name 
'u_int32_t'

gmake[1]: *** [siptrace.o] Error 1


Thanks

Nathaniel

___
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





-
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2180 / Virus Database: 2433/5070 - Release Date: 
06/14/12







___
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

Re: [SR-Users] siptrace port number error

2012-05-07 Thread Alexandr Dubovikov


Hi Reda,

5/6/2012 4:56 PM, Reda Aouad wrote:

Hi Alex,

Thank you for the fix. Just upgraded to Kamailio 3.3 and now Kamailio 
starts without the previous error. Can this be backported to version 3.2?



It was not my fix :-)

 you can just use the sipcapture module from 3.3 together with 3.2, 
just recompile.


Bu the problem is still not solved. Although Kamailio starts, I get 
now a runtime error.
ERROR: sipcapture [sipcapture.c:675]: ERROR: 
sipcapture:hep_msg_received:  unsupported family [71]


unsupported family says: this packet is not HEP.



This is my config running NODE and AGENT on same server:


listen=udp:10.238.235.173:53 http://10.238.235.173:53
listen=udp:127.0.0.1:9060 http://127.0.0.1:9060

modparam(sipcapture, db_url, mysql://homer:homer@localhost/homer)
modparam(sipcapture, capture_on, 1)
modparam(sipcapture, capture_node, homer01)
modparam(sipcapture, hep_capture_on, 1)

modparam(siptrace, traced_user_avp, $avp(s:traced_user))
modparam(siptrace, trace_on, 1)
modparam(siptrace, trace_flag, FLD_TRACE)
modparam(siptrace, duplicate_uri, sip:127.0.0.1:9060 
http://127.0.0.1:9060)

modparam(siptrace, hep_mode_on, 1)
modparam(siptrace, trace_to_database, 0)

request_route {
...
setflag(FLD_TRACE);
sip_capture();
...
}


It seems sipcapture is listening on both eth0 and loopback interfaces, 
and when it detects packets not encapsulated using HEP on eth0 
(requests from SIP clients), it gives the error above.


kamailio is listening on the both interfaces, not sipcapture self.



Is there a way to tell sipcapture to bind only on one interface using 
HEP mode? It seems impossible for now to run NODE and AGENT on the 
same server using HEP mode...


you can make a trick, check in hep_msg_recieved() a destination port of 
the receive_info structure


something like this:

ri = (struct receive_info *)srevp[2];

if(ri-dst_port != 9060) return -1;


Thanks for helping.
Reda



Wbr,
Alexandr
___
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] siptrace port number error

2012-04-15 Thread Alexandr Dubovikov


Hi Reda,

please take the last git and check it again.

Wbr,
Alexandr

4/15/2012 8:53 PM, Reda Aouad wrote:

Hi,

I'm trying to setup Kamailio as a Homer capture server itself.
Kamailio listens on 2 ports : 53 for SIP users, and 9060 for homer SIP 
capture.

siptrace module duplicates packets to sipcapture module on port 9060.

I'm getting the following error :
ERROR: siptrace [siptrace.c:1669]: invalid port number; must be in 
[1024,65536]


This is my conf
---

listen=udp:10.238.235.173:53 http://10.238.235.173:53
listen=udp:127.0.0.1:9060 http://127.0.0.1:9060

#!ifdef WITH_SIPTRACE
modparam(siptrace, traced_user_avp, $avp(s:traced_user))
modparam(siptrace, trace_on, 1)
modparam(siptrace, trace_flag, FLD_TRACE)
modparam(siptrace, duplicate_uri,sip:127.0.0.1:9060 
http://127.0.0.1:9060)

modparam(siptrace, hep_mode_on,1);
modparam(siptrace, trace_to_database, 0);
#!endif


Any help?

Thanks
Reda



___
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

Re: [SR-Users] siptrace error...

2012-03-30 Thread Alexandr Dubovikov


Krishna,

take the last siptrace.c from ser's git and add after line 1703 this code:

if(len  0) tmp_piport[len - 1] = '\0';


so, code must looks so:

/* our tmp string */
1703 
http://git.sip-router.org/cgi-bin/gitweb.cgi?p=sip-router;a=blob;f=modules_k/siptrace/siptrace.c;h=b54d893dcda013006ee8069c6e3f313c427fa76e;hb=HEAD#l1703 
strncpy(tmp_piport, pipport, len);
1704 
http://git.sip-router.org/cgi-bin/gitweb.cgi?p=sip-router;a=blob;f=modules_k/siptrace/siptrace.c;h=b54d893dcda013006ee8069c6e3f313c427fa76e;hb=HEAD#l1704 
if(len  0) tmp_piport[len-1] = '\0';
1705 
http://git.sip-router.org/cgi-bin/gitweb.cgi?p=sip-router;a=blob;f=modules_k/siptrace/siptrace.c;h=b54d893dcda013006ee8069c6e3f313c427fa76e;hb=HEAD#l1705 
len = 0;



and let me know if it works for you.

Wbr,
Alexandr



3/29/2012 10:35 PM, Krishna Kurapati wrote:

Daniel,

I finally had some time to put a log after it failed to convert from 
to socket.


ERROR: siptrace [siptrace.c:1704]: there is not a valid number port 
5060??k5
Mar 29 13:30:32 siptest /usr/sbin/kamailio[19848]: ERROR: siptrace 
[siptrace.c:1514]: ERROR: bad FROM tcp:10.1.0.6:5060 
http://10.1.0.6:5060 or TO tcp:75.62.17.45:63343 
http://75.62.17.45:63343


The passing parameter to the function look fine. Well formed and null 
terminated. Inside it is failing.

Any ideas

Attaching the code segments around the lines


Code around line 1514:

   /* Convert proto:ip:port to sockaddress union SRC IP */
if (pipport2su(from-s, from_su, proto)==-1 || 
(pipport2su(to-s, to_su, proto)==-1))

{
LOG(L_ERR, ERROR: bad FROM %s or TO %s\n, from-s, 
to-s);

goto error;
}


Code around line 1704:

   else {
/*the address contains a port number*/
*p = '\0';
p++;
port_str.s = p;
port_str.len = strlen(p);
LM_DBG(the port string is %s\n, p);
if(str2int(port_str, port_no) != 0 ) {
LM_ERR(there is not a valid number port 
%s\n, p);

goto error;
}
*p = '\0';
}






On Wed, Mar 28, 2012 at 2:16 PM, Daniel-Constantin Mierla 
mico...@gmail.com mailto:mico...@gmail.com wrote:


have you changed the log line to print the port? can you print the
entire string, with proto and ip to see if there are
spaces/invalid characters (print it between special chars, like [])?

The line is inside the mirroring traffic via hep protocol, is what
you want to get, right?

Cheers,
Daniel


On 3/28/12 12:53 PM, Krishna Kurapati wrote:

I tried to pull null terminator to see if that fixes the issue.
That is why there is shift in the lines. It is same as line 1701.

Krish Kura

On Wed, Mar 28, 2012 at 3:57 AM, Daniel-Constantin Mierla
mico...@gmail.com mailto:mico...@gmail.com wrote:

Hello,

are you working with a custom siptrace module? the line in
siptrace.c does not match. If you changed the sources, paste
here the lines in siptrace.c around 1705, 10 before and 10 after.

Cheers,
Daniel


On 3/26/12 3:23 PM, Krishna Kurapati wrote:

Hi,

I keep getting this error in the sip_trace module:

Mar 26 06:19:26 siptest /usr/sbin/kamailio[4279]: ERROR:
siptrace [siptrace.c:1705]: there is not a valid number port
5060?/??

Krish Kura


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org  mailto:sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


-- 
Daniel-Constantin Mierla

Kamailio Advanced Training, April 23-26, 2012, Berlin, Germany
http://www.asipto.com/index.php/kamailio-advanced-training/




-- 
Daniel-Constantin Mierla

Kamailio Advanced Training, April 23-26, 2012, Berlin, Germany
http://www.asipto.com/index.php/kamailio-advanced-training/




___
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

Re: [SR-Users] siptrace error...

2012-03-28 Thread Alexandr Dubovikov


Hello Krishna,

do you use git version or release 3.2 ?

I don't really understand what's a problem do you have ?

Wbr,
Alexandr


3/28/2012 12:53 PM, Krishna Kurapati wrote:
I tried to pull null terminator to see if that fixes the issue. That 
is why there is shift in the lines. It is same as line 1701.


Krish Kura

On Wed, Mar 28, 2012 at 3:57 AM, Daniel-Constantin Mierla 
mico...@gmail.com mailto:mico...@gmail.com wrote:


Hello,

are you working with a custom siptrace module? the line in
siptrace.c does not match. If you changed the sources, paste here
the lines in siptrace.c around 1705, 10 before and 10 after.

Cheers,
Daniel


On 3/26/12 3:23 PM, Krishna Kurapati wrote:

Hi,

I keep getting this error in the sip_trace module:

Mar 26 06:19:26 siptest /usr/sbin/kamailio[4279]: ERROR: siptrace
[siptrace.c:1705]: there is not a valid number port 5060?/??

Krish Kura


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org  mailto:sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


-- 
Daniel-Constantin Mierla

Kamailio Advanced Training, April 23-26, 2012, Berlin, Germany
http://www.asipto.com/index.php/kamailio-advanced-training/




___
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

Re: [SR-Users] Question on (sipcapture, raw_interface, )

2012-02-17 Thread Alexandr Dubovikov



I have anwered you already: use two instance of captagent or two 
instance of kamailio. (each for one interface)


Wbr,
Alexandr

16.02.2012 15:05, Nelson Pereira wrote:
but im not talking about sniff, but the SIPCAPTURE  raw_interface 
function...



On Thu, Feb 16, 2012 at 8:57 AM, Klaus Darilion 
klaus.mailingli...@pernau.at mailto:klaus.mailingli...@pernau.at 
wrote:


Using tcpdump/ngrep it is not possible to sniff on 2 interfaces,
but it is possible to sniff an the any pseudo interface:

tcpdump -i any .
ngrep -d any .

There may be other sniffing tools which support to sniff on
multiple interfaces.

regards
Klaus


On 16.02.2012 14:09, Nelson Pereira wrote:

Is it possible to monitor 2 interfaces?
I have 2 Asterisk servers and they are on 2 different switches
so I need
to capture ETH0 and ETH3 which is where the mirror ports are
connected
to from each switch.

Thanks



___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
mailing list
sr-users@lists.sip-router.org
mailto: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


___
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] Need example of Kamailio.cfg for a port mirror setup

2012-02-17 Thread Alexandr Dubovikov



The link has been not changed, you know it already:

http://code.google.com/p/homer/wiki/HOWTO

Homer Capture Agent (for all other unsupported system)

if your SIP system (PBX, proxy) doesn't have a built-in capture agent 
with HEP or IPIP encapsulation support, you can use Homer Capture Agent 
(captagent). This is an external application (daemon) that collect SIP 
messages thru PCAPlib and send them to your capture server. The 
captagent support IPv4 and IPv6.


preventing your next question: the captagent your can find in the git.

http://code.google.com/p/homer/source/browse/


Wbr,
Alexandr


17.02.2012 13:15, Nelson Pereira wrote:

Can captagent be installed on a asterisk server? If so, is there a howto?

Sent from my iPhone4 on IOS4

On Feb 17, 2012, at 7:07 AM, Alexandr Dubovikov v...@start4.info 
mailto:v...@start4.info wrote:



Hi,

start two captagents instance, each on own interface and duplicate 
all traffic to your kamailio node. (HEP protocol)


Wbr,
Alexandr

16.02.2012 17:51, Nelson Pereira wrote:
I would like to know if someone can show me an example of there 
setup configuration in kamailio.cfg for capturing packets comming in 
from a mirror port.
The reason I ask is that if I do a TCPDUMP on the server, I see all 
traffic to and from different sources on my Voice network.


But when I use Homer SIPCAPTURE which uses Kamailio in the 
background, I only see traffic sent FROM my PBX but not seing the 
traffic comming back to it.


I mean I only see one side of the call, yet TCPDUMP confirmed I see 
everything


What am I missing ?

Thanks

NP


___
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 mailto: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


___
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] creating DB in MySQL for Homer Capture server gives errors

2012-02-14 Thread Alexandr Dubovikov


  
  
Hi Nelson,

your mysql server is old. The best way upgrade your mysql server
minimum up to 5.1.43, if not, don't use UNIX_TIMESTAMP partitioning
for this mysql.

Wbr,
Alexandr

14.02.2012 15:25, Nelson Pereira wrote:

  
  
  
  
  
Hi all,

Trying to create the Homer SIP capture
  (Kamailio) DB and getting an error:

Error
SQL query: 
CREATE TABLE `sip_capture` (
`id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `date`
timestamp NOT NULL DEFAULT '-00-00 00:00:00', `micro_ts`
bigint(18) NOT NULL DEFAULT '0', `method` varchar(50) NOT
NULL DEFAULT '', `reply_reason` varchar(100) NOT NULL,
`ruri` varchar(200) NOT NULL DEFAULT '', `ruri_user`
varchar(100) NOT NULL DEFAULT '', `from_user` varchar(100)
NOT NULL DEFAULT '', `from_tag` varchar(64) NOT NULL DEFAULT
'', `to_user` varchar(100) NOT NULL DEFAULT '', `to_tag`
varchar(64) NOT NULL, `pid_user` varchar(100) NOT NULL
DEFAULT '', `contact_user` varchar(120) NOT NULL,
`auth_user` varchar(120) NOT NULL, `callid` varchar(100) NOT
NULL DEFAULT '', `callid_aleg` varchar(100) NOT NULL DEFAULT
'', `via_1` varchar(256) NOT NULL, `via_1_branch`
varchar(80) NOT NULL, `cseq` varchar(25) NOT NULL,
`diversion` varchar(256) NOT NULL, `reason` varchar(200) NOT
NULL, `content_type` varchar(256) NOT NULL, `authorization`
varchar(256) N[...] 
MySQL said: 
#1064
- You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the right
syntax to use near 'PARTITION BY RANGE (
UNIX_TIMESTAMP(`date`) ) (
PARTITION pmax VALUES LESS THAN ' at line 50


System
Information:
 Apache/2.2.10 (Linux/SUSE)
 MySQL client version:
5.0.67
 PHP extension: mysqli

Server is SLES 11 SP1
  
  
  
  
  ___
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

Re: [SR-Users] Homer SIP Capture Setup Question

2012-01-24 Thread Alexandr Dubovikov


Hi,

Sorry, it was my mistake in the sample.

in the FAQ we have fixed this issue :-)
http://code.google.com/p/homer/wiki/FAQ

*Q: I use HEP and see kamailio replying with 100 Trying, 200 OK. Why is 
that?*


A: The messages have been replied to by onreply_route; To disable 
replies, adjust your kamailio.cfg as follows:


onreply_route{
 sip_capture();
 drop;
}


Wbr,
Alexandr

1/17/2012 2:37 PM, JR Richardson wrote:

On 01/16/2012 09:11 PM, JR Richardson wrote:


So my question; what is the difference between a drop; and exit;
within the on_reply route

Remember that an onreply_route is a callback that allows you to
intercept a reply, but the reply is forwarded by default afterward (if
using stateful forwarding).  This is different from a request route,
where it's up to you to marshal everything, and to explicitly forward
the message.

Thus, exiting an onreply_route has null effect.  It doesn't do
anything to stop the reply from being forwarded, because forwarding is
the behaviour--the onreply_route is just a hook.  In contrast, 'drop'
explicitly drops the message and prevents further forwarding of the
reply from taking place.

This is different than in a request route, where exiting precludes any
forwarding action, because forwarding action must be taken explicitly
-- e.g. t_relay().

--
Alex Balashov - Principal

Aaaah, concise explanation, once again, thanks for turning on the light bulb
Alex.

JR


___
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

Re: [SR-Users] kamailio sip-capture error on compile

2011-10-05 Thread Alexandr Dubovikov

Hi Jeff,

As I know the problem has been resolved. Is it ?

Wbr,
Alexandr


03.10.2011, в 23:06, Jeff Anderson wrote:

 I have been following this document 
 (http://code.google.com/p/homer/wiki/HOWTO) to build the homer server. I 
 receive the warning message on step 8. I don't specifically know if 
 sip-capture is or is not working. I know that my sip traffic is making it to 
 the server but it is not getting imported into the db. I figured i would try 
 and correct this warning message hoping that it would be the fix for my data 
 not getting inserted into the db. Building this homer server is my first 
 introduction to kamailio. I thought maybe someone on this list may have seen 
 this error before. I am not sure where to go next in troubleshooting the 
 problem.
 
 Thanks,
 
 Jeff Anderson
 
 On Mon, Oct 3, 2011 at 2:34 PM, Andrew Pogrebennyk apogreben...@sipwise.com 
 wrote:
 Jeff,
 
 On 10/03/2011 08:45 PM, Jeff Anderson wrote:
  I am trying to get kamailio sip-capture up and running for use with homer. I
  can get the service to start but i receive the following error.
 
  [root@homer kamailio]# /usr/local/sbin/kamailio -c
  loading modules under
  /usr/local/lib/kamailio/modules_k/:/usr/local/lib/kamailio/modules/
   0(10208) WARNING: core [socket_info.c:912]: WARNING: fix_hostname: could
  not rev. resolve 10.40.0.22
  [...]
  Does anyone have any ideas on how to resolve this error?
 
 This message is from kamailio core, not sip-capture. I don't see
 anything abnormal in the log. Could you please share what are you doing
 and what makes you think sip-capture doesn't work?
 
 Regards,
 Andrew
 
 
 ___
 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

___
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] [sr-dev] releasing v3.2.0

2011-09-28 Thread Alexandr Dubovikov

Hello Daniel,

I had one issue in the sipcapture (mirroring mode), but the problem was
found and I'll commit the patches today/tommorow.

Wbr,
Alexandr

2011/9/28 Daniel-Constantin Mierla mico...@gmail.com

 Hello,

 it is time to set the time to release v3.2.0. From my point of view,
 testing went very well, considering also that core and main modules were not
 touched much during this devel cycle, the most of the efforts were on new
 modules and application service components such as presence server, Lua ...

 A convenient date for me will be Tuesday, October 18, 2011, allowing to
 work a bit on packaging and docs. If there are other preferences, jump in
 this discussion.

 Cheers,
 Daniel

 --
 Daniel-Constantin Mierla -- http://www.asipto.com
 Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kat
 http://linkedin.com/in/miconda -- http://twitter.com/miconda


 __**_
 sr-dev mailing list
 sr-...@lists.sip-router.org
 http://lists.sip-router.org/**cgi-bin/mailman/listinfo/sr-**devhttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev

___
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] [sr-dev] New developer: Alexandr Dubovikov

2011-08-19 Thread Alexandr Dubovikov


On 19.08.2011 10:44, Olle E. Johansson wrote:

19 aug 2011 kl. 10:23 skrev Daniel-Constantin Mierla:


Hello,

a new person has now developer access to GIT repository - Alexandr Dubovikov, 
contributor in the past with patches, is going to work now on extensions 
related to Homer project - turning the SIP server in a SIP capturing server. 
His developer id is adubovikov.

You can read more about Homer project at:
  * http://code.google.com/p/homer/
  * http://www.kamailio.org/events/2011-Cluecon/AD-Homerv2.pdf

Welcome Alexandr!


Thank you!


/O
___
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

Wbr,
Alexandr

___
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] Homer Project

2011-08-04 Thread Alexandr Dubovikov

Hello sr-users,

I would like to present a new project called Homer.

What is Homer ?

Homer is a capture solution for SIP logging.

How does it work?

Homer has 4 components:
1. Capture Agent
2. Capture Node
4. Capture DB
3. Web GUI.

The capture agent takes your local SIP traffic and sends it to the defined
capture node in HEP protocol.
If you are user of FreeSWITCH or Kamailio, use build-in capture agent. In
other case, you can use an external generic daemon, but only for SIP/UDP.
The capture node is based on kamailio, can receive SIP traffic encapsulated
in IP proto 4 (IPIP) or in HEP procotol and store it into MySQL DB.
To gain access to the capture DB, download a simple webinterface (PHP
based). After it you are able to do search, generate PCAP file,
callflow, look at the details of SIP messages etc.

Homer works in our company and easy collect ~5 M packets per hour.

The patches for kamailio and some other information can be found here:
http://homer.googlecode.com

Beta testers are welcome :-) I'll help everybody to setup/configure Homer
:-)

With best regards,
Alexandr
___
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] [sr-dev] FOSDEM 2017

Re: [SR-Users] Fosdem 2015

Re: [SR-Users] Fosdem 2015

Re: [SR-Users] Fosdem 2015

[SR-Users] Fosdem 2015

Re: [SR-Users] Montoring/Reporting Solution - Commercial/Open Source

Re: [SR-Users] siptrace source ip causes martians

Re: [SR-Users] siptrace source ip causes martians

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

Re: [SR-Users] sip_capture columns

Re: [SR-Users] Homer / Kamailio / Freeswitch

Re: [SR-Users] siptrace/sipcapture and MSRP

Re: [SR-Users] Segmentation fault in sip-capture

Re: [SR-Users] Segmentation fault in sip-capture

Re: [SR-Users] Segmentation fault in sip-capture

Re: [SR-Users] siptrace vs. sipcapture

Re: [SR-Users] web homer not displaying data

Re: [SR-Users] kamailio 3.3 sipcapture and Homer Capture Agent 4

Re: [SR-Users] sip_capture schema?

Re: [SR-Users] sip_capture schema?

Re: [SR-Users] sip_capture schema?

Re: [SR-Users] sipcapture unsupported family

Re: [SR-Users] sipcapture unsupported family

Re: [SR-Users] Sipcapture and Siptrace Compile Error

Re: [SR-Users] siptrace port number error

Re: [SR-Users] siptrace port number error

Re: [SR-Users] siptrace error...

Re: [SR-Users] siptrace error...

Re: [SR-Users] Question on (sipcapture, raw_interface, )

Re: [SR-Users] Need example of Kamailio.cfg for a port mirror setup

Re: [SR-Users] creating DB in MySQL for Homer Capture server gives errors

Re: [SR-Users] Homer SIP Capture Setup Question

Re: [SR-Users] kamailio sip-capture error on compile

Re: [SR-Users] [sr-dev] releasing v3.2.0

Re: [SR-Users] [sr-dev] New developer: Alexandr Dubovikov

[SR-Users] Homer Project

36 matches

Site Navigation

Mail list logo

Footer information