FOSDEM - Real Time Communications devroom CfP
=
NOTE: we have extended the deadline but we will give preference
to people who submitted earlier when we set the time for each
talk. Please submit your proposal ASAP so that you can get
your preferred time
Hi Juan Carlos - I feel your pain!
I've finished for the year so I don't have access to the code at the
moment. I'll have a look at this in the new year to see if I can post
something sensible! :-)
Short version is that it turned out to be a horrible challenge to get it
working as desired. My mem
then you are fine :-)
On 4/12/2020 09:26, Mark Allen wrote:
> Interestingly - TIMER already seems to use some form of dummy message
> to avoid problems. If I add the line...
>
> timer_route[checkNodeCache, 5] {
> xlog("TIMER_ROUTE");
> xlog("Message info: $fU, $tU, $td, $rm");
Hi, iam having the same situation, can you copy the opensips.cfg as
reference, iam having issue with incoming calls to webrtc extensions, my
opensips version is 3.1 and is working with mid_registar, i can do calls to
SIP extensions, SIP Trunk, but not working when incoming calls to extension
Webrtc
Best Regards
Saurabh Chopra
+918861979979
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Hi Donat/Opensips Team,
We have tested with "working_mode_preset" as *sql only* because db_mode is
deprecated. And as far as opensips logs is concerned , I am attaching
opensips logs as a text file with *log_level=4, *please check if you could
find anything unusual.
Will wait for your feedback.
Hi Mark, can you share the configuration? i need to do something similar but
without success, thank you.
Using your example:
REGISTER: SIP softphone (LinPhone) -> OpenSIPS Mid-registrar -> Asterisk
= success
REGISTER: WebRTC webphone (Mizutech) -> OpenSIPS Mid-registrar -> Asterisk
Well, let's spin the wheel again for a new cycle – one more year, one
more evolution cycle, one more OpenSIPS major release. Even more, a new
topic is to be addressed. So let me introduce you to the upcoming
OpenSIPS 3.2 .
For the upcoming OpenSIPS 3.2 release the main focus is on the
*/in-
