Re: [SR-Users] how to drop 200ok and survive?

[Daniel-Constantin Mierla]

Hello,

On 18/02/16 20:35, Uri Shacked wrote:
> Hi,
>
> for some strange reason, ask my regulator i need to manipulate
> certain calls.
> the scenario goes like this:
>
> 1. caller sends invite to kamailio.
> 2. kamailio transfer the call to asterisk.
> 3. asterisk send progress and play "hello".
> 4. asterisk creates a new call (dial) to the same kamailio with
> destination callee.
> 5. the callee answers the call.
>
> here, i need to block the 200ok. so that the caller does not receive it.
>
> i managed to block it with t_suspend().
> but, there is no bidirectional media.
> the 183 progress was sent with sendreceive.
> it seems the asterisk is waiting for the ACK in order to open both
> ways for media.
>
> i tried to use uac_send_req() but it is being sent with no to tag. and
> when i try manipulating the uac_req(turi) it does not help because it
> takes all the string i entered and wraps it with <>.
>
> any ideas?
>
But if asterisk is waiting for ACK, that is not going to happen if you
drop the 200ok.

Maybe Asterisk is waiting for PRACK following the 183, can you check the
Requires header in 183?

While 200ok can be dropped by having a reply_route with drop for 200ok,
it doesn't feel like it is solving what you are looking for.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
http://miconda.eu


___
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] dispatcher flag

[Daniel-Constantin Mierla]

Btw, if you just want to see if it is active or inactive, it may work by
ds_select_dst() and see if the $du or any of $avp(AVP_DST) is the uri,
if not then is inactive.

Cheers,
Daniel

On 18/02/16 11:59, alexandre.ancone...@orange.com wrote:
>
> Ok thanks i’m going to try this.
>
> Best regards.
>
> Alexandre
>
>  
>
> *De :*sr-users [mailto:sr-users-boun...@lists.sip-router.org] *De la
> part de* Daniel-Constantin Mierla
> *Envoyé :* jeudi 18 février 2016 11:27
> *À :* Kamailio (SER) - Users Mailing List
> *Objet :* Re: [SR-Users] dispatcher flag
>
>  
>
> Hello,
>
> jsonrpc-s module has a function to execute rpc commands from kamailio.cfg:
>
> -
> http://www.kamailio.org/docs/modules/devel/modules/jsonrpc-s.html#jsonrpc-s.f.jsonrpc_exec
>
> Then you can use jansson module to get the values from the json rpc
> result.
>
> Cheers,
> Daniel
>
> On 18/02/16 09:35, alexandre.ancone...@orange.com
>  wrote:
>
> Hi,
>
> I’m using the dispatcher module with Kamailio 4.3.4, the keep
> alive mechanism and the routing are OK, but I would like to get in
> my request_route the flag(s) (active, inactive, probing …) that
> the dispatcher give to each destination. I know that in command
> line I can run kamcmd or kamctl to get :
>
>  
>
> NRSETS: 1
>
> RECORDS: {
>
> SET: {
>
> ID: 1
>
> TARGETS: {
>
> DEST: {
>
> URI: sip: xxx.xxx.xxx.xxx:
>
> FLAGS: IP
>
> PRIORITY: 0
>
> }
>
> DEST: {
>
> URI: sip:xxx.xxx.xxx.xxx:
>
> FLAGS: AP
>
> PRIORITY: 0
>
> How can I get that in the request_route process ? Any suggestion
> would be appreciated ;)
>
> Best Regards,
>
> Alexandre.
>
>  
>
> 
> _
>
>  
>
> Ce message et ses pieces jointes peuvent contenir des informations 
> confidentielles ou privilegiees et ne doivent donc
>
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez 
> recu ce message par erreur, veuillez le signaler
>
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
> electroniques etant susceptibles d'alteration,
>
> Orange decline toute responsabilite si ce message a ete altere, deforme 
> ou falsifie. Merci.
>
>  
>
> This message and its attachments may contain confidential or privileged 
> information that may be protected by law;
>
> they should not be distributed, used or copied without authorisation.
>
> If you have received this email in error, please notify the sender and 
> delete this message and its attachments.
>
> As emails may be altered, Orange is not liable for messages that have 
> been modified, changed or falsified.
>
> Thank you.
>
>
>
>
> ___
>
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>
> sr-users@lists.sip-router.org 
>
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
>
> -- 
> Daniel-Constantin Mierla
> http://twitter.com/#!/miconda  - 
> http://www.linkedin.com/in/miconda
> Book: SIP Routing With Kamailio - http://www.asipto.com
> http://miconda.eu
> _
>
> Ce message et ses pieces jointes peuvent contenir des informations 
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu 
> ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou 
> falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged 
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete 
> this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been 
> modified, changed or falsified.
> Thank you.

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
http://miconda.eu

[SR-Users] ACC Module

[Alberto Sagredo]

I have a strange behaviour when configuring ACC module to put CDRs

It must be as simple as this:

modparam("acc", "cdr_enable", 1)

But got this error:

feb 19 09:26:14 kamailio /usr/local/sbin/kamailio[23712]: ERROR: acc
[acc_mod.c:604]: mod_init(): failed to init cdr generation
feb 19 09:26:14 kamailio /usr/local/sbin/kamailio[23712]: ERROR: 
[sr_module.c:962]: init_mod(): Error while initializing module acc
(/usr/local/lib64/kamailio/modules/acc.so)


I have read documentation and seems ok. Tables in databases are created and
ALTER commands applied. IM getting actually ACC registers on acc table, but
could not active cdrs for acc.

What am i missing?
___
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] ACC Module

[Alberto Sagredo]

Looking into code is related to this previously error

ERROR: acc [acc_cdr.c:852]: init_cdr_generation(): can't load dialog API



2016-02-19 9:28 GMT+01:00 Alberto Sagredo :

> I have a strange behaviour when configuring ACC module to put CDRs
>
> It must be as simple as this:
>
> modparam("acc", "cdr_enable", 1)
>
> But got this error:
>
> feb 19 09:26:14 kamailio /usr/local/sbin/kamailio[23712]: ERROR: acc
> [acc_mod.c:604]: mod_init(): failed to init cdr generation
> feb 19 09:26:14 kamailio /usr/local/sbin/kamailio[23712]: ERROR: 
> [sr_module.c:962]: init_mod(): Error while initializing module acc
> (/usr/local/lib64/kamailio/modules/acc.so)
>
>
> I have read documentation and seems ok. Tables in databases are created
> and ALTER commands applied. IM getting actually ACC registers on acc table,
> but could not active cdrs for acc.
>
> What am i missing?
>
___
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] ACC Module

[Alberto Sagredo]

I had to previously load dialog module :)

loadmodule "dialog.so"
modparam("dialog", "default_timeout", 43200 )
modparam("dialog", "db_mode", 0 ) # no database writes
modparam("dialog", "dlg_flag", 3 )
modparam("dialog", "hash_size",  4096 )

Hope this would help to anyone.




2016-02-19 9:47 GMT+01:00 Alberto Sagredo :

> Looking into code is related to this previously error
>
> ERROR: acc [acc_cdr.c:852]: init_cdr_generation(): can't load dialog API
>
>
>
> 2016-02-19 9:28 GMT+01:00 Alberto Sagredo :
>
>> I have a strange behaviour when configuring ACC module to put CDRs
>>
>> It must be as simple as this:
>>
>> modparam("acc", "cdr_enable", 1)
>>
>> But got this error:
>>
>> feb 19 09:26:14 kamailio /usr/local/sbin/kamailio[23712]: ERROR: acc
>> [acc_mod.c:604]: mod_init(): failed to init cdr generation
>> feb 19 09:26:14 kamailio /usr/local/sbin/kamailio[23712]: ERROR: 
>> [sr_module.c:962]: init_mod(): Error while initializing module acc
>> (/usr/local/lib64/kamailio/modules/acc.so)
>>
>>
>> I have read documentation and seems ok. Tables in databases are created
>> and ALTER commands applied. IM getting actually ACC registers on acc table,
>> but could not active cdrs for acc.
>>
>> What am i missing?
>>
>
>
___
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] Registration Failure - IMS

[Cristina Caridi]

Hello Franz,

sorry but I missed your previuos mail.
In the attach you can find the trace of the registration.

Thank you,
Cristina

2016-02-16 17:06 GMT+01:00 Cristina Caridi :

> Hello,
> do you have any suggestion on this?
>
> Thank You,
> Cristina
>
>
> -- Forwarded message --
> From: Cristina Caridi 
> Date: 2016-02-05 9:26 GMT+01:00
> Subject: Re: [SR-Users] Registration Failure - IMS
> To: Jason Penton 
> Cc: Daniel-Constantin Mierla , "Kamailio (SER) - Users
> Mailing List" 
>
>
> Hello,
>
> thank you for the responsive answer!
> Ok, I will skip IP SEC mechanism for the moment :)
>
> But I have another problem related to registration process. After
> REGISTER-401 Unauthorized-REGISTER-200 OK, the IMS client sends the
> SUBSCRIBE message (for the "reg" event package subscription) to the S-CSCF,
> the latter replies with NOTIFY and the client correctly responds with 200
> OK. In order to be notified on any change of registration state for the
> client, also the P-CSCF sends the SUBSCRIBE message to the S-CSCF, the
> S-CSCF sends a NOTIFY to the proxy but, instead of replying with 200 OK,
> the P-CSCF replies with 404-Not Here (like it doesn't recognize that the
> recipient of the NOTIFY in the Req-URI is the P-CSCF itself).
>
> Have you ever seen similar issue?
> I've checked the S-CSCF database and it correctly contains the P-CSCF
> subscription. Can you suggest any workaround or I'm missing something?
>
> Thank you for your support,
>
> Cristina
>
>
>
> 2016-02-04 21:26 GMT+01:00 Jason Penton :
>
>> Hi Cristina,
>>
>> Unfortunately IPSEC is not supported 100% on the P-CSCF at this time.
>> There are pieces of code that exist for it but it is not something we
>> focused on yet. Perhaps some of the other devs will get to it when they get
>> the need or some spare time
>>
>> Cheers
>> Jason
>>
>> On Thu, Feb 4, 2016 at 7:42 PM, Daniel-Constantin Mierla <
>> mico...@gmail.com> wrote:
>>
>>> Hello,
>>>
>>> maybe some other IMS guys are able to help more, but in general the
>>> authentication in handled in the configuration file of Kamailio by calling
>>> various auth functions. You have to spot where those are used and why is
>>> responding with 401. Eventually run it with debug=3 in kamailio.cfg to get
>>> more verbosity of what it is done in the code.
>>>
>>> Also, it may help to check the emails from Franz Edler during January
>>> and February on this list, he provided configs and many details about
>>> building a prototype IMS platform. See next link and follow up discussion:
>>>
>>>   -
>>> http://lists.sip-router.org/pipermail/sr-users/2016-January/091204.html
>>>
>>> Cheers,
>>> Daniel
>>>
>>> On 03/02/16 11:58, Cristina Caridi wrote:
>>>
>>> Hello,
>>>
>>> I'm a new starter of Kamailio (SER). I am using the version 4.4.0-dev6
>>> in a Debian machine.
>>> I've configured all the IMS network elements, the FHoSS and also Boghe
>>> IMS/RCS client in a Windows machine.
>>>
>>> When an IMS user belonging to my network tries to register and IP SEC
>>> mechanism is enabled, the registration flow stops at 401 Unauthorized from
>>> S-CSCF -> I-CSCF -> P-CSCF -> client.
>>> The problem is that the HSS in MAA message does not send the
>>> SIP-Auth-Data-item that should be cointain the Confidentiality Key and the
>>> Integrity Key; so the client is not able to challenge the S-CSCF sending
>>> another REGISTER message.
>>>
>>> Do you have any suggestions about this? When IP SEC is disabled (by
>>> managing client options), the registration works well.
>>> Maybe is there any configuration at HSS level that i'm not considering?
>>>
>>> Thank you in advance for your help,
>>> Cristina
>>>
>>>
>>> ___
>>> 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
>>> Book: SIP Routing With Kamailio - http://www.asipto.comhttp://miconda.eu
>>>
>>>
>>> ___
>>> 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
>>>
>>>
>>
>>
>> --
>>
>> *Jason Penton*
>> *Senior Manager: Applications and Services*
>> *Smile Communications Pty (Ltd)*
>> *Mobile:* +27 (0) 83 283 7000
>> *Skype:* jason.barry.penton
>> jason.pen...@smilecoms.com 
>> www.smilecoms.com
>>
>>
>>
>> This email is subject to the disclaimer of Smile Communications at 
>> http://www.smilecoms.com/home/email-disclaimer/ 
>> 
>>
>>
>
>


Registration_fail.pcap
Description: Binary data
___
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

Re: [SR-Users] Error or Bug: [t_msgbuilder.c:490]: build_local_reparse(): ERROR: build_local_reparse: HDR_EOH_T was not found

[Sid Mason]

That saved lives and many worried families are relieved!


