Re: [SR-Users] Call is not placing in kamailio

2017-07-12 Thread Logeshwaran G
@Alex, Any clues ?? On Wed, Jul 12, 2017 at 4:51 PM, Logeshwaran G wrote: > :) PFA > > On Wed, Jul 12, 2017 at 3:55 PM, Alex Balashov > wrote: > >> On Wed, Jul 12, 2017 at 03:48:04PM +0530, Logeshwaran G wrote: >> >> > I am not sure .. Shall

Re: [SR-Users] TR: Failure Mode

2017-07-12 Thread Nicolas Breuer
Hello, Thanks for this feedback. I can for sure remove the sl_send_reply from branch_failure_route and I can trace that, if I remove that And the destination is busy , the kamalio will only send the 408 "time-out" reply. De : Daniel-Constantin Mierla [mailto:mico...@gmail.com] Envoyé :

Re: [SR-Users] RTPProxy - lookup request failed

2017-07-12 Thread Daniel-Constantin Mierla
Good to know about both -T and -W options. In many of my rtpproxy installations I migrated to 2.0, because the default packaged rtpproxy version from distros (mainly stable debian or centos -- which come with some 1.2.1+patches), seems to be a problem with re-INVITEs changing the RTP port.

Re: [SR-Users] RTPProxy - lookup request failed

2017-07-12 Thread Maxim Sobolev
Yes, Daniel is correct you can bump overall timeout with the -T option. There is also another option -W now since 3 years ago (2.0+) to set timeout specifically on early sessions, so that you can have bigger timeout during call setup phase which might be relevant in this case. Hope it helps. -Max

Re: [SR-Users] TR: Failure Mode

2017-07-12 Thread Daniel-Constantin Mierla
Hello, do not send replies in branch failure route. At that phase, the outgoing branches are not yet completed. More important, do not use sl_send_reply() (this sends a stateless reply) after the transaction has been created (which is the case of branch failure route or failure route), use

Re: [SR-Users] Call is not placing in kamailio

2017-07-12 Thread Logeshwaran G
:) PFA On Wed, Jul 12, 2017 at 3:55 PM, Alex Balashov wrote: > On Wed, Jul 12, 2017 at 03:48:04PM +0530, Logeshwaran G wrote: > > > I am not sure .. Shall I send you my Kamailio.cfg file ?? > > Whoa! At least buy me dinner first. > > Kidding — please do. > > -- > Alex

Re: [SR-Users] Call is not placing in kamailio

2017-07-12 Thread Alex Balashov
On Wed, Jul 12, 2017 at 03:48:04PM +0530, Logeshwaran G wrote: > I am not sure .. Shall I send you my Kamailio.cfg file ?? Whoa! At least buy me dinner first. Kidding — please do. -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web:

Re: [SR-Users] Call is not placing in kamailio

2017-07-12 Thread Logeshwaran G
I am not sure .. Shall I send you my Kamailio.cfg file ?? On Wed, Jul 12, 2017 at 3:43 PM, Alex Balashov wrote: > Are you using the stock Kamailio.cfg, out of the box? > > On Wed, Jul 12, 2017 at 03:40:33PM +0530, Logeshwaran G wrote: > > > Please find the

Re: [SR-Users] Call is not placing in kamailio

2017-07-12 Thread Alex Balashov
Are you using the stock Kamailio.cfg, out of the box? On Wed, Jul 12, 2017 at 03:40:33PM +0530, Logeshwaran G wrote: > Please find the attachment. > > On Wed, Jul 12, 2017 at 3:36 PM, Alex Balashov > wrote: > > > On Wed, Jul 12, 2017 at 03:32:12PM +0530, Logeshwaran

Re: [SR-Users] Call is not placing in kamailio

2017-07-12 Thread Logeshwaran G
Please find the attachment. On Wed, Jul 12, 2017 at 3:36 PM, Alex Balashov wrote: > On Wed, Jul 12, 2017 at 03:32:12PM +0530, Logeshwaran G wrote: > > > Its in Trying state. I am not sure any changes need to be done in > > kamailio.cfg?? > > > > Guide me to resolve

Re: [SR-Users] Call is not placing in kamailio

