date:20170317

Re: [SR-Users] cisco spa502g issues

2017-03-17 Thread ben



Hi Daniel,


I shall have a look at that when Im back in the office on monday :)


Cheers,


Ben.


On 17/03/17 18:04, Daniel-Constantin Mierla wrote:

Hello,

maybe the new phones do STUN and or the ALG breaks somehow the
signaling. You should send the ngrep output taken on sip server for such
a call in order to be able to analyze what can happen:

ngrep -d any -qt -W byline port 5060

Cheers,
Daniel


On 17/03/2017 06:32, b...@wtf.com.au wrote:

Hi guys,

we have a bunch of SIP phones behind a fire wall, with our kamalio
server out on the internet. Most of them are the older SPA92x series,
but we have some new SPA502g's.

We have no problems calling between 92x and 502's. How ever the 502's
calling each other do not get voice path.

I have noticed that the phones REGISTER differently:

  AOR:: 5546@
  Contact:: sip:5546@:1032 Q=
  Expires:: 180
  Callid:: 4754c4f9-c67e1018@10.0.41.29
  Cseq:: 43112
  User-agent:: Cisco/SPA502G-7.6.2a
  State:: CS_DIRTY
  Flags:: 0
  Cflag:: 0
  Socket:: udp::5060
  Methods:: 6815


  AOR:: 5...@sip.skunkworks.net.au
  Contact:: sip:5590@10.0.41.14:5060 Q=
  Expires:: 1154
  Callid:: 24435738-224b06db@10.0.41.14
  Cseq:: 8012
  User-agent:: Linksys/SPA921-5.1.8
  Received:: sip::1026
  State:: CS_SYNC
  Flags:: 0
  Cflag:: 64
  Socket:: udp::5060
  Methods:: 4767

The older 921 has its private IP in the contact, where as the newer
502 has the external IP of our office in the contact.

Our file wall is a Watchguard T-10 (latest updates etc) with the
SIP-ALG running.

Any thoughts on where to start looking ?

Cheers,

Ben.

___
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] Generate extra cdr per dialog

2017-03-17 Thread Diego Nadares

Hi Guys,

I'm using acc module for accounting with the following conf:


modparam("acc", "cdr_enable", 1)
modparam("acc", "cdr_expired_dlg_enable", 1)
modparam("acc", "cdr_start_on_confirmed", 1)
modparam("acc", "cdr_facility", "LOG_LOCAL1")
modparam("acc", "cdr_end_id", "end_time_dt")
modparam("acc", "cdr_extra",
"sip_code=$rs;sip_reason=$rr;"
"hangup_src=$dlg_var(hangup_disposition);"

"prefix=$dlg_var(prefix);gos=$dlg_var(gos);endpoint_type=$dlg_var(endpoint_type);"
"ip_a=$dlg_var(ip_a);ip_b=$dlg_var(ip_b);"


It works fine. At the end of the call the cdr is generated ok.

BUT In MANAGE_FAILURE,  If the first call failed and if there are more
dests, we are generating a new call in the same dialog (Some of the dialog
vars like ip_a, ip_b can change for the new dest )

I would like to generate both cdrs, the one that failed and the new one
(with some dlg vars with new data).

if(rtjson_next_route() && t_check_status("503")) {
$avp(current_route) = $avp(current_route)+1;
t_on_branch("MANAGE_BRANCH");
t_on_failure("MANAGE_FAILURE");
route(RELAY);
exit;
}


Right now just the last call cdr is saved.

I all ready made this work with db_acc (transaction oriented) but I think
in my case it will be more reliable with cdr (dialog oriented).

Thanks in advance!

Diego.
___
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] f_malloc WARNINGS in syslog

2017-03-17 Thread Diego Nadares

Thanks Daniel!

2017-03-17 4:22 GMT-03:00 Daniel-Constantin Mierla :

