Re: [OpenSIPS-Users] - INVITE (SDP) includes Originators IP info

[Abdul Basit]

Nitesh,

You need a B2BUA function
<https://www.tutorialspoint.com/session_initiation_protocol/session_initiation_protocol_b2bua.htm>
with
the help of a topo-hiding module with opensips as Bela shared in his email.
Also, install the RTP proxy on the same opensips box (not necessary if you
need separate signaling and media boxes).

Far end party will not be able to see the A-party information.

https://www.opensips.org/Documentation/Tutorials-B2BUA-3-2

I hope this will help.

--
regards,

abdul basit

On Wed, 19 Oct 2022 at 03:14, Bela H  wrote:

> Hi Nitesh,
>
>
>
>1. Check the topology hiding function:
>https://opensips.org/docs/modules/3.2.x/topology_hiding.html
>2. Use e.g. rtpproxy:
>
> https://opensips.org/docs/modules/3.2.x/rtpproxy.html#func_rtpproxy_offer
>
>
> http://opensips.com.br/wiki/index.php?title=Oopensips_Nat_script_with_RTPPROXY_-_English
>
> https://github.com/sippy/rtpproxy
>
>
>
> I hope these help!
>
>
>
> Cheers,
>
> Bela
>
>
>
> *From: *Nitesh Divecha 
> *Sent: *Wednesday, 19 October 2022 04:26
> *To: *OpenSIPS users mailling list 
> *Subject: *[OpenSIPS-Users] - INVITE (SDP) includes Originators IP info
>
>
>
> Hello All,
>
>
>
> This is my first OpenSIPS project so I'm a newbie!
>
>
>
> After going back and forth with "uac_replace_from()", I was successfully
> able to make a call from my ATA -> OpenSIPS -> Outbound Provider ->
> CellPhone. All worked fine with two-way audio except few issues:
>
>
>
> 1) Outbound Provider was able to see my ATA (Originator's
> IP/User-Agent/etc) in SIP INVITE (SDP) which kinda raised some eyebrows
> with Outbound provider. How can I block or strip all the Originator's
> contact info in SIP INVITE (SDP) and only send OpenSIPS info? Meaning I
> want to protect my Originators and don't want to show anything to the
> Outbound Provider. Outbound providers should only communicate to the
> OpenSIPS server.
>
>
>
> 2) When the call was up I failed to capture any media/RTP on the OpenSIPS
> server. I want to involve OpenSIPS in media/RTP between ATA and outbound
> providers. How can I force media/RTP to pass-thru OpenSIPS IP so I'm not
> exposing Originator's IP.
>
>
>
> Any insights will be highly appreciated.
>
>
>
> Cheers,
>
> Nitesh
>
>
> ___
> 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-Business] [Release] OpenSIPS 3.0.0 release becomes stable

[Abdul Basit]

Congratulations!!!

--
regards,

abdul basit | p: +92 32 1416 4196 | o: +92 30 0841 1445


On Mon, 23 Sep 2019 at 13:34, Brett Nemeroff  wrote:

> Great News Bogdan and Team! What an amazing accomplishment! Looking
> forward to seeing how OpenSIPs develops going forward from this milestone!
>
> -Brett
>
>
> On Wed, May 29, 2019 at 11:35 AM Bogdan-Andrei Iancu 
> wrote:
>
>> Hi everyone !
>>
>> One and half month of testing, reporting, debugging, fixing and
>> re-testing - what was the result?
>>
>> The OpenSIPS 3.0 stable version is now ready.
>>
>> It was a tremendous collective effort to make this important step from
>> beta to stable release - and this would not have been possible without
>> the help of you, of the OpenSIPS community - people involved in testing,
>> people contributing with fixes, people doing reports, people making
>> OpenSIPS even a greater software.
>>
>> Now, it is the time to sit, sip and relax :)
>>
>> and Enjoy 3.0!
>>
>> --
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>https://www.opensips-solutions.com
>> OpenSIPS Summit 2019
>>https://www.opensips.org/events/Summit-2019Amsterdam/
>>
>>
>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
> ___
> Business mailing list
> busin...@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/business
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] [OpenSIPS-Business] [Release] OpenSIPS 3.0.0 release becomes stable

[Abdul Basit]

Appreciated and Congratulations to the community for achieving new
milestone.

--
regards,

abdul basit


On Wed, 29 May 2019 at 21:34, Bogdan-Andrei Iancu 
wrote:

> Hi everyone !
>
> One and half month of testing, reporting, debugging, fixing and
> re-testing - what was the result?
>
> The OpenSIPS 3.0 stable version is now ready.
>
> It was a tremendous collective effort to make this important step from
> beta to stable release - and this would not have been possible without
> the help of you, of the OpenSIPS community - people involved in testing,
> people contributing with fixes, people doing reports, people making
> OpenSIPS even a greater software.
>
> Now, it is the time to sit, sip and relax :)
>
> and Enjoy 3.0!
>
> --
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>https://www.opensips-solutions.com
> OpenSIPS Summit 2019
>https://www.opensips.org/events/Summit-2019Amsterdam/
>
>
> ___
> Business mailing list
> busin...@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/business
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] [NEW] Gateway between SIP and SMPP messages

[Abdul Basit]

nice addition as this will eliminate the kannel integration logic along
side with SIP services.

How to handle message max. characters length while transmitting the message
over SMPP and concatenation on receiving message from SMSC?
Is this implementation address multilingual support, i.e Unicode support?

--
regards,

abdul basit

On Fri, 25 Jan 2019 at 20:51, Liviu Chircu  wrote:

> OpenSIPS GitHub [1] will build it on Sunday :)
>
> [1]: https://github.com/opensips-github
>
> Liviu Chircu
> OpenSIPS Developerhttp://www.opensips-solutions.com
>
> On 25.01.2019 17:46, Slava Bendersky wrote:
>
> Hello Răzvan,
>
> proto_smpp missing README in main tree  or just wasn't generated ?
>
> volga629
>
> --
> *From: *"Răzvan Crainea"  
> *To: *"OpenSIPS users mailling list" 
> 
> *Sent: *Friday, January 25, 2019 4:34:38 AM
> *Subject: *Re: [OpenSIPS-Users] [NEW] Gateway between SIP and SMPP
> messages
>
> Unfortunately this is a feature, not a bug, so it won't be backported to
> 2.4.
>
> Cheers,
> Răzvan
>
> On 1/24/19 7:21 PM, johan de clercq wrote:
> > Do you backport this to 2.4 ?
> >
> > BR,
> >
> > -Original Message-
> > From: Users 
>  On Behalf Of Razvan Crainea
> > Sent: Thursday, January 24, 2019 5:37 PM
> > To: OpenSIPS users mailling list 
> ; OpenSIPS devel mailling list
>  
> > Subject: [OpenSIPS-Users] [NEW] Gateway between SIP and SMPP messages
> >
> > Hi, Everyone!
> >
> > Check out the latest OpenSIPS module, proto_smpp[1], that you can use to
> create a two-way bridge between SIP and SMPP text messages. Read more about
> this on our blog[2].
> >
> > [1] https://opensips.org/html/docs/modules/3.0.x/proto_smpp.html
> > [2]
> >
> https://blog.opensips.org/2019/01/24/gateway-between-sip-and-smpp-messages/
> >
> > Cheers,
> > --
> > Răzvan Crainea
> > OpenSIPS Core Developer
> > http://www.opensips-solutions.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
> >
>
> --
> Răzvan Crainea
> OpenSIPS Core Developer
>http://www.opensips-solutions.com
> Meet the OpenSIPS team at the next OpenSIPS Summit:
>https://www.opensips.org/events
>
> ___
> 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
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] opensips will not start while loading huge blacklist

[Abdul Basit]

Yes. I understand and I check that point specifically.
Thank you for your quick solution.

--
regards,

abdul basit


On Wed, 3 Oct 2018 at 00:37, Bogdan-Andrei Iancu 
wrote:

> Hi Abdul,
>
> Thanks for the feedback. I just want to be sure you understand that the
> change I did does not speed up the loading process, but it simply decouples
> the startup sequence from the data loading process. Shortly OpenSIPS does
> not have to wait for the DB data to be loaded in order to start up.
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   http://www.opensips-solutions.com
> OpenSIPS Bootcamp 2018
>   http://opensips.org/training/OpenSIPS_Bootcamp_2018/
>
> On 10/02/2018 07:22 PM, Abdul Basit wrote:
>
> Thanks a lot.
> Earlier status
> Opensips service was started in *(real 1m6.474s)*
>
> # time opensipsctl fifo reload_blacklist
> WARNING: database engine not found - tried 'MYSQL'
>
> real0m3.948s
> user0m0.039s
> sys 0m0.013s
>
> time systemctl stop opensips
>
> real0m1.424s
> user0m0.004s
> sys 0m0.000s
>
> *I pulled source from master.*
>
> # time systemctl start opensips
> Oct  2 15:57:41 srouter-215 systemd[1]: Starting OpenSIPS is a very fast
> and flexible SIP (RFC3261) server...
> Oct  2 15:57:41 srouter-215 opensips[15906]: Listening on
> Oct  2 15:57:41 srouter-215 opensips[15906]: udp: x.x.x.x [x.x.x.x]:9020
> Oct  2 15:57:41 srouter-215 opensips[15906]: udp:
> x6:x6:x6:x6:x6:x6 [[x6:x6:0:0:x6:x6:x6:x6]]:9020
> Oct  2 15:57:41 srouter-215 opensips[15906]: Aliases:
> Oct  2 15:57:41 srouter-215 opensips[15906]: *: x.x.x.x:*
>
> real0m0.066s
> user0m0.003s
> sys 0m0.002s
> root@srouter-215:~# Oct  2 15:57:41 srouter-215 systemd[1]: Started
> OpenSIPS is a very fast and flexible SIP (RFC3261) server.
>
> /var/log/opensips.log is here ... https://pastebin.com/8md6sBiP
>
> # time opensipsctl fifo reload_blacklist
> WARNING: database engine not found - tried 'MYSQL'
> Oct  2 16:17:24 srouter-215 SIPSrv[16185]:
> INFO:userblacklist:reload_sources: got 1386901 entries from
> 'globalblacklist'
>
> real0m41.551s
> user0m0.037s
> sys 0m0.015s
>
> # time systemctl stop opensips
> Oct  2 16:06:38 srouter-215 systemd[1]: Stopping OpenSIPS is a very fast
> and flexible SIP (RFC3261) server...
> Oct  2 16:06:50 srouter-215 systemd[1]: Stopped OpenSIPS is a very fast
> and flexible SIP (RFC3261) server.
>
> real0m12.134s
> user0m0.003s
> sys 0m0.002s
>
>
> Looks like issue has been fixed.. :)
>
> --
> regards,
>
> abdul basit
>
>
> On Tue, 2 Oct 2018 at 18:55, Bogdan-Andrei Iancu 
> wrote:
>
>> OK, I pushed on master a patch to move the initial data load after the
>> startup sequence. The patch should apply to 2.4 also.
>>
>>
>> https://github.com/OpenSIPS/opensips/commit/32cba1d751ee5a5b705da97ac4333fcad3d67728
>>
>> While checking the module, I found some issues with it:
>>
>> * before my patch, the load (for same data) was independently done in
>> each opensips process (even if the data is shared) :)
>>
>> * the "reload" is no error pron - if the new data load fails, the old
>> existing data is lost
>>
>> * during the data reload the module has no data, so it cannot operate
>> (it will actually block) - normally it should continue with the old data
>> until the new data is fully loaded and validated.
>>
>> Let me know if the patch makes a different for you and I will backport it
>> to 2.4 too.
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>   http://www.opensips-solutions.com
>> OpenSIPS Bootcamp 2018
>>   http://opensips.org/training/OpenSIPS_Bootcamp_2018/
>>
>> On 10/02/2018 04:18 PM, Bogdan-Andrei Iancu wrote:
>>
>> Hi,
>>
>> Taking a closer look at the module (to be honest I do not user it, as
>> drouting does a similar job) I see the module is loading the data into
>> memory. It is doing this during the init stage, holding back the entire
>> OpenSIPS startup.
>> Module doing similar heavy db load were changed to do the load
>> post-startup. Let patch the module to decouple the loading from the
>> startup, so that OpenSIPS will start without delays.
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>   http://www.opensips-solutions.com
>> OpenSIPS Bootcamp 2018
>>   http://opensips.org/training/OpenSIPS_Bootcamp_2018/
>>
>> On 10/02/2018 04:04 PM, Jon Abrams wrote:

Re: [OpenSIPS-Users] opensips will not start while loading huge blacklist

[Abdul Basit]

Thanks a lot.
Earlier status
Opensips service was started in *(real 1m6.474s)*

# time opensipsctl fifo reload_blacklist
WARNING: database engine not found - tried 'MYSQL'

real0m3.948s
user0m0.039s
sys 0m0.013s

time systemctl stop opensips

real0m1.424s
user0m0.004s
sys 0m0.000s

*I pulled source from master.*

# time systemctl start opensips
Oct  2 15:57:41 srouter-215 systemd[1]: Starting OpenSIPS is a very fast
and flexible SIP (RFC3261) server...
Oct  2 15:57:41 srouter-215 opensips[15906]: Listening on
Oct  2 15:57:41 srouter-215 opensips[15906]: udp: x.x.x.x [x.x.x.x]:9020
Oct  2 15:57:41 srouter-215 opensips[15906]: udp:
x6:x6:x6:x6:x6:x6 [[x6:x6:0:0:x6:x6:x6:x6]]:9020
Oct  2 15:57:41 srouter-215 opensips[15906]: Aliases:
Oct  2 15:57:41 srouter-215 opensips[15906]: *: x.x.x.x:*

real0m0.066s
user0m0.003s
sys 0m0.002s
root@srouter-215:~# Oct  2 15:57:41 srouter-215 systemd[1]: Started
OpenSIPS is a very fast and flexible SIP (RFC3261) server.

/var/log/opensips.log is here ... https://pastebin.com/8md6sBiP

# time opensipsctl fifo reload_blacklist
WARNING: database engine not found - tried 'MYSQL'
Oct  2 16:17:24 srouter-215 SIPSrv[16185]:
INFO:userblacklist:reload_sources: got 1386901 entries from
'globalblacklist'

real0m41.551s
user0m0.037s
sys 0m0.015s

# time systemctl stop opensips
Oct  2 16:06:38 srouter-215 systemd[1]: Stopping OpenSIPS is a very fast and
flexible SIP (RFC3261) server...
Oct  2 16:06:50 srouter-215 systemd[1]: Stopped OpenSIPS is a very fast and
flexible SIP (RFC3261) server.

real0m12.134s
user0m0.003s
sys 0m0.002s


Looks like issue has been fixed.. :)

--
regards,

abdul basit


On Tue, 2 Oct 2018 at 18:55, Bogdan-Andrei Iancu 
wrote:

> OK, I pushed on master a patch to move the initial data load after the
> startup sequence. The patch should apply to 2.4 also.
>
>
> https://github.com/OpenSIPS/opensips/commit/32cba1d751ee5a5b705da97ac4333fcad3d67728
>
> While checking the module, I found some issues with it:
>
> * before my patch, the load (for same data) was independently done in
> each opensips process (even if the data is shared) :)
>
> * the "reload" is no error pron - if the new data load fails, the old
> existing data is lost
>
> * during the data reload the module has no data, so it cannot operate
> (it will actually block) - normally it should continue with the old data
> until the new data is fully loaded and validated.
>
> Let me know if the patch makes a different for you and I will backport it
> to 2.4 too.
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   http://www.opensips-solutions.com
> OpenSIPS Bootcamp 2018
>   http://opensips.org/training/OpenSIPS_Bootcamp_2018/
>
> On 10/02/2018 04:18 PM, Bogdan-Andrei Iancu wrote:
>
> Hi,
>
> Taking a closer look at the module (to be honest I do not user it, as
> drouting does a similar job) I see the module is loading the data into
> memory. It is doing this during the init stage, holding back the entire
> OpenSIPS startup.
> Module doing similar heavy db load were changed to do the load
> post-startup. Let patch the module to decouple the loading from the
> startup, so that OpenSIPS will start without delays.
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   http://www.opensips-solutions.com
> OpenSIPS Bootcamp 2018
>   http://opensips.org/training/OpenSIPS_Bootcamp_2018/
>
> On 10/02/2018 04:04 PM, Jon Abrams wrote:
>
> OpenSIPs is loading the global blacklist into a digit trie structure into
> shared memory on startup (or reload_blacklist command). That causes the
> startup delay.
>
> - Jon
>
> On Tue, Oct 2, 2018 at 7:55 AM Abdul Basit  wrote:
>
>> Hi Bogdan,
>>
>> I don't think so its translating to DB query on run time, instead its
>> caching the blacklist.
>> I am saying so because opensips response is quick, where as when I query
>> manually from DB, it take some time even prefix col. is indexed.
>> Moreover, while opensips restart i get following warnings in syslog:
>>
>>
>>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] opensips will not start while loading huge blacklist

[Abdul Basit]

Hi Bogdan,

I don't think so its translating to DB query on run time, instead its
caching the blacklist.
I am saying so because opensips response is quick, where as when I query
manually from DB, it take some time even prefix col. is indexed.
Moreover, while opensips restart i get following warnings in syslog:

Oct  2 12:35:28 srouter-215 SIPSrv[20876]: WARNING:core:timer_ticker: timer
task  already scheduled for 990 ms (now 17920 ms), it may
overlap..
Oct  2 12:35:28 srouter-215 SIPSrv[20876]: WARNING:core:timer_ticker: timer
task  already scheduled for 990 ms (now 17920 ms), it
may overlap..
Oct  2 12:35:28 srouter-215 SIPSrv[20876]: WARNING:core:timer_ticker: timer
task  already scheduled for 990 ms (now 17920 ms), it
may overlap..
Oct  2 12:35:28 srouter-215 SIPSrv[20876]: WARNING:core:timer_ticker: timer
task  already scheduled for 990 ms (now 17920 ms), it may
overlap..
Oct  2 12:35:28 srouter-215 SIPSrv[20876]: WARNING:core:timer_ticker: timer
task  already scheduled for 990 ms (now 17920 ms), it may
overlap..
Oct  2 12:35:28 srouter-215 SIPSrv[20876]: WARNING:core:timer_ticker: timer
task  already scheduled for 990 ms (now 17920 ms), it may
overlap..
Oct  2 12:35:28 srouter-215 SIPSrv[20876]: WARNING:core:utimer_ticker:
utimer task  already scheduled for 100 ms (now 18020 ms), it may
overlap..
Oct  2 12:35:28 srouter-215 SIPSrv[20876]: WARNING:core:utimer_ticker:
utimer task  already scheduled for 100 ms (now 18120 ms), it may
overlap..
Oct  2 12:35:28 srouter-215 SIPSrv[20876]: WARNING:core:utimer_ticker:
utimer task  already scheduled for 100 ms (now 18220 ms), it may
overlap..
*Oct  2 12:35:28 srouter-215 SIPSrv[20882]:
INFO:userblacklist:reload_sources: got 1386901 entries from
'globalblacklist' *
Oct  2 12:35:28 srouter-215 SIPSrv[20882]: WARNING:core:handle_timer_job:
utimer job  has a 1817 us delay in execution
Oct  2 12:35:28 srouter-215 SIPSrv[20882]: WARNING:core:handle_timer_job:
timer job  has a 1728 us delay in execution
Oct  2 12:35:28 srouter-215 SIPSrv[20882]: WARNING:core:handle_timer_job:
timer job  has a 1728 us delay in execution

Once globalblacklist loaded *1386901 entries* , opensips behave normally.
When I will add more records to globalblacklist, opensips wouldn't start
due to service timeout.
One way might be to increase service timeout to allow opensips keep loading
the entries but it may take ages.

--
regards,

abdul basit

On Tue, 2 Oct 2018 at 13:19, Bogdan-Andrei Iancu 
wrote:

> Hi Abdul,
>
> OK, but what is the blacklist related operation you do in startup route ??
> As far as I know, the blacklist module is not doing any kind of caching, so
> any check you do against the blacklists will translate into a DB query,
> right ?
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   http://www.opensips-solutions.com
> OpenSIPS Bootcamp 2018
>   http://opensips.org/training/OpenSIPS_Bootcamp_2018/
>
> On 10/01/2018 06:58 PM, Abdul Basit wrote:
>
> Yes. That's right.
> The code I am using is as below. globalblacklist table has complete
> number as prefix with and whitelist status.
>
> route {
> .
> if ( !check_blacklist("globalblacklist") ) {
> xlog("L_NOTICE","[$fU/$tU/$ci] [$rm] Destination [$rU] is not Allowed.
> Dropping call.\n");
> sl_send_reply("403", "Forbidden");
> exit;
> }
> else {
> xlog("L_INFO", "[$fU/$tU/$ci] [$rm] INBOUND CALL for [$ru]");
> route(10);
> exit;
> }
> .
> }
>
>
> --
> regards,
>
> abdul basit
>
>
> On Mon, 1 Oct 2018 at 19:07, Bogdan-Andrei Iancu 
> wrote:
>
>> Hi Abdul,
>>
>> IF I understand correctly, you use startup route to load (from DB?) some
>> blacklists into localcache ?
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>   http://www.opensips-solutions.com
>> OpenSIPS Bootcamp 2018
>>   http://opensips.org/training/OpenSIPS_Bootcamp_2018/
>>
>> On 09/28/2018 04:10 AM, Abdul Basit wrote:
>>
>> Hi team,
>>
>> I have a opensips 2.4 deployed having 4 children and with mysql
>> configured for loading user blacklist to opensips local cache on opensips
>> startup.
>> Opensips work fine on filtering the call based on user blacklist records
>> loaded into local cache.
>>
>> While blacklist was growing upto 1.3m records, opensips startup was
>> taking ~60 sec on VM of 16GB RAM and 6 CPU.
>> I increased shared memory to *6144* and package memory to *256.*
>> Filter works fine here yet. Call load is not that much only blacklist
>> entries are growing.
>>
>> But now blacklist has grown to very huge number, up to 10m records in
>> mysql. Opensips is n

Re: [OpenSIPS-Users] opensips will not start while loading huge blacklist

[Abdul Basit]

Yes. That's right.
The code I am using is as below. globalblacklist table has complete number
as prefix with and whitelist status.

route {
.
if ( !check_blacklist("globalblacklist") ) {
xlog("L_NOTICE","[$fU/$tU/$ci] [$rm] Destination [$rU] is not Allowed.
Dropping call.\n");
sl_send_reply("403", "Forbidden");
exit;
}
else {
xlog("L_INFO", "[$fU/$tU/$ci] [$rm] INBOUND CALL for [$ru]");
route(10);
exit;
}
.
}


--
regards,

abdul basit


On Mon, 1 Oct 2018 at 19:07, Bogdan-Andrei Iancu 
wrote:

> Hi Abdul,
>
> IF I understand correctly, you use startup route to load (from DB?) some
> blacklists into localcache ?
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   http://www.opensips-solutions.com
> OpenSIPS Bootcamp 2018
>   http://opensips.org/training/OpenSIPS_Bootcamp_2018/
>
> On 09/28/2018 04:10 AM, Abdul Basit wrote:
>
> Hi team,
>
> I have a opensips 2.4 deployed having 4 children and with mysql configured
> for loading user blacklist to opensips local cache on opensips startup.
> Opensips work fine on filtering the call based on user blacklist records
> loaded into local cache.
>
> While blacklist was growing upto 1.3m records, opensips startup was taking
> ~60 sec on VM of 16GB RAM and 6 CPU.
> I increased shared memory to *6144* and package memory to *256.*
> Filter works fine here yet. Call load is not that much only blacklist
> entries are growing.
>
> But now blacklist has grown to very huge number, up to 10m records in
> mysql. Opensips is not starting successfully and service startup requests
> timeout after huge CPU spikes while trying to populate local cache from
> mysql.
> I increased shared memory to *12288* and package memory to *1024* but no
> success yet.
>
> I indexed mysql blacklist table but no luck.
>
> Please advise what settings I should add to opensips for successful
> startup.
>
> --
> regards,
>
> abdul basit
>
>
> ___
> 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 will not start while loading huge blacklist

[Abdul Basit]

Hi Jon,

Thanks, I'll check it out with memcached and Redis both.
Current disturbance is opensips restart due to localcache loading from
mysql. Once loaded, it works like a charm.

Any idea about *-m* and *-M* vales? How much RAM was allocated to the box?

Opensips performed better when I increased shared and package memory.
I want to avoid overkill of resources.

--
regards,

abdul basit

On Sun, 30 Sep 2018 at 20:00, Jon Abrams  wrote:

> On the high CPS box its an old OpenSIPs 1.9 instance running 64 children
> IIRC on a pair of old 6 core Westmere Core Xeons. On a 2.2 box the code
> looks sort of like this:
>
> # memcached config
> modparam("cachedb_memcached", "cachedb_url", "memcached:blacklist://
> 127.0.0.1:11211/")
>
>
> # in the main route block
> if (cache_fetch("memcached: blacklist ", "$avp(key)", $avp(value)))
> {
>#reject the call or something
> }
>
> The only other possible downside to memcached is the lack of longest
> prefix match, which you may not need. You also need to build the Memcached.
>
> I don't have any OpenSIPs Redis code samples handy, as I think I've only
> used it with that other open source SIP server.
>
> Since the data is not being loaded into OpenSIPs memory, startup times are
> considerably faster. With memcached you need to remember or script it to
> reload the blacklist into memory on reboot or restart of memcached.
>
> With Redis you can persist it, although make sure check the performance
> hit when you turn on persistence. AOF isn't bad, especially with a SSD
> disk. The background save can add a bunch of latency when it kicks off.
> If its a lot of data, I usually do a BGSAVE once a day during off-peak
> times with a cron job. But I don't think 20-30 million entries will cause
> much disturbance.
>
> - Jon
>
> On Sun, Sep 30, 2018 at 9:13 AM Abdul Basit  wrote:
>
>> Hi Jon,
>>
>> Good to know.
>> If possible, can you share the settings you have for opensips?
>> Whats the server hardware specification?
>> Whats opensips service startup time?
>>
>> --
>> regards,
>>
>> abdul basit
>>
>> On Sun, 30 Sep 2018 at 05:17, Jon Abrams  wrote:
>>
>>> I have used memached to store 20-30 million entry blacklists while
>>> maintaining 6000-9000 responses per second on a dipping server. The
>>> downside is its not persistent.
>>>
>>> I've used redis as well to store the whole North American LNP database
>>> in memory, but I've only tried pushing it to a couple thousand CPS so far.
>>> I would imagine it would perform at least as well as the memcached if
>>> needed.
>>>
>>> I wouldn't worry about the speed difference between local cache speed
>>> and using Redis/Memcached over a socket in a normal deployment scenario.
>>>
>>> - Jon
>>>
>>> On Sat, Sep 29, 2018 at 6:17 PM Abdul Basit 
>>> wrote:
>>>
>>>> Hi team,
>>>>
>>>> I am thinking to do horizontal scaling through dispatcher module and
>>>> sharding the blacklist to 2 or 3 opensips nodes local cache.
>>>> or using redis for blacklist repository but local cache is even more
>>>> quick.
>>>>
>>>> Any comments or experience to share about the problem I am facing
>>>> currently?
>>>>
>>>> --
>>>> regards,
>>>>
>>>> abdul basit
>>>>
>>>>
>>>> On Fri, 28 Sep 2018 at 06:10, Abdul Basit  wrote:
>>>>
>>>>> Hi team,
>>>>>
>>>>> I have a opensips 2.4 deployed having 4 children and with mysql
>>>>> configured for loading user blacklist to opensips local cache on opensips
>>>>> startup.
>>>>> Opensips work fine on filtering the call based on user blacklist
>>>>> records loaded into local cache.
>>>>>
>>>>> While blacklist was growing upto 1.3m records, opensips startup was
>>>>> taking ~60 sec on VM of 16GB RAM and 6 CPU.
>>>>> I increased shared memory to *6144* and package memory to *256.*
>>>>> Filter works fine here yet. Call load is not that much only blacklist
>>>>> entries are growing.
>>>>>
>>>>> But now blacklist has grown to very huge number, up to 10m records in
>>>>> mysql. Opensips is not starting successfully and service startup requests
>>>>> timeout after huge CPU spikes while trying to populate local cache from
>>>>> mysql.
>>>>> I increased shared memory to *12288* and package memory to *1024* but
>>>>> no success yet.
>>>>>
>>>>> I indexed mysql blacklist table but no luck.
>>>>>
>>>>> Please advise what settings I should add to opensips for successful
>>>>> startup.
>>>>>
>>>>> --
>>>>> regards,
>>>>>
>>>>> abdul basit
>>>>>
>>>> ___
>>>> 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 will not start while loading huge blacklist

[Abdul Basit]

Hi Jon,

Good to know.
If possible, can you share the settings you have for opensips?
Whats the server hardware specification?
Whats opensips service startup time?

--
regards,

abdul basit

On Sun, 30 Sep 2018 at 05:17, Jon Abrams  wrote:

> I have used memached to store 20-30 million entry blacklists while
> maintaining 6000-9000 responses per second on a dipping server. The
> downside is its not persistent.
>
> I've used redis as well to store the whole North American LNP database in
> memory, but I've only tried pushing it to a couple thousand CPS so far. I
> would imagine it would perform at least as well as the memcached if needed.
>
> I wouldn't worry about the speed difference between local cache speed and
> using Redis/Memcached over a socket in a normal deployment scenario.
>
> - Jon
>
> On Sat, Sep 29, 2018 at 6:17 PM Abdul Basit  wrote:
>
>> Hi team,
>>
>> I am thinking to do horizontal scaling through dispatcher module and
>> sharding the blacklist to 2 or 3 opensips nodes local cache.
>> or using redis for blacklist repository but local cache is even more
>> quick.
>>
>> Any comments or experience to share about the problem I am facing
>> currently?
>>
>> --
>> regards,
>>
>> abdul basit
>>
>>
>> On Fri, 28 Sep 2018 at 06:10, Abdul Basit  wrote:
>>
>>> Hi team,
>>>
>>> I have a opensips 2.4 deployed having 4 children and with mysql
>>> configured for loading user blacklist to opensips local cache on opensips
>>> startup.
>>> Opensips work fine on filtering the call based on user blacklist records
>>> loaded into local cache.
>>>
>>> While blacklist was growing upto 1.3m records, opensips startup was
>>> taking ~60 sec on VM of 16GB RAM and 6 CPU.
>>> I increased shared memory to *6144* and package memory to *256.*
>>> Filter works fine here yet. Call load is not that much only blacklist
>>> entries are growing.
>>>
>>> But now blacklist has grown to very huge number, up to 10m records in
>>> mysql. Opensips is not starting successfully and service startup requests
>>> timeout after huge CPU spikes while trying to populate local cache from
>>> mysql.
>>> I increased shared memory to *12288* and package memory to *1024* but
>>> no success yet.
>>>
>>> I indexed mysql blacklist table but no luck.
>>>
>>> Please advise what settings I should add to opensips for successful
>>> startup.
>>>
>>> --
>>> regards,
>>>
>>> abdul basit
>>>
>> ___
>> 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 will not start while loading huge blacklist

[Abdul Basit]

Hi team,

I am thinking to do horizontal scaling through dispatcher module and
sharding the blacklist to 2 or 3 opensips nodes local cache.
or using redis for blacklist repository but local cache is even more quick.

Any comments or experience to share about the problem I am facing currently?

--
regards,

abdul basit


On Fri, 28 Sep 2018 at 06:10, Abdul Basit  wrote:

> Hi team,
>
> I have a opensips 2.4 deployed having 4 children and with mysql configured
> for loading user blacklist to opensips local cache on opensips startup.
> Opensips work fine on filtering the call based on user blacklist records
> loaded into local cache.
>
> While blacklist was growing upto 1.3m records, opensips startup was taking
> ~60 sec on VM of 16GB RAM and 6 CPU.
> I increased shared memory to *6144* and package memory to *256.*
> Filter works fine here yet. Call load is not that much only blacklist
> entries are growing.
>
> But now blacklist has grown to very huge number, up to 10m records in
> mysql. Opensips is not starting successfully and service startup requests
> timeout after huge CPU spikes while trying to populate local cache from
> mysql.
> I increased shared memory to *12288* and package memory to *1024* but no
> success yet.
>
> I indexed mysql blacklist table but no luck.
>
> Please advise what settings I should add to opensips for successful
> startup.
>
> --
> regards,
>
> abdul basit
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] opensips will not start while loading huge blacklist

[Abdul Basit]

Hi team,

I have a opensips 2.4 deployed having 4 children and with mysql configured
for loading user blacklist to opensips local cache on opensips startup.
Opensips work fine on filtering the call based on user blacklist records
loaded into local cache.

While blacklist was growing upto 1.3m records, opensips startup was taking
~60 sec on VM of 16GB RAM and 6 CPU.
I increased shared memory to *6144* and package memory to *256.*
Filter works fine here yet. Call load is not that much only blacklist
entries are growing.

But now blacklist has grown to very huge number, up to 10m records in
mysql. Opensips is not starting successfully and service startup requests
timeout after huge CPU spikes while trying to populate local cache from
mysql.
I increased shared memory to *12288* and package memory to *1024* but no
success yet.

I indexed mysql blacklist table but no luck.

Please advise what settings I should add to opensips for successful
startup.

--
regards,

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

Re: [OpenSIPS-Users] OpenSIPS Unable to parse msg received from

[Abdul Basit]

Hi Alain Bieuzent,

I added sip msg validate code in start of main route but i didn't get these
additional log lines.
Still getting messages from opensips core:

Aug 23 13:22:24 homer-proxy /usr/sbin/opensips[25568]:
ERROR:core:receive_msg: Unable to parse msg received from [x.x.x.x:61648]
Aug 23 13:22:27 homer-proxy /usr/sbin/opensips[25568]:
ERROR:core:parse_msg:
message=;tag=1c1737546331#015#012To:
#015#012Call-ID: c@x.x.x.x#015#012CSeq: 63697
REGISTER#015#012Authorization: Digest username="yy",realm="x.x.x.x"
,nonce="5b7e9911db6acf694065c578ff32fa51ce24bb374d67",uri="sip:x.x.x.x"
,algorithm=MD5,response="debec3f66d2ac1ec488138871ffa1d60"#015#012Contact:
;expires=360#015#012Supported:
em,timer,replaces,path,resource-priority#015#012Allow:
REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUBSCRIBE,UPDATE#015#012Expires:
360#015#012User-Agent: Audiocodes-Sip-Gateway-MP-118
FXS/v.5.20A.043.005#015#012Content-Length: 0#015#012#015#012>

Hi Bogdan,

Yes, I did it as per cfg in shared link. But again i am getting the parse
error messages. Looks like request is initiating from some buggy sip client.

Aug 23 13:43:39 homer-proxy /usr/sbin/opensips[26027]:
ERROR:core:parse_first_line: bad request first line
Aug 23 13:43:39 homer-proxy /usr/sbin/opensips[26027]:
ERROR:core:parse_first_line: at line 0 char 34:
Aug 23 13:43:39 homer-proxy /usr/sbin/opensips[26027]:
ERROR:core:parse_first_line: parsed so far: AudiocodesGW 1372031417
1372031297
Aug 23 13:43:39 homer-proxy /usr/sbin/opensips[26027]:
ERROR:core:parse_msg: message=
Aug 23 13:43:39 homer-proxy /usr/sbin/opensips[26027]:
ERROR:core:receive_msg: Unable to parse msg received from [x.x.x.x:64443]
Aug 23 13:43:40 homer-proxy /usr/sbin/opensips[26027]:
ERROR:core:parse_to_param: unexpected char [C] in status 13: <<;tag=#015#012
>> .
Aug 23 13:43:40 homer-proxy /usr/sbin/opensips[26027]: ERROR:core:parse_to:
unexpected end of header in state 13
Aug 23 13:43:40 homer-proxy /usr/sbin/opensips[26027]:
ERROR:core:get_hdr_field: bad to header
Aug 23 13:43:40 homer-proxy /usr/sbin/opensips[26027]:
ERROR:core:parse_to_param: unexpected char [C] in status 13: <<;tag=#015#012
>> .
Aug 23 13:43:40 homer-proxy /usr/sbin/opensips[26027]: ERROR:core:parse_to:
unexpected end of header in state 13
Aug 23 13:43:40 homer-proxy /usr/sbin/opensips[26027]:
ERROR:core:get_hdr_field: bad to header
Aug 23 13:43:40 homer-proxy /usr/sbin/opensips[26027]: ERROR:tm:t_check:
reply cannot be parsed

The impact I am getting is the homer UI is not showing complete sip ladder.

--
regards,

abdul basit | p: +92 32 1416 4196 | o: +92 30 0841 1445


On Thu, 9 Aug 2018 at 19:02, Bogdan-Andrei Iancu 
wrote:

> Hi Abdul,
>
> have you checked the tutorial on HEP switching ?
> https://blog.opensips.org/2017/10/12/opensips-as-hep-proxyswitch/
>
> Maybe you are using the wrong routes in the script.
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   http://www.opensips-solutions.com
> OpenSIPS Bootcamp 2018
>   http://opensips.org/training/OpenSIPS_Bootcamp_2018/
>
> On 08/09/2018 04:40 PM, Abdul Basit wrote:
>
> Hi Alain,
>
> Thank you for your suggestion.
> I will update cfg and get back with results.
>
> Do i need to upgrade opensips to 2.4 as well?
>
>
> --
> regards,
>
> abdul basit | p: +92 32 1416 4196 | o: +92 30 0841 1445
>
>
> On Thu, 9 Aug 2018 at 17:35, Alain Bieuzent 
> wrote:
>
>> Hi Abdul,
>>
>>
>>
>> try to add this part of code at the begining of your routing code to add
>> more logs :
>>
>>
>>
>> if(!sipmsg_validate(""))
>>
>> {
>>
>> xlog("L_WARN", "Dropping mal formed Messages Retcode : $retcode
>> ");
>>
>> xlog("L_WARN","--- error from [$si:$sp]\n+\n$mb\n\n");
>>
>> exit;
>>
>> }
>>
>>
>>
>> then you can find the retcode value there :
>> http://www.opensips.org/html/docs/modules/2.4.x/sipmsgops.html#func_sipmsg_validate
>>
>>
>>
>>
>>
>> *De : *Users  au nom de Abdul Basit <
>> basit.e...@gmail.com>
>> *Répondre à : *OpenSIPS users mailling list 
>> *Date : *jeudi 9 août 2018 à 14:18
>> *À : *OpenSIPS users mailling list 
>> *Objet : *[OpenSIPS-Users] OpenSIPS Unable to parse msg received from
>>
>>
>>
>> Hi Team,
>>
>>
>>
>> I am using opensips as hep proxy to distribute traffic to multiple homer
>> noes for trace capturing.
>>
>>
>>
>> # opensips -V
>>
>> version: opensips 2.3.2 (x86_64/linux)
>>
>> flags: STATS: On, DISA

Re: [OpenSIPS-Users] OpenSIPS Unable to parse msg received from

[Abdul Basit]

I upgraded home proxy server opensips just in case it may help resolving
the issues.

# opensips -V
version: *opensips 2.4.2* (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_MALLOC,
FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method support: poll, epoll, sigio_rt, select.
main.c compiled on  with gcc 6.3.0

But result is same. I am continuously getting parse_mgs errors.
any idea about fixation of the issue?

--
regards,

abdul basit


On Thu, 23 Aug 2018 at 16:52, Abdul Basit  wrote:

> Hi Alain Bieuzent,
>
> I added sip msg validate code in start of main route but i didn't get
> these additional log lines.
> Still getting messages from opensips core:
>
> Aug 23 13:22:24 homer-proxy /usr/sbin/opensips[25568]:
> ERROR:core:receive_msg: Unable to parse msg received from [x.x.x.x:61648]
> Aug 23 13:22:27 homer-proxy /usr/sbin/opensips[25568]:
> ERROR:core:parse_msg: 
> message= 70#015#012From: ;tag=1c1737546331#015#012To:
> #015#012Call-ID: c@x.x.x.x#015#012CSeq: 63697
> REGISTER#015#012Authorization: Digest username="yy",realm="x.x.x.x"
> ,nonce="5b7e9911db6acf694065c578ff32fa51ce24bb374d67",uri=
> "sip:x.x.x.x",algorithm=MD5,response="debec3f66d2ac1ec488138871ffa1d60"#015#012Contact:
> ;expires=360#015#012Supported:
> em,timer,replaces,path,resource-priority#015#012Allow:
> REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUBSCRIBE,UPDATE#015#012Expires:
> 360#015#012User-Agent: Audiocodes-Sip-Gateway-MP-118
> FXS/v.5.20A.043.005#015#012Content-Length: 0#015#012#015#012>
>
> Hi Bogdan,
>
> Yes, I did it as per cfg in shared link. But again i am getting the parse
> error messages. Looks like request is initiating from some buggy sip client.
>
> Aug 23 13:43:39 homer-proxy /usr/sbin/opensips[26027]:
> ERROR:core:parse_first_line: bad request first line
> Aug 23 13:43:39 homer-proxy /usr/sbin/opensips[26027]:
> ERROR:core:parse_first_line: at line 0 char 34:
> Aug 23 13:43:39 homer-proxy /usr/sbin/opensips[26027]:
> ERROR:core:parse_first_line: parsed so far: AudiocodesGW 1372031417
> 1372031297
> Aug 23 13:43:39 homer-proxy /usr/sbin/opensips[26027]:
> ERROR:core:parse_msg: message=  x.x.x.x#015#012s=Phone-Call#015#012c=IN IP4 x.x.x.x#015#012t=0 0#015#012m
> =audio 6070 RTP/AVP 8 96#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:96
> telephone-event/8000#015#012a=fmtp:96 0-15#015#012a=ptime:20#015#012a=
> sendrecv#015#012a=rtcp:6071 IN IP4 x.x.x.x#015#012>
> Aug 23 13:43:39 homer-proxy /usr/sbin/opensips[26027]:
> ERROR:core:receive_msg: Unable to parse msg received from [x.x.x.x:64443]
> Aug 23 13:43:40 homer-proxy /usr/sbin/opensips[26027]:
> ERROR:core:parse_to_param: unexpected char [C] in status 13: <<;tag=
> #015#012>> .
> Aug 23 13:43:40 homer-proxy /usr/sbin/opensips[26027]:
> ERROR:core:parse_to: unexpected end of header in state 13
> Aug 23 13:43:40 homer-proxy /usr/sbin/opensips[26027]:
> ERROR:core:get_hdr_field: bad to header
> Aug 23 13:43:40 homer-proxy /usr/sbin/opensips[26027]:
> ERROR:core:parse_to_param: unexpected char [C] in status 13: <<;tag=
> #015#012>> .
> Aug 23 13:43:40 homer-proxy /usr/sbin/opensips[26027]:
> ERROR:core:parse_to: unexpected end of header in state 13
> Aug 23 13:43:40 homer-proxy /usr/sbin/opensips[26027]:
> ERROR:core:get_hdr_field: bad to header
> Aug 23 13:43:40 homer-proxy /usr/sbin/opensips[26027]: ERROR:tm:t_check:
> reply cannot be parsed
>
> The impact I am getting is the homer UI is not showing complete sip ladder.
>
> --
> regards,
>
> abdul basit | p: +92 32 1416 4196 | o: +92 30 0841 1445
>
>
> On Thu, 9 Aug 2018 at 19:02, Bogdan-Andrei Iancu 
> wrote:
>
>> Hi Abdul,
>>
>> have you checked the tutorial on HEP switching ?
>> https://blog.opensips.org/2017/10/12/opensips-as-hep-proxyswitch/
>>
>> Maybe you are using the wrong routes in the script.
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>   http://www.opensips-solutions.com
>> OpenSIPS Bootcamp 2018
>>   http://opensips.org/training/OpenSIPS_Bootcamp_2018/
>>
>> On 08/09/2018 04:40 PM, Abdul Basit wrote:
>>
>> Hi Alain,
>>
>> Thank you for your suggestion.
>> I will update cfg and get back with results.
>>
>> Do i need to upgrade opensips to 2.4 as well?
>>
>>
>> --
>> regards,
>>
>> abdul basit | p: +92 32 1416 4196 | o: +92 30 0841 1445
>>
>>
>> On Thu, 9 Aug 2018 at 17:35, Alain Bieuzent 
>> wrote:
>>
>>> Hi Abdul,
>>

Re: [OpenSIPS-Users] OpenSIPS Unable to parse msg received from

[Abdul Basit]

Hi Team,
I received reply on August 23rd from list Your message to Users awaits
moderator approval
Can the moderator approve this thread?

--
regards,

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

Re: [OpenSIPS-Users] OpenSIPS Unable to parse msg received from

[Abdul Basit]

Hi Alain,

Thank you for your suggestion.
I will update cfg and get back with results.

Do i need to upgrade opensips to 2.4 as well?


--
regards,

abdul basit | p: +92 32 1416 4196 | o: +92 30 0841 1445


On Thu, 9 Aug 2018 at 17:35, Alain Bieuzent  wrote:

> Hi Abdul,
>
>
>
> try to add this part of code at the begining of your routing code to add
> more logs :
>
>
>
> if(!sipmsg_validate(""))
>
> {
>
> xlog("L_WARN", "Dropping mal formed Messages Retcode : $retcode ");
>
> xlog("L_WARN","--- error from [$si:$sp]\n+\n$mb\n\n");
>
> exit;
>
> }
>
>
>
> then you can find the retcode value there :
> http://www.opensips.org/html/docs/modules/2.4.x/sipmsgops.html#func_sipmsg_validate
>
>
>
>
>
> *De : *Users  au nom de Abdul Basit <
> basit.e...@gmail.com>
> *Répondre à : *OpenSIPS users mailling list 
> *Date : *jeudi 9 août 2018 à 14:18
> *À : *OpenSIPS users mailling list 
> *Objet : *[OpenSIPS-Users] OpenSIPS Unable to parse msg received from
>
>
>
> Hi Team,
>
>
>
> I am using opensips as hep proxy to distribute traffic to multiple homer
> noes for trace capturing.
>
>
>
> # opensips -V
>
> version: opensips 2.3.2 (x86_64/linux)
>
> flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC,
> F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
>
> ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
> MAX_URI_SIZE 1024, BUF_SIZE 65535
>
> poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
>
> main.c compiled on  with gcc 6.3.0
>
>
>
> Host operating system is
>
>
>
> # lsb_release -a
>
> No LSB modules are available.
>
> Distributor ID: Debian
>
> Description:Debian GNU/Linux 9.3 (stretch)
>
> Release:9.3
>
> Codename:   stretch
>
>
>
> I am continuously getting error on opensips logs. I have changed CLI as
> yyy and IPs as x.x.x.x
>
>
>
> Aug  9 13:47:00 homer-proxy /usr/sbin/opensips[6845]:
> ERROR:core:receive_msg: Unable to parse msg received from [x.x.x.x:39169]
>
> Aug  9 13:47:07 homer-proxy /usr/sbin/opensips[6847]:
> ERROR:core:parse_msg: message= 360#015#012User-Agent: Audiocodes-Sip-Gateway-MP-114
> FXS/v.5.20A.043.005#015#012Content-Length: 0#015#012#015#012>
>
> Aug  9 13:47:07 homer-proxy /usr/sbin/opensips[6847]:
> ERROR:core:receive_msg: Unable to parse msg received from [x.x.x.x:53693]
>
> Aug  9 13:47:07 homer-proxy /usr/sbin/opensips[6845]:
> ERROR:core:parse_msg: message= 360#015#012User-Agent: Audiocodes-Sip-Gateway-MP-114
> FXS/v.5.20A.043.005#015#012Content-Length: 0#015#012#015#012>
>
> Aug  9 13:47:07 homer-proxy /usr/sbin/opensips[6845]:
> ERROR:core:receive_msg: Unable to parse msg received from [x.x.x.x:33715]
>
> Aug  9 13:47:50 homer-proxy /usr/sbin/opensips[6845]:
> ERROR:core:parse_msg:
> message= 360#015#012User-Agent: Audiocodes-Sip-Gateway-MP-114
> FXS/v.5.20A.043.005#015#012Content-Length: 0#015#012#015#012>
>
> Aug  9 13:47:50 homer-proxy /usr/sbin/opensips[6845]:
> ERROR:core:receive_msg: Unable to parse msg received from [x.x.x.x:33715]
>
> Aug  9 13:48:15 homer-proxy /usr/sbin/opensips[6848]:
> ERROR:core:parse_method: invalid character =
>
> Aug  9 13:48:15 homer-proxy /usr/sbin/opensips[6848]:
> ERROR:core:parse_msg: message= G729/8000#015#012a=fmtp:18 annexb=no#015#012a=rtpmap:97
> iLBC/8000#015#012a=fmtp:97 mode=30#015#012a=rtpmap:110
> speex/8000#015#012a=rtpmap:117 speex/16000#015#012a=rtpmap:9
> G722/8000#015#012a=rtpmap:4 G723/8000#015#012a=fmtp:4
> annexa=no#015#012a=rtpmap:101 telephone-event/8000#015#012a=fmtp:101
> 0-16#015#012a=ptime:20#015#012a=sendrecv#015#012a=nortpproxy:yes#015#012>
>
> Aug  9 13:48:15 homer-proxy /usr/sbin/opensips[6848]:
> ERROR:core:receive_msg: Unable to parse msg received from [x.x.x.x:5060]
>
> Aug  9 13:48:24 homer-proxy /usr/sbin/opensips[6846]:
> ERROR:core:parse_msg:
> message= 360#015#012User-Agent: Audiocodes-Sip-Gateway-MP-118
> FXS/v.5.20A.043.005#015#012Content-Length: 0#015#012#015#012>
>
> Aug  9 13:48:39 homer-proxy /usr/sbin/opensips[6845]:
> ERROR:core:receive_msg: Unable to parse msg received from [x.x.x.x:37979]
>
> Aug  9 13:48:40 homer-proxy /usr/sbin/opensips[6845]:
> ERROR:core:parse_msg:
> message= 360#015#012User-Agent: Audiocodes-Sip-Gateway-MP-118
> FXS/v.5.20A.043.005#015#012Content-Length: 0#015#012#015#012>
>
> Aug  9 13:48:40 homer-proxy /usr/sbin/opensips[6845]:
> ERROR:core:receive_msg: Unable to parse msg received from [x.x.x.x:37979]
>
> Aug  9 13:48:44 homer-proxy /usr/sbin/opensips[6845]:
> ERROR:core:parse_met

[OpenSIPS-Users] OpenSIPS Unable to parse msg received from

[Abdul Basit]

Hi Team,

I am using opensips as hep proxy to distribute traffic to multiple homer
noes for trace capturing.

# opensips -V
version: opensips 2.3.2 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_MALLOC,
FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
main.c compiled on  with gcc 6.3.0

Host operating system is

# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux 9.3 (stretch)
Release:9.3
Codename:   stretch

I am continuously getting error on opensips logs. I have changed CLI as
yyy and IPs as x.x.x.x

Aug  9 13:47:00 homer-proxy /usr/sbin/opensips[6845]:
ERROR:core:receive_msg: Unable to parse msg received from [x.x.x.x:39169]
Aug  9 13:47:07 homer-proxy /usr/sbin/opensips[6847]: ERROR:core:parse_msg:
message=
Aug  9 13:47:07 homer-proxy /usr/sbin/opensips[6847]:
ERROR:core:receive_msg: Unable to parse msg received from [x.x.x.x:53693]
Aug  9 13:47:07 homer-proxy /usr/sbin/opensips[6845]: ERROR:core:parse_msg:
message=
Aug  9 13:47:07 homer-proxy /usr/sbin/opensips[6845]:
ERROR:core:receive_msg: Unable to parse msg received from [x.x.x.x:33715]
Aug  9 13:47:50 homer-proxy /usr/sbin/opensips[6845]: ERROR:core:parse_msg:
message=
Aug  9 13:47:50 homer-proxy /usr/sbin/opensips[6845]:
ERROR:core:receive_msg: Unable to parse msg received from [x.x.x.x:33715]
Aug  9 13:48:15 homer-proxy /usr/sbin/opensips[6848]:
ERROR:core:parse_method: invalid character =
Aug  9 13:48:15 homer-proxy /usr/sbin/opensips[6848]: ERROR:core:parse_msg:
message=
Aug  9 13:48:15 homer-proxy /usr/sbin/opensips[6848]:
ERROR:core:receive_msg: Unable to parse msg received from [x.x.x.x:5060]
Aug  9 13:48:24 homer-proxy /usr/sbin/opensips[6846]: ERROR:core:parse_msg:
message=
Aug  9 13:48:39 homer-proxy /usr/sbin/opensips[6845]:
ERROR:core:receive_msg: Unable to parse msg received from [x.x.x.x:37979]
Aug  9 13:48:40 homer-proxy /usr/sbin/opensips[6845]: ERROR:core:parse_msg:
message=
Aug  9 13:48:40 homer-proxy /usr/sbin/opensips[6845]:
ERROR:core:receive_msg: Unable to parse msg received from [x.x.x.x:37979]
Aug  9 13:48:44 homer-proxy /usr/sbin/opensips[6845]:
ERROR:core:parse_method: invalid character :
Aug  9 13:48:44 homer-proxy /usr/sbin/opensips[6845]: ERROR:core:parse_msg:
message=
Aug  9 13:48:44 homer-proxy /usr/sbin/opensips[6845]:
ERROR:core:receive_msg: Unable to parse msg received from [x.x.x.x:46187]
Aug  9 13:48:44 homer-proxy /usr/sbin/opensips[6845]:
ERROR:core:parse_method: invalid character :
Aug  9 13:48:44 homer-proxy /usr/sbin/opensips[6845]: ERROR:core:parse_msg:
message=
Aug  9 13:48:44 homer-proxy /usr/sbin/opensips[6845]:
ERROR:core:receive_msg: Unable to parse msg received from [x.x.x.x:46187]
Aug  9 13:49:37 homer-proxy /usr/sbin/opensips[6845]: ERROR:core:parse_msg:
message=;expires=360#015#012Supported:
em,timer,replaces,path,resource-priority#015#012Allow:
REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUBSCRIBE,UPDATE#015#012Expires:
360#015#012User-Agent: Audiocodes-Sip-Gateway-MP-118
FXS/v.5.20A.043.005#015#012Content-Length: 0#015#012#015#012REGISTER
sip:x.x.x.x SIP/2.0#015#012Via: SIP/2.0/TCP
192.168.1.17;branch=z9hG4bKac1134765850;alias#015#012Max-Forwards:
70#015#012From: ;tag=1c1134760571#015#012To:
#015#012Call-ID:
943343231120001012@192.168.1.17#015#012CSeq: 50295 REGISTER#015#012Contact:
;expires=360#015#012Supported:
em,timer,replaces,path,resource-priority#015#012Allow:
REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUBSCRIBE,UPDATE#015#012Expires:
360#015#012User-Agent: Audiocodes-Sip-Gateway-MP-118
FXS/v.5.20A.043.005#015#012Content-Length: 0#015#012#015#012REGISTER
sip:x.x.x.x SIP/2.0#015#012Via: SIP/2.0/TCP
192.168.1.17;branch=z9hG4bKac1134889896;alias#015#012Max-Forwards:
70#015#012From: ;tag=1c1134884593#015#012To:
#015#012Call-ID:
943363361120001012@192.168.1.17#015#012CSeq: 50295 REGISTER#015#012Contact:
;expires=360#015#012Supported:
em,timer,replaces,path,resource-priority#015#012Allow:
REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUBSCRIBE,UPDATE#015#012Expires:
360#015#012User-Agent: Audiocodes-Sip-Gateway-MP-118 FXS/v.5.20A.043.0>

Opensip is simply distributing the received hep traffic to the homer server
in the pool and not doing any processing by itself.
Can you suggest whats the cause of these errors and how can I correct them?
Where should I look for correction?

Thank you in advance.

--
regards,

abdul basit | p: +92 32 1416 4196 | o: +92 30 0841 1445
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] check_blacklist function Question

[Abdul Basit]

Never mind. Issue has been fixed.
I was overlooking the number. Few digits were different in next request
that fail the exact number match and causing call to go through.

--
regards,

abdul basit | p: +92 32 1416 4196 | o: +92 30 0841 1445


On Sun, 15 Jul 2018 at 06:12, Abdul Basit  wrote:

> Hi Team,
> I have a scenario where I have to block list certain numbers (premium
> ones).
> I populated these numbers with in "globalblacklist" table. I followed
> documentation:
>
> http://www.opensips.org/html/docs/modules/2.4.x/userblacklist.html#func_check_blacklist
>
> While part of destination number defined as prefix, like 1437,
> blacklisting works and all the calls starting with destination number
> '1437' will block.
> id prefix  whitelistdescription
> 1  1437 0NULL
>
> But for the required case, if I add full number in prefix column, like
> 14375436291, opensips will not block the call.
> id prefixwhitelistdescription
> 1  14375436291 0NULL
>
> How can i block list of full numbers through opensips?
>
> --
> regards,
>
> abdul basit
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] check_blacklist function Question

[Abdul Basit]

Hi Team,
I have a scenario where I have to block list certain numbers (premium ones).
I populated these numbers with in "globalblacklist" table. I followed
documentation:
http://www.opensips.org/html/docs/modules/2.4.x/userblacklist.html#func_check_blacklist

While part of destination number defined as prefix, like 1437, blacklisting
works and all the calls starting with destination number '1437' will block.
id prefix  whitelistdescription
1  1437 0NULL

But for the required case, if I add full number in prefix column, like
14375436291, opensips will not block the call.
id prefixwhitelistdescription
1  14375436291 0NULL

How can i block list of full numbers through opensips?

--
regards,

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

Re: [OpenSIPS-Users] Billing stack with Opensips and Cgrates

[Abdul Basit]

Nice work and especially sharing of your work.
Keep it up.

--
regards,

abdul basit


On Sat, 14 Jul 2018 at 15:30, Srigo Kanapathipillai 
wrote:

> Thank you Liviu!! I’m happy you like it, Its motivate me to write my
> projects.
>
> To answer your question, Dan asked me almost the same question:
> https://github.com/ksrigo/billing_system/issues/1. I think db_flatestore
> + CDRC is much simpler at least from maintaining perspective (we have less
> services to maintain). As soon as I get some details from Dan, I will test
> it and let you know.
>
> *Voice Engineer*
> *Srigo Kana*
>
>
> On 13 Jul 2018, at 11:11, Liviu Chircu  wrote:
>
> This is awesome, Srigo!  I'd be curious to see if there are any throughput
> differences between your "syslog - Filebeat - Logstash" stack vs. a
> "db_flatstore - " approach.  Nevertheless,
> this is the proper way to do it: de-coupled from SIP and de-coupled from DB.
>
> PS: I am the proud owner of your project's 1st Star
>
> Cheers,
>
> Liviu Chircu
> OpenSIPS Developerhttp://www.opensips-solutions.com
>
> On 13.07.2018 10:52, KSrigo wrote:
>
> Hi,
>
> Recently I have been working on implementing a Billing system at iBrowse.
> Throughout the process I wrote a tutorial.
> For those who are interested, I’m sharing it here:
>
> https://github.com/ksrigo/billing_system
>
> Please let me know your feedback.
>
> *Voice Engineer*
> *Srigo Kana*
>
>
> ___
> 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
>
>
> ___
> 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] [RELEASE] OpenSIPS 2.2.7, 2.3.4 and 2.4.1 minor releases

[Abdul Basit]

Congratulations!

On Thu, 24 May 2018 10:20 pm Bogdan-Andrei Iancu, 
wrote:

> Greetings again!
>
> I am glad to announce that our plan was successfully completed : the
> OpenSIPS minor releases 2.4.1, 2.3.4 and 2.2.7 are now out!
>
> After more time of spinning OpenSIPS in production environments we managed
> to track down and fix various bugs. You can find a full list of changes
> here:
>
> * OpenSIPS 2.4.1 ChangeLog:
> http://opensips.org/pub/opensips/2.4.1/ChangeLog
> 
> * OpenSIPS 2.3.4 ChangeLog:
> http://opensips.org/pub/opensips/2.3.4/ChangeLog
> 
> * OpenSIPS 2.2.7 ChangeLog:
> http://opensips.org/pub/opensips/2.2.7/ChangeLog
> 
>
> All of these were made possible by with the OpenSIPS community's help, for
> which we would like to thank you very much!
>
> Enjoy riding OpenSIPS!
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   http://www.opensips-solutions.com
> OpenSIPS Summit 2018
>   http://www.opensips.org/events/Summit-2018Amsterdam
>
> On 05/17/2018 01:39 PM, Bogdan-Andrei Iancu wrote:
>
> Greetings!
>
> A new cycle is about to be complete: OpenSIPS is tortured all over the
> worlds; this produces feedback and reports; and this translates into more
> fix, in a better stability of the released OpenSIPS versions.
>
> Shortly, it's time for a new set of minor releases, to officially
> incorporate all the fixes in the last months/weeks: OpenSIPS 2.2.7, 2.3.4
> and 2.4.1
>
> The new releases are due next week, on Wednesday, May 24th 2018.
>
> If you have any pending GitHub issues/mailing list bug threads concerning
> the mentioned branches, this would be a good time to bump them!
>
> Thank you for your contributions to this project!
>
> Best regards,
>
>
> ___
> 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] What would be the best way to get CDRs from opensips considering opensips handles heavy traffic load

[Abdul Basit]

You can use cgrates for CDR parsing from flat file system

On Sat, 5 May 2018 11:54 pm Ben Newlin,  wrote:

> We use the db_flatstore module to have Opensips write the CDRs from the
> ACC module directly to a file. We have a second application which reads the
> file and processes the CDRs separately.
>
>
>
> Thanks,
>
> Ben Newlin
>
>
>
> *From: *Users  on behalf of Aqs Younas <
> aqsyou...@gmail.com>
> *Reply-To: *OpenSIPS users mailling list 
> *Date: *Saturday, May 5, 2018 at 3:32 AM
> *To: *OpenSIPS users mailling list 
> *Subject: *Re: [OpenSIPS-Users] What would be the best way to get CDRs
> from opensips considering opensips handles heavy traffic load
>
>
>
> Thanks for reply. Opensips handles around 2000 concurrent calls with cps
> of 40 at the peak time. I see when opensips writes in ACC and my portal
> runs queries on the same table, opensips process almost comes to halt and a
> restart is always needed to make it alive.
>
>
>
> I want opensips to do something like just write CDRS in file/post
> somewhere or put in rabbitmq queue and do continue with processing sip
> traffic. Also, i would prefer to have something built-in instead of
> building my own CDRs.
>
>
>
> Best Regards,
>
>
>
> Aqs Younas
>
>
>
>
>
> On Sat, 5 May 2018 at 5:46 AM, Jon Abrams  wrote:
>
> If you don't need them immediately, you can use the old fashion write CDRS
> to syslog. Rotate the log file every so often to process the CDRs. Journald
> is too slow for this though - you must use rsyslog or syslog-ng.
>
> If you use the builtin OpenSIPS accounting and need results more
> real-time, then I'd look at RADIUS accounting. If you generate your own
> CDRs, then there are the event datagram and rabbitmq modules that provide
> opportunities.
>
> Out of curiosity, what do you consider heavy traffic?
>
> - Jon
>
>
>
> On Fri, May 4, 2018 at 4:32 PM, Aqs Younas  wrote:
>
> Greeting list,
>
>
>
> I would like to ask expert option,  how they are getting CDRs from
> opensips which handles heavy traffic.
>
>
>
> Actually I don't want to have opensips mantain database connections and
> write records in a single table acc.
>
>
>
> Best Regards,
>
>
>
> Aqs Younas
>
>
>
> ___
> 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] Fwd: [SR-Users] MSILO: SIP stored offline MESSAGE repetitive delivery

[Abdul Basit]

Hi Opensips team,

I faced instant message timeout issues with MSILO module while setting SIP
IM server using kamailio.
It turned out that fr_timer values was too low to wait for MESSAGE delivery
to the destination (online/offline both cases) that server was replying
with 408.
Which result in message sending failed on sending side where as IM was
reaching to the destination.

The same issue is true for msilo sample configuration
<http://www.opensips.org/html/docs/modules/2.3.x/msilo.html#idp5682352> for
opensips.
Kindly update it at your end as well. This will save lot of time for the
ones who want to use opensips as IM server.

--
regards,

abdul basit | p: +92 32 1416 4196 | o: +92 30 0841 1445

-- Forwarded message --
From: Abdul Basit <basit.e...@gmail.com>
Date: 13 April 2018 at 02:28
Subject: Re: [SR-Users] MSILO: SIP stored offline MESSAGE repetitive
delivery
To: Henning Westerholt <h...@kamailio.org>


Thanks Henning.

Good move. You removed the timers so that they use their default values :)

Same need to be done in sample msilo script
https://kamailio.org/docs/modules/5.1.x/modules/msilo.html#idp45433660

Who will be doing that?


--
regards,

abdul basit | p: +92 32 1416 4196 | o: +92 30 0841 1445

On 13 April 2018 at 00:37, Henning Westerholt <h...@kamailio.org> wrote:

> On Thursday, 12 April 2018 10:15:19 CEST Abdul Basit wrote:
> > My issue for IM handling has been resolved.
> >
> > @MS helped to look into the matter. From to the example
> > [..]
> >
> > I replaced it as below
> >
> > # -- tm params --
> >
> > modparam("tm", "fr_timer", 1 )
> > modparam("tm", "fr_inv_timer", 15 )
> > modparam("tm", "wt_timer", 10 )
> >
> >
> > Lower fr_timer was initiating 408 without waiting for 200 OK from
> > destination because 10ms is too low. This was confusing msilo module and
> > the sender device that MESSAGE sent was failed.
> > Increasing the fr_timer value resolved the issue.
> > This also resolved a ripple effect. i.e, kamailio delivery of offline
> > messages from DB store to the destination party.
> > Since kamailio was get message delivery error, it was
> > executing failure_route[1] that was storing the message again in DB store
> > as offline message and so on.
> >
> > lower fr_timer values are also exits in 3.x, 4.x, 5x and dev branches
> > documentation.
> > [..]
>
> Hello Abdul,
>
> great that you found the issue. I have fixed this issue in git master and
> also
> 5.1 and 5.0 branch.
>
> Best regards,
>
> Henning
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Send LUA logs via HEP to Homer server

[Abdul Basit]

Thank you for prompt reply.

I will look into it.


--
regards,

abdul basit


On 16 January 2018 at 23:08, Serge S. Yuriev <m...@nevian.org> wrote:

> Hi
>
> I believe you should look at Pastash from Homer authors
>
> --
> Wbr, Serge via mobile
>
> 16.01.2018, 19:59, "Abdul Basit" <basit.e...@gmail.com>:
>
> Hi team,
>
> I am processing incoming INVITE events in my lua script.
> To print the logs with kamailio syslog, i am using
>
>  sr.log("info", "-- Collecting data from kamailio -- ")
>
> I am searching for a way to send selective logs for an incoming call from
> lua script through HEP3 towards Homer server.
>
> How can I make it work? What utility or library is helpful.
>
> *PS:* captagent is configured on the same server for SIP traces.
>
> I know this should go to kamailio team, but how opensips will implement
> this lua integration with HEP.
>
> --
> regards,
>
> abdul basit
>
>
> ___
> 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] Send LUA logs via HEP to Homer server

[Abdul Basit]

Hi team,

I am processing incoming INVITE events in my lua script.
To print the logs with kamailio syslog, i am using

 sr.log("info", "-- Collecting data from kamailio -- ")

I am searching for a way to send selective logs for an incoming call from
lua script through HEP3 towards Homer server.

How can I make it work? What utility or library is helpful.

*PS:* captagent is configured on the same server for SIP traces.

I know this should go to kamailio team, but how opensips will implement
this lua integration with HEP.

--
regards,

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

Re: [OpenSIPS-Users] Error: invalid sendtoparameters

[Abdul Basit]

please share you opnesips.cfg especially the section you configured listen
parameter.

what's opensips version and OS you are using?

--
regards,

abdul basit | p: +92 32 1416 4196 | o: +92 30 0841 1445

On 20 October 2017 at 09:22, Nabeel <nabeelshik...@gmail.com> wrote:

> Hello,
>
> Please help me understand this error below. Is it of concern?
> The server is not bound to localhost, it is bound to public IPs.
>
>
>> Oct 20 05:10:12 server2 /usr/local/sbin/opensips[923]:
>> ERROR:core:proto_udp_send: sendto(sock,0x7f1f89c2bcf0,4,0,0x7ffc5f146db0,16):
>> Invalid argument(22)
>> Oct 20 05:10:12 server2 /usr/local/sbin/opensips[923]:
>> CRITICAL:core:proto_udp_send: invalid sendtoparameters#012one possible
>> reason is the server is bound to localhost and#012attempts to send to the
>> net
>> Oct 20 05:10:12 server2 /usr/local/sbin/opensips[923]:
>> ERROR:nathelper:msg_send: send() for proto 1 failed
>> Oct 20 05:10:12 server2 /usr/local/sbin/opensips[923]:
>> ERROR:nathelper:nh_timer: sip msg_send failed!
>
>
>
> ___
> 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] ClueCon Slides: Industrial Grade FreeSWITCH, Scaling, Balancing, High Availability, SIP, WebRTC

[Abdul Basit]

nice presentation!!!

--
regards,

abdul basit | p: +92 32 1416 4196 | o: +92 30 0841 1445

On 10 August 2017 at 23:12, Giovanni Maruzzelli <gmar...@gmail.com> wrote:

> *Industrial Grade FreeSWITCH Scaling, Balancing and High Availability for
> SIP and WebRTC*
>
> Scaling your FreeSWITCH platform to serve a growing user base is a
> critical challenge. We'll go through the best techniques, practices, and
> implementations for Voice and Video Calls, Conferencing, WebRTC, SIP,
> Chatting, Presence and Instant Messaging
> Slides can also be downloaded from http://opentelecom.it/cluecon2017.pdf
>
> Enjoy ClueCon!
>
> -giovanni
>
> --
>
> Sincerely,
>
> Giovanni Maruzzelli
> OpenTelecom.IT
> cell: +39 347 266 56 18
>
> ___
> 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] SIP password auth mechanism

[Abdul Basit]

Hi Bogdan,

Sorry for very late reply. I couldn't find any implementation if *EC-SRP *yet.

However, Ejabbered implemented https://en.wikipedia.org/wiki/
Salted_Challenge_Response_Authentication_Mechanism *(SCRAM)*
<https://en.wikipedia.org/wiki/Salted_Challenge_Response_Authentication_Mechanism>

This is interesting model and can be adopted for SIP based services as
well.

--
regards,

abdul basit | p: +92 32 1416 4196 | o: +92 30 0841 1445

On Fri, Mar 10, 2017 at 8:29 PM, Bogdan-Andrei Iancu <bog...@opensips.org>
wrote:

> Hi Abdul,
>
> I see that's a draft, so hard to judge on how far it will get. And
> something like this is not on our roadmap, maybe because of its very, very
> low priority in terms of needs. Do you have any idea if anyone actually
> implemented this ?
>
> Regards,
>
> Bogdan-Andrei Iancu
>   OpenSIPS Founder and Developer
>   http://www.opensips-solutions.com
>
> OpenSIPS Summit May 2017 Amsterdam
>   http://www.opensips.org/events/Summit-2017Amsterdam.html
>
> On 03/09/2017 12:37 PM, Abdul Basit wrote:
>
> Hi Geeks,
>
> While exploring further I found a draft explaining elliptic curve secure
> remote protocol (*EC-SRP*) for SIP authentication
> https://tools.ietf.org/html/draft-liu-sipcore-ec-srp5-03
>
> This explanation seems align with my requirements of not storing password
> in database.
> UAC and UAS both should support EC-SRP.
>
> Do we have any road-map of opensips implementing of EC-RSP or similar
> authentication mechanism?
> I will check the same with PJSIP because i couldn't find any traces on
> their forum as well.
>
> --
> regards,
>
> abdul basit
>
>
> On Wed, Mar 8, 2017 at 9:53 PM, Abdul Basit <basit.e...@gmail.com> wrote:
>
>> Hi Bogdan,
>>
>> I am using PJSIP as UAC and Opensips as UAS with radius for AAA.
>> I wanted to avoid getting into the code but let me check the flexibility.
>>
>> Thank you for your reply :)
>>
>> --
>> regards,
>>
>> abdul basit
>>
>> On Wed, Mar 8, 2017 at 1:34 AM, Bogdan-Andrei Iancu <
>> <bog...@opensips.org>bog...@opensips.org> wrote:
>>
>>> Hi Abdul,
>>>
>>> Besides the digest auth, there is no other standard auth mechanism for
>>> SIP, AFAIK.
>>>
>>> If you have control over the SIP UAC, of course, you could try to build
>>> your own auth mechanism - OpenSIPS offers enough flexibility in terms of
>>> both header manipulation and data computing.
>>>
>>> Regards,
>>>
>>> Bogdan-Andrei Iancu
>>>   OpenSIPS Founder and Developer
>>>   http://www.opensips-solutions.com
>>>
>>> OpenSIPS Summit May 2017 Amsterdam
>>>   http://www.opensips.org/events/Summit-2017Amsterdam.html
>>>
>>> On 03/07/2017 10:26 AM, Abdul Basit wrote:
>>>
>>> Hi,
>>> I have a scenario where I will create password HASH = SALT + STRING and
>>> save SALT and resulted HASH only in DB. I will transport random STRING
>>> value to my custom sip application as password.
>>> Digest authentication is not comply with this requirement. Is that any
>>> supported authentication mechanism that can fulfill this requirement.
>>> or is there any more appropriate authentication mechanism by
>>> opensips/kamailio?
>>> One of the objectives is in case DB will compromise, users passwords
>>> will not available because random STRING will not store in DB.
>>> Looking forward for suggestions and comments.
>>> -- regards,
>>> abdul basit
>>>
>>> ___
>>> 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-Devel] New MediaProxy Release version 2.6.6

[Abdul Basit]

Nice. Let's test.

On 8 May 2017 20:22, "Adrian Georgescu"  wrote:

> Hello,
>
> There is a new Mediaproxy software available
>
> Changelog mediaproxy (2.6.6)
>
>* Updated list of non-routable IP addresses and the corresponding RFC
>
> The software is packaged for latest Debian and Ubuntu versions.
>
> To update or install the software follow the instructions at
>
> http://mediaproxy.ag-projects.com
>
> Regards,
> Adrian
>
>
> ___
> Devel mailing list
> de...@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] SIP password auth mechanism

[Abdul Basit]

Hi Bogdan,

I am using PJSIP as UAC and Opensips as UAS with radius for AAA.
I wanted to avoid getting into the code but let me check the flexibility.

Thank you for your reply :)

--
regards,

abdul basit

On Wed, Mar 8, 2017 at 1:34 AM, Bogdan-Andrei Iancu <bog...@opensips.org>
wrote:

> Hi Abdul,
>
> Besides the digest auth, there is no other standard auth mechanism for
> SIP, AFAIK.
>
> If you have control over the SIP UAC, of course, you could try to build
> your own auth mechanism - OpenSIPS offers enough flexibility in terms of
> both header manipulation and data computing.
>
> Regards,
>
> Bogdan-Andrei Iancu
>   OpenSIPS Founder and Developer
>   http://www.opensips-solutions.com
>
> OpenSIPS Summit May 2017 Amsterdam
>   http://www.opensips.org/events/Summit-2017Amsterdam.html
>
> On 03/07/2017 10:26 AM, Abdul Basit wrote:
>
> Hi,
>
> I have a scenario where I will create password HASH = SALT + STRING and
> save SALT and resulted HASH only in DB.
>
> I will transport random STRING value to my custom sip application as
> password.
>
> Digest authentication is not comply with this requirement.
>
> Is that any supported authentication mechanism that can fulfill this
> requirement.
> or is there any more appropriate authentication mechanism by
> opensips/kamailio?
>
> One of the objectives is in case DB will compromise, users passwords will
> not available because random STRING will not store in DB.
>
> Looking forward for suggestions and comments.
>
> --
> regards,
>
> abdul basit
>
>
> ___
> 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

[OpenSIPS-Users] SIP password auth mechanism

[Abdul Basit]

Hi,

I have a scenario where I will create password HASH = SALT + STRING and
save SALT and resulted HASH only in DB.

I will transport random STRING value to my custom sip application as
password.

Digest authentication is not comply with this requirement.

Is that any supported authentication mechanism that can fulfill this
requirement.
or is there any more appropriate authentication mechanism by
opensips/kamailio?

One of the objectives is in case DB will compromise, users passwords will
not available because random STRING will not store in DB.

Looking forward for suggestions and comments.

--
regards,

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

Re: [OpenSIPS-Users] [RELEASE] OpenSIPS minor releases: 2.2.3 and 1.11.10

[Abdul Basit]

good work team

--
regards,

abdul basit | p: +92 32 1416 4196 | o: +92 30 0841 1445

On Fri, Feb 24, 2017 at 8:38 PM, Ramachandran, Agalya (Contractor) <
agalya_ramachand...@comcast.com> wrote:

> Thank you Liviu. I will try in the latest version and will update you my
> observation.
>
>
>
> Regards,
> Agalya
>
>
>
> *From:* Users [mailto:users-boun...@lists.opensips.org] *On Behalf Of *Liviu
> Chircu
> *Sent:* Friday, February 24, 2017 3:44 AM
> *To:* users@lists.opensips.org
> *Subject:* Re: [OpenSIPS-Users] [RELEASE] OpenSIPS minor releases: 2.2.3
> and 1.11.10
>
>
>
> Hi Agalya,
>
> There are no specific fixes addressing this issue, since it should be
> working right out of the box - libcurl should be able to handle it.
> Personally, I haven't been able to reproduce it. If problems persist for
> you even in 2.2.3, we are here to help!
>
> Regards,
>
>
> Liviu Chircu
>
> OpenSIPS Developer
>
> http://www.opensips-solutions.com
>
> On 24.02.2017 00:00, Ramachandran, Agalya (Contractor) wrote:
>
> Hi Liviu,
>
>
>
> Its great news. I have a question with respect to rest_client module.
>
> Does async with https support is added in 2.2.3?
>
>
>
> Regards,
>
> Agalya
>
>
>
> *From:* Users [mailto:users-boun...@lists.opensips.org
> <users-boun...@lists.opensips.org>] *On Behalf Of *Liviu Chircu
> *Sent:* Thursday, February 23, 2017 12:57 PM
> *To:* OpenSIPS users mailling list <users@lists.opensips.org>
> <users@lists.opensips.org>; OpenSIPS devel mailling list
> <de...@lists.opensips.org> <de...@lists.opensips.org>;
> n...@lists.opensips.org
> *Subject:* [OpenSIPS-Users] [RELEASE] OpenSIPS minor releases: 2.2.3 and
> 1.11.10
>
>
>
> Hi, all!
>
>
>
> We are happy to announce a new set of OpenSIPS minor versions, namely 2.2.3 
> and 1.11.10,
>
> incorporating the last 4 months of backports and no less than 126 commits!
>
>
>
> While roughly half of these commits strictly relate to static code analysis 
> issues
>
> (thank you Răzvan for the Coverity initiative!), the rest of them include
>
> important corner-case fixes in more critical areas such as the TCP layer, 
> usrloc contact management,
>
> dialog replication, dispatcher, drouting, rest_client - to name a few.
>
>
>
> All three releases are ready for production use and even more  
> stable/accurate than before.
>
> Since they contain the latest bug fixes, we strongly recommend you to upgrade 
> your current instances.
>
>
>
> Thank you all for your reports, fixes, pull requests and all other 
> contributions to this project!
>
>
>
> The full ChangeLogs for the newly released versions are:
>
> http://opensips.org/pub/opensips/2.2.3/ChangeLog
>
> http://opensips.org/pub/opensips/1.11.10/ChangeLog
>
>
>
> Get the latest versions from:
>
> http://opensips.org/pub/opensips/
>
>
>
> Enjoy OpenSIPS,
>
> --
>
> Liviu Chircu
>
> OpenSIPS Developer
>
> http://www.opensips-solutions.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
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] scheduled concurrent call reporting

[Abdul Basit]

Khalil,

Why don't you consider snmpstat module for stats collection from opensips?


On 25 Jan 2017 17:12, "Khalil Khamlichi"  wrote:

> Liviu, you just saved my day. my plan is to push information to redis
> every 10s maybe 5s if need there is, when dashboard is complete I might
> consider saving the stream of data for plotting and further analysis.
>
>
> On Wed, Jan 25, 2017 at 11:45 AM, Liviu Chircu  wrote:
>
>> I do not see any problems with calling "get_profile_size()" from timer
>> routes, event routes, etc. As such, you can safely bypass the block
>> restriction using the following example:
>>
>> route [get_prof_sz_inboundCalls] {
>> get_profile_size("inboundCalls",,"$var(size)");
>> }
>>
>> route [get_prof_sz_outboundCalls] {
>> get_profile_size("outboundCalls",,"$var(size)");
>> }
>>
>> timer_route [mytimer, 1]
>> {
>> route(get_prof_sz_inboundCalls);
>> xlog("inboundCalls: $var(size)\n");
>>
>> route(get_prof_sz_outboundCalls);
>> xlog("outboundCalls: $var(size)\n");
>> }
>>
>> Regards,
>>
>> Liviu Chircu
>> OpenSIPS Developerhttp://www.opensips-solutions.com
>>
>> On 24.01.2017 01:05, Khalil Khamlichi wrote:
>>
>> the idea is that I don't need to get the number of calls 30 times per
>> second which would happens if I save to redis on each invite. scheduling
>> the saving to redis every 10 seconds serves  well my purpose but the
>> timer_route doesn't seem to accept get_profile_size()
>>
>> any hints would be appreciated.
>>
>> On Mon, Jan 23, 2017 at 10:39 PM, Khalil Khamlichi <
>> khamlichi.kha...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I am trying to get call load information out of opensips at regular
>>> intervals to get some sort of realtime view of the load on the server.
>>>
>>> After applying profiles on the the INVITEs, I have tried to call
>>> get_profile_size from a timer_route.
>>> I am getting error :
>>>
>>> CRITICAL:core:yyerror: parse error in config file
>>> /usr/local//etc/opensips/opensips.cfg, line 483, column 38-39: Command
>>> cannot be used in the block
>>>
>>> Any alternative solutions ?
>>>
>>> Thanks in advance.
>>>
>>> kkh
>>>
>>
>>
>>
>> ___
>> 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
>>
>>
>
> ___
> 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] Release] OpenSIPS 2.2.0 Beta is out !

[Abdul Basit]

Interesting!!!
On 31 Mar 2016 23:48, "Hristo Donev"  wrote:

> Hello,
>
> Thanks for your great project.
> All working fine!
>
> Thank you !!!
>
> Hristo Donev
> VoIP support Center BG-Tel
> web: www.bg-tel.com
>
> 2016-03-31 19:13 GMT+03:00 Bogdan-Andrei Iancu :
>
>> Hi all,
>>
>> In the name of the entire OpenSIPS team, I'm proud to announce the
>> release of the OpenSIPS 2.2.0 Beta.
>>
>> This version continues the work from 2.1 and extends the async support in
>> other parts like RADIUS, LDAP, HEP or sleep(). In the same time it brings
>> new interesting and useful features like:
>> * build-in clustering support (data replication and sharing without
>> shared storage)
>> * advanced SIP Capturing and HEP proxying (powerful and flexible SIP
>> tracing, HEPv3 switching)
>> * WSS support
>> * SQL Cacher (ability to cache generic SQL tables)
>> * enhanced events support (text backend, load balancing & redundancy
>> in delivery)
>> * realtime monitoring of registered end-points
>> * in-dialog pinging with re-INVITEs
>> and many other :
>> http://www.opensips.org/About/Version-2-2-0
>>
>> The performance, the ability to debug and troubleshoot, the integration
>> effort, all were part of the work for OpenSIPS 2.2.0
>>
>> OpenSIPS 2.2 is the result of the whole community effort - there were
>> many people involved, actively contributing with code, helping with testing
>> and reporting - and we want to thank you all for making this release
>> possible:
>> https://github.com/OpenSIPS/opensips/blob/2.2/CREDITS
>>
>> Version 2.2 is a release candidate - the stable GA version is to be
>> release in the next  month, after more in depth testing .
>>
>> You can download OpenSIPS 2.2.0
>> http://opensips.org/pub/opensips/latest/
>> Also, thanks to Nick Altmann, the YUM and APT repos are populated with
>> the 2.2.0 packages:
>> yum.opensips.org
>> apt.opensips.org
>>
>> Enjoy,
>>
>> --
>> Bogdan-Andrei Iancu
>> OpenSIPS Founder and Developer
>> http://www.opensips-solutions.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
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] [OpenSIPS-Devel] [RELEASE] OpenSIPS 2.1.1 is now available

[Abdul Basit]

Great news!!!
On Aug 19, 2015 11:04 PM, Bogdan-Andrei Iancu bog...@opensips.org wrote:

 Hello everyone,

 Minor version 2.1.1 is now available on branch 2.1. This is a release
 bringing multiple and valuable fixes, a result of the continues work of
 testing and fixing the revolutionary 2.1 version.

 Please update as soon as possible as it worth it ! Download the tarball
 with sources from :
 http://opensips.org/pub/opensips/2.1.1/

 RPM and DEB packages will be shortly available on the official
 repositories, after the nightly builts.

 There are hundreds of reports, tens of fixes and maybe several hundreds of
 commits - all these are the result of the entire OpenSIPS community -
 people testing, reporting and fixes. And I want to thanks to all these
 people, to these OpenSIPS'ers !

 Enjoy 2.1.1 !!

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


 ___
 Devel mailing list
 de...@lists.opensips.org
 http://lists.opensips.org/cgi-bin/mailman/listinfo/devel

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

Re: [OpenSIPS-Users] Lawful solution with opensips/rtp proxy

[Abdul Basit]

Hi.

any idea or pointer to some blog regarding lawful intercept solution.
On Apr 13, 2015 5:30 PM, Abdul Basit basit.e...@gmail.com wrote:

 Hi,

 I am searching for LI solution that can integrate with opensips and rtp
 proxy for LEA.

 Can anyone suggest for a model for HI1, HI2 and HI3 interfaces for
 monitoring and interception according to ETSI standards?

 Is there any ready made product available in market.

 --
 regards,

 abdul basit

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

[OpenSIPS-Users] Lawful solution with opensips/rtp proxy

[Abdul Basit]

Hi,

I am searching for LI solution that can integrate with opensips and rtp
proxy for LEA.

Can anyone suggest for a model for HI1, HI2 and HI3 interfaces for
monitoring and interception according to ETSI standards?

Is there any ready made product available in market.

--
regards,

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