Re: [OpenSIPS-Users] Using Redis as database for uac_registrant module

2015-09-10 Thread Sasmita Panda
Bogdan-Andrei Iancu writes: > > First I missed the PS :). > > Thanks for that, I will keep an eye on the osipsdagram to see how it goes ! > > Regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > http://www.opensips-solutions.com > > On 10.07.2014 12:59, Dan Christian Bogos w

[OpenSIPS-Users] How to get the line number in script

2015-09-10 Thread Podrigal, Aron
Hi, Is there a way to get the line number within the opensips script. I want to use that in xlog statements and in replies. Thanks -- Aron Podrigal - '101', '1110010', '110', '1101110' '101', '110', '1100100', '1110010', '1101001', '1100111', '111', '1101100' P: '2b', '31

[OpenSIPS-Users] Regarding db_cachedb and cachedb_redis integration with opensips .

2015-09-10 Thread Sasmita Panda
Hi All , I am trying to compile openisps-1.11 with db_cachedb and cachedb_redis module . I wanted to use this for auth, userloc,drouting,dialog etc . I have tried this with auth_db . bellow is the example . loadmodule "auth_db.so" modparam("auth_db", "load_credentials", "$avp(user_rp

[OpenSIPS-Users] TLS tcp_blocking_connect errors

2015-09-10 Thread Matt Hamilton
In one of our calling scenarios, INVITEs are sent via TLS to multiple UACs in an office (all ring, one picks up). The UACs are not NATed. Once in a while, we get tcp_connect error from one of the phones. None of the tcp related parameters (e.g. tcp_connection_lifetime, etc.) are set in our scri

[OpenSIPS-Users] Migrating from RTPProxy to MediaProxy

2015-09-10 Thread Terrance Devor
Hello Everyone, Our current NAT'ed environment is as follows Internet <---> Cisco Green Box <-> OpenSIPS (192.168.2.2) <-> RTPProxy (192.168.2.5) I think this is called far end nat? Anyhow, it works perfectly fine (ie, flows m

[OpenSIPS-Users] Logic behind check of current_turn in presence module?

2015-09-10 Thread surya
Hi All, Here I am referring opensips1.8.4 I am not able to understand the use of current_turn and last_turn variables in update_presentity function. As I understand: For initial request current_turn=0 and last_turn=0 and for subsequent requests where etag matches and found in hash, each will