> Hello,
>
> set memdbg and memlog parameters to a higher value than debug parameter.
> The messages are useful only if you troubleshoot memory operations.
>
> Cheers,
> Daniel
>
> On 16/03/2017 21:16, Diego Nadares wrote:
>
> Hi Guys,
>
> I'm seeing a lot of warnings in my syslog. Is this normal? Or maybe I am
> doing something wrong in my cfg?
>
> 
> Mar 16 17:11:47 dwsipm03 ./kamailio[26226]: WARNING: 
> [mem/f_malloc.c:444]: fm_malloc(): fm_malloc(0x7f68e5199010, 8) called from
> nathelper: nathelper.c: nh_timer(2078)
> Mar 16 17:11:47 dwsipm03 ./kamailio[26226]: WARNING: 
> [mem/f_malloc.c:527]: fm_malloc(): fm_malloc(0x7f68e5199010, 8) returns
> address 0x7f68e52a2d50
> Mar 16 17:11:47 dwsipm03 ./kamailio[26226]: WARNING: 
> [mem/f_malloc.c:588]: fm_free(): fm_free(0x7f68e5199010, 0x7f68e52a2d50),
> called from nathelper: nathelper.c: nh_timer()
> Mar 16 17:11:47 dwsipm03 ./kamailio[26226]: WARNING: 
> [mem/f_malloc.c:607]: fm_free(): fm_free: freeing block alloc'ed from
> nathelper: nathelper.c: nh_timer(2078)
> .
> Mar 16 17:15:44 dwsipm03 ./kamailio[26210]: WARNING: 
> [mem/f_malloc.c:607]: fm_free(): fm_free: freeing block alloc'ed from core:
> xavp.c: xavp_new_value(94)
> Mar 16 17:15:44 dwsipm03 ./kamailio[26210]: WARNING: 
> [mem/f_malloc.c:588]: fm_free(): fm_free(0x7f68d9d51000, 0x7f68da069ca8),
> called from tm: h_table.c: free_cell_helper(246)
> Mar 16 17:15:44 dwsipm03 ./kamailio[26210]: WARNING: 
> [mem/f_malloc.c:607]: fm_free(): fm_free: freeing block alloc'ed from tm:
> h_table.c: build_cell(317)
> Mar 16 17:15:44 dwsipm03 ./kamailio[26210]: WARNING: 
> [mem/f_malloc.c:588]: fm_free(): fm_free(0x7f68d9d51000, 0x7f68da031f00),
> called from tm: h_table.c: free_cell_helper(150)
> 
>
>
> Thanks in advance.
>
> Diego
>
>
> ___
> 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 Mierlawww.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
>
>
> ___
> 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] ht_db_load_table(): key type must be string (type=6)

2017-03-17 Thread Ginhoux, Patrick

Hi,

Now the kamailio installation is completed, I try to start kamailio but got an 
error on a modparam line.

By looking at the kamailio.cfg (with debug mode) it looks like the instruction 
is not correct :

modparam("htable", "fetch_rows", 1000)

