[SR-Users] rtpengine inserted random line into sdp

2020-06-25 Thread Andrew Chen 
Hi forum,

I'm starting my rtpengine project and I'm facing a strange problem with
rtpengine.  I am seeing this in the SDP part of the INVITE:

a=rtcp:52021

a=rtcp-mux

2001:470:7:3A7:0:0:0:2

a=direction:active

a=oldmediaip:54.153.25.234

As you can see there is a random insert of the local kamailio IP in there
and I'm have tried the following to remove it but failed to succeed:

- Remove in the offer the combination of ICE and replace-session-connection
flags
- Switched between rtpengine_offer and rtpengine_manage
- Restarted ngcp-rtpengine-daemon process
- Used sdpops function sdp_remove_line_by_preifx()

Currently running Kamailio 5.1.2.

I am running out of ideas.

Any suggestions would be greatly appreciated.

-- 
Andy Chen
Sr. Telephony Lead Engineer
achen@ fuze.com

-- 
*Confidentiality Notice: The information contained in this e-mail and any

attachments may be confidential. If you are not an intended recipient, you

are hereby notified that any dissemination, distribution or copying of this

e-mail is strictly prohibited. If you have received this e-mail in error,

please notify the sender and permanently delete the e-mail and any

attachments immediately. You should not retain, copy or use this e-mail or

any attachment for any purpose, nor disclose all or any part of the

contents to any other person. Thank you.*
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Advertise concept

2020-06-25 Thread Fred Posner 
On Thu, 2020-06-25 at 11:22 -0500, Social Boh wrote:
> Sorry for private message, Fred
> Thank you for your answer. 
> 
> > You could use it for all communication, regardless of method... so
> > if 
> > behind NAT, it would certainly make sense to use advertise for 
> > registers. 
>  
> you means outbound register because behind NAT kamailio can't accept
> inbound register over public IP, right? 
> 
> 

The whole point of advertise is it will allow the inbound traffic to
work (including REGISTER) assuming you have your NAT forwarding set-up 
properly on whatever network device is handling this translation.

--fred


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Advertise concept

2020-06-25 Thread Social Boh 

Sorry for private message, Fred

Thank you for your answer.


You could use it for all communication, regardless of method... so if
behind NAT, it would certainly make sense to use advertise for
registers.


you means outbound register because behind NAT kamailio can't accept 
inbound register over public IP, right?


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org

https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Advertise concept

2020-06-25 Thread Fred Posner 
On Thu, 2020-06-25 at 09:23 -0500, Social Boh wrote:
> Hello,
> 
> maybe i don't understood completely the use of Advertise parameter.
> 
> We use it only if Kamailio is behind a NAT and Kamailio have to 
> comunicate over is PublicIP with provider, other SIP proxy and PBX
> but 
> never to accept Users REGISTER.
> 
> Is it right?
> 
> Regards
> 

You could use it for all communication, regardless of method... so if
behind NAT, it would certainly make sense to use advertise for
registers.

The most common use scenario would be when the kamailio server is
NAT'd and needs to advertise a public IP, however there are other use
cases when it can be utilized as well.

--fred


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Server error on LIR select next S-CSCF

2020-06-25 Thread BALL SUN 
anyone can help?

On Thu, Jun 25, 2020 at 12:38 AM BALL SUN  wrote:
>
> HI
>
> We noticed an issue here, not sure is it related to HSS profile.
>
> the setting is like this
> Caller: MSISDN-A, IMSI-A
> Called: MSISDN-B, IMSI-B
>
>
> Both UEs can be registered based on IMSI number. Also the
> corresponding tel:MSISDN is added to the corresponding IMPU.
>
> now, when we make a call from UE-A to UE-B, UE-A sends INVITE to
> Kamailio IMS,  the R-URI is sip:MSISDN-B, and LIR from I-CSCF sends to
> HSS and the check is based on the public identity tel:MSISDN-B, and it
> passed, and we noticed that the INVITE send out from P-CSCF to UE-B is
> with R-RUI = IMSI-B not MSISDN-B. This make the UE-B did not response
> and leading to "Server error on LIR select next S-CSCF'.
>
> anyone can help to point out the problem in where? which part of
> configuration in Kamailio or FHoSS?
>
> please help
>
> - RBK
>
>
> On Mon, Jun 22, 2020 at 12:12 PM BALL SUN  wrote:
> >
> > Hello
> >
> > Anyone has an idea?
> >
> >
> > On Fri, Jun 19, 2020 at 5:31 PM BALL SUN  wrote:
> > >
> > > Hi
> > >
> > > I have. but still not sure why.
> > >
> > > On Fri, Jun 19, 2020 at 4:43 PM Pavithra Mohanraja
> > >  wrote:
> > > >
> > > > Hi,
> > > >
> > > > Have you given your scscf domain in icscf db table ?
> > > > Also check ur scscf is running properly
> > > > Thanks,
> > > > Pavithra
> > > >
> > > > On Fri, Jun 19, 2020 at 1:22 PM BALL SUN  wrote:
> > > >>
> > > >> Hi
> > > >>
> > > >> I have a setup using Kamailio IMS, and when trying to make a SIP call
> > > >> between clients, S-CSCF returns " SIP/2.0 500 Server error on LIR
> > > >> select next S-CSCF", do you have any idea on how to fix?
> > > >>
> > > >> - RBK
> > > >>
> > > >> ___
> > > >> Kamailio (SER) - Users Mailing List
> > > >> sr-users@lists.kamailio.org
> > > >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
> > > >
> > > > ___
> > > > Kamailio (SER) - Users Mailing List
> > > > sr-users@lists.kamailio.org
> > > > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Advertise concept

2020-06-25 Thread Social Boh 

Hello,

maybe i don't understood completely the use of Advertise parameter.

We use it only if Kamailio is behind a NAT and Kamailio have to 
comunicate over is PublicIP with provider, other SIP proxy and PBX but 
never to accept Users REGISTER.


Is it right?

Regards

--
---
I'm SoCIaL, MayBe


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] kamailio - 5.3.2 - Possible memleak in Core Module

2020-06-25 Thread José Seabra 
Hi Daniel,
Thank you for your reply.

I will do stress tests with the latest version from branch 5.3.
If it is still happening I will let you know.

Cheers,
José

Daniel-Constantin Mierla  escreveu no dia quinta,
25/06/2020 à(s) 14:44:

> Hello,
>
> first, it is better if you test with latest version from the branch 5.3,
> because 5.3.2 is already outdated in that series. Otherwise, we may
> troubleshoot a side effect of an issue already fixed.
>
> Second, the function that allocated most of the shm memory is related to
> transaction, cloning the message in shared memory. Can you fetch the stats
> and see how many transactions are listed when you face that issues?
>
> kamctl stats
>
> Cheers,
> Daniel
> On 25.06.20 11:11, José Seabra wrote:
>
> Hello there.
>
> During my stress tests against our kamailio servers I detected that it was
> running out of shm memory.
>
>
> edge-sip-proxy[6119]: ERROR: ESP_LOG: 10405249-1580@10.225.121.206:
>  [core/mem/q_malloc.c:298]: qm_find_free():
> qm_find_free(0x7ff37092, 4224); Free fragment not found!
> edge-sip-proxy[6119]: ERROR: ESP_LOG: 10405249-1580@10.225.121.206:
>  [core/mem/q_malloc.c:432]: qm_malloc(): qm_malloc(0x7ff37092,
> 4224) called from core: core/sip_msg_clone.c: sip_msg_shm_clone(496),
> module: core; Free fragment not found!
> edge-sip-proxy[6119]: ERROR: ESP_LOG: 10405249-1580@10.225.121.206:
>  [core/sip_msg_clone.c:499]: sip_msg_shm_clone(): could not allocate
> shared memory from shm pool
> edge-sip-proxy[6119]: ERROR: ESP_LOG: 10405249-1580@10.225.121.206: tm
> [t_lookup.c:1293]: new_t(): out of mem:
> edge-sip-proxy[6119]: ERROR: ESP_LOG: 10405249-1580@10.225.121.206: tm
> [t_lookup.c:1439]: t_newtran(): new_t failed
> edge-sip-proxy[6119]: ERROR: ESP_LOG: 10405249-1580@10.225.121.206: sl
> [sl_funcs.c:392]: sl_reply_error(): stateless error reply used: I'm
> terribly sorry, server error occurred (1/SL)
>
>
> The output of kamctl stats shmem confirms that kamailio is running out of
> memory:
> {
>   "jsonrpc":  "2.0",
>   "result": [
> "shmem:fragments = 36427",
> "shmem:free_size = 14123552",
> "shmem:max_used_size = 268435456",
> "shmem:real_used_size = 254311904",
> "shmem:total_size = 268435456",
> "shmem:used_size = 215787904"
>   ],
>   "id": 10901
> }
>
> Then I was check what was the module that were consuming more memory with 
> kamcmd
> mod.stats all shm and the output of this command showed me that Core
> module was consuming most of shm memory, as you can see bellow is the
> output of this command shows that Core - build_req_buf_from_sip_req is
> consuming most of shm.
>
> Module: core
> {
> sip_msg_shm_clone(496): 4872856
> create_avp(175): 24768
> msg_lump_cloner(986): 154376
> xavp_new_value(106): 780896
> build_req_buf_from_sip_req(2187): 183984624
> counters_prefork_init(211): 36864
> cfg_clone_str(130): 96
> cfg_shmize(217): 848
> main_loop(1303): 8
> init_pt(106): 8
> init_pt(105): 8
> init_pt(104): 5256
> register_timer(995): 232
> cfg_register_ctx(47): 64
> init_tcp(5021): 8192
> init_tcp(5015): 32768
> init_tcp(5007): 8
> init_tcp(5000): 8
> init_tcp(4993): 8
> init_tcp(4987): 8
> init_tcp(4975): 8
> init_avps(90): 8
> init_avps(89): 8
> init_dst_blacklist(438): 16384
> init_dst_blacklist(430): 8
> timer_alloc(498): 96
> init_dns_cache(361): 8
> init_dns_cache(352): 16384
> init_dns_cache(344): 16
> init_dns_cache(336): 8
> init_timer(267): 8
> init_timer(266): 16384
> init_timer(265): 8
> init_timer(264): 8
> init_timer(253): 8
> init_timer(221): 8
> init_timer(210): 278544
> init_timer(209): 8
> init_timer(197): 8
> cfg_child_cb_new(829): 64
> sr_cfg_init(361): 8
> sr_cfg_init(354): 8
> sr_cfg_init(347): 8
> sr_cfg_init(335): 8
> sr_cfg_init(323): 8
> qm_shm_lock_init(1202): 8
> Total: 190229920
> }
>
> Then I stopped the sipp that was running against kamailio in order to see
> if the memory consumed by *build_req_buf_from_sip_req* decreased but it
> didn't, so, it seems that there is a memleak in this version.
>
> If the information that I'm sending in this email is not enough to
> identify the root cause of this, please let me know if there is anything
> else that I can do here to help identify better what is the main reason.
> Than you
>
> Best Regards
> --
> Cumprimentos
> José Seabra
>
> ___
> Kamailio (SER) - Users Mailing 
> Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
> --
> Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- 
> www.linkedin.com/in/miconda
> Funding: https://www.paypal.me/dcmierla
>
>

-- 
Cumprimentos
José Seabra
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] kamailio - 5.3.2 - Possible memleak in Core Module

2020-06-25 Thread Daniel-Constantin Mierla 
Hello,

first, it is better if you test with latest version from the branch 5.3,
because 5.3.2 is already outdated in that series. Otherwise, we may
troubleshoot a side effect of an issue already fixed.

Second, the function that allocated most of the shm memory is related to
transaction, cloning the message in shared memory. Can you fetch the
stats and see how many transactions are listed when you face that issues?

