[OpenSIPS-Users] OpenSIPS reopen TCP connectios and sends INVITE, but not BYE. How to change it?

Hi. After some log debug I have observed the following behavior in the OpenSISP (2.2.1): When OpenSIPS has to send a SIP INVITE to a peer through a TCP connection that was closed before by some way, OpenSIPS open a new one and then sends the SIP message to the peer successfully. However,

Re: [OpenSIPS-Users] How to ensure current IPV6 listening address

I am reluctant to take out a github membership to simply request a feature. Perhaps someone with an existing membership could request the feature. Opensips currently is unable to detect the IPV6 address of an interface when given the interface name in the configuration. This is a request to

Re: [OpenSIPS-Users] How to ensure current IPV6 listening address

Thank you for investigating this. To improve the chance of Opensips getting the current IP address from the FQDN I employed the NetworkManager dispatcher to send an immediate update to the name server. I am sure that one could parse the output of 'ip addr" and somehow update opensips.cfg but

Re: [OpenSIPS-Users] Is it a kind of TCP keep alive produced by OpenSIPS?

Hi Răzvan. Thank you very much. I'm facing a problem here related to TCP connection teared down during dialogs. While a peer is not in dialogs, its TCP connection to OpenSIPS keeps online all the time. However, when such peer enters in a conversation (be part of a dialog), after few minutes

Re: [OpenSIPS-Users] Is it a kind of TCP keep alive produced by OpenSIPS?

Hi, Rodrigo! The logs you are tracing are printed when OpenSIPS receives something from the client, and then immediately responds back. Due to the fact that we don't see any other debug messages, like SIP parsing & stuff, makes me think that it is a CRLF pinging - the client periodically

[OpenSIPS-Users] Dialog replication problems

Hi All, I have a reduntant OpenSIPS 2.2.1 setup with clusterer, binary interface replication and a floating IP. I am encountering a few niuances and am wondering if I am doing something wrong or if there is a bug. 1) Replicated dialog hash id is different on the standby server from the active

[OpenSIPS-Users] Is it a kind of TCP keep alive produced by OpenSIPS?

Dear OpenSIPS users, In the OpenSIPS log I see: Jan 01 19:30:38 colibri-imx6-jfl opensips[3444]: Jan 1 19:30:38 [3451] DBG:core:tcp_read_req: Using the global ( per process ) buff Jan 01 19:30:38 colibri-imx6-jfl opensips[3444]: Jan 1 19:30:38 [3451] DBG:core:tcp_handle_req:

Re: [OpenSIPS-Users] opensips + rtpproxy bridge on loopback interfaces

Hi Razvan, Le 26/10/2016 à 15:35, Răzvan Crainea a écrit : Hi, Cedric! If you double checked the PCAP and you really are missing the flow from RTPProxy to callee, I take your word for it. Pehaps the logging is misleading. Now, if RTPProxy does not send any packet to the callee, this means

Re: [OpenSIPS-Users] opensips + rtpproxy bridge on loopback interfaces

Hi, Cedric! If you double checked the PCAP and you really are missing the flow from RTPProxy to callee, I take your word for it. Pehaps the logging is misleading. Now, if RTPProxy does not send any packet to the callee, this means that it doesn't get any packets from him. This means that

Re: [OpenSIPS-Users] opensips + rtpproxy bridge on loopback interfaces

Hello Razvan, Le 26/10/2016 à 13:52, Răzvan Crainea a écrit : Hi, Cedric! Are you sure that the flows you do not see are the ones you mentioned? According to the logs, you do not see the RTP coming from the caller: RTP stats: 410 in from callee, 0 in from caller Do these stats work correctly

Re: [OpenSIPS-Users] opensips + rtpproxy bridge on loopback interfaces

Hi, Cedric! Are you sure that the flows you do not see are the ones you mentioned? According to the logs, you do not see the RTP coming from the caller: RTP stats: 410 in from callee, 0 in from caller So the problem seems to be not on the private network, but on the public one. Or there is a

Re: [OpenSIPS-Users] opensips + rtpproxy bridge on loopback interfaces

I've made a new test, replacing mediaproxy "external" address by 111.122.100.18 (which is the SIG address). It works fine (rtp stream is complete), but that's not what I'm trying to do. I need to have a different address for the SIG and for the MEDIA. Hope it helps... Regards, Cédric Le

[OpenSIPS-Users] opensips + rtpproxy bridge on loopback interfaces

Hello, I'm trying to set up opensips (v2.2.2) and rtpproxy (2.0.beta.20150106) one the same server, using loopback interfaces. -- network config : lo:2 : inet 111.122.100.18/32 (SIG address) lo:4 : inet 111.122.100.20/32 (MEDIA address) eth1 :

[OpenSIPS-Users] sippy rtp_cluster usage

​ Hello, I am currently using rtpproxy with opensips and need to add more rtpproxies (hosted on different servers) I thought to use rtp_cluster as the frontend for multiple rtpproxies. Although the rtp_cluster socket does respond fine via the rtpproxy command protocol. And, I get: