[OpenSIPS-Users] establish a SIP trunk connection between two distinct VoIP systems

[Nilesh Apte]

Hello OpenSIPS community,

I'm currently working on a project and would greatly appreciate some
assistance from anyone who might have experience in this area. My objective
is to establish a SIP trunk connection between two distinct VoIP systems,
with an OpenSIPS server acting as the intermediary.

If anyone has insights, guides, or examples on how to configure OpenSIPS
for this specific scenario, your help would be invaluable. I'm looking for
guidance on the necessary configuration steps and best practices to ensure
a stable and reliable connection.

Thank you in advance for your time and expertise.

Best regards,
Nilesh


On Tue, Jun 24, 2025 at 9:31 PM Nilesh Apte <nilesh.apte at jampot.in> wrote:

> Hello Opensips community,
>
> I would like to know if anyone can help me create a SIP trunk between two
> VoIP systems using an OpenSIPS server.
>
> Thank you in advance for your help.
>
> Best,
> Nilesh
>
> *Nilesh APTE*:
>
> Jampot Technologies Pvt Ltd.
>
> Cell:+91-9920104880 |Belgium:+32-474692366
>
> Email: nilesh.apte at jampot.in
> Addr: Office No.807 & 808, Skyline Wealthspace C, near SBI ATM,
> Vidyavihar Scoiety, Vidyavihar, Mumbai, Maharastra, India.
>
> Landline Number +91-22-2511 4500 |Support +91-9595901020 |Sales
> +91-8600801010
>
>
> On Tue, 24 Jun 2025 at 18:55, Richard Revels via Users <
> users at lists.opensips.org> wrote:
>
>> Greetings,
>> I have started having issues with some proxies running opensips 3.2.19
>> and some others running 3.4.12
>> With approximately 230 cps and 7300 dialogs the proxy starts emitting log
>> messages like
>>
>> Jun 24 15:42:18 sip-proxy.local
>> /usr/local/opensips/sbin/opensips[190328]: WARNING:core:utimer_ticker:
>> utimer task <tm-utimer> already scheduled 150 ms ago (now 3671145080 ms),
>> delaying execution
>> Jun 24 15:42:18 sip-proxy.local
>> /usr/local/opensips/sbin/opensips[190328]: WARNING:core:utimer_ticker:
>> utimer task <tm-utimer> already scheduled 200 ms ago (now 3671145130 ms),
>> delaying execution
>> Jun 24 15:42:18 sip-proxy.local
>> /usr/local/opensips/sbin/opensips[190328]: WARNING:core:utimer_ticker:
>> utimer task <tm-utimer> already scheduled 300 ms ago (now 3671145230 ms),
>> delaying execution
>> Jun 24 15:42:18 sip-proxy.local
>> /usr/local/opensips/sbin/opensips[190328]: WARNING:core:utimer_ticker:
>> utimer task <tm-utimer> already scheduled 400 ms ago (now 3671145330 ms),
>> delaying execution
>> Jun 24 15:42:18 sip-proxy.local
>> /usr/local/opensips/sbin/opensips[190328]: WARNING:core:utimer_ticker:
>> utimer task <tm-utimer> already scheduled 500 ms ago (now 3671145430 ms),
>> delaying execution
>> Jun 24 15:42:19 sip-proxy.local
>> /usr/local/opensips/sbin/opensips[190328]: WARNING:core:utimer_ticker:
>> utimer task <tm-utimer> already scheduled 600 ms ago (now 3671145530 ms),
>> delaying execution
>> Jun 24 15:42:19 sip-proxy.local
>> /usr/local/opensips/sbin/opensips[190328]: WARNING:core:utimer_ticker:
>> utimer task <tm-utimer> already scheduled 700 ms ago (now 3671145630 ms),
>> delaying execution
>> Jun 24 15:42:19 sip-proxy.local
>> /usr/local/opensips/sbin/opensips[190328]: WARNING:core:utimer_ticker:
>> utimer task <tm-utimer> already scheduled 800 ms ago (now 3671145730 ms),
>> delaying execution
>> Jun 24 15:42:19 sip-proxy.local
>> /usr/local/opensips/sbin/opensips[190328]: WARNING:core:utimer_ticker:
>> utimer task <tm-utimer> already scheduled 900 ms ago (now 3671145830 ms),
>> delaying execution
>> Jun 24 15:42:19 sip-proxy.local
>> /usr/local/opensips/sbin/opensips[190328]: WARNING:core:timer_ticker: timer
>> task <tm-timer> already scheduled 1000 ms ago (now 3671145830 ms), delaying
>> execution
>>
>>
>> The cpu usage on the threads goes from 3% - 11% depending on thread to
>> 30% across the board.
>>
>> I have been running these versions of opensips for some time now (months
>> for 3.4 and years for 3.2) and do see occasional latency in db or rest
>> connection responses but only recently have started having this issue.
>>
>> So,
>>
>> How are SIP calls distributed across the processing threads?  I was
>> thinking it would be round robin w/ attention given to busy or not.  but it
>> seems like the lower pid threads do a lot more work on these proxies
>>
>> What are possible causes of the timers having trouble completing tasks?
>> is it cpu use, waiting on some other task to finish, combination or more?
>>
>> Is there tuning that can be done to have more timer handling threads?  i
>> tried this with modparam("tm", "timer_partitions") which seemed to make the
>> problem worse
>>
>> Thank you in advance for any guidance you can give me on troubleshooting
>> this issue.
>> Richard Revels
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>

-- 

*Nilesh APTE*:

Jampot Technologies Pvt Ltd.

Cell:+91-9920104880 |Belgium:+32-474692366

Email: nilesh.apte at jampot.in
Addr: Office No.807 & 808, Skyline Wealthspace C, near SBI ATM, Vidyavihar
Scoiety, Vidyavihar, Mumbai, Maharastra, India.

Landline Number +91-22-2511 4500 |Support +91-9595901020 |Sales
+91-8600801010
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20250630/da5861f8/attachment.html>