kamctl stats

Cheers,
Daniel

On 25.06.20 11:11, José Seabra wrote:
> Hello there.
>
> During my stress tests against our kamailio servers I detected that it
> was running out of shm memory.
>
>
> edge-sip-proxy[6119]: ERROR: ESP_LOG: 10405249-1580@10.225.121.206
> : 
> [core/mem/q_malloc.c:298]: qm_find_free():
> qm_find_free(0x7ff37092, 4224); Free fragment not found!
> edge-sip-proxy[6119]: ERROR: ESP_LOG: 10405249-1580@10.225.121.206
> : 
> [core/mem/q_malloc.c:432]: qm_malloc(): qm_malloc(0x7ff37092,
> 4224) called from core: core/sip_msg_clone.c: sip_msg_shm_clone(496),
> module: core; Free fragment not found!
> edge-sip-proxy[6119]: ERROR: ESP_LOG: 10405249-1580@10.225.121.206
> : 
> [core/sip_msg_clone.c:499]: sip_msg_shm_clone(): could not allocate
> shared memory from shm pool
> edge-sip-proxy[6119]: ERROR: ESP_LOG: 10405249-1580@10.225.121.206
> : tm [t_lookup.c:1293]: new_t():
> out of mem:
> edge-sip-proxy[6119]: ERROR: ESP_LOG: 10405249-1580@10.225.121.206
> : tm [t_lookup.c:1439]:
> t_newtran(): new_t failed
> edge-sip-proxy[6119]: ERROR: ESP_LOG: 10405249-1580@10.225.121.206
> : sl [sl_funcs.c:392]:
> sl_reply_error(): stateless error reply used: I'm terribly sorry,
> server error occurred (1/SL)
>
>
> The output of kamctl stats shmem confirms that kamailio is running out
> of memory:
> {
>   "jsonrpc":  "2.0",
>   "result": [
>     "shmem:fragments = 36427",
>     "shmem:free_size = 14123552",
>     "shmem:max_used_size = 268435456",
>     "shmem:real_used_size = 254311904",
>     "shmem:total_size = 268435456",
>     "shmem:used_size = 215787904"
>   ],
>   "id": 10901
> }
>
> Then I was check what was the module that were consuming more memory
> with kamcmd mod.stats all shm and the output of this command showed me
> that Core module was consuming most of shm memory, as you can see
> bellow is the output of this command shows that Core -
> build_req_buf_from_sip_req is consuming most of shm.
>  
> Module: core
> {
> sip_msg_shm_clone(496): 4872856
> create_avp(175): 24768
> msg_lump_cloner(986): 154376
> xavp_new_value(106): 780896
> build_req_buf_from_sip_req(2187): 183984624
> counters_prefork_init(211): 36864
> cfg_clone_str(130): 96
> cfg_shmize(217): 848
> main_loop(1303): 8
> init_pt(106): 8
> init_pt(105): 8
> init_pt(104): 5256
> register_timer(995): 232
> cfg_register_ctx(47): 64
> init_tcp(5021): 8192
> init_tcp(5015): 32768
> init_tcp(5007): 8
> init_tcp(5000): 8
> init_tcp(4993): 8
> init_tcp(4987): 8
> init_tcp(4975): 8
> init_avps(90): 8
> init_avps(89): 8
> init_dst_blacklist(438): 16384
> init_dst_blacklist(430): 8
> timer_alloc(498): 96
> init_dns_cache(361): 8
> init_dns_cache(352): 16384
> init_dns_cache(344): 16
> init_dns_cache(336): 8
> init_timer(267): 8
> init_timer(266): 16384
> init_timer(265): 8
> init_timer(264): 8
> init_timer(253): 8
> init_timer(221): 8
> init_timer(210): 278544
> init_timer(209): 8
> init_timer(197): 8
> cfg_child_cb_new(829): 64
> sr_cfg_init(361): 8
> sr_cfg_init(354): 8
> sr_cfg_init(347): 8
> sr_cfg_init(335): 8
> sr_cfg_init(323): 8
> qm_shm_lock_init(1202): 8
> Total: 190229920
> }
>
> Then I stopped the sipp that was running against kamailio in order to
> see if the memory consumed by /build_req_buf_from_sip_req/ decreased
> but it didn't, so, it seems that there is a memleak in this version.
>  
> If the information that I'm sending in this email is not enough to
> identify the root cause of this, please let me know if there is
> anything else that I can do here to help identify better what is the
> main reason.
> Than you
>
> Best Regards
> -- 
> Cumprimentos
> José Seabra
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Funding: https://www.paypal.me/dcmierla

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] siptrace: methods blacklist modparam

