Hi Kirill,
Indeed, the explanations are not 100% clear - if the dialog replication
is enabled, the profile info (profiles used by dialogs) is also
replicated and seen as part of the local profiles, not shared profile.
So you can use the profiles without the /b or /s
Best regards,
Bogdan-And
Hi Konrad,
For sure there was something wrong - could you give it a another try
with latest 3.0 beta ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
OpenSIPS Summit 2019
https://www.opensips.org/events/Summit-2019Amsterdam/
On 04/08/2019
Hi,
I'm getting a problem connecting to one of my uplink peers, every time I
can see this error:
Apr 23 19:01:04 INFO:core:probe_max_sock_buff: using snd buffer of 416 kb
Apr 23 19:01:04 INFO:core:init_sock_keepalive: TCP keepalive enabled on
socket 6
Apr 23 19:01:04 ERROR:core:tcp_connect_blockin
I checked just now.
It sufficient to comment out UDP listening port and leave just TCP
///
#listen=udp:172.17.0.2:5060 # CUSTOMIZE ME
listen=tcp:172.17.0.2:5060 # CUSTOMIZE ME
///
ERROR:core:fm_malloc: not enough free shm memory (63093216 bytes left, need
8843713106240), pleas
Is there any following error / warning log ? Or you get only that single
err line ??
And you get that error by using TCP without UDP ? using TCP + UDP is fine ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
OpenSIPS Summit 2019
https://www.
Hello,
I switched to opensips3 and b2b internal scenario stopped working:
Apr 23 10:33:29 [55] ERROR:b2b_logic:fixup_b2b_logic: Wrong Scenary ID. No
scenario with this ID [�Ͷ�s]
Apr 23 10:33:29 [55] ERROR:core:fix_cmd: Fixup failed for param [1]
Apr 23 10:33:29 [55] ERROR:core:fix_actions: Failed
Hi everyone,
I'm seeing some odd behaviour in tha initial requests are allowed but
RE-INVITES are resulting in 403. From my logging I can see the INVITE
coming in so I think it must be matching. Why would it not obey and route
the request?
This is the bit of my request route that identifies the s
Should've added I'm running OpenSIPS 2.4.4
Mark.
On Tue, 23 Apr 2019 at 12:10, Mark Farmer wrote:
> Hi everyone,
>
> I'm seeing some odd behaviour in tha initial requests are allowed but
> RE-INVITES are resulting in 403. From my logging I can see the INVITE
> coming in so I think it must be m
Hi, Mark!
The best way to proceed is to add an xlog("checking $si:$sp\n") before
check_source_address(), then some useful xlog() messages on each if
branch, so we can confirm the theory that this is an OpenSIPS issue, and
not a problem specific to your setup.
Liviu Chircu
OpenSIPS Developer
fm_malloc is first error:
Apr 23 12:11:27 [50] INFO:core:mod_init: initializing UDP-plain protocol
Apr 23 12:11:27 [50] INFO:dialog:mod_init: Dialog module - initializing
Apr 23 12:11:27 [50] INFO:core:evi_publish_event: Registered event
Apr 23 12:11:27 [50] INFO:topology_hiding:mod_init: initiali
Hi,
Thanks for the report, this was a bug and I've pushed the fix for it, it
should be fine now.
Regards,
Vlad Patrascu
OpenSIPS Developer
http://www.opensips-solutions.com
On 04/23/2019 01:54 PM, Konrad Malewski wrote:
Hello,
I switched to opensips3 and b2b internal scenario stopped worki
Hi to all
I can sat is great developer open sips
i like to get is any book i can buy about clustering and federations
Thank you
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Hello,
I am testing Opensips3 (last commit from github) and I encounter an issue:
dmesg:
[Tue Apr 23 17:03:27 2019] traps: opensips[16387] general protection
ip:7f86ed1a2676 sp:7ffef01c70b8 error:0
below is the log of opensips
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16387]:
CRITICAL:c
Hi Abdoul,
Unfortunately without the corefile, it is almost impossible to
troubleshoot this.
For the future, see
https://opensips.org/Documentation/TroubleShooting-Crash to understand
how to properly get the core files.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https:
14 matches
Mail list logo