2017-07-12 Thread Alex Balashov
On Wed, Jul 12, 2017 at 03:32:12PM +0530, Logeshwaran G wrote: > Its in Trying state. I am not sure any changes need to be done in > kamailio.cfg?? > > Guide me to resolve the issue. Can you provide a capture please? -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 /

Re: [SR-Users] Call is not placing in kamailio

2017-07-12 Thread Logeshwaran G
Its in Trying state. I am not sure any changes need to be done in kamailio.cfg?? Guide me to resolve the issue. On Wed, Jul 12, 2017 at 3:24 PM, Alex Balashov wrote: > On Wed, Jul 12, 2017 at 02:57:43PM +0530, Logeshwaran G wrote: > > > I have installed Kamailio-5.0,

Re: [SR-Users] What happens to calls when Kamailio restarts?

2017-07-12 Thread Alex Balashov
On Wed, Jul 12, 2017 at 09:05:27AM +, Samuel F. wrote: > Suppose Kamailio crashes (and started again), is restarted or failed > over to a different server (same IP). What then happens with calls? Speaking generically, not a lot. All SIP messages passing through the proxy can be forwarded

Re: [SR-Users] TR: Failure Mode

2017-07-12 Thread Nicolas Breuer
Hello Daniel, The 486 is send by « myself" in the branch failure code. ## 486 busy if (t_check_status("486") && $sht(branch=>$ci) != "" ) { xlog("L_NOTICE", " Error

[SR-Users] What happens to calls when Kamailio restarts?

2017-07-12 Thread Samuel F .
Hi, I have a question regarding calls and Kamailio restarts. Suppose Kamailio crashes (and started again), is restarted or failed over to a different server (same IP). What then happens with calls? Let's suppose the following scenario: - 1000 calls active on the machine - Some are in call

[SR-Users] Call is not placing in kamailio

2017-07-12 Thread Logeshwaran G
Dear Team, I have installed Kamailio-5.0, and i have included subscriber table as well. Two users have successfully registered but cant able to place the call in between the users. Kindly help me for placing the call. Thanks in Advance, Logesh ___

Re: [SR-Users] RTPProxy - lookup request failed

2017-07-12 Thread Daniel-Constantin Mierla
Hello, knowing that rtpproxy v2.0 has -T is very useful. v1.2 is very old, so I think its time to migrate to v2.0. With this occasion I checked rtpengine -- it has a bunch of options related to timeouts, so it's a good alternative to go for it as well. Cheers, Daniel On 12.07.17 09:24, Marian

Re: [SR-Users] RTPProxy - lookup request failed

2017-07-12 Thread Marian Piater
Hi, works fine, after recompile RTPProxy with newer version (2.2.alpha.20160822) and using option -T 150. There was no necessary to modify the source code. /usr/bin/rtpproxy -s udp:127.0.0.1 7722 -u rtpproxy rtpproxy -p /var/run/rtpproxy/rtpproxy.pid -F -l XXX.XXX.XXX.XXX -d DBUG LOG_LOCAL0 -T

Re: [SR-Users] TR: Failure Mode

2017-07-12 Thread Daniel-Constantin Mierla
Hello, your latest sip trace shows that 486 is sent out to caller (the acc record from syslog shows that the transaction was completed with that code as well). An ACK follows, but then I see also 408. Can you check you config and see if there is some other place that can generate the reply, like

Re: [SR-Users] Setup IMS core Network When Network behind nat

2017-07-12 Thread Daniel-Constantin Mierla
ok, good that you found the solution. Cheers, Daniel On 11.07.17 16:37, Mojtaba wrote: > > Hi. > I found where was my problem. I had a misunderestanding. I used public > domaim as outbound proxy and i could register to ims. > > On 11 Jul 2017 15:00, "Mojtaba"

Re: [SR-Users] RTPProxy - lookup request failed

2017-07-12 Thread Daniel-Constantin Mierla
Hello, ok -- it would be good to know if that solved the problem, so others can find the answer in the archive when facing a similar situation. Cheers, Daniel On 11.07.17 15:55, Marian Piater wrote: > > Hello, > > thank you for quick reply, I tried to find some options in the man > pages, but