date:20160408

Re: [OpenSIPS-Users] Opensips SIP trunk call handling

2016-04-08 Thread Aqs Younas

You better ask this question on freeswitch list.

Anyway you need to handle call in public.xml and add ip in acl too.
On Apr 8, 2016 6:51 PM, "Francjos" <35...@heb.be> wrote:

To tell Freeswitch that calls come from Opensips proxy, do i have to create
a
new external profile in sip_profiles directory or add an extension in
dialplan/public.xml or both of two?

Second question, in this file
:/usr/local/freeswitch/conf/autoload_configs/acl.conf.xml , i read that i
have to specify the CIDR, is the ip address the one of Opensips?

Thank you



--
View this message in context:
http://opensips-open-sip-server.1449251.n2.nabble.com/Opensips-SIP-trunk-call-handling-tp7602552p7602562.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] opensips 2.2 dont print anything via rsyslog

2016-04-08 Thread Bogdan-Andrei Iancu


Hi Artem,

As debug_mode is by default 0, is the logging working if you remove the 
debug_mode=0 line ?


Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 05.04.2016 15:42, Чалков Артём wrote:

Hey all!
After updating to opensips 2.2 (latest), my opensips not print 
anything in log using rsyslog (actually, even doesn't create logfile). 
When it was on 2.1 - everything was ok.

Anybody encountered same problem? Or maybe i missed something?
My log-related part of config:

log_level=3
xlog_default_level=3
log_facility=LOG_LOCAL0
debug_mode=0

My rsyslog's part of config about local0:

$template DailyLogs,"/var/log/sip/%$MONTH%-%$DAY%-%$HOUR%"

local0.* -?DailyLogs




___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips Multi instance issue on SIP TLS

2016-04-08 Thread feroze waris

Ben

are you saying log lines printed above listen parameter or above error.
if you are talking about listen parameter then no and if you are talking
about error then yes. This error occurs when proxy tries to relay invite
request to B party

regards
Feroze




On Fri, Apr 8, 2016 at 8:04 PM, Benjamin Cropley  wrote:

> Feroze,
>
> Are any other lines of logging printed just above it?
>
> Ben
>
> On Fri, Apr 8, 2016 at 3:48 PM, feroze waris 
> wrote:
>
>> Ben
>>
>> I have put the address of my interface
>>
>> Regards
>> Feroze
>>
>> On Fri, Apr 8, 2016 at 7:39 PM, Benjamin Cropley <
>> benjamin.crop...@gmail.com> wrote:
>>
>>> Feroze
>>>
>>> Can I just check.. in the listen variable have you put the address of
>>> your interface or 1.2.3.4?
>>>
>>> You need to put your address.. not 1.2.3.4
>>>
>>> On Fri, Apr 8, 2016 at 3:30 PM, feroze waris 
>>> wrote:
>>>
 Hi ben

 As you said i have enabled the listen=tls:1.2.3.4:5061 on receiving
 proxy as well.  Now i am getting the following error in this case

 Apr  8 14:08:12 localhost OPENSIPS[623]: ERROR:tm:msg_send: send() for
 proto 3 failed
 Apr  8 14:08:12 localhost OPENSIPS[623]: ERROR:tm:t_forward_nonack:
 sending request failed
 Apr  8 14:08:12 localhost OPENSIPS[623]: ERROR:tm:w_t_relay:
 t_forward_nonack failed


 regards
 Feroze

 On Fri, Apr 8, 2016 at 1:15 PM, Benjamin Cropley <
 benjamin.crop...@gmail.com> wrote:

> Feroze,
>
> I think you misunderstood :)
>
> I was saying, the URI has ;transport=tls, but the receiving server
> probably doesn't have a port open to listen for it.. Don't remove this if
> you want to use TLS, as by using rewrite() you're effectively breaking TLS
> ;)
>
> In the documentation it says if you dont specify a listen= variable,
> then it will listen on 'all interfaces'. It doesn't say whether it will
> listen to UDP TCP and TLS. But I would guess it's possibly only UDP and 
> TCP.
>
> Therefore, make sure on the servers receiving the packets that you
> specifically set a tls listening interface with listen = tls:
> 1.2.3.4:5061
>
> Good luck
> Ben
>
>
> On Fri, Apr 8, 2016 at 7:29 AM, feroze waris <
> feroze.chaud...@gmail.com> wrote:
>
>> Hi ben
>>
>> I have checked the traces and you were right that there was transport
>> = tls in RURI when request forwards from load balancer  to 2 opensips
>> instances . I have replaced the RURI using rewrite() function and removed
>> the transport parameter but the issue remains and i am getting the same
>> error
>>
>>
>> regards
>> Feroze
>>
>> On Thu, Apr 7, 2016 at 1:09 PM, Benjamin Cropley <
>> benjamin.crop...@gmail.com> wrote:
>>
>>> Wild guess here, based on what I've read..
>>>
>>> It might be your request URI is explicitly declaring which protocol
>>> to use, and OpenSIPS has no interface configured for that protocol.. eg.
>>> ;transport=tls is added to the request URI but there's no listen = tls:
>>> 1.2.3.4:5061
>>>
>>> I know it's tricky to look at a trace for TLS. But have a look at
>>> http://wiki.snom.com/FAQ/How_to_decode_TLS_calls_using_wireshark
>>>
>>> Good luck
>>> Ben
>>>
>>> On Wed, Apr 6, 2016 at 6:24 PM, feroze waris <
>>> feroze.chaud...@gmail.com> wrote:
>>>
 Hi ben

 yes i am load balancing the Register and Invite request to two
 proxy servers using dispatcher module but all three servers (i.e load
 balncer and two opensips servers) are sharing same opensips database.
 This issue is not occurring in UDP call but on TLS this error
 occurs.

 Regards
 Feroze

 On Wed, Apr 6, 2016 at 7:34 PM, Benjamin Cropley <
 benjamin.crop...@gmail.com> wrote:

> Feroze,
>
> Are you load balancing REGISTER *and *INVITE requests to
> different nodes?
>
> If so, then unless you share location information between the
> Registrars, then they wont all know where to route INVITEs.
>
> Ben
>
>
> On Wed, Apr 6, 2016 at 3:20 PM, feroze waris <
> feroze.chaud...@gmail.com> wrote:
>
>> Hello
>>
>> I have one load balancer connected to 2 opensips server
>> Request is balancing through dispatcher module on load balancer
>> the problem is when Register request of B party lands on
>> different server than that server at which A Party sends invite 
>> request the
>> call drops and i am getting following error
>> Apr  6 07:58:31 localhost OPENSIP[1793]: ERROR:tm:update_uac_dst:
>> failed to fwd to af 2, proto 3  (no

Re: [OpenSIPS-Users] Opensips Multi instance issue on SIP TLS

2016-04-08 Thread Benjamin Cropley

Feroze,

Are any other lines of logging printed just above it?

Ben

On Fri, Apr 8, 2016 at 3:48 PM, feroze waris 
wrote:

> Ben
>
> I have put the address of my interface
>
> Regards
> Feroze
>
> On Fri, Apr 8, 2016 at 7:39 PM, Benjamin Cropley <
> benjamin.crop...@gmail.com> wrote:
>
>> Feroze
>>
>> Can I just check.. in the listen variable have you put the address of
>> your interface or 1.2.3.4?
>>
>> You need to put your address.. not 1.2.3.4
>>
>> On Fri, Apr 8, 2016 at 3:30 PM, feroze waris 
>> wrote:
>>
>>> Hi ben
>>>
>>> As you said i have enabled the listen=tls:1.2.3.4:5061 on receiving
>>> proxy as well.  Now i am getting the following error in this case
>>>
>>> Apr  8 14:08:12 localhost OPENSIPS[623]: ERROR:tm:msg_send: send() for
>>> proto 3 failed
>>> Apr  8 14:08:12 localhost OPENSIPS[623]: ERROR:tm:t_forward_nonack:
>>> sending request failed
>>> Apr  8 14:08:12 localhost OPENSIPS[623]: ERROR:tm:w_t_relay:
>>> t_forward_nonack failed
>>>
>>>
>>> regards
>>> Feroze
>>>
>>> On Fri, Apr 8, 2016 at 1:15 PM, Benjamin Cropley <
>>> benjamin.crop...@gmail.com> wrote:
>>>
 Feroze,

 I think you misunderstood :)

 I was saying, the URI has ;transport=tls, but the receiving server
 probably doesn't have a port open to listen for it.. Don't remove this if
 you want to use TLS, as by using rewrite() you're effectively breaking TLS
 ;)

 In the documentation it says if you dont specify a listen= variable,
 then it will listen on 'all interfaces'. It doesn't say whether it will
 listen to UDP TCP and TLS. But I would guess it's possibly only UDP and 
 TCP.

 Therefore, make sure on the servers receiving the packets that you
 specifically set a tls listening interface with listen = tls:
 1.2.3.4:5061

 Good luck
 Ben


 On Fri, Apr 8, 2016 at 7:29 AM, feroze waris  wrote:

> Hi ben
>
> I have checked the traces and you were right that there was transport
> = tls in RURI when request forwards from load balancer  to 2 opensips
> instances . I have replaced the RURI using rewrite() function and removed
> the transport parameter but the issue remains and i am getting the same
> error
>
>
> regards
> Feroze
>
> On Thu, Apr 7, 2016 at 1:09 PM, Benjamin Cropley <
> benjamin.crop...@gmail.com> wrote:
>
>> Wild guess here, based on what I've read..
>>
>> It might be your request URI is explicitly declaring which protocol
>> to use, and OpenSIPS has no interface configured for that protocol.. eg.
>> ;transport=tls is added to the request URI but there's no listen = tls:
>> 1.2.3.4:5061
>>
>> I know it's tricky to look at a trace for TLS. But have a look at
>> http://wiki.snom.com/FAQ/How_to_decode_TLS_calls_using_wireshark
>>
>> Good luck
>> Ben
>>
>> On Wed, Apr 6, 2016 at 6:24 PM, feroze waris <
>> feroze.chaud...@gmail.com> wrote:
>>
>>> Hi ben
>>>
>>> yes i am load balancing the Register and Invite request to two proxy
>>> servers using dispatcher module but all three servers (i.e load balncer 
>>> and
>>> two opensips servers) are sharing same opensips database.
>>> This issue is not occurring in UDP call but on TLS this error
>>> occurs.
>>>
>>> Regards
>>> Feroze
>>>
>>> On Wed, Apr 6, 2016 at 7:34 PM, Benjamin Cropley <
>>> benjamin.crop...@gmail.com> wrote:
>>>
 Feroze,

 Are you load balancing REGISTER *and *INVITE requests to different
 nodes?

 If so, then unless you share location information between the
 Registrars, then they wont all know where to route INVITEs.

 Ben


 On Wed, Apr 6, 2016 at 3:20 PM, feroze waris <
 feroze.chaud...@gmail.com> wrote:

> Hello
>
> I have one load balancer connected to 2 opensips server
> Request is balancing through dispatcher module on load balancer
> the problem is when Register request of B party lands on different
> server than that server at which A Party sends invite request the call
> drops and i am getting following error
> Apr  6 07:58:31 localhost OPENSIP[1793]: ERROR:tm:update_uac_dst:
> failed to fwd to af 2, proto 3  (no corresponding listening socket)
> Apr  6 07:58:31 localhost OPENSIP[1793]:
> ERROR:tm:t_forward_nonack: failure to add branches
> Apr  6 07:58:31 localhost OPENSIP[1793]: ERROR:tm:w_t_relay:
> t_forward_nonack failed
>
> I am using Openisps version 2.1.1 and using TLS on it
>
>
> Regards
> Feroze
>
> ___
> Users mailing list
>

Re: [OpenSIPS-Users] opensips 2.2 dont print anything via rsyslog

2016-04-08 Thread Чалков Артём

Thank you, Liviu! 08.04.2016, 17:55, "Liviu Chircu" :Hi Artem!  You must also set "log_stderror = false". Omitting this setting will cause the "log_facility" param to be ignored, and all OpenSIPS processes will log everything to stderr.Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.comOn 05.04.2016 15:42, Чалков Артём wrote:Hey all! After updating to opensips 2.2 (latest), my opensips not print anything in log using rsyslog (actually, even doesn't create logfile). When it was on 2.1 - everything was ok.Anybody encountered same problem? Or maybe i missed something?  My log-related part of config:log_level=3 xlog_default_level=3 log_facility=LOG_LOCAL0 debug_mode=0 My rsyslog's part of config about local0:$template DailyLogs,"/var/log/sip/%$MONTH%-%$DAY%-%$HOUR%"local0.* -?DailyLogs ___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
,___Users mailing listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] opensips 2.2 dont print anything via rsyslog

2016-04-08 Thread Liviu Chircu


Hi Artem!

You must also set "log_stderror = false". Omitting this setting will 
cause the "log_facility" param to be ignored, and all OpenSIPS processes 
will log everything to stderr.


Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com

On 05.04.2016 15:42, Чалков Артём wrote:

Hey all!
After updating to opensips 2.2 (latest), my opensips not print 
anything in log using rsyslog (actually, even doesn't create logfile). 
When it was on 2.1 - everything was ok.

Anybody encountered same problem? Or maybe i missed something?
My log-related part of config:

log_level=3
xlog_default_level=3
log_facility=LOG_LOCAL0
debug_mode=0

My rsyslog's part of config about local0:

$template DailyLogs,"/var/log/sip/%$MONTH%-%$DAY%-%$HOUR%"

local0.* -?DailyLogs



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] TLS - Certificate Validation Failure error on SIP Phones - OpenSIPS version 1.11.5

2016-04-08 Thread Rodrigo Pimenta Carvalho

Hi.


I got the same problem in softphone ZOIPER.

I just let my ZOIPER ignore the file received from OpenSIPS and then the 
problem was solved. Otherwise I should had to install the client party on the 
phone. It was possible for me because in my project I didn't have to use 
certificates, just cryptographic messages with TLS.


See below the configuration in my OpenSIPS.cfg file (my proxy is version 2.2 
from 2015):


loadmodule "proto_tls.so"

 modparam("proto_tls","verify_cert", "0")
 modparam("proto_tls","require_cert", "0")  #0 means  *do not* force the client 
to present a certificate where as 1 means *do* ask the client to present a cert.
 modparam("proto_tls","tls_method", "TLSv1")  #If you want RFC3261 conformance 
and all your clients support TLSv1 (or you are planning to use encrypted 
"tunnels" only between differe


modparam("proto_tls", "certificate",  
"/usr/local/etc/opensips/tls/rootCA/certs/cert.pem")
modparam("proto_tls", "private_key", 
"/usr/local/etc/opensips/tls/rootCA/private/key.pem")
modparam("proto_tls", "ca_list", 
"/usr/local/etc/opensips/tls/rootCA/cacert.pem")
modparam("proto_tls", "ca_dir", "/usr/local/etc/opensips/tls/rootCA/")


# Sets the TLS protocol. The first parameter, if set, represents the id of the 
domain. TLS method which can be:
#
#TLSv1_2 - means OpenSIPS will accept only TLSv1.2 connections (rfc3261 
conformant).
#
#TLSv1 - means OpenSIPS will accept only TLSv1 connections (rfc3261 
conformant).
#
#SSLv3 - means OpenSIPS will accept only SSLv3 connections
#
#SSLv2 - means OpenSIPS will accept only SSLv2 connections (almost all old 
clients support this).
#
#SSLv23 - means OpenSIPS will accept any of the above methods, but the 
initial SSL hello must be v2 (in the initial hello all the supported protocols 
are advertised enabling swit
#
#Default value is SSLv23.


Tell me if I'm wrongly, please.


Best regards.



RODRIGO PIMENTA CARVALHO
Inatel Competence Center
Software
Ph: +55 35 3471 9200 RAMAL 979



De: users-boun...@lists.opensips.org  em nome 
de Ali Pey 
Enviado: sexta-feira, 8 de abril de 2016 10:25
Para: OpenSIPS users mailling list
Assunto: Re: [OpenSIPS-Users] TLS - Certificate Validation Failure error on SIP 
Phones - OpenSIPS version 1.11.5

Hello Hamid,

The parameters below don't have any effects. In my scenario, the sip phones are 
rejecting the tls connection by saying "Certificate Validation Failure".

Neither of parameters below had any effects.


Anyone else has any idea what I need to look for?

Regards,
Ali Pey


On Fri, Apr 8, 2016 at 4:00 AM, Hamid Hashmi 
> wrote:
Please define  following values

tls_ca_list = "/path/to/file"
tls_method  = tlsv1

for details please consult 
http://www.opensips.org/html/docs/tutorials/tls-1.4.x.html

Regards
Hamid R. Hashmi


Date: Thu, 7 Apr 2016 13:14:28 -0400
From: ali...@gmail.com
To: users@lists.opensips.org
Subject: [OpenSIPS-Users] TLS - Certificate Validation Failure error on SIP 
Phones - OpenSIPS version 1.11.5


Hello,

My opensips server is just a registrar server and I have enabled tls with the 
following settings:

listen=tls:xx.xx.xx.xx:5061
disable_tls=no
tls_certificate="/etc/opensips/pbx-bundle.crt"
tls_private_key="/etc/opensips/pbx.key"


When my sip phones try to open tls connection, they reject the connection 
saying "Certificate Validation Failure". My certificate is valid and works fine 
on the https website.

What am I missing? What should I look for?

Regards,
Ali Pey



___ Users mailing list 
Users@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips Multi instance issue on SIP TLS

2016-04-08 Thread feroze waris

Ben

I have put the address of my interface

Regards
Feroze

On Fri, Apr 8, 2016 at 7:39 PM, Benjamin Cropley  wrote:

> Feroze
>
> Can I just check.. in the listen variable have you put the address of your
> interface or 1.2.3.4?
>
> You need to put your address.. not 1.2.3.4
>
> On Fri, Apr 8, 2016 at 3:30 PM, feroze waris 
> wrote:
>
>> Hi ben
>>
>> As you said i have enabled the listen=tls:1.2.3.4:5061 on receiving
>> proxy as well.  Now i am getting the following error in this case
>>
>> Apr  8 14:08:12 localhost OPENSIPS[623]: ERROR:tm:msg_send: send() for
>> proto 3 failed
>> Apr  8 14:08:12 localhost OPENSIPS[623]: ERROR:tm:t_forward_nonack:
>> sending request failed
>> Apr  8 14:08:12 localhost OPENSIPS[623]: ERROR:tm:w_t_relay:
>> t_forward_nonack failed
>>
>>
>> regards
>> Feroze
>>
>> On Fri, Apr 8, 2016 at 1:15 PM, Benjamin Cropley <
>> benjamin.crop...@gmail.com> wrote:
>>
>>> Feroze,
>>>
>>> I think you misunderstood :)
>>>
>>> I was saying, the URI has ;transport=tls, but the receiving server
>>> probably doesn't have a port open to listen for it.. Don't remove this if
>>> you want to use TLS, as by using rewrite() you're effectively breaking TLS
>>> ;)
>>>
>>> In the documentation it says if you dont specify a listen= variable,
>>> then it will listen on 'all interfaces'. It doesn't say whether it will
>>> listen to UDP TCP and TLS. But I would guess it's possibly only UDP and TCP.
>>>
>>> Therefore, make sure on the servers receiving the packets that you
>>> specifically set a tls listening interface with listen = tls:
>>> 1.2.3.4:5061
>>>
>>> Good luck
>>> Ben
>>>
>>>
>>> On Fri, Apr 8, 2016 at 7:29 AM, feroze waris 
>>> wrote:
>>>
 Hi ben

 I have checked the traces and you were right that there was transport =
 tls in RURI when request forwards from load balancer  to 2 opensips
 instances . I have replaced the RURI using rewrite() function and removed
 the transport parameter but the issue remains and i am getting the same
 error


 regards
 Feroze

 On Thu, Apr 7, 2016 at 1:09 PM, Benjamin Cropley <
 benjamin.crop...@gmail.com> wrote:

> Wild guess here, based on what I've read..
>
> It might be your request URI is explicitly declaring which protocol to
> use, and OpenSIPS has no interface configured for that protocol.. eg.
> ;transport=tls is added to the request URI but there's no listen = tls:
> 1.2.3.4:5061
>
> I know it's tricky to look at a trace for TLS. But have a look at
> http://wiki.snom.com/FAQ/How_to_decode_TLS_calls_using_wireshark
>
> Good luck
> Ben
>
> On Wed, Apr 6, 2016 at 6:24 PM, feroze waris <
> feroze.chaud...@gmail.com> wrote:
>
>> Hi ben
>>
>> yes i am load balancing the Register and Invite request to two proxy
>> servers using dispatcher module but all three servers (i.e load balncer 
>> and
>> two opensips servers) are sharing same opensips database.
>> This issue is not occurring in UDP call but on TLS this error occurs.
>>
>> Regards
>> Feroze
>>
>> On Wed, Apr 6, 2016 at 7:34 PM, Benjamin Cropley <
>> benjamin.crop...@gmail.com> wrote:
>>
>>> Feroze,
>>>
>>> Are you load balancing REGISTER *and *INVITE requests to different
>>> nodes?
>>>
>>> If so, then unless you share location information between the
>>> Registrars, then they wont all know where to route INVITEs.
>>>
>>> Ben
>>>
>>>
>>> On Wed, Apr 6, 2016 at 3:20 PM, feroze waris <
>>> feroze.chaud...@gmail.com> wrote:
>>>
 Hello

 I have one load balancer connected to 2 opensips server
 Request is balancing through dispatcher module on load balancer
 the problem is when Register request of B party lands on different
 server than that server at which A Party sends invite request the call
 drops and i am getting following error
 Apr  6 07:58:31 localhost OPENSIP[1793]: ERROR:tm:update_uac_dst:
 failed to fwd to af 2, proto 3  (no corresponding listening socket)
 Apr  6 07:58:31 localhost OPENSIP[1793]: ERROR:tm:t_forward_nonack:
 failure to add branches
 Apr  6 07:58:31 localhost OPENSIP[1793]: ERROR:tm:w_t_relay:
 t_forward_nonack failed

 I am using Openisps version 2.1.1 and using TLS on it


 Regards
 Feroze

 ___
 Users mailing list
 Users@lists.opensips.org
 http://lists.opensips.org/cgi-bin/mailman/listinfo/users


>>>
>>> ___
>>> Users mailing list
>>> Users@lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>>
>>
>>

Re: [OpenSIPS-Users] Opensips Multi instance issue on SIP TLS

2016-04-08 Thread Benjamin Cropley

Feroze

Can I just check.. in the listen variable have you put the address of your
interface or 1.2.3.4?

You need to put your address.. not 1.2.3.4

On Fri, Apr 8, 2016 at 3:30 PM, feroze waris 
wrote:

> Hi ben
>
> As you said i have enabled the listen=tls:1.2.3.4:5061 on receiving proxy
> as well.  Now i am getting the following error in this case
>
> Apr  8 14:08:12 localhost OPENSIPS[623]: ERROR:tm:msg_send: send() for
> proto 3 failed
> Apr  8 14:08:12 localhost OPENSIPS[623]: ERROR:tm:t_forward_nonack:
> sending request failed
> Apr  8 14:08:12 localhost OPENSIPS[623]: ERROR:tm:w_t_relay:
> t_forward_nonack failed
>
>
> regards
> Feroze
>
> On Fri, Apr 8, 2016 at 1:15 PM, Benjamin Cropley <
> benjamin.crop...@gmail.com> wrote:
>
>> Feroze,
>>
>> I think you misunderstood :)
>>
>> I was saying, the URI has ;transport=tls, but the receiving server
>> probably doesn't have a port open to listen for it.. Don't remove this if
>> you want to use TLS, as by using rewrite() you're effectively breaking TLS
>> ;)
>>
>> In the documentation it says if you dont specify a listen= variable, then
>> it will listen on 'all interfaces'. It doesn't say whether it will listen
>> to UDP TCP and TLS. But I would guess it's possibly only UDP and TCP.
>>
>> Therefore, make sure on the servers receiving the packets that you
>> specifically set a tls listening interface with listen = tls:1.2.3.4:5061
>>
>> Good luck
>> Ben
>>
>>
>> On Fri, Apr 8, 2016 at 7:29 AM, feroze waris 
>> wrote:
>>
>>> Hi ben
>>>
>>> I have checked the traces and you were right that there was transport =
>>> tls in RURI when request forwards from load balancer  to 2 opensips
>>> instances . I have replaced the RURI using rewrite() function and removed
>>> the transport parameter but the issue remains and i am getting the same
>>> error
>>>
>>>
>>> regards
>>> Feroze
>>>
>>> On Thu, Apr 7, 2016 at 1:09 PM, Benjamin Cropley <
>>> benjamin.crop...@gmail.com> wrote:
>>>
 Wild guess here, based on what I've read..

 It might be your request URI is explicitly declaring which protocol to
 use, and OpenSIPS has no interface configured for that protocol.. eg.
 ;transport=tls is added to the request URI but there's no listen = tls:
 1.2.3.4:5061

 I know it's tricky to look at a trace for TLS. But have a look at
 http://wiki.snom.com/FAQ/How_to_decode_TLS_calls_using_wireshark

 Good luck
 Ben

 On Wed, Apr 6, 2016 at 6:24 PM, feroze waris  wrote:

> Hi ben
>
> yes i am load balancing the Register and Invite request to two proxy
> servers using dispatcher module but all three servers (i.e load balncer 
> and
> two opensips servers) are sharing same opensips database.
> This issue is not occurring in UDP call but on TLS this error occurs.
>
> Regards
> Feroze
>
> On Wed, Apr 6, 2016 at 7:34 PM, Benjamin Cropley <
> benjamin.crop...@gmail.com> wrote:
>
>> Feroze,
>>
>> Are you load balancing REGISTER *and *INVITE requests to different
>> nodes?
>>
>> If so, then unless you share location information between the
>> Registrars, then they wont all know where to route INVITEs.
>>
>> Ben
>>
>>
>> On Wed, Apr 6, 2016 at 3:20 PM, feroze waris <
>> feroze.chaud...@gmail.com> wrote:
>>
>>> Hello
>>>
>>> I have one load balancer connected to 2 opensips server
>>> Request is balancing through dispatcher module on load balancer
>>> the problem is when Register request of B party lands on different
>>> server than that server at which A Party sends invite request the call
>>> drops and i am getting following error
>>> Apr  6 07:58:31 localhost OPENSIP[1793]: ERROR:tm:update_uac_dst:
>>> failed to fwd to af 2, proto 3  (no corresponding listening socket)
>>> Apr  6 07:58:31 localhost OPENSIP[1793]: ERROR:tm:t_forward_nonack:
>>> failure to add branches
>>> Apr  6 07:58:31 localhost OPENSIP[1793]: ERROR:tm:w_t_relay:
>>> t_forward_nonack failed
>>>
>>> I am using Openisps version 2.1.1 and using TLS on it
>>>
>>>
>>> Regards
>>> Feroze
>>>
>>> ___
>>> Users mailing list
>>> Users@lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>>
>>
>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>

 ___
 Users mailing list
 Users@lists.opensips.org

[OpenSIPS-Users] Should I worry about INFO "no free tcp receiver"?

2016-04-08 Thread Rodrigo Pimenta Carvalho

Hi.


I saw in the OpenSIPS log:


Apr 08 14:32:37 colibri-imx6 opensips[880]: Apr  8 14:32:37 [892] 
INFO:core:probe_max_sock_buff: using snd buffer of 320 kb
Apr 08 14:32:37 colibri-imx6 opensips[880]: Apr  8 14:32:37 [892] 
INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 34
Apr 08 14:32:37 colibri-imx6 opensips[880]: Apr  8 14:32:37 [892] 
INFO:core:send2child: no free tcp receiver, connection passed to the least busy 
one (1)

Should I worry about it?

Could it become a warning some day?


Any hint will be very helpful!


Best regards.


RODRIGO PIMENTA CARVALHO
Inatel Competence Center
Software
Ph: +55 35 3471 9200 RAMAL 979
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips Multi instance issue on SIP TLS

2016-04-08 Thread feroze waris

Hi ben

As you said i have enabled the listen=tls:1.2.3.4:5061 on receiving proxy
as well.  Now i am getting the following error in this case

Apr  8 14:08:12 localhost OPENSIPS[623]: ERROR:tm:msg_send: send() for
proto 3 failed
Apr  8 14:08:12 localhost OPENSIPS[623]: ERROR:tm:t_forward_nonack: sending
request failed
Apr  8 14:08:12 localhost OPENSIPS[623]: ERROR:tm:w_t_relay:
t_forward_nonack failed


regards
Feroze

On Fri, Apr 8, 2016 at 1:15 PM, Benjamin Cropley  wrote:

> Feroze,
>
> I think you misunderstood :)
>
> I was saying, the URI has ;transport=tls, but the receiving server
> probably doesn't have a port open to listen for it.. Don't remove this if
> you want to use TLS, as by using rewrite() you're effectively breaking TLS
> ;)
>
> In the documentation it says if you dont specify a listen= variable, then
> it will listen on 'all interfaces'. It doesn't say whether it will listen
> to UDP TCP and TLS. But I would guess it's possibly only UDP and TCP.
>
> Therefore, make sure on the servers receiving the packets that you
> specifically set a tls listening interface with listen = tls:1.2.3.4:5061
>
> Good luck
> Ben
>
>
> On Fri, Apr 8, 2016 at 7:29 AM, feroze waris 
> wrote:
>
>> Hi ben
>>
>> I have checked the traces and you were right that there was transport =
>> tls in RURI when request forwards from load balancer  to 2 opensips
>> instances . I have replaced the RURI using rewrite() function and removed
>> the transport parameter but the issue remains and i am getting the same
>> error
>>
>>
>> regards
>> Feroze
>>
>> On Thu, Apr 7, 2016 at 1:09 PM, Benjamin Cropley <
>> benjamin.crop...@gmail.com> wrote:
>>
>>> Wild guess here, based on what I've read..
>>>
>>> It might be your request URI is explicitly declaring which protocol to
>>> use, and OpenSIPS has no interface configured for that protocol.. eg.
>>> ;transport=tls is added to the request URI but there's no listen = tls:
>>> 1.2.3.4:5061
>>>
>>> I know it's tricky to look at a trace for TLS. But have a look at
>>> http://wiki.snom.com/FAQ/How_to_decode_TLS_calls_using_wireshark
>>>
>>> Good luck
>>> Ben
>>>
>>> On Wed, Apr 6, 2016 at 6:24 PM, feroze waris 
>>> wrote:
>>>
 Hi ben

 yes i am load balancing the Register and Invite request to two proxy
 servers using dispatcher module but all three servers (i.e load balncer and
 two opensips servers) are sharing same opensips database.
 This issue is not occurring in UDP call but on TLS this error occurs.

 Regards
 Feroze

 On Wed, Apr 6, 2016 at 7:34 PM, Benjamin Cropley <
 benjamin.crop...@gmail.com> wrote:

> Feroze,
>
> Are you load balancing REGISTER *and *INVITE requests to different
> nodes?
>
> If so, then unless you share location information between the
> Registrars, then they wont all know where to route INVITEs.
>
> Ben
>
>
> On Wed, Apr 6, 2016 at 3:20 PM, feroze waris <
> feroze.chaud...@gmail.com> wrote:
>
>> Hello
>>
>> I have one load balancer connected to 2 opensips server
>> Request is balancing through dispatcher module on load balancer
>> the problem is when Register request of B party lands on different
>> server than that server at which A Party sends invite request the call
>> drops and i am getting following error
>> Apr  6 07:58:31 localhost OPENSIP[1793]: ERROR:tm:update_uac_dst:
>> failed to fwd to af 2, proto 3  (no corresponding listening socket)
>> Apr  6 07:58:31 localhost OPENSIP[1793]: ERROR:tm:t_forward_nonack:
>> failure to add branches
>> Apr  6 07:58:31 localhost OPENSIP[1793]: ERROR:tm:w_t_relay:
>> t_forward_nonack failed
>>
>> I am using Openisps version 2.1.1 and using TLS on it
>>
>>
>> Regards
>> Feroze
>>
>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>

 ___
 Users mailing list
 Users@lists.opensips.org
 http://lists.opensips.org/cgi-bin/mailman/listinfo/users


>>>
>>> ___
>>> Users mailing list
>>> Users@lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>>
>>
>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>

Re: [OpenSIPS-Users] Opensips SIP trunk call handling

2016-04-08 Thread Francjos

To tell Freeswitch that calls come from Opensips proxy, do i have to create a
new external profile in sip_profiles directory or add an extension in
dialplan/public.xml or both of two?

Second question, in this file
:/usr/local/freeswitch/conf/autoload_configs/acl.conf.xml , i read that i
have to specify the CIDR, is the ip address the one of Opensips?

Thank you



--
View this message in context: 
http://opensips-open-sip-server.1449251.n2.nabble.com/Opensips-SIP-trunk-call-handling-tp7602552p7602562.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] TLS - Certificate Validation Failure error on SIP Phones - OpenSIPS version 1.11.5

2016-04-08 Thread Ali Pey

Hello Hamid,

The parameters below don't have any effects. In my scenario, the sip phones
are rejecting the tls connection by saying "Certificate Validation Failure".

Neither of parameters below had any effects.


Anyone else has any idea what I need to look for?

Regards,
Ali Pey


On Fri, Apr 8, 2016 at 4:00 AM, Hamid Hashmi 
wrote:

> Please define  following values
>
> tls_ca_list = "/path/to/file"
> tls_method  = tlsv1
>
> for details please consult
> http://www.opensips.org/html/docs/tutorials/tls-1.4.x.html
> 
>
> Regards
> Hamid R. Hashmi
>
> --
> Date: Thu, 7 Apr 2016 13:14:28 -0400
> From: ali...@gmail.com
> To: users@lists.opensips.org
> Subject: [OpenSIPS-Users] TLS - Certificate Validation Failure error on
> SIP Phones - OpenSIPS version 1.11.5
>
>
> Hello,
>
> My opensips server is just a registrar server and I have enabled tls with
> the following settings:
>
> listen=tls:xx.xx.xx.xx:5061
> disable_tls=no
> tls_certificate="/etc/opensips/pbx-bundle.crt"
> tls_private_key="/etc/opensips/pbx.key"
>
>
> When my sip phones try to open tls connection, they reject the connection
> saying "Certificate Validation Failure". My certificate is valid and works
> fine on the https website.
>
> What am I missing? What should I look for?
>
> Regards,
> Ali Pey
>
>
> ___ Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> 
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> 
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips SIP trunk call handling

2016-04-08 Thread Francjos

First, I'm gonna  test the simple case without load balancing , i'll do
changes after i success the simple routing.

Thanks



--
View this message in context: 
http://opensips-open-sip-server.1449251.n2.nabble.com/Opensips-SIP-trunk-call-handling-tp7602552p7602560.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips SIP trunk call handling

2016-04-08 Thread Benjamin Cropley

No problem.

If that's all you want to do, then just include it within a route{} block
and you should be good to go.

I will say, of that's all you want to do, when you 'load balance the invite
to FS', FS will respond with a 100 trying - and at the minute your script
will reply to FS with a 405..

Perhaps you should spend some time reading about SIP, as it'll help you
more easily implement stuff on OpenSIPS

On Fri, Apr 8, 2016 at 10:12 AM, Francjos <35...@heb.be> wrote:

> Thank you for redirecting me to the tutorial. I picked up a part of what i
> need,i think i can adjust it to my needs but the problem i still have is
> where to include the logic of load balancing in opensips.cfg. The logic is
> the following:
>
>  if (is_method("INVITE")) {
> if (!load_balance("1","pstn","1")) {
> send_reply("503","Service Unavailable");
> exit;
> }
> }
> else if (is_method("REGISTER")) {
> if (!ds_select_dst("1", "0")) {
> send_reply("503","Service Unavailable");
> exit;
> }
> }
> else {
> send_reply("405","Method Not Allowed");
> exit;
> }
>
> So that Opensips can routes calls to the write Freeswitch.
>
> Thanks again.
>
>
>
> --
> View this message in context:
> http://opensips-open-sip-server.1449251.n2.nabble.com/Opensips-SIP-trunk-call-handling-tp7602552p7602558.html
> Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips SIP trunk call handling

2016-04-08 Thread Francjos

Thank you for redirecting me to the tutorial. I picked up a part of what i
need,i think i can adjust it to my needs but the problem i still have is
where to include the logic of load balancing in opensips.cfg. The logic is
the following:

 if (is_method("INVITE")) {
if (!load_balance("1","pstn","1")) {
send_reply("503","Service Unavailable");
exit;
}
}
else if (is_method("REGISTER")) {
if (!ds_select_dst("1", "0")) {
send_reply("503","Service Unavailable");
exit;
}
}
else {
send_reply("405","Method Not Allowed");
exit;
}

So that Opensips can routes calls to the write Freeswitch.

Thanks again.



--
View this message in context: 
http://opensips-open-sip-server.1449251.n2.nabble.com/Opensips-SIP-trunk-call-handling-tp7602552p7602558.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips SIP trunk call handling

2016-04-08 Thread Benjamin Cropley

Franjos,

Have you read
http://www.opensips.org/Documentation/Tutorials-OpenSIPSFreeSwitchIntegration
?

Versions are a little out of date, but I think it looks correct still

Ben

On Fri, Apr 8, 2016 at 9:27 AM, Francjos <35...@heb.be> wrote:

> Thanks .Can you please give me more details on how i have to proceed.
> Thanks again
>
>
>
> --
> View this message in context:
> http://opensips-open-sip-server.1449251.n2.nabble.com/Opensips-SIP-trunk-call-handling-tp7602552p7602556.html
> Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips SIP trunk call handling

2016-04-08 Thread Francjos

Thanks .Can you please give me more details on how i have to proceed.
Thanks again



--
View this message in context: 
http://opensips-open-sip-server.1449251.n2.nabble.com/Opensips-SIP-trunk-call-handling-tp7602552p7602556.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips Multi instance issue on SIP TLS

2016-04-08 Thread Benjamin Cropley

Feroze,

I think you misunderstood :)

I was saying, the URI has ;transport=tls, but the receiving server probably
doesn't have a port open to listen for it.. Don't remove this if you want
to use TLS, as by using rewrite() you're effectively breaking TLS ;)

In the documentation it says if you dont specify a listen= variable, then
it will listen on 'all interfaces'. It doesn't say whether it will listen
to UDP TCP and TLS. But I would guess it's possibly only UDP and TCP.

Therefore, make sure on the servers receiving the packets that you
specifically set a tls listening interface with listen = tls:1.2.3.4:5061

Good luck
Ben


On Fri, Apr 8, 2016 at 7:29 AM, feroze waris 
wrote:

> Hi ben
>
> I have checked the traces and you were right that there was transport =
> tls in RURI when request forwards from load balancer  to 2 opensips
> instances . I have replaced the RURI using rewrite() function and removed
> the transport parameter but the issue remains and i am getting the same
> error
>
>
> regards
> Feroze
>
> On Thu, Apr 7, 2016 at 1:09 PM, Benjamin Cropley <
> benjamin.crop...@gmail.com> wrote:
>
>> Wild guess here, based on what I've read..
>>
>> It might be your request URI is explicitly declaring which protocol to
>> use, and OpenSIPS has no interface configured for that protocol.. eg.
>> ;transport=tls is added to the request URI but there's no listen = tls:
>> 1.2.3.4:5061
>>
>> I know it's tricky to look at a trace for TLS. But have a look at
>> http://wiki.snom.com/FAQ/How_to_decode_TLS_calls_using_wireshark
>>
>> Good luck
>> Ben
>>
>> On Wed, Apr 6, 2016 at 6:24 PM, feroze waris 
>> wrote:
>>
>>> Hi ben
>>>
>>> yes i am load balancing the Register and Invite request to two proxy
>>> servers using dispatcher module but all three servers (i.e load balncer and
>>> two opensips servers) are sharing same opensips database.
>>> This issue is not occurring in UDP call but on TLS this error occurs.
>>>
>>> Regards
>>> Feroze
>>>
>>> On Wed, Apr 6, 2016 at 7:34 PM, Benjamin Cropley <
>>> benjamin.crop...@gmail.com> wrote:
>>>
 Feroze,

 Are you load balancing REGISTER *and *INVITE requests to different
 nodes?

 If so, then unless you share location information between the
 Registrars, then they wont all know where to route INVITEs.

 Ben


 On Wed, Apr 6, 2016 at 3:20 PM, feroze waris  wrote:

> Hello
>
> I have one load balancer connected to 2 opensips server
> Request is balancing through dispatcher module on load balancer
> the problem is when Register request of B party lands on different
> server than that server at which A Party sends invite request the call
> drops and i am getting following error
> Apr  6 07:58:31 localhost OPENSIP[1793]: ERROR:tm:update_uac_dst:
> failed to fwd to af 2, proto 3  (no corresponding listening socket)
> Apr  6 07:58:31 localhost OPENSIP[1793]: ERROR:tm:t_forward_nonack:
> failure to add branches
> Apr  6 07:58:31 localhost OPENSIP[1793]: ERROR:tm:w_t_relay:
> t_forward_nonack failed
>
> I am using Openisps version 2.1.1 and using TLS on it
>
>
> Regards
> Feroze
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>

 ___
 Users mailing list
 Users@lists.opensips.org
 http://lists.opensips.org/cgi-bin/mailman/listinfo/users


>>>
>>> ___
>>> Users mailing list
>>> Users@lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>>
>>
>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] TLS - Certificate Validation Failure error on SIP Phones - OpenSIPS version 1.11.5

2016-04-08 Thread Hamid Hashmi

Please define  following valuestls_ca_list = "/path/to/file"
tls_method  = tlsv1for details please consult 
http://www.opensips.org/html/docs/tutorials/tls-1.4.x.html
RegardsHamid R. Hashmi

Date: Thu, 7 Apr 2016 13:14:28 -0400
From: ali...@gmail.com
To: users@lists.opensips.org
Subject: [OpenSIPS-Users] TLS - Certificate Validation Failure error on SIP 
Phones - OpenSIPS version 1.11.5

Hello,
My opensips server is just a registrar server and I have enabled tls with the 
following settings:
listen=tls:xx.xx.xx.xx:5061
disable_tls=notls_certificate="/etc/opensips/pbx-bundle.crt"tls_private_key="/etc/opensips/pbx.key"

When my sip phones try to open tls connection, they reject the connection 
saying "Certificate Validation Failure". My certificate is valid and works fine 
on the https website.
What am I missing? What should I look for?
Regards,Ali Pey

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
  ___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips SIP trunk call handling

2016-04-08 Thread Aqs Younas

You need to manage calls in freeswitch.
On Apr 8, 2016 12:32 PM, "Francjos" <35...@heb.be> wrote:

> Hello,
>
> I wish to configure Opensips that have to act as load balancer to
> freeswitch
> boxes.
> When i directly connect freeswitch to the trunk, incoming calls are managed
> in /usr/local/freeswitch/conf/dialplan/public/ directory. What about if i
> use load balancing? Where do i have to manage incoming (and out ) calls? IN
> Freeswitch or in Opensips?
>
> Thanks
>
>
>
> --
> View this message in context:
> http://opensips-open-sip-server.1449251.n2.nabble.com/Opensips-SIP-trunk-call-handling-tp7602552.html
> Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Opensips SIP trunk call handling

2016-04-08 Thread Francjos

Hello,

I wish to configure Opensips that have to act as load balancer to freeswitch
boxes.
When i directly connect freeswitch to the trunk, incoming calls are managed
in /usr/local/freeswitch/conf/dialplan/public/ directory. What about if i
use load balancing? Where do i have to manage incoming (and out ) calls? IN
Freeswitch or in Opensips?

Thanks



--
View this message in context: 
http://opensips-open-sip-server.1449251.n2.nabble.com/Opensips-SIP-trunk-call-handling-tp7602552.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips Multi instance issue on SIP TLS

2016-04-08 Thread feroze waris

Hi ben

I have checked the traces and you were right that there was transport = tls
in RURI when request forwards from load balancer  to 2 opensips instances .
I have replaced the RURI using rewrite() function and removed the transport
parameter but the issue remains and i am getting the same error


regards
Feroze

On Thu, Apr 7, 2016 at 1:09 PM, Benjamin Cropley  wrote:

> Wild guess here, based on what I've read..
>
> It might be your request URI is explicitly declaring which protocol to
> use, and OpenSIPS has no interface configured for that protocol.. eg.
> ;transport=tls is added to the request URI but there's no listen = tls:
> 1.2.3.4:5061
>
> I know it's tricky to look at a trace for TLS. But have a look at
> http://wiki.snom.com/FAQ/How_to_decode_TLS_calls_using_wireshark
>
> Good luck
> Ben
>
> On Wed, Apr 6, 2016 at 6:24 PM, feroze waris 
> wrote:
>
>> Hi ben
>>
>> yes i am load balancing the Register and Invite request to two proxy
>> servers using dispatcher module but all three servers (i.e load balncer and
>> two opensips servers) are sharing same opensips database.
>> This issue is not occurring in UDP call but on TLS this error occurs.
>>
>> Regards
>> Feroze
>>
>> On Wed, Apr 6, 2016 at 7:34 PM, Benjamin Cropley <
>> benjamin.crop...@gmail.com> wrote:
>>
>>> Feroze,
>>>
>>> Are you load balancing REGISTER *and *INVITE requests to different
>>> nodes?
>>>
>>> If so, then unless you share location information between the
>>> Registrars, then they wont all know where to route INVITEs.
>>>
>>> Ben
>>>
>>>
>>> On Wed, Apr 6, 2016 at 3:20 PM, feroze waris 
>>> wrote:
>>>
 Hello

 I have one load balancer connected to 2 opensips server
 Request is balancing through dispatcher module on load balancer
 the problem is when Register request of B party lands on different
 server than that server at which A Party sends invite request the call
 drops and i am getting following error
 Apr  6 07:58:31 localhost OPENSIP[1793]: ERROR:tm:update_uac_dst:
 failed to fwd to af 2, proto 3  (no corresponding listening socket)
 Apr  6 07:58:31 localhost OPENSIP[1793]: ERROR:tm:t_forward_nonack:
 failure to add branches
 Apr  6 07:58:31 localhost OPENSIP[1793]: ERROR:tm:w_t_relay:
 t_forward_nonack failed

 I am using Openisps version 2.1.1 and using TLS on it


 Regards
 Feroze

 ___
 Users mailing list
 Users@lists.opensips.org
 http://lists.opensips.org/cgi-bin/mailman/listinfo/users


>>>
>>> ___
>>> Users mailing list
>>> Users@lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>>
>>
>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] migration doc missing info

2016-04-08 Thread Pasan Meemaduma

Hi Guys,
I'm migrating my test opensips installation from 2.1 -> 2.2 and found that 
module path being changed in 2.2 as below,
mpath="/usr/lib/opensips/modules/" -> 
mpath="/usr/lib/x86_64-linux-gnu/opensips/modules/"


But this wasn't indicated in the migration docs.

http://www.opensips.org/Documentation/Migration-2-1-0-to-2-2-0

Hope you can fix that, so ppl won't surprise with missing module errors -_-

RegardsPasan
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips SIP trunk call handling

Re: [OpenSIPS-Users] opensips 2.2 dont print anything via rsyslog

Re: [OpenSIPS-Users] Opensips Multi instance issue on SIP TLS

Re: [OpenSIPS-Users] Opensips Multi instance issue on SIP TLS

Re: [OpenSIPS-Users] opensips 2.2 dont print anything via rsyslog

Re: [OpenSIPS-Users] opensips 2.2 dont print anything via rsyslog

Re: [OpenSIPS-Users] TLS - Certificate Validation Failure error on SIP Phones - OpenSIPS version 1.11.5

Re: [OpenSIPS-Users] Opensips Multi instance issue on SIP TLS

Re: [OpenSIPS-Users] Opensips Multi instance issue on SIP TLS

[OpenSIPS-Users] Should I worry about INFO "no free tcp receiver"?

Re: [OpenSIPS-Users] Opensips Multi instance issue on SIP TLS

Re: [OpenSIPS-Users] Opensips SIP trunk call handling

Re: [OpenSIPS-Users] TLS - Certificate Validation Failure error on SIP Phones - OpenSIPS version 1.11.5

Re: [OpenSIPS-Users] Opensips SIP trunk call handling

Re: [OpenSIPS-Users] Opensips SIP trunk call handling

Re: [OpenSIPS-Users] Opensips SIP trunk call handling

Re: [OpenSIPS-Users] Opensips SIP trunk call handling

Re: [OpenSIPS-Users] Opensips SIP trunk call handling

Re: [OpenSIPS-Users] Opensips Multi instance issue on SIP TLS

Re: [OpenSIPS-Users] TLS - Certificate Validation Failure error on SIP Phones - OpenSIPS version 1.11.5

Re: [OpenSIPS-Users] Opensips SIP trunk call handling

[OpenSIPS-Users] Opensips SIP trunk call handling

Re: [OpenSIPS-Users] Opensips Multi instance issue on SIP TLS

[OpenSIPS-Users] migration doc missing info

24 matches

Site Navigation

Mail list logo

Footer information