Re: [OpenSIPS-Users] port number in record-route

2017-03-31 Thread Aqs Younas
Nope, this is if you want to manually write the complete record route
header, instead of calling record_route().
On Sat, Apr 1, 2017 at 12:52 AM Satish Patel  wrote:

> Does this work if i use record_route_preset without PORT number
> specify and let SER decide which is the best port to use?
>
> something like this, without PORT specify
>
>
> record_route_preset("62.32.212.10;nat=yes");
>
>
>
> On Fri, Mar 31, 2017 at 4:00 AM, Aqs Younas  wrote:
> > This might help you.
> > http://www.opensips.org/html/docs/modules/2.2.x/rr.html#id293864
> >
> > On 31 March 2017 at 06:31, Satish Patel  wrote:
> >>
> >> is there a way i can re-write record-route port number?
> >>
> >> On Wed, Mar 29, 2017 at 6:29 PM, Alex Balashov
> >>  wrote:
> >> > Record-Route headers contain URIs, and like any SIP URI, they can
> >> > contain a port component. If that port component is omitted, 5060 is
> >> > presumed.
> >> >
> >> > On March 29, 2017 6:27:30 PM EDT, Satish Patel 
> >> > wrote:
> >> >>what is the use of port number in record-route?
> >> >>
> >> >>I am having major issue with that look like we are running sip server
> >> >>on different port to protect ourself from sip scanner we are using
> >> >>non-standard port like 6060/7070 multiple port on single server so it
> >> >>will failover to other port if firewall block them.
> >> >>
> >> >>I am seeing record-route adding first port in listen: directive for
> >> >>example
> >> >>
> >> >>listen=udp:x.x.x.x:7070 udp:x.x.x.x:7070 udp:x.x.x.x:5062
> >> >>
> >> >>In this case my record-route always using 7070 in header default
> >> >>recordless request coming on 5062.
> >> >>
> >> >>I found one more issue here someone posted while ago
> >> >>
> >>
> >> >> >>
> https://lists.cs.columbia.edu/pipermail/sip-implementors/2001-March/000601.html
> >> >>
> >> >>___
> >> >>Users mailing list
> >> >>Users@lists.opensips.org
> >> >>http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >> >
> >> >
> >> > -- Alex
> >> >
> >> > --
> >> > Principal, Evariste Systems LLC (www.evaristesys.com)
> >> >
> >> > Sent from my Google Nexus.
> >> >
> >> > ___
> >> > 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] port number in record-route

2017-03-31 Thread Satish Patel
Does this work if i use record_route_preset without PORT number
specify and let SER decide which is the best port to use?

something like this, without PORT specify


record_route_preset("62.32.212.10;nat=yes");



On Fri, Mar 31, 2017 at 4:00 AM, Aqs Younas  wrote:
> This might help you.
> http://www.opensips.org/html/docs/modules/2.2.x/rr.html#id293864
>
> On 31 March 2017 at 06:31, Satish Patel  wrote:
>>
>> is there a way i can re-write record-route port number?
>>
>> On Wed, Mar 29, 2017 at 6:29 PM, Alex Balashov
>>  wrote:
>> > Record-Route headers contain URIs, and like any SIP URI, they can
>> > contain a port component. If that port component is omitted, 5060 is
>> > presumed.
>> >
>> > On March 29, 2017 6:27:30 PM EDT, Satish Patel 
>> > wrote:
>> >>what is the use of port number in record-route?
>> >>
>> >>I am having major issue with that look like we are running sip server
>> >>on different port to protect ourself from sip scanner we are using
>> >>non-standard port like 6060/7070 multiple port on single server so it
>> >>will failover to other port if firewall block them.
>> >>
>> >>I am seeing record-route adding first port in listen: directive for
>> >>example
>> >>
>> >>listen=udp:x.x.x.x:7070 udp:x.x.x.x:7070 udp:x.x.x.x:5062
>> >>
>> >>In this case my record-route always using 7070 in header default
>> >>recordless request coming on 5062.
>> >>
>> >>I found one more issue here someone posted while ago
>> >>
>>
>> >> >>https://lists.cs.columbia.edu/pipermail/sip-implementors/2001-March/000601.html
>> >>
>> >>___
>> >>Users mailing list
>> >>Users@lists.opensips.org
>> >>http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>> >
>> >
>> > -- Alex
>> >
>> > --
>> > Principal, Evariste Systems LLC (www.evaristesys.com)
>> >
>> > Sent from my Google Nexus.
>> >
>> > ___
>> > 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] MediaProxy Got traffic information for stream