2020-06-25 Thread Nuno Ferreira 
Hello,

We are a heavy Homer/Hepic (tks QXIP team) users and on our setup, there
are some SIP methods we don’t want to get into the database or send to the
capture server because there’s no value-added for call troubleshooting
purposes (OPTIONS, KDMQ, HTTP (from JSONRPC)…)

Typically we achieve the message filtering using siptrace in “manual” mode
and control what to send from the script. This works fine for some
situations, but there are a few we need to have the automatic mode on:

   -

   topos enabled: using manual mode we don’t get the “wire” version of the
   signaling
   -

   TCP connections: there are a few situations where the destination port
   is traced with 0 - I believe this is due to the fact the TCP socket not
   established when the message is collected


There are other technics to filter like using a HEP relay proxy dropping
unwanted traffic, but having a native kamailio functionality would make
things much easier. With that in mind, I’ve created a PR (#2374
) that allows to blacklist
methods we don’t want to send to the capture server when using automatic
trace mode. I believe this is a very helpful change for the community as
well.

To block SIP OPTIONS and KDMQ we just need to declare a new modparam:

modparam("siptrace", "trace_on", 1)

modparam("siptrace", "methods_blacklist_auto", 16896)

Let me know what you think about it.

Nuno

-- 
*Confidentiality Notice: The information contained in this e-mail and any

attachments may be confidential. If you are not an intended recipient, you

are hereby notified that any dissemination, distribution or copying of this

e-mail is strictly prohibited. If you have received this e-mail in error,

please notify the sender and permanently delete the e-mail and any

attachments immediately. You should not retain, copy or use this e-mail or

any attachment for any purpose, nor disclose all or any part of the

contents to any other person. Thank you.*
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] siptrace: methods blacklist modparam

2020-06-25 Thread Federico Cabiddu 
Hi Nuno,
I think it's a good and useful addition, I had a quick look on the PR and
it looks good, but I'll have a deeper look as soon as possible.

Cheers,

Federico

On Thu, Jun 25, 2020 at 11:30 AM Nuno Ferreira  wrote:

> Hello,
>
> We are a heavy Homer/Hepic (tks QXIP team) users and on our setup, there
> are some SIP methods we don’t want to get into the database or send to the
> capture server because there’s no value-added for call troubleshooting
> purposes (OPTIONS, KDMQ, HTTP (from JSONRPC)…)
>
> Typically we achieve the message filtering using siptrace in “manual” mode
> and control what to send from the script. This works fine for some
> situations, but there are a few we need to have the automatic mode on:
>
>-
>
>topos enabled: using manual mode we don’t get the “wire” version of
>the signaling
>-
>
>TCP connections: there are a few situations where the destination port
>is traced with 0 - I believe this is due to the fact the TCP socket not
>established when the message is collected
>
>
> There are other technics to filter like using a HEP relay proxy dropping
> unwanted traffic, but having a native kamailio functionality would make
> things much easier. With that in mind, I’ve created a PR (#2374
> ) that allows to
> blacklist methods we don’t want to send to the capture server when using
> automatic trace mode. I believe this is a very helpful change for the
> community as well.
>
> To block SIP OPTIONS and KDMQ we just need to declare a new modparam:
>
> modparam("siptrace", "trace_on", 1)
>
> modparam("siptrace", "methods_blacklist_auto", 16896)
>
> Let me know what you think about it.
>
> Nuno
>
> *Confidentiality Notice: The information contained in this e-mail and any
> attachments may be confidential. If you are not an intended recipient, you
> are hereby notified that any dissemination, distribution or copying of this
> e-mail is strictly prohibited. If you have received this e-mail in error,
> please notify the sender and permanently delete the e-mail and any
> attachments immediately. You should not retain, copy or use this e-mail or
> any attachment for any purpose, nor disclose all or any part of the
> contents to any other person. Thank you.*
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] kamailio - 5.3.2 - Possible memleak in Core Module

2020-06-25 Thread José Seabra 
Hello there.

During my stress tests against our kamailio servers I detected that it was
running out of shm memory.


edge-sip-proxy[6119]: ERROR: ESP_LOG: 10405249-1580@10.225.121.206: 
[core/mem/q_malloc.c:298]: qm_find_free(): qm_find_free(0x7ff37092,
4224); Free fragment not found!
edge-sip-proxy[6119]: ERROR: ESP_LOG: 10405249-1580@10.225.121.206: 
[core/mem/q_malloc.c:432]: qm_malloc(): qm_malloc(0x7ff37092, 4224)
called from core: core/sip_msg_clone.c: sip_msg_shm_clone(496), module:
core; Free fragment not found!
edge-sip-proxy[6119]: ERROR: ESP_LOG: 10405249-1580@10.225.121.206: 
[core/sip_msg_clone.c:499]: sip_msg_shm_clone(): could not allocate shared
memory from shm pool
edge-sip-proxy[6119]: ERROR: ESP_LOG: 10405249-1580@10.225.121.206: tm
[t_lookup.c:1293]: new_t(): out of mem:
edge-sip-proxy[6119]: ERROR: ESP_LOG: 10405249-1580@10.225.121.206: tm
[t_lookup.c:1439]: t_newtran(): new_t failed
edge-sip-proxy[6119]: ERROR: ESP_LOG: 10405249-1580@10.225.121.206: sl
[sl_funcs.c:392]: sl_reply_error(): stateless error reply used: I'm
terribly sorry, server error occurred (1/SL)


The output of kamctl stats shmem confirms that kamailio is running out of
memory:
{
  "jsonrpc":  "2.0",
  "result": [
"shmem:fragments = 36427",
"shmem:free_size = 14123552",
"shmem:max_used_size = 268435456",
"shmem:real_used_size = 254311904",
"shmem:total_size = 268435456",
"shmem:used_size = 215787904"
  ],
  "id": 10901
}

Then I was check what was the module that were consuming more memory
with kamcmd
mod.stats all shm and the output of this command showed me that Core module
was consuming most of shm memory, as you can see bellow is the output of
this command shows that Core - build_req_buf_from_sip_req is consuming most
of shm.

Module: core
{
sip_msg_shm_clone(496): 4872856
create_avp(175): 24768
msg_lump_cloner(986): 154376
xavp_new_value(106): 780896
build_req_buf_from_sip_req(2187): 183984624
counters_prefork_init(211): 36864
cfg_clone_str(130): 96
cfg_shmize(217): 848
main_loop(1303): 8
init_pt(106): 8
init_pt(105): 8
init_pt(104): 5256
register_timer(995): 232
cfg_register_ctx(47): 64
init_tcp(5021): 8192
init_tcp(5015): 32768
init_tcp(5007): 8
init_tcp(5000): 8
init_tcp(4993): 8
init_tcp(4987): 8
init_tcp(4975): 8
init_avps(90): 8
init_avps(89): 8
init_dst_blacklist(438): 16384
init_dst_blacklist(430): 8
timer_alloc(498): 96
init_dns_cache(361): 8
init_dns_cache(352): 16384
init_dns_cache(344): 16
init_dns_cache(336): 8
init_timer(267): 8
init_timer(266): 16384
init_timer(265): 8
init_timer(264): 8
init_timer(253): 8
init_timer(221): 8
init_timer(210): 278544
init_timer(209): 8
init_timer(197): 8
cfg_child_cb_new(829): 64
sr_cfg_init(361): 8
sr_cfg_init(354): 8
sr_cfg_init(347): 8
sr_cfg_init(335): 8
sr_cfg_init(323): 8
qm_shm_lock_init(1202): 8
Total: 190229920
}

