Re: [OpenSIPS-Users] Media Issue once the UA - connected

Hi Sanjeev, Well, things are getting a bit more complex here as you run OpenSIPS behind a NAT (in a private network) - this means that opensips will be 'visible' with different IPs by the parties in the same private network and by the parties in the public network. In the same time you need

Re: [OpenSIPS-Users] Help with my OpenSips architecture

Hi Dominic, I have a similar setup in a test rig. For comparison, here is the output I get for the same fifo commands: opensipsctl fifo clusterer_list Cluster:: 1 Node:: 1 DB_ID=1 URL=bin:192.168.0.118:5678 Enabled=1 Link_state=Up Next_hop=1 Description=vSvr2 opensipsctl fifo

Re: [OpenSIPS-Users] soket error

Hi Volga, When doing dialog replication, you need to be sure that the two OpenSIPS instances do have the same listener - this is needed as the dialogs are "anchored" to the IP address used as listener. In your case, the server receiving the replicated traffic does not have as listener the

Re: [OpenSIPS-Users] cluster presence

Hi Volga, The logs report a serious heavy execution of certain timer routines in OpenSIPS, like the presence cleanup takes more than 191 secsmost probably due long lasting DB queries ??? or because of heavy load in OpenSIPS that leads to starvation in handling the timer jobs - what is

Re: [OpenSIPS-Users] Help with my OpenSips architecture

Hi Dominic, The state listed by 'clusterer_list_cap' refers to the startup synchronization mechanism. When you register a sip device on an instance, that event is replicated on the spot to the other instances in the cluster, but older registrations are only pulled from other nodes at

Re: [OpenSIPS-Users] Help with my OpenSips architecture

Thanks a lot once again, that was the issue (flags=seed), here is the output of the command now: # opensipsctl fifo clusterer_list_cap Cluster:: 1 Capability:: usrloc-contact-repl State=Ok Dominic On Thu, Aug 9, 2018 at 5:13 AM, John Quick wrote: > Hi Dominic, > > I have a similar setup

[OpenSIPS-Users] OpenSIPS Unable to parse msg received from

Hi Team, I am using opensips as hep proxy to distribute traffic to multiple homer noes for trace capturing. # opensips -V version: opensips 2.3.2 (x86_64/linux) flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT ADAPTIVE_WAIT_LOOPS=1024,

Re: [OpenSIPS-Users] OpenSIPS Unable to parse msg received from

Hi Abdul, try to add this part of code at the begining of your routing code to add more logs : if(!sipmsg_validate(""))     {     xlog("L_WARN", "Dropping mal formed Messages Retcode : $retcode ");     xlog("L_WARN","--- error from [$si:$sp]\n+\n$mb\n\n");    

Re: [OpenSIPS-Users] OpenSIPS Unable to parse msg received from

Hi Alain, Thank you for your suggestion. I will update cfg and get back with results. Do i need to upgrade opensips to 2.4 as well? -- regards, abdul basit | p: +92 32 1416 4196 | o: +92 30 0841 1445 On Thu, 9 Aug 2018 at 17:35, Alain Bieuzent wrote: > Hi Abdul, > > > > try to add this

Re: [OpenSIPS-Users] OpenSIPS Unable to parse msg received from

Hi Abdul, have you checked the tutorial on HEP switching ? https://blog.opensips.org/2017/10/12/opensips-as-hep-proxyswitch/ Maybe you are using the wrong routes in the script. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com OpenSIPS Bootcamp

[OpenSIPS-Users] Multiple IPs

Hi All. Currently, I am using OpenSIPs on AWS without issues (NAT environment). I have it configured as follows (I have removed the real IP and replaced it with 1.2.3.4): listen=udp:eth0:5060 advertised_address="1.2.3.4" alias="1.2.3.4" advertised_port=5060 What I would like to do is add