2017-03-31 Thread Andreas Bøckmann
Hello,

I am hoping somebody can explain to me how MediaProxy receives "traffic
information" from OpenSIPS.

I am trying to use two different GWs to reach PSTN but I am experiencing
no-audio using one of them and the only thing I can see that is different
is in MediaProxy logs.
.
The call flow is similar (late offer).

--> INVITE
<- 183/180
<-  200 OK SDP
--> ACK SDP

Got traffic information for stream: (audio) Unknown (RTP: 1.2.3.4:10002,
RTCP: Unknown) <-> 2.3.4.5:16388 <-> 2.3.4.5:16390 <-> 4.5.6.7:11390 (RTP:
4.5.6.7:11390, RTCP: 4.5.6.7:11391)

Got traffic information for stream: (audio) Unknown (RTP: 1.2.3.4:1,
RTCP: Unknown) <-> 2.3.4.5:16384 <-> 2.3.4.5:16386 <-> 3.4.5.6:22458 (RTP:
Unknown, RTCP: Unknown)

As I see this MediaProxy has all 3 relevant IPs in both cases; but it's not
set in "RTP:" for the call which does not have audio so I am wondering how
this can be?

What's the missing piece here so that MediaProxy knows "3.4.5.6" is "RTP:" ?


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


Re: [OpenSIPS-Users] unixodbc connection problem - gnutls /dev/urandom error

2017-03-31 Thread Jeff Pyle
Of course after playing with this for 2 days I find the solution right after I 
post to the list.

It was a tds_version issue.  For whatever reason FreeTDS configured with 
versions 7.1 and 7.2 don't connect from OpenSIPS, but they do from isql.  4.2, 
7.3 and 7.4 work fine from both.  In my case it's to a MS SQL Server 2014 so 
7.4 appropriate.  The 
default tds_version is 8.0, an alias for 7.1, so that's why the default didn't 
work.



- Jeff



From: Users [users-boun...@lists.opensips.org] on behalf of Jeff Pyle
Sent: Friday, March 31, 2017 09:29
To: users@lists.opensips.org
Subject: [OpenSIPS-Users] unixodbc connection problem - gnutls /dev/urandom 
error

Hello,

I'm trying to connect OpenSIPS 2.2.3 to a MS SQL database for avpops through 
unixodbc + freetds on Debian 8.  I see the following OpenSIPS errors:

DBG:db_unixodbc:db_unixodbc_new_connection: opening connection: 
unixodbc://:@localhost/SQLMaster
ERROR:db_unixodbc:db_unixodbc_new_connection: failed to connect
ERROR:db_unixodbc:db_unixodbc_extract_error: 
unixodbc:SQLDriverConnect=08001:1:0:[unixODBC][FreeTDS][SQL Server]Unable to 
connect to data source
ERROR:db_unixodbc:db_unixodbc_extract_error: 
unixodbc:SQLDriverConnect=01000:2:20002:[unixODBC][FreeTDS][SQL Server]Adaptive 
Server connection failed

This only occurs within OpenSIPS.  Testing on isql with the same credentials 
and DSN works fine.

FreeTDS gives the following logs:

login.c:1057:detected flag 0
net.c:1259:GNUTLS: level 5:
  REC[0x21569b0]: Allocating epoch #0
net.c:1259:GNUTLS: level 3:
  ASSERT: gnutls_constate.c:586
net.c:1259:GNUTLS: level 5:
  REC[0x21569b0]: Allocating epoch #1
net.c:1259:GNUTLS: level 2:
  Failed to read /dev/urandom: Bad file descriptor
net.c:1259:GNUTLS: level 3:
  ASSERT: rnd.c:174
net.c:1259:GNUTLS: level 3:
  ASSERT: rnd.c:291
...and so on.

/dev/urandom is present, has crw-rw-rw- permissions, and works properly 
according to rngtest from rng-tools.

I've seen some posts indicating this may be a gnutls bug and recompiling 
freetds with openssl is required.  I tried that - no change.

Since this only occurs within OpenSIPS I thought I'd pose the question here.  
Any insight is greatly appreciated.



- Jeff

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


[OpenSIPS-Users] unixodbc connection problem - gnutls /dev/urandom error

2017-03-31 Thread Jeff Pyle
Hello,

I'm trying to connect OpenSIPS 2.2.3 to a MS SQL database for avpops through 
unixodbc + freetds on Debian 8.  I see the following OpenSIPS errors:

DBG:db_unixodbc:db_unixodbc_new_connection: opening connection: 
unixodbc://:@localhost/SQLMaster
ERROR:db_unixodbc:db_unixodbc_new_connection: failed to connect
ERROR:db_unixodbc:db_unixodbc_extract_error: 
unixodbc:SQLDriverConnect=08001:1:0:[unixODBC][FreeTDS][SQL Server]Unable to 
connect to data source
ERROR:db_unixodbc:db_unixodbc_extract_error: 
unixodbc:SQLDriverConnect=01000:2:20002:[unixODBC][FreeTDS][SQL Server]Adaptive 
Server connection failed

This only occurs within OpenSIPS.  Testing on isql with the same credentials 
and DSN works fine.

FreeTDS gives the following logs:

login.c:1057:detected flag 0
net.c:1259:GNUTLS: level 5:
  REC[0x21569b0]: Allocating epoch #0
net.c:1259:GNUTLS: level 3:
  ASSERT: gnutls_constate.c:586
net.c:1259:GNUTLS: level 5:
  REC[0x21569b0]: Allocating epoch #1
net.c:1259:GNUTLS: level 2:
  Failed to read /dev/urandom: Bad file descriptor
net.c:1259:GNUTLS: level 3:
  ASSERT: rnd.c:174
net.c:1259:GNUTLS: level 3:
  ASSERT: rnd.c:291
...and so on.

/dev/urandom is present, has crw-rw-rw- permissions, and works properly 
according to rngtest from rng-tools.

I've seen some posts indicating this may be a gnutls bug and recompiling 
freetds with openssl is required.  I tried that - no change.

Since this only occurs within OpenSIPS I thought I'd pose the question here.  
Any insight is greatly appreciated.



- Jeff

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


[OpenSIPS-Users] opensips-1.11 storing data in memory issue .

2017-03-31 Thread Sasmita Panda
Hi  All ,

I am using opensips-1.11 from long time . But today i faced some issue .
when a username det rigistered , it givind some error in the logs like
bellow .

*CRITICAL:usrloc:preload_udomain: empty domain for user ...skipping *

*I am getting that entry in the DB but I am not getting anything in the
memory . Every call to this number failing with error 404 Not found .*


*loadmodule "usrloc.so"*
*modparam("usrloc", "db_url", "mysql://:@localhost/opensips")*
*modparam("usrloc", "db_mode", 1)*

*Other default modules are loaded also . It not giving any error when
starting . But while register its throughing such error . *

*  What the problem i am not getting it . This is happening in one
machine . In other machine the same config with same code is runnign fine .*

*Please help me if I am doing anything wrong .*

*Thanks & Regards*
*Sasmita Panda*
*Network Testing and Software Engineer*
*3CLogic , ph:07827611765*
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] port number in record-route

2017-03-31 Thread Aqs Younas
This might help you.
http://www.opensips.org/html/docs/modules/2.2.x/rr.html#id293864

On 31 March 2017 at 06:31, Satish Patel  wrote:

> is there a way i can re-write record-route port number?
>
> On Wed, Mar 29, 2017 at 6:29 PM, Alex Balashov
>  wrote:
> > Record-Route headers contain URIs, and like any SIP URI, they can
> contain a port component. If that port component is omitted, 5060 is
> presumed.
> >
> > On March 29, 2017 6:27:30 PM EDT, Satish Patel 
> wrote:
> >>what is the use of port number in record-route?
> >>
> >>I am having major issue with that look like we are running sip server
> >>on different port to protect ourself from sip scanner we are using
> >>non-standard port like 6060/7070 multiple port on single server so it
> >>will failover to other port if firewall block them.
> >>
> >>I am seeing record-route adding first port in listen: directive for
> >>example
> >>
> >>listen=udp:x.x.x.x:7070 udp:x.x.x.x:7070 udp:x.x.x.x:5062
> >>
> >>In this case my record-route always using 7070 in header default
> >>recordless request coming on 5062.
> >>
> >>I found one more issue here someone posted while ago
> >>
> >>https://lists.cs.columbia.edu/pipermail/sip-implementors/2001-March/
> 000601.html
> >>
> >>___
> >>Users mailing list
> >>Users@lists.opensips.org
> >>http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
> >
> > -- Alex
> >
> > --
> > Principal, Evariste Systems LLC (www.evaristesys.com)
> >
> > Sent from my Google Nexus.
> >
> > ___
> > 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