My config.h file from OpenSIPS sources still has 5060 as the default SIP
port. Does this need to be changed to 12223 and OpenSIPS recompiled from
source if I want to use port 12223?. Will that fix the error?
___
Users mailing list
Users@lists.opensips.o
I'm using port 12221 for rtpproxy (from default script) and port 12223 for
OpenSIPS. Are those 'bad ports' like the error says?
On 19 Aug 2015 06:48, "Nabeel" wrote:
> Hi,
>
> The rtpproxy error is resolved with your suggestion, but I still get the
> 'bad port' errors in the log followed by CANC
Hi,
The rtpproxy error is resolved with your suggestion, but I still get the
'bad port' errors in the log followed by CANCEL of the call:
ERROR:core:parse_via: bad port
> ERROR:core:parse_via: 10.61.208.143:46032:-1;rport;branch=z9hG4bK78006#015#012Max-Forwards:
> 70#015#012To: #015#012From:
>
Hi Bogdan,
Sorry for sending this on the eve of the new release. I opened a
feature request a couple of weeks ago with regards to perl_exec() not
accepting a variable as a parameter and wondering if the fix is included
in the new release.
Feature request #594 (perl_exec() does not accept variable
Bogdan,
it appears to be broken as of 1.11 and 2.1 yes. I couldn't find any more
indications in the logs that would point to a visible error, but the ACK
still has no SDP.
I have a few machines to test this out with the different versions, let me
know if you want a specific trace or core dump, ha
Hello,
For the Management Interface (MI), the XMLRPC backend is one of the most
used one due to its spreading and flexibility. Nevertheless, the XMLRPC
implementation in OpenSIPS did not take full advantage of the XML power
when comes to syntax.
In OpenSIPS 2.2 (devel version) , the mi_xmlrpc_ng
In my table there is a priority column! ;) I don't know where did I get
that schema... sorry, my mistake.
Now, going back to the workarround (just in case someone has the same
issue), since I'm not using the attrs column value in the config file, I
will use that column to order the set. To accompl
Hello,
The BIN interface is designed for high-traffic data exchange between
multiple OpenSIPS interfaces. This requires a fast, reliable and lossless
transport for the BIN interface. Unfortunately, the existing UDP transport
for BIN showed significant package loss under high traffic even in a
priv
Bodgan,
Yes , i tried 1.11 and had the same issue, so i went down to 1.8 TLS and it
worked right away with the same scenario. A fee config changes but overal
its the standrad script.
With 1.8 i see the sdp on the Ack and the call connects without problems.
Even video.
Not sure why it did not wor
Sebastian,
So 1.11 and above are broken in this late ACK generation ? If so, I will
dig into .
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 18.08.2015 16:20, Sebastian Sastre wrote:
Bodgan,
Yes , i tried 1.11 and had the same issue, so i
Rodrigo,
See more on the MI interface in OpenSIPS:
http://www.opensips.org/Documentation/Interface-MI-1-11
And about the MI commands exposed by the dialog module:
http://www.opensips.org/html/docs/modules/1.11.x/dialog.html#id296664
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Develop
Hi Søren,
The logs do not show any indication of you using topology_hiding. So, I
guess it is about "fixing" the natted IP addresses, right ? If so, for
the replies coming from behind nat, you need to do fix_nated_contact() .
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http:/
Hi Rodrigo,
What you can do is to write down an external script to look for the S1
calls (using the MI dlg_list_dlg command) and to terminate the call
(using the dlg_end_dlg MI command).
You can invoke such an external script via exec() module.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder a
Dear OpenSIPS-users,
Let´s suppose someone (S1) is talking at a softphone.
Let´s suppose another person (S2) needs to talk to S1 at same time.
So, S2 calls S1.
How to configure OpenSIPS to tear down ("hang up") the current S1 call and then
send the S2 INVITE message to S1? Some example?
Federico,
There is no "priority" field in the dispatcher table in 1.11 :
http://www.opensips.org/Documentation/Install-DBSchema-1-11#AEN4123
wrong table ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 17.08.2015 21:03, Federico Edorna wrote:
Hi Sebastian,
You mentioned yesterday on IRC channel that you fixed the problem ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 17.08.2015 13:40, Sebastian Sastre wrote:
Bodgan,
Thanks i wasn't sure on the ack process. This is the log , the
Hello Guys,
Do you guys have an idea why I'm see some rfc1918 IP addresses in 180 ringing
messages? - All other messages are topology hiding rewriteing with my server
address.
180 ringing header:
2015/08/17 13:02:49.513033 XXX.XXX.XXX.117:5060 -> XXX.XXX.XXX.36:5060
SIP/2.0 180 Ringing
Via: SI
17 matches
Mail list logo