[root@vm-vse02-siprouter1 ~]# systemctl status kamailio.service -l
kamailio.service - SYSV: Kamailio is a fast, reliable and flexible SIP Server.
   Loaded: loaded (/etc/rc.d/init.d/kamailio)
   Active: failed (Result: exit-code) since Fri 2017-03-17 15:38:13 CET; 17s ago
  Process: 1526 ExecStart=/etc/rc.d/init.d/kamailio start (code=exited, 
status=1/FAILURE)

Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: INFO: pike 
[pike.c:99]: pike_init(): PIKE - initializing
Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: INFO: pike 
[ip_tree.c:81]: init_lock_set(): probing 256 set size
Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: INFO: cfgutils 
[cfgutils.c:767]: mod_init(): no hash_file given, disable hash functionality
Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: ERROR: htable 
[ht_db.c:276]: ht_db_load_table(): key type must be string (type=6)
Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: ERROR:  
[core/sr_module.c:968]: init_mod(): Error while initializing module htable 
(/usr/lib64/kamailio/modules/htable.so)
Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: INFO:  
[core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
Mar 17 15:38:13 vm-vse02-siprouter1 kamailio[1526]: Starting kamailio:
Mar 17 15:38:13 vm-vse02-siprouter1 systemd[1]: kamailio.service: control 
process exited, code=exited status=1
Mar 17 15:38:13 vm-vse02-siprouter1 systemd[1]: Failed to start SYSV: Kamailio 
is a fast, reliable and flexible SIP Server..
Mar 17 15:38:13 vm-vse02-siprouter1 systemd[1]: Unit kamailio.service entered 
failed state.
[root@vm-vse02-siprouter1 ~]#

modparam("htable", "fetch_rows", "1000")

[root@vm-vse02-siprouter1 ~]# systemctl status kamailio.service -l
kamailio.service - SYSV: Kamailio is a fast, reliable and flexible SIP Server.
   Loaded: loaded (/etc/rc.d/init.d/kamailio)
   Active: failed (Result: exit-code) since Fri 2017-03-17 15:26:21 CET; 3s ago
  Process: 1452 ExecStart=/etc/rc.d/init.d/kamailio start (code=exited, 
status=1/FAILURE)

Mar 17 15:26:20 vm-vse02-siprouter1 systemd[1]: Starting SYSV: Kamailio is a 
fast, reliable and flexible SIP Server
Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: Not starting : invalid 
configuration file!
Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: 0(1460) ERROR:  
[core/modparam.c:141]: set_mod_param_regex(): parameter  of type 
<1> not found in module 
Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: 0(1460) CRITICAL:  
[core/cfg.y:3404]: yyerror_at(): parse error in config file 
//etc/kamailio/kamailio.cfg, line 308, column 41: Can't set module parameter
Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: 0(1460) WARNING:  
[core/cfg.y:3378]: warn_at(): warning in config file 
//etc/kamailio/kamailio.cfg, line 971, column 6-13: constant value in if(...)
Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: ERROR: bad config file (1 
errors)
Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: 0(1460) INFO:  
[core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
Mar 17 15:26:21 vm-vse02-siprouter1 systemd[1]: kamailio.service: control 
process exited, code=exited status=1
Mar 17 15:26:21 vm-vse02-siprouter1 systemd[1]: Failed to start SYSV: Kamailio 
is a fast, reliable and flexible SIP Server..
Mar 17 15:26:21 vm-vse02-siprouter1 systemd[1]: Unit kamailio.service entered 
failed state.
[root@vm-vse02-siprouter1 ~]#

The documentation shows that fetch_rows is an integer :
 fetch_rows (integer)
How many rows to fetch at once from database.
Default value is 100.
Example 1.12. Set fetch_rows parameter
...
modparam("htable", "fetch_rows", 1000)

So how to explain the first error.

Have you any thoughts on this case ?

Cordialement
Patrick GINHOUX

___
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] Error on of type <2> not found in module and SCTP API Not initialized

2017-03-17 Thread Ginhoux, Patrick

Last update,

With the correct Perl package for Rhel 7, now my kamailio installation has 
complete with success.

And the module app_perl initialization error below goes away.

So that I can close this topic.

Cordialement
Patrick GINHOUX

De : Ginhoux, Patrick
Envoyé : vendredi 17 mars 2017 07:40
À : SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users 
Mailing List 
Objet : RE: [SR-Users] Error on  of type <2> not found 
in module  and SCTP API Not initialized

Thanks Federico for this answer,

I see that in my .cfg there was a double ‘h’ in the name, while now there is 
only one (I need probably new glasses ☺ ).

Now it is fixed but now I got an error with the PERL mdule I’m trying to get 
for Rhel 7:

Mar 16 13:46:38 vm-vse02-siprouter1 /usr/sbin/kamailio[6767]: INFO: app_perl 
[app_perl_mod.c:219]: parser_init(): setting lib path: 
'/usr/lib64/kamailio/modules/'
Mar 16 13:46:38 vm-vse02-siprouter1 /usr/sbin/kamailio[6767]: ERROR: app_perl 
[app_perl_mod.c:241]: parser_init(): failed to load perl file 
"/etc/kamailio/snmptrap.pl" with code 2.
Mar 16 13:46:38 vm-vse02-siprouter1 /usr/sbin/kamailio[6767]: ERROR:  
[core/sr_module.c:968]: init_mod(): Error while initializing module app_perl 
(/usr/lib64/kamailio/modules/app_perl.so)

I opened another topic related to the rpm package for PERL module that is not 
available for Rhel 7 (see thread “Search for kamailio PERL module for 5.0 
level”).

Because I’m a newbie in this domain, I don’t have the experience to build a rpm 
package. Then one of my colleague helps me to build it. But because of this 
error, there is maybe something missing in the PERL installation on my server.
I’m doing some research.

If you have some ideas…

Cordialement
Patrick GINHOUX

De : sr-users [mailto:sr-users-boun...@lists.sip-router.org] De la part de 
Federico Cabiddu
Envoyé : jeudi 16 mars 2017 13:41
À : SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users 
Mailing List 
>
Objet : Re: [SR-Users] Error on  of type <2> not found 
in module  and SCTP API Not initialized

Hi,
param name has changed some versions ago:
http://www.kamailio.org/docs/modules/devel/modules/dispatcher.html#dispatcher.p.ds_probing_threshold

Cheers,

Federico

On 16 Mar 2017 13:35, "Ginhoux, Patrick" 
> wrote:
Hi,

I’m migrating my kamailio.cfg from the 3.3.1 release to 5.0.0 and encounter the 
following errors :

Mar 16 12:56:45 vm-vse02-siprouter1 systemd[1]: Starting SYSV: Kamailio is a 
fast, reliable and flexible SIP Server
Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: Not starting : invalid 
configuration file!
Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: 0(6652) ERROR:  
[core/modparam.c:141]: set_mod_param_regex(): parameter  
of type <2> not found in module 
Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: 0(6652) CRITICAL:  
[core/cfg.y:3404]: yyerror_at(): parse error in config file 
//etc/kamailio/kamailio.cfg, line 295, column 49: Can't set module parameter
Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: 0(6652) WARNING:  
[core/cfg.y:3378]: warn_at(): warning in config file 
//etc/kamailio/kamailio.cfg, line 971, column 6-13: constant value in if(...)
Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: ERROR: bad config file (1 
errors)
Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: 0(6652) INFO:  
[core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
Mar 16 12:56:45 vm-vse02-siprouter1 systemd[1]: kamailio.service: control 
process exited, code=exited status=1
Mar 16 12:56:45 vm-vse02-siprouter1 systemd[1]: Failed to start SYSV: Kamailio 
is a fast, reliable and flexible SIP Server..
Mar 16 12:56:45 vm-vse02-siprouter1 systemd[1]: Unit kamailio.service entered 
failed state.

Below the extract of my kamailio.cfg file :

modparam("dispatcher", "list_file", DISPATCHER_FILE)
modparam("dispatcher", "ds_probing_mode", 1)
modparam("dispatcher", "ds_probing_threshhold",3)
modparam("dispatcher", "flags", 2)
modparam("dispatcher", "attrs_avp", "$avp(dsattrs)")
modparam("dispatcher", "dst_avp", "$avp(dsdst)")
modparam("dispatcher", "grp_avp", "$avp(dsgrp)")
modparam("dispatcher", "cnt_avp", "$avp(dscnt)")
modparam("dispatcher", "ds_hash_size", 8)
modparam("dispatcher", "ds_ping_interval", 10)
modparam("dispatcher", "force_dst", 1)

For the dispatcher error :
I don’t find any change (eg in the Changelog for 5.0.0.) regarding the 
dispatcher module.
So is it a bug in the dispatcher module or have I to change it to something 
else ?

For the SCTP API error :
I don’t know what to do here.

Thanks to people that can help me on these 2 errors

Cordialement
Patrick GINHOUX

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org

Re: [SR-Users] Configuration to fetch SIP response body.

2017-03-17 Thread Daniel-Constantin Mierla

Note there are two variables that you may have to check:

  $mb - full SIP message (request/response) - headers and body

https://www.kamailio.org/wiki/cookbooks/devel/pseudovariables#mb_-_sip_message_buffer

  $rb - only the body for sip request/response (no headers)

https://www.kamailio.org/wiki/cookbooks/devel/pseudovariables#rb_-_body_of_requestreply

Cheers,
Daniel

On 17/03/2017 06:51, vi...@advaitamtech.com wrote:
>
> Yes. It worked.
>
>  
>
> Thank you.
>
>  
>
> -Original Message-
> From: "Alex Balashov" 
> Sent: Thursday, 16 March, 2017 8:32pm
> To: "Kamailio (SER) - Users Mailing List" 
> Subject: Re: [SR-Users] Configuration to fetch SIP response body.
>
> Won't accessing $mb in an onreply_route work?
>
> On Thu, Mar 16, 2017 at 08:25:48PM +0530, vi...@advaitamtech.com wrote:
>
> >
> > Hi,
> >
> > Is there any configuration to fetch SIP response body received?.
> >
> > My requirement is to fetch the SIP response body and save it into
> database.
> >
> > Thanks,
> > Vivek
>
> > ___
> > 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
>
>
> -- 
> Alex Balashov | Principal | Evariste Systems LLC
>
> Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
> Web: http://www.evaristesys.com/, http://www.csrpswitch.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
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

___
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] Search for kamailio PERL module for 5.0 level

2017-03-17 Thread Ginhoux, Patrick

Hi,

Thanks for the link as now I can see all I need for kamailio 5.0.x .

I just get the rpms and complete with success the installation.

So I can continue my installation.

Great job and thanks again for the help.

Cordialement
Patrick GINHOUX

De : Daniel-Constantin Mierla [mailto:mico...@gmail.com]
Envoyé : vendredi 17 mars 2017 08:06
À : Ginhoux, Patrick ; Kamailio (SER) - Users 
Mailing List 
Objet : Re: [SR-Users] Search for kamailio PERL module for 5.0 level


Hello,

links for various distros were added at:

  * https://www.kamailio.org/wiki/packages/rpms#kamailio_50x

A short report back on mailing list saying if the packages work ok would be 
appreciated.

Cheers,
Daniel

On 16/03/2017 16:25, Ginhoux, Patrick wrote:
Hi,

I just need to get the rpm but I have difficulties to find the correct link. 
Can you help on this ?

Cordialement
Patrick GINHOUX

De : Daniel-Constantin Mierla [mailto:mico...@gmail.com]
Envoyé : jeudi 16 mars 2017 16:10
À : Ginhoux, Patrick 
; Kamailio 
(SER) - Users Mailing List 

Objet : Re: [SR-Users] Search for kamailio PERL module for 5.0 level


Hello,

I already triggered the rebuild of rpms, some of them being completed already:

  - https://build.opensuse.org/package/show/home:kamailio:v5.0.0-rpms/kamailio50
If you want to get access and play with the specs in order to tune the rpms, 
then make an account on that portal and let me know the user id -- I will be 
glad to allow others helping with the generations of rpms, because I don't 
really use rpm-based systems myself.

Cheers,
Daniel
On 16/03/2017 15:08, Ginhoux, Patrick wrote:
Hi Daniel,

Thanks for the help.

Can you tell me when I can expect to get the PERL module built for 5.0 ?

If it is something that you need to schedule (it is something I can 
understand), then I could use the kamailio 4.4 level instead of 5.0 .

Cordialement
Patrick GINHOUX

De : sr-users [mailto:sr-users-boun...@lists.sip-router.org] De la part de 
Daniel-Constantin Mierla
Envoyé : jeudi 16 mars 2017 13:13
À : Kamailio (SER) - Users Mailing List 

Objet : Re: [SR-Users] Search for kamailio PERL module for 5.0 level


Hello,

probably perl module failed to be build on this distros by the opensuse build 
service. I will try to re-enable building them on centos and redhat and see the 
results.

Cheers,
Daniel

On 14/03/2017 18:08, Ginhoux, Patrick wrote:
Hi,

I’m a beginner in the use of kamailio product, so I try below to explain my 
problem with my words:


1)  PERL module issue :


Some years ago a SIP Router proxy running RedHat 6.2 was developped using the 
kamailio version 3.3 and the following packages used  :

kamailio-3.3.2-1.1.1.x86_64.rpm
kamailio-snmpstats-3.3.2-1.1.1.x86_64.rpm
kamailio-mysql-3.3.2-1.1.1.x86_64.rpm
kamailio-perl-3.3.2-1.1.1.x86_64.rpm

We have the project to migrate this SIP Proxy to RedHat 7.1 and used the latest 
Kamailio v5.0.0 Release:

kamailio-5.0.0-24.1.x86_64.rpm
kamailio-mysql-5.0.0-24.1.x86_64.rpm
kamailio-snmpstats-5.0.0-24.1.x86_64.rpm

However I don’t find the kamalio-perl package for RedHat 7.1. I see that the 
perl module has been renamed to ‘app_perl’ but I don’t find it either for 
kamailio 5.0.0.


2)  Kamailio.cfg script



Our proxy used the kamailio.cfg from the sample  of the 3.3.3 release.



So can I reuse the same 3.3.3 kamailio.cfg file with the 5.0.0 release or 
should I migrate (rewrite it) from the 5.0.0 sample ?

So I’m looking for some help on these issues.

Is there people that had this case ?

Thanks in advance for any answer.

