Re: [SR-Users] question about kamailio handling of forwarded invite

#x27; due to a failure to pass ACL '(BASELINE)' > [Jan 21 23:13:20] NOTICE[20785][C-0001] chan_sip.c: Failed to > authenticate device <mailto:sip%3A95678@10.0.1.35>>;tag=as4028dabf > > Is the 10.0.1.30 in the IP ACL white list for Asterisk? > > Cheers,

[SR-Users] question about kamailio handling of forwarded invite

ot; in the Via header while the first one has "i=1". Not sure what the "i=1" is for. Would appreciate some insights on how kamailio is adding/handling the "i=#" in Via header. Thanks. Ding Ma SPG, Motorola Solutions ___ SIP

Re: [SR-Users] problem with dispatcher load balancing

, to know if > there is anything to fix there. > > Cheers, > Daniel > > > On 14/09/15 21:52, Ding Ma wrote: > > Hi, > > Figured this out. Seems I had made a mistake in the names of AVPs. Changed > the AVP names as the exact names used in the example contained in >

Re: [SR-Users] problem with dispatcher load balancing

, not really an issue even if it is not enforced. Thanks, On Thu, Aug 27, 2015 at 9:07 AM, Ding Ma wrote: > Hi, Daniel > > I just tested the dispatcher in 4.3.1. It showed the same behavior as > 4.2.3. All the calls are sent to one Asterisk (the last one in the > dispatcher lis

Re: [SR-Users] Kamailio TLS configuration

When your server contacts the public server, your server acts as a tls client. So you may need to copy the server section settings (at least the calist) into the client section of tls.cfg. Sent from my iPhone > On Aug 28, 2015, at 12:01 PM, Alexandru Covalschi <568...@gmail.com> wrote: > > Hel

Re: [SR-Users] problem with dispatcher load balancing

> > > On 12/06/15 06:06, Ding Ma wrote: > > OK, we’ll try to update and report back. Wonder if the latest 4.3 has all > the fixes went into the latest 4.2.x. We already have plan to upgrade to > 4.3. > Thanks. > > On Jun 10, 2015, at 10:01 AM, Daniel-Constantin Mierla &g

[SR-Users] Question about how location server_id is supposed to be used.

Looking for some doc that describes how the new columns in 4.3.x location table is supposed to be used. Can find some email discussions about this, but seems no formal doc exists. Would appreciate if someone can provide an explanation. Thanks ___ SIP Exp

Re: [SR-Users] problem with dispatcher load balancing

d I will look at > it with the first chance. > > Cheers, > Daniel > > On 10/06/15 16:50, Ding Ma wrote: >> We're running kamailio 4.2.3. Are there any changes to dispatcher in 4.2.x? >> Thanks, >> >> # kamailio -V >> version: kamailio 4.

Re: [SR-Users] problem with dispatcher load balancing

io_rt, select. id: 5596bd compiled on 09:32:37 May 6 2015 with gcc 4.4.7 On Wed, Jun 10, 2015 at 7:01 AM, Daniel-Constantin Mierla wrote: > Hello, > > what version of kamailio are you using? > > Cheers, > Daniel > > > On 09/06/15 20:51, Ding Ma wrote: > > I

[SR-Users] problem with dispatcher load balancing

I'm trying to set up kamailio dispatcher to distribute calls to 2 asterisk servers. So far, the failover case seems ok, but I cannot get the dispatcher to distribute load. All calls are going to the last destination entry in the dispatcher table even if I have set the maxload attributes. I'm using

Re: [SR-Users] missing BYE when 2 redundant kamailio servers share the same database

h 2 kamailio instances. We > want to make sure each phone only sends requests through its registrar. > > I have included pjsua logs in subsequent emails in this thread. Those > logs have SIP messages, but only provide client perspective. > > Thanks for the help, > > Ding &

Re: [SR-Users] missing BYE when 2 redundant kamailio servers share the same database

. I have included pjsua logs in subsequent emails in this thread. Those logs have SIP messages, but only provide client perspective. Thanks for the help, Ding > On Mar 20, 2015, at 3:00 AM, Daniel-Constantin Mierla > wrote: > > Hello, > > On 19/03/15 02

[SR-Users] missing BYE when 2 redundant kamailio servers share the same database

Hi, all I'm trying to set up 2 kamailio servers for active-active redundancy. The two kamailio severs share the the same database with db_mode=3, and no registration replication. Use pjsua2 as SIP client for testing. The test setup is as follows: kamailio server 1(k1): 10.0.1.30:5061 kamaili

[SR-Users] missing BYE when 2 redundant kamailio servers share the same database

This is the SIP log when using location routing for BYE from peer server. pjsua2_good.log 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-

[SR-Users] missing BYE when 2 redundant kamailio servers share the same database

This is the SIP log with the 500 error for BYE. pjsua2_missingbye.log 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-Users] missing BYE when 2 redundant kamailio servers share the same database

Hi, all I'm trying to set up 2 kamailio servers for active-active redundancy. The two kamailio severs share the the same database with db_mode=3, and no registration replication. Use pjsua2 as SIP client for testing. The test setup is as follows: kamailio server 1(k1): 10.0.1.30:5061

[SR-Users] How the README file in each module's directory is generated?

Is there a doc tool? Or just use an editor? Thanks ___ 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] FS#380 - fixes for memory leak in TLS module

Daniel, Klaus, Sorry to reply late to your comments, was busy doing some other things until now. Just provided some comments in https://sip-router.org/tracker/index.php?do=details&task_id=380 Please take a look and let me know if you agree with my assessment. Thanks, Ding ___

Re: [SR-Users] kamailio tls.reload core dump

Yes, give me a couple of days to get a clean patch based on 4.0.4. The original patch was done on 4.0.3. Thanks, On 11/15/2013 3:59 AM, Klaus Darilion wrote: Hi Ding Ma! It would be great if you can provide the patch at the tracker. https://sip-router.org/tracker/ regards Klaus On

Re: [SR-Users] tls.so: mod_register failed on fedora 18 x86_64

Hi, all We have applied the openssl 1.0.1e patch described in the email chain between Roberto Fichera and Daniel-Constantin Mierla back in August. But Kamailio 4.0.4 still fails to start up and the log shows memory allocation problem. By the way, we're running kamailio on RHEL 6.5. Wonder if we ha

Re: [SR-Users] kamailio tls.reload core dump

's the process to submit changes for review? Thanks, Ding On 10/24/2013 03:18 AM, Klaus Darilion wrote: You should build Kamailio without optimizations. "out>" does not bring much information. regards Klaus On 23.10.2013 21:48, Ding Ma wrote: Hi, all This is related to

[SR-Users] kamailio tls.reload core dump

Hi, all This is related to the previous tls.reload not safe email chain. Now we have a detailed gdb output that shows the stack trace of the core dump. Please take a look. This looks like a bug. Please let me know if you have any insights on how to fix this. Thanks, Ding #0 0x7f0a6126a2b2 in

Re: [SR-Users] why kamcmd tls.reload is not safe

in_loop () No symbol table info available. #17 0x0046a912 in main () No symbol table info available. On 10/21/2013 10:30 PM, Olle E. Johansson wrote: 22 okt 2013 kl. 05:20 skrev Ding Ma : Klaus, With the information you provided, I did find the emails initiated by Jan Janak on this top

Re: [SR-Users] why kamcmd tls.reload is not safe

ling lists (ser, openser). IIRC the feature and the detailed discussion way by Jan Janak. Maybe this helps you to refine your Google search. regards Klaus On 19.10.2013 21:33, Ding Ma wrote: In the current Kamailio TLS module document, there is a statement about tls.reload being unsafe. But the o

[SR-Users] why kamcmd tls.reload is not safe

In the current Kamailio TLS module document, there is a statement about tls.reload being unsafe. But the only way to periodically update CRL without restarting Kamailio is to use tls.reload. In our test with tls.reload for CRL, it seems Kamailio would crash after about 100 times of tls.reload i