Re: [SR-Users] The problem of get_aor_hash function

19, st_ino = 72092, st_nlink = 2, st_mode = 16832, st_uid = 0, st_gid = 0, __pad0 = 0, st_rdev = 0, st_size = 40, st_blksize = 4096, st_blocks = 0, st_atim = {tv_sec = 1532054497, tv_nsec = 553300960}, st_mtim = {tv_sec = 1532054692, tv_nsec = 531753344}, st_ctim = {

[SR-Users] The problem of get_aor_hash function

Dear all, I'm trying Kamailio 5.1.4 and IMS module. When registering to Kamailio IMS using the same ip and port for 30 users (different contact user part), the P-CSCF get the same hash number and aor value. The function get_aor_hash(_d, &_ci->via_host, _ci->via_port, _ci->via_prot) in

[SR-Users] ims_usrloc_pcscf module hashing_type parameter does not work

Dear sir, I'm working on Kamailio 4.4.0 and 5.1.4. When registering to Kamailio IMS using the same ip and port for 30 user (different contact user part), the pcscf get the same hash number and aor value. The hashing_type = 0 seems not to be work. Can anyone help me?

[SR-Users] Kamailio IMS PCSCF database problem

Dear sir, I'm using Kamailio 4.4.0 and 5.1.4 IMS module. During using SIPp 3000 subscriber register testing, after enabling PCSCF DB URL function, the contents of 3000 subscribers on PCSCF location table are the same. Using the same IP address and UDP port of 3000 SIPp REGISTER message seems to

Re: [SR-Users] ims_dialog default_timeout parameter

Any suggestions? Thanks. > On 10.04.18 10:43, tyd wrote: > > > > Hello, >> >> do you get also dialog statistics? tm stats are not relevant in this >> context. >> >> Cheers, >> Daniel >> > Hi, > > I'm re-running SIPp. > The share memory is dec

Re: [SR-Users] ims_dialog default_timeout parameter

pened_connections = 0 tcp:current_write_queue_size = 0 tcp:established = 0 tcp:local_reject = 0 tcp:passive_open = 0 tcp:send_timeout = 0 tcp:sendq_full = 0 # > > On 10.04.18 09:19, tyd wrote: > > Hello, >> >> On 10.04.18 07:25, tyd wrote: >> >> Hi, Daniel >> >> N

Re: [SR-Users] ims_dialog default_timeout parameter

> > Hello, > > On 10.04.18 07:25, tyd wrote: > > Hi, Daniel > > No, the dialogs were not terminated after 10 minutes if no BYE message was > sent. > > > Not using ims_dialog, but it may be that it doesn't send bye when the > dialog lifetime elapses, just de

Re: [SR-Users] ims_dialog default_timeout parameter

at production environment ? Thanks. 2018-04-10 0:27 GMT+08:00 Daniel-Constantin Mierla <mico...@gmail.com>: > Hello, > > that should be the call lifetime. Are the dialogs terminated after 10 > minutes? > > Cheers, > Daniel > > On 09.04.18 16:58, tyd wrote: > > Dear al

[SR-Users] ims_dialog default_timeout parameter

Dear all, What's the meaning of ims_dialog default_timeout parameter ? *Default value is 「43200 (12 hours)」* When modparam("ims_dialog", "default_timeout", 600) was set, the situation of Kamailio S-CSCF out of memory was solved and is running smoothly. Debian 8 with Kamailio 4.4.7

[SR-Users] S-CSCF can not allocate memory

Hello, I haved install debian 8 and kamailio 4.4.7 for IMS testing. After registering 1 users, SIPp generates CPS 25 SIP INVITE message and BYE message after 100 seconds. After about 24 calls, there are "cannot allocate memory" messgae on S-CSCF. The command of S-CSCF is "kamailio -m 512