Cordialement
Patrick GINHOUX

PS : I just create my account today but don’t get the email to validate it.







___

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

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




--

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



--

Daniel-Constantin Mierla

www.twitter.com/miconda --

Re: [SR-Users] cisco spa502g issues

2017-03-17 Thread Daniel-Constantin Mierla

Hello,

maybe the new phones do STUN and or the ALG breaks somehow the
signaling. You should send the ngrep output taken on sip server for such
a call in order to be able to analyze what can happen:

ngrep -d any -qt -W byline port 5060

Cheers,
Daniel


On 17/03/2017 06:32, b...@wtf.com.au wrote:
> Hi guys,
>
> we have a bunch of SIP phones behind a fire wall, with our kamalio
> server out on the internet. Most of them are the older SPA92x series,
> but we have some new SPA502g's.
>
> We have no problems calling between 92x and 502's. How ever the 502's
> calling each other do not get voice path.
>
> I have noticed that the phones REGISTER differently:
>
>  AOR:: 5546@
>  Contact:: sip:5546@:1032 Q=
>  Expires:: 180
>  Callid:: 4754c4f9-c67e1018@10.0.41.29
>  Cseq:: 43112
>  User-agent:: Cisco/SPA502G-7.6.2a
>  State:: CS_DIRTY
>  Flags:: 0
>  Cflag:: 0
>  Socket:: udp::5060
>  Methods:: 6815
>
>
>  AOR:: 5...@sip.skunkworks.net.au
>  Contact:: sip:5590@10.0.41.14:5060 Q=
>  Expires:: 1154
>  Callid:: 24435738-224b06db@10.0.41.14
>  Cseq:: 8012
>  User-agent:: Linksys/SPA921-5.1.8
>  Received:: sip::1026
>  State:: CS_SYNC
>  Flags:: 0
>  Cflag:: 64
>  Socket:: udp::5060
>  Methods:: 4767
>
> The older 921 has its private IP in the contact, where as the newer
> 502 has the external IP of our office in the contact.
>
> Our file wall is a Watchguard T-10 (latest updates etc) with the
> SIP-ALG running.
>
> Any thoughts on where to start looking ?
>
> Cheers,
>
> Ben.
>
> ___
> 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
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


___
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] f_malloc WARNINGS in syslog

2017-03-17 Thread Daniel-Constantin Mierla

Hello,

set memdbg and memlog parameters to a higher value than debug parameter.
The messages are useful only if you troubleshoot memory operations.

Cheers,
Daniel


On 16/03/2017 21:16, Diego Nadares wrote:
> Hi Guys,
>
> I'm seeing a lot of warnings in my syslog. Is this normal? Or maybe I
> am doing something wrong in my cfg?
>
> 
> Mar 16 17:11:47 dwsipm03 ./kamailio[26226]: WARNING: 
> [mem/f_malloc.c:444]: fm_malloc(): fm_malloc(0x7f68e5199010, 8) called
> from nathelper: nathelper.c: nh_timer(2078)
> Mar 16 17:11:47 dwsipm03 ./kamailio[26226]: WARNING: 
> [mem/f_malloc.c:527]: fm_malloc(): fm_malloc(0x7f68e5199010, 8)
> returns address 0x7f68e52a2d50
> Mar 16 17:11:47 dwsipm03 ./kamailio[26226]: WARNING: 
> [mem/f_malloc.c:588]: fm_free(): fm_free(0x7f68e5199010,
> 0x7f68e52a2d50), called from nathelper: nathelper.c: nh_timer()
> Mar 16 17:11:47 dwsipm03 ./kamailio[26226]: WARNING: 
> [mem/f_malloc.c:607]: fm_free(): fm_free: freeing block alloc'ed from
> nathelper: nathelper.c: nh_timer(2078)
> .
> Mar 16 17:15:44 dwsipm03 ./kamailio[26210]: WARNING: 
> [mem/f_malloc.c:607]: fm_free(): fm_free: freeing block alloc'ed from
> core: xavp.c: xavp_new_value(94)
> Mar 16 17:15:44 dwsipm03 ./kamailio[26210]: WARNING: 
> [mem/f_malloc.c:588]: fm_free(): fm_free(0x7f68d9d51000,
> 0x7f68da069ca8), called from tm: h_table.c: free_cell_helper(246)
> Mar 16 17:15:44 dwsipm03 ./kamailio[26210]: WARNING: 
> [mem/f_malloc.c:607]: fm_free(): fm_free: freeing block alloc'ed from
> tm: h_table.c: build_cell(317)
> Mar 16 17:15:44 dwsipm03 ./kamailio[26210]: WARNING: 
> [mem/f_malloc.c:588]: fm_free(): fm_free(0x7f68d9d51000,
> 0x7f68da031f00), called from tm: h_table.c: free_cell_helper(150)
> 
>
>
> Thanks in advance.
>
> Diego
>
>
> ___
> 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
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

___
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] (no subject) - EU toll free numbers

2017-03-17 Thread Daniel-Constantin Mierla

Hello,

first: it is recommended to add subject to emails to mailing lists,
otherwise it is not indexed properly in the archive.

Probably Voxbone is an option and I guess you can find more for various
countries.

Cheers,
Daniel

On 16/03/2017 20:02, Alberto Llamas wrote:
> Hi Guys,
>
> Who knows and can recommend a company a company where I could order
> Toll free numbers for EU?.
>
> I really appreciate any hint and sorry for the noise.
>
> Regards,
>
> -- 
> Alberto Llamas
> TelecommunicationsEngineer
> dCAP | KPAC | SSCA
>
>
>
> /"Internet is all about share"/
>
>
> ___
> 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
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

___
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] cisco spa502g issues

2017-03-17 Thread Ben Kramer


Hi guys,

we have a bunch of SIP phones behind a fire wall, with our kamalio 
server out on the internet. Most of them are the older SPA92x series, 
but we have some new SPA502g's.


We have no problems calling between 92x and 502's. How ever the 502's 
calling each other do not get voice path.


I have noticed that the phones REGISTER differently:

AOR:: 5546@
Contact:: sip:5546@:1032 Q=
Expires:: 180
Callid:: 4754c4f9-c67e1018@10.0.41.29
Cseq:: 43112
User-agent:: Cisco/SPA502G-7.6.2a
State:: CS_DIRTY
Flags:: 0
Cflag:: 0
Socket:: udp::5060
Methods:: 6815


AOR:: 5...@sip.skunkworks.net.au
Contact:: sip:5590@10.0.41.14:5060 Q=
Expires:: 1154
Callid:: 24435738-224b06db@10.0.41.14
Cseq:: 8012
User-agent:: Linksys/SPA921-5.1.8
Received:: sip::1026
State:: CS_SYNC
Flags:: 0
Cflag:: 64
Socket:: udp::5060
Methods:: 4767

The older 921 has its private IP in the contact, where as the newer 502 
has the external IP of our office in the contact.


Our file wall is a Watchguard T-10 (latest updates etc) with the SIP-ALG 
running.


Any thoughts on where to start looking ?

Cheers,

Ben.

___
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] Search for kamailio PERL module for 5.0 level

2017-03-17 Thread Daniel-Constantin Mierla

Hello,

links for various distros were added at:

  * https://www.kamailio.org/wiki/packages/rpms#kamailio_50x

A short report back on mailing list saying if the packages work ok would
be appreciated.

Cheers,
Daniel


On 16/03/2017 16:25, Ginhoux, Patrick wrote:
>
> Hi,
>
>  
>
> I just need to get the rpm but I have difficulties to find the correct
> link. Can you help on this ?
>
>  
>
> Cordialement
>
> Patrick GINHOUX
>
>  
>
> *De :*Daniel-Constantin Mierla [mailto:mico...@gmail.com]
> *Envoyé :* jeudi 16 mars 2017 16:10
> *À :* Ginhoux, Patrick ; Kamailio (SER)
> - Users Mailing List 
> *Objet :* Re: [SR-Users] Search for kamailio PERL module for 5.0 level
>
>  
>
> Hello,
>
> I already triggered the rebuild of rpms, some of them being completed
> already:
>
>   -
> https://build.opensuse.org/package/show/home:kamailio:v5.0.0-rpms/kamailio50
>
> If you want to get access and play with the specs in order to tune the
> rpms, then make an account on that portal and let me know the user id
> -- I will be glad to allow others helping with the generations of
> rpms, because I don't really use rpm-based systems myself.
>
> Cheers,
> Daniel
>
> On 16/03/2017 15:08, Ginhoux, Patrick wrote:
>
> Hi Daniel,
>
>  
>
> Thanks for the help.
>
>  
>
> Can you tell me when I can expect to get the PERL module built for
> 5.0 ?
>
>  
>
> If it is something that you need to schedule (it is something I
> can understand), then I could use the kamailio 4.4 level instead
> of 5.0 .
>
>  
>
> Cordialement
>
> Patrick GINHOUX
>
>  
>
> *De :*sr-users [mailto:sr-users-boun...@lists.sip-router.org] *De
> la part de* Daniel-Constantin Mierla
> *Envoyé :* jeudi 16 mars 2017 13:13
> *À :* Kamailio (SER) - Users Mailing List
>  
> *Objet :* Re: [SR-Users] Search for kamailio PERL module for 5.0 level
>
>  
>
> Hello,
>
> probably perl module failed to be build on this distros by the
> opensuse build service. I will try to re-enable building them on
> centos and redhat and see the results.
>
> Cheers,
> Daniel
>
>  
>
> On 14/03/2017 18:08, Ginhoux, Patrick wrote:
>
> Hi,
>
>  
>
> I’m a beginner in the use of kamailio product, so I try below
> to explain my problem with my words:
>
>  
>
> 1)  PERL module issue :
>
>  
>
> Some years ago a SIP Router proxy running RedHat 6.2 was
> developped using the kamailio version 3.3 and the following
> packages used  :
>
>  
>
> kamailio-3.3.2-1.1.1.x86_64.rpm
>
> kamailio-snmpstats-3.3.2-1.1.1.x86_64.rpm
>
> kamailio-mysql-3.3.2-1.1.1.x86_64.rpm
>
> kamailio-perl-3.3.2-1.1.1.x86_64.rpm
>
>  
>
> We have the project to migrate this SIP Proxy to RedHat 7.1
> and used the latest Kamailio v5.0.0 Release:
>
>  
>
> kamailio-5.0.0-24.1.x86_64.rpm
>
> kamailio-mysql-5.0.0-24.1.x86_64.rpm
>
> kamailio-snmpstats-5.0.0-24.1.x86_64.rpm
>
>  
>
> However I don’t find the kamalio-perl package for RedHat 7.1.
> I see that the perl module has been renamed to ‘app_perl’ but
> I don’t find it either for kamailio 5.0.0.
>
>  
>
> 2)  Kamailio.cfg script
>
>  
>
> Our proxy used the kamailio.cfg from the sample  of the 3.3.3
> release.
>
>  
>
> So can I reuse the same 3.3.3 kamailio.cfg file with the 5.0.0
> release or should I migrate (rewrite it) from the 5.0.0 sample ?
>
>  
>
> So I’m looking for some help on these issues.
>
>  
>
> Is there people that had this case ?
>
>  
>
> Thanks in advance for any answer.
>
>  
>
> Cordialement
>
> Patrick GINHOUX
>
>  
>
> PS : I just create my account today but don’t get the email to
> validate it.
>
>  
>
>
>
>
>
> ___
>
> 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
>
> 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 
> 
>
>
>
> -- 
> Daniel-Constantin Mierla
> www.twitter.com/miconda  -- 
>

Re: [SR-Users] Error on of type <2> not found in module and SCTP API Not initialized

2017-03-17 Thread Ginhoux, Patrick

Thanks Federico for this answer,

I see that in my .cfg there was a double ‘h’ in the name, while now there is 
only one (I need probably new glasses ☺ ).

Now it is fixed but now I got an error with the PERL mdule I’m trying to get 
for Rhel 7:

Mar 16 13:46:38 vm-vse02-siprouter1 /usr/sbin/kamailio[6767]: INFO: app_perl 
[app_perl_mod.c:219]: parser_init(): setting lib path: 
'/usr/lib64/kamailio/modules/'
Mar 16 13:46:38 vm-vse02-siprouter1 /usr/sbin/kamailio[6767]: ERROR: app_perl 
[app_perl_mod.c:241]: parser_init(): failed to load perl file 
"/etc/kamailio/snmptrap.pl" with code 2.
Mar 16 13:46:38 vm-vse02-siprouter1 /usr/sbin/kamailio[6767]: ERROR:  
[core/sr_module.c:968]: init_mod(): Error while initializing module app_perl 
(/usr/lib64/kamailio/modules/app_perl.so)

I opened another topic related to the rpm package for PERL module that is not 
available for Rhel 7 (see thread “Search for kamailio PERL module for 5.0 
level”).

Because I’m a newbie in this domain, I don’t have the experience to build a rpm 
package. Then one of my colleague helps me to build it. But because of this 
error, there is maybe something missing in the PERL installation on my server.
I’m doing some research.

If you have some ideas…

Cordialement
Patrick GINHOUX

De : sr-users [mailto:sr-users-boun...@lists.sip-router.org] De la part de 
Federico Cabiddu
Envoyé : jeudi 16 mars 2017 13:41
À : SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users 
Mailing List 
Objet : Re: [SR-Users] Error on  of type <2> not found 
in module  and SCTP API Not initialized

Hi,
param name has changed some versions ago:
http://www.kamailio.org/docs/modules/devel/modules/dispatcher.html#dispatcher.p.ds_probing_threshold

Cheers,

Federico

On 16 Mar 2017 13:35, "Ginhoux, Patrick" 
> wrote:
Hi,

I’m migrating my kamailio.cfg from the 3.3.1 release to 5.0.0 and encounter the 
following errors :

Mar 16 12:56:45 vm-vse02-siprouter1 systemd[1]: Starting SYSV: Kamailio is a 
fast, reliable and flexible SIP Server
Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: Not starting : invalid 
configuration file!
Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: 0(6652) ERROR:  
[core/modparam.c:141]: set_mod_param_regex(): parameter  
of type <2> not found in module 
Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: 0(6652) CRITICAL:  
[core/cfg.y:3404]: yyerror_at(): parse error in config file 
//etc/kamailio/kamailio.cfg, line 295, column 49: Can't set module parameter
Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: 0(6652) WARNING:  
[core/cfg.y:3378]: warn_at(): warning in config file 
//etc/kamailio/kamailio.cfg, line 971, column 6-13: constant value in if(...)
Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: ERROR: bad config file (1 
errors)
Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: 0(6652) INFO:  
[core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
Mar 16 12:56:45 vm-vse02-siprouter1 systemd[1]: kamailio.service: control 
process exited, code=exited status=1
Mar 16 12:56:45 vm-vse02-siprouter1 systemd[1]: Failed to start SYSV: Kamailio 
is a fast, reliable and flexible SIP Server..
Mar 16 12:56:45 vm-vse02-siprouter1 systemd[1]: Unit kamailio.service entered 
failed state.

Below the extract of my kamailio.cfg file :

modparam("dispatcher", "list_file", DISPATCHER_FILE)
modparam("dispatcher", "ds_probing_mode", 1)
modparam("dispatcher", "ds_probing_threshhold",3)
modparam("dispatcher", "flags", 2)
modparam("dispatcher", "attrs_avp", "$avp(dsattrs)")
modparam("dispatcher", "dst_avp", "$avp(dsdst)")
modparam("dispatcher", "grp_avp", "$avp(dsgrp)")
modparam("dispatcher", "cnt_avp", "$avp(dscnt)")
modparam("dispatcher", "ds_hash_size", 8)
modparam("dispatcher", "ds_ping_interval", 10)
modparam("dispatcher", "force_dst", 1)

For the dispatcher error :
I don’t find any change (eg in the Changelog for 5.0.0.) regarding the 
dispatcher module.
So is it a bug in the dispatcher module or have I to change it to something 
else ?

For the SCTP API error :
I don’t know what to do here.

Thanks to people that can help me on these 2 errors

Cordialement
Patrick GINHOUX


___
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] cisco spa502g issues

[SR-Users] Generate extra cdr per dialog

Re: [SR-Users] f_malloc WARNINGS in syslog

[SR-Users] ht_db_load_table(): key type must be string (type=6)

Re: [SR-Users] Error on of type <2> not found in module and SCTP API Not initialized

Re: [SR-Users] Configuration to fetch SIP response body.

Re: [SR-Users] Search for kamailio PERL module for 5.0 level

Re: [SR-Users] cisco spa502g issues

Re: [SR-Users] f_malloc WARNINGS in syslog

Re: [SR-Users] (no subject) - EU toll free numbers

[SR-Users] cisco spa502g issues

Re: [SR-Users] Search for kamailio PERL module for 5.0 level

Re: [SR-Users] Error on of type <2> not found in module and SCTP API Not initialized

13 matches

Site Navigation

Mail list logo

Footer information