Then I stopped the sipp that was running against kamailio in order to see
if the memory consumed by *build_req_buf_from_sip_req* decreased but it
didn't, so, it seems that there is a memleak in this version.

If the information that I'm sending in this email is not enough to identify
the root cause of this, please let me know if there is anything else that I
can do here to help identify better what is the main reason.
Than you

Best Regards
-- 
Cumprimentos
José Seabra
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Kamailio-5.3.3. NAT and RTP not working

2020-06-25 Thread Pavithra Mohanraja 
Hi,

Now i am trying with kamailio-5.3.4 version as a docker containers. There I
am not using ipsec, pcrf related configurations .
There registration and call establishment is happening. but during hangup ,
BYE packet is sent from alice to bob.
and scscf returns *403* *Domain not served (destination not found error) . *

The same way happens from bob to alice also . couldnt able to find the root
cause of the issue .

Thats why i thought of deploying the ims which you have written with VolTE
setup. there i face different kind of issue.

Kindly help me in the first case . If you need any clarifications on
this please let me know. I can give since i am completely blocked with this.


Thanks,
Pavithra

On Thu, Jun 25, 2020 at 12:29 PM supreeth herle 
wrote:

> can you please paste here your DNS zone file and pcscf configuration
> files? It looks like DNS is not setup properly as sip:example.com is not
> being resolved to point to ICSCF.
>
> Best Regards,
> Supreeth
>
> On Thu, 25 Jun 2020 at 07:20, Pavithra Mohanraja 
> wrote:
>
>> Hi Supreeth,
>>
>> I have followed your guide to build kamailio IMS
>>
>> https://open5gs.org/open5gs/docs/tutorial/02-VoLTE-setup/
>>
>> services are running fine .
>> when i try to make a call . registration fails with 478 unresolvable
>> destination
>>
>> 93(25632) INFO: rr [rr_mod.c:515]: pv_get_route_uri_f(): No route header
>> present.
>> 93(25632) NOTICE:

Re: [SR-Users] Kamailio-5.3.3. NAT and RTP not working

2020-06-25 Thread Pavithra Mohanraja 
Hi Supreeth,

This is my DNS file

$ORIGIN sip.example.com.
$TTL 1W
@   1D IN SOA   localhost. root.localhost. (
1   ; serial
3H  ; refresh
15M ; retry
1W  ; expiry
1D ); minimum

1D IN NSns
ns  1D IN A 10.45.5.95

pcscf   1D IN A 10.45.5.95
_sip._udp.pcscf 1D SRV 0 0 5070 pcscf
_sip._tcp.pcscf 1D SRV 0 0 5070 pcscf

icscf   1D IN A 10.45.5.95
_sip._udp   1D SRV 0 0 4060 icscf
_sip._tcp   1D SRV 0 0 4060 icscf

scscf   1D IN A 10.45.5.95
_sip._udp.scscf 1D SRV 0 0 6060 scscf
_sip._tcp.scscf 1D SRV 0 0 6060 scscf

hss 1D IN A 10.45.5.95



And pcscf config file is taken from ur git source

https://github.com/herlesupreeth/Kamailio_IMS_Config
changed only IP and domain name

# IP-Adress for incoming SIP-Traffic, in the following format:

# SIP / UDP
listen=udp:10.45.5.95:5070
# Uncomment the below line only when UE is behind double NAT (e.g. VoIP
calling over WiFi/ CN behind a NAT)
#listen=udp:10.4.128.21:5060 advertise 172.24.15.30:5060
# SIP / TCP
listen=tcp:10.45.5.95:5070
# Uncomment the below line only when UE is behind double NAT (e.g. VoIP
calling over WiFi/ CN behind a NAT)
#listen=tcp:10.4.128.21:5060 advertise 172.24.15.30:5060
# SIP / TCP/TLS
#listen=tls:11.22.33.44:5061