On Fri, Feb 19, 2016 at 3:43 PM, Daniel-Constantin Mierla  wrote:

> You have to put end of line \r\n at the end of the parameter for
> append_hf().
>
> Cheers,
> Daniel
>
>
> On 19/02/16 08:39, Sid Mason wrote:
>
> Yes, there is a append_hf("Remote-Party-ID:
>
> below is the complete section:
>
>
> # Send to Asterisk
> route[TOASTERISK] {
> ds_mark_dst("P");
> if(!ds_select_dst("1", "4")) {
> sl_send_reply("500", "Service Unavailable");
> xlog("L_INFO","[$fU@$si:$sp]{$rm} No destinations available for $rd \n");
> exit;
> }
> # Replace FROM header to Kamailio's address
> #
> http://www.kamailio.org/docs/modules/4.3.x/modules/uac.html#uac.f.uac_replace_from
> uac_replace_from("","sip:$sel(cfg_get.kamailio.bind_external_domain):5060"
> );
> # rewrite Destinatin URI
> #$du= $au + "@10.1.4.22:5060";
> # Add Remote-Party-ID to header
> append_hf("Remote-Party-ID: \"$au\"
> 
> ;party=calling;privacy=off;screen=no");
> xlog("L_INFO","route[TOASTERISK]: [$fU@$si:$sp]{$rm} From Outside World
> to Asterisk Box $du\n");
> rtpproxy_manage("cawei");
>
> route(RELAY);
> exit;
> }
>
> Regards
>
>
> Subject: Re: [SR-Users] Error or Bug: [t_msgbuilder.c:490]:
> build_local_reparse(): ERROR: build_local_reparse: HDR_EOH_T was
> not
> found
> Message-ID: < <56b79afd.8010...@gmail.com>56b79afd.8010...@gmail.com>
> Content-Type: text/plain; charset="windows-1252"
>
> Hello,
>
> do you have an action like:
>
> append_hf("Remote-Party-ID: ...");
>
> in kamailio.cfg?
>
> Can you paste all that action here?
>
> Cheers,
> Daniel
>
>
> --
> Daniel-Constantin Mierlahttp://twitter.com/#!/miconda - 
> http://www.linkedin.com/in/miconda
> Book: SIP Routing With Kamailio - http://www.asipto.comhttp://miconda.eu
>
>
___
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] how to drop 200ok and survive?

[Uri Shacked]

Hi,

thanks for the quick response.
regarding to the 200 drop, it is less of an issue. i actually tried
t_drop_replies() on the reply_route.
it works only on failure_route.
but, didn't try another on_reply route and drop. i will try. thanks.

still, daniel is right, the main problem is the ACK.
as i wrote, i use uac_req_send() to try and send the asterisk a fake ACK.

i enter the following:

$uac_req(method)="ACK";
$uac_req(ruri)= "exten@asterisk:5080";
$uac_req(furi)="f...@caller.com";
$uac_req(turi)="exten@asterisk:5080" + ";" + "saved_to_tag"
$uac_req(callid)=$dlg(callid);
uac_req_send();

the problem is that the actual ACK sent, is malformed in the TO header.

it is populated as 
instead of ;to_tag

what do you think?

thanks,
uri





Hello,
>
> On 18/02/16 20:35, Uri Shacked wrote:
> > Hi,
> >
> > for some strange reason, ask my regulator i need to manipulate
> > certain calls.
> > the scenario goes like this:
> >
> > 1. caller sends invite to kamailio.
> > 2. kamailio transfer the call to asterisk.
> > 3. asterisk send progress and play "hello".
> > 4. asterisk creates a new call (dial) to the same kamailio with
> > destination callee.
> > 5. the callee answers the call.
> >
> > here, i need to block the 200ok. so that the caller does not receive it.
> >
> > i managed to block it with t_suspend().
> > but, there is no bidirectional media.
> > the 183 progress was sent with sendreceive.
> > it seems the asterisk is waiting for the ACK in order to open both
> > ways for media.
> >
> > i tried to use uac_send_req() but it is being sent with no to tag. and
> > when i try manipulating the uac_req(turi) it does not help because it
> > takes all the string i entered and wraps it with <>.
> >
> > any ideas?
> >
> But if asterisk is waiting for ACK, that is not going to happen if you
> drop the 200ok.
>
> Maybe Asterisk is waiting for PRACK following the 183, can you check the
> Requires header in 183?
>
> While 200ok can be dropped by having a reply_route with drop for 200ok,
> it doesn't feel like it is solving what you are looking for.
>
> 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] BUG: qm_free: freeing already freed pointer

[Rene Montilva]

Hi Daniel

i made the  version change to 4.3.4 , but now i got this error and then the
kamailio froze

Feb 19 10:18:22 server6-2 /usr/sbin/kamailio[3403]: WARNING: tm
[h_table.c:130]: free_cell_helper(): removed cell 0x7ff2dd63d548 is still
linked in hash table (t_lookup.c:1486)
Feb 19 10:18:22 server6-2 kernel: [5743376.041415] kamailio[3430]: segfault
at 0 ip 7ff3602a8fb2 sp 7fff2b1c22f0 error 6 in
tm.so[7ff36025+eb000]
Feb 19 10:18:22 server6-2 /usr/sbin/kamailio[3324]: ALERT: 
[main.c:728]: handle_sigs(): child process 3430 exited by a signal 11
Feb 19 10:18:22 server6-2 /usr/sbin/kamailio[3324]: ALERT: 
[main.c:731]: handle_sigs(): core was not generated
Feb 19 10:18:22 server6-2 /usr/sbin/kamailio[3324]: INFO: 
[main.c:743]: handle_sigs(): terminating due to SIGCHLD
Feb 19 10:18:22 server6-2 /usr/sbin/kamailio[3437]: INFO: 
[main.c:798]: sig_usr(): signal 15 received
Feb 19 10:18:22 server6-2 /usr/sbin/kamailio[3431]: INFO: 
[main.c:798]: sig_usr(): signal 15 received
Feb 19 10:18:22 server6-2 /usr/sbin/kamailio[3438]: INFO: 
[main.c:798]: sig_usr(): signal 15 received
Feb 19 10:18:22 server6-2 /usr/sbin/kamailio[3434]: INFO: 
[main.c:798]: sig_usr(): signal 15 received
Feb 19 10:18:22 server6-2 /usr/sbin/kamailio[3432]: INFO: 
[main.c:798]: sig_usr(): signal 15 received
Feb 19 10:18:22 server6-2 /usr/sbin/kamailio[3428]: INFO: 
[main.c:798]: sig_usr(): signal 15 received




Feb 19 10:18:22 server6-2 /usr/sbin/kamailio[3324]: WARNING: tm
[h_table.c:130]: free_cell_helper(): removed cell 0x7ff2dd649438 is still
linked in hash table (h_table.c:440)
Feb 19 10:18:22 server6-2 /usr/sbin/kamailio[3324]: WARNING: tm
[h_table.c:130]: free_cell_helper(): removed cell 0x7ff2dd622fb8 is still
linked in hash table (h_table.c:440)
Feb 19 10:18:22 server6-2 /usr/sbin/kamailio[3324]: INFO: 
[sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized


On Tue, Feb 16, 2016 at 11:26 AM, Rene Montilva 
wrote:

> Yes, i'll do it
>
> thanks Daniel, for you support
>
> On Tue, Feb 16, 2016 at 11:12 AM, Daniel-Constantin Mierla <
> mico...@gmail.com> wrote:
>
>> Hello,
>>
>> can you upgrade to latest version in  branch 4.3? Or at least the release
>> of 4.4.
>>
>> Cheers,
>> Daniel
>>
>>
>> On 16/02/16 14:30, Rene Montilva wrote:
>>
>> Hi Daniel
>>
>> it is:
>>
>> version: kamailio 4.3.3 (x86_64/linux)
>> flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS,
>> DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC,
>> DBG_QM_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE,
>> USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
>> ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
>> MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
>> poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
>> id: unknown
>> compiled with gcc 4.7.2
>>
>>
>> On Tue, Feb 16, 2016 at 2:38 AM, Daniel-Constantin Mierla <
>> mico...@gmail.com> wrote:
>>
>>> Hello,
>>>
>>> what is the exact version you are running (kamailio -v)?
>>>
>>> This issue should handled nicer by the latest branch 4.3.
>>>
>>> Cheers,
>>> Daniel
>>>
>>>
>>> On 16/02/16 02:31, Rene Montilva wrote:
>>>
>>> Hi list
>>>
>>> i've got this bug report in kamailio 4.3 at syslog, then it frozen, i
>>> checked my config file looking for htable parameter, and i notice i have
>>> htable param without autexpire
>>>
>>> is this reason why kamailio crash?
>>>
>>> "/usr/sbin/kamailio[24113]: :  [mem/q_malloc.c:453]: qm_free():
>>> BUG: qm_free: freeing already freed pointer (0x7f673dead5d8), called from
>>>  tm: h_table.c: free_cell(133), first free tm: h_table.c: free_cell(133)
>>> - aborting "
>>>
>>>
>>> --
>>> Ing. Rene Montilva
>>> *FOSS Developer and VoIP Engineer.*
>>>
>>>
>>>
>>> ___
>>> 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
>>> Book: SIP Routing With Kamailio - http://www.asipto.comhttp://miconda.eu
>>>
>>>
>>> ___
>>> 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
>>>
>>>
>>
>>
>> --
>> Ing. Rene Montilva
>> *FOSS Developer and VoIP Engineer.*
>>
>>
>> --
>> Daniel-Constantin Mierlahttp://twitter.com/#!/miconda - 
>> http://www.linkedin.com/in/miconda
>> Book: SIP Routing With Kamailio - http://www.asipto.comhttp://miconda.eu
>>
>>
>
>
> --
> Ing. Rene Montilva
> *FOSS Developer and VoIP Engineer.*
>
>


-- 
Ing. Rene Montilva
*FOSS Developer and VoIP Engineer.*
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.si

Re: [SR-Users] rfc: kamailio.cfg polishing for v4.4

[Anthony Messina]

On Tuesday, February 09, 2016 08:45:23 AM Daniel-Constantin Mierla wrote:
> Hello,
> 
> wondering if people feel it is need to polish the current default
> kamailio.cfg, to prepare the version for next major release. It can be
> browsed online at:
> 
>   - https://github.com/kamailio/kamailio/blob/master/etc/kamailio.cfg
> 
> It is mainly about very common scenarios that are encountered out there
> and we should deal with by default. Have in mind that there are the
> basic and advanced versions of kamailio.cfg in the etc folder. Also, I
> am looking for tunings for core parameters and module parameters that
> make the config more suitable for common use case.
> 
> Speaking of those extra config files, I think the kamailio-advanced.cfg
> and kamailio-basic.cfg should be deployed in shared doc folder, not
> being active configs upon default installation.
> 
> Cheers,
> Daniel

It would be nice to demonstrate consistent coding style, spaces, etc.

if(...
if (...

And maybe this is more a wish for proper advice than cleanup, but I'd love to 
see the config show the recommended use of rtpengine_manage() (not rtpproxy) 
in the branch_route and decouple rtpengine from NAT, as it can bridge between 
significantly more than just internal/external interfaces.

-A

-- 
Anthony - https://messinet.com/ - https://messinet.com/~amessina/gallery
8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E


signature.asc
Description: This is a digitally signed message part.
___
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] DNSSRV to resolve to multiple Kamailio servers

[Derek Bolichowski]

Hello,
I'm trying to create a DNSSRV record that resolves to multiple Kamailio servers 
for my clients to authenticate against.  Before using Kamailio, we had a DNSSRV 
record setup that resolved to our multiple Asterisk servers via their WAN 
Address.

I've tried to do the same with Kamailio, but not having much luck.

The DNSSRV record is setup as follows, as you can see from the output of a 
`dig` query:

;_sip._udp.kam.some-domain.com.   IN  SRV

;; ANSWER SECTION:
_sip._udp.kam.some-domain.com. 14399 IN   SRV 20 100 5060 
kam1.some-domain.com.
_sip._udp.kam.some-domain.com. 14399 IN   SRV 10 100 5060 
kam2.some-domain.com.

I am not able to register any devices to this SRV record.  However I /CAN/ 
register directly to kam1.some-domain.com and kam2.some-domain.com

Registration attempts to the DNSSRV Record (kam.some-domain.com) do not even 
appear in /var/log/messages.

We have the domain name for kam (SRV Record), kam1 and kam2 setup in 
kamailio.domain and kamailio.dispatcher.

What am I missing here?  Thank you for taking the time to read this!

Derek Bolichowski
___
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] [SPAM]Re: Registration Failure - IMS

[Franz Edler]

Hello Cristina,

> In the attach you can find the trace of the registration.

I have checked your tracefile and confirm: that is a problem which needs 
further debugging.
Up to now I did not activate "WITH_REGINFO" in my installation, therefore I 
cannot compare.
If I find time (this weekend) I will do that and come back with the findings.

BR Franz


___
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