[OpenSIPS-Users] rtpproxy module not supporting valid payload types

2020-04-02 Thread Robert Dyck
Regarding opensips-3.0 Use case - webrtc client behind NAT The rtpproxy module emitted the error message "can't extract media port from the message" ( by the way, very misleading ). In reality extract_mediainfo fails because it could not find a supported payload type in the media description.

[OpenSIPS-Users] [Blog] BLF reloaded, or a more accurate and detailed approach

2020-04-02 Thread Bogdan-Andrei Iancu
Hi all, The BLF (or dialoginfo) support has in the upcoming OpenSIPS 3.1 a more accurate and detailed reporting, being able to handle parallel and serial call forking. This is an important milestone on the #class5 path.

[OpenSIPS-Users] OpenSIPs Console Two o more servers configuration.

2020-04-02 Thread Social Boh
Hello list, I'm trying to configure two boxes on the OpenSIPs Console trough boxes.global.inc.php without success. Both boxes have the same $boxes[$box_id]['assoc_id']=1; One is local: $boxes[$box_id]['mi']['conn']="json:127.0.0.1:8088/json"; and one is remote:

Re: [OpenSIPS-Users] Access to listen/advertised IP Addresses

2020-04-02 Thread Sharad Kumar via Users
Hi Mark, If your initial goal is to get the listener IP where you received the request then you can try these variables. *$Ri* - reference to IP address of the interface where the request has been received *$Rp* - reference to the port where the message was received

Re: [OpenSIPS-Users] Access to listen/advertised IP Addresses

2020-04-02 Thread Sharad Kumar via Users
Hi Mark,  If your initial goal is to get the interface IP where request is received then you can try these variables. *$Ri* - reference to IP address of the interface where the request has been received *$Rp* - reference to the port where the message was received

[OpenSIPS-Users] Access to listen/advertised IP Addresses

2020-04-02 Thread Mark Farmer
Hi everyone Is there a way to access within the script the listen or 'listen as' IP addresses that are set in Global Parameters? I've been looking at the core variables but I can't see how it could be done. I'd like to reference them without setting a custom variable. I am using OpenSIPS 2.4.7

Re: [OpenSIPS-Users] mid_registrar - AOR mode - Disable parallel forking.

2020-04-02 Thread Liviu Chircu
On 02.04.2020 11:16, Alain Bieuzent wrote: The issue (in my case) that in case of asterisk box send a call to janus (via opensips mid_registrar module), the call is forked to the 2 janus endpoints in parallel I want to limit the incoming to only the last endpoint registered. Is there a

Re: [OpenSIPS-Users] trouble migrating from 3.0 to 3.1 with drouting.

2020-04-02 Thread Johan De Clercq
Hello, should I open a bug for this on github or how do I need to proceed ? BR, Op di 31 mrt. 2020 om 19:23 schreef johan : > Hi guys when I call do_routing in opensips 3.1. I have : > > Mar 31 16:52:25 hendrix /data/opensips/sbin/opensips[20886]: > callid=hxj~vmgW54: route[drouting]: let's

[OpenSIPS-Users] mid_registrar - AOR mode - Disable parallel forking.

2020-04-02 Thread Alain Bieuzent
Hi, I’m trying to use mid_registrar module between a janus gateway and asterisk box. I have the same janus endpoints registered 2 time opensips mid_registrar module (so only 1 with opensips IP forward to asterisk box) The issue (in my case) that in case of asterisk box send a call to