# IPSEC / UDP
#!define IPSEC_LISTEN_ADDR "10.45.5.95"
#!define IPSEC_CLIENT_PORT 5100
#!define IPSEC_SERVER_PORT 6100

# IP used in Rx_AAR_Register - IP of this P-CSCF, to be used in the flow
for the AF-signaling
#!define RX_AF_SIGNALING_IP "10.4.128.21"
# Uncomment the below line only when UE is behind double NAT (e.g. VoIP
calling over WiFi/ CN behind a NAT)
##!define RX_AF_SIGNALING_IP "172.24.15.30"

alias=pcscf.sip.example.com

#!define MY_WS_PORT 80
#!define MY_WSS_PORT 443

#!define PCSCF_URL "sip:pcscf.sip.example.com:5070"

#!define TCP_PROCESSES 8



I am not using pcrf .. rest of the things are same.
OPTIONS request are looping and sometimes registration is getting stopped
with 504 server timeout ..
Unable to find the root-cause.

Kindly do the needful.



On Thu, Jun 25, 2020 at 12:29 PM supreeth herle 
wrote:

> can you please paste here your DNS zone file and pcscf configuration
> files? It looks like DNS is not setup properly as sip:example.com is not
> being resolved to point to ICSCF.
>
> Best Regards,
> Supreeth
>
> On Thu, 25 Jun 2020 at 07:20, Pavithra Mohanraja 
> wrote:
>
>> Hi Supreeth,
>>
>> I have followed your guide to build kamailio IMS
>>
>> https://open5gs.org/open5gs/docs/tutorial/02-VoLTE-setup/
>>
>> services are running fine .
>> when i try to make a call . registration fails with 478 unresolvable
>> destination
>>
>> 93(25632) INFO: rr [rr_mod.c:515]: pv_get_route_uri_f(): No route header
>> present.
>> 93(25632) NOTICE:

[SR-Users] Question about textops

2020-06-25 Thread Mojtaba 
Hello,
Some confusing things while developing in Kamailio:
In is_method_f function in textops module, the code checks the HDR_CSEQ_F
in msg also, and if the method name appears in CSEQ_F, The result is
returned TRUE.
These question will  arise why in this function, the CSEQ field in message
will check?
if(parse_headers(msg, HDR_CSEQ_F, 0)!=0 || msg->cseq==NULL)
{
LM_ERR("cannot parse cseq header\n");
return -1; /* should it be 0 ?!?! */
}
if(m->s==0)
return (get_cseq(msg)->method_id&m->len)?1:-1;
else
return (get_cseq(msg)->method_id==METHOD_OTHER
&& get_cseq(msg)->method.len==m->len
&& (strncasecmp(get_cseq(msg)->method.s, m->s,
m->len)==0))?1:-1;

I think it would be nice to add new function like: is_cseq_method_f in
module to avoid some problem understanding.

-- 
--Mojtaba Esfandiari.S
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Kamailio-5.3.3. NAT and RTP not working

2020-06-25 Thread supreeth herle 
can you please paste here your DNS zone file and pcscf configuration files?
It looks like DNS is not setup properly as sip:example.com is not being
resolved to point to ICSCF.

Best Regards,
Supreeth

On Thu, 25 Jun 2020 at 07:20, Pavithra Mohanraja 
wrote:

> Hi Supreeth,
>
> I have followed your guide to build kamailio IMS
>
> https://open5gs.org/open5gs/docs/tutorial/02-VoLTE-setup/
>
> services are running fine .
> when i try to make a call . registration fails with 478 unresolvable
> destination
>
> 93(25632) INFO: rr [rr_mod.c:515]: pv_get_route_uri_f(): No route header
> present.
> 93(25632) NOTICE: