[OpenSIPS-Devel] Can't get 2.3 running with voiptests properly

Bogdan-Andrei Iancu bogdan at opensips.org
Thu Jul 27 13:04:47 EDT 2017


What's the call flow ? I suppose the INVITE gets relayed out, but is 
there any reply coming back from the B side ?

Bogdan-Andrei Iancu
   OpenSIPS Founder and Developer
   http://www.opensips-solutions.com

OpenSIPS Bootcamp 2017, Houston, US
   http://opensips.org/training/OpenSIPS_Bootcamp_2017.html

On 07/27/2017 08:02 PM, Maxim Sobolev wrote:
> Thanks, I'll try that. However it's not really "stuck-stuck", see my 
> e-mail, it does re-transmissions and eventually "unstucks" itself.
>
> On Thu, Jul 27, 2017 at 9:53 AM, Bogdan-Andrei Iancu 
> <bogdan at opensips.org <mailto:bogdan at opensips.org>> wrote:
>
>     Hi Maxim,
>
>     When you see it stuck, run "opensipsctl trap" to get a dump with
>     the backtraces from all processes .....and you can see what that
>     they are doing...
>
>     Regards,
>
>     Bogdan-Andrei Iancu
>        OpenSIPS Founder and Developer
>        http://www.opensips-solutions.com <http://www.opensips-solutions.com>
>
>     OpenSIPS Bootcamp 2017, Houston, US
>        http://opensips.org/training/OpenSIPS_Bootcamp_2017.html
>     <http://opensips.org/training/OpenSIPS_Bootcamp_2017.html>
>
>     On 07/27/2017 07:46 PM, Maxim Sobolev wrote:
>>     Hi folks, we are getting some unexpected trouble with getting 2.3
>>     to run properly with voiptests. The issue is that after brief
>>     time after starting up the proxy stops accepting any new
>>     requests/replies. As far as I can tell no error output is
>>     produced and the opensips eventually exits normally. I've added
>>     some debug output into the routing script to log replies, but I
>>     don't see anything logged after 100 Trying.
>>
>>     Full log can be found here, it also dumps effective config.
>>
>>     https://travis-ci.org/sippy/voiptests/jobs/257935671
>>     <https://travis-ci.org/sippy/voiptests/jobs/257935671>
>>
>>     The only thing I can think of being unusual in our setup is that
>>     we are running in "foreground" mode, so that we can wait(1) on
>>     the pid and retrieve status code when it finishes.
>>
>>     Any ideas are greatly appreciated. We can also add more debug if
>>     needed.
>>
>>     Jul 26 23:53:38 [21441] OpenSIPS received a reply 100/INVITE from
>>     0:0:0:0:0:0:0:1
>>
>>     Jul 26 23:53:38 [21441] OpenSIPS received a reply 100/INVITE from
>>     0:0:0:0:0:0:0:1
>>
>>     Jul 26 23:53:38 [21441] OpenSIPS received a reply 100/INVITE from
>>     0:0:0:0:0:0:0:1
>>
>>     Jul 26 23:53:38 [21441] OpenSIPS received a reply 100/INVITE from
>>     0:0:0:0:0:0:0:1
>>
>>     Jul 26 23:53:38 [21441] OpenSIPS received a reply 100/INVITE from
>>     0:0:0:0:0:0:0:1
>>
>>     Jul 26 23:53:38 [21440] OpenSIPS received a reply 100/INVITE from
>>     127.0.0.1
>>
>>     Jul 26 23:53:38 [21440] OpenSIPS received a reply 100/INVITE from
>>     127.0.0.1
>>
>>     Jul 26 23:53:38 [21440] OpenSIPS received a reply 100/INVITE from
>>     127.0.0.1
>>
>>     Jul 26 23:53:38 [21441] OpenSIPS received a reply 100/INVITE from
>>     0:0:0:0:0:0:0:1
>>
>>     Jul 26 23:53:38 [21440] OpenSIPS received a reply 100/INVITE from
>>     127.0.0.1
>>
>>     Jul 26 23:53:38 [21441] OpenSIPS received a reply 100/INVITE from
>>     0:0:0:0:0:0:0:1
>>
>>     Jul 26 23:53:38 [21440] OpenSIPS received a reply 100/INVITE from
>>     127.0.0.1
>>
>>     Jul 26 23:53:38 [21440] OpenSIPS received a reply 100/INVITE from
>>     127.0.0.1
>>
>>     Jul 26 23:53:38 [21440] OpenSIPS received a reply 100/INVITE from
>>     127.0.0.1
>>
>>     Jul 26 23:53:38 [21441] OpenSIPS received a reply 100/INVITE from
>>     0:0:0:0:0:0:0:1
>>
>>     Jul 26 23:53:38 [21441] OpenSIPS received a reply 100/INVITE from
>>     0:0:0:0:0:0:0:1
>>
>>     Jul 26 23:53:38 [21441] OpenSIPS received a reply 100/INVITE from
>>     0:0:0:0:0:0:0:1
>>
>>     Jul 26 23:53:38 [21441] OpenSIPS received a reply 100/INVITE from
>>     0:0:0:0:0:0:0:1
>>
>>     Jul 26 23:53:38 [21441] OpenSIPS received a reply 100/INVITE from
>>     0:0:0:0:0:0:0:1
>>
>>     Jul 26 23:53:38 [21441] OpenSIPS received a reply 100/INVITE from
>>     0:0:0:0:0:0:0:1
>>
>>     Jul 26 23:53:38 [21440] OpenSIPS received a reply 100/INVITE from
>>     127.0.0.1
>>
>>     Jul 26 23:53:38 [21440] OpenSIPS received a reply 100/INVITE from
>>     127.0.0.1
>>
>>
>>
>>     +kill -TERM 21436
>>
>>     +echo MM_PID: 21436
>>
>>     MM_PID: 21436
>>
>>     +wait 21436
>>
>>     Thank you for flying opensips
>>
>>     +MM_RC=0
>>
>
>
>
>
> -- 
> Maksym Sobolyev
> Sippy Software, Inc.
> Internet Telephony (VoIP) Experts
> Tel (Canada): +1-778-783-0474
> Tel (Toll-Free): +1-855-747-7779
> Fax: +1-866-857-6942
> Web: http://www.sippysoft.com
> MSN: sales at sippysoft.com <mailto:sales at sippysoft.com>
> Skype: SippySoft

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/devel/attachments/20170727/9e60eacf/attachment.html>


More information about the